Specification Template Lifecycle

A Specification Template 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 Template cannot be changed directly; it can only be promoted/demoted via the connected SCO.

Only Template Administrators and Specification Office Managers can create Specification Templates.

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 Template. For example, if the SCO is promoted from the Draft state to the Peer Review state, the Specification Template, also in the Draft state, will be promoted to the Peer Review state. A separate SCO is needed to promote a Specification Template from the Approved 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 Approved Specification Template.

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

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

Draft

This is the initial state for a new Specification Template.

Peer Review

This state is controlled by the SCO.

Formal Approval

This state is controlled by the SCO.

Approved

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

Obsolete

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