{"id":61,"date":"2021-04-05T05:37:26","date_gmt":"2021-04-05T09:37:26","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/?p=61"},"modified":"2026-03-26T15:41:58","modified_gmt":"2026-03-26T19:41:58","slug":"bridging-plm-eam-gaps","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/2021\/04\/05\/bridging-plm-eam-gaps\/","title":{"rendered":"Bridging PLM-EAM Gaps"},"content":{"rendered":"\n

In many cases when maintenance activity is being performed, the technician makes use of the set of tools & replacement parts which are defined by the manufacturer as part of 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, original part could have been replaced in the past which might require a different set of tools and spare parts. 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 down time of the asset. What could be the root cause of lack of latest information? This is a result of the gap between PLM & EAM systems. This gap can be minimized with an integrated digital thread solution.<\/p>\n\n\n\n

\"SLM<\/figure>\n\n\n\n

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 other hand, a typical EAM system would have service operations such as work order management, scheduling, costing, dispatching etc. Conveying updated information of Service Plans & sBOMs is major concern in connecting PLM to EAM systems. The EAM systems which performs service operations may have missing important updates available from PLM systems. This could bring down the effectiveness of the asset\u2019s maintenance.<\/p>\n\n\n\n

sBOM & Service Plan in Teamcenter SLM<\/strong><\/p>\n\n\n\n

\"Details
Details of sBom & Service Plan defined in Teamcenter SLM<\/figcaption><\/figure><\/div>\n\n\n\n

Above image shows sBOM with occurrence specific details. Service Plan will have information about how the product needs to be serviced. It contains information about frequency, work cards, time & activity details.<\/p>\n\n\n\n

Imported data from Teamcenter SLM to IBM Maximo<\/strong><\/p>\n\n\n\n

The IBM Maximo user can pull latest & configured sBOM & Service Plan information from Teamcenter SLM. The resulting data in IBM Maximo can be seen in below images.<\/p>\n\n\n\n

\"Teamcenter<\/figure><\/div>\n\n\n\n

The Assets, Items, Spares are created in IBM Maximo by referring Teamcenter sBOM.<\/p>\n\n\n\n

\"IBM<\/figure>\n\n\n\n

The Job Plans & Job Plan Tasks are created in IBM Maximo by referring Work Cards & Activities from Teamcenter.<\/p>\n\n\n\n

Work Order History Gap:<\/strong><\/p>\n\n\n\n

Another gap that can be addressed through an integrated digital thread solution is lack of visibility of performance. 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 in below image.<\/p>\n\n\n\n

\"SLM<\/figure><\/div>\n\n\n\n

Import of Work Order History from Maximo to Teamcenter SLM:<\/strong><\/p>\n\n\n\n

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

\"Fielded<\/figure><\/div>\n\n\n\n

This image shows Active Workspace (AW) which is 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.<\/p>\n\n\n\n

Summary:<\/strong><\/p>\n\n\n\n

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 in order to improve quality of product based on feedback of failures, reduce commissioning time, avoid repeating technician visits and increase asset\u2019s availability. <\/p>\n","protected":false},"excerpt":{"rendered":"

In many cases when maintenance activity is being performed, the technician makes use of the set of tools & replacement…<\/p>\n","protected":false},"author":76732,"featured_media":71,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[337],"class_list":["post-61","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/40\/2021\/04\/featured-image-1.png","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/posts\/61","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/users\/76732"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/comments?post=61"}],"version-history":[{"count":5,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/posts\/61\/revisions"}],"predecessor-version":[{"id":81,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/posts\/61\/revisions\/81"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/media\/71"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/media?parent=61"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/categories?post=61"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/tags?post=61"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/industry?post=61"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/product?post=61"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/wp-json\/wp\/v2\/coauthors?post=61"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}