1 Strategic Standardisation Group Standards Radar ChartV1.9 17/02/2017 Copyright © 2017 AeroSpace and Defence Industries Association of Europe - ASD (based upon AIA presentation principle)

2 Executive Summary The SSG Radar Chart shows the various technology standards under the attention of the SSG. The Adopt Existing Standard quadrant refers to standards which have been developed outside of ASD but which have relevance to the ASD. The Monitor External Development quadrant refers to standards which are being developed outside of the ASD but which may have relevance to the ASD. The Participate in External Development quadrant refers to outside standards development where SSG members are actively participating and influencing. The ASD Development quadrant shows standards and templates that the SSG is developing internally Through this synthesis view, the SSG intends to build on the methods developed by AIA and to develop a common Aerospace view on e-Business Standards.

3 Process Overview Standards begin in the outer “Track” ring while the SSG reviews and/or evaluates the standard. If a standard demonstrates relevance to ASD needs, it is promoted to the “Candidate” ring for deeper review. Candidate Standards that the SSG deems stable and relevant are presented to the ASD SSG Members for adoption as an ASD standard. It is recommended that candidate standards are proven through pilot implementations prior to adoption. Candidates adopted by the ASD SSG Members are promoted to the inner “Adopted” ring and enter a review and maintenance cycle.

4 Criteria for adoption Criteria for a standard to be “Adopted”:Standard officially published and available Consistency of the standard with the ASD Through Life- cycle interoperability policy Refer to the related report on ASD SSG website, at Adoption statement validated by ASD members (the adoption statement could refer to any pilot implementations/deployments)

5 Radar screen Available Monitor external external standards developmentTrack OAGIS VEC KBL RFID App Stds PLCS DEXs PAS55 ArchiMate Available external standards OSLC Modelica FMI Monitor external development SysML STEP AP233 TSCP STEP AP235 STEP VDA4969 TSCP ILH v1 Supplier UID STEP AP238 STEP AP212 Candidate STEP AP239ed2 TSCP TF SAML STEP AP210 BPMN STEP AP209 TSCP IdFv1 ISO 22745 XPDL ebXML ReqIF Adopted QIF ISO 8000 SPEC2300 GEIA-0007 STEP AP203 PRC/U3D TSCP SEv1 3D Visualisation SPEC2000 STEP AP214 MIMOSA COLLADA IEEE 1636 SCORM ISO 14306 JT V1 STEP ASD S-Series TSCP 3D visualisation LOTAR ATA eBusiness S1000D S2000M STE100 ISO 14306 JT V2 Boost Aero S3000L S4000P SX000i TDP message STEP AP242ed1 SX001G S5000F MoSSEC EN9300-1xx S6000T SX002D STEP AP242ed2 ASD development EN9300-3xx Participate in external development EN9300-2xx SPEC2000 STEP AP239ed3 EN9300-4xx EN9300-6xx SPEC2300 SPEC1000BR iSPEC2200 Blip available EN9300 LOTAR SPEC42 yy Blip in preparation yy Current ASD SSG actions Version: V1.9 (February 2017)

6 3D Visualisation Abstract Click the icon below to view the details.The design and manufacture of today’s products is largely based on 3D electronic models developed on CAx systems. While these tools provide powerful capabilities for developing product definitions, the objective of 3D visualization is to allow the resulting information to be viewed across a wider population without the need for high-end CAD workstations or CAD software licences. This facilitates review and information use, accelerating product development. Standard information formats for visualization allow such tools to be used to view information generated by different native CAx systems. Visualization is not intended to replace or overlap CAx systems functionalities. It is not intended to replace existing CAx data exchanges but to complement it in those cases where the data receiver does not need the functionality of the authoring system and only requires a selected subset of the completed information model. In addition, a sender, in order to protect intellectual property, may not wish to release underlying constructional information and the knowledge included in a rich CAx data model, but may wish to disclose only selected information. Visualisation data is destined for a data consumer rather than for a data creator or updater. Click the icon below to view the details. Back to the Radar Last revised: 6

7 ArchiMate Abstract Click the icon below to view the details.ArchiMate is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains in an unambiguous way. ArchiMate is a technical standard from The Open Group and is based on the concepts of the IEEE 1471 standard. It is supported by various tool vendors and consulting firms. ArchiMate distinguishes itself from other languages such as Unified Modeling Language (UML) and Business Process Modeling Notation (BPMN) by its enterprise modeling scope. Click the icon below to view the details. Back to the Radar Last revised:

8 BoostAero Abstract Click the icon below to view the details.The BoostAero initiative was initially established as a joint French and Exostar initiative to achieve a standardized set of procurement e-trading messages, in order to avoid a proliferation of incompatible portals. This deliberately sought to build on the internationally agreed set of core components for ebXML by working through UN/CEFACT, in order to ensure interoperability with other electronic trading environments. The initial set of messages has been developed and piloted, and is now being deployed in production use. It was recognized at an early stage that the diversity of the global aerospace supply chain meant that the business objective could only be achieved by seeking global adoption of the standard. The BoostAero team therefore approached European ASD and American AIA seeking broader acceptance of their approach. The initial AIA due diligence process highlighted no major obstacles to use of BoostAero, but some need for modifications, similar to the European view. The BoostAero standard has been adopted in 2009 by the BoostAeroSpace Hub founders (i.e. Airbus, Dassault-Aviation, EADS, Safran, Thales) as the standard for exchanges on AirSupply between customers and suppliers. This will generalize the use of BoostAero standards in the A&D Supply Chain. Click the icon below to view the details. Back to the Radar Last revised:

9 BPMN - Business Process Modelling NotationAbstract BPMN is a standardized graphical notation that depicts the steps in a business process and the end-to-end flow of a business process. It has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities. It targets at facilitating communication between users, business analysts, vendors and service providers that need to communicate business process in as standardized manners, within eBusiness context. Click the icon below to view the details. Back to the Radar Last revised: 9

