Remotely monitor and service customer equipment

Completed

Microsoft’s Connected Field Service Solution for Dynamics 365 combines monitoring and preventative maintenance with the Internet of Things (IoT). It replaces your traditional break-fix service model with a more proactive never-fail model. Your organization can capture all the information that is being transmitted from your IoT-enabled devices and turn that information into actionable items that can be executed directly from a Dynamics 365 instance.

Diagram of information being transmitted from IoT-enabled device.

Customer assets such as appliances, equipment, sensors, or any IoT-enabled device can be registered with an Azure IoT Hub or with a custom IoT provider from within Dynamics 365 or the Field Service mobile application. Assets that contain multiple sensors can be grouped and registered at one time to simplify deployment. For example, a refrigerator might be equipped with multiple sensors. It might contain a temperature sensor that monitors the overall temperature of the unit. But it might also contain multiple moisture sensors that monitor specific moisture levels of specific zones. It might even contain a motion sensor that monitors how often the door of the unit is opened.

Once you register a sensor-equipped asset that is connected to the internet as an IoT device, it begins sending information to an Azure IoT Hub or a custom IoT hub connection. So if the asset is the refrigerator, it sends information such as temperature readings. When a spike or drop in temperature is detected, an alert is surfaced for the device in Dynamics 365. Based on the conditions defined in the alert (type, severity, and so on), it can trigger an automated process that helps with handling and resolving the alert. For example, if a compressor unit on a device fails, your organization might elect to dispatch a technician as soon as possible. A work order can be automatically created, and the specific compressor needed to resolve the issue can be added to the work order as a necessary part.

Diagram showing a list of Devices and the Alerts associated with each.

Sometimes when an alert is triggered it might not require on-site assistance. You might interact with the device remotely by sending commands directly to the device from within Dynamics 365. For example, if an increase in temperature is detected, it might get routed to a specific queue where a technician might remotely send a command to the device to perform a firmware update.

Diagram of an alert detected, queue it is routed to, and technician remotely sending a command to the device for a firmware update.

Devices can be grouped into categories to make it easier to define specific properties that are unique to those types of devices. Each alert that is triggered or remote command that is sent to a device is stored directly in Dynamics 365. So you can easily view the history of what has occurred and what actions have been taken on those devices. Because the records are stored in Dynamics 365, you can easily create business process flows that can help with:

  • Troubleshooting procedures.

  • Remotely sending commands.

  • Routing items to queues.

  • Creating work orders.

You can make all the information captured available to technicians from within the mobile app when they're dispatched. So they have a complete history available to them when they arrive at a customer location.

As we work through the remainder of this module, we examine each of the steps involved in more detail.

Reference video link: Use Connected Field Service to remotely monitor and service customer equipment