Product Key Customer Benefits
Implement program-specific rules to various aspects of product development to avoid ambiguity and error, considering that development activities might be shared between many entities (supplies, contractors, etc). The ability to customize a product life cycle contributes to better program management. For instance, the development cycle for prototypes is usually shorter than the cycle for products already in production.
- Manage several programs simultaneously
Use program milestones to configure products to minimize any complexity associated with program dynamics. Program milestones can be defined to represent dates or product units. For instance, a program can be defined to contain 3 milestones (design, testing, manufacturing) where each milestone represents a set of dates (design=01/01/02 - 12/31/02, testing=01/01/03-06/01/03, manufacturing=06/02/~ ). The milestones' values (actual dates and product units) can be changed easily during a program shift without impacting any of the effectivities that have been applied on parts and assemblies in a product structure.
- Manage program shifts with ease
This separation is necessary for satisfying a wide array of corporate change processes and maturity modeling requirements. A life cycle specifies WHAT should be done to successfully mature an object (part, document, etc.) to its final stage. It should be separated from workflow and other task management applications that specify HOW the work is to be done even though their usage is usually integrated within a business process. For instance, completion of a engineering change release workflow usually dictates a change in status of the object (part, product, etc.) to "release".
- Separate object life cycle from task-oriented workflow definitions