EIA-836 Version 10.doc

EIA Standard 836 CM Data Exchange and Interoperability 15 June 2002 EIASTANDARDConfiguration Management Data Exchange and InteroperabilityEIA 836JUNE 2002ELECTRONIC INDUSTRIES ALLIANCEGOVERNMENT ELECTRONICS AND INFORMATION TECHNOLOGY ASSOCIATIONENGINEERING DEPARTMENT A SECTOR OFEIA 836NOTICEEIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or nonmember of EIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Publications preclude their voluntary use by those other than EIA members, whether the standard is to be used either domestically or internationally.Standards and Publications are adopted by EIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, EIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication.This EIA Standard is considered to have International Standardization implication, but the International Electrotechnical Commission activity has not progressed to the point where a valid comparison between the EIA Standard and the IEC document can be made.This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use.(From Project Number 4763, formulated under the cognizance of the GEIA G-33 Data and Configuration Management Committee.)Published byELECTRONIC INDUSTRIES ALLIANCE 2002Technology Strategy & Standards Department2500 Wilson Boulevard,Arlington, VA 22201PRICE: Please refer to the currentCatalog of EIA Electronic Industries Alliance Standards and Engineering Publications or call Global Engineering Documents,USA and Canada (1-800-854-7179) - International (303-397-7956)All rights reservedPrinted in U.S.A.AcknowledgementEIA-836 development was a collaborative effort involving several GEIA member organizations and the Department of Defense. It was initiated in January 2000, at the request of OSD (AT&L) to replace MIL-STD-2549. The EIA-836 project was undertaken by the G-33 (Configuration and Data Management) Committee, with the expressed purpose of expanding its scope to cover a wide spectrum of industry, and to view Configuration Management functions and data elements from an industry perspective. The EIA-836 Working Group consisted of representatives from Boeing, Lockheed Martin, Northrop Grumman, Raytheon, Rockwell Collins, SAIC, ManTech, MLR Associates, Trident Systems, US Army, and OSD(AT&L). Other GEIA Systems, Standards and Technology Committees that interfaced with the project are G-47 (Systems Engineering), and the Information Technology and Integration Committee. An Oversight Group providing advice and council to the Working Group included representatives from major contractors and other associations such as the Aerospace Industries Association (AIA). Support and funding for this project came from DoD, and from the ManTech Enterprise Integration Center in Fairmont, West Virginia, without whose support this effort could not have been completed. Funded effort was augmented by a great deal of voluntary participation by committee members and other interested parties. With apologies to anyone inadvertently left out, the following individuals (in alphabetical order) contributed to the success of the EIA-836 project during its 2-1/2 year life cycle:Adams, MarkPortal DynamicsLeavitt, Merv*OUSD(A,T&L)Baroni, LindaManTechMayers, JoeMulkerin AssociatesBichel, BillBoeingMoody, RussSAICBooker, GayleUS ArmyMystkowski, JoeNorthrop Grumman Crawford, JamesLMCONaclerio, PeteBoeingDesiderio, GeorgeOUSD(AT&L)Newlon, RobertBoeingElley, GordonNorthrop-GrummanNey, GordonUS ArmyForbes, JimLMINoble, Don LMCOFox, DickMatrix OneOlson, SteveSystems Mgt & IntegrationFrench, SteveUS ArmyParks, TomLMIGilds, DennyRockwell-CollinsParry, TomOUSD(AT&L)Hall, DonDLA/ DEBPOPierson, PaulLMCOHamm, ErnieCH2MHILL, Hanford Group, Inc.Reber, JohnTrident SystemsHauer, CynthiaMillenium DMRickenbaugh, JimNCCIMHoward, GeraldUS ArmyRitter, Bill LMCOJohnson, DavidAIAKohl, RonITIKidwell, RobertManTechSadauskas, LeeUS ArmyKlebba, MikeTRWSchuldt, RonLMCOKohl, RonITISpahle, MichaelHoneywell Kreiler, Chris CACIStarkweather, WayneRaytheonLager, Alan*MLR Associates * Co-chairsPage Intentionally BlankContentsClick on any entry Foreword (Informative)1Introduction (Informative)21. Scope31.1Scope of the Standard31.2 Overview of the Standard32.References63. Definitions84. Symbols and Abbreviations104.1 Symbols104. 2Abbreviations105.CM Business Objects11Business Object Header125.1CM Planning and Management Business Objects13Action Item Status Report135.2Configuration Identification Business Objects13Interface Document List13Release Record14Tracking Identifier Assignment Record15Hardware Product Detail Record16Software Product Detail Record16Facility Product Detail Record16Process Detail Record17Product Definition Information Set175.3Configuration Change Management Business Objects17Request For Change18Request For Variance18Change Proposal19Change Directive24Document Revision Notice25Change Commitment Record27Change Implementation Plan275.4 Configuration Status Accounting Business Objects28Change Process Status Report28Product-Material Usage Report31Installation Completion Record32Change Incorporation Report33As Designed Status Report34As Built Status Report35As Maintained-Modified Status Report365.5 Configuration Verification and Audit Business Objects37As Designed As Built Reconciliation Report37Configuration Audit Report385.6 Data-Document Management Business Objects38Document Comment Record38Document Transfer405.7 General Business Objects40Manufacturing Plan40Modification Instruction42Modification Kit Validation Report42Product Delivery-Acceptance Record43Kit Shipment Report446. CM Data Dictionary45EIA-836 CM Data Dictionary456.1 Data Dictionary Content456.2Data Element Naming Conventions457. CM Reference Schema Description497.1Core Components49Address50ChangeControlAuthorityIdentification50Copyright50Data Rights51DateTimeGroup51Distribution Restriction52Document Identification Group52Document Identification52Document Representation53Effectivity54Entity55Export Control55Facility Identification55File56License Agreement56Organization57Packaged Product57Part-Material Identification58Patent58Person58Postal Address59Product Identification59Product Instance59Product Protection60Security Classification60Software Identification61Trademark61Unit of Measure627.2Business Relationships62Business Relationships62Trading Partnership62Agreement-Contract-Data63Change Control Authority647.3Product Detail65Product Detail65Product Type65Hardware66Software69Process71Facility717.4Product Configuration73Product Configuration73As Designed Product Structure75As Designed Change and Traceability Requirements76As Planned Product Structure78As Built Configuration78As Maintained-Modified Configuration807.5Document81Document81Universal Document Data82Product Requirements Document83Specification Document83Engineering Design Document83Product Operation Document84Product Maintenance Document84Generic Document847.6Configuration Management Actions84CM Actions85Configuration Management Planning Action85Action Item87Selecting Configuration Items88Assigning Tracking Identifiers89Identifying Products And Documents90Releasing and Approving Documents91Requesting Change Or Variance92Classifying Changes96Change Impact Assessment97Determining Change Effectivity And Cost100Change Decision Action102Change Implementing Action103Configuration Audit Action105Delivery and Acceptance106Maintaining Status Accounting1078. Application Notes (Informative)109Annex A. EIA-836 User Guidance (Informative)111A.1 Scope111A.2 Introduction111A.3 Interpreting the Schema Diagrams112A.4 XML Instance Document Example116A.5 Interpreting the XML DTD File117A.6 Additional Sources of XML Information119Annex B. Data Element Alias Cross-Reference (Informative)120B.1Scope120B.2Alias Cross-Reference Content120Annex C. EIA-836 to EIA-649 Principles Cross-Reference (Informative)122C.1Scope.122C.2836/649 Cross Reference Content122Annex D. Data Element UDEF Cross-Reference (Informative)127D.1Scope.127D.2Data Element-UDEF Cross Reference Content127146Foreword (Informative)In the era of digital data and e-business, rapid access to accurate Configuration Management (CM) data has never been more important. Effective access to, sharing of, and exchange of CM data including common business objects and ad-hoc queries to information in databases or hosted on websites depends upon standardized CM data definitions including data element relationships. EIA-836 facilitates the interoperability and exchange of CM data by clearly delineating CM data elements and their relationships, and by providing the information content of CM data exchanges. The level of interoperability between dissimilar systems is determined by trading partner agreement. The extensible markup language (XML) facilitates data sharing and exchange among different systems. EIA-836 provides a set of standard definitions and business objects that can be used by XML frameworks in interfacing the content elements among one or more systems or databases.EIA-836 is designed to have wide applicability across vertical industries. The process employed to provide access, sharing or exchange, is typically accomplished using one of many available product data management tools or systems, often customized to a specific organizational environment. To be most effective, the capabilities of the process, tools or systems, should embody the CM principles in ANSI/EIA-649 “National Consensus Standard for Configuration Management,” in conjunction with the business objects and data element definitions in EIA-836.Access to this standard and the automated comment system is via /cm or Http:/. The comment sytem may also be accessed directly tocomment or check for already documented comments, and comment dispositions, at /custcomm/eia649.For further information about this standard or to participate in the GEIA G-33 Committee EIA-836 Working Group, contact Chistopher Denham at GEIA (703) 907-7567, e-mail CDenham Introduction (Informative)EIA-836 is a logical extension of ANSI/EIA-649, which defines the CM principles upon which it is based. EIA-836 also supports the Product Life Cycle Support (PLCS) Activity and Data Models. As shown in Figure 1, the primary focus of EIA-836 is on data element definitions, relationships, and business objects for information exchange.EIA-836 is a fundamental reference vocabulary for the access, sharing and exchange of CM data (including product configuration information), and for developing; mapping and using CM-enabled tools, systems, and databases. It facilitates interoperability regardless of specific schema or specific method of data transfer.As in EIA-649, a product is any item including any of the generic categories of hardware, software, document, processes, data, materials, or services. (This is consistent with the definition of “product” in ISO Standard 9000:2000). As Thus, for example, a piece-part is a product, an assembly is a product, and an end item is a product. 1. Scope1.1Scope of the StandardEIA-836 provides a comprehensive reference vocabulary. It includes definitions of all CM data elements and attributes considered to be within the CM domain that address: Product identification and relationships Configuration identification, Configuration change management Configuration status accounting, Configuration verification and audit, and Data and document management.The set of CM Business Objects in EIA-836 facilitates exchange of documents, data transactions, messages, and inquiries. The business objects may be modified or tailored by users to suit specific trading partner situations and different industry domains.EIA-836 provides a complete set of XML reference schema to provide the context for the CM data definitions by graphically illustrating the data element and attribute relationships, and to establish a basis for data modeling, data mapping, and data exchange.Since the focus of this standard is on CM data, it does not address all of the content elements of such objects as engineering drawings, part models, or specifications. The standard includes data necessary to locate such objects and includes only metadata pertinent to configuration management. Content, such as the following is considered to be out of scope: Product definition geometry, topology, tolerances, features, specifications/requirements Process description, and manufacturing process plans.1.2 Overview of the StandardThe body of EIA-836 essentially consists of CM Business Objects, the CM Data Dictionary, and CM reference Schemas. The Business Objects and Reference Schema are annotated with data element definitions. Annexes to the standard contain user guidance, and several informative cross-reference tables.Clauses 1 through 4 of this standard contain the scope, references, definitions, and symbols and abbreviations. Clause 5 CM Business Objects contains detailed content descriptions of CM Business Objects, which are data exchange documents represented as templates rather than rigid standards. Clause 6 CM Data Dictionary is an alphabetic listing showing the definition of all the data elements and attributes that are used in the EIA-836 Business Objects and Reference Schema. Clause 6 also describes the naming conventions used for the data elements and attributes.Clause 7 CM Reference Schema Description provides a description and graphical representation of the relationships between CM data elements implemented in an XML schema EIA-836 uses the term “schema” in the generic sense of data relationships or structures; it should not infer an association with the W3C XML Schema Candidate Recommendations. Data relationships are essential to a clear understanding of the data element definitions. Even more important, however, proper relationships are what enable a system to access the correct CM data for a given product configuration from among vast amounts of potentially erroneous or irrelevant data that a data query might otherwise return. The purpose of the schema is to convey a clear picture of the relationships to provide context for the data element definitions. Clause 8 Application Notes (Informative) provides information on how EIA-836 may be used.Annex A EIA-836 User Guidance (Informative) provides user assistance in navigating and applying EIA-836Annex B. Data Element Alias Cross-Reference (Informative) provides a listing of alias (alternative) names for the data element names used in the reference and business object schema, listed alphabetically by alias name.Annex C. EIA-836 to EIA-649 Principles Cross-Reference (Informative) provides a mapping of the content of EIA-836 to the underlying principles in EIA-649.Annex D. Data Element UDEF Cross-Reference (Informative) provides a Universal Data Element Framework (UDEF) name and code for the EIA-836 data elements and attributes in that have “data content”.Figure 2 illustrates how reference schema and business objects are related. The reference schema contains Core Components that are used many times throughout both the reference schema and the business objects. It also includes individual schemas in five other categories: Business Relationships, Product Detail, Product Configuration, Document and CM Actions. Each EIA-836 data element and attribute is declared in only one schema, and may be used by any other schema by including it in the content model of an element declared and defined in that schema.The Business Objects consist of individual schemas that are categorized by the CM function that they support. Since the CM Actions schemas address the information elements involved in individual configuration management actions that occur in the performance of configuration management, they are closely related to and define many of the elements used in the transactions defined by the Business Objects. Both the Reference Schemas and the Business Objects typically relate to a Program or Project, a Product or Products, or an Instance of a Product. They typically relate Products and associated Doc