{"id":162,"date":"2021-08-19T13:48:23","date_gmt":"2021-08-19T17:48:23","guid":{"rendered":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/?p=162"},"modified":"2026-03-26T15:42:04","modified_gmt":"2026-03-26T19:42:04","slug":"asset-maintenance-with-teamcenter-and-maximo","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/service-lifecycle-management\/2021\/08\/19\/asset-maintenance-with-teamcenter-and-maximo\/","title":{"rendered":"Asset Maintenance with Teamcenter and Maximo"},"content":{"rendered":"\n

Efficiently manage asset maintenance throughout an asset’s service life, bridging together the Service BOM and Execution.<\/p>\n\n\n\n

\"Man<\/figure>\n\n\n\n

Siemens and IBM have entered into an alliance<\/a> that delivers uniform and centralized BOM management across the enterprise, supporting a holistic asset maintenance process. This blog highlights solutions from Teamcenter Service Lifecycle Management<\/a> and Maximo<\/a>, and how they are integrated to provide a complete solution for maintaining physical assets throughout their service life.<\/p>\n\n\n\n

Closed-loop Asset Maintenance<\/h3>\n\n\n\n

To achieve a closed-loop Asset Maintenance process, service engineering should occur in parallel with design and configuration work. This is possible using Teamcenter and Maximo integrated solutions, where the data (asset information) flows from Teamcenter to Maximo, and back from Maximo to Teamcenter. <\/p>\n\n\n\n

The Service BOM <\/a>(sBOM), managed in Teamcenter, will contain the design of the product with serviceability information such as, whether a design in the sBOM is a lot, or whether it\u2019s serialized, etc. The Service Plan<\/a> details the steps for servicing the components from the sBOM. The Service Plan, defined and managed in Teamcenter, has three main components which are Service Requirements, Work Cards, and Activities. Each Service Requirement represents the maintenance that needs to be performed on the asset. This Service Plan definition is used by Maximo to create Work Orders. <\/p>\n\n\n\n

\"asset
Figure 1: Service Plan of a Landing Gear<\/figcaption><\/figure>\n\n\n\n
\n\n\n\n

 In Figure 1, the Service Plan of a Landing Gear is defined in Teamcenter. It has six (6) Service Requirements highlighted in green. There can be a Frequency defined on the Service Requirement, indicating how often the maintenance needs to be carried out on the asset.<\/p>\n\n\n\n

\"This
Figure 2: “Replace Tire” Service Requirement<\/figcaption><\/figure>\n\n\n\n

As seen in Figure 2, there is a Frequency defined as \u201cReplaceTireFrequency\u201d on the Service Requirement \u201cReplaceTire\u201d. It indicates that the \u201cReplaceTire\u201d has to be performed every six months. The Planner can also define that a Service Requirement resolves a specific Fault Code.<\/p>\n\n\n\n

\"This
Figure 3: This shows the “Replace Existing Tire” Work Card<\/figcaption><\/figure>\n\n\n\n

The Work Card details how the Service Requirement is to be completed. The Planner can specify the Skills, Tools, and Resources on the Work Card. In Figure 3, the \u201cReplaceExistingTire\u201d, Work Card is defined on the Service Requirement \u201cReplaceTire\u201d. If more detailing is required on a Service Requirement, additional Work Cards can be added to it.<\/p>\n\n\n\n

\"This
Figure 4: This shows the “Inspect Oil Leakage” Work Card<\/figcaption><\/figure>\n\n\n\n

Similarly, in the Service Requirement, \u201cInspectOilLeakageHydUnit,\u201d \u201cInspect Oil Leakage,\u201d there is a related Work Card, as seen in Figure 4. The Service Requirement\/Work Card also has information regarding the tools and resources required to perform the maintenance. The skills and qualifications required by the Technician to perform the Service Requirement are also defined in Teamcenter. In this example, the Work Card \u201cInspectOilLeakage,\u201d has the defined resources and necessary skill sets required to carry out the maintenance work.<\/p>\n\n\n\n

Furthermore, activities are defined on the Work Card, as granular steps. There can be multiple Activities described on the Work Card. Activities sequencing is defined in Teamcenter, along with the duration required to perform each Activity. The sub-assembly can also be assigned to the Activity, along with the equipment used to perform it. All of the Activities that need to be performed in order to \u201cReplace the Tire\u201d are also defined in Teamcenter. The Work Time required for completing the \u201cReplace Existing Tire\u201d activity is the sum of the Work Time required for all activities under it.<\/p>\n\n\n\n

As you can see, the Service Plan<\/strong>, Frequency<\/strong>, Service Requirement<\/strong>, and Work Card<\/strong> \u2013 all critical components to an execution process, are created and managed in Teamcenter, but the execution information<\/strong> is stored in Maximo. With execution data flowing between Teamcenter and Maximo, the product design can be enhanced based on operational information such as failure code, parts affected, replacement part life, etc.<\/p>\n\n\n\n

Accessing Teamcenter data from Maximo<\/h3>\n\n\n\n

To import the sBOM structure of the asset, Maximo queries Teamcenter using a tracking number such as an Item ID, Serial Number, or Part Number of the Physical Part (Fielded Asset). Once the import is triggered, the entire configured sBOM present in Teamcenter is used to create an equivalent asset hierarchy in Maximo. This results in the mapping of Teamcenter Parts to Maximo Assets or Items.<\/p>\n\n\n\n

The movie below shows Teamcenter asset information imported to Maximo.<\/p>\n\n\n\n