1 Digital threads in industry based on PLM open standards ______ STEP AP 242 ISO :2014 Managed Model Based 3D Engineering Jean Brangé – AFNeT ISO Project Leader for AP242 edition 2

2

3 STEP landscape before AP242 Concept Simulation Definition Manufacturing Support Process & use cases Information Shared PDM repository PLCS DEX’s Systems Engineering AP233 Product Lifecycle Support AP239 PDM schema Configuration controlled 3D design AP203 Analysis AP209 Core data for automotive mechanical AP214 Qu’est ce qu’un Protocole d’Application ? Le standard STEP est divisé en plusieurs Protocoles d’Application qui appartiennent à la famille des normes ISO Chaque protocole définit un standard d’échange de données pour une famille de produit définie, à une étape donnée de leur cycle de vie. Les Protocoles d’Application les plus populaires concernant la CAO sont l’AP203, aussi connu sous le code ISO , et l’AP214, aussi connu sous le code ISO Le Protocole d’Application STEP-NC possède le code ISO (AP238). D’autres Protocoles d’Application définissent des standards d’échange de données pour des produits spéciaux tels que les navires (AP216) et les cartes de circuits imprimés (AP210), et pour des étapes différentes de cycle de vie comme le plan des processus pour produits usinés (AP240) et l’échange d'information par vérification dimensionnelle (AP219). Comment un Protocole d’Application est-il défini? Chaque Protocole d’Application inclut un périmètre décrivant son usage, un diagramme d’activité décrivant les fonctions qu’un ingénieur nécessite pour travailler dans le cadre de ce périmètre, et un Application Requirement Model (ARM) décrivant les besoins en informations de ces activités. Ces besoins d’informations sont ensuite mappées vers l’ensemble commun des Ressources Intégrées (Integrated Resources) et le résultat est un standard d’échange de données pour les activités du périmètre défini. Comment les Protocoles d’Application partagent-ils les données ? Les Protocoles d’Application définissent souvent des informations similaires. L’architecture STEP supporte ce partage en cartographiant chaque modèle de protocole (ARM) vers l’ensemble commun des Ressources Intégrées pour produire l’Application Interpreted Model (AIM). L’AIM est le modèle implémenté par les systèmes d’échange de données et est la clé pour le partage de données car il utilise la même définition pour le même concept pour tous les Protocoles d’Application. Ainsi un système d’échange qui implémente un code pour traiter ces données dans un contexte donné, peut utiliser le même code pour traiter les données dans n’importe quel autre contexte. Qu’est-ce EXPRESS ? EXPRESS est un langage utilisé pour définir le modèle AIM et la plupart des modèles ARM. EXPRESS a été défini pour modéliser la géométrie, il a donc un mécanisme d’héritage très puissant et la capacité de décrire des contraintes mathématiques complexes. Cette habilité est plus que nécessaire pour la plupart des applications, cependant, EXPRESS est rarement utilisé pour des applications autres que la modélisation de produit. Electronic assembly, interconnect, and packaging design AP210

4 STEP in the product lifecycleModify Design of Realized Product Analyse Product AP235 AP209 AP210 AP242 AP209 AP210 simulation request results ECR, ECO product design as modified Design Product Manufacture / Deliver Product Modify Realized Product AP242 AP209 AP210 AP242 AP238 AP235 AP239 Systems Engineering product as designed ECR, ECO product as manufactured/ delivered product as maintained product as required ECR, ECO AP233 Design Product Support Solution Product Support Process AP239 AP239 Product Operation AP239

5 Managed Model Based 3D EngineeringAP242 in the STEP landscape Concept Simulation Definition Manufacturing Support Process & use cases Information Shared PDM repository PLCS DEX’s Systems Engineering AP233 Product Lifecycle Support AP239 Managed Model Based 3D Engineering AP242 PDM schema Configuration controlled 3D design AP203 Multidisciplinary Analysis and Design AP209 Core data for automotive mechanical AP214 Electronic assembly, interconnect, and packaging design AP210 Formation STEP

6 AP242 is an answer to key business needsCompatible with existing scope of AP203ed2, AP214ed3, AP239 and LOTAR A detailed documentation to facilitate the standard appropriation Interoperability for exchange and sharing of CAD and PDM Extended enterprise Life cycle support Shared PDM solutions Customer 3D Model based design Long term archiving Domain integration (Engineering analysis, Manufacturing simulation, Inspection planning, etc) Supplier data exchange Data sharing on SOA basis Engineering visualization Service provider for exchange and sharing Manufacturer Supplier Formation STEP

