This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
-- GrayBachelor - 25 Jun 2012
Statement of OSLC ALM-PLM Specification coverage for the scenario "Product owner creates a product definition"
| Application topic | Scenario need | How addressed in the Spec as drafted | Notes | Example |
| Product Identity | Add product name | Recommended use of existing property | ||
| Add product unique identifier | Recommended use of existing property | |||
| Add a formal enterprise product identifier | Not adddress directly | Can be adopted from AP239 | ||
| Create coding and classification | Add relevant product families | Not adddress directly | Can be adopted from AP239 | |
| Add organisational ownership and contacts | Created and modfied by are addressed in OSLC Core | |||
| Add classification terms from enterprise catalog | Not adddress directly | |||
| Add classification or identification tags | Minimal support via resource type of Product | |||
| Define lifecycle state and control codes | Set initial lifecycle state | Not adddress directly | ||
| Add lifecycle indication codes | Minimal support via created and moodified | |||
| Define and or add lifecycle state processing rules | Not adddress directly | |||
| Define product capabilities and qualities | Add capabilities, features, functions or descriptions e.g. from a catalog | Not adddress directly | Can be adopted from AP214, 239 | |
| Add a reference to some market need or demand that this product is aimed to address | Support via link a to Requirement. | Multiple options for link type | ||
| Add variant parameters which will condition the product capabilities | Not adddress directly | Example provided | ||
| Add some variant expressions that define combinations of capabilities | Not adddress directly | Example provided | ||
| Associate variant parameters and variant expressions with capabilities, demands or descriptions | Support via link a to Requirement. | |||
| Define product compositional structure | Add or define compositional types | Composition support via resource type of view | ||
| Add other products as components to compositional structures | Product view resource links in Product view resource | |||
| Add other structures e.g. document structures | Links in Product view resources can be any resource type | |||
| Define variant processing to compositional structures | Add variant expressions at some product family or product compositional level or item | |||
| Add variant expressions at some product content level e.g. Assembly, Component | ||||
| Define variant expressions for re-use independent of product | ||||
| Define approvals | Add or define approval needed requests-overall and sectional | |||
| Approve product definitions | ||||
| Define workflows | Add or define workflows | |||
| Associate information with a product | Add or define product information associations | |||
| Define events | Add or define event | |||
| Add or define subscriptions to events | ||||
| Add of define notifications based upon subscriptions to events |
This topic: Main > PlmHome > PlmMeeting180612 > StatementOfSpecApplicationCreateProduct
Topic revision: r1 - 25 Jun 2012 - 14:57:38 - GrayBachelor
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback