Specification Change Order Lifecycle

A Specification Change Order (SCO) is processed by moving it through the states in its lifecycle. Specification Managers, Template Administrators and Specification Office Managers can create SCOs.

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.

The following describes the states included in the SCO lifecycle:

Draft

To promote the SCO to the Peer Review state, at least one Approver List must be connected to the SCO. A Reviewer List may be connected to the SCO. If a Reviewer List is not connected to the SCO, the user will be presented with a warning message, but the SCO will still be promoted to the Peer Review state.

Peer Review

Reviewers listed on the Reviewer List must review, comment on, and approve the SCO in this lifecycle state. Once all assigned reviewers have approved the SCO, it is automatically promoted to the Formal Approval lifecycle state.

The owner of the SCO may also manually promote the SCO to Formal Approval without a completed Peer Review route.

Formal Approval

Reviewers listed on the Approver List must review, comment on, and approve the SCO in this lifecycle state. Once all assigned reviewers have approved the SCO, it is automatically promoted to the Final Check lifecycle state.

Final Check

The owner, or a co-owner, of the SCO reviews the information provided in the SCO and can promote the SCO to the Approved lifecycle state.

Some installations may use a default setting for Specification Central that bypasses the Final Check lifecycle state. In this case, once the Formal Approval state is completed, the SCO is promoted to the Approved state.

Approved

This lifecycle state indicates that the SCO has completed all lifecycle states.