7 AP242 is the fusion of AP203 and AP214, augmented with new functionalitiesThe AP242 standard The scope and foundations of the AP 242 standard has been defined in the White Paper "Development of a Convergent Modular STEP Application Protocol Based on AP 203 and AP 214:  STEP AP 242 – Managed Model Based 3D Engineering" , Version 1.0, 2009‐11‐05. The STEP  AP 242 standard  is managed by ISO \TC 184 \SC 4 as ISO AP 242. The purchase of such standard, when released, can be done via the national standardization bodies. It is developed in a in a phased approach, in several editions, according to business requirements and agreed project plans (scope, resources, time, quality) for coverage of the Managed 3D Model Based Engineering process, as illustrated by the next figure. Overall planning of AP 242 edition 1 and edition 2: The development of AP 242 edition 1 has started mid of 2010 and is planned to become “International Standard” Q The aerospace and automotive industries are preparing the scope and project plan of AP 242 edition 2 (anticipated to start Q and to become IS  Q4 2016). The detailed planning is given by the following figure.

8 AP242 edition 1 scope

9 AP242 Business Object Model capabilitiesAP214 BOM is based on a set of capabilities, organized according this figure. 

10 PDM concepts of AP242 Business Object Model

11 AP242 Business Object Model as a whole

12 Typical Use cases Formation STEPExamples of PDM interop associated use cases -          Interoperability between different systems   PDM - PDMPDM configured product structure exchange with the supply chain (full structure)PDM - PDMPDM configured product structure exchange with the supply chain (incremental)PDM - CADCAD assembly structure interchangePDM - ERPERP feeding (e.g Bill of Material export) with the supply chain 
- Long Term Archiving and Retrieval (LTA&R): - LTA&R of a PDM "As designed" resolved Product Structure with effectivities
- LTA&R of a PDM "As built" resolved Product Structure with effectivities - Visualization of archived PDM configured product structure information List not exhaustive: for more information refer to the CAX IF use cases and the STEP AP 242 use cases described by the respective industry associations. Dependancies / related standards STEP AP 242 PDM data model is based on the convergence of STEP AP 203 and STEP AP 214, and is also shared with STEP AP 209, AP 210, AP 233, AP 239, (list not exhaustive).
Final activities are carried out in 2013 to ensure the PDM harmonization of STEP AP 242 Business Object Model and STEP AP 239 PLCS Platform Specific Model (PSM). Status of availability of COTS solutions STEP AP 242 standard will support 2 implementation formats: “Part 21 AIM” format, consistent with the previous implementation format of STEP AP 203 and AP 214 standards “Part 28 XSD” format, based on XML, common with STEP AP 239 PLCS PSM. Related recommended practices In parallel of the 2 implementation formats, there will be 2 categories of PDM recommended practices for AP 242: Recommended practices for PDM interfaces based on “Part 21 AIM” format - PDM schema usage guide - Link to the CAX-IF recommended practices page : Future recommended practices for for PDM interfaces based on “Part 28 XSD” format - In preparation, with the planned start of the international PDM Implementer Forum in semester 1, 2014. Formation STEP

13 Bi-directional mappingAP242 exchange models Mixte Scenarios Scenario 1: Exchanges based on compressed ASCII files with all CAD and PDM information in one package Exchange based on monolithic express file Part 21/26/28 Based exchanges Data Repository Import / Export PDM + CAD obj. Scenario 2: exchanges based on ASCII compressed file for CAD and XML files for PDM data ASCII and XML files are linked by external references The mapping between XML and Express objects is bi-directional PDM obj. PDM obj. Bi-directional mapping Part 21/26/28 Based exchanges Data Repository XML Schema based excnahges PDM obj. CAD obj. External ref. TDP Import / Export Exchange based on shuttered xml (for PDM) and express (for geometry) files exchange Part 21: Implementation methods: Clear text encoding of the exchange structure Part 26: Implementation methods: Binary representation of EXPRESS-driven data: specifies a binary representation of EXPRESS-driven data using the Hierarchical Data Format Version 5 (HDF5). Part 28: Implementation methods: XML representations of EXPRESS schemas and data, using XML schemas: specifies the way in which an XML representation described by an XML schema can be used in the exchange of data that is described by an EXPRESS schema. TDP: Technical Data Package

