Construction Management and AWEIS

Bentley AssetWise Enterprise Interoperability Service (AWEIS) connects applications in a loosely coupled, services-oriented architecture. Bentley offers it as part of its cloud-based CONNECT services platform, providing Interoperability as a Service (IaaS) to facilitate exchanges between Bentley software products and between Bentley and third-party software solutions. Bentley’s interoperability offering addresses the needs of modern software deployment architectures, supporting cloud-hosted, standalone, and/or hybrid topologies.
When APM has been configured to work with AWEIS to exchange data with your CMMS, the CMMS is the master system where assets, work documents, employees, and maintenance groups are maintained. APM is the system for inspection management, strategy development, and performance tracking. This overview uses examples from SAP Plant Maintenance as the external CMMS.

Integration Points

The following diagram shows integration points between APM and SAP Plant Maintenance.

Synchronize Asset Data

During the implementation project, CMMS assets (for example, SAP equipment and functional locations) are imported as new assets into APM. In addition, the characteristics feature makes it possible to import asset characteristics from the CMMS and to map characteristic values to APM asset properties. Interoperability processes communicate information about new and updated CMMS assets to APM, ensuring that asset information remains synchronized.
Construction forms add new APM assets that have been purchased and delivered to the job site for installation. They also record existing assets to be installed at the location. New, updated, and removed assets are communicated to the CMMS using asset change requests. The data includes asset characteristics (specifications), hierarchy information, and asset statuses for the corresponding CMMS equipment.
When information about new or updated assets is sent to the CMMS, the CMMS asset record is created or modified. Information such as the equipment number is sent back and recorded on the asset in APM.

Requests for Work, Notifications, and Interop Work Requests

Requests for work are created in APM, for example, through alarm acknowledgments, and sent to the CMMS for the creation of notifications and maintenance orders (in the case of SAP). The request can reference CMMS preplanned work (such as a solution package) to modify the next date on the corresponding maintenance plan.
New notifications and changes are sent from the CMMS to APM, where corresponding interop work requests are created or updated.

SAP Maintenance Orders and Interop Work Orders

In this interoperability example, maintenance orders that are created and updated in SAP are 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 create a set of inspection checksheets on the work order.

SAP Maintenance Plans and 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 job number, description, priority, work type, work classification, and maintenance group.
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 inspection activities for a construction form.
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 are linked through the solution package.
SAP is the master system for solution packages and will send updates any time that there is a change to the mapped data in the maintenance plan.