*
Concepts
*
Tasks
 

Setting up Failure Codes

Failure codes provide a more flexible alternative to the object parts, damage codes, and activity codes referenced on recommendations from events. Failure codes and levels are independent of each other, unlike object parts, damage codes, and activity codes, which form logical hierarchies of ownership. The Failure code type setting in the site interoperability profile determines if failure codes, object parts (and so on), or neither are available on a site.
You can define as many as five levels of failure codes and name them to match the names used in the CMMS (for example, activity type, activity cause, and activity source). APM can then be populated with instances of failure codes from the work orders, work requests, and solution packages sent from the CMMS. In APM, you can add failure codes to requests for work, failure records, and failure modes.
AWEIS conforms to the current site interoperability profile and standard behavior when adding and updating failure codes in APM. For example:
•
If a new work order arrives with failure codes from five levels but APM supports only three levels, three codes are recorded on the interop work order and a message is logged in AWEIS
•
If a new work order arrives with a failure code that does not exist in APM (and APM supports the failure code level), the code is recorded on the work order and added to APM
•
If incoming failure codes already exist in APM but with different details, the code details are not updated in APM
•
Updates to existing failure codes are subject to the Value Lists settings in the site interoperability profile. These settings control which failure code properties can be updated and which actions performed by AWEIS
Note: To use failure codes in APM, you must first enable feature 46. In the Enterprise window, select the Features view and the Enabled Features tab. Click Browse, select “Failure codes support with AssetWise Interoperability”, and click OK. If APM is running as a smart client, click Refresh Enabled Features. Then restart the client to use the functionality.
This topic explains setup tasks in APM. For information about the required setup tasks in AWEIS, see “Setting up APM Failure Codes” in AssetWise Interoperability Setup Guide.
This topic explains:
•
Setting up APM to use Failure Codes
•
Viewing Failure Codes and Events

Setting up APM to use Failure Codes

Setting up failure codes involves the following steps:
•
In the Site Interoperability Profile window, select the Work Management and Failure Coding tabs. In the Failure code type options, select Failure codes. The tab changes as follows:
The default number of failure code levels is three. You can select a different number (up to five). Provide a descriptive name for each level. For example:
For more information, see Setting up Site Interoperability Profiles for AWEIS.
•
AWEIS can then import failure code values into APM from the CMMS. When a failure code value is added or updated in the CMMS or when a work document is sent from the CMMS, failure code values in APM are updated.
Tip: To view the codes, open the Site window, select the Work Management view, Settings, and Failure Codes tabs. You will see one tab for each of the levels you added in the site profile. For example:
•
Once codes have been defined at the next level, you can edit a higher-level code to specify which codes from the next lower level are allowed to be selected in a request for work, for example. In this example of a first-level code, the second-level codes are available for selection:
•
You can set up your work types to specify whether a failure code is mandatory on a request for work. In the Work Type and Site Settings dialog, select the Requests or Trigger Requests tab and then the Mandatory Properties tab. Select the failure code levels that are mandatory. For example:
Similarly, you can specify that failure codes are read-only in APM.
•
On individual instances of failure codes, you can set options for generating checksheets for recommendations from events where the failure code is referenced. For more information, see Generating Checksheets for Interop Work Documents.
For more information, see Setting up Site-Specific Work Types.

Viewing Failure Codes and Events

You can view and use failure codes or events in the following locations.

Requests for Work

Request for Work windows display either events or failure codes:
•
When recommendations from events are supported, the Events tab is available, where you can add events and select part groups, parts, damage codes, and activity codes. Here is an example from a request for work created from scratch:
•
When failure codes are supported, the Failure Codes tab is available, where you can select failure code values and add a description. Here is an example from a request for work created from scratch:
Similar changes have been made to Acknowledge Indicator Alarm windows when the acknowledgment method is Request for Work, as well as in other windows where you can create requests.

Interop Work Requests and Interop Work Orders

The Interop Work Request and Interop Work Order windows, Properties view, contain tabs labeled either Event or Failure Codes, depending on the Failure code type setting in the site’s interoperability profile.

Maintenance Action Plans

When you are developing failure modes on a strategy development analysis (MTA2, RCM2, or RBI), you can add failure data and patterns in the Maintenance Action Plan window, Failure Information view. The third tab in this view is labeled either Events or Failure Codes, depending on the Failure code type setting in the site’s interoperability profile.
On the Failure Codes tab, you can select codes and add a failure description. For example:

Failure Records

In the Failure or Anomaly window, the Properties view contains a tab labeled either Events or Failure Codes, depending on the Failure code type setting in the site’s interoperability profile.
When you reference a failure mode on the General tab, the failure mode’s failure codes and description are copied to the Failure Codes tab. You can also select codes and add a failure description. For example:

Solution Packages

Solution packages support failure codes, if specified by the Failure code type setting in the site’s interoperability profile. You can select failure codes and provide a default description on solution package templates. When a solution package is referenced in a request for work or other work document, the failure codes are copied from the solution package. Note that if the work document already has one or more failure codes, those codes are not replaced by values from the solution package.