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 803
New product
IEEE 803 1983 Edition, January 1, 1983 Recommended Practice for Unique Identification in Power Plants and Related Facilities - Principles and Definitions
More info
Description / Abstract:
This recommended practice provides a single source of unique
identification principles and definitions which, along with related
recommended practices concerning component function identifiers,
implementation instructions, and system descriptions, make up a
concept, entitled the Energy Industry Identification System (EIIS),
for uniquely identifying systems, structures, and components of
nuclear and fossil fueled power plant projects (electric power
generating stations) and related facilities. Hydro and other types
of power plant projects are not included in this issue.
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 their own internal identification concept, but rather they have only to transcode at the interface of their organization from their internal language to this common language concept.
The users may, if they so choose, adopt this concept for their internal 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 their own internal identification concept, but rather they have only to transcode at the interface of their organization from their internal language to this common language concept.
The users may, if they so choose, adopt this concept for their internal 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.