Production order & operations
Work-order reference, facility or line, operation stage, event time and status where configured.
TDG / Source system
MESManufacturing Execution System
An MES may capture work orders, production steps, material issues or consumption, output and quality events. Its value for TDG and DPP preparation depends on actual shop-floor coverage: which lines use it, how records are created and whether events link to the right product and material references.
MES / Typical contribution
What this source may contribute.
Production events, material consumption and process traceability. Use these examples to guide discovery—not as a guarantee that every field is captured or a final DPP requirement list.
Material consumption & output
Issued or consumed materials, output quantity, rework and waste where recorded.
Process traceability events
Links among order, material lot, process step, equipment or inspection at available granularity.
Scope check: A system label does not guarantee automated shop-floor tracking. MES usage, event granularity, integrations and record quality vary; confirm the workflow with factory data owners.
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 |
|---|---|
| Work / production order | Which identifier ties the order to the product definition and buyer request? |
| Material lot consumed | Is the consumed lot scanned, selected, entered manually or not captured? |
| Operation and timestamp | Are time, facility/line and stage definitions consistent? |
| Output, rework and waste | How are corrections, scrap, rework and reporting cut-offs handled? |
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 MES data.
Make the product-data journey understandable before selecting an integration or platform.
Select a bounded journey
Choose one style/order, facility and period; confirm which lines and steps are in scope.
Trace the event keys
Map work order, product, material and batch references to their source records.
Check real coverage
Compare system events with the factory process; note manual steps and missing records.
Set review and access rules
Agree who validates event data, who can view it and how exceptions are corrected.
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.