PLCS based interoperability in PLM

Transcription

1 PLCS based interoperability in PLM The why and how of a pragmatic approach Nigel Shaw

2 Agenda What is PLCS? What do we mean by interoperability? Required capabilities key concepts Some examples of application of PLCS Future developments

3 What is PLCS? The Key Business Problem: How to keep the information needed to operate and maintain a product aligned with the changing product over its life cycle? Product Definition Information Maintenance Schedules Tools Test Equipment Product in Focus ISO Feedback Transportation Consumables Software Spares Training Support Facilities ISO Storage a through life information Requirements model

4 The PLCS Concept Model A high level view

5 What do we mean by interoperability? the ability of computer systems or software to exchange and make use of information (Oxford English Dictionary) The information can come from: Another IT system Another process With respect to existing information, the new information: Overlaps in content Another enterprise Another domain/discipline Another life cycle phase Relates to it References it Describes the same real world things PART: ABC123

6 What do we need for interoperability? the ability of computer systems or software to exchange and make use of information (Oxford English Dictionary) The information can come from: Another IT system Another process With respect to existing information, the new information: Overlaps in content Another enterprise Another domain/discipline Another life cycle phase Relates to it References it Describes the same real world things PART: ABC123

7 So what makes PLCS good for interoperability?

8 PLCS Key concepts Multiple identifiers Designs versus individuals Designed for history & change Relationships and Extensibility DEXs

9 Multiple identifiers Every item that can have an identifier can have more than one Every identifier has a context Who owns the identifier The original perceived need The new need: GUIDs from different systems for the same object System A GUID = _XXiFAMA0EeWv3 KMxAS5FRQ+_o2 N7AL7XEeWv3KM xas5frq System B GUID = EAID_C4B25272_E 714_4f6a_838C_2C AA2C778C57

10 Support System Product Designs versus individuals Life cycle of the design Life cycle of the individual

11 Support System Product Designed for history & change Life cycle of the design Life cycle of the individual

12 Support System Product Designed for history & change Life cycle of the design Life cycle of the individual

13 Relationships and Extensibility Data will change over time Track the history Manage specifics Who, when, why Relationships that can be specialised through classification Part of the history Includes multiple BOMs Identity Relationships Entity / Object Types of Things Types of Activity Tangible Things Actual Activities Characterizations Dates/Times Organizations Properties States Justifications Classifications Effectivity

14 DEXs (Data Exchange Specifications) When you have the richness to vary/extend/specialise that PLCS offers Need the means to be specific for contracting and conformance Hence Data Exchange Specifications

15 Different industries Defence Commercial Aerospace Modelling and Simulation Automotive Energy Road and Rail

16 Defence

17 Commercial Aerospace Modelling and Simulation - MBSE TOICA Using MoSSEC implemented using PLCS SAVI Systems Architecture Virtual Integration Cross model type MBSE

18 Automotive

19 Automotive

20 Energy Slides as presented PI Congress 2014

21 Road and Rail in Sweden (Acando & Eurostep for Trafikverket) Managing asset data for road and rail networks in Sweden Not what PLCS was aimed at but still complex products with long life cycles and on-going maintenance

22 Future development Release of PLCS PSM Feedback from French DGA, Swedish Defence and BAE Systems In preparation Likely to be made available via SourceForge Edition 3 Move to return to ISO as main publication route New Work Item approved under ISO TC 184/SC 4 Funded effort with plan to get going in 2017 Closer integration with ASD standards MoSSEC Modelling and Simulation information in a collaborative Systems Engineering Context New Work Item currently out for ballot under ISO TC 184/SC 4

23 Questions