Concepts

Tasks

Settings

Overview of Setting up APM for AWEIS

Before you can exchange data pertaining to inspection management, work management, strategy development, and performance tracking with the external CMMS, you must configure settings and value lists for your organization. This topic explains the types of options that are available and provides links to detailed information.

For information about using AWEIS with APM construction management functionality, see Setting up APM for Construction Management.

For information about using APM with AWEIS for anomaly assessment and tracking, see Setting up APM for Anomaly Risk Assessment and Integration.

Create AssetWise Interoperability Systems

APM and AWEIS support the integration of two or more instances of a CMMS (such as SAP Plant Maintenance) with sites in a single APM database. For example, a facility, factory, or plant in SAP could exchange data with its corresponding site in APM.

Note: Even if you decide to integrate a single CMMS with the top site in APM, you must create an AssetWise Interoperability system to reference the CMMS and APM site.

When you create the Interoperability system, APM generates an InfoSource UUID for it. The InfoSource UUID is used in interop messages to manage data that is owned by the CMMS.

To support the integration of multiple sites, you can maintain site-specific value lists in APM, along with site type settings that control which sites own employees and trade resources.

For more information, see:

•	Setting up AssetWise Interoperability Systems

•	Setting up Site Integration Between APM and CMMS Instances

•	Setting up Site Value Lists

Set up Site Profiles and Activate Sites

Site interoperability profiles that you define at the enterprise level make it easier to manage the availability of CMMS data at the site level. You can assign a profile in the site’s AssetWise interoperability settings.

For more information, see Setting up Site Interoperability Profiles for AWEIS.

For each site to be integrated, including parent sites, activate interoperability and assign a Site Interoperability profile.

For more information, see Activating AssetWise Enterprise Interoperability in APM.

Note: The Work Management Integration module must be selected in Site Properties so that the site can use interoperability. For more information, see Enabling and Disabling Application Modules on Sites.

Prepare APM Data for Interoperability

You can make your APM data “Interop ready,” that is, enabled for synchronization with external systems. You will need to do this whether you have already populated the APM database with assets and inspections or you are starting with an install database.

Use Interoperability Data Readiness requests to identify the rules and parameters for updating all or a subset of a class’ instances (for example, all asset types or a selected list of asset types). This includes options to exclude APM-only assets from being activated. You can process requests manually or set up the Process Interop Data Readiness Requests scheduled action to run at regular intervals.

For more information, see Preparing APM Data for Interoperability.

Set up Characteristic Map Sets

The Characteristics feature makes it possible to import object attributes from the CMMS and to map the characteristic values to the properties of APM objects. AWEIS can create characteristics as needed when adding interop assets, work requests, work orders, and solution packages to APM. Characteristic map sets are used to update the corresponding properties of APM assets and interop work documents.

Outgoing asset change requests and requests for work can include characteristic values that are sent to the CMMS. When APM creates a request for work, for example, it refers to the appropriate characteristic map set to export information from the request that can then update characteristics in the corresponding object in the CMMS.

Setting up characteristic functionality involves:

•	At the enterprise level, setting characteristic mapping defaults to allow AWEIS to create new characteristic instances and to set the date format. The values are defaulted on the Characteristic Mapping dialog, where they can be changed. See Setting Defaults for Characteristic Mapping

•	Setting up asset characteristic mapping. See Setting up Characteristic Mapping for Assets

•	Setting up characteristic mapping for asset change requests. See Setting up Characteristic Mapping for Asset Change Requests

•	Setting up characteristic mapping for interop work documents. See Setting up Characteristic Mapping for Interop Work Documents

Identify Asset Types for AWEIS

Create or adjust asset types to reflect their roles. For example, you can specify whether assets represent assets or segments in the CMMS. And you can associate asset types with a characteristic class and mapping set.

For more information, see **Setting up Asset Types.

Set up Asset Change Requests

Change requests specify updates to be performed on assets in the external CMMS (for example, SAP) that manages assets and work. AssetWise Enterprise Interoperability (AWEIS) conveys requests to the CMMS and returns information to APM. The asset update is performed in the CMMS and then information such as a new equipment number is communicated back to APM, where the interop asset is updated.

Setting up APM for asset change requests involves the following tasks:

•	If appropriate, create or update asset types. For example, if you are implementing the new electricity transmission and distribution network assets, you might create asset types for network switch, junction, primary chamber, protector, and transformer. To support change requests, be sure to:

•	Set asset management policies such as support for change requests and the default change request template. You might also support networks vault location information

•	Assign the appropriate specification panel to the asset type. The panel will be available in the Asset window and in asset change requests

•	Select the appropriate characteristic class and map set for the asset type. These are used to import characteristics from the CMMS and map them to asset properties in APM

