Today
On the shop floor, controllers, operator panels and remote maintenance routers run firmware that is ten years old. Which version runs where is scattered across asset lists, maintenance files and commissioning records. Manufacturers and authorities publish new security advisories every week, and nobody checks them against their own machines; anyone who ships equipment has the same problem again at their customers.
An example
An authority publishes an advisory on a widely used remote maintenance router: firmware up to version 2.4 allows sign-in without a password, severity critical (CVSS 9.8). demi finds the router at Aldevo Wassertechnik on two test benches in the Arnsberg plant and in 37 delivered filter systems FA DN 150 at water utilities, 29 of them with active remote access according to commissioning records and the latest service reports. The agent ranks them by reachability and drafts the maintenance tickets and a notice to the affected customers. The head of IT and the service manager release both the same day. Until the update, service switches off remote access to the 29 systems, and the updates run in the next maintenance windows.
Your data, wherever it lives
Which controller runs which firmware where is scattered today: in asset lists as spreadsheets, in maintenance files and tickets, in commissioning records as PDFs and in the controllers themselves; the advisories appear on the websites of manufacturers and authorities. demi reads, understands and links both, with your rights. The AI knows on the day of an advisory which machine is affected, and maintenance and IT decide what happens.
Where the data lives today
- Machines & sensors
- Databases
- Office files
- PDFs
- Tickets
- Web & portals
- Photos, video & audio
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 asset lists, maintenance, tickets, commissioning records and, where connected, the controllers themselves. demi replaces nothing and builds a register of every controller, panel and network device with type, firmware version, location and remote access. Published security advisories are added, many of them machine-readable in the CSAF format.
- 2 · PermitPermission Layer
Firmware lists, network plans and findings are sensitive: only IT, OT security and maintenance management see them, and a finding on a machine also its maintenance team. demi only reads and changes nothing on a controller. Who accepts a risk or releases a measure is logged.
- 3 · ActIntelligence Layer
Matching product and version against the range named in an advisory follows fixed rules, not guesswork. The agent rates each hit by severity, network reachability and the machine's importance for production, summarizes the manufacturer's recommendation and drafts the maintenance ticket. Maintenance and IT decide what is done.
How it runs
- 1
demi reads asset lists, maintenance files and commissioning records and, where connected, firmware versions directly from the controllers.
- 2
This produces a register of every controller, panel and network device with type, version, location and remote access.
- 3
Every new security advisory from manufacturers and authorities is matched against this register.
- 4
The agent reports each affected machine, rates it by severity and reachability and names the manufacturer's recommendation.
- 5
Maintenance and IT decide on update, isolation or a deliberate wait, and demi tracks the measure until it is closed.
What changes
An up-to-date register of all controllers and firmware versions
Affected machines known on the day of the advisory
Updates in the maintenance window instead of an emergency
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
+72 hfreed per year
Assumptions and calculation
demi matches each advisory against your installed base; maintenance and IT decide what to do.
45 min → 27 min per case
How we calculate
20 security advisories × 45 min × 40% × 1.0 (manual) × 12 months = 4,320 min = 72 h
Value per year, before demi costs
Freed per year+72 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
+$4,680
gained per year
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 machine runs?
From asset lists, maintenance files, commissioning records, photos of type plates and, where the controller is connected, directly from it. If two sources disagree, the agent shows both with their dates. Where the version is unknown, it says so, and the next maintenance round gets the task of checking.
Does demi interfere with the controllers?
No. demi only reads: no updates, no configuration changes, no scans that could disturb a running machine. Maintenance plans and carries out updates, usually during a planned shutdown.
Where do the security advisories come from?
From publications by manufacturers and national cybersecurity bodies, many of them machine-readable in the CSAF format. demi checks them daily. A fixed rule matches product and version; the language model only summarizes the advisory and the recommendation in plain language.
What if a controller cannot be updated?
Then the agent shows the manufacturer's alternatives, such as switching off a service, separating the network segment or opening remote access only when needed. The machine stays marked as a risk, with the decision on who carries it and until when. At the next maintenance or when an update appears, demi brings the case back.
