Electronic Enterprise Integration Committee Standards Radar Chart

1. Electronic Enterprise Integration CommitteeStandards Radar Chart as of February 2009 Unpublished work © 2009 Aerospace Industries Association of America, Inc.

2. Executive Summary • The EEIC Radar Chart shows the various technology standards under the attention of the EEIC • The Adopt Existing Standard quadrant refers to standards which have been developed outside of AIA but which have relevance to the AIA. • The Monitor External Development quadrant refers to standards which are being developed outside of the AIA but which may have relevance to the AIA. • The Participate in External Development quadrant refers to outside standards development where EEIC members are actively participating and influencing. • The AIA Development quadrant shows standards and templates that the EEIC is developing internally

3. Process Overview • Standards begin in the outer “Track” ring while the EEIC reviews and/or evaluates the standard. • If a standard demonstrates relevance to AIA needs, it is promoted to the “Candidate” ring for deeper review. • Candidate Standards that the EEIC deems stable and relevant are presented to the eBusiness Steering Group (eBSG) for adoption as an AIA standard. • Candidates adopted by the eBSG are promoted to the inner “Adopted” ring and enter a review and maintenance cycle.

4. Radar UIMA d AIA Guidelines TSCP PM/EVM Monitor external development Adopt existing standard CPI Boost AeroSpace • Supplier • UID Boost Aero EIA-927 SEINE Units ML RFID App Stds ebXML PLCS STEP UDEF OTD S3000L SOA Supplier RFID GECA Template X12 EDI GTPA Template Supplier UID Guidebook LOTAR EDIG Adopted Candidate Clickable GTPA Participate in external development NCO CDE S1000D TDP (SMC) AIA development REACH IT EKM As of 2009-02-11 Track

5. Abstract The AIA EEWG (predecessor to the EEIC) developed these AIA user implementation conventions (IC) for 16 ANSI X12 EDI standard transactions under its charter from the AIA SMC. The initial set of 16 transactions cover the order management suite of documents commonly used between prime contractor and their suppliers. The suite of 16 is still widely used by member companies and has significantly reduced the cost of suppliers supporting disparate EDI implementations by the primes. ANSI X.12 EDI Implementation Conventions Click the icon below to view the details. Back to the Radar Chart Last revised: 01/22/07

6. BoostAero Abstract • BoostAeroSpace is a French initiative for a “European Aerospace digital hub”, building on the results of the earlier BoostAero and SEINE projects. The initial portfolio of services is intended to cover Supply Chain Management and collaboration tools (like Exostar), with extensions into CRM, MRO and Product data management (PDM/PLM). The current plan is to achieve pilot operation by end Q1 2009 and an initial set of operational services by the end of 2009. Further capabilities are planned through to the end of 2012. • There is a recognition that a global solution is required, and the project is actively seeking to establish joint governance of the underlying standards with AIA and ASD to ensure interoperability. Click the icon below to view the details. Back to the Radar Chart Last revised: 01/26/09

7. BoostAeroSpace Abstract • BoostAeroSpace is a French initiative for a “European Aerospace digital hub”, building on the results of the earlier BoostAero and SEINE projects. The initial portfolio of services is intended to cover Supply Chain Management and collaboration tools (like Exostar), with extensions into CRM, MRO and Product data management (PDM/PLM). The current plan is to achieve pilot operation by end Q1 2009 and an initial set of operational services by the end of 2009. Further capabilities are planned through to the end of 2012. • There is a recognition that a global solution is required, and the project is actively seeking to establish joint governance of the underlying standards with AIA and ASD to ensure interoperability. Click the icon below to view the details. Back to the Radar Chart Last revised: 02/11/09

