Previous Document Next Document Show Current Location in Contents

Specification Lifecycle

A Specification, or Technical Specification, is processed by moving it through the states in its lifecycle. This is done automatically by the system via the promotion of the connected Specification Change Order (SCO). The lifecycle for a Specification cannot be changed directly; it can only be promoted/demoted via the connected SCO.

Only Specification Managers and Specification Office Managers can create Specifications.

If the item is in a route, the route can be set up to prevent the item from being promoted until the route is complete. If there is a route that is blocking the promotion of the item, the Lifecycle page displays in the arrow that points to the next state.

Listed below is a table that shows how the lifecycle states for an SCO will determine the state for the Specification. For example, if the SCO is promoted from the Draft state to the Peer Review state, the Specification, also in the Draft state, will be promoted to the Peer Review state. A separate SCO is needed to promote a Specification from the Issued state to the Obsolete state. Therefore the final row in this table shows how the automatic promotion to Obsolete occurs when the SCO applies to an already Issued Specification.

Object
Lifecycle States
Specification Change Order (SCO)
Draft
Peer Review
Formal Approval
Final Check
Approved
Specification (New)
Draft
Peer Review
Formal Approval

Issued
Specification (Already Issued)
Issued



Obsolete

The following describes the states included in the Specification lifecycle as driven by the connected SCO. For details, see Specification Change Order Lifecycle.

Draft

This is the initial state for a new Specification.

Peer Review

This state is controlled by the SCO.

Formal Approval

This state is controlled by the SCO.

Issued

This state is controlled by the SCO. When the connected SCO is Approved, the system automatically promotes the Specification to Issued.

Obsolete

This state is controlled by the SCO. A separate SCO is required to move a Specification from the Issued state to the Obsolete state. Once the SCO is promoted to the Approved state, the Specification will automatically be promoted to the Obsolete state.

Previous Document Next Document Show Current Location in Contents

Last updated: 04/22/04 17:05:20