Product identity & versions
Style or product ID, variant, size/colour, lifecycle status, effective version and approval date—where captured.
TDG / Source system
PLMProduct Lifecycle Management
PLM systems may hold approved product definitions: style or product identifiers, specifications, variants and bill-of-materials structure. For an RMG data journey, this can be a useful starting point—but it does not automatically contain production-lot traceability or every data point a DPP may need.
PLM / Typical contribution
What this source may contribute.
Product BOM, specifications and approved product versions. Use these examples to guide discovery—not as a guarantee that every field is captured or a final DPP requirement list.
Specification & construction
Construction details, measurements, care/label references and documents linked to the correct product version.
Product bill of materials
Materials, trims and components, BOM quantities, revision history and supplier references where maintained.
Scope check: A PLM record can describe intended product composition; it does not prove which material lot was consumed in production. Reconcile the BOM with purchasing, inventory and production sources when needed.
Make the relationships explicit
Fields matter when they can be linked and reviewed.
A TDG data map records the source, identifier, owner and review status alongside the value.
| Example field or checkpoint | Question to resolve |
|---|---|
| Style / product ID + version | Which version was approved for this order, and how is it distinguished from a draft? |
| Variant / colour / size | Which variant level is represented in the source record? |
| BOM item and revision | Can each BOM line be resolved to a material or supplier reference? |
| Owner and effective date | How are changes approved, versioned and corrected? |
Illustrative only. Actual field names, formats and disclosure permissions depend on client systems, business process, data rights and applicable product-specific rules.
From source to governed handoff
A practical way to map PLM data.
Make the product-data journey understandable before selecting an integration or platform.
Find the approved definition
Identify the authoritative specification and BOM version for one selected product/style.
Map identifiers
Relate PLM product, style and variant references to order, buyer or ERP identifiers.
Record provenance
Capture source, owner, effective date, approval state and unresolved fields.
Agree the handoff
Set which fields can be shared and how future product changes are communicated.
Compliance boundary: A system record, certificate or readiness map is not by itself proof of compliance. Confirm evidence scope and applicable DPP rules for the product and market.
Explore related sources
Follow the product data across systems.
A product record is usually assembled across more than one source. Select another system to continue.
The connected data journey
Start with the question. Then map the systems.
Explore how TDG can connect records, owners, evidence and approved data exchange.