10 COLLADA - COLLAborative Design ActivityAbstract The COLLADA format is a file format for exchange between 3D applications (including games). COLLADA file is an XML file. The specification and the XML-based schema are publicly available. Collada 1.5 specification was published in April 2008 by Khronos Group. Example of applications and software supporting COLLADA: 3dsMax, 3Dvia, Blender, Photoshop. The features supported are: B-rep geometry / Mesh geometry / Level of Detail and Streaming Instantiation Transform hierarchy (rotation, translation, shear, scale, matrix) Compressed Exchange format Animation / Kinematics Physics (rigid bodies, constraints, rag dolls, collision, volumes) Shaders / Materials/ Textures / Lights /Skinning Cameras ISO/PAS 17506:2012 Industrial automation systems and integration -- COLLADA digital asset schema specification for 3D visualization of industrial data was published in July 2012. Click the icon below to view the details. Back to the Radar Last revised: 10

11 ebXML Core Components Abstract Click the icon belowThe ebXML Core Components Technical Specification can 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 Components provides business people, business document modelers and business data modelers, Business Process modelers, 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 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. Click the icon below to view the details. Back to the Radar Last revised:

12 FMI - Functional Mock-up InterfaceAbstract Functional Mock-up Interface (FMI) is a tool independent standard to support both model exchange and co-simulation of dynamic models using a combination of xml-files and compiled C-code. FMI improves and simplifies the exchange of dynamic system models between different modelling, simulation and co-simulation tools. Applications range from software/model/hardware-in-the-loop simulation to embedded systems To create the FMI standard, a large number of software companies and research centers have worked in the MODELISAR European R&D project. The MODELISAR project started in 2008 to define the FMI specifications, deliver technology studies, prove the FMI concepts through Use Cases elaborated by the consortium partners and enable tool vendors to build products. After the end of the MODELISAR project in 2011, FMI is managed and developed as a Modelica Association Project (MAP) The FMI specifications are distributed under open source license. Click the icon below to view the details. Back to the Radar Last revised:

13 ISO 14306 - JT Edition 1 Abstract Click the icon belowThe JT format is an industry focused, high-performance, lightweight, flexible file format for capturing and repurposing three-dimensional product definition data that enables collaboration, validation and visualization throughout the extended enterprise It can contain any combination of 3D approximate (faceted) data, 3D exact boundary representation surfaces (NURBS, B-Spline), Product and Manufacturing Information (PMI), and Metadata (textual attributes) either exported from the native CAD system or inserted by a product data management (PDM) system. It contains 3 possible 3D exact representations (JT B-Rep, XT B-Rep and XT-Parasolid LWPA). ISO 14306:2012 “JT Edition 1” was adopted by ISO in December 2012 as a 3D visualization capability, in addition to the ISO series (STEP). ISO 14306:2012 defines the syntax and semantics of the JT Version 9.5 file format. Click the icon below to view the details. Back to the Radar Last revised:

14 ISO 14306 - JT Edition 2 Abstract Click the icon belowIn 2012, ISO/DIS 14306: “JT file format specification for 3D visualization” has failed the DIS Ballot and after the following resolution workshop, ISO TC 184/SC 4 has requested WG 12 to develop a New Work Item Proposal (NP) for a new edition of ISO 14306, called JT Edition 2, including but not limited to: Replacing XT Brep and JT Brep with STEP curve, surface and Brep entity definitions. Extending the scope to include external references to support semantic PMI for assemblies and other requirements from AP 242. The replacement of XT Brep and JT Brep is motivated by the dependencies to specific software and software vendors for non-ambiguous information sharing and efficient standard implementation. The scope of the second edition has not changed from the first edition and is focused on 3D visualization, excluding product data exchange and long term archiving. Click the icon below to view the details. Back to the Radar Last revised:

15 ISO 22745 Open technical Dictionaries and automated data exchangeAbstract The initiative is intended to enshrine the practice and capability of Electronic Open Technical Dictionaries and used to support automated data transactions between participating entities. 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 from the characteristic properties. This standard in conjunction with ISO 8000 Pt 110 has been used in trials to generate automatically from source technical descriptions in accordance with the US Federal Item Identification Guides and NATO Codification System. The trials used a schema provided by ECCMA as part of the only currently accredited ISO OTD (ECCMA Open technical Dictionary) Click the icon below to view the details. Back to the Radar Last revised:

16 ISO 8000 - Data Quality Abstract Click the icon belowThe ISO 8000 series of standards covers data quality activities, terminology, characteristics (criteria) and testing. Data quality is a pervasive problem for organizations across the globe and has a major economic impact. No one nation can afford to develop a unique perspective on the solution to this problem. The standard is applicable to all types of industrial data, including master data, transaction data and product data. ISO 8000 defines characteristics that can be tested by any organization in the data supply chain to objectively determine conformance of the data to ISO ISO 8000 does not require external certification of data quality. Therefore, data quality conformance can be self-controlled. ISO 8000 provides a framework for improving data quality that can be used independently or in conjunction with quality management systems. Click the icon below to view the details. Back to the Radar Last revised:

17 EN9300 LOTAR - Long Term Archiving and RetentionAbstract The LOTAR project is designed to provide a capability to preserve digital aerospace and defence 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 the requirements, the information content and the processes required to ingest, store, administer, manage and access the information. The LOTAR international project brings together the works started in Europe by ASD Stan LOTAR, supported by ProSTEP iViP, and the US similar works started by PDES Inc and AIA, under the auspices of the International Aerospace Quality Group (IAQG). This general recommendation of the ASD SSG regarding the LOTAR standards are completed by other SSG recommendations per specific domains: LOTAR 3D PMI : long term preservation of 3D PMI information, LOTAR PDM : long term preservation of PDM information. LOTAR Composite : long term preservation of Composite information. LOTAR Electrical : long term preservation of Electrical Harness information, Click the icon below to view the details. Back to the Radar Last revised:

