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
.
TWiki
>
Main Web
>
PlmHome
>
PlmScenarioProductOwnerCreatesProduct
(25 Jun 2012,
GrayBachelor
)
(raw view)
-- Main.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 ---++++++ <a name="Business_Context" title="Business_Context"></a> 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. ---++++++ <a name="Scenario_Outline" title="Scenario_Outline"></a> Scenario Outline Create a basic product identity <blockquote> 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 </blockquote> Note: Its is assumed that already this basic product is under version control Create coding and classification <blockquote> Add relevant product families Add organisational ownership and contacts Add classification terms from enterprise catalog Add classification or identification tags </blockquote> Define lifecycle state and control codes <blockquote> Set initial lifecycle state Add lifecycle indication codes e.g. prelimary, not for sale Define and or add lifecycle state processing rules e.g. for transition to next stage </blockquote> Define product capabilities and qualities <blockquote> 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 capabilities e.g. its functions or capacities 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 </blockquote> Define product compositional structure <blockquote> 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 </blockquote> 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 <blockquote> Add variant expressions at some product family or product compositional or item level Add variant expressions at some product content level e.g. Assembly, Component Define variant expressions for re-use independent of product </blockquote> or some combination Define approvals <blockquote> Add or define approval needed requests-overall and sectional Approve product definitions (partial or overall) </blockquote> Define product related workflows <blockquote> Add or define workflows </blockquote> Associate information with a product (can be associated with any of the above product definition <blockquote> Add or define product information associations </blockquote> Define events and event handling <blockquote> Add or define events Add or define subscriptions to events Add or define actions e.g. notifications associated with subscriptions to events </blockquote> ---++++++ Scenario process support note The above list of activities and results are executed variously in sequences, combinations and revisited multiple times during the life of a product definition. For add/define include remove, change etc.
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 25 Jun 2012 - 13:54:40 -
GrayBachelor
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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