Product Life Cycle Support Version 1.0

Committee Specification Draft 01 /
Public Review Draft 01

12 March 2013

Specification URIs

This version:

http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd01/plcslib-v1.0-csprd01.html (Authoritative)

http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd01/plcslib-v1.0-csprd01.pdf

Previous version:

N/A

Latest version:

http://docs.oasis-open.org/plcs/plcslib/v1.0/plcslib-v1.0.html (Authoritative)

http://docs.oasis-open.org/plcs/plcslib/v1.0/plcslib-v1.0.pdf

Technical Committee:

OASIS Product Life Cycle Support (PLCS) TC

Chairs:

Howard Mason (howard.mason@baesystems.com), BAE SYSTEMS plc

Jerry Smith (Gerald.L.Smith180.civ@mail.mil), US Department of Defense (DoD)

Editor:

Tor Arne Irgens (tai@sfk.mil.no), Norwegian Defence Logistics Organization

Additional artifacts:

This prose specification is one component of a Work Product which also includes:

Related work:

This specification replaces or supersedes:

This specification is related to:

  • ISO 10303-239:2012 "Industrial automation systems and integration -- Product data representation and exchange -- Part 239: Application protocol: Product life cycle support"

Declared XML namespaces:

Abstract:

The purpose of the OASIS Product Life Cycle Support (PLCS) standard is to establish structured data exchange and sharing capabilities for use by industry to support complex engineered assets throughout their total life cycle. The OASIS Product Life Cycle Support (PLCS) standard is defined by Data Exchange Specifications (DEX) that are based upon ISO 10303 (STEP) Application Protocol 239 Product Life Cycle Support.

The scope of the information content of ISO 10303-239 covers:

  • The identification and composition of a product design from a support viewpoint;
  • The definition of documents and their applicability to products and support activities;
  • The identification and composition of individual products;
  • Configuration management activities, over the complete life cycle;
  • Activities required to sustain product function;
  • The resources needed to perform such activities;
  • The planning and scheduling of such activities;
  • The capture of feedback on the performance of such activities, including the resources used;
  • The capture of feedback on the usage and condition of a product;
  • The definition of the support environment in terms of people, organizations, skills, experience and facilities.

The business goals of the OASIS PLCS DEXs are to satisfy three significant requirements for owners/operators of complex products and systems such as aircraft, ships and power plants, namely:

  • Reduction in the total cost of ownership;
  • Increased asset availability;
  • Effective information management throughout the product lifecycle.

Status:

This document was last revised or approved by the OASIS Product Life Cycle Support (PLCS) TC on the above date. The level of approval is also listed above. Check the Latest version location noted above for possible later revisions of this document.

Technical Committee members should send comments on this specification to the Technical Committees email list. Others should send comments to the Technical Committee by using the Send A Comment button on the Technical Committees web page at http://www.oasis-open.org/committees/plcs/.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (http://www.oasis-open.org/committees/plcs/ipr.php).

Citation format:

When referencing this specification the following citation format should be used:

[PLCS v1.0]

Product Life Cycle Support Version 1.0. 12 March 2013. OASIS Committee Specification Draft 01 / Public Review Draft 01.  http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd01/plcslib-v1.0-csprd01.html.

 

 

Notices

Copyright © OASIS Open 2013. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/policies-guidelines/trademark for above guidance.

 

Table of Contents

1     Introduction

1.1     Terminology

1.2     Normative References

1.3     Non-Normative References

1.4     Components of the standard

2     Conformance

   2.1 PLCS Platform Specific Model (PLCS PSM)

   2.2 Reference Data Ontologies

   2.3 PLCS Templates

Appendix A.     Acknowledgments

Appendix B.     Revision History

 

 


1       Introduction

The purpose of the ISO Product Life Cycle Support (PLCS) standard is to support complex engineered assets such as planes and ships throughout their total life cycle. It puts particular emphasis on the in-service phase of the product and, in particular, it supports the seamless transition from design and manufacture through to product support and feedback of usage and change.