18 EN9300-1XX - Long-Term Archiving and Retrieval of 3D Geometry, CAD structure and Product Manufacturing Information (LOTAR 3D CAD) Abstract The LOTAR The LOTAR project is designed to provide a capability to preserve digital aerospace and defence 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. This document focuses on the EN9300-1XX family for long term archiving and retrieval of CAD mechanical information, including assembly structure, 3D Geometric shape representation (explicit and implicit), associated Product and Manufacturing Information (PMI), and machining form features. The EN9300-1XX family is organized as a sequence of parts, each building on the previous in a consistent way. Some of the EN9300-1XX standards are adopted and exploited by the Aerospace and Defence industry. As technology matures additional parts will be released in order to support new requirements within the aerospace community. Click the icon below to view the details. Back to the Radar Last revised:

19 EN9300-2XX - Long-Term Archiving and Retrieval of Product Management Data & Configured Mechanical Product Structure (LOTAR PDM) Abstract The LOTAR project is designed to provide a capability to preserve digital aerospace and defense 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. This document focuses on the ASD EN9300-2XX family for long term preservation of the Product Management Data Information throughout lifecycle. The EN9300-2XX family is organized as a sequence of parts, each building on the previous in a consistent way. Some of the EN9300-2XX standards are draft. As technology matures additional parts will be released in order to support new requirements within the aerospace community. Click the icon below to view the details. Back to the Radar Last revised:

20 EN9300-3XX - Long-Term Archiving and Retrieval of Composite Information (LOTAR Composite)Abstract The LOTAR The LOTAR project is designed to provide a capability to preserve digital aerospace and defence 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. This document is focused on the EN9300-3XX family for the long term archiving and retrieval of the composite structures. The EN9300-3XX family is organized as a sequence of parts, each building on the previous in a consistent way. EN9300-3XX standards are in development and will be adopted and exploited by the Aerospace and Defense industry. As technology matures additional parts will be released in order to support new requirements within the aerospace community. Click the icon below to view the details. Back to the Radar Last revised:

21 EN9300-4XX - Long-Term Archiving and Retrieval of Electrical Harness Information (LOTAR Electrical Harness) Abstract The LOTAR project is designed to provide a capability to preserve digital aerospace and defence 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. This document is focused on the EN9300-4XX family for the long term archiving and retrieval of Electrical Harness information. The EN9300-4XX family is organized as a sequence of parts, each building on the previous in a consistent way. Some of the EN9300-4XX standards are adopted and exploited by the Aerospace and Defense industry. As technology matures additional parts will be released in order to support new requirements within the aerospace community. Click the icon below to view the details. Back to the Radar Last revised:

22 MIMOSA Machinery Information Management Open Systems AllianceAbstract MIMOSA is a not-for-profit trade association dedicated to developing and encouraging the adoption of open information standards in operations and maintenance (O&M) in manufacturing, fleet, and facility environments. MIMOSA has developed two information-exchange open standards, providing for example metadata reference libraries and a series of information-exchange standards using XML and SQL: A standard for management applications: Open Systems Architecture for Enterprise Application Integration (OSA-EAI™) Includes modelling, metadata, source, query/response, historicity, etc. Applicability: Diagnostics, prognostics, trending, test, and maintenance, Acquisition of built-in-test results, storage of raw and transformed data, and exchange of data for analysis and viewing A standard for condition-based maintenance: Open Systems Architecture for Conditioned Based Maintenance (OSA-CBM™) Object interfaces (modules with exposed methods) Platform oriented (helicopter, vehicle, ship). Click the icon below to view the details. Back to the Radar Last revised:

23 Modelica Abstract Click the icon below to view the details.Modelica® is a non-proprietary, object-oriented, declarative, equation based language to conveniently model complex physical systems containing, e.g., mechanical, electrical, electronic, hydraulic, thermal, control, electric power or process-oriented subcomponents.. Modelica is a free language developed by the (non-profit) Modelica Association since The Modelica Association develops also the a free library for multi-domain models: the Modelica Standard Library. The Modelica design effort was initiated in September The goal was to develop an object-oriented language for modeling of technical systems in order to reuse and exchange dynamic system models in a standardized format. Modelica supports behaviours described by differential, algebraic, and discrete equations, enabling a large spectrum of 0D/1D simulations. 3D simulation based on partial differential equations (e.g. FEM, CFD) is not supported, but results of such simulations can be integrated (e.g. using surrogate models). Click the icon below to view the details. Back to the Radar Last revised:

24 MoSSEC - Modelling and Simulation in Collaborative Systems Engineering ContextAbstract The ISO MoSSEC project is designed to provide a capability to share modelling and simulation (M&S) information in a collaborative systems engineering context, and to enable full traceability and re-use of this information throughout the product lifecycle and independent of the specific IT applications used across collaborating enterprises. The targeted standard covers a core subset of systems engineering information content and the related practices and information services necessary to support engineering collaboration. The ISO MoSSEC international project brings together the works started in Europe by CRESCENDO and TOICA Consortia to apply AP233/AP239 for this scope, and similar works in Europe and US motivated by similar goals. The project deliverable will be a new STEP Application Protocol [AP] under ISO TC 184/SC 4 within the New STEP Architecture and utilising a subset of the AP239/AP242 harmonised information model. This AP will include an activity model for usage guidance; AP-level definitions for agreed implementation technologies; conformance classes; documentation and dissemination material. Click the icon below to view the details. Back to the Radar Last revised:

25 OAGIS Open Applications Group Integration SpecificationAbstract The specification provides a set of standardized XML messages for use throughout the supply chain. It defines a series of Business Object Definitions (BODs) to support the standardized exchange of typical messages used in B2B applications for commercial supply chain and accounting transactions. Each BOD comprises a Verb (get, show, list, process etc.) and a Noun (purchase order, shipping list, invoice, BoM etc.). Some 16 verbs and 75 nouns are defined by OAGIS 9. Messages can be tailored to meet local user requirements. Brief scenarios are provided to illustrate usage of most BODs. EDS used selected nouns from OAGIS 8 as an integration model for the UK MoD Supply Enterprise Information Architecture (EIA) hub. OAGIS 8 has also been applied to a few messages linking the Log Info System, LITS, to the EIA Hub on the Tornado ATTAC project. OAGIS 9 differs from the earlier versions due to alignment with the ebXML Core Components Library (see separate blip) developed by OASIS and UN/CEFACT, which is the agreed international approach for transactional messages. There has been a deliberate decision to break upward compatibility to address this alignment. The specification is freely available for download from the OAGi site Click the icon below to view the details. Back to the Radar Last revised: 25

