1. 1 AeroSpace and Defence Industries Association of Europe Technical Data Package (TDP) Project – Current Status – Transportation of Technical Data Package using a standardized TDP Message 10th of March, 2009

2. Slide 2 TDP Project – Overview & Status – March 2009 Current Status of the Project Current Status Kick Off: December 2008 Based on regular Teleconferences & Working Sessions Participants: EADS-MAS (+ project lead), EADS IW, AFNet, Boost International Interest “high” / Participation “low” Work Package status: WP2.2 / WP 2.3 are in work, WP 2.3 and WP3 under preparation Input / BPs: Boost, Seine, Eurofighter Typhoon (EADS-MAS), Astrium France Communication with OASIS PLCS Community (PLCS Teleconfs) Objective: Creation of international DEX (OASIS PLCS) (TDP Project internally – or by external support, e.g. OASIS/PLCS Community, Eurostep France, Jotne EPM Technologies Norway)

3. Slide 3 TDP Project – Overview & Status – March 2009 TDP Project – Rough Planning Original Timescale – Planning at ASD SSG meeting #2 Kick Off: November 2008 April: MS1 >> Ballot End: June 2009 Potential prototype: between EADS-MAS and Airbus (DXM) Timescale – “Now” Kick Off: December 2008 Ballot: approx. May/June 2009 End: approx. July 2009 Potential prototypes: PHENIX (HUB pilot to be used for TDP purposes), EADS IW demonstrator

4. Slide 4 TDP Project – Overview & Status – March 2009 TDP Project Definition of Work Packages WP1 – TDP Project Management WP1.1Agreement on Deliverables & Benefits WP1.2Clarification/Estimation of Resources WP1.3Way of working (T-Cons, Team Work, Meetings) WP1.4Work Packages Definition WP1.5Communication/Commitment PLCS, OASIS and Industry WP2 – Evaluation of “TDP Message” best practices WP2.1Present & Document company individual BP incl. Attributes (1 MD per company + T-Con) WP2.2Identification of common BP methods / Consolidation of attributes (4 MD + 1 MD per company + T-Con, distribution of material before T-Con) WP2.3Definition of functional requirements as input for the DEX (4 MD + 1 MD per company + T-Con or Meeting, distribution of material in advance)

5. Slide 5 TDP Project – Overview & Status – March 2009 TDP Project Definition of Work Packages WP3 – Definition of standardized “TDP Message” WP3.1Business Process Description for DEX on TDP Message (PLCS expert + 2MD per company) WP3.2Concrete specification of each attribute (PLCS expert + 1MD per company) WP3.3Create/Formalise OASIS PLCS DEX document (PLCS expert + 1MD per company / communication management by project lead) Note >> PLCS expert: 10 MD – max. 20 MD WP4 – Pilots/Demonstration WP4.1Develop Pilot(s) WP4.2Analysis of Pilot testing WP4.3Promotion MS1 – Ballot

6. Slide 6 TDP Project – Overview & Status – March 2009 week 08 TDP Project Roadmap “as planned” week 51week 52week 01week 02week 03week 04week 05week 06 December 08January 09February 09 WP2.1 Present & Document BPs 11.12 week 50 WP1 TDP Project Management Contains: Agree on Deliverables & Benefits Resources Requirements Way of Working (incl. T-Cons) WP Definition Communication & Commitment PLCS, OASIS and Industry WP2.2 Common BPs & Attributes Consolidation WP2.3 Define functional Requirements >> input for DEX week 07 week 09 29.01 12.02 19.01 End of Feb 09 finish WP2 start WP3 including: TDP Message Attributes

7. Slide 7 TDP Project – Overview & Status – March 2009 TDP Project Roadmap “as is & current forecast” December 08January 09February 09March 09April 09 WP2.1 Present & Document BPs 11.12 WP1 TDP Project Management Contains: Agree on Deliverables & Benefits Resources Requirements Way of Working (incl. T-Cons) WP Definition Communication & Commitment PLCS, OASIS and Industry WP2.2 Common BPs & Attributes Consolidation WP2.3 Define functional Requirements >> input for DEX 29.01 06.03 19.01 Mar / Apr 09 finish WP2 start WP3 including: TDP Message Attributes WP3 Definition TDP Message >> DEX

