Today
Lithium batteries in commercial and bulky waste cause smouldering spots and fires in sorting plants more and more often. The thermal camera flags the hotspot, the loader driver pulls it out, and the plant logbook gets an entry. Nobody checks which customer delivered the load, because alarms, weighbridge and customer data never meet. So batteries from the same sources land in the bunker again every week.
An example
At Wertora Recycling, the thermal camera over the bunker of the commercial waste sorting line reports 23 hotspots in October, four of them with extinguishing. The agent assigns 19 of them to loads with high confidence: eleven come from containers of just three customers who together deliver a tenth of the volume, among them an electrical wholesaler with mixed packaging waste from its returns department. It prepares evidence with camera images per customer for sales and, following the contract, proposes a talk and visual checks at tipping first, and the agreed contaminant surcharge if it happens again. The plant manager agrees, and the wholesaler sets up its own collection box for batteries.
Your data, wherever it lives
Fire events sit today in the alarm logs of thermal cameras and extinguishing systems and in the plant logbook, deliveries in the weighbridge database, customers and contracts in the ERP and CRM, tipping images on the video server and battery finds, if anywhere, on a tally sheet. demi reads, understands and links all of it per alarm and load, with your rights. The AI shows in minutes which customers the batteries come from; plant management and sales decide what happens with the customer.
Where the data lives today
- Machines & sensors
- Photos, video & audio
- Databases
- ERP
- CRM
- Office files
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 fire detection and extinguishing systems, the weighbridge, ERP, CRM, the plant logbook and the cameras at the tipping points. demi replaces nothing and links every alarm with time, bunker section and temperature to the loads tipped there before it: weighbridge ticket, license plate, waste code, customer, contract and the camera image of the tipping. Battery finds from the picking cabin are added by photo.
- 2 · PermitPermission Layer
Alarms and evaluations per customer are visible to plant management, fire safety and the sales staff of that customer; contract data and prices only to sales and executive management. The analysis covers customers, waste types and rounds, not individual drivers; license plates only serve to find the load. A talk, a surcharge or an acceptance ban is decided by authorized people, according to the customer's contract.
- 3 · ActIntelligence Layer
The agent assigns every hotspot by time, position in the bunker and camera images to the likely loads and states how certain the assignment is. Over weeks it shows which customers and waste types trigger alarms unusually often relative to their volume. For every conspicuous customer it prepares evidence and a proposal under the contract: a talk, visual checks at tipping, a surcharge or an acceptance ban. Assignments and rates are computed with fixed rules; the language model only writes the texts.
How it runs
- 1
The thermal camera reports a hotspot in the bunker; demi records time, bunker section, temperature and any extinguishing.
- 2
The agent finds the loads tipped at that spot beforehand, with weighbridge ticket, customer, waste code and camera image.
- 3
Battery finds from the picking cabin and entries in the plant logbook are added by photo and voice.
- 4
Every week the agent shows which customers stand out relative to their volume and prepares evidence and a proposal under the contract per customer.
- 5
Plant management and sales decide on a talk, checks, a surcharge or an acceptance ban and speak to the customer.
What changes
You know which customers bring batteries into the bunker
Customer talks based on evidence instead of guesses
Fewer fire events and clean records for insurers and authorities
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
+90 hfreed per year
Assumptions and calculation
demi assigns every alarm to its loads and prepares evidence per customer; you decide on measures.
60 min → 42 min per case
How we calculate
25 hotspot alarms × 60 min × 30% × 1.0 (manual) × 12 months = 5,400 min = 90 h
Value per year, before demi costs
Freed per year+90 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
+$5,850
gained per year
90 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 assign a hotspot to a load when everything in the bunker is mixed?
By time and place: the camera reports in which bunker section it gets hot and when, and weighbridge and tipping records show which loads landed there before. Camera images of the tipping narrow it down further. Every assignment carries a confidence level, and unclear cases never count against a customer.
May we charge a customer a surcharge?
Your contract with the customer settles that, for example a clause on contaminants. demi shows the relevant clause and compiles the evidence: alarms, weighbridge tickets, camera images. Whether and how the clause is applied is decided by sales and executive management.
Which data does demi need from fire detection?
The alarm log with time, position and temperature, as the fire detection or control system exports it, plus the extinguishing records. Stored thermal images help but are not required. No new cameras are needed if thermal cameras already watch the bunker.
Are the customers' drivers rated?
No. The analysis covers customers, waste types and rounds. License plates and weighbridge tickets only serve to find the load and are deleted after the periods you set.
