MRO Neutral Structure Management

7/27/2019 MRO Neutral Structure Management

1/25

Siemens PLM Software

Siemens AG 2012. All Rights Reserved.

Neutral BOM Managementand the Impact on Physical

Structure

James Batka

Software Product Consultant

http://plmworld.org/


2/25



Page 2

Teamcenter MRO

Challenges

Services must manage SBOMindependent of Engineering

Must include all service parts

Engineering must maintaincontrol of design

Remain manageable in size

Neutral BOM requirements

BUT

Some Neutral BOM requirements conflict!

Creating a neutral BOM for services

Managing neutral BOM for services

Exporting and Importing data

Change Management

Data Quality


3/25



Page 3

Teamcenter MRO

Why use MRO?

Report describing engine testfailure from the 1980s

Turbine engine disk failureduring testing

A disk fragment flew ~ mi,

through ceiling of office buildingsceiling

Landed on desk of the testprogram lead engineer

Hot disk fragment (probably 700

800 F) burned the engineersdesk top and bounced onto thefloor


4/25



Page 4

Teamcenter MRO

Why use MRO?

Incident investigation found:

Disk failed due to improper heattreatment

Heat treatment failed due to bad

thermal sensor Other disks created using the

same process were in flight inboth military and commercialaircraft

The engine company had totrack down and remove alldefective engines from vehiclesand inventory

MRO:

Tracks all serial parts enteredinto the system

Tracks production lot

membership Tracks the location of both serial

and lot parts

What took the engine companyweeks or more of time in the

1980s could be accomplished ina few minutes with TeamcenterMRO!


5/25



Page 5

Teamcenter MRO

Neutral Structure versus Physical Structure

Authorized

Neutral

EngineeringDesign & Development ProductionDelivery & Support

Physical

Actual


6/25

Siemens PLM Software Siemens AG 2012. All Rights Reserved.

Page 6

Why use MRO?

Complexities of managing physical structure

ED&D eBOMRev A

Production & Delivery Sustainment

Rebase

Modification Retrofit

eBOMRev BUpgrade

Brake Rotor

eBOMRev C

eBOMRev D

Upgrade StrutNew Brake

Pad

Hull-40 Hull-30Hull-50 Hull-20 Hull-10


7/25Siemens PLM Software Siemens AG 2012. All Rights Reserved.

Page 7

Neutral BOM Management for MRO

Service BOM

Service BOM

What is it?

Requirements

Part Selection

Managing SBOM

Other Considerations

HD User Experience

Intelligently Integrated

Information

Future-proof Architecture



Page 8

Service BOM

What is it?

As template:Used to generate physical structure

As reference:Used to highlight missing, extra to design,deviated, and differences between design& reality

A correct Service BOM is critical to MRO!

Neutral Structure used by Physical Structure



Page 9

Service BOM

What is it?

EBOM SBOM

How do you determine what should be included / excluded?How do you manage differences?

Service BOM differs from the Engineering BOM!



Page 10

Service BOM

Requirements and Recommendations

Requirements:

Must (eventually) include:

Options & Variants

Substitutes

Upstream BOM changes mustpropagate to SBOM

Ability to add parts to BOM forservices use (e.g. customer &vendor parts)

Recommendations:

Created and managed byservices organization

Manage changes with formal

change management process


11/25Siemens PLM Software

Siemens AG 2012. All Rights Reserved.Page 11

Service BOM

Parts to include in SBOM

Rules for including / excluding parts from SBOM

DoD Guidelines:

DoD Instruction 5000.64 (IUID Guidelines)

Part acquisition >= $5000

All serially managed parts

Controlled inventory parts

Mission essential parts (e.g. essentiality codes 1, 3, 5, 6, & 7)

DoD Instruction 4130.1-R (SMR Code)

Reparable parts

Plus any parts required by customer Plus any assembly higher in the product structure which contains

any of these parts regardless of whether it satisfies theserequirements





Managing SBOM

Service BOM

Managing SBOM

Multi-Structure Manager

Independently managed BOMs

150% BOMOther Considerations

HD User Experience


Information





Managing SBOM

Teamcenter Multi-Structure Manager

MSM assists in managing perspectives

of single BOM

Plusses:

Recommended method of managingmultiple BOMs by product development

Organizations less dependent uponcooperation

Minuses:

Requires MSM licenses

Our team lacked experience with this

method

Requires disciplined changed

management

Multi-Structure Manager




Managing SBOM

Independently Managed BOMs

Duplicate parts created to represent

a single part

Plusses:

Organizations not dependent uponcooperation

No Teamcenter licenses required Best method for dealing with vendor

parts

Minuses:

Most prone to data errors

Most duplication of effort

Requires disciplined change

management

EBOM SBOM




Managing SBOM

150% BOM

BOM which combines parts into single BOM

Plusses:

No Teamcenter licenses required

Changes within service parts do NOT requireengineering authorization

Minuses: Requires cooperation between organizations

Requires disciplined change management

Other:

Use part types to enable different security andsearches for EBOM/SBOM parts

Changes to design require engineeringauthorization good for highly regulatedenvironments

EBOM + SBOM






Service BOM

Managing SBOM


Maintenance Planning

Data Export / Import Change Management

Data Quality