8. Slide 8 TDP Project – Overview & Status – March 2009 More information Dedicated website for TDP Project Including all project related material – BPs, Studies, MoM, etc. … Open for anybody willing to have information or to contribute To get access please contact: Melanie Baudisch EADS-MAS

9. Slide 9 TDP Project – Overview & Status – March 2009 File(s) TDP Transportation Process “Data Exchange” -Standardized TDP Message -TDP structure -Monitoring and history -Online transportation of TDP -Secured transfer -Acknowledgement Procedure for product data import/export - … Product Meta Data File 1 File 2 File 3 Scope of Technical Data Package Brief Overview TDP TDP Message Product Meta Data Product Data Product Data Exchange “PLM/PDM world” -Product data import/export -Data format: STEP AP214/AP203, part21/part28 … -Consideration of all kind of possible exchange scenarios … import export

10. Slide 10 TDP Project – Overview & Status – March 2009 Scope of Technical Data Package Requirements Technical Data Package (TDP) Definition - TDP can be regarded as a “container / carrier file”, which collects all relevant data for file transmission - TDP is a set of product data (1-n digital files) product meta-data (1 digital file) data dispatch note (TDP message) TDP Message For a minimum shall provide information on sender, receiver & list of all digital files of the TDP in order to support automatic routing, acknowledgment and validation of transportation of the TDP and its content (further TDP Message attributes to be defined) Currently out of scope: product meta-data provides information to allow import of its meta-data and related TDP product data into the receiving target system TDP TDP Message Product Meta Data Product Data

11. Slide 11 TDP Project – Overview & Status – March 2009 Technical Data Package (TDP) Requirement A Standardized TDP Message >> including a minimum set of required and commonly defined attributes Requirement B TDP transfer process must be independent of the product meta-data & associated product data import/export process >> in order to support any way to define the product meta-data format (e.g. Step AP214/AP203, part21/part28) >> TDP transfer and product data exchange between systems are two different needs and distinct processes, but have to be consistent and harmonized Scope of Technical Data Package Requirements TDP TDP Message Product Meta Data Product Data

12. Slide 12 TDP Project – Overview & Status – March 2009 Overview of the communication of the Technical Data Package standardized message Company A Company B Designer 1 CAD / PDM files Selection of the CAD/PDM files to be sent to the Designer 2 Data exchange responsible 1 Creation of the TDP and sending of the TDP to the DEX Resp. 2 Designer 2 Reception of the CAD/PDM files sent by Designer 1 To be completed and sent back CAD / PDM files Sending of/Receiving the TDP message for information TDP (“Container”) Message Data exchange responsible 2 Reception of the TDP from DEX Resp. 1 and preparation for Designer Simple & Widely used All along lifecycle of product Error prone Subject to automation Heterogeneous automation & practices SEINE, PHENIX PLM4GC, BOOST OASIS PLCS ASD Strategic Standardization G. EADS Strategic Standardization C. Subject for Standardization

13. Slide 13 TDP Project – Overview & Status – March 2009 Scope of Technical Data Package State of the Practice Several heterogeneous “local“ TDP methods (e.g. Eurofigther Standards, Airbus Procedures) Eurofighter Standard for Step Data Exchange (J17.400) “Data Despatch Note“ Airbus Procedure (AP2650) “Data Transfer Sheet“