See **Setting up Asset Types

•	Create one or more asset change request types for asset property changes. You can assign a default request status, characteristic map set, and more, as well as specify whether the review or approval process is required

See Setting up Asset Change Request Types

•	Set up characteristic mapping for asset property change requests

See Setting up Characteristic Mapping for Asset Change Requests

•	Create an asset change request template for each of the asset types that typically warrant change requests. The template controls the content and behavior of the request based on asset type. In asset types, you can specify default templates

See Setting up Asset Change Request Templates

•	If you will be using the APM approval process for requests, select the site’s approval settings and set up approval routes and approvers

See Approvals Settings

Set up Solution Package Templates

If the work document system is Interop (you are using AWEIS), preplanned work comes from the external system in the form of solution packages (which cannot be created in APM). You can create solution package templates in APM and then, in the asset program profile detail, link standard task templates to those solution package templates. For each standard task template in a detail, you can specify up to five solution package templates, along with cycles and asset preferences.

See Setting up Solution Package Templates.

Set up APM Outbound Events

When certain APM objects are created, updated, or deleted, events can be produced (serialized) and published to an external system using AWEIS.

Configuring this functionality involves the following steps:

•	Enable outbound events in the site interoperability profile

•	Configure the server\service instance

•	Create an APM Outbound Event service provider

•	Set Interop Event Handler options

See Setting up APM Outbound Events.

Define Work Management Settings

Set up Site-Specific Work Types

You can configure work type settings that are tailored to the sites where the work types are used. Site-specific settings are provided for these situations:

•	Ready to send options – Determine when requests for work must be manually marked as ready to send

•	Requests for work without solution packages – Determine which properties are mandatory and which are read-only

•	Requests for work that trigger solution packages – Determine which properties are mandatory and which are read-only

For more information, see Setting up Site-Specific Work Types.

Set up Default Work Types

Requests for work can be created in several ways. For example, you can create them from scratch in the site’s Work Management view, from an indicator alarm acknowledgment, when defining follow-up work from a failure record, maintenance action plan, or safety override incident, or when reviewing a reliability program. You can set the site’s default work types for a variety of uses from one central location.

For more information, see Setting Default Work Types.

Set up Work Statuses

The work statuses on interop work orders and requests for work can be used to control checksheet generation on work orders and to update checksheet statuses. The work status indicates whether the document is open, closed, or canceled.

For more information, see Setting up Work Statuses.

Set up Secondary Status Codes and Groups

Secondary status codes are recorded on requests for work and interop work requests. Typically, status codes are added to APM when new work requests arrive from the CMMS. However, you can also create secondary status codes in Work Management settings and specify the sites and groups with which they can be used.

You can also create status groups to organize status codes and to specify how codes are used.

For more information, see Setting up Secondary Status Codes and Groups.

Set 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.

For more information, see Setting up Failure Codes.

Set up Follow-up Work Creation Settings

When the status of an interop work request or interop work order changes in the CMMS, the change is communicated to APM with an interop message. The status is then updated on the APM interop work document. The status change can trigger logic to determine if a follow-up request for work is needed.

For more information, see Setting up Follow-up Work Creation Settings.

Set up APM for Work Document Change Requests

Setting up APM for work document change requests involves the following tasks:

•

Set up change request types, which determine whether requests can be created for work requests, work orders, or both. Types also specify whether requests must be associated with users designated as maintenance or construction supervisors, which properties are mandatory or optional on requests, which work statuses are available, and whether the request must be sent for approval

See Setting up Work Document Change Request Types

•	Create change request statuses for the site. The status indicates the request’s progress in the workflow, for example, “New request”, “Ready to send to interop”, or “Complete”. It also determines rules for the request, for example, whether properties can be updated

See Setting up Work Document Change Request Statuses

•	Set up change request creation settings. Checksheet status can determine whether a change request for the associated interop work request or interop work order needs to be sent to the CMMS

See Defining Change Request Creation Settings

•	If you will be using the APM approval process for requests, select the site’s approval settings and set up approval routes and approvers

See Approvals Settings

Set up Object Parts and Related Codes

You can set up object part groups, object parts, damage codes, and activity codes. When creating a request for work, you can add one or more events that identify the problem the requested work is meant to correct.

See Setting up Object Parts, Groups, and Related Codes.

Set up Task Type Types and Groups

You can set up task types to represent the work steps to be performed, as explained in requests for work.

See Setting up Task Types and Groups.

Add Default Number of Personnel to Trades

You can set the default number of personnel that will automatically be added to labor requirements on requests for work, interop work requests, and interop work orders. The default makes it easier to calculate the total required time on work documents, especially if the trade resources in your CMMS do not specify a quantity.

For more information, see Adding a New Trade.