© The ATHENA Consortium. CI2: The ATHENA Interoperability Framework Module 3: Collaborative Product Development Scenario Aeronautics and Aerospace Sector

2 © The ATHENA Consortium. Scenario Description Interoperability Issues Architecture of Solutions Collaborative Product Development This unit is structured as follows:

3 © The ATHENA Consortium. Scenario Description Business context Involved actors Process Engineers Person responsible for data package Operational data exchange team 2 Operational Exchange Team member EAI PDF Manu f. PDF Airbu s Operational Exchange Team member

4 © The ATHENA Consortium. Aeronautics and Aerospace Sector The aeronautics sector is a vital asset for Europe’s economic and social prosperity. Provides employment for 3.1 million people.

5 © The ATHENA Consortium. EADS Group This scenario is based on the experience of EADS Group business units, including: Airbus EADS Space Transportation ASTRIUM and Eurocopter

6 © The ATHENA Consortium. Collaborative Product Development Scenario L.T. Archiving International Product Data Standards M S E OEM PRODUCT DATA M anufacturing S upport E ngineering Equipments Supplier Engine Supplier Engine Supplier Global Supplier Engine Supplier Equipments Supplier Global Supplier Engine Suppliers Equipments Supplier Global Supplier Risk-Sharing Partner Service Suppliers Level 1 Level 2 Level 3 Supplier Military Agencies Civil Airlines Mil. Agency Manuf. Supplier Airlines Manuf. Supplier Configured & Controlled Product Data for: > Design > Simulation > Manufacturing & > Support

7 © The ATHENA Consortium. Product Data Management (PDM) Product Data Management (PDM) are software applications that are enhancing Product Data Sharing between all the actors involved in the design, manufacturing and support process. Early involvement of down stream activities using the virtual aircraft Concept Definition Production Support CONCEPTDEFINITION DEVELOPMENT SERIES FEASABILITY

8 © The ATHENA Consortium. Organisations Within this scenario we consider the PDM Coupling process of two organisations: The industrial integrator (AIRBUS) Manufacturer

9 © The ATHENA Consortium. Actors We will consider three different participants: Operational data exchange team Person responsible for data package Engineers

10 © The ATHENA Consortium. “As-is” and “To-be” Process “As-is” process reflects the current situation with its interoperability problems. “To-be” process reflects the envisaged ideal situation in which Interoperability problems don’t exist.

11 © The ATHENA Consortium. PDM Coupling: “As-is” Process PDM AIRBUS PDM Manufacture r Engineer Data Package responsible Operational Exchange Team member Operational Exchange Team member

12 © The ATHENA Consortium. PDM Coupling: “To-be” Process PDM AIRBUS PDM Manufacture r Engineer Data Package responsible Systems are integrated/coupled Enterprise Application Integration (EAI) Operational Exchange Team member 1212 Operational Exchange Team member EAI

13 © The ATHENA Consortium. PDM Coupling: “To-be” Process “To-be” Process End-user point of view 11

14 © The ATHENA Consortium. PDM Coupling: “To-be” Process PDM AIRBUS PDM Manufacture r “To-be” Process Operational Exchange Team Point of View 1212 Operational Exchange Team member 1313 Operational Exchange Team member EAI

15 © The ATHENA Consortium. PDM Coupling: “To-be” Process PDM AIRBUS PDM Manufacture r “To-be” Process IT Department Point of View 1414 IT Department EAI

16 © The ATHENA Consortium. Interoperability Issues Interoperability issues are problems concerning interoperability extracted from analysis of business scenarios.

17 © The ATHENA Consortium. Business Category Interoperability Issues Neutral standards to prepare negotiation between the different actors Integration of heterogeneous tools (cost control, system engineering, etc.) Linking programme, product and enterprise viewpoints

18 © The ATHENA Consortium. Knowledge Category Interoperability Issues Knowledge capture, assimilation and management Product-related knowledge sharing between product life cycle phases Integration of the relevant industrial sector, ICT, and enterprise-modelling models Establishment of knowledge management standards and best practices

19 © The ATHENA Consortium. Software Category Interoperability Issues (1) Independence between business logic and technical solutions Easy customisation of the software product and technical interfaces Auto-descriptive applications

20 © The ATHENA Consortium. Software Category Interoperability Issues (2) Internal information model of software products based on standards Application interfaces and service description according to standards Coherent support of the main technical software platform

21 © The ATHENA Consortium. Architecture of Solutions Data Enterprise Processes Services Data CM II Executable Cooperative Configuration Management Processes CBPS Wfmc Published PLM Services OASIS PLCS OMG Mantis Information Repositories STEP Enterprise Processes Services Data

24 © The ATHENA Consortium. This course has been developed under the funding of the EC with the support of the EC ATHENA-IP Project. Disclaimer and Copyright Notice: Permission is granted without fee for personal or educational (non-profit) use, previous notification is needed. For notification purposes, please, address to the ATHENA Training Programme Chair at In other cases please, contact at the same e_mail address for use conditions. Some of the figures presented in this course are freely inspired by others reported in referenced works/sources. For such figures copyright and all rights therein are maintained by the original authors or by other copyright holders. It is understood that all persons copying these figures will adhere to the terms and constraints invoked by each copyright