Quantcast Reviewing Design Requirements cont'd - doe-std-1073-20030029

 

Click here to make tpub.com your Home Page

Page Title: Reviewing Design Requirements cont'd
Back | Up | Next

Click here for thousands of PDF manuals

Google


Web
www.tpub.com

Home

   
Information Categories
.... Administration
Advancement
Aerographer
Automotive
Aviation
Construction
Diving
Draftsman
Engineering
Electronics
Food and Cooking
Logistics
Math
Medical
Music
Nuclear Fundamentals
Photography
Religion
   
   

 

Share on Google+Share on FacebookShare on LinkedInShare on TwitterShare on DiggShare on Stumble Upon
Back
Reviewing Design Requirements cont'd - doe-std-1073-20030028
Up
Configuration Management - index
Next
Using System Design Descriptions


DOE-STD-1073-2003
Configuration Management
operating and design pressures and temperatures,
component input and output design requirements (e.g., pump net positive suction
head and power requirements),
design procedure documentation,
inspection acceptance criteria,
documentation of hydrotest parameters and results,
maintenance and testing procedures, and
quality assurance requirements.
Tools for assessing accuracy include:
checks of reasonableness by competent design personnel,
checks to determine whether the design requirements apply to current physical
configuration, and
independent verification of critical calculations and analysis.
In determining whether the design requirements are properly documented, the team
should consider whether:
the design information is clearly identified;
the design requirements are differentiated from the design basis;
safety, environmental, and mission design requirements are differentiated from
other types of design requirements; and
the design documentation is indexed, integrated, and usable.
The contractor must document, retain, and maintain the team's conclusions and the basis
for the conclusions regarding the adequacy of the facility design requirements in a
retrievable form. The documentation should indicate the relevant design information by
system and an index of design documents should be provided.
At the conclusion of this effort, the team must decide if any of the still missing
information is truly critical to safe and effective configuration management. If the
information is not critical, then the contractor should not invest additional resources in
recovering the information at this time. If major construction or modification is
performed on the system at a later date, the design information should be developed at
that time. If the conclusion of the team is that the design requirements and their design
basis are not adequately documented, complete, or accurate and additional information is
critical to ensure safe and effective configuration management, then the team must
develop a plan to recover that information. If the missing information is necessary to
support the safety or authorization basis, then the missing information must be retrieved
or regenerated. If the team concludes that a design reconstitution is recommended, the
team should develop and document specific recommendations for that effort.
Appendix D provides additional information on regeneration and recovery of design
requirements.
3-11


Privacy Statement - Press Release - Copyright Information. - Contact Us

Integrated Publishing, Inc.