TDP Message header usage TDP Message header usage

Today in industry, providing a message describing content of a TDP to be tranported between companies is a shared practice, simple and widely used. If made manually, it is error prone. As e consequence, it is frequently subject to automation, but numerous specific ways exist to formalize this message. As a consequence, it was identified as a subject for standardization by several enterprises and standardization governance initatives in Aerospace & Defence, in particular in order to support emerging PLM hub projects, such as PHENIX PHUSION or BoostAersopace.

From a company A, designers are preparing, from their working environment, a technical data package encompassing Product Data (as files), and  associated Product meta data indicating what the files are describing (parts organized according a product structure, with associated composite documents and complementary information. The content of the TDP is to be securely transported, and a complementary file is usually provided, describing all the files of the TDP, sender and reveiver plus complementary security related information. This is described in the following figure.

Need for a single standards Need for a single standards

Several heterogeneous "local" TDP message formalism and processes exist, such as for example Eurofighter standard or AIrbus standardized procedure (c.f. next figure). A single standard is needed!


For this reason, a project was launched to produce such a standard, as a part of a coherent eBusiness PLM standards identified as those of European Aerospace&Defence Industry.