The data needed is often distributed over multiple IT systems and organizations, and historically has been difficult to access and consolidate. The PLCS standard provides a large, integrated information model covering the whole lifecycle. The PLCS standard provides the basic mechanisms enabling neutral file exchanges between IT systems and organisations. This helps remove delays and costs for both the end user of the product and the supplier, and is particularly important for service-based contracts such as "power-by-the-hour".

The PLCS information model is larger than any single existing application, and needs detailed application rules in order to be used uniformly by different users and supported by different software applications. This standard, "Product Life Cycle Support Version 1.0" defines the usage of the PLCS information model through the use of Data Exchange Specifications (DEXs) that specify how it can be used to directly support real life business processes. It builds the DEXs from reusable components (s) that guarantee uniform interpretation of PLCS between different DEXs, and adds extensible business terminology (Reference Data) to the model. Each Data Exchange Specification (DEX) provides data exchange and sharing capabilities for a focused set of transactions based upon the integrated data model of (DEX) Application Protocol 239 (Product Life Cycle Support).

Note: No DEXs are included in this version of the standard, "Product Life Cycle Support Version 1.0", but will be included in future releases.

The information content of PLCS covers:

  • The identification and composition of a product design from a support viewpoint;
  • The definition of documents and their applicability to products and support activities;
  • The identification and composition of individual products;
  • Configuration management activities, over the complete life cycle;
  • Activities required to sustain product function;
  • The resources needed to perform such activities;
  • The planning and scheduling of such activities;
  • The capture of feedback on the performance of such activities, including the resources used;
  • The capture of feedback on the usage and condition of a product;
  • The definition of the support environment in terms of people, organizations, skills, experience and facilities.

The business goals of the OASIS PLCS DEXs are to satisfy three significant requirements for owners/operators of complex products and systems such as aircraft, ships and power plants, namely:

  • Reduction in the total cost of ownership;
  • Increased asset availability;
  • Effective information management throughout the product lifecycle.

 

1.1       Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

 

1.2       Normative References

[RFC2199]  S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.faqs.org/rfcs/rfc2119.html, IETF RFC 2119, March 1997.

[OWL]  OWL Web Ontology Language Reference, W3C Recommendation 10 February 2004, http://www.w3.org/TR/owl-ref, OWL, 2004.

[XMLSchema]  W3C XML Schema Definition Language (XSD), http://www.w3.org/standards/techs/xmlschema.

[Schematron]  ISO/IEC 19757-3:2006 - Information technology -- Document Schema Definition Languages (DSDL) -- Part 3: Rule-based validation -- Schematron, Schematron, 2006.

 

1.3       Non-Normative References

[XMI]  MOF 2.0/XMI Mapping Specification, v2.1, http://schema.omg.org/spec/XMI/2.1, 2005.

[SysML]  OMG Systems Modeling Language(OMG SysML™),Version 1.2, http://www.omg.org/spec/SysML/1.2/, SysML, 2010.

[10303-11:2004]  Industrial automation systems and integration - Product data representation and exchange: Part 11: Description methods: The EXPRESS language reference manual., ISO 10303-11, 2004.

[ISO 10303-239:2012(E)]  Industrial automation systems and integration - Product data representation and exchange: Application Protocol: Product life cycle support, ISO 10303-239, 2012.

 

1.4       Components of the standard

The Product Life Cycle Support Version 1.0 comprises the following components:

For a summary of these components and inter relationships, see DEX technology overview.

 

 

2           Conformance

This edition of the OASIS PLCS standardizes the components described below.

Not every implementation will use all the components.

Implementations shall conform to those components used as specified in the following sections.

2.1 PLCS Platform Specific Model (PLCS PSM)

The PLCS Platform Specific Model (PLCS PSM) is used as the data exchange form.

The PLCS PSM is represented in EXPRESS, SysML and XML Schema with the XML Schema being derived from the EXPRESS and SysML models.

Implementations shall conform to the XML Schema.

The following models are provided for explanatory purposes:

  • PLCS Platform Specific Model EXPRESS;
  • PLCS Platform Specific Model canonical SysML XMI.

 

The PLCS PSM exchange format, to which implementations shall conform, is represented as the following XML Schema with an associated set of Schematron rules:

2.2 Reference Data Ontologies

Reference data provides a tailorable vocabulary that adds business specific semantics to the information model.