8. Abstract The objective was to create a non-refutable, web-based document template and a predictable standard process for negotiating and producing legally executed electronic agreements for business relationships. An international standard would provide a consistent, predictable format for model documents. It would establish a standard process for electronically negotiating an instance of a consensus agreement. This process must include a standard mechanism for authenticating digital signatories and identity proofing, verification and validation. The model template would align with the regulatory frameworks and legal structures of companies engaging in e-business practices. It establishes a common set of rules by which parties agree to construct and negotiate electronic agreements in a hosted, web-based environment, thus ensuring auditable and non-refutable agreement. Features of the “Clickable Agreement Standard” would include: acceptance at an individual clause level; configuration management and audit trail of iterative versions of the electronic agreement; allowances for the addition of proposed revisions and comments during negotiation. In October 2005 the AIA EEIC eAgreements Work Group submitted a proposal that was accepted by the UN/CEFACT for immediate development of: 1) a standard non-refutable electronic agreement document template accepted by international courts of law; 2) a standard technical methodology for the iterative, electronic negotiation process for producing the document template; 3) an update to the existing UN/ECE (Economic Commission of Europe) electronic business agreement policy; 4) a validation of above by the UN/CEFACT Legal Committee. Clickable Global Trade Partner Agreement (GTPA) Click the icon below to view the details. Back to the Radar Chart Last revised: 9/29/2008

9. Abstract The DoD is seeking to apply a standard framework for continuous process improvement throughout the complete maintenance cycle for its entire range of systems, in order to achieve improved readiness and reliability at reduced total ownership cost and downtime. This thread complements the Performance Based Outcomes (PBO) strategy and the Total Life Cycle Systems Management (TLCSM) structure. The initiative is based on the development of consistent metrics and predictive modeling for materiel readiness, reliability and cycle time, to allow assessment of the impact of maintenance options such as CBM and RCM. As well as a major change in culture and process, effective implementation will require the reliable collection of accurate usage and maintenance information to feed the analysis. Continuous Process Improvement (CPI) Click the icon below to view the details. Back to the Radar Chart Last revised: 11/06/06

10. Abstract This ongoing project is designed to address the requirement for product data interoperability in product development across the product lifecycle in an environment where aerospace application vendors isolate their differentiated value in proprietary systems and closed architectures. The project seeks to identify key engineering interoperability scenarios and deliver recommendations on common information standards to be used, and to facilitate their deployment across the industry and its customers through the development of appropriate guidance material. Engineering Data Interoperability Group Click the icon below to view the details. Back to the Radar Chart Last revised: 03/02/08

11. Electronic Knowledge Management (EKM) • Abstract This ongoing project is designed to address the requirement for product data interoperability in product development across the product lifecycle in an environment where aerospace application vendors isolate their differentiated value in proprietary systems and closed architectures. The project seeks to identify key engineering interoperability scenarios and deliver recommendations on common information standards to be used, and to facilitate their deployment across the industry and its customers through the development of appropriate guidance material. Click the icon below to view the details. Back to the Radar Chart Last revised: 11/26/08

12. Abstract No Abstract Available FIPS 201 Click the icon below to view the details. Back to the Radar Chart Last revised:

13. Abstract The GECA provides global parties with a common set of rules by which they agree to exchange electronic data. The template is used to support electronic collaboration between companies engaging in domestic and international eBusiness practices. The GECA will supplement the primary terms and conditions and will govern the exchange of collaborative eData. The latest version of the GECA may be found on the AIA (HTTP://www.aia-aerospace.org) website, but may also be found on websites and other locations such as trading exchanges, portals and enterprise web pages. Global Electronic Collaborative Agreement (GECA) Click the icon below to view the details. Back to the Radar Chart Last revised: 01/16/07

14. Abstract GEIA-927 is being developed as a US reference model to achieve interoperability among IT systems for complex engineer-to-order systems, products and processes over the life cycle; building on many of today's data standards, integrating best-in-class data models from these partial solutions with the GEIA-927 top-level integration model. It is not intended to replace the existing information models, but to indicate how they can work together. GEIA-927 - Common Data Schema for Complex Systems Click the icon below to view the details. Back to the Radar Chart Last revised: 06/01/2007

15. Abstract The Global Trading Partner Agreement (GTPA) model template provides trading partners with risk mitigation guidelines addressing electronic trading risks such as unique regulatory and legal structures, information security and privacy policies for engaging in electronic commerce. The model GTPA supplements the primary terms and conditions governing the sale of goods and services between trading partners. The intent of the GTPA is to mitigate risk applying to all trading partners not withstanding corporate size or location and minimize barriers encountered when engaging with prospective trading partners. It is written to align with the regulatory frameworks and legal structures of companies engaging in domestic and international e-business transactions. The GTPA establishes a common set of rules by which trading partners agree to exchange business transaction data electronically. It is recommended that the GTPA be used as written, although it may be modified to accommodate partner unique electronic trading requirements. The concept of an industry standard is supported and endorsed by the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT). Global Trading Partner Agreement Template (GTPA) Click the icon below to view the details. Back to the Radar Chart Last revised: 01/16/07

