Click here to make tpub.com your Home Page

Page Title: Format and Content of DOE-STD-3024-98
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
   
   

 



DOE-STD-3024-98
Since the requirements in this standard have been selected to be most applicable at DOE Hazard
Category 2 nonreactor nuclear facilities, and more specifically to safety systems at those facilities,
further tailoring of the requirements for those systems would generally be inappropriate.
When applying this standard to non-safety systems at nuclear facilities and to systems at nonnuclear
facilities, the graded approach should be employed. Attachment 1 to this standard provides guidance on
these applications. The graded approach considers many factors that must be considered on a case-by-
case basis. These include importance of the facility, remaining facility lifetime, the magnitude of the
hazards involved, the importance of the system, and the complexity of the system. The types and
amount of information contained in an SDD will vary depending on the specific system being described.
Engineering judgement must be used to ensure that appropriate, useful, and necessary information is
provided in the SDD, while avoiding the expenditure of resources to include information that does not
add value to the SDD. The level of effort involved in the development of an SDD will be determined in
part by the availability of current and dependable design information. Attachment 2 to this standard
provides guidance on compiling technical information for preparation of SDDs and may be useful for
existing systems where a well documented design information is not readily available.
Format and Content of DOE-STD-3024-98
Following this introduction, this standard presents the outline for an SDD, followed by guidance on the
technical content of an SDD. Because this standard provides guidance on developing a document, the
technical content guidance sections have been numbered to correspond with the outline of that
document. This formatting is intended to make this standard easier to understand and easier to refer to
later.
This standard and the outline of the SDD have been developed in a style intended to be as user friendly
as possible. The standard and the corresponding SDDs may be read the first time on a straight-through,
cover-to-cover basis, or various sections may be referred to as the need arises. To facilitate this first
reading, certain information is presented early to promote a solid understanding of the information that
follows. Section 1 and Section 2 of the SDD provide preliminary information that is will be
advantageous to understanding the requirements that follow in Section 3. The requirements are
presented first in order to lay the ground work for why the system is designed with certain capabilities
and characteristics. Section 4 then describes how the system meets its requirements.
As used in this standard, the term "requirement" refers to those characteristics that have been
developed, specified, and approved as an output of the design engineering process, and have been issued
by the design engineering authority for the system. These requirements may be contained in documents
such as drawings, procurement specifications, components lists, bills of materials, installation
specifications, and testing specifications. All the engineering considerations behind these issued
requirements are considered the bases of the requirements. Basis information includes specific design
inputs and constraints (for example, functional and performance needs, mandated regulations, codes,
and standards and design procedures), and intermediate products of the design process (such as studies,
analyses, and calculations). The basis for a requirement might address several different considerations.
For example, the bases might include information that indicates that a portion of certain capability was
specified in order to meet the functional requirements that were design inputs, another portion because
of particular regulatory requirements, an additional part of the total capability was to meet certain
general engineering design constraints that might include site-specific engineering policies, standards,
and procedures, and that another part of the total capability was specified as safety margin.
Page ix


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

Integrated Publishing, Inc. - A (SDVOSB) Service Disabled Veteran Owned Small Business