SAE EIA836 Rev B

The primary focus of this standard is information of interest to Configuration Management (CM) practitioners related to the performance of CM functions as products are conceived, proposed, defined, developed, produced, operated, maintained, modified, and disposed. This information is stored when generated and, from time to time, must be moved or shared with others.

This standard, through the use of the Data Dictionary, defines real world things of interest to the CM practitioner, which are the foundation of the following CM functional areas, and are needed for effective data exchange and interoperability:

• Configuration Management Planning and Management
• Configuration Identification
• Configuration Change Management
• Configuration Audit
• Configuration Verification
• Configuration Status Accounting

The Data Dictionary [21] defines terms that are used to define these objects of interest, which are listed below. Some of terms are considered to flow from applying CM principles or performing CM functions and are designated as part of the CM domain. Others, while important to CM, are designated as being a part of other domains.

This standard is an industry consensus standard and, as such, is intended to serve as a guidance document. The information provided in this standard may be used in the preparation of solicitations, requests for proposals, contracts, and business partner agreements.

Several possible avenues can lead to the application of this standard, or parts thereof. A procuring organization may reference this standard within a solicitation or request for proposal. Alternatively, the procuring organization may specify or recommend use of industry best practices and/or published guidelines that, in turn, recommend this standard.

Some of the benefits of this standard are as follows:

• This standard provides definitions and relationships for all CM objects and a cross-reference to their sources. It is a primary source for CM data element definitions to be included in systems and standards development such as GEIA-927, and in vendor development of improved CM tools.
• A CM practitioner could take any of the CM objects and turn them into a contract requirement for data. Take, for example, ChangeBoardMinutes. Its content could be referenced as a data requirement in a contract.
• The Data Dictionary defined in this standard can be used as a common (canonical) standard to which multiple trading partners can map for interoperability and data exchange.
• The Data Dictionary can be directly transformed into a data exchange schema language, such as World Wide Web Consortium XML Schema Language, and used to specify and validate data exchanges. This can result in a significant product life cycle cost reduction. (See Reference Schema [375] and How to Use EIA-836 to Exchange Data [425].)