Review and Upgrade of Existing Document Control Processes

DOESTD107393

Identify document types used at the facility.

Determine which document types should be in the CM program.

Determine which specific documents should be in the CM program.

First, a complete survey of document types in use should be conducted with support of the various

organizations at the facility. Each organization should identify the document types it prepares and the

important document types it uses. Document types identified during the initial assessments should

also be addressed.

After document types are identified, a document owner should be assigned to each document type.

The natural document owner is the person or organization responsible for developing and revising the

technical content of documents within the assigned document type. The owners should review the

document types for which they are responsible to identify those important for supporting the CM

program objective and criteria. They should then perform an importance evaluation In light of their

experience with, and knowledge of, the document types. Document scope criteria may vary according

to the importance of the SSCs involved. These criteria should be defined to include only those

document types that support the design or operation of facility SSCs included In the CM program.

Document types that reflect the facility's design requirements and those that are necessary for day-to-

day operation should receive the highest priority for inclusion in the CM program.

Finally, the document owners, with the assistance of those persons responsible for the document

retrieval function, should identify the individual documents within each document type and determine

which of these documents should be included in the CM program. To accomplish this, a determination

should be made as to whether that document supports an SSC that is included in the CM program.

The CM program equipment scope criteria and the specific list of SSCs within the CM program, if

available, should be provided to the document owners for support in their evaluation. For example, if

Quality Receipt Inspections were a document type to be included in the CM program, it would not be

necessary to include inspections that pertain to equipment not included in the program. The intent is to

include only those documents necessary to support configuration management. Documents specifying

requirements for day-to-day operations (e.g., procedures, drawings, vendor-supplied documents) and

those necessary for modifying the facility (e.g., design requirements, design calculations, accident

analyses) should be Included. If there is any doubt, the document should be included in the CM

program. It may be advantageous to coordinate this activity with the design reconstitution document

searches described in Section 3.2.

After identification of the specific documents for inclusion in the CM program, the following information

on each document should be recorded in the document databases to facilitate tracking and control:

document type, unique document number, and document uses and priority. This information should be

retained. Selected document information (e.g., SSC-specific drawings, procedures, and vendor

information) should also be entered into the CM equipment database to establish a cross-reference or

link between SSCs within the CM program and the associated documents.

2.3.1.2 Review and Upgrade of Existing Document Control Processes

For each document type to be included in the CM program, the adequacy of the existing document

control process should be evaluated against each of the basic document control functions. A survey of

existing document control processes should be conducted to identify the process that either identifies,

stores, controls, tracks, or retrieves the included document types. After the document control element

is developed, documents within the CM program should be processed in a manner consistent with the

model shown in Figure 211, as discussed in more detail in Section 2.3.2.

II-32