Anomaly Detector

Overview

This flow is used to notify a user when an anomaly is detected allowing to review the report and send a work order if needed.

Description

This flow collects all the measurement readings from the IoT device and saves them in the IFS serial object and notifies the flow user when there is an Anomaly detected.
This flow can handle:
This application is capable of:
  • Review the prior measurements in a tabular and a graphical view
  • View previously created work orders
  • Create a new work order

Steps

1. IFS IoT Device Map

Use this basic data window to create or edit the mapping of a device to an IFS Applications object. It's also possible to navigate to the observations received for the device. IFS Applications objects that are possible to map against devices need to be IoT aware.
Create a web link that can be scheduled to initiate a call to the Novacura endpoint to read the measurements readings and to trigger the workflow.
​
Parameter Id
Description
DeviceId
Device id used for the mapping of a device to an IFS Applications object.
TestPointId
The identity of the test point of the serial object.
ParameterCode
The parameter identity that connects to the test point of the serial object. This field is connected to the Parameters table in the Test points /Parameters tab in Functional Object, Serial Object or Tool/Equipment.
Spike (optional)
Should be only used for testing.
-Set as '1' when a manual anomaly is needed to be triggered for testing.
-Default set it as 0
Example :
Use the generated web link(URL) to test the machine workflow that will run without user interaction using the Postman, which is a comprehensive set of tools that helps accelerate the API Lifecycle - from design, testing, documentation, and mocking to discovery. To test the process create a post request with the generated link and use the above-defined JSON payload.

3. View Anomaly Alert

Check the handover inbox for a new alert notification which is triggered when there is an anomaly detected from the readings of the device.
​
​
​
​

4. Review the Anomaly report

View the anomaly report which is depicted in a graph with prior measurements and has all the serial object details of the connected IoT device.
Select the required serial object node if there are any anomalies detected and create a Fault report (Work order in IFS).
​
​
​
​
​
​
​
​
​
​

5. Report a fault

This window is used to create a new work order for the detected anomaly, where the user fills in set of fields and has the option to review the prior measurements and historical works orders created against the same serial object using the below pin steps.
​
​
​
​
​
​
​
​
​
​
​
​
β€’ Enter Fault Description (Mandatory)
β€’ Enter Long Fault Description
β€’ Select Maintenance Organization (Mandatory)
β€’ Select Customer
β€’ Select Work Type
β€’ Select Work Stage
β€’ Select Priority
β€’ Select Discovery
β€’ Select Item Class
β€’ Select Fault Type
β€’ Select Attach Documents or Media Items
β€’ Press [Save] to proceed.