26 OSLC - Open Services for Lifecycle CollaborationAbstract Open Service for Lifecycle Collaboration (OSLC) is an open community, originally proposed in 2008, to define a set of specifications that enable integration of software development and more broadly Application Lifecycle Management (ALM) and Product lifecycle Management (PLM) products and services. The OSLC initiative is divided up into a dozen workgroups and each workgroup develops specifications in context of a specific part of the lifecycle. For example, there are workgroups for Change Management, Quality Management, Requirements Management, Software Configuration Management and Build Automation. As of June 2013, the OSLC initiative is a Member Section of the Open Standard Organization OASIS. The OSLC specifications build on the W3C Resource Description Framework (RDF), Linked Data and REST, enabling integration at data level via links between related resources. OSLC resources are defined in terms of RDF properties. Operations on resources are performed using HTTP. OSLC also specifies user interface techniques to enable preview, creation and selection of links. Click the icon below to view the details. Back to the Radar Last revised: 26

27 PRC/U3D - Open Services for Lifecycle CollaborationAbstract The PDF format is a file format for the representation of documents. PDF allows to preserve the layout (text, font, graphics and other information). It is independent of the operating system and the software. PDF was originally developed by Adobe Systems in The open format has been published by the ISO in 2008. PDF/E is a subset of pdf. The intent is the exchange of engineering and technical data. The part 1 of PDF/E published by the ISO in 2008 include the U3D format. The part 2 of PDF/E will include the PRC 1.0 format. U3D is a file format for 3D data. U3D was originally develop by a group including Intel, Boeing, HP, Adobe Systems. U3D standard has been published in 2006 by ECMA international. PRC is a file compressed format allows to have different representation of a 3D model. PRC was originally developed by TTF. PRC format has reached the Draft International Standard stage in 2012. Click the icon below to view the details. Back to the Radar Last revised: 27

28 PAS 55:2008 BSI Publically Available Specification Asset ManagementAbstract PAS 55 defines the requirements for an integrated and cohesive Asset Management system, providing a clear “line of sight” from organization direction and goals down to individual, day-to-day activities. Asset Management in this context is the systematic and coordinated activities and practices through which an organization optimally manages assets and systems, their performance, risks and expenditures over their life cycles for the purpose of achieving the organisational strategic plan. To ensure consistency with other related management system standards, PAS 55 was documented as a specification, with the information on implementing asset management distilled into key requirements. The criterion for including such requirements has been that, without them, the asset management system would be regarded as deficient. This Specification is applicable to any organization where physical assets are a critical factor in achieving its goals. Click the icon below to view the details. Back to the Radar Last revised: 28

29 RFID Application StandardsAbstract 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 Click the icon below to view the details. Back to the Radar Last revised:

30 S1000D - Specification for Technical PublicationsAbstract The international specification for technical publications using a common source database, commonly known as S1000D, has been produced to establish standards for the technical documentation of any civil or military vehicle or equipment. It is based on international standards such as 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. S1000D is linked to the PLCS development, which enables the compilation of technical documentation direct from the current product structure. The specification also includes rules and XML Schemas to enable the production of SCORM-compliant Web Based Training (WBT). Click the icon below to view the details. Back to the Radar Last revised:

31 S2000M International specification for material management specificationAbstract The ASD S2000M defines the Materiel Management processes and procedures to be used in support of any military Product. Although this Specification is designed for military Product support, it may nevertheless be used for the support of any non-military Product. The S2000M describes the business relationship between Industry and Customer by providing the process flow, the relevant transactions and data elements used. The S2000M is organized into basic chapters: Chapter 1A Provisioning Chapter 1B NATO Codification Chapter 2 Procurement Planning Chapter 3 Order Administration Chapter 4 Invoicing Chapter 5 Repair Administration Chapter 6 S2000M Light Click the icon below to view the details. Back to the Radar Last revised: 31

32 S3000L - International procedure specification for Logistic Support Analysis LSAAbstract With the introduction of a new and complex technical product, all logistic requirements must be made available in a timely manner. This requires a process to ensure consideration of logistic requirements during the design of the product and support the establishment of a proper support system. The LSA process includes a number of analysis activities concerning a wide range of technical and logistic considerations and the careful documentation of the results of these analysis activities. The achievement of proper supportability is of crucial importance concerning operation and life cycle costs. Early consideration of logistic aspects is increasingly important with regard to both operational and economic aspects. A product that cannot be operated and maintained properly and cost effectively is not acceptable to the end user. The purpose of the specification S3000L is to cover the activities and requirements governing the establishment of the LSA process. Click the icon below to view the details. Back to the Radar Last revised:

33 S4000P - International specification for developing and continuously improving preventive maintenance Abstract According to the ASD scope, S4000P must cover all kind of Product types including any complex technical platform, system, equipment or facility (eg. on air/sea/land, under sea, under ground, in space). The main purpose of ASD S4000P is to assist regulatory authorities and all parties involved in the analysis process in developing and releasing initial Preventive Maintenance Task Requirements (PMTR) and intervals for new Products prior entry into service. The S4000P analysis methodologies remain applicable for later optimizations/modifications of the Product design in Product systems and/or of Product structure and/or of Product zones during the Product in-service phase. Once developed, authorized and packaged into interval clusters in a Product Operator Maintenance Program (OMP), the S4000P In-Service Maintenance Optimization (ISMO) process enables continuous improvement of Product maintenance during the in-service phase. Every development of a PMTR or later improvements of a preventive maintenance task for a Product is linked to at least one of the following aspects: Ensure / maintain Product safety, including safety/emergency systems and/or emergency equipment, Avoid any conflict with law and/or significant impact on environmental integrity (ecological damage) during Product mission/operation and/or maintenance, Optimize mission/operational capability/availability of the Product, Optimize Product economy (Life Cycle Costs = LCC). Click the icon below to view the details. Back to the Radar Last revised: 33

