Maintenanceand Control of Design Information Summaries

DOESTD107393

the design requirements, not the basis for the requirements. Thus, field validation concentrates

almost exclusively on the design requirements. Design basis may be referred to for the resolution of

open items and conflicts between the design requirements and either the physical configuration or the

facility documentation.

Field validation is done on DISs rather than on raw design information for the following reasons: the

design requirements are fully reconstituted, complete, and accurate; sufficient time has been allowed

for reconstituted design requirements to be reflected in the physical configuration and configuration

documents; design basis reconstitution represents an extra validation of the design requirements; the

DIS is a user-friendly compilation of the design requirements, sorted by system and topic and

differentiated by type; and DIS issuance is the final step in overall CM program development. With the

issuance of DIS Revision 1, the facility needs to be confident that the DISs are complete and accurate

and that the CM program basic relationships are established. From this point on, the CM program

focuses primarily on maintaining these relationships.

Field validation does not take the place of initial reconcilement of design requirements, physical

configuration, and configuration documentation. As design requirements are reconstituted, they should

be released and forwarded through the established change control and document control processes.

Open items and discrepancies identified as the reconstituted design requirements are released should

be resolved long before field validation. Field validation is the final check that everything is consistent.

Every DIS should have some degree of field validation. The first several should receive full validation,

similar to a vertical-slice assessment. Reduced-scope field validations may be acceptable for later

DISs if the results of the initial validations are positive. Section 2.5 provides guidance on the

performance of vertical-slice assessments and DIS field validation.

3.6.8 MAINTENANCE AND CONTROL OF DESIGN INFORMATION SUMMARIES

The DR program should establish the DIS maintenance and control procedures. Once the DISs are

complete and the maintenance and control procedures are in place, maintenance and control of the

reconstituted design information are integrated into the normal CM program work activities. The design

requirements element is responsible for establishment and maintenance of the design requirements

and design basis; the document control element, for the control of documents within the CM program.

Typically, the design authority would be assigned ownership of the DISs that are to be controlled in

accordance with CM document control element. Thus, the design authority would ensure both that the

design information is current and accurate and that the DIS is current and accurate.

Maintenance and control are necessary to ensure that the DISs retain their value as a reference tool for

facility activities. Document controls applicable to DISs should be comparable to those for the SAR.

Supporting information, computer software, and other DIS references should also be appropriately

controlled.

Examples of appropriate controls would include publishing notices of page changes, updating the

databases at the time of such changes, and incorporating the changes annually into the DISs. (if the

number or complexity of outstanding change notices were significant, incorporation into the DISs would

be accelerated.) The DISs should be reviewed and reissued (e.g., every 2 to 5 years on a staggered

schedule, and more often for highly modified and safety-significant DISs) to ensure that they continue to

meet facility needs and do not become obsolete.

Ready availability to users is essential for the DISs. Facilities should consider establishing information

systems featuring centralized information control and user access from convenient terminals. The

most effective information retrieval systems have the following attributes: convenient locations, simple

II-81