Mandate Failure Codes in Work Orders

Reporting failure/action/cause codes in corrective maintenance (CM) work orders allows tracking and analysis of failures and resolutions. The codes are not required in preventive maintenance (PM) work orders.

There are two ways to mandate failure/action/cause in CM work orders. You may choose to use option 1 only, or use it with option 2 to manage how failures are reported by your maintenance staff based on circumstances of your assets/locations.

  • ​When option 2 is enabled, option 1 can overwrite option 2 for specific asset/location groups.

Option 1. Require Failure/Action/Cause by Asset Groups

Edit an asset group (Menu path: Asset Module | Codes | Asset Groups) and set "Required in WO" to true. You can do the same for a location group (Menu path: Asset Module | Codes | Location Groups).

In this option, you can optionally set a failure set to allow for only selective failure/action/cause codes to be available for an asset or location group. 

Failure sets can be managed at Failure Module (Menu path: Failure Module | Failure Sets).

Option 2. Require Failure/Action/Cause for All CM Work Orders

Option 2 makes it mandatory to enter failure/cause/action codes for all CM work orders unless overwritten by Option 1. This is done through a system configuration. Email Calem Support to enable this configuration for your cloud service. If you are using an on-premise Calem service, see "14.38.1 Mandatory Failure Codes" of Admin Guide at Calem Support Site (a customer account is required to download manuals from the support site).

When completing a CM work order, the failure/action/cause codes will be mandated based on the configuration above.

Session Logs and Site Monitoring
Data Upload Part 3: Preventive Maintenance