Introduction
A program manager at a systems integrator needs a quote for a new hydraulic actuator assembly. The engineering team has the 3D models, drawings, performance requirements, applicable standards, and test criteria, but they live in different places. Someone assembles a bundle by hand and sends it to three suppliers. One supplier asks, "Is the drawing set final?" Another receives a model that includes export-controlled data that was never cleared to see.
The engineering was sound. The problem was the package: nobody could say what it contained, what state it was in, or who was entitled to see it. This is the problem that led ENOVIA to develop the concept of Technical Data Package (TDP). In 2024, ENOVIA introduced the ability to create a TDP within the 3D Product Architect (PAU) role using the application Collaboration Package Management. I created a general overview of this app in a post in the Community you can access here. Now I would like to get a little deeper into the details of the TDP.
What Is a Technical Data Package (TDP)?
Whenever you ask a supplier to quote a subsystem or service, you have to describe what you want in precise detail. The TDP is the formal wrapper for that description. It is used widely across US government and military programs and is defined in MIL-STD-31000 Rev B. In short, it is the technical definition that supports acquiring, producing, inspecting, engineering, and logistically supporting an item. It can include models, engineering design data, associated lists, specifications, standards, performance requirements, quality assurance provisions, software documentation, and packaging details.
One point is easy to miss: a TDP contains engineering documents, not manufacturing ones. It tells the supplier what you need and the requirements it must meet. How the supplier builds it remains at the supplier's discretion.
The TDP in ENOVIA
ENOVIA supports creating and managing TDPs through the Collaboration Package Management app, available in the 3D Product Architect (PAU) role. The app governs how data is gathered and protected for exchange with suppliers and partners. It controls sharing with all stakeholders and manages the disclosure of sensitive data. Here is how that plays out in practice.
Communicate intent with Package Level
When you create a TDP, you can set a Package Level to tell the recipient what kind of content to expect:
- Conceptual: sketches, models, and text documenting the basic concepts for developing an item that meets operational requirements.
- Developmental: data documenting a specific design derived from a concept.
- Product: drawings or models containing all the documentation required to manufacture the object.
- Blank: no level defined.
The Package Level is informational only. It sets expectations for the recipient but does not affect the governance of the package or its publications. In the actuator scenario, labeling the package "Developmental" would have answered the supplier's "is this final?" question before they asked it.
Govern the package through its lifecycle
Like other documents on the platform, a TDP moves through maturity states. Each state defines what can and cannot be done with the package.
State | What it means for the TDP |
|---|---|
Draft | The TDP is created here. The owner can edit or delete it. |
Work | The owner can edit and demote it. It can no longer be deleted. |
Frozen | It cannot be edited, deleted, or revised, but it can be demoted. To publish content that includes IP or export-controlled data, the owner demotes the package to Work and selects Allow To Publish for that content. |
Released | Reached once all IP and export-controlled contents are allowed to publish. A released TDP cannot be demoted. |
Obsolete | A TDP can be promoted here once all related publications are obsolete. When a collaboration package is released, all its previous revisions become obsolete. |
Content isn't altered after the fact, and nothing containing controlled data goes out without a deliberate decision by the owner. Once a TDP is released, you know what was shared and that it cannot be altered or rolled back.
Protect sensitive data by design
Different suppliers may not need to see all content of a specific package, To address this, the app manages the disclosure of sensitive data as part of the package process. You can also classify a TDP within a security class and security library using the IP Protection Management or IP Export Control Management apps. The collaboration package is then secured by the rules and policies of that security class. Subsequently, TDPs published for international use would automatically be governed by this additional layer of access control.
Keep history without keeping confusion
Keep history without confusion (shorter?)
The TDP is revision controlled. You can revise and improve a package over time while retaining the history of prior packages, which is useful when you need to compare what was sent in one round of quoting with the next. Because earlier revisions become obsolete once a new one is released, recipients are not left guessing which version is current.
An audited way to work
Taken together, Collaboration Package Management gives you an audited way to create, govern, and manage every aspect of a technical data package, from the first draft through publication to obsolescence. When someone asks months later what you sent a supplier, the record lives on the platform rather than in a mailbox.
Revisiting the scenario where a program manager needs a quote for a new hydraulic actuator using a managed TDP:
- The package is labeled with its Package Level, so the supplier knows the intent.
- It is frozen and released only after the controlled content has been explicitly approved for publication.
- It carries a clear revision, and the superseded ones are obsolete.
- The development program has a record of what was shared and with who.
Note: Available apps, roles, and capabilities can vary by release and configuration. Check with your platform administrator or the Dassault Systèmes documentation for what is enabled in your environment.
Summary
- A Technical Data Package (TDP) is the formal description of what you need from a supplier: models, drawings, specifications, standards, and requirements. It covers what is needed, not how to manufacture it.
- On the 3DEXPERIENCE platform, TDPs are created and managed using the Collaborative Package Management app in the 3D Product Architect (PAU) role.
- The Package Level (Conceptual, Developmental, Product, or blank) tells recipients what to expect. It is informational and does not change governance.
- The Package lifecycle (Draft, Work, Frozen, Released, Obsolete) controls who can edit, demote, delete, or publish at each stage. Releasing requires that IP and export-controlled content be explicitly allowed to publish.
- IP Protection Management and IP Export Control Management applications let you apply security classes to the package, so access follows policy.
- Revision control preserves the history of prior packages for comparison while keeping the current one clear.
If your supplier handoffs still depend on hand-built bundles and good intentions, a governed TDP is a practical way to make them repeatable and auditable.
