Today
Which machine runs where, with which parts and software, is spread across the ERP, service tools, spreadsheets and technicians' notes. Service, sales and recalls work with gaps. Anyone who needs an answer has to ask around.
An example
At Ebert & Lorenz Maschinenbau the head of service asks: which HP 250 kN hydraulic presses still run firmware 2.3 with the old valve block? The agent lists 46 presses at 31 customers, each with its site and last service visit.
Your data, wherever it lives
Deliveries sit today in the ERP, customers and sites in the CRM, BOMs in the PLM, firmware versions in spreadsheets, and service reports in the service tool, as PDFs or in technicians' e-mails and notes. demi reads, understands and links them per serial number into one record per unit, with your rights. The AI finds every unit with a given part or software version in seconds instead of someone asking around for days, and the service team decides on a visit or a recall.
Where the data lives today
- ERP
- CRM
- PLM
- Office files
- Tickets
- PDFs
- E-mails
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: the ERP, CRM, PLM, spreadsheets and portal. demi replaces nothing and joins deliveries, as-built and as-maintained BOMs, firmware versions, service reports and sites into one record per unit. Duplicate customers and spelling variants are merged.
- 2 · PermitPermission Layer
Customers see only their own units in the portal, service sees all of them, and prices and contracts follow sales rights. Service confirms gaps and conflicts before they enter the record, and this is recorded.
- 3 · ActIntelligence Layer
The agent answers questions about any unit, keeps the as-maintained BOM current from service reports and finds every unit with a given part or software version. Such lists come from a query on the records, not from an estimate, each fact with its delivery or report as the source.
How it runs
- 1
Clarify the data sources: ERP, service tools and spreadsheets
- 2
demi merges deliveries and reports per serial number
- 3
Review gaps and conflicts; service confirms
- 4
Ask questions about one unit or across all of them
- 5
Every new service report keeps the record current
What changes
One record per machine, for every team
Faster service and targeted recalls
Upgrade potential becomes visible
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
+240 hfreed per year
Assumptions and calculation
demi shows site, parts, software level and open cases for each serial number; you decide the next step.
10 min → 6 min per case
How we calculate
300 machine lookups × 10 min × 40% × 1.0 (manual) × 12 months = 14,400 min = 240 h
Value per year, before demi costs
Freed per year+240 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
+$15,600
gained per year
240 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 do we build the installed base from scattered data?
demi starts with deliveries from the ERP: serial number, customer, as-built BOM. Service reports, spreadsheets and firmware versions are added on top. Where sources disagree, demi shows both and service decides.
Does it track replaced parts?
Yes. When a service report records a swap, demi updates the as-maintained BOM of that unit. The as-built state is kept, so both are visible.
Can customers see their own machines?
Yes, in a portal. Each customer sees only their units, with documents, maintenance and open cases. Internal notes and prices stay hidden.
What if a unit has moved to another site?
Then the delivery address is out of date. demi takes new sites from service reports and visits. Units nobody has reported on for a long time are flagged so service can follow up.