34 S5000F - Operational and Maintenance Data FeedbackAbstract In-service data feedback is one of the most important functions of in service support. It enables fleet managers, support managers and technical system manufacturers to perform a thorough analysis of operational and maintenance performance of a technical system. The results of the analysis can be the basis for: enhancement of the maintenance and support concept improvement of the product or the system by modifications and retrofit activities sophisticated operational planning management of requirements and contracts The overall aim to be achieved through in-service data feedback is the increase of fleet availability and optimization of effectiveness. In addition the in-service data feedback information is a firm requirement by industry to agree to and manage Performance Based Logistics (PBL) contracts and to fulfil their obligations in the regard to product liability. The aim with S5000F is to handle information from the in service operation (from the operator to the Product manufacturer or the maintainer) or vice-versa during the in-service phase. The processes used for this are described in the specification, with the focus on specific use cases that are associated to activities that typically require in-service data feedback. The association of data feedback to specific use cases ensures that no unnecessary information is requested from the field. Click the icon below to view the details. Back to the Radar Last revised:

35 SX000i - International guide for the use of the S-Series Integrated Logistics Support (ILS) specifications - (“ILS Guide”) Abstract Integrated Logistic Support (ILS) is the integrated management of the definition and development of all support resources, using a common process and methodology, so as to harmonize the different support elements, prevent unnecessary rework and reduce overall life-cycle costs. The SX000i has been developed to ensure the compatibility and the commonality of ILS processes among the AIA/ASD S-Series ILS specifications. By providing a single framework that documents the global ILS process and interactions, and by defining governance requirements for the S-Series ILS Specifications, the SX000i and S-Series Specifications will enable all stakeholders to apply common logistics processes so as to share and exchange data securely through the life of products and services. Through the secure and standardized exchange of data and information, product performance and life cycle cost can be more easily analyzed and optimized, and collaboration between customers and industry can be simplified. Click the icon below to view the details. Back to the Radar Last revised:

36 SX001G - Glossary for the S-series ILS specificationsAbstract With the drive for an integrated set of Integrated Logistic Support (ILS) specifications, the need arises for common definitions, common terminology, common abbreviations and data elements. This cannot be achieved if these elements are spread across different specifications. The SX001G glossary will provide a common reference across all S-series specifications. Click the icon below to view the details. Back to the Radar Last revised:

37 SX002D - Common data model for the S-Series ILS SpecificationsAbstract With the drive for an integrated set of Integrated Logistic Support (ILS) specifications, the need arises for interoperability between the different data models of the different specifications. This cannot be achieved unless a common core is hared across all specifications The SX002D defines a Common Data Model across all S-Series ILS specifications, and will cover all elements shared by at least two specifications. SX002D is based on AP239 and will therefore allow the integration with other domains, such as requirements (AP233) or engineering (AP242) as soon as the different APs have been all integrated. Click the icon below to view the details. Back to the Radar Last revised:

38 SAML - Security Assertion Markup LanguageAbstract SAML Defines a protocol to exchange, identification and authentication information in order to enable security and confidence through Internet collaboration. SAML provides distributed SSO functions on the Internet , allowing people to be identify in their own user management system and access distant resources (applications and data) using a unique and proven identity. Click the icon below to view the details. Back to the Radar Last revised:

39 SCORM - Sharable Content Object Reference Model 2004Abstract SCORM describes a technical framework that references a harmonized set of e-learning-based guidelines, specifications and standards. Internationally proven as a training technology, implementations have succeeded through use of a content model to ensure consistent run-time environment behaviours that manage and track distributed learning events across e-learning communities. SCORM is built upon the work of the Aviation Industry Computer-Based Training (CBT) Committee (AICC), the IMS Global Learning Consortium, Inc., the Institute of Electrical and Electronics Engineers (IEEE), the Alliance for Remote Instructional Authoring and Distribution Networks for Europe (ARIADNE) and others. It creates one unified "reference model" of interrelated technical specifications and guidelines that meet United States Department of Defense (DoD) high-level requirements for Web-based learning content and systems. South Korea’s Education Ministry has implemented SCORM across all grade levels to manage after-school tutorial programs. SCORM has proven to support a diversity of content and communities. Click the icon below to view the details. Back to the Radar Last revised:

40 STE100 - ASD Simplified Technical English - International specification for the preparation of technical documentation in a controlled language Abstract ASD-STE100 (European Community Trade Mark No ) is an international specification for the preparation of maintenance documentation in a controlled language. A controlled language is a form of language with special restrictions on grammar, style and vocabulary usage. It was developed in the early Eighties (as AECMA Simplified English) to help the users of English-language documentation to understand what they read. The ASD-STE100 provides a set of Writing Rules and a Dictionary of controlled vocabulary. The Writing Rules cover aspects of grammar and style; the Dictionary specifies the general words that can be used. These words were chosen for their simplicity and ease of recognition. In general, there is only one word for one meaning, and one part of speech for one word. In addition to the specified general vocabulary, ASD-STE100 accepts the use of company-specific or project-oriented technical words, provided that they fit into one of the categories listed in the Specification. Control of any additional specific vocabulary is, of course, the responsibility of the company or the project itself. Click the icon below to view the details. Back to the Radar Last revised:

41 STEP - Standard for the Exchange of Product model dataAbstract STEP provides a comprehensive set of internationally-agreed integrated information models to address the problem of exchanging, sharing and archiving product information across 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. Click the icon below to view the details. Back to the Radar Last revised:

42 STEP AP203 - Configuration controlled 3D design of mechanical parts and assembliesAbstract ISO :2011 specifies the application protocol for “Configuration control 3D design” edition 2. The following are within the scope of ISO :2011: Products that are mechanical parts and assemblies; Product definition data and configuration control data pertaining to the design phase of a product's development; Representation of an instance of a part in an assembly through its usage in a sub-assembly; Three dimensional shape representations of a part Geometric validation properties to allow the translation of geometric shape representations (advanced boundary representation and faceted boundary representation solids) to be checked for quality; Geometric and dimensional tolerances applied to geometric shape representations; Materials and their composition of chemical substance; Composite material structure and shape; Catalogue data characterized by property value pairs; Three dimensional presentation of product data: Technical drawings as two dimensional presentation of product data. The first edition has been published by ISO in 1994 and the second edition has been published by ISO in 2011, in a modular form. Click the icon below to view the details. Back to the Radar Last revised: 42

