Today
A value changes in engineering or in the ERP, but the data sheets on the website, in the distributor portal, on sales laptops and in open quotes still show the old one, often in four languages. Customers and planners design foundations, cables and orders around outdated values. The error surfaces only at acceptance or with a complaint.
An example
At Wattaris, engineering changes the core steel of the TR 630 kVA distribution transformer (20/0.4 kV, Dyn5, ONAN): no-load losses drop and the total weight rises by 85 kg. After the change is approved in the PLM, the agent regenerates the data sheet in German, English, Polish and Czech, marks the changed values, checks the losses against the limits of the EU ecodesign regulation and archives the old version. It finds the old one still on the website, in the distributor portal and in 17 open quotes, and proposes informing nine municipal utilities and two engineering firms that plan foundations and transport with the old weight. Product management releases the sheet, and the sales reps send the notices the same day.
Your data, wherever it lives
The valid values live today in the PLM and ERP, the data sheets as PDFs and layout files in the DMS, in SharePoint, on the website and in the distributor portal, the versions sent out in quotes and e-mails, and customers and open projects in the CRM. demi reads, understands and links them, with your rights. So a change reaches every data sheet in every language on the same day, and product management and sales decide what goes out and who is informed.
Where the data lives today
- PLM
- ERP
- PDFs
- DMS & archive
- SharePoint
- CRM
- E-mails
- Web & portals
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the PLM, ERP or PIM, the DMS, the file share, the CRM and your website. demi replaces nothing and maps every value in the data sheet to its master-data field, learned once from your existing data sheets. demi also knows which version sits where and who received it: on the website, in the distributor portal, in quotes and e-mails.
- 2 · PermitPermission Layer
Only approved changes trigger a new data sheet; drafts from engineering stay internal, as do costs and suppliers. Product management releases every new data sheet, and each sales rep decides which of their customers get a notice. Which version a customer received, and when, stays traceable.
- 3 · ActIntelligence Layer
The agent detects every approved change, regenerates the data sheet in your template and in every language and marks the changed values. It checks units and statements against the standards and limits named in the data sheet and finds old versions still in circulation. For customers with open quotes and orders, distributors and sales, it drafts the matching notice right away.
How it runs
- 1
demi reads your existing data sheets and maps every value to its field in the PLM, ERP or PIM.
- 2
When a change is approved, the agent regenerates the data sheet in every language and marks what changed.
- 3
Product management checks the comparison of old and new version and releases it.
- 4
The agent archives the old version with its validity period and replaces it on the website and distributor portal.
- 5
It shows which customers, distributors and sales reps have the old version and drafts a notice per customer that sales sends.
What changes
Data sheets that match the product you deliver
Every language up to date on the same day
Targeted notices to customers with outdated values
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+180 hfreed per year
Assumptions and calculation
demi regenerates the data sheet in every language after each approved change; you check and release.
90 min → 54 min per case
How we calculate
25 data sheet updates × 90 min × 40% × 1.0 (manual) × 12 months = 10,800 min = 180 h
Value per year, before demi costs
Freed per year+180 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$11,700
gained per year
180 h ÷ 1,760 h per role = 0.1 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
How does demi know which value in the data sheet belongs to which master-data field?
From your existing data sheets: the agent reads them once and maps every value to its field in the PLM, ERP or PIM. Values that appear nowhere in master data, because someone once typed them into the layout by hand, it shows you; you confirm the mapping once.
What happens to the old version of a data sheet?
It is archived with its validity period and stays retrievable. So for every quote and delivery you can show which version applied at the time. It disappears from the website and distributor portal as soon as the new one is released.
Do customers get an automatic e-mail when a data sheet changes?
No. The agent proposes who should be informed, such as customers with open quotes or orders for that type, and drafts the notice. Whether and when it goes out is decided by the responsible sales rep.
Do the layout and structure of our data sheets stay the same?
Yes. The agent works with your data sheet template, fonts and structure. Values, units and footnotes come from master data, and texts in other languages from your glossary.
