Device data

Completed

IoT devices generate data. At any given time, an IoT device sensor communicates reporting information about the device. The information that is being reported is called a property. An IoT device property might be a temperature reading, a humidity reading, or the wireless network that the device is connected to. Depending on settings and thresholds that are defined for devices in the IoT hub that is being used, systems might or might not decide to do something with that information. For example, a temperature sensor is constantly reporting the current temperature. When that temperature exceeds a predetermined threshold, it might report that reading somewhere.

Organizations that are using Dynamics 365 Field Service can retrieve that information and pull it into their Field Service environment. After the wireless network and transmitting channel properties are set on a device, you can pull the device data and view current reported properties in Connected Field Service. Based on the information that is pulled down, an organization might use this information to determine the next steps in the application.

In Dynamics 365, the Connected Field Service device data can be captured in multiple ways:

  • Pull Device Data - Initiates a device data pull directly from the IoT Device record in Field Service.

  • IoT Alert - When an alert is generated, details about the alert are sent to Connected Field Service.

  • Scheduled Data Pull - Similar to a direct device data pull, except that it is done on a defined schedule.

Pull device data

The simplest way to pull in data from a device is by doing a device data pull. While you are on the IoT Device record, you can select the Pull Device Data button on the command bar, which will pull in the most recent data from the device. The Pull Device Data button is also available on customer asset records. If the asset is connected to IoT devices, selecting the Pull Device Data button will pull the data for all connected IoT devices.

Screenshot of Field Service showing an IoT device, with the Pull Device Data option highlighted.

After the data has been pulled down, a list of the data pulls for the device will be available on the Device Data History tab.

Device data on IoT alerts

Another way that data is reported is through IoT alerts. Alerts are generated when a threshold is crossed in IoT Hub, such as a temperature that exceeds a reading that has been classified as safe. Based on the IoT Hub solution that you are using, an automation can be triggered that will send this data to Dynamics 365 Field Service. This information is captured in an IoT alert record. When an alert is triggered, device data is automatically pulled for the associated device.

Screenshot of an IoT alert in Field Service.

Organizations can use the data in the alert record to help determine the next steps. For example, if the temperature exceeded a threshold but was within a specific range, you might elect to interact remotely. If it wasn't reporting data or was outside a safe range, you might want to dispatch someone to work on it. This concept is discussed in depth later.

Schedule device data pulls

If your organization uses an Azure IoT Hub as your IoT provider, you can also schedule device data pulls to happen when you need them. By scheduling device pulls on a regular schedule, you can ensure that the most current data readings are available as you need them.

Defining a schedule is done from the Settings area of the Connected Field Service application. Select the IoT Settings record and then select the Device Data Pulls tab. After you have turned on this setting, you can configure the frequency of the data pulls based on your needs.

Screenshot of the IoT Settings record on the Device Data Pulls tab.