14 Bi-directional mappingAP242 exchange models Mixte Scenarios for Hubs Exchanges are realized through an on-line shared PDM hub Queries, updates , TDP creation/extraction are managed by a hub AP242 data exchange with a HUB scenario example XML Schema based transactions TDP Read/write queries PDM obj. Manufacturer data repository Shared Repository External ref. Supplier data repository CAD obj. CAD obj. PDM obj. TDP Part 21: Implementation methods: Clear text encoding of the exchange structure Part 26: Implementation methods: Binary representation of EXPRESS-driven data: specifies a binary representation of EXPRESS-driven data using the Hierarchical Data Format Version 5 (HDF5). Part 28: Implementation methods: XML representations of EXPRESS schemas and data, using XML schemas: specifies the way in which an XML representation described by an XML schema can be used in the exchange of data that is described by an EXPRESS schema. External ref. Import / Export Part 21/26/28 Based exchanges Part 21/26/28 Based exchanges PDM obj. PDM obj. Bi-directional mapping

15 Annexes

16 AP242 ISO Definition This part of ISO specifies an application module for the representation of engineering data and product data that is based on a three dimensional model. ISO is supplemented with a Business Object Model Module. That module contains the ISO Business Object Model consisting of an information model which is on a high level of granularity and thus is suited for the communication with and understandability by domains experts of Aerospace and Defense and Automotive. It consists of Business Objects representing major concepts and information requirements of Model Based 3D Engineering in these domains and uses the vocabulary of the STEP modules where this vocabulary reflects the terminology of the domain experts. The relationship between the Business Object Model and the ARM of AP 242 is explained in the Business Object Model Module document. A technical discussion of the business object model is contained in Annex H of ISO Formation STEP

17 Why a new AP Opportunity to reduce AP203 and AP214 developement costsAutomotive and Aerospace together: opportunities to enhance the STEP Application Protocoles Opportunity to reduce AP203 and AP214 developement costs AP242 covers all functions of AP203 ed2 and AP214 ed3 AP242 includes new functions Better PMI Composites 3D parametric geometry Information rights management Software Data quality A new data model to ease the use of STEP with web technologies Situation Chevauchement de l’AP 203 et 214 (env. 75%) Deux standards : diffusion coûteuse et contraignante La filière aérospatiale a besoin d'un standard pour l’archivage long terme et pour l'intégration des fournisseurs le long du cycle de vie (entretien) L’automobile a besoin d’améliorer les fonctionnalités actuellement disponibles Proposition de projet Fusion de l’AP203 et 214, conduite par les parties prenantes Europe / Asie: ProSTEP iViP, ASD-STAN, JAMA, VDA USA: PDES Inc., AIA, NIST Industrie: EADS, BoostAeroSpace, Boeing, Lockheed Martin, Rockwell Collins PMI : Product and Manufacturing Information

18 Data exchange & sharingAP242 answers the challenges ot PLM and extended enterprise A – PLM functions 1 2 3 4 PLM domains CAO 2D CAO 3D DMU PPR Co-Innovation Collaboration modes Co-Design Co-Review Subcontracting Data exchange & sharing Virtual plateau Portal Plans CAO files CAO files STEP files Physical plateau We can distinguish several stages of maturity in the collaboration according to characteristics such as: the collaboration mode : sequential or concurrent the cycle time for one iteration of the information the status of information when it is shared : in progress, validated, approved the type of the information: documents or drawings, 2D or 3D models, product structure (BOM) the format of the information: native or standard (IGES, DXF, SET, STEP, ...) the system used: single system, two homogeneous systems, two or more disparate systems... Of course, all the different combinations of characteristics are possible, even if they are not all relevant, but the most frequently encountered profiles today are: Drawings exchanges between identical CAD systems Drawings exchanges between heterogeneous CAD systems using a standard Physical plateau : Subcontractor is working on OEM system at the OEM premises Virtual Plateau : Subcontractor is working, from his own premises using a network, on OEM Plateau which is located at the OEM premises, with the same technologies as private OEM system, but physically separate On the Cloud Collaborative HUB : OEM, Partners and Subcontractors are working together on a shared PDM which is located on the Cloud and which is interoperable with their own systems using standards 1970 1985 1995 2000 Internal design 1 Subcontractor participation 2 Virtual plateau OEM - T1 3 Virtual plateau OEM - T1 + T1 - Tiers n 4 Supplier Risk Sharing Partner B – Extended enterprise integration