14. Slide 14 TDP Project – Overview & Status – March 2009 Deliverables / Objectives International recommended best practises for the exchange of standardized messages for TDP >> OASIS PLCS DEX Demonstration of standards (DEXs >> http://www.plcs-resources.org)http://www.plcs-resources.org Pilots / Demonstrators Expected Benefits Single open standards Unified and constant applicable data exchange management infrastructure for TDP purposes European involvement in recommended practices >> basis to discuss with US (AIA) for possibly international standards Simple specification for various important benefits Deliverables & Benefits

15. Slide 15 TDP Project – Overview & Status – March 2009 Contents of a DEX (based on STEP AP239 XML) (acc. to www.plcs-resources.org)  Introduction;  Business process;  A description of the business process that the DEX is supporting;  Identification of the process in the AP239 activity model supported;  Usage guidance for the model;  DEX specific Reference Data;  The subset of the Information model supported by the DEX;  EXPRESS information model;  XML Schema (derived from the EXPRESS); Note >> DEX development usually undertaken with the PLCS DEXlib environment for formal OASIS publication format Development of an OASIS PLCS DEX

16. Slide 16 TDP Project – Overview & Status – March 2009 TDP Project – General / Planning Start Kick Off: 11th Dec 2008 (EADS MAS - Manching) Organization Project lead: Melanie Baudisch (EADS MAS) Based on regular teleconferences Common Workspace Interim meetings – as required Final meeting on project completion Work Packages Members EADS MAS Germany, EADS MAS Spain, EADS IW, Astrium, AFNeT, HAI (Hellenic Aerospace Industry), AgustaWestland Potential further members: Airbus, Eurocopter, Dassault-Aviation, Thales, Safran, VOLVO Aero, SAAB, BAE Systems, CostVision …

17. Slide 17 TDP Project – Overview & Status – March 2009 TDP Project - General / Planning Technical assumptions New OASIS PLCS DEX based on STEP AP239 XML European A&D Company individual “Best Practices” Based on the experience of the SEINE project Potentially harmonization with AIA (Aerospace Industries Association) Funding / Resources Each participant responsible for own funding Approx. 15-20 MD contribution per participant External resources: PLCS expert required (see WP3, slide 13)

18. Slide 18 TDP Project – Overview & Status – March 2009 Contact points Melanie Baudisch, EADS MAS, +49 84 59 81 78 943 melanie.baudisch@eads.com Nicolas Figay, EADS IW, + 33 1 46 97 36 60 nicolas.figay@eads.net

19. 19 AeroSpace and Defence Industries Association of Europe Drawback Technical outputs of project

20. Slide 20 TDP Project – Overview & Status – March 2009 PLCS Existing resources SEINE BOOST Phenix PLM4GC Eurofighter AP232 PLCS Community WP 2.2: TDP and current practices

21. Slide 21 TDP Project – Overview & Status – March 2009 WP2.2: Mapping with current practices Collection using an Excel Table Processes and Practices Comparison of data Study of implied processes and tooling With Eurofighter, BOOST, Phenix, AP232, etc

22. Slide 22 TDP Project – Overview & Status – March 2009 WP3 preparation concrete DEX development Point about available resource DEX Structure DEXLIB DEXPRO STEPMOD AP238 AP232 Potential complementary support for training, tooling and expertise Eurostep EPM Technology Issue of resources for subcontracting What is to be collected as input and what is precisely to be produced to be identified with planned resources Different scenarios to be evaluated for subcontracting Usage of DEXPRO connected on sourceforge with current involved persons Preparation than workshop with one of the sub-contractor

23. Slide 23 TDP Project – Overview & Status – March 2009 WP3 preparation assessment of usage of DEXPRO on DEXLIB Information collection and study concerning DEX structure, process, platform and tooling Structure: within DEXLIB Platform: Sourceforge Tooling DEXPRO (install and tested) Model editors To do: to plug on repository and evaluate time to produce a DEX with the tool

24. Slide 24 TDP Project – Overview & Status – March 2009 WP3 preparation: Assessment of information to prepare for DEX development New or updated representing_message template (simplified) - For file transportation only (not digital documents) Update Capability Messaging and Representing _Message with Envelop To take into account changes from new AP239 version (signal by Eurostep) Produce the TDP DEX

25. Slide 25 TDP Project – Overview & Status – March 2009 Function, structure, and purpose of Capabilities The structure of the Capability comprises: a subset of the information model that can be used to define a particular business term; a definition of the information model; usage guidance for the model; usage guidance for the Reference Data; a set of Templates. In summary, Capabilities: ensure (through the Templates) a common interpretation of PLCS; avoid multiple dialects of PLCS; reduce the amount of guidance documentation for those wishing to use only parts of PLCS; and simplify instantiation of the PLCS data model. Each Capability is identified within the DEXlib repository by a number, an identifier and a name, e.g number: C001, identifier: assigning_identifiers, name: Assigning Identifiers.These are assigned to the Capability in the initial development process. Each Capability contains: an introduction, explaining the nature and purpose of the Capability; a business overview; a description of the information model used by the Capability, with examples of its use; a full specification of the information model used by the Capability, derived from the relevant AP239 Implementation Module; and a set of one or more Templates. WP3 preparation: Assessment of information to prepare for DEX development