How Work Orders Are Automatically Created with Oracle IoT Asset Monitoring

When an incident is created for an imported asset in Oracle Asset Monitoring, part of the Oracle Fusion Cloud IoT Intelligent Applications, the incident can automatically translate into a maintenance work order in Oracle Maintenance. For example, if a threshold rule triggers an incident when a device associated with an asset is overheating, a maintenance work order corresponding to the incident automatically gets created in Maintenance.

To enable automatic work order creation, you must create maintenance programs that include condition event codes in Maintenance. These programs have work requirements that are defined for an asset, or group of assets, one or more condition codes, and one or more work definitions. Asset Monitoring then uses these programs to create condition-based maintenance work orders using REST Services in Maintenance. Additionally, your assets must be enabled to create work orders and operate in a maintenance-enabled organization in order to create work orders automatically.

For assets that are operating in non-maintenance organizations, you can still create work orders from IoT. However, they don't use the condition event reference and work definitions in the maintenance programs. Instead, they create new work orders with header details only, enabling you to further define their work scope on the Manage Maintenance Work Orders page. To support this capability, you must setup organizational relationships between the maintenance and non-maintenance organizations and elevate them to a primary relationship status. When the work order is created, it isn't created in the asset's operating organization, but in the primary maintenance organization.

The Maintenance Work Order REST API uses a configured action entitled createConditionBasedWorkOrders. While public, this configured action is intended to be used only by Asset Monitoring.