Preventive Maintenance

This section discusses how about preventive maintenance during Oracle Field Service and IOT integration.

These steps occur when the asset triggers an alert that will be captured to create an activity:

1. The monitored Asset triggers an alert that it needs to be serviced (for example, regular annual maintenance). The asset also stores information about the SLA (the amount of days after the alert is triggered by which the mobile worker must come).
2. The application sends the alert to Oracle Field Service via OIC.
3. The application creates a new activity with asset related information received from IoTCS. It assigns the activity to a predefined "bucket" from where it can be routed to a suitable Mobile Worker as and when required.
4. The created Activity will have the following fields populated from IoTCS:

   • Asset Name –Displays the name of the Asset as available in IoTCS

   • Asset Description–Displays the description of the Asset as available in IoTCS

   • Summary–Displays the summary of the Alert as available in IoTCS

   • Severity–Displays the priority of the Activity. For a Maintenance activity, this is set to 'Low'. For an Outage, it will be 'Critical'

   • Address–Displays the address of the Activity

   • City–Displays the city name as in the Activity address

   • Zip/Postal Code–Displays the postal code

   • State–Displays the state name as in the Activity address

   • SLA End–Displays the SLA end value calculated based on the current date and the value received from IoTCS

   • Activity Type–Specifies the Activity type. The default value is Asset Maintenance. You may modify this value if needed

   • Resource ID–Specifies the Bucket where the Activity will be created. This is set to the Bucket 'Routing' for this integration; it can be modified as per customer preference.

   • Appt Number -Specifies the external Id of the Activity

   • Customer Number –Displays the customer number as received from IoTCS