Product Life Cycle Support DEXs

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

The purpose of the OASIS Product Life Cycle Support (PLCS) DEXs 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) DEXs standard is defined by Data Exchange Specifications (DEXs) that are based upon ISO 10303 (STEP) Application Protocol 239 (Product Life Cycle Support).

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:

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 Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee's 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).

Notices

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 the 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/who/trademark.php for above guidance.

1.0 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, "OASIS PLCS DEXs ed. 2008:1" defines the usage of the PLCS information model by breaking it up into smaller parts (DEXs) that directly support real life business processes. It builds the DEXs from reusable components (Templates) that guarantees uniform interpretation of PLCS between different DEXs, and adds extendible 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 ISO 10303 (STEP) Application Protocol 239 (Product Life Cycle Support).

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.

This edition of the OASIS PLCS DEX standardizes the following components:

The DEXs:
- Task Set DEX
Templates used by the DEXs
EXPRESS and XML Schemas of the DEXs
DEX Reference Data

Future editions of the OASIS PLCS DEXs 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. Acknowledgements

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

Participants:

Sean Barker	BAE Systems
Trine Hansen	DNV
Leif Tonning	DNV
Fredik Lied Larsen	DNV
Peter Bergström	Eurostep AB
Rob Bodington	Eurostep Limited
David Price	Eurostep Limited
Trisha Rollo	Eurostep Limited
Phil Spiby	Eurostep Limited
Mike Ward	Eurostep Limited
Mats Nilsson	FMV
Ann Meads	LSC Group
Tim Turner	LSC Group
Leif Gyllström	SAAB

In addition members of the following organizations have contributed with business knowledge, reviewing and other support activities: BAE Systems, DNV, Eurostep Group, FMV, Jotne EPM Technology, LSC Group, Mantech, Norwegian Defence Systems Management Division, Rolls-Royce, SAAB, UK MoD and US DoD.

Release	Date	Changes
Version 1 Committee Specification R5	Thu Sep 09 17:12:09 2010	Re-released DEX: task_set (Log), Revision: 1.80
Version 2 Public Review Draft R4	Mon Apr 19 17:12:09 2010	Re-released DEX: task_set Revision: 1.80
Version 2 Committee Draft R3	Fri Mar 26 17:12:09 2010	Updated DEX: task_set Revision: 1.80
Version 1 Committee Draft R2	Thu Feb 11 18:42:09 2010	Updated DEX: task_set Revision: 1.76
Version 1 Public Review Draft R1	Tue Mar 11 17:25:11 2008	New DEX: aviation_maintenance New DEX: task_set