Today
For machines from the nineties, nobody knows any more which build state is installed. The parts list sits in the old ERP that only two people can still operate, the drawings are scans or microfilm in the archive, and what service has replaced since is on paper reports. So a technician drives out to look before anyone can quote a spare part or cost a retrofit.
An example
A customer of Ebert & Lorenz Maschinenbau wants to retrofit its HP 250 kN hydraulic press from 1998 with a new control system and needs a seal kit for the cylinder. The agent finds the order file as a scan, the parts list in the legacy system, two drawings in the scanned microfilm archive and eleven service records. It shows that the cylinder was replaced in 2009 and has needed a different seal kit since, and that a safety relay added in 2014 appears in no wiring diagram. Service confirms the state and quotes the seal kit and the retrofit without anyone driving out to look.
Your data, wherever it lives
The as-delivered state of your old machines sits today in paper order files, in old drawings as scans, on microfilm or half moved into the PLM, in parts lists from the old ERP that only runs for lookups, and in service records and photos on the drive. demi reads, understands and links them by order, serial and drawing number, with your rights. The AI assembles a machine's state in minutes instead of days, and your service team decides what the customer is offered.
Where the data lives today
- Legacy systems
- Scans & paper
- PLM
- Folders & drives
- Photos, video & audio
- ERP
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 legacy system, ERP, PLM, DMS and file share. demi replaces nothing and joins the order file, old drawings, the as-delivered parts list, acceptance report, service records and photos into one record per machine. Records are linked by order, serial and drawing number, even where numbering schemes have changed since.
- 2 · PermitPermission Layer
Old order files and prices are visible only to service and sales staff with rights to that customer. The reconstructed state goes into the system and to the customer only after an authorised person in service has confirmed it; the confirmation is recorded.
- 3 · ActIntelligence Layer
The agent reads scanned drawings, parts-list printouts and handwritten service notes, assigns them to the machine and builds the state at delivery and the state today. Every item names its document and page. Where sources contradict each other or something is missing, it shows the gap instead of filling it.
How it runs
- 1
A customer request names the serial or order number of a machine delivered decades ago.
- 2
The agent gathers the order file, old drawings, old parts list, acceptance report and service records.
- 3
It builds the as-delivered state assembly by assembly, every item with document and page.
- 4
Later retrofits and replaced parts from the service records lead to today's state; gaps are flagged.
- 5
Service checks, confirms and uses it to answer the spare-part request, retrofit quote or customer question.
What changes
Spare parts and retrofits clarified without a trip to the customer
One confirmed state per old machine, for service and sales
Knowledge from back then stays when the legacy system is switched off
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
+216 hfreed per year
Assumptions and calculation
demi assembles the as-delivered state from files, old drawings and service records; you confirm it.
4 h → 2.8 h per case
How we calculate
15 requests on old machines × 4 h × 30% × 1.0 (manual) × 12 months = 216 h
Value per year, before demi costs
Freed per year+216 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€14,040
gained per year
216 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 what was delivered back then?
From your records: order file, order confirmation, as-delivered parts list, drawings and acceptance report. demi also reads them as scans or as printouts from the legacy system, and links them by order, serial and drawing number. Every item in the as-delivered state names the document it comes from.
What about retrofits and parts replaced since delivery?
The agent takes them from service reports, spare-part deliveries and photos. You see two states: what was delivered and what should be installed today. demi cannot know what was never documented; the agent flags the spot, and the technician checks it on the next visit.
Do we have to keep the legacy system alive for this?
No, but you can. demi reads the data from the legacy system once and keeps it with its source, so it stays usable even after the system is switched off. We work out with you whether the data comes as an export, a print list or through an interface.
Can this be done for all old machines at once?
Yes. demi reads decades of delivery notes, invoices, service reports and acceptance reports, scans included, and builds a register from them: which machine with which serial number and equipment stands at which customer. Service confirms the entries step by step, starting with the machines that get the most requests.