43 STEP AP209 - Multidisciplinary analysis and designAbstract In the context of Design/Analysis integration, STEP AP209 is a standard for exchange and long term archiving of information between iterative design and analysis stages of the product life cycle. First edition of STEP AP209 was published in 2001 under the name “Composite and Metallic Structural Analysis”. The primary intent of the standard is to combine CAD, CAE and PDM capabilities to enable sharing of PDM controlled composite and metallic design, analysis, and material properties information. Augmenting shared information between design and analysis, both disciplines have separate but related product definitions allowing support of independent configuration control between the disciplines. Transfer between CAD 3D shape and CAE analysis information may be bi-directional enabling the feedback of information in the iterative design/analysis environment. A second edition of STEP AP209, renamed “Multidisciplinary analysis and design” is in final stage of development with the DIS submitted end of June 2013. On top of its migration to the modular architecture, STEP AP209 ED2 has enlarged its coverage beyond the STEP AP209 ED1 classical Finite Element Analysis capabilities: CFD, mainly based upon the CGNS standard; Generalized structured and unstructured analysis and mesh capabilities, developed under the European Union GEM program; Complete discrete/continuous mathematical field representation capability, based upon the David Taylor Labs/Boeing DT-NURBS package. The result is that STEP AP209 ED2 will now address a much wider set of multi-disciplinary analysis and optimization problems. Click the icon below to view the details. Back to the Radar Last revised: 43

44 STEP AP210 Electronic Assembly Interconnect and Packaging DesignAbstract In 2001, ISO published the first edition of a STEP Application Protocol for Electronic Assembly Interconnect and Packaging Design (AP 210) as an International Standard. This Application Protocol (AP) provides the groundwork for significant advances in product data reuse and cycle time reduction by defining a standardized, computer-interpretable method for representing the design of: Assemblies with electrical content at multiple levels of product hierarchy, Assemblies being designed jointly by electrical and mechanical departments, Interconnect designed using layered abstraction, typically Printed Circuit Boards (PCBs). This AP achieves a significant breakthrough in re-usable component models, allowing component suppliers to provide 3D product models with electrical intelligence integrated with catalog data in a computer-interpretable neutral form for the first time. This achievement was reached through a coordinated effort involving numerous Fortune 500 companies and government organizations including Rockwell Collins Inc., Boeing, Delphi-Delco Electronic Systems, IBM, the US Naval Supply Systems Command RAMP Program Office, and NIST. A second edition of AP 210 based on STEP modules consistent with APs such as AP 203, AP 209, AP 233 and AP 239 is scheduled for publication in 2010. Click the icon below to view the details. Back to the Radar Last revised: 44

45 STEP AP212 - Electrotechnical design and installationAbstract AP 212 is an international standard that specifies data representation for the exchange and sharing of electromechanical plants and industrial systems design information. It addresses electrical product definition necessary to support electrical cable tray: current analysis, equipment, lighting, cable sizing, electrical connectivity checks and cable tray interference detection. This application protocol does not impose any restriction on the usage of these systems for particular applications - equipment for power-transmission, distribution, and generation, electrical machinery, electric light, electric heat, control and automation systems are all in scope. It was an initiative of the electrical industry and has being developed in cooperation with ProSTEP GmbH, with the help of the German Electrotechnical Committee (DKE) and with the cooperation of other industrial consortia, e.g. GOSET(F) and PDES Inc. (USA), and is standardized internationally as a joint effort of IEC/TC3 and ISO/TC 184/SC 4. The first edition has been published in 2001 by ISO and since then no further updates or preparation for a new edition have been requested by industry. Click the icon below to view the details. Back to the Radar Last revised: 45

46 STEP AP214 Core data for automotive mechanical design processesAbstract This application protocol is one of the relevant STEP APs available for ASD deployment (c.f. STEP blip for more information on this set of standards). STEP AP214 provides an integrated information models to address the problem of exchanging, sharing and archiving product information related to mechanical design process across dissimilar computer applications throughout the lifecycle of the product, including Product Data Management systems and Computer Aided Design tools dealing with different kind of geometrical representations and metadata allowing to describe product structure, document structure, configuration management information, change process information, effectivity information, person and organization, etc. Deployment of the STEP AP214 standard enables companies to have a proven single definition for all the product-related information used for mechanical design process, with different views on lifecycle phases considered by the designers. Click the icon below to view the details. Back to the Radar Last revised: 46

47 STEP AP233 - Systems EngineeringAbstract This application protocol is one of the relevant STEP APs available for ASD deployment (c.f. STEP blip for more information on this set of standards). STEP AP233 provides an integrated information models to address the problem of exchanging, sharing and archiving product information related to system engineering design process across dissimilar computer applications throughout the lifecycle of the product, including Product Data Management systems and Computer Aided Design tools dealing with different kind of system representations and metadata allowing to describe system structures, document structure, configuration management information, change process information, effectivity information, person and organization, etc. Deployment of the STEP AP233 standard enables companies to have a proven single definition for all the product-related information used for mechanical design process, with different views on lifecycle phases considered by the system designers. Click the icon below to view the details. Back to the Radar Last revised: 47

48 STEP AP235 Engineering properties for product design and verificationAbstract STEP AP 235 defines the context, scope, and information requirements for properties of products that can be used for product design and design validation, the testing, measurement and approval processes used to determine those properties and specifies the integrated resources necessary to satisfy these requirements. Considering that the value of an engineering property of a product is dependent on the process used to measure the property value and on the conditions used in that process, AP 235 provides the means to associate a property value explicitly to the conditions in which it was measured, and thus provide an audit trail to the origins of data values that can be used in product design. AP 235 enables to represent the relationships between the test piece, the sample and the original product, as the measurement procedure generally requires a representative test piece with specific shape and dimensions. AP 235 handles the method used to process the engineering properties from the testing results (e.g. central value and associated uncertainty). Click the icon below to view the details. Back to the Radar Last revised: 48