16. Abstract No Abstract Available International Aerospace and Defense Federation Alliance (IADFA) Click the icon below to view the details. Back to the Radar Chart Last revised: 02/27/06

17. Abstract This project is a Public-Private Partnership to address a request from the US Government to recommend which business model(s) should be considered for procuring access to information managed by industry under a common data environment. The concept of a common data environment highlights the ability of data to be securely exchanged between two organizations, at little or no transformation cost, regardless of the local data development or data management environment. In order to respond to the Government’s request, this project group is organized along five areas that span standards and processes, infrastructure, contracting, finance and accounting, and business strategy. Extensive coordination with other committees and major industry groups has been on-going and will continue, ensuring an industry-wide perspective. Contributions from data standards groups representing the international community highlight the global nature of the demand for data exchangeability. NCO-CDE Click the icon below to view the details. Back to the Radar Chart Last revised: 03/02/08

18. Abstract The initiative is intended to enshrine the practice and capability of the ECCMA Open Technical Dictionary used to support the US DLA and the NATO Codification System. It provides a common structure for defining open technical dictionaries as repositories of sets of terminology derived from other standards, with links back to the originating document. Such repositories can accommodate multiple definitions of the same term, although each definition will have its own unique identification The dictionaries can then be used to set up catalogues and classification schemes using the terminology in the dictionaries to define property-values pairs, with terms resolvable over the Internet using the unique identifiers. A further application of the dictionaries links the properties of features in STEP product definitions to the NATO Codification Scheme, and also to automatically generate STEP product definitions fromthe characteristic properties. Open Technical Dictionaries Click the icon below to view the details. Back to the Radar Chart Last revised: 06/01/07

19. Abstract PLCS provides an internationally-agreed information model to address the problem of keeping the full set of information related to a product in alignment with that product throughout its lifecycle. Deployment of the PLCS standard will enable companies to have a single definition for all the product-related information related to individual products throughout their lifecycle, independent of changes in process and information technology. The standard will enable suppliers to deliver and receive support information in a consistent form, irrespective of the source. Interoperability will be facilitated by the adoption of common subsets of the standard, known as Data Exchange Sets (DEXs) to support particular logistics information flows, and the use of common reference data to configure the standard for operational use. Example scenarios Feedback of maintenance and performance information from an individual asset in a standard form to multiple receiving systems. Configuration management of individual assets. Integration of product modification program, scheduled and condition-based maintenance into a coherent work package, with resource allocation Maintenance planning for different operational environments Product Life Cycle Support (PLCS - ISO 10303-239) Click the icon below to view the details. Back to the Radar Chart Last revised: 04/14/08

20. Program Management Earned Value Management Abstract • The Defense Contract Management Agency (DCMA) in conjunction with the National Defense Industrial Association (NDIA) has defined Earned Value Management (contract Cost and Schedule reporting) standards for web based solutions. It is based on the ebXML Core Components in UN/CEFACT. In 2006 a Proof-of-Concept (POC) was demonstrated by DCAM with Boeing and NAVAIR. • DCMA CIO is now driving deployment of the resulting EVM XML standards to the DoD supply chain. AIA members Boeing, Raytheon and Northrop Grumman are in various stages of coordination with DCMA for this effort. DCAM, NASA and NAVAIR are the initial customers identified for this deployment Click the icon below to view the details. Back to the Radar Chart Last revised: 01/22/07

21. REACH-IT Abstract • The European Union (EU) recently established regulations to control the chemical composition of all products (articles) entering any country within the EU. The published goals of the regulations are to “ensure a high level of protection of human health and the environment as well as the free movement of substances …” • Those members of the aerospace industry who sell products to any country in the European Union need to understand the best practices IT methods and data formatsfor registering REACH related electronic data with the applicable organizations of the European Union. Click the icon below to view the details. Back to the Radar Chart Last revised: 08/15/08

