Design Bases Rules PDF Print E-mail

Definition:

A Design Bases Rule is a statement that specifies or bounds a group of regulatory or non-regulatory requirements that will be included within the Configuration Management System (CMS).


The Design Bases Rules for a given CMS, collectively called the Design Bases Rule Set, ultimately determine which requirements must be managed within the CMS. Each Design Bases Rule is crafted to include and exclude specific requirements within the CMS. Since Design Bases Rules determine what design requirements must be managed, they determine the scope of the managed information, and consequently the cost of back-fitting the Configuration Management System to legacy plants.

Each requirement included in the Configuration Management System must reference an associated Design Bases Rule to justify its inclusion.



Example 1:

The CMS shall include requirements from Title 10, United States Code of Federal Regulations, Part 50, Appendix A.

Example 2:

The CMS shall include requirements taken from generally accepted industry codes and standards, such as IEEE, ASME, ASTM, and AISC standards.

Example 3:

The CMS shall include requirements taken from the owner’s economic goals for the nuclear plant that are stated in the contract between the Owner/Operator and Architect/Engineer (Contract No. xxx, dated xxx).

Example 4:

The CMS shall include requirements taken from non-regulatory requirements that are specified in the contract between Owner/Operator and Architect/Engineer (Contract No. xxx, dated xxx).
 

Online Now

None

Tell a Colleague

Click here to notify your associates about this site.
Copyright © 2010. Nuclear Open Configuration Management Alliance. Designed by interLogic, inc. and Shape5.com