49 STEP AP239 - Product Life Cycle Support (PLCS), Edition 2Abstract 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. The required information includes product data management, task descriptions, operating states, planned and unplanned maintenance and complete historical records 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 libraries to configure the standard for operational use. Click the icon below to view the details. Back to the Radar Last revised:

50 STEP AP239 - Product Life Cycle Support (PLCS), Edition 3Abstract In 2015, a divergence risk was identified between the different versions of STEP PLCS (ISO AP239 ed1, ed2 and the corresponding OASIS PSM specification) and product support standards (AIA-ASD S-Series suite of ILS specifications, SAE). To solve this issue, a PLCS Edition 3 project was proposed to ISO end of 2015. Objective of this PLCS Edition 3 are to: Harness current product life cycle standardization efforts, such as ISO ed 1, ed 2, ASD/AIA S-Series, and SAE GEIA-STD-0007 as inputs in developing baseline requirements for ISO AP239 ed3. Ensure interoperability with AP242 and other STEP APs through the new STEP architecture. Incorporate requirements from implementation experience and the Product Support standards. The project has started in 2016, with the objective to deliver a Draft International Standard in 2018. Click the icon below to view the details. Back to the Radar Last revised:

51 STEP AP242 Managed Model Based 3D Engineering, Edition 1Abstract For 20 years a significant amount of effort has been made by the Aerospace and Automotive industry to develop two parallel STEP standards: AP 203 edition 1 was published in 1994, primarily driven by Aerospace and Defence requirements and developed and maintained by PDES, Inc. AP 214 edition 1 was published in 2001, driven primarily by automotive requirements, and developed and maintained by the ProSTEP iViP and SASIG organizations. The ASD SSG working jointly with ProSTEP iViP, and NIST working jointly with PDES, Inc. have identified an opportunity for a convergent AP, based on AP 214 edition 3 and AP 203 edition 2. As a response, a new project has been launched by ISO TC 184/SC 4: ISO in 2010. The main technical requirement for AP 242 ed1 is to become the cornerstone standard of the cross-process capabilities for interoperability of core engineering design information under configuration management, that is to say, Providing specifications for exchange and long term archiving, Providing a consistent business object model used for XML exchange and PLM web services, and Providing a data model for 3D tessellated model Click the icon below to view the details. Back to the Radar Last revised:

52 STEP AP242 Managed Model Based 3D Engineering, Edition 2Abstract STEP AP 242 edition 1 standard is the result of the convergence of STEP AP 203 ED3 and AP 242 ED3; this standard is described by a specific component summary: Application Protocol 242 “Managed Model Based 3D Engineering” edition 1. The industry has launched a project to increase the functionalities of the edition 1 to several domains. The goal is to consolidate the key role of STEP AP 242 as the backbone information model for Core 3D design information, covering progressively the different technical disciplines requested by the manufacturing industries. The main extensions of AP 242 edition 2 are for Electrical harness for design and construction, and for 3D additive manufacturing / 3D printing design information. Click the icon below to view the details. Back to the Radar Last revised:

53 SysML - Systems Modeling LanguageAbstract SysML is a standardized modelling language defined by International System Engineering community dealing with complex systems of systems, with a strong involvement of Aerospace&Defence industry. The focus is to support Computer Aided modelling of systems for requirements, analysis, design, verification and validation purpose, being specific system modelling applications independent (organization or used software product). This standard does not address only data interchange of data between applications, but also standardized visual modelling language dedicated to people producing system informational and behavioural models. It is achieve by defining it as a dialect (profile) of the second version of the Unified Modelling Language (UML2). This language can consequently be used for interchanging models between people, system modelling/simulation platform and information/models management systems. As all simulation and system modelling tools are not necessarily based on SysML, and as UML model interchange format (XMI) is still not very mature, SysML is also aligned with ISO STEP application protocol dealing with System Engineering (AP233), allowing interchange and long term archiving of data representing systems all along the phases of the lifecycle of complex systems of systems within Aerospace and Defence industry. Click the icon below to view the details. Back to the Radar Last revised: 53

54 TDP Message - Technical Data Package MessageAbstract The aim of the Technical Data Package Message project is to standardize the TDP message that will be used for TDP exchange processes and services related to online transportation of TDP, secured transfer, monitoring, history and acknowledgment procedure for product data import and export. Based on the more relevant existing PLM eBusiness standards and associated frameworks, the TDP message should be useable with legacy exchange protocols, standardized or not, and useable for any kind of exchange all along the phases of the lifecycle of a product. TDP transportation and TDP data exchange are fully decoupled. For this reason, TDP message and Product metadata are considered separately. It allows addressing very simply the transportation, being independent of the application protocol used for Product Meta Data. The product data exchange, related to product data import and export between PDM solutions and CAD/CAM/CAS tools is out of scope. Click the icon below to view the details. Back to the Radar Last revised: 54

55 TSCP - Transglobal Secure Collaboration ProgramAbstract 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 Last revised:

56 TSCP IdFv1 - Identity Federation v1Abstract 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. Identity Federation technologies have emerged that enable an organization to manage user identities locally whilst also providing authentication and authorization information to other organizations to enable access to their information resources and services. This requires the organization that authenticates the user (the Identity Provider or IdP) to securely assert a set of statements about that user to the organization which operates the service being accessed (the Relying Party or RP), and for those statements to be trusted. An agreed common set of attributes that are asserted about a user enables asserting organizations and receiving organizations to reuse the same assertion format with multiple partners. This common profile can reduce the time spent by partners negotiating what attributes to send, the definitions of those attributes, the technology used to pass the assertion and the syntactical formatting of the attributes. The TSCP IdF v1 Assertion Profile establishes a common identity federation Security Assertion Mark-up Language (SAML) profile for the Aerospace and Defense (A&D) industry. The goal of the IdF v1 Assertion Profile is to: Identify a common set of attributes (definitions and syntax) about an authenticated user, required to facilitate interoperability between Identity Providers and Relying Parties. Allow for equivalent attribute data to be passed via either the either the SAML 2.0 or WS-Fed Protocol. Click the icon below to view the details. Back to the Radar Last revised: 56