22. Abstract Radio Frequency Identification (RFID) provides the capability to attach identity and other information to a physical object in the form of an electronic tag, which can be accessed remotely through a radio frequency reader and transmitted to application software. RFID tag hardware consists of a computer chip plus antenna which can be read from, and optionally written to, using an RF reader via radio frequency. Tag and Reader can operate in active mode with battery powered tags or in passive mode using reader power. Basic RFID is used to locate, track and identify assets and commodities, and to trigger events such as information exchange. New RFID capabilities offer a range of business opportunities for attaching additional information to a tagged product or shipping container and exploiting that information to streamline business processes. RFID applications are now being developed for Transportation, Logistics, Material / Inventory Management and Aircraft Maintenance in the Aerospace and Defense (A&D) Industry. ERP and MRP applications supporting RFID applications Multiple Industry verticals defining cross industry RFID data vocabularies RFID technology has multiple technology dimensions requiring agreed common interoperable standards and implementation guidance across the A&D Supply Chain: Hardware, covering the physical aspects of tags and readers Air interface, which defines how readers communicate with tags, to read and write information, with option of selective reading of subsets of information from a tag Conformance and performance standards for comparing actual devices with standards Data content, covering identifiers, structure, semantics and syntax Application protocols for communicating data and instructions to application software Applications, which combine the above into a business solution Operational guidance The first three of these are not specific to any particular business sector. Effective exploitation of RFID by the A&D industry will require specific business scenarios and the associated identification of tag-based information requirements. The scenarios will include a clear definition of the actors, information flows and event trigger points. RFID Application Standards Click the icon below to view the details. Back to the Radar Chart Last revised: 04/22/08

23. Abstract An industry guideline, including templates and samples, is being developed to minimize the burden of RFID requirements on the supply chain by recommending a standard solution set of file formats and methods of information transfer. The recommendations allow flexibility in choosing format and transfer mode according to a supplier's own technical capabilities. Even though the industry guideline is intended for the exchange of RFID data between industry partners (i.e., suppliers to prime contractors), the data requirements documented here are compliant with DoD RFID requirements, which prime contractors must satisfy. The AIA Electronic Enterprise Integration Committee will ensure that possible changes in contractual RFID requirements are harmonized in future revisions of the industry guideline. RFID Industry Data Exchange Guideline Click the icon below to view the details. Back to the Radar Chart Last revised: 02/27/07

24. Abstract The International specification for technical publications utilizing a common source database, commonly known as S1000D, has been produced to establish standards for the documentation of any civil or military vehicle or equipment. It is based on international standards such as SGML/XML and CGM for production and use of electronic documentation. In addition, it defines a Common Source Data Base (CSDB) to provide source information for compilation of the publications and for use in electronic logistics information systems to deliver modules of information direct to the user. More recently, it has been linked to the PLCS development, which enables the compilation of technical documentation direct from the current product structure. S1000D Click the icon below to view the details. Back to the Radar Chart Last revised: 03/02/08

25. Abstract Funded by the French Ministry of Industry, the SEINE project has been established to continue the work of the industry-funded BoostAero initiative (see separate blip) and extend the scope of the work into Product Lifecycle Management for collaborative co-design in the extended enterprise, across multiple industry sectors. Unlike BoostAero, SEINE recognizes that a wide range of PLM standards and processes are already available, and seeks to assemble the necessary standardized processes, information, IT tools and legacy interfaces to facilitate a set of business scenarios between prime contractors and their supply chain. SEINE recognizes the need for simple solutions for the supply chain. It has also recognized the potential benefit of collaboration with initiatives such as the AIA EDIG. SEINE (Standards for the Extended Innovative Numerical Enterprise) Click the icon below to view the details. Back to the Radar Chart Last revised: 01/05/07

