Appendix II-D Content of Design Information Summaries

DOESTD107393

APPENDIX IID

CONTENT OF DESIGN INFORMATION SUMMARIES

There are many different design information summary (DIS) formats that adequately present the

needed information. This appendix presents an acceptable format and discussion that may be useful in

establishing facility-specific DIS formats. This appendix also discusses DIS benefits.

The following discussion focuses on a system DIS. Format and content for a topical DIS can be

developed using this general guidance. The following general format could be adopted for a system

DIS:

System Description

Operability Requirements

System Design Requirements

System Design Basis

Component Requirements and Basis

Design Topics

Additional Information

This format captures the recommended DIS contents and organizes them into a user-friendly format.

This format has the fundamental attribute of starting with basic and going into increasing levels of detail.

Component-level design considerations are separated from system-level design considerations.

Certain design topics (such as operations, maintenance, and testing requirements) are separated from

other design considerations to provide focused attention for the end-users.

DISs should use the matrix approach, which makes significant use of text material but references key

supporting design process documents. The text includes system descriptions and drawings, operability

requirements, system functions, component information, system and component design basis,

regulatory requirements, and DOE commitments. Referenced documents should include calculations

and analyses, codes and standards, design practices, procurement specifications, and TSR. It is

unnecessary to duplicate the content of other self-contained documents such as ASME code stress

reports, environmental qualification data packages, vendor manuals, operations and maintenance

procedures, industry codes and standards, specifications, generic regulatory requirements, and

calculations.

The following discussion provides the information that should be included in each DIS section. The

type of information included in the DIS should be directly related to specific user needs in support of the

overall program objective. DISs are written for a variety of users and experience levels. DIS users will

range from operations, maintenance, testing, procurement, training, and QA personnel to design

engineers. DISs should be tailored to meet individual facility needs and constraints, making use of

existing programs and results.

SYSTEM DESCRIPTION

This information provides general background and introduction regarding the DIS's subject. To avoid

reliance on current experience levels, DISs should be written for a hypothetical 3-year engineer. Such

an engineer (or scientist) would have a general facility background, would know the facility layout, and

would know the general actions the system needs to perform. The descriptive information for a system

DIS could be presented in the following DIS sections:

II-D-1