Product Life Cycle Support DEXs Version R5. 18 November 2010. OASIS Committee Specification 01. http://docs.oasis-open.org/plcs/dexlib/cs01/oasis_cover.htm

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. 19 July 2013. OASIS Committee Specification Draft 02. http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/plcslib-v1.0-csd02.html.

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 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. These usage rules cover:

The subset of the overall information model that needs to be exchanged to meet a particular business objective;
The data elements that are available to the exchange, selected from the optional data elements in the underlying model;
Constraints on the population of the model, for example, requiring that a network of subsystems take the form of a tree.

This standard "Product Life Cycle Support Version 1.0" defines how these usage rules are applied to the PLCS information model, as grouped together in Data Exchange Specifications (DEXs), each of which specify how the PLCS information model is 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.

[OCL] Object Constraint Language (OCL), Version 2.0, http://www.omg.org/spec/OCL/2.0/, OCL, 2006.

[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 standard comprises the components summarized below.

Note: This front page is provided as a high level summary of the Product Life Cycle Support Version 1.0 standard. The detailed description of the components listed below is provided as a set of HTML pages which should be accessed through a web browser.

Contexts: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/sys/context_index_base.html
A Context identifies a domain or business purpose area for which DEXs are defined;
DEXs: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/sys/dex_index_base.html
A DEX identifies and documents a subset of the ISO 10303-239 (PLCS) information model required for a specific business purpose;
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.
Templates: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/sys/template_index_base.html
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;
Model Usage Guides: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/sys/sys/model_ug_index_base.html
Model Usage Guides provide guidance on how the information model and templates should be used.
Reference data: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/sys/refdata_index_base.html
Reference Data provides a tailorable vocabulary that adds business specific semantics to the information model.
Concept model: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/data/PLCS/concept_model/model_base.html
A high level model of the main concepts used in ISO 10303-239. It is intended to be used to introduce on a single page the scope that PLCS addresses.
Activity model: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/sys/activity_model_index_base.html
The ISO 10303-239 Activity Model that illustrates the business activities that are supported by ISO 10303-239;
PLCS PSM: http://docs.oasis-open.org/plcs/plcslib/v1.0/csd02/data/PLCS/psm_model/model_base.html
The PLCS Platform Specific Model (PLCS PSM) that is used as the data exchange form for all DEXs. The PLCS PSM is a SysML model with an derived XML Schema;

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

2 Conformance

This edition of the OASIS PLCS standardizes the following components:

The PLCS Platform Specific Model (PLCS PSM) that 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.
Reference Data that provides a tailorable vocabulary that adds business specific semantics to the information model. The Reference Data is represented in OWL.
Templates that provide a precise specification of how the PLCS PSM is used to represent a given concept.

Not every implementation will use all the components.

There are two types of conforming implementations:

a data exchange XML file and
a data exchange application.

An implementation is a conforming data exchange file, a PLCS Platform Specific Model data file (a PSM data exchange file), if the file is in accordance with the conditions specified in the following sections. Namely that PSM data exchange file:

Conforms to the PLCS Platform Specific Model XML Schemata: common.xsd, plcs_psm.xsd (Section 2.1);
Conforms to the PLCS Platform Specific Model Schematron: plcs_psm.sch (Section 2.1);
Contains references to the OWL classes or objects specified in the following OWL ontologies (Section 2.2):

PLCS PSM Reference Data plcs-psm-en.owl
PLCS Reference Data plcs-rdl-en.owl

Is structured according to the patterns specified in the Templates (Section 2.3).

An implementation is a conforming data exchange application that must consume and produce any conforming PSM data exchange file.

The following sections describe how the PLCS PSM, Reference Data and Templates are used to establish conformance to this standard.

2.1 PLCS Platform Specific Model (PLCS PSM)

The PLCS Platform Specific Model (PLCS PSM) is a specification of 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.

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 Schemata with an associated set of Schematron rules:

PLCS Platform Specific Model XML Schema: common.xsd, plcs_psm.xsd;
PLCS Platform Specific Model Schematron: plcs_psm.sch.

An implementation is a conforming data exchange file, a PLCS Platform Specific Model data file (a PSM data exchange file) that:

Conforms to the PLCS Platform Specific Model XML Schemata: common.xsd, plcs_psm.xsd;
Conforms to the PLCS Platform Specific Model Schematron: plcs_psm.sch.

An implementation is a conforming data exchange application that must consume and produce any conforming PSM data exchange file.

2.2 Reference Data Ontologies

Reference Data provides a tailorable vocabulary that adds business specific semantics to the by PLCS Platform Specific Model .

The Reference Data is represented in OWL.

An implementation is a conforming data exchange file, a PLCS Platform Specific Model data file (a PSM data exchange file) that:

Conforms to the PLCS Platform Specific Model XML Schemata: common.xsd, plcs_psm.xsd; (Section 2.1)
Conforms to the PLCS Platform Specific Model Schematron: plcs_psm.sch (Section 2.1);

The PSM data exchange file may contain references to OWL classes or objects. When such references occur they must refer to OWL classes or objects in the following OWL ontologies:

PLCS PSM Reference Data plcs-psm-en.owl
PLCS Reference Data plcs-rdl-en.owl

An implementation is a conforming data exchange application that must consume and produce any conforming PSM data exchange file.

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 PLCS Platform Specific Model is used to represent a given concept.

Implementations shall conform to the specific Templates used.

An implementation is a conforming data exchange file, a PLCS Platform Specific Model data file (a PSM data exchange file) that:

Conforms to the PLCS Platform Specific Model XML Schemata: common.xsd, plcs_psm.xsd; (Section 2.1)
Conforms to the PLCS Platform Specific Model Schematron: plcs_psm.sch (Section 2.1);
Where PSM contains references to OWL classes or objects, such references occur they must refer to OWL classes or objects in the following OWL ontologies:

PLCS PSM Reference Data plcs-psm-en.owl
PLCS Reference Data plcs-rdl-en.owl

Contains data elements structured according to the patterns specified in the Templates.

The following Templates are standardized:

Template: ActualActivity
Template: ActualMission
Template: ActualMissionItem
Template: ActualProductUsage
Template: Applicability
Template: Approval
Template: Baseline
Template: Breakdown
Template: BreakdownElement
Template: BreakdownElementRealization
Template: BreakdownStructure
Template: Catalog
Template: CatalogItem
Template: CatalogItemRealization
Template: CatalogItemStructure
Template: Certification
Template: ClassCode
Template: Classifier
Template: Collection
Template: Contract
Template: DatedEffectivity
Template: Descriptor
Template: DirectedActivity
Template: Document
Template: EffectivityAssertion
Template: Envelope
Template: EnvironmentDefinition
Template: EnvironmentObserved
Template: EventReport
Template: EventReportItem
Template: Fleet
Template: FleetItem
Template: FunctionalBreakdown
Template: FunctionalBreakdownStructure
Template: FunctionalElement
Template: Identification
Template: IndividualCode
Template: Justification
Template: MeasuredProperty
Template: Message
Template: Name
Template: Observation
Template: Organization
Template: Part
Template: PartAssembly
Template: Person
Template: PersonInOrganization
Template: PhysicalBreakdown
Template: PhysicalBreakdownStructure
Template: PhysicalElement
Template: PlannedActivity
Template: ProductConfiguration
Template: ProductConfigurationOptionRelationship
Template: ProductConfigurationStructure
Template: Project
Template: PropertyValueNumeric
Template: PropertyValueText
Template: ProxyItem
Template: RealizedPart
Template: RealizedPartAssembly
Template: Requirement
Template: ResourceOrder
Template: ResourceOrderAcknowledgment
Template: ResourceOrderDelivery
Template: ResourceOrderDeliveryReceipt
Template: ResourceOrderLineItem
Template: ResourcePool
Template: ResourcePoolItem
Template: Scheme
Template: SchemeEntry
Template: StateAssertion
Template: StateAssessment
Template: StatePrediction
Template: StockItem
Template: SystemBreakdown
Template: SystemBreakdownStructure
Template: SystemElement
Template: Task
Template: ViewDefinitionContext
Template: Warranty
Template: WorkDone
Template: WorkOrder
Template: WorkRequest

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-csprd02	2013-06-21	Product Life Cycle Support Version 1.0 Committee Specification Draft 02 Public Review Draft 02 Republication for plcs-plcslib-v1.00-csd02 for ballot as Committee Specification Draft 02 Public Review Draft 02
plcs-plcslib-v1.00-csd02	2013-06-21	Product Life Cycle Support Version 1.0 Committee Specification Draft 02 Release addressing issues raised during public review of OASIS Committee Specification Draft 01 / Public Review Draft 01 http://docs.oasis-open.org/plcs/plcslib/v1.0/csprd01/plcslib-v1.0-csprd01.html PLCS PSM The following issues have been addressed against the PLCS PSM: Issue: 204 "SecurityClassification 'level'" Issue: 203 "Extend CollectionAssignment select" Issue: 202 "SecurityClassificationAssignment.classification" Issue: 201 "AttachmentSlotOnProduct needs Id" Issue: 200 "JustificationSupportAssignment / justification missing" Issue: 199 "Schematron uses prefix plcs:" Issue: 198 "Incorrect relationships shown for AttachmentSlotAsRealized & attachmentSlotDesign" Issue: 197 "PropertyValueAssignment - descriptions should be improved" Issue: 195 "RiskEvent.perceivedProbability - model only allows one probability to be defined" Issue: 194 "RiskPerception.riskLevel - model only allows one level to be defined" Issue: 193 "RiskPerceptionContext not required" Issue: 192 "plcs psm xsd has incorrect nesting of some relationship attributes" Issue: 191 "Effectivity should be applicable to ResourceItemRealization" Issue: 189 "URI constraint needed" Issue: 187 "DateTimeString constraints needed" Issue: 159 "DatedEffectivity attribute definitions not updated" Templates The following issues have been addressed against the Templates: Issue: 355 "OASIS: WorkDone : change cardinality of property activityInputs" Issue: 354 "Use of Connectors in parametric diagrams - should be Binding Connectors" Issue: 351 "OASIS:Contract - missing detail in parametric diagram" Issue: 350 "OASIS: BreakdownElementRealization : remove realizationRole property" Issue: 349 "OASIS: Approval - Wrong input property type for approvingPersOrOrg" Issue: 347 "OASIS:ResourcePoolItem - Incorrect classification Actual_dated_effectivity" Issue: 346 "OASIS:ResourcePool - Incorrect classification Actual_dated_effectivity" Issue: 345 "OASIS:ActualMissionItem - Incorrect classification Actual_dated_effectivity" Issue: 344 "OASIS:ResourceOrder redundant property 'orderType'" Issue: 343 "OASIS:WorkRequest: redundant 'purpose' property" Issue: 342 "OASIS: StateAssessment: Add 'Name' [0..1] property" Issue: 341 "OASIS: StateAssertion : Add Name [0..1] Property" Issue: 340 "OASIS:Requirement binding to public property" Issue: 339 "Incorrect Reference Properties" Issue: 338 "templates have 'Shared' property - should be 'Reference'" Issue: 337 "OASIS:WorkRequest unclear semantic difference between purpose and classifications" Issue: 336 "OASIS:SystemBreakdownStructure structureRole is a reference in XMI file and should be part property" Issue: 335 "OASIS:ResourceOrder classifications should be a part property" Issue: 334 "OASIS:PropertyValueText classifier should be a part property" Issue: 333 "OASIS: Certification - Template block diagram not exposing all properties" Issue: 332 "OASIS: Warranty - Wrong constraint and cardinality on classification" Issue: 331 "OASIS: Warranty - Add Names property" Issue: 330 "OASIS: Warranty - Template block diagram not exposing all properties" Issue: 329 "OASIS:ActualMission - typo" Issue: 328 "OASIS:StateAssessment multiplicities wrong" Issue: 327 "OASIS:Identifier - merge with Name template" Issue: 326 "OASIS:Project has a mandatory Name and optional Id - should be the other way around" Issue: 325 "OASIS:Organization - add name property" Issue: 324 "OASIS:DirectedActivity- mandatory description property" Issue: 323 "OASIS:ActualMissionItem, typo" Issue: 322 "OASIS:ActualActivity, move text to MUG for Activity" Issue: 321 "OASIS:ActualActivity, suggestion for new wording" Issue: 320 "OASIS:ActualActivity, suggestion for new wording" Issue: 319 "OASIS:ActualActivity, suggestion for new wording" Issue: 315 "OASIS:EventReportItem - incorrect URL" Issue: 314 "OASIS: WorkRequest - Cardinality of triggeredByJustification in BDD" Issue: 313 "OASIS:MeasuredProperty - spelling in valueType property" Issue: 312 "OASIS:Warranty template needed" Issue: 311 "OASIS: Certification template needed" Issue: 310 "OASIS: ResourceOrderDeliveryReceipt - Use new Approval template" Issue: 309 "OASIS: Approval : template needed" Issue: 308 "Invalid XML example data files" Issue: 306 "OASIS:ActualProductUsage Property 'product' definition" Issue: 305 "OASIS:StockItem - property ids should be a Part property" Issue: 304 "OASIS:Identification example data invalid" Issue: 252 "Template test data section should be improved" Issue: 247 "OASIS:DatedEffectivity needs constraint startDate should be before endData" Issue: 228 "OASIS:Contract - some constraints required" Reference Data The following issues have been addressed against the Reference Data: Issue: 218 "create Perceived_probability individual of Context_dependent_property_definition" Issue: 217 "create Risk_level individual of Context_dependent_property_definition" Issue: 213 "Some subclasses of Effectivity in the RDL should be subclasses of assignment" Issue: 212 "supplier reference data required" Issue: 82 "Add classes for Warranties" Issue: 81 "Add class: PersOrgAsg_actual_custodian PersOrgAsg_planned_custodian" Issue: 80 "Add class: Hypothesized_fault_state_assignment" Issue: 79 "Add OWL object: Cost" Issue: 78 "Add class: Activity_resources_removed" Issue: 77 "Add class: Activity_resources_fitted" Issue: 32 "change definition and comment for Approval" General The following general issues have been addressed: Issue: 180 "OASIS Coverpage: bulleted lists" Issue: 179 "Add Property checks" Issue: 178 "OASIS conformance clarity" Issue: 177 "Concept model link broken" Issue: 176 "Overloaded terminology" Issue: 175 "OASIS cover - Introduction para 1" Issue: 173 "Normref hyperlinks should open at top level of browser" Issue: 172 "Incorrect text in the example data section" Issue: 171 "Change of wording in the Template Parametric diagram section" Issue: 170 "No reference to OMG OCL" Issue: 169 "Publication package: dropdown menus behind cover page items" Issue: 168 "Publication package should be consistent wrt dvlp folder files included" Issue: 167 "dex_index_content.html incorrect URL" Issue: 166 "Template: Add a link in the 'Template Block' section to the 'Template Parametric diagram'" Issue: 165 "QA: Check that all template properties are on a parametric diagram" Issue: 163 "Model defnition: Incorrect display of Real properties" Issue: 162 "Common.xsd not copied across into publication package" Issue: 159 "Sort model class definitions" Issue: 158 "Spelling misstake in AAM"
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 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"