19 Géométrie Assemblage AP242 functions 3D CAD Interoperability (1/2)Géométrie 3D exacte explicite Géométrie 3D tessellée explicite 3D parametrique & historique de constr. Assemblage Overview of STEP AP 242 functionalities for CAD 3D Geometry , assembly  and PMI interoperability Here, the objective is to provide an overview, from the users perspective, of the STEP AP 242 functionalities for 3D CAD interoperability. It is summed up according to the following paragraphs:
            - Overview and illustration of capabilities
            - Examples of associated use cases
            - Dependencies / related standards
            - Status of availability of COTS solutions
            - Status of recommended practices / implementers forums Overview and illustration of capabilities: Geometry -Exact shape representation, which is use in the current CAD tool implementing in STEP AP214 and STEP AP203 -Tessellated shape representation. This representation is new in STEP. It allows display efficiently the 3D shape by using a simplified representation (example: triangulated faces). The STEP tessellated representation allows to have topological information (example: face is a collection of triangle) -Parametric representation: Representation allowing  the preservation of the parameter and the construction history  Assembly External element reference: this mechanism allows a reference to a specific geometric element thought an assembly in several files. Example: constraint between 2 faces of different models. Example of associated use cases - Interoperability between different systems  CAD-CAECAD 3D design geometry to/from Engineering Analysis CAD-CADCAD 3D geometry with PMI and assemblies exchange with the supply chain CAD-CAMCAD 3D with PMI "semantic" exchange for down stream reuse  -  Long Term Archiving and Retrieval (LTA&R): o        LTA&R of CAD 3D  PMI "graphic" for certification
 o        LTA&R of CAD 3D with PMI "semantic" design for manufacturing and repairs Visualization of archived CAD 3D tessellated geometry Note: the list is not exhaustive. For more information, refer to the CAX IF use cases and the STEP AP 242 use cases described by the respective industry associations. Dependencies / related standards STEP AP 242 CAD 3D geometry data model is based on the convergence of STEP AP 203 and STEP AP 214, and is also shared with STEP AP 209, AP 210, AP 238 standards (list not exhaustive)  Status of availability of COTS solutions For more details, reference to the CAx IF web site, page “implementation coverage”: Related recommended practices STEP recommended practices for CAD 3D geometry: CAx Implementer Forum: Géométrie de l’assemblage et des composants dans le même fichier Assemblage avec référence externe vers un fichier de géométrie 3D Assemblage distribué Formation STEP

20 PMI AP242 functions 3D CAD Interoperability (2/2)Product and Manufacturing Information Dimensionnement & tolérancement géométrique 3D Annotations 3D Symboles 3D Représentation graphique Représentation sémantique Overview and illustration of capabilities (continued): PMI -Graphic representation
The advantages of graphical Presentation are that since it is rendered, it is presented in the STEP file exactly as it was in the CAD system. Since the instantiation is done using basic geometric entities, basically every viewer or CAD system which finds the link in the file structure can display it.
The PMI is stored in STEP using geometric entities:
 - polylines (points, curves,…) , already use in STEP AP214
 - or tessellated , new in AP242 §         -Semantic representation
The PMI is stored in the file with the PMI semantic entities. It captures the semantic of the Geometric Dimension and Tolerance. After exchange, it allows the interpretation and the modification like in the native CAD system (ISO and ASME PMIs). Example of associated use cases - Interoperability between different systems  CAD-CAECAD 3D design geometry to/from Engineering Analysis CAD-CADCAD 3D geometry with PMI and assemblies exchange with the supply chain CAD-CAMCAD 3D with PMI "semantic" exchange for down stream reuse  -  Long Term Archiving and Retrieval (LTA&R): o        LTA&R of CAD 3D  PMI "graphic" for certification
 o        LTA&R of CAD 3D with PMI "semantic" design for manufacturing and repairs Visualization of archived CAD 3D tessellated geometry Note: the list is not exhaustive. For more information, refer to the CAX IF use cases and the STEP AP 242 use cases described by the respective industry associations. Dependencies / related standards STEP AP 242 CAD 3D geometry data model is based on the convergence of STEP AP 203 and STEP AP 214, and is also shared with STEP AP 209, AP 210, AP 238 standards (list not exhaustive)  Status of availability of COTS solutions For more details, reference to the CAx IF web site, page “implementation coverage”: Related recommended practices STEP recommended practices for CAD 3D geometry: Associated CAx Implementer Forum: Formation STEP

21 AP242 functions : Machining Form Features InteroperabilityExamples of associated use cases -          Interoperability between different systems   CAD-CAMCAD 3D with machining form features exchange for down stream reuse CAD-CAMCAD 3D with machining form features exchange with the supply chain for part manufacturing  -          Long Term Archiving and Retrieval (LTA&R): o        LTA&R of CAD 3D with PMI and machining form features for manufacturing and repairs·         Visualization of archived CAD 3D with PMI and machining form features List not exhaustive: for more information refer to the CAX IF use cases and the STEP AP 242 use cases described by the respective industry associations Dependencies / related standards The data model of STEP AP 242 for machining form feature is consistent with STEP AP 224 “Mechanical product definition for process plans using machining features” and with STEP NC …  Status of availability of COTS solutions Prototypes in development in different international R&D projects. More information to be published in 2014.  Related recommended practices STEP recommended practices for CAD 3D geometry: Associated CAx Implementer Forum:

22 AP242 functions : Composite Design InteroperabilityContour & surface Solide 3D tessellé Composite Assembly STEP AP242 is the convergence of STEP AP203 and STEP AP214. AP242 covers the definition of the shape and structure of composite structural materials. This subject was already covered by the STEP AP203 edition 2, however AP242 adds the new capability to represent 3D tessellated shape representation of each ply. Another new capability for sharing composite structures information in the AP242 standard is the EXPRESS-based business object model (BO Model) and the XML schema derived from it. The illustration below presents Business Objects representing major concepts such as Plies/Ply pieces, Core, Filaments, Sequences, Material Properties and Orientation (Rosette).  Examples of associated use cases Interoperability between different systems CAD-CADCAD 3D composite design exchange with the supply chain CAD-CAECAD 3D composite design to Engineering Analysis CAD-CAMCAD 3D composite design to Manufacturing  - Long Term Archiving and retrieval (LTA&R) LTA&R of CAD 3D composite design for certification LTA&R of CAD 3D composite design for manufacturing and repairs Visualization of archived CAD 3d composite design information Note that this list not exhaustive: for more information refer to the CAX IF use cases and the STEP AP 242 use cases described by the respective industry associations   Dependencies / related standards The data model of AP 242 for CAD 3D composite design is based on STEP AP 203 and STEP AP209. Status of availability of COTS solutions Beta version interfaces for CAD composite design are in test for different systems. More information will be published in 2014. Related recommended practices STEP recommended practices for CAD 3D Composite design: draft available: link Associated CAx Implementer Forum for Composite design: planned to start in 2014. Formation STEP

23 AP242 functions : Kinematics InteroperabilityExamples of associated use cases -          Interoperability between different systems   CAD-CADCAD 3D kinematics exchange with the supply chain  -          Long Term Archiving and Retrieval (LTA&R): o        LTA&R of CAD 3D kinematics for reuse and support in operation ·         Visualization of archived CAD 3D kinematics information List not exhaustive: for more information refer to the CAX IF use cases and the STEP AP 242 use cases described by the respective industry associations Dependancies / related standards The data model of AP 242 for CAD 3D kinematics is based on STEP AP 214. Status of availability of COTS solutions Beta version interfaces for CAD 3D Kinematics are in development for different systems.
More information to be published in 2014.  Related recommended practices STEP recommended practices for CAD 3D kinematics: under development Associated CAx Implementer Forum: start planned in 2014 Formation STEP

24 AP242 functions : Requirement InteroperabilityExamples of associated use cases - Interoperability between different systems:    RM - RM Requirement management exchange in the supply chain  RM - SM Requirement management exchange between a RM system and a SM system  RM - PDM  Requirement management exchange between a RM system and a PDM system  RM - SLM Requirement management exchange between a RM system and a SDM system - Long Term Archiving and Retrieval (LTA&R):        LTA&R of a requirement structure for reuse and support in operation - Visualization of archived  requirement management information List not exhaustive: for more information refer to the CAX IF use cases and the STEP AP 242 use cases described by the respective industry associations Nota: RM : Requirement Management - SM: Systems Modeling - SDM: Simulation Data Management Dependancies / related standards The data model of AP 242 for Requirement management is based on STEP AP 233 “Systems Engineering”, harmonized for this scope with STEP AP 239 PLCS. The requirement management capability of STEP AP 214 is included in STEP AP 242; the STEP AP 242 standard has therefore interrelations / synergies with the OMG ReqIF standard and its associated implementer forum. Status of availability of COTS solutions Prototypes in development in different international R&D projects.
More information to be published in 2014. Related recommended practices STEP recommended practices for Requirement management: draft available as part of the different international projects.
Associated STEP Implementer Forum for Requirement management : planned to start in 2014 / 2015. Formation STEP

25 High level view AP 242 PDM Business Object ModelProduct Specification Physical structure Activity Work Management Identification Classification Configuration Part, Version, View identification Requirement Name & Description Multi Linguism Document structure Geometric Shape Property Material Effectivity Transformation Breakdown Information Right Process Plan Delta Change Person ,Organization & Address Part Occurrence Assembly Structure Date & Time Approval, Contract & Project

26 Activity diagram for AP242 1/2Formation STEP

27 Activity diagram for AP242 2/2Zoom in « Concept Development » activity Formation STEP