57 TSCP ILHv1- Identity Federation v1Abstract The TSCP Information Labeling and Handling v.1 specification (ILH) aims to mitigate the risks related to compliance by ensuring that information protection policy requirements are consistently codified. This is done by allowing information to be labeled with the consistent indication of all protection policies that must apply, and by enabling consistent systemic and procedural enforcement of such labeled information within applications. The ILH specification lays the groundwork for commercial-off-the-shelf (COTS) solutions to ensure consistent interpretation and enforcement of existing policies, regulations, contracts and licenses by instituting the following: Digital Policy Management: allows the analysis and capture of information protection requirements of all the required regimes, from human-readable forms to computer-processable forms. Information Labeling: allows organizations to label information with the indication of all the information protection requirements that must apply, consistent within and across organizations, supporting enforcement by human users as well as by automated protection mechanisms. Information Protection: allows automated protection of information in accordance with the applicable protection policies indicated by information labels. ILH provides consistent protection within as well as outside Document Management Systems (DMS) through Data Rights Management Systems. Click the icon below to view the details. Back to the Radar Last revised: 57

58 TSCP SEv1 - Secure Email v1Abstract 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. The TSCP Secure v1 specification allows organizations to send digitally signed and/or encrypted . About 49.6 billion messages (spam excluded) are sent every day worldwide. has become an indispensable part of the business fabric of every enterprise. Much of traffic generated by aerospace and defense companies and government organizations is sensitive and must be protected against eavesdropping. In addition, due to inherent security weaknesses in the Simple Mail Transfer Protocol (SMTP), the protocol of the Internet, it is easy to forge and modify messages. Attackers can make messages appear as coming from legitimate users or modify their content to suit their purposes. The TSCP Secure Specification is proposed to address these concerns. The TSCP Secure Specification v1 will be more widely implemented and used to provide confidentiality and integrity for exchanges, if the specifications and key supporting documentation are made publicly available and their usage is encouraged by adoption as industry specifications in Europe and the US. Click the icon below to view the details. Back to the Radar Last revised: 58

59 TSCP TF - Trust Framework for the Supply ChainAbstract The challenges involving securing the supply chain are far reaching, covering areas such as physical security and counterfeit parts to the electronic aspect of intrusion to company systems. Within the electronic area, there are many attack vectors intruders use. The TSCP Trusted Supply Chain Working Group is focused on Supply Chain identity assurance and improving the resilience to the associated attacks. Currently, there is little standardization for the Supply Chain on the strength of identity assurance, the credentials used for system access, or the processes to ensure it e.g. proofing, vetting, accreditation, certification, etc. The TSCP Trusted Supply Chain Working Group is currently evaluating the potential advantages of TSCP becoming a FICAM approved Trust Framework Provider (TFP) for the A&D industry which would include non PKI and PKI Levels of Assurance As part of this effort, a high priority has been set on developing a near term solution for major A&D companies to trust one another’s suppliers’ credentials if they meet agreed upon minimum levels of identity assurance. This will reduce credential redundancy, complexity and cost to both suppliers and their prime contractors. Included in this solution would be a legal trust mechanism to ensure legal agreements are clear and enforceable. Moving beyond this, the working group intends to investigate and build out additional trust framework elements. Click the icon below to view the details. Back to the Radar Last revised: 59

60 VDA 4968 VEC KBL “Kabelbaumliste” - Harness Description ListAbstract During the last years, the target of the VDA Working Group “Car Electric” (with participation of major OEMs and harness suppliers) is the improvement of the development process of vehicle electrical system and its integration into the entire vehicle development process. Therefore the concept of vehicle electric container, which contains all required parts of the electrical system, was developed, based on ISO “Electrical Design and Installation” standard. The Vehicle Electric Container (VEC) has four different parts: The Harness Description List (KBL; stands for "Kabelbaumliste”) The Electrical Logic (ELOG) The Component Model (KOMP) and The Geometry Model (GEO). The harness description list, which is described in the VDA recommendation 4964, was the origin and later extended by the other parts to the vehicle electric container. The KBL part contains: Harness, variants and modules Components Parts lists Connectivity lists Topology It is based on the STEP standard AP 212. Click the icon below to view the details. Back to the Radar Last revised: 60

61 VDA 4969 - Simulation Data Management in Integrated Collaborative CAD/CAE Process ChainsAbstract The C³I recommendation (VDA 4969), published by the German Association of the Automotive Industry (VDA) and the ProSTEP iViP Association, provides an open and commonly available description of requirements, processes and use cases for the cross-enterprise and cross-domain integration of simulation and computation. It builds on the “Integration of Simulation and Computation in a PDM Environment (SimPDM)” recommendation (VDA 4967). It defines processes, relations and use cases which fulfil the requirements regarding communication and integration. This covers cross-enterprise and cross-domain scenarios as well as the interaction between authoring tools and data management systems. The recommendation also gives standardized definitions of CAE process modules and simulation data management (SDM) core functionalities. In order to enable system support, the recommendation also defines a general metadata model and describes possible system extensions. The C3I metadata model is designed in a modular way to allow custom tailoring of solutions, and a mapping to existing data formats is given to illustrate how established interfaces can be extended to fulfil the requirements described in this recommendation. The recommendation does not define an interchange format between different CAE applications. Click the icon below to view the details. Back to the Radar Last revised: 61

62 XPDL - XML Process Description LanguageAbstract The XML Process Description Language is the format for storing and interchange workflow models that can be executed by Workflow systems as specified by Workflow Management Coalition. It is aligned with the Object Management Group’s Business Process Modelling Notation (c.f. BPMN Blip), which is a visual process notation standard endorsed by Wfmc, and broadly adopted across the industry. Knowing that numerous Product Data Management Systems include a workflow execution component, which allows controlling data through change management process, XPDL is a mean to interchange PLM workflow process models between PDM systems. Click the icon below to view the details. Back to the Radar Last revised: 62

63 No blip available Back to the Radar Sorry!ASD SSG plans to provide a blip for this component standard in one of the next Radar Chart versions. Back to the Radar 63