Introduction

One of the most common interactions between a company and their supplier is getting a quote for some sub-system or service. Beyond ordering from a catalog, this will require you, as the company, to accurately describe what you want in great detail. This is commonly done within the context of a “Technical Data Package” (TDP).

Because of it’s broad use across the US government and military industry, the TDP is defined through MIL-STD-31000 RevB where the it is defined as follows:
“This technical definition supports the acquisition, production, inspection, engineering, and logistics support of the item. The description defines the required design configuration and/or performance requirements, and procedures required to ensure adequacy of item performance. It consists of applicable technical data such as models, engineering design data, associated lists, specifications, standards, performance requirements, quality assurance provisions, software documentation and packaging details.”
 

Note that the TDP  contains  engineering documents, not manufacturing ones. The supplier may infer how to manufacture the product you need through the specifications in the TDP but it is still at the suppliers discretion how it is built.
 

TDP in the 3DEXPERIENCE platform

The 3DEXPERIENCE platform supports the creation and management of these Technical Data Packages through Collaborative Package Management app, available in the role “3D Product Architect (PAU)”. This app governs the process of gathering and protecting data to be exchanged with suppliers and partners and controls product data sharing with all involved stakeholders while managing the disclosure of sensitive data. 

The overall process supported by this app is summarized as follows:

When creating a TDP, you can provide clarity for the recipient by defining the‘Package Level’ that can be:

• [Blank] >> no definition?
• Conceptual - A collection of sketches, models, and text that documents the basic concepts to develop an item that meets operational requirements.
• Developmental - A collection of data that is used to document a specific design of an object from a concept.
• Product - A collection of product drawings or models that contain all the required documentation used to manufacture the object.

Note:  this is purely informational and does not affect the governance of the package or its publications.

TDP Lifecycle maturity states:

The TDP has a maturity lifecycle like other documents on the platform. Let’s take a closer look at what can be done within each of these lifecycle states in regards to the TDP:

Draft

• The TDP is created in the In Draft maturity state. 
• The owner can then edit and/or delete it.

Work

• The owner of the TDP can edit and demote. 
• The TDP cannot be deleted. 

Frozen

• The TDP cannot be edited, deleted, or revised, but it can still be demoted.
• To publish the package content that includes IP and export control data, the owner must demote the package to Work and select the Allow To Publish check box for the package content. 

Released

• Once all IP and export controlled package contents are allowed to publish, the TDP is promoted to Released.
• Once a TDP is released, you cannot demote it. 
• The TDP can be promoted to Obsolete if all related publications are obsolete.

Obsolete

• Once a collaboration package is released, all previous revisions are obsolete.

Now let’s take a look at the overall process of package definition through publication in the video below.

Conclusion

As you can see in the video the Collaborative Package Management app offers an audited way to create, govern, and manage all aspects of a technical data package. Although not covered in the above  video, it is important to note that the TDP is reversion controlled so you can revise and improve a package over time, but retain the history of the prior packages if comparatives are necessary over time. Another capability that can be is considered is the ability to classify a TDP within a security class and a security library using the IP Protection Management or IP Export Control Management apps. The collaboration package is secured by the rules and policies of the security class as provided by the IP Protection and Export Control app.