26. Abstract The OASIS consortium developed a Reference Model for Service Oriented Architecture. The Reference Model for Service Oriented Architecture is an abstract framework for understanding significant entities and relationships between them within a service-oriented environment, and for the development of consistent standards or specifications supporting that environment. It is based on unifying concepts of SOA and may be used by architects developing specific service oriented architectures or in training and explaining SOA. The reference model is not directly tied to any standards, technologies or other concrete implementation details. However, it does seek to provide a common semantics that can be used unambiguously across and between different implementations. Service Oriented Architecture (SOA) Click the icon below to view the details. Back to the Radar Chart Last revised: 08/15/07

27. Abstract STEP provides a comprehensive set of internationally-agreed integrated information models to address the problem of exchanging product information between dissimilar computer applications throughout the lifecycle of the product. Deployment of the STEP standard enables companies to have a proven single definition for all the product-related information related to individual products throughout their lifecycle, independent of changes in process and information technology. The standard will enable suppliers to deliver and receive support information in a consistent form, irrespective of the source. Interoperability is facilitated by the adoption of common subsets of the standard, known as Application Protocols to support particular information flows. STEP - Standard for the Exchange of Product model data Click the icon below to view the details. Back to the Radar Chart Last revised: 03/02/08

28. Supplier UID Abstract • The Aerospace Industry Guideline for IUID Data Exchange between partners and primes has been published on the AIA Web site in the Library Section. The industry guideline, including templates and samples, was developed to minimize the burden of IUID requirements on the supply chain by recommending a standard solution set of file formats and methods of information transfer. The recommendations allow flexibility in choosing format and transfer mode according to a supplier's own technical capabilities. Even though the industry guideline is intended for the exchange of IUID data between industry partners (i.e., suppliers to prime contractors), the data requirements documented here are compliant with DoD IUID requirements, which prime contractors must satisfy. The AIA Electronic Enterprise Integration Committee will ensure that possible changes in contractual IUID requirements are harmonized in future revisions of the industry guideline. Click the icon below to view the details. Back to the Radar Chart Last revised: 12/22/06

29. Transglobal Secure Collaboration Program (TSCP) Abstract • The Transglobal Secure Collaboration Program (TSCP) is a government-industry partnership specifically focused on mitigating the risks related to compliance, complexity, cost and IT that are inherent in large-scale, collaborative Aerospace and Defense programs that span national jurisdictions. • TSCP offers a collaborative environment where leaders in A&D can explore ways to jointly address the challenges of demonstrating trustworthiness to government agencies, project partners and supply networks. • TSCP is establishing and testing a common standards-based framework, mutually beneficial operating rules and mechanisms for federated trust environments for secure collaboration and sharing of sensitive information in international defence and aerospace programs. The approach balances the need to protect intellectual property (IP) while demonstrating willingness and ability to meet contractual requirements from government customers for auditable, identity-based, secure flows of information. Publicly available standards and specifications are exploited wherever available Click the icon below to view the details. Back to the Radar Chart Last revised: 02/11/09

30. Abstract The UDEF is an evolving global best practice method for naming and indexing data element concepts (as defined by ISO/IEC 11179) that exist across multiple applications and disparate data standards. It assigns each data element concept an alphanumeric tag plus a semantically rich name – that in most cases can stand-alone without requiring a separate definition. For example, “Purchase Order Number” found in an invoice from industry to the government is a commonly encountered data element concept. This concept has a UDEF tag d.t.2_13.35.8 and associated UDEF name Purchase.Order.DOCUMENT_Government.Assigned.IDENTIFIER. The UDEF is not another data standard. The UDEF provides a semantic bridge between data standards or between applications that need to share data but cannot use an existing data standard. The UDEF name and associated ID pair is similar in several ways to the Domain Name System (DNS) used to manage computer-sensible IP addresses in 123.456.789 format and to associate them to user-friendly formats such as www.company.com If adopted on a global scale, the UDEF would become a Semantic DNS. Organizations that intend to implement Service Oriented Architecture (SOA) will need to address the semantic integration question. To become a globally adopted best practice, the UDEF must be hosted by a global registry/repository. The Open Group is in the process of establishing the UDEF as the universally used classification system for data elements. AIA is among several industries involved in developing and promoting the UDEF concept. Universal Data Element Framework (UDEF) Click the icon below to view the details. Back to the Radar Chart Last revised: 03/02/08

