featured image 1 900x502 1

Bridging PLM-EAM Gaps

In many cases, when the maintenance activity is being performed, the technician uses the set of tools & replacement parts defined by the manufacturer as part of the product service plan. This is normally contained in a Product Lifecycle Management (PLM) system.

In reality, this information could be out of synchronization in the Enterprise Asset Management (EAM) system. For example, the original part could have been replaced in the past, which might require a different set of tools and spare parts. The technician comes to know about it only after a visit. Re-visit is required with the correct set of tools, spares, or even skills to properly perform the job. This inadvertently increases the downtime of the asset. What could be the root cause of the lack of the latest information? This is a result of the gap between PLM & EAM systems. This gap can be minimized with an integrated digital thread solution.

Bridging PLM-EAM Gaps
Bridging PLM-EAM Gaps

Siemens Teamcenter Service Lifecycle Management (SLM) has a Design & Service Engineering solution to support service plan definition, including service requirements, frequencies, activities, technical publications, etc. On the other hand, a typical EAM system would have service operations such as work order management, scheduling, costing, dispatching, etc. Conveying updated information on Service Plans & sBOMs is a major concern in connecting PLM to EAM systems. The EAM systems which perform service operations may have missing important updates available from PLM systems. This could bring down the effectiveness of the asset’s maintenance.

sBOM & Service Plan in Teamcenter SLM

02 1024x454 1
Details of sBom & Service Plan defined in Teamcenter SLM.

The above image shows sBOM with occurrence-specific details. The service plan will have information about how the product needs to be serviced. It contains information about frequency, work cards, time & activity details.

Imported data from Teamcenter SLM to IBM Maximo

The IBM Maximo user can pull the latest & configured sBOM & Service Plan information from Teamcenter SLM. The resulting data in IBM Maximo can be seen below images.

03 1 1024x475 1

The Assets, Items, Spares are created in IBM Maximo by referring to Teamcenter sBOM.

04 1024x585 1
Bridging PLM-EAM Gaps 8

The Job Plans & Job Plan Tasks are created in IBM Maximo by referring Work Cards & Activities from Teamcenter.

Work Order History Gap:

Another gap that can be addressed through an integrated digital thread solution is the lack of performance visibility. The part movements, usage, fault codes & failures would be captured after execution of Work Orders in IBM Maximo. This information will be transferred to Teamcenter As-Maintained structures. This information from the field can be useful input for the designer to perform design improvement analysis. Such workflow of getting feedback from real assets closes the loop between PLM & EAM systems. It is done by leveraging the Digital Thread of assets from design to service engineering, from service engineering to service operations, and vice versa.
For a given asset, the Work Order history is created in IBM Maximo in a standard way, as shown below image.

05 1

Import of Work Order History from Maximo to Teamcenter SLM:

For a given sBOM in Teamcenter SLM, the Designer/Service Engineer can pull the Work Order history of the associated assets from IBM Maximo, as shown below images. This Work Order history provides vital information of fielded assets to the designer, which improves the design.


This image shows Active Workspace (AW), which is the web version of Teamcenter. Teamcenter Service Engineer can pull the Work Order history from IBM Maximo by providing date range & associated Fault Code in AW.


The above solution is an attempt to minimize the gap between PLM & EAM systems and to close the loop of Design, Manufacturing, and Service Operations to improve the quality of the product based on the feedback of failures, reduce commissioning time, avoid repeating technician visits and increase asset’s availability.

Disclaimer: I am the author at PLM ECOSYSTEM, focusing on developing digital-thread platforms with capabilities across CAD, CAM, CAE, PLM, ERP, and IT systems to manage the product data lifecycle and connect various industry networks. My opinions may be biased. Articles and thoughts on PLMES represent solely the author's views and not necessarily those of the company. Reviews and mentions do not imply endorsement or recommendations for purchase.

Leave a Comment

Your email address will not be published. Required fields are marked *