HD User Experience


Information



17/25


Page 17


Maintenance Planning

Thoughts on Maintenance Planning:

For military and highly regulated industries, technical manual andmaintenance planning MUST share source of task information

Neither Content Management nor Maintenance Planning can

currently output maintenance planning detail into technical manuals

Military required to followmost recent technical

manuals even whenthey are known to be outof date


18/25


Page 18

Other Consideration

Data Export and Import

PLMXML

Existing Teamcenter capability

Can export & import

Service actions

Service BOM

Physical Structure

Related data

S1000D

Existing industry standard

Intended for the exchange of:

Service tasks

Service BOM

Physical structure

Related data

USAF & Army already receivemaintenance data in this format

A&D companies already delivermaintenance data in this format

BUT

Teamcenter cannot (yet) parse S1000D XML

Teamcenter cannot (yet) produce S1000D documents

MIL-STD-3031A, DEPARTMENT OF

DEFENSE STANDARD PRACTICE: ARMY

BUSINESS RULES FOR S1000D


19/25


Page 19


Change Management and its role in MRO

Forward Change Process results in deployment of new designs to

existing systems

Retrofit new capability to existing systems

Upgrade or rebuild system to new standards

Determines when to update physical structure to new designreference (rebase)

Reverse change process (Service Discrepancy -> Problem ->

Change Request -> Change process) can be used to heal data

errors such as:

Physical structure mistakes

Physical structure referencing incorrect SBOM

Previously undocumented substitute and alternate parts


20/25


Page 20


Data Quality

All downstream processes affected by quality of Engineering data

SBOM Problems SBOM require fixing onlytwo structures:

Spend time correcting your EBOM / SBOM prior to deploying MRO

It will pay back your investment many fold over time!

EBOM & SBOM

Physical structure problems require

correcting EBOM, SBOM, and ALL physicalstructures referencing the affected SBOM

Correcting errors in the EBOM/SBOM isextremely difficult

Each correction must propagate through theenterprise change management process

Which cou ld be

dozens o r more!

Cant modify released

revis ions o f a part!

This could bog th eprocess dow n


21/25


22/25


23/25


Page 23

MRO Neutral BOM Management

Related Sessions

502 Teamcenter Change Management Overview

Wednesday / 9:30 AM

228 MRO Overview

Wednesday / 1:00 PM

62 I Need it NOW, I Need it CORRECT

Wednesday / 1:45 PM

702 Birds of a Feather

Wednesday / 4:10 PM


24/25


Page 24

MRO Neutral BOM Management

Related Materials

Sample US AF Technical Order (AFI) http://www.ngbpdc.ngb.army.mil/pubs/21/afi21-105_angsup_I.pdf

S1000D

http://www.s1000d.net/

http://www.everyspec.com/MIL-STD/MIL-STD+%283000+-+9999%29/MIL-STD-

3031A_32065/ DoD IUID (DoD Instruction 5000.64)

http://www.acq.osd.mil/dpap/pdi/uid/index.html

http://www.dtic.mil/whs/directives/corres/pdf/832004p.pdf

http://www.acq.osd.mil/dpap/UID/attachments/UIDfaq_extended.doc

DoD SMR Code (DoD 4130.1-R) http://www.dtic.mil/whs/directives/corres/pdf/414001r.pdf
http://plmworld.org/http://www.ngbpdc.ngb.army.mil/pubs/21/afi21-105_angsup_I.pdfhttp://www.s1000d.net/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.acq.osd.mil/dpap/pdi/uid/index.htmlhttp://www.dtic.mil/whs/directives/corres/pdf/832004p.pdfhttp://www.acq.osd.mil/dpap/UID/attachments/UIDfaq_extended.dochttp://www.dtic.mil/whs/directives/corres/pdf/414001r.pdfhttp://www.dtic.mil/whs/directives/corres/pdf/414001r.pdfhttp://www.dtic.mil/whs/directives/corres/pdf/414001r.pdfhttp://www.acq.osd.mil/dpap/UID/attachments/UIDfaq_extended.dochttp://www.acq.osd.mil/dpap/UID/attachments/UIDfaq_extended.dochttp://www.dtic.mil/whs/directives/corres/pdf/832004p.pdfhttp://www.dtic.mil/whs/directives/corres/pdf/832004p.pdfhttp://www.dtic.mil/whs/directives/corres/pdf/832004p.pdfhttp://www.acq.osd.mil/dpap/pdi/uid/index.htmlhttp://www.acq.osd.mil/dpap/pdi/uid/index.htmlhttp://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.everyspec.com/MIL-STD/MIL-STD+(3000+-+9999)/MIL-STD-3031A_32065/http://www.s1000d.net/http://www.s1000d.net/http://www.s1000d.net/http://www.ngbpdc.ngb.army.mil/pubs/21/afi21-105_angsup_I.pdfhttp://www.ngbpdc.ngb.army.mil/pubs/21/afi21-105_angsup_I.pdfhttp://www.ngbpdc.ngb.army.mil/pubs/21/afi21-105_angsup_I.pdfhttp://www.ngbpdc.ngb.army.mil/pubs/21/afi21-105_angsup_I.pdfhttp://plmworld.org/http://plmworld.org/

Documents

MRO Neutral Structure Management