Today
A manufacturer releases new firmware because it fixes a fault or closes a security gap. But nobody knows exactly which units at customers still run the old version: it is scattered across deliveries, service reports, spreadsheets and the messages of units that are online. So the update never reaches every unit, customers hear about it too late, and when a customer or an auditor asks, the proof per serial number is missing.
An example
Wallner+Hardt Sensortechnik releases firmware for its drive controllers that fixes a speed-control fault and closes a security gap in the Ethernet interface. From deliveries, service reports and the messages of connected units, demi finds 1,860 controllers on an older version at 174 customers; 140 of them have an older hardware revision and need an intermediate version first. 1,120 controllers can be reached remotely, customers update 610 themselves with instructions, and for the remaining 130 the agent plans site visits, bundled with maintenance in the same region. The service manager releases plan and notices. Six weeks later the list shows the version of every serial number; 37 units are still open, each with its next step.
Your data, wherever it lives
Which firmware runs on which unit is scattered today: released versions in the PLM, deliveries with serial numbers in the ERP, customers and contracts in the CRM, the version found on site in service reports and tickets, messages from units that are online, and much of it in old lists. demi reads, understands and links them per serial number, with your rights. The AI finds every affected unit in minutes and plans the update instead of weeks of list work, and your service management decides and releases.
Where the data lives today
- PLM
- ERP
- CRM
- Tickets
- Machines & sensors
- E-mails
- Office files
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: firmware versions, release notes and compatibility with hardware revisions in the PLM, deliveries with serial numbers in the ERP, customers, contacts and service contracts in the CRM, field service jobs and tickets with the version found on site, the messages of remotely connected units, and old serial-number spreadsheets. demi replaces nothing and links every serial number to customer, site, hardware revision and current firmware. For every update you see which units are affected and how to reach them.
- 2 · PermitPermission Layer
Service and product management see all units and versions, sales only the units of their own customers. Service management releases customer notices and the job plan; an update is installed only by an authorised technician, remotely or on site, or by the customer, and every step is recorded.
- 3 · ActIntelligence Layer
demi determines exactly which units are affected from serial number, hardware revision and firmware version, not by estimate. The agent assigns each unit the route by which it gets the update: remote access, the customer with instructions, or the next field visit, bundled with maintenance in the same region. It writes the customer notices in the customer's language and ticks off a serial number only when the unit or the service report confirms the new version.
How it runs
- 1
Product management releases a firmware with its reason, urgency and the matching hardware revisions.
- 2
demi finds every unit on an older version, with customer, site and hardware revision.
- 3
The agent plans the route per unit: remote access, update by the customer or a site visit, bundled by region.
- 4
Service management releases plan and customer notices; technicians and customers install the update.
- 5
Each serial number is ticked off once the unit or the service report confirms the new version; open units stay visible.
What changes
Every affected unit is known and has a route to the update
Proof per serial number of which version was installed and when
Customers learn in time what they need to do
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
+144 hfreed per year
Assumptions and calculation
demi finds every affected unit, plans the route and records the update per serial number; you release.
20 min → 14 min per case
How we calculate
120 unit updates × 20 min × 30% × 1.0 (manual) × 12 months = 8,640 min = 144 h
Value per year, before demi costs
Freed per year+144 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
+€9,360
gained per year
144 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 firmware a unit runs?
For units that are online, straight from their messages; for the rest, from service reports, tickets and delivery data, each with a date. The agent shows for every unit where the version comes from and how old the information is. If a version is unknown, the unit counts as affected until someone checks.
What about units that cannot take the new update?
Which firmware fits which hardware revision is stored in your PLM. The agent checks this per serial number and plans an intermediate version or a replacement where needed. Units with no suitable route go to product management for a decision.
Does demi install updates on the units itself?
No. demi finds, plans, informs and documents. The update is installed through your remote service, by your technicians or by the customer, always after release. Every step is recorded.
Does this help with the Cyber Resilience Act?
The EU Cyber Resilience Act requires manufacturers to provide security updates and to report actively exploited vulnerabilities. demi shows you per serial number which version runs, when which update came and which customers were informed; the evidence sits in one place. What you report and declare, your team decides.
