Use Operational Rules to Automatically Create Maintenance Work Orders

You can leverage condition events from connected assets to automatically generate condition-based maintenance work orders. When a connected asset fails or produces an error, you no longer need to manually create a maintenance work order.

Condition-based alerts using machine events include the following:

• Event Ingestion: Connected assets can send fault events. These events contain the asset number, the time of the event, the fault type, and the fault code. You can configure fault codes in Maintenance as condition codes. Condition codes can be created for failure and diagnosis.
• Evaluation Criteria: Use operational rules to evaluate incoming fault events. When you configure an operational rule, it applies to all connected assets, so that any incoming event from a connected asset is evaluated against all configured operational rules.
• Outcome: The outcome for an operational rule describes the actions that are executed when the evaluation criteria is met. If the fault code has been configured as a failure condition code, then the created work order contains a failure event. If the fault code has been configured as a diagnostic condition code, then the created work order uses the maintenance program corresponding to the diagnostic condition code.

To automatically create Maintenance work orders:

• Ensure that operational rules have been set up for equipment fault codes to capture and evaluate events from connected assets.
• Use maintenance programs that include fault event codes for which condition codes are set up in Maintenance. The maintenance programs can have work requirements defined for an asset or group of assets, can use one or more condition codes, and contain one or more work definitions.