Concepts

Tasks

Settings

Performing Risk Assessment on a Request for Work

When AssetWise Enterprise Interoperability (AWEIS) is active for the site and has been configured to integrate with an external Anomaly Assessment and Tracking (AA&T) system, you can perform risk assessments for requests for work.

Note: Support for anomaly assessment is generally available. However, you must first enable feature 108 to use the functionality in APM. In the Enterprise window, select the Features view and the Enabled Features tab. Click Browse, select “Anomaly risk assessment” and click OK. If APM is running as a smart client, click Refresh Enabled Features on the server. Then restart the client to use the functionality.

Note: The request for work’s work type site settings must require that risk be assessed for the request. For related information about setting up anomaly risk assessment, see Setting up Site-Specific Work Types.

The risk assessment process consists of the following steps:

1.	The request for work is created.

2.	Once the request has been approved (if required), you can perform the risk assessment:

•	Evaluate the consequences of failure, including the severity of economic, health and safety, environmental, and reputation consequences

•	Evaluate the probability of failure

APM calculates the sum of the consequences and uses the probability score to arrive at the criticality score. The criticality determines the risk assessment result, which, in turn, determines:

•	Whether or not the anomaly is actionable

•	Which acknowledgment methods are available

•	Whether an anomaly event is created

3.	If the assessment result specifies it, an anomaly event is created. The request’s interop status might change to “Anomaly event created”. If the result is not actionable, the request for work is “Held in APM”.

Note: Once a request for work is approved and an anomaly event created, the request cannot be redrafted.

4.	The anomaly event is published. The event is processed by the middleware and sent to the AA&T system.

5.	The AA&T system creates the anomaly and notification (if the CMMS is SAP Plant Maintenance), sends the notification to the CMMS, and sends messages to APM to update the anomaly event and request for work. The AA&T system continues to track the anomaly and communicate changes to APM.

This topic explains components of risk assessment as well as how to perform risk assessment. It explains:

•	Risk Assessment

It explains how:

•	To Perform a Risk Assessment for a Request for Work

Risk Assessment

To perform risk assessment, the severity of the consequences of failure must be determined. Consequences are categorized:

•	Economic effects – Financial effect of failure on assets and production. Labor and material costs associated with lost production and with repairing or replacing the damaged equipment are economic consequences

•	Health and safety effects – Equipment failure can cause hazards in the workplace. Examples are extreme temperatures or pressure or noxious fumes

•	Environmental effects – Environmental incidents are an important category to consider when determining overall consequence. Typically, two types of environmental incidents are considered:

•	Release of liquids that may cause soil and water pollution

•	Release of gases that may cause atmospheric pollution

•	Reputation effects – Consequences to reputation measure the impact that negative media attention has on an organization’s ability to operate in good faith. Typically, the severity of bad press is evaluated in terms of how far-reaching it is and how long it takes to mitigate

Each of these consequence categories is assigned a value. The sum of the values in all categories is used in the calculation of the consequence assessment.

For more information, see Overview of Risk Analysis.

To Perform a Risk Assessment for a Request for Work

1.	In the Site window, select the Work Management view and the Requests for Work tab.

2.	Right-click the request and click Assess Risk. The Anomaly Risk Assessment dialog appears. For example:

On the Risk Assessment tab, the Asset identification area shows the following:

•	Anomaly asset – The asset on which the indicator reading was recorded

•	Asset – The interop asset. Its counterpart in the CMMS is updated with information about the anomaly event. If the anomaly asset is an APM-only asset, APM searches up the asset hierarchy to find the nearest interop asset and displays it here

•	Safety critical equipment – Indicates if the asset’s use involves risk (there is a potential that a mishap could occur, with severe consequences). If this property was set on the anomaly asset, the value is displayed

3.	For each of the consequences, either select a value from the list or click to use the evaluation questionnaire. APM calculates and displays the result in the Consequences box.

For an example of using evaluation questionnaires, see Performing Risk Analysis for RBI Failure Modes.

4.	Evaluate the probability of failure by either selecting a value from the list or using the questionnaire. APM determines the criticality score and the risk assessment result. For example:

Note: The criticality value is highlighted with a color chosen by your organization. In this example, the value “High” is highlighted with red ().

Note: If the default risk assessment result can be overridden, a button is available to toggle between actionable and non-actionable:

5.	Add more information in the Recommendations or Anomaly comment boxes.

6.	Select the Anomaly Details tab:

7.	Provide additional information:

Setting Name

Description

Anomaly type

Failure or anomaly types, along with classifications, allow anomaly events and failure records to be grouped for easy identification. Useful types might be Electrical, Environmental, Mechanical, Operational, Safety, and so on. Examples of classifications are Lubrication, Operator Error, and Installation Defect.

Anomaly classification

Failure or anomaly classifications, along with types, allow anomaly events and failure records to be grouped for easy identification. Examples of classifications are Lubrication, Operator Error, and Installation Defect.

Anomaly severity

Indicates the seriousness of the problem. Three severity types are supported: • Potential: a condition that has been noticed that would result in an actual failure if the problem is not resolved. The actual failure has not yet occurred. Potential failures are normally reported as the result of an indicator reading that has raised a warning alarm against the asset. • Partial: the asset’s performance has decreased to a point where it is no longer performing one of its functions at the specified levels. The asset is still functioning. • Total: the asset’s performance has decreased to a point where the asset is no longer performing at its required level. The asset has completely failed. You can create severities as required for your organization.

Asset risk category

Asset risk categories are defined in Oil and Gas specifications.

Anomaly owner

APM employee associated with the anomaly.

Fitness for service date

Expected date on which the asset will be assessed for fitness for service.

Comment

Additional information about fitness for service.

Part	“Part” is an example of a failure code name. Your organization decides on the number, names, and values for failure codes.

Damage code

Damage codes provide predefined categories to describe asset damage. For example, ARLK for Air Leak. Damage code can be optional when you are adding an event to a request for work. However, if a damage code and activity code are not selected, the event will not have a work priority.

Action

“Action” is an example of a failure code name. Your organization decides on the number, names, and values for failure codes.

8.	Select the Anomaly Description tab to add more information.

The Request Details tab displays information from the source request for work.

9.	Select the Failure tab, where you can create or link to a failure.

10.	Click OK. The dialog closes and the Requests for Work tab displays updated information.

If the request for work’s assessment is actionable, its Interop status typically changes to “Anomaly event created”. If the result is not actionable, its status changes to “Held in APM”.