31. Abstract This initiative is designed to provide a standardized approach to assigning semantics to unstructured information such as Word documents, audio and video, a set of basic interface definitions for implementing interoperable tools for analyzing unstructured information to discover appropriate semantics, and a Java runtime library for supporting such UIM application tools. It is based on extending the IBM UIMA Java Framework to be independent of any particular programming model and platform. The framework has already been released to the open-source community. Unstructured Information Management Alliance (UIMA) Click the icon below to view the details. Back to the Radar Chart Last revised: 08/11/08

32. Abstract Units Markup Language (UnitsML) is being developed as a standard method for encoding scientific units of measure in XML.   The development and deployment of a markup language for units will allow for the unambiguous storage, exchange, and processing of numeric data, thus facilitating the collaboration and sharing of information over the Internet. It is anticipated that UnitsML markup will be used by the developers of other markup languages to address the needs of specific communities (e.g. mathematics, chemistry, materials science, etc.). The UnitsML language is expected to be the first part of a project that is composed of three components: an XML schema (UnitsML), a database containing detailed information on SI (International System of Units) and non-SI scientific units of measure, and tools to facilitate the incorporation of UnitsML into other markup languages. The XML schema under development for UnitsML allows for the ability to represent scientific units of measure in XML and will be used for validating XML documents that use UnitsML.  The UnitsML schema is not intended to be a standalone schema, but rather to be used in combination with other specific schemas through the use of namespaces. SI units can be represented through the use of base units (e.g., meter, second), special derived units (e.g., joule, volt), and any combination of these units with appropriate prefixes and exponential powers (e.g., mm o s-2). In addition, commonly used derived SI units (e.g., square meter, meter per second) and non-SI units (e.g., minute, ångström, and inch) will be explicitly supported for reference within XML documents. Units Markup Language Click the icon below to view the details. Back to the Radar Chart Last revised: 11/05/06

33. Abstract The ebXML Core Components Technical Specificationcan be employed wherever business information is being shared or exchanged amongst and between enterprises, governmental agencies, and/or other organizations in an open and worldwide environment. The Core Componentsprovides business people, business document modelers and business data modelers, Business Processmodelers, and application developers of different organizations a common set of vocabulary building blocks to support interoperability of business information. This interoperability covers both interactive and batch exchanges of business data between applications through the use of Internet and Web based information exchanges as well as traditional Electronic Data Interchange (EDI) systems. The ebXML Core Components Technical Specification, Version 2.01 (ebCCTS) is also published as ISO/TS 15000-5. Under the governance of UN/CEFACT TBG17, a library of approved core components is available for various standards organizations to use as building blocks for their transactions. These core components provide the basis for the XML-based, eBusiness vocabularies to be used for our global Aerospace & Defense industry. The core components are the foundation for the evolving BoostAero set of aerospace ebusiness transactions and for the Program Management Earned Value Management transactions. ebXML Core Components Click the icon below to view the details. Back to the Radar Chart Last revised: 06/01/07

34. Abstract The eBusiness Implementation Guidebook provides a single reference point for the AIA eBusiness methodology, the list of eBusiness Framework components approved by the eBSG for use in the industry, and how the components should be assembled to provide business solutions for an extensible list of eBusiness scenarios. New components, scenarios and solutions can be added to the Guidebook as they are completed, which means that the Guidebook is a living document, accessible through the AIA website. eBusiness Implementation Guidebook Click the icon below to view the details. Back to the Radar Chart Last revised: 10/29/07

35. Abstract The LOTAR project is designed to provide a capability to store digital product information in a standard neutral form that can be read and reused throughout its lifecycle, independent of changes in the IT application environment originally used to create it. The multi-part standard covers both the information content and the processes required to ingest, store, administer, manage and access the information. LOTAR brings together the work started under the AIA Manufacturing Maintenance and Repair Committee with similar work in ASD-Europe, under the auspices of the International Aerospace Quality Group (IAQG). Long Term Archiving and Retention (LOTAR) Click the icon below to view the details. Back to the Radar Chart Last revised: 08/14/08