--
GrayBachelor - 18 Jun 2012
Product owner creates a new Product
This scenario is aimed at assisting the clarification and validation the use of the proposed OSLC specifcation by taking the basic case of creating a product
Business Context
Product management owners or systems architect/engineers responsible for product definition need to create a new product, which either is a software product or contains software constituents.
Today it takes too much time and effort to build up and check a unified ALM-PLM product definition that succefully meets process criteria, which may well be changing due to innovation in the products themselves and processses usedto handle them.
Typical improvement goals are to reduce the time to create accepted product definitions, thereby sincrease efficiency, reduce errors and rework.
Scenario entry points
There are multiple potential entry points for product creation, for example
- to make a new product as a member of a product family perhaps a varaint to an existing family member or hosted by a family (e.g. as an accessory)
- to make a new product from defined capabilities or qualities
- to make a new product from an existing product or variant (In many industries this may be 80% of product creation cases)
- to create a product from scratch (In many industries this may be 20% of product creation cases)
In general some combinatrion of the above issued, this is the overall aim of this scenario. The cost of product content over the lifecycle trend to increase re-use.
Scenario Outline
Create a basic product identity
Add product name
Add product unique identifier(may be a temporary or an alias)
Add a formal enterprise product identifier (typically requires approval to allocate a number from the enterprise register
Note: Its is assumed that already this basic product is under version control
Create coding and classification
Add relevant product families
Add organisational ownership and contacts
Add classification terms from enterprise catalog
Add classification or identification tags
Define lifecycle state and control codes
Set initial lifecycle state
Add lifecycle indication codes e.g. prelimary, not for sale
Add lifecycle state processing rules e.g. for transition to next stage
Define product capabilities and qualities
Add capabilities, features, functions or descriptions e.g. from a catalog
Add a reference to some market need or demand that this product is aimed to address
Add variant parameters which will condition the product
Add some variant expressions that define combinations of capabilities such as governed by variant parameters
Associate variant parameters and variant expressions with capabilities, demands or descriptions
Define product compositional structure
Add or define compositional types e.g. bill of materials, system assembly
Add other products as components to compositional structures e.g. products, documents, artefacts
Add other structures e.g. document structures
Define variant processing to compositional structures
Variant processing enables conditional content specification - i.e. Boolean to include, exclude, set the number of items, set dependencies or mutual exclusivity
Add variant expressions at some product family or product level
Add variant expressions at some product content level e.g. Assembly, Component
Define variant expressions for re-use independent of product
or some combination