Aero Space and Defence Industries Association of Europe

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

Current Status of the Project Current Status n Kick Off: December 2008 n Based on regular Teleconferences & Working Sessions n Participants: EADS-MAS (+ project lead), EADS IW, AFNet, Boost n International Interest “high” / Participation “low” n Work Package status: WP 2. 2 / WP 2. 3 are in work, WP 2. 3 and WP 3 under preparation n Input / BPs: Boost, Seine, Eurofighter Typhoon (EADS-MAS), Astrium France n Communication with OASIS PLCS Community (PLCS Teleconfs) n 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) Slide 2 TDP Project – Overview & Status – March 2009

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

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

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

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

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

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

Scope of Technical Data Package Brief Overview TDP Transportation Process “Data Exchange” TDP Message - Product Meta Data Product Data Standardized TDP Message TDP structure Monitoring and history Online transportation of TDP Secured transfer Acknowledgement Procedure for product data import/export … import export File(s) File 1 Product Meta Data File 2 File 3 Product Data Exchange “PLM/PDM world” - Product data import/export - Data format: STEP AP 214/AP 203, part 21/part 28 … - Consideration of all kind of possible exchange scenarios … Slide 9 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 - TDP is a set of TDP Message product data (1 -n digital files) product meta-data (1 digital file) Product Meta Data dispatch note (TDP message) Product Data 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 Slide 10 TDP Project – Overview & Status – March 2009

Scope of Technical Data Package Requirements TDP Message Technical Data Package (TDP) Product Meta Data Requirement A Product Data 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 AP 214/AP 203, part 21/part 28) >> TDP transfer and product data exchange between systems are two different needs and distinct processes, but have to be consistent and harmonized Slide 11 TDP Project – Overview & Status – March 2009

Overview of the communication of the Technical Data Package standardized message Company A Company B Designer 1 Designer 2 Message CAD / PDM files Selection of the CAD/PDM files to be sent to the Designer 2 Data exchange responsible 1 TDP (“Container”) Message Reception of the CAD/PDM files sent by Designer 1 To be completed and sent back Data exchange responsible 2 Sending of/Receiving the TDP message for information Creation of the TDP and sending of the TDP to the DEX Resp. 2 Reception of the TDP from DEX Resp. 1 and preparation for Designer Simple & Widely used All along lifecycle of product Subject for Error prone Standardization Subject to automation Heterogeneous automation & practices Slide 12 TDP (“Container”) SEINE, PHENIX PLM 4 GC, BOOST OASIS PLCS ASD Strategic Standardization G. EADS Strategic Standardization C. 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 (J 17. 400) “Data Despatch Note“ Slide 13 Airbus Procedure (AP 2650) “Data Transfer Sheet“ TDP Project – Overview & Status – March 2009

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

Development of an OASIS PLCS DEX Contents of a DEX (based on STEP AP 239 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 AP 239 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 formal OASIS publication format Slide 15 TDP Project – Overview & Status – March 2009

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

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

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

WP 2. 2: TDP and current practices PLCS Existing resources Slide 20 PLCS Community AP 232 Eurofighter Phenix PLM 4 GC BOOST SEINE TDP Project – Overview & Status – March 2009

WP 2. 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, AP 232, etc Slide 21 TDP Project – Overview & Status – March 2009

WP 3 preparation concrete DEX development Point about available resource n DEX Structure n DEXLIB n DEXPRO n STEPMOD n AP 238 n AP 232 Potential complementary support for training, tooling and expertise n Eurostep n 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 n Usage of DEXPRO connected on sourceforge with current involved persons n Preparation than workshop with one of the sub-contractor Slide 22 TDP Project – Overview & Status – March 2009

WP 3 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 n DEXPRO (install and tested) n Model editors To do: to plug on repository and evaluate time to produce a DEX with the tool Slide 23 TDP Project – Overview & Status – March 2009

WP 3 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 AP 239 version (signal by Eurostep) Produce the TDP DEX Slide 24 TDP Project – Overview & Status – March 2009

WP 3 preparation: Assessment of information to prepare for DEX development Function, structure, and purpose of Capabilities The structure of the Capability comprises: n a subset of the information model that can be used to define a particular business term; n a definition of the information model; n usage guidance for the Reference Data; n a set of Templates. In summary, Capabilities: n ensure (through the Templates) a common interpretation of PLCS; n avoid multiple dialects of PLCS; n reduce the amount of guidance documentation for those wishing to use only parts of PLCS; and n 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: C 001, identifier: assigning_identifiers, name: Assigning Identifiers. These are assigned to the Capability in the initial development process. Each Capability contains: n an introduction, explaining the nature and purpose of the Capability; n a business overview; n a description of the information model used by the Capability, with examples of its use; n a full specification of the information model used by the Capability, derived from the relevant AP 239 Implementation Module; and n a set of one or more Templates. Slide 25 TDP Project – Overview & Status – March 2009