Cart
0
Product
Products
(empty)
No products
To be determined
Shipping
$0.00
Total
Product successfully added to your shopping cart
Quantity
Total
There are 0 items in your cart.
There is 1 item in your cart.
Total products
Total shipping
To be determined
Total
Reduced price!
View larger
View larger
IEEE 805
New product
IEEE 805 84th Edition, January 1, 1984 Recommended Practice for System Identification in Nuclear Power Plants and Related Facilities
More info
Description / Abstract:
This recommended practice provides a single source of nuclear power plant system descriptions which, along with related recommended practices concerning unique identification principles and definitions, component function identifiers, and implementation instructions, makes up a concept for uniquely identifying systems, structures, and components of light water nuclear power plant projects (electric power generating stations) and related facilities. Fossil, hydro, and other types of power plants are not included in this edition.
Purpose.
The purpose of this series of recommended practices is to present a common language of communication which will permit a user to correlate a system, structure, or component with another organization for the purposes of reporting, comparison, or general communication. It does not require a using organization to change its own internal identification concept, but if the organization chooses to do so it has only to transcode at the interface from their internal language to this common language concept.
The user may choose to adopt this concept for internal organizational use. It represents the accumulated practice of the industry assimilated into one set of practices. A significant feature of this concept is that the unique identification code identifies the function at the component level and not the hardware itself.
Purpose.
The purpose of this series of recommended practices is to present a common language of communication which will permit a user to correlate a system, structure, or component with another organization for the purposes of reporting, comparison, or general communication. It does not require a using organization to change its own internal identification concept, but if the organization chooses to do so it has only to transcode at the interface from their internal language to this common language concept.
The user may choose to adopt this concept for internal organizational use. It represents the accumulated practice of the industry assimilated into one set of practices. A significant feature of this concept is that the unique identification code identifies the function at the component level and not the hardware itself.