Where the data usually sits
- ERP: article master, suppliers, purchasing, sometimes batch/lot
- PLM/CAD: BOM, materials, revisions, engineering files
- Quality systems: certificates, tests, deviations
- Sustainability: EPD, climate calculations, chemical lists
- Outside systems: spreadsheets, PDFs, email, supplier portals
Why the gaps appear
- Fields exist in several systems with different definitions
- Supplier data has no product link
- Documents are valid but not version-controlled against SKU
- Nobody owns the update when a material or supplier changes
A DPP project that only “exports ERP” often misses the very fields the legal requirement cares about.
A working model
- Choose the requirement picture and a pilot line
- Map each DPP field to a source + owner
- Mark gaps: missing / uncertain / manual
- Automate what exists, gated process for what is missing
- Publish the passport and connect change events (ECO, supplier change)
Continue with the checklist or book a demo.