PLCS - The Product Life Cycle Support Standard - An Executive Overview

1. PLCS - The Product Life Cycle Support Standard - An Executive Overview

2. Introduction

3. What is PLCS? • It stands for Product Life Cycle Support • It is an International Standard • It is an information standard • It defines the form of information and how it can be linked together • It is a means to: • Exchange or share product data • Manage change • Maintain product histories • across organizational and application boundaries and between life cycle phases

4. Why PLCS? • Management of complex products through life involves: • Multiple organizations • Multiple IT systems • Many point to point links for exchange/sharing • Many different functions • Mostly operating in “cylinders of excellence” • Managing change and obsolescence • No standard existed for the joined up view required to manage and optimise products and their support systems through life

5. How to keep the information needed to operate and maintain a product aligned with the changing product over its life cycle? Product in Focus Product Definition Information Transportation Consumables Maintenance Schedules Software Tools Spares Test Equipment Training Support Facilities Storage Requirements Setting the Business ContextThe Key Business Problem Feedback

6. Product Life Cycle Support (PLCS)Typically complex systems environment – point to point integration CM Data Operational Objectives CM Data CM Data CM Data 4. Maintenance Management 9. Product Data 14 Defects & Failure Reporting 5. Requirements Management 12 Depot Maint Mgmt Functional Requirements Defects and Failures CM Data Maintenance Mgt Data 1. Support Data Support Data 3. Stock Mgmt 13. Distribution, Transportation 7. FMECA Design Data FMECA Results LSA Data Support Data Distribution Data LSA Data 2. Maintainers Viewing Tool 6. LSAR 8. CAD 10 IETM 11 Parts Supplier Database Part Data LSA Data Tech Pubs Data Support Data

7. Product Life Cycle Support (PLCS)PLCS will enable cost effective information exchanges 3. Stock Mgmt 5. Requirements Management 2. Maintainers Viewing Tool 1. Support Data 4. Maintenance Management 6. LSAR 7. FMECA FMECA Results Maintenance Mgmt Data Support data LSA Data Maintenance Mgmt Data Part data Functional Req. PLCS compliant information exchanges Tech Pub Data Maintenance Mgt Data Design Data Design data Defects& Failures Distribution Data Parts Data 9. Product Data 13. Distribution, Transportation 8. CAD 10 IETM 11 Parts Supplier Database 14 Defects & Failure Reporting 12 Depot Maint Mgmt In future, support system integration will be easier to implement

8. Finnish Defence Forces Who paid for PLCS to be created in 1999-2005? Five Defense Departments: USA, UK, Norway, Sweden, Finland Note: PLCS is dual use, NOT defense specific Risk management Norway Major OEMs: USA, UK, Sweden IT systems providers and consultants: ERP, PLM and specialist tools US, UK, Netherlands

9. What activities does PLCS cover?

10. Top level PLCS coverage Provide through life support for product Product needing support Supported product Information Information Change & Events IT infrastructure Support infrastructure

11. Top level PLCS coverage Provide through life support for product Product needing support Supported product Disposed product Information Information Change & Events Feedback Requirements IT infrastructure Support infrastructure

12. PLCS Activity - first level breakdown Provide through life support for product Supported product Product needing support Information Information Manage Information to support a product Generate Support Solution Commission Support System Provide Support

13. The bigger PLCS picture Design & Manufacture Provide through life support for product Provide through life support for product Product needing support Product needing support Supported product Supported product Information Information Information Information Systems Engineering HUMS CBM Manage Information to support a product Manage Information to support a product Generate Support Solution Generate Support Solution Commission Support System Commission Support System Provide Support Provide Support Business transactions Order, Receipt, Store, Allocate

14. The bigger PLCS picture Design & Manufacture Provide through life support for product Product needing support Supported product Information Information Systems Engineering HUMS CBM Manage Information to support a product Generate Support Solution Commission Support System Provide Support Business transactions Order, Receipt, Store, Allocate

15. The bigger PLCS picture Manage Information to support a product Design & Manufacture Provide through life support for product Product needing support Supported product Information Information Systems Engineering Manage Information to support a product Generate Support Solution Commission Support System Provide Support HUMS CBM Business transactions Order, Receipt, Store, Allocate

16. What does PLCS contain?

17. PLCS Content Key Activity Specifications ActivityHistory Product Designs Product Breakdowns Individual Products States Product Descriptions Management Process Environment Details

18. PLCS Content – very high level Items of interest Project Contract Location Configurations and discipline views Tasks and Schedules Faults and Operating States The physical Products (UID) Support and usage history Commissioning of Work/Change Properties, People and Times and more

19. PLCS business functionality • Exchange and sharing of data across the product life cycle • Capture of relationships/dependencies between items from different disciplines • Which usually reside in different specialist systems • Capture of information to enable comparison of what was supposed to be and what actually happened • Maintenance, failures, usage, configurations • Enable management of change

20. Maintenance Task perfomance Maintenance Schedule Maintenance Task Planning Actual Fault states Maintenance Task Maintenance Requirements Maintenance Analysis Fault state definitions Maintenance Plan Manufacturing BOM Design Requirements Design Configuration Spare Parts Configuration Domain Definitions (CAD, etc) Design Analysis As-maintained Individual Configuration Location Management As-built Cross-discipline Change Extended Enterprise Change Management Usage LSAR Individuals Designs Definition

21. PLCS for Data Exchange

22. Data Exchange Specifications (DEXs) • PLCS has a big scope and a rich flexible data model • For specific Data Exchanges a more tailored specification called a PLCS DEX is used • Reduces scope • a subset of the overall PLCS information content • XML schema to match • Details how to capture specifics (e.g. Item Unique Id) • Allows for localised terminology • DEXs can be used to contracting for information • Data sets from different DEXs are easily combined • All covered by the underlying PLCS data model

23. PLCS DEX for Maintenance and Repair • Funded by Black & Rossi • Stakeholders: • NATO – Coalition Logistics Interoperability • US Marines – PLMAV program • NAMSA • UID Office • Objectives: • Demonstrate interoperability using PLCS in an international arena

24. Maintenance & Repair: PLCS Maintainer Operator

25. Maintenance & Repair: PLCS Maintainer Operator PLCS DEXA Data Exchange Specification

26. DEX fit with Business Process Information is communicated using a subset of PLCS expressed in XML Approach is independent of the applications used at either end of the exchange

27. Summary • PLCS is an ISO standard that enables exchange and sharing of technical data and feedback for complex systems/products • A DEX is a way to specify Messages for exchange that are part of a consistent broader approach that maximises information connectivity • The Maintenance and Repair DEX will support Coalition Logistic Interoperability needs • In line with the NATO STANAG for PLCS