1 / 11

PLCS Teleconf Meeting on the 23 rd October 2008

PLCS Teleconf Meeting on the 23 rd October 2008. Transportation of Technical Data Package, using a standardized TDP message Proposal from EADS and SSG members. Technical Data Package (TDP): Process Transportation of a TDP including validation mechanism

oksana
Download Presentation

PLCS Teleconf Meeting on the 23 rd October 2008

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PLCS Teleconf Meeting on the 23 rd October 2008 Transportation of Technical Data Package, using a standardized TDP message Proposal from EADS and SSG members

  2. Technical Data Package (TDP): Process Transportation of a TDP including validation mechanism acknowledgment procedure to monitor secured TDP transport Import TDP within the target system Definitions TDP is a set of product data (digital files) plus product meta-data (digital file) plus data dispatch note (content of the message). Message provides information on sender, receiver and describes all digital files of the TDP, in order to support automatic routing, acknowledgment and validation of transportation of product & meta data files. Product meta-data provides information to allow import of the meta-data and related TDP product data into the receiving target system. Scope of standards for exchange of “TDP”Process / Definitions TDP Message Product Meta Data Product Data

  3. Requirement Aminimum standardized ”message" for a TDP Requirement B TDP process must be independent of Product Data import/export process, in order to support any way to define Product meta-data (e.g. AP214 / AP203, part21 / part28, …) TDP Transportation and interchange of Product Data between systems are two different needs and distinct processes, but that have to be consistent. Scope of standards for exchange of “TDP”Requirements TDP Message Product Meta Data Product Data

  4. Several heterogeneous “local“ TDP standards (e.g. Airbus Procedures, Eurofighter standards) >> We need a European Aeronautic standard ! Scope of standards for exchange of “TDP”State of the Practice Airbus Procedure (AP2650) “Data Transfer Sheet“ Eurofighter Standard for Step Data Exchange (J17.400) “Data Despatch Note“

  5. Product meta data File 1 File3 File 2 Overview of the scope of TDP : 2 main functions Creation of a new ASD project TDP Process • Transportation of the TDP through the network • Monitoring and history • Acknowledgments • Message informationSender, Receiver, level of security, list of digital files… TDP standardized message Quick Win Share some common information(Persons & Organizations,optionaly: project context…) Secured Transportation Acknowledgment Procedure Product Data interchange between systems For automated import by the PLM / DMS system of the receiver Consideration of all kind of Exchange scenarios

  6. Company A Company B Designer 2 Designer 1 CAD / PDM files Message Message CAD / PDM files Reception of the CAD/PDM files to send to the Designer 2 Selection of the CAD/PDM files to send to the Designer 2 Sending of the TDP messagefor information Data exchangeresponsible 1(DEX 1) Creation of the TDPand sending of the TDP to the DEX 2 TDP (“Container”) TDP (“Container”) Overview of the communication of the Technical Data Package standardized message

  7. Organization Proposed leader: Melanie BAUDISCH (EADS MAS) Potential members EADS MAS, Astrium, Airbus, Eurocopter, Dassault-Aviation, Thales, Safran, AFNET, VOLVO … plus other PLCS members? Based on teleconferences Business requirements: for collaboration processes between OEMs and Suppliers (direct communication), with BoostAeroSpace Technical assumptions: New OASIS PLCS DEX based on STEP AP 239 XML Based of the experience of the SEINE project Harmonization with AIA New ASD Stan project for a TDP standardized message

  8. Deliverables: International recommended practises for the exchange of standardized messages for Technical Data Packages (PLCS DEX) Demonstration of Standards Expected Benefits: Single open European Aeronautic standards Based on shared relevant PLM standard (STEP AP239, PLCS) >> compliance with US efforts Simple specification for important benefits European involvement in recommended practices >> basis to discuss with US for international standards Deliverables & Benefits

  9. Planning Start: Nov. 2008; April : MS1 -> Ballot End: June 2009 Potential prototype : Prototype between DXM EADS-MAS, Airbus Kick off: November (meeting) New ASD Stan project for a TDP standardized message

  10. Are some PLCS members interested to join? How to proceed to make the project contributing to a PLCS DEX definition? Any feedback or complementary information? Discussions

  11. Melanie Baudisch, EADS MAS +49 84 59 81 78 943 melanie.baudisch@eads.com Nicolas Figay, EADS + 33 1 46 97 36 60 nicolas.figay@eads.net Representing of EADS, AIRBUS, EADS MAS Contact points

More Related