Navigation Navigation
TDP Message specifications TDP Message specifications

Strategic choice to define the content

The strategic choice made when proposing was to rely on already existing set of standards dealing with Technical Data Package and Product data exchange, sharing and long term retention. It was also to support emerging eBusiness PLM needs and collaborative platform supporting the whole Aerospace&Defence Community. The considered standards and initiatives were:

  • Phenix PLM for Global Collaboration
  • AP232
  • Eurofighter
  • PLC community

TDP Message header format and syntax

The following choices were made for TDP message header syntax and format:

  • Because AP239 was the single application procotole formalizing messages and envelops (inside modules being part of the STEP Modules library), the TDP message header schema is defined using a subset of AP239. It should be pointed out that it does not make it a part of PLCS, at it can be used by any kind of processes not related to Customer Support processes.
  • The chosen file syntax is XML, base on ISO Part 28
  • The content of the TDP message is the one covered by AP232 Conformance Class 1, i.e. file related. TDP transportation is done for file, not for document or product parts.

The schema for the TDP message header is today defined and ready to use. Both EXPRESS and in XML Schema languages were used to define it, and  associated specificications for usage in the context of a hub were formalized.

A second version is under preparation through feedback coming from Industrial pilots such as BoostAerospace and Phenix. In fact, the schema may remain the same but the recommended practices will be impacted in order to ensure interoperability between different industrial pilots.

Formalized DEX

In order to formalized recommended practice, the initial aim was to produce a DEX as defined by PLCS, being OASIS DEX (prefered target) but eventually an ASD SSG DEX if more appropriate. The infrastructure for providing a DEX have been studied in order to produce the TDP DEX message, knowing that:

  • DEXLIB technological framework is quite complex and requires a lot of effort to produce a formal DEX
  • PLCSLIB is under validation and will be used as soon as frozen

As a consequence, it was decided to wait for feedback of the different pilot projects concerning implementation of the TDP Message DEX before to formalize the DEX and to submit it at OASIS. Infrastructure for formalizing the DEX is under preparation, as described in the "Tools" section.