The Reference Data is represented in OWL.

The following OWL ontologies are standardized and implementations shall conform to them:

2.3 PLCS Templates

The usage of the PLCS information model by a DEX is defined through Templates. The Templates provide a precise specification of how the model is used to represent a given concept.

Implementations shall conform to the specific Templates used.

The following Templates are standardized:

 

Note: Future versions of this standard, "Product Life Cycle Support Version 1.0", will extend the number of DEXs, Templates and Reference Data, as well as other parts to facilitate the adoption of the PLCS standard.

 

Appendix A. Acknowledgments

Participants:

The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Alf Andersson, Swedish Defence Materiel Administration

Sean Barker, BAE Systems

Rob Bodington, Eurostep Limited

Leif Gyllström, Saab AB

Trine Hansen, Det Norske Veritas

Patrick Houbaux, Eurostep SARL

Gunnel Johansson, The Swedish Centre for Terminology

Fredik Lied Larsen, Det Norske Veritas

Mats Nilsson, Swedish Defence Materiel Administration

Henrik Nilsson, The Swedish Centre for Terminology

Jon Rustand, Det Norske Veritas

Nigel Shaw, Eurostep Limited

David Skogan, Det Norske Veritas

Phil Spiby, Eurostep Limited

Peter Svanberg, The Swedish Centre for Terminology

Mike Ward, Eurostep Limited

In addition, members of the following organizations have contributed with technical resources, business knowledge, reviewing and other development and support activities: BAE Systems, Black & Rossi, Boeing, Det Norske Veritas, Eurostep Group, French Direction générale de l'armement, Lockheed Martin, Norwegian Defence Systems Management Division, Rolls-Royce, Saab AB, Swedish Defence Materiel Administration, The Swedish Centre for Terminology, UK Ministry of Defence and US Department of Defense.

Appendix B.  Revision History

Revision

Date

Changes Made

plcs-plcslib-v1.00-csprd01

2013-03-12

Product Life Cycle Support Version 1.0 Committee Specification Draft 01 Public Review Draft 01

Republication for plcs-plcslib-v1.00-csd01 for ballot as Committee Specification Draft 01 Public Review Draft 01

plcs-plcslib-v1.00-csd01

2013-03-12

Product Life Cycle Support Version 1.0 Committee Specification Draft 01 Public Review Draft 01

Initial release for review

PLCS PSM
The following issues have been addressed against the PLCS PSM:

  • Issue: 185 "Effectivity assignment should apply to RelationshipObjects"
  • Issue: 186 "ContractAssignmentSelect - Need to be able to assign a contract to Collection"

Templates
The following issues have been addressed against the Templates:

  • Issue: 286 "OASIS:StockItem id should be ids[1..*]"
  • Issue: 287 "OASIS:WorkOrder id should be ids[1..*]"
  • Issue: 288 "OASIS:WorkRequest id should be ids[1..*]"
  • Issue: 289 "OASIS:Task id should be ids[1..*]"
  • Issue: 290 "OASIS:WorkDone id should be ids[1..*]"
  • Issue: 291 "OASIS:PropertyValueNumeric incorrect private properties"
  • Issue: 292 "OASIS:ActualProductUsage - Incorrect binding between product and ActivityAssignment"
  • Issue: 293 "OASIS:Envelope - Wrong use of reference data"
  • Issue: 294 "OASIS:Justification - ids should be [1..*]"
  • Issue: 295 "OASIS:WorkRequest: Use Justification template "
  • Issue: 296 "OASIS:Applicability - call deprecated Individual template"
  • Issue: 297 "OASIS:Envelope id should be ids[1..*]"
  • Issue: 298 "OASIS:Message id should be ids[1..*]"
  • Issue: 299 "OASIS:Justification classify JustificationSupportAssignment and JustificationAssignment"
  • Issue: 300 "OASIS:StockItem - wrong type for property resourceItemSelect"
  • Issue: 301 "All templates: Incorrect / missing reference data constraints"
  • Issue: 302 "OASIS:EventReport - Need to be split into EventReport and EventReportItem"

Reference Data
The following issues have been addressed against the Reference Data:

  • Issue: 76 "Create Event_report_membership class"