Control and Tracking - s1073pt10029

DOESTD107393

1.3.3.3 Control and Tracking

Only the currently-approved revisions of documents within the CM program should be used. Revisions

to documents within the CM program to incorporate pending changes should be completed in a timely

manner. The number of unincorporated document changes allowed to accumulate before revisions

are implemented should be determined according to the priority of the document, the complexity of the

changes and the overlap of the changes. For each document within the CM program, the following

information should be readily available: revision level, current status, document owner, information

regarding pending changes, and other data necessary for control and tracking, such as storage

location and outstanding document change notices (DCNs).

1.3.3.4 Retrieval

Documents should be retrieved in a timely manner upon request. Maximum retrieval times for each

document should be established, and they should be based on the priorities established by the

document owners. Documents should be identifiable from a document database, which should be able

to identify documents within the CM program related to particular SSCs, types of SSCs, technical

topics, and other information to support identification, such as SSC vendors. When a copy of a

document within the CM program is issued, pending changes and associated information should be

identified.

The objective of the change control element is to maintain consistency among the design requirements,

the physical configuration, and the facility documentation as changes are made.

1.3.4.1 Identification of Changes

All mechanisms that can lead to temporary or permanent changes in the design requirements, facility

configuration, or facility documentation within the CM program should be identified. Such mechanisms

might include hardware modifications not controlled as projects, hardware modifications controlled as

projects, maintenance changes, operational changes, procurement changes, document changes, and

computer software changes. Change mechanisms should be evaluated to determine which are

adequate as is, and which need to be improved, consolidated, or terminated. The resulting change

mechanisms should be integrated with the CM program. Within approved CM change mechanisms,

each proposed change, including temporary changes and partially implemented changes, should be

described sufficiently to support technical reviews, management reviews, and approvals.

1.3.4.2 Technical Review of Changes

Each specific proposed change should be reviewed to determine if it is within the bounds of the design

requirements. Changes to the design requirements should be evaluated and approved by the design

authority prior to implementation. The technical reviews should evaluate safety, environmental, and

mission impacts; determine appropriate post-implementation acceptance criteria; and identify the

affected SSCs and facility documentation.

1.3.4.3 Management Review of Changes

Before implementation, management should review proposed changes (including those that do not

involve a change to design requirements) to verify that the technical reviews have been performed

adequately, that the change package is complete and ready for implementation, and that any external

I-9