Associate Work Order Operation to a Failure Instance

Capturing asset failures, causes, and resolutions helps organizations measure and analyze asset reliability and availability, which also helps assess maintenance effectiveness and efficiency. As part of the manage maintenance work order and the maintenance dispatch list, you can create a failure event and report a failure instance that records the failure code, cause code, resolution code, and the failed component and asset number.

In this update, you can now identify the work order operation using the new field Operation Sequence when creating a new failure instance.

New Failure Instance with Operation Sequence Selection Drop Down

Associating a specific failure instance with a work order operation  makes it easier to understand what repair was done for each reported failure.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

It's necessary to have the following setup before attempting a failure capture for a work order asset:

• Defining valid failure, cause, and resolution codes
• Defining a default failure set

Key Resources

• Check out the What's New content of the Capture Failure Information of Work Order Asset feature
• Check out the What's New content of the Track Asset Failure using REST API feature
• Note a new Optional attribute Op Seq was added to the Failure Instance REST

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Manage Failure Events for Work Order Asset (MNT_MANAGE_FAILURE_EVENT_WO_ASSET_PRIV)
• Manage Maintenance Work Orders (MNT_MANAGE_MAINTENANCE_WORK_ORDER_HEADERS_PRIV)
• Manage Maintenance Work Order Operations (MNT_MANAGE_MAINTENANCE_WORK_ORDER_OPERATIONS_PRIV)
• Review Maintenance Dispatch List (MNT_REVIEW_MAINTENANCE_DISPATCH_LIST_PRIV)
• Manage Maintenance Management Work Area (MNT_MANAGE_MAINTENANCE_MANAGEMENT_WORK_AREA_PRIV)

These privileges were available prior to this update.