Concepts

Tasks

Settings

Overview of Work Management with AWEIS

Your AWEIS implementation is set up to exchange work documents and information between APM and your external CMMS. Examples in this topic use SAP Plant Maintenance as the external CMMS.

The CMMS manages corrective work, sending interop work requests, interop work orders, and solution packages to APM for information purposes – and to generate the checksheets to be completed in APM, which is the inspection management system. With some exceptions, information on interop work documents is read-only in APM.

APM manages inspection activities, strategy development, and performance tracking. These activities result in requests for work to be performed in the CMMS.

APM can be configured to integrate with an external Anomaly Assessment and Tracking (AA&T) system. With the help of AWEIS and other middleware, anomaly events are sent to the AA&T system, which then becomes the master system for the anomaly events. Information, including event statuses, is sent to the anomaly event in APM to keep the two systems synchronized.

When the integration has been set up, you can perform risk assessment when acknowledging indicator alarms or creating requests for work. The resulting criticality is added to the new anomaly event and used to determine if the anomaly is actionable. Actionable events are sent to the AA&T system for the creation of notifications, which are then sent on to the CMMS (SAP) to generate maintenance orders.

For more information, see Anomaly Risk Assessment and Integration.

This topic explains the work documents and their work flow. It covers:

•	Request for Work and Interop Work Requests

•	Interop Work Orders

•	Solution Packages

•	Standard Tasks

•	Failure Tracking

Request for Work and Interop Work Requests

Requests for work can be created in APM in several ways. For example, they can be created manually to acknowledge indicator alarms or request follow-up work. They can also be generated automatically in response to indicator state changes, work document status changes, or solution package due date changes. Requests can define recommendations from events or reference preplanned tasks in the form of solution packages.

When you submit a request, AWEIS processes the message and sends the request to the CMMS. It returns an acknowledgment that either accepts or rejects the request.

•	If the request is accepted, an interop work request or interop work order is added to APM with a link to the original request for work. In the CMMS, a SAP notification or maintenance order is created or updated

•	If the request for work is rejected, a reason is returned to APM, and the request for work’s interop status is set to “Rejected by system of record”. If appropriate, you can then revise the request and resubmit it

New SAP notifications and changes are sent from the CMMS to APM, where corresponding interop work requests are created or updated.

Interop Work Orders

When the external CMMS is SAP, maintenance orders that are created and updated in SAP can be sent to APM, where simple interop work orders are created and managed. When a work order is sent from SAP that references a solution package and cycle, the linked standard tasks are used to generate a set of inspection checksheets on the interop work order.

APM can be set up to generate links between checksheets and the interop work requests referenced in work orders. See Linking Checksheets and Interop Work Requests.

Reset Solution Package Evaluation Status

On occasion, it is necessary to evaluate interop work orders by regenerating their checksheets. For example, when additional standard tasks are added to a solution package, you might wish to reset the solution package’s evaluation status in order to generate checksheets for the new tasks.

Open the Interop work order dialog, click the Tools menu, and then Reset Solution Package Evaluation Status. The next time that the Create Work Order Checksheets function is executed for the site (Tools menu, Inspection Management, Create Work Order Checksheets), checksheets are created for only the new standard tasks in the solution package.

Solution Packages

In this interoperability example, maintenance plan information is sent from SAP to APM in the form of solution packages that represent preplanned work. The solution package includes information such as solution package level, job number, description, priority, work type, work classification, and maintenance group.

This mechanism allows for a loose coupling between the SAP maintenance plan and the APM solution package. The schedule and work cycles are controlled in SAP, but the details of the corresponding inspections are maintained in APM and linked through the solution package.

SAP is the master system for solution packages and will send updates when there is a change to the mapped data in the maintenance plan.

In APM, an administrator creates solution package templates and links them and cycles to standard tasks in the asset program profiles that APM uses to generate activities such as inspection tasks for a construction form. Solution package templates can then be referenced on the solution packages sent from the CMMS.

Solution package templates can also be referenced on requests for work created in APM, for example, in response to indicator alarms or for follow-up work. Solution package information can be included on standard tasks to be copied to the requests for work that are created from the checksheets generated from the standard task. In SAP, the request for work can trigger the maintenance plan that creates corrective tasks.

For each site, you can set up as many as four solution package levels, naming the levels with terms specific to your CMMS or organization. For example, the levels could be named Maintenance plan, Maintenance item, and Operation or Plan, Task, and Subtask.

A message sent to APM from the CMMS indicates the preplanned work’s level. In APM, the level is matched to the solution package type’s level (1 to 4). The solution package type identifies the kind of object, for example, maintenance plan. The site interoperability profile determines the behavior, for example, the level that supports cycles or steps.

Standard Tasks

Standard tasks are used for generating checksheets, rather than for identifying corrective work.

Failure Tracking

When AWEIS is active for a site, failure records can be created or updated based on the events referenced on requests for work, interop work requests, and interop work orders.

For example, when the CMMS sends a work order to APM, a failure record might be created at the same time, based on the work order’s highest priority event. The appropriate properties are copied to the failure record from the work document, for example, asset, date occurred, and either failure codes or object part, damage code, and activity code. The source work document is referenced on the failure record, and the failure is referenced on the source event.

The site interoperability profile specifies whether failures can be created for new interop work requests, interop work orders, or both.

These settings control the following:

•	Whether failures are created from interop work requests, interop work orders, or both

Note: The setting in the site profile overrides similar settings on individual damage codes.

•

How APM attempts to match a prospective failure record to existing ones when object parts, damage codes, and activity codes are used at the site. When a new interop work document arrives, APM checks if it is associated with a request for work and looks for a match between the events defined in the interop work document and the request. If a match is found, the request’s existing failure is updated. If a match is not found, a new failure record is added. Events can be matched based on one of the following:

•	Same object part code

•	Same object part and damage code

•	Same object part, damage code, and activity code

Failure statistics are calculated for failure codes, object parts, damage codes, and activity codes. Each statistic record includes time between failures, time to repair, and restoration time.