Introduction and overview of the proposed PLM extensions

A set of PLM extensions has been identified and is proposed for adoption.

Find attached a working summary of the extensions, including an introduction and overview of examples being built up around Lyo.

Your comments and feedback is welcome.

Timetable

The PLM Workgroup roadmap has been published and the aim is to agree a first set of PLM extensions during 4Q2011.

The extensions will be presented to the OSLC Core workgroup on October 5th.

The weekly working meetings of the OSLC PLM workgroup will progressively address feedback and build out examples to support topics raised and to assist prototyping.

Summary of the proposals

The proposals consist of extensions proposed for any OSLC resource as "Core extensions" and an specification for Product resource types.

We will layout the Core extensions, to promote the discussion and clarification we have started a PLM Specification based on the OSLC CM 2.0 Spec which is itself based on Core 2.0.

You can see the application of the Core extensions to RM in the supporting detailed material below.

New draft Experimental PLM Specification

New A draft Specification for PLM Resource exterimental is being prepared. Initially as a document. A wiki structure will be assembled to support it.

Attached below. Last update Oct 11th 2011.

Open items:

Presentation of the Spec

1. Layout for the Product, Product Version and Product View

Spec Content

1. Description of the Application ID

2. Agreement and description of Variant Expression as an anotation. An alternative approacxh is Variant properties and Variant property expressions

Not addressed

1.Coding and classification
2. Alias / alternative names
3. Lifecycle states
4. Change notification
5. Approvals

Detailed supporting material for the proposals

The detailed description of the PLM extensions, with RM examples, is available on the PLM spec extension page

See below for additional examples are shown in the backup materials.

How to provide feedback

You are welcome to add comments here, or add an attachment or use the community mailer - your comments are welcome !

Regarding the notion of "replaces" in the description of version...Is that just to get at the idea of "next version" (so you get the chain of revisions by following"replaces" back to a resource that only has "isVersionOf" and then back to a resource that does NOT have "isVersionOf" which is the base?)...or is it to deal with the notion that a version of a part may be replaced by a version of some other part with the same fit and function?

Example: We have two base resources that are fans from different manufacturers that go on various boards. We (a company that has enough clout with our supplier) recognize that one of them could replace the other, maybe with just a small modification. So a version of the fan from manufacturer A that was used in several products will no longer be used, instead a version of the fan from manufacturer B will replace it and we don't have to carry both in inventory. If that's what "replaces" means, that will fail the test proposed, cause the base resource of the replacement is different from the base resource of what it replaces, but the specific version of one can replace a version of the other.

-- AndyBerner - 05 Oct 2011

Replaces is to refer to product changes, i.e. revisions . The example is more of an alternative product - which is not covered today. Anyway its all about clarifying terms and scope of the Spec

-- GrayBachelor - 11 Oct 2011