Skip to content
Management & reportingCleaning & Facility Services

Cleaning machines by telematics: use per site

AI links run time, area output and battery state of every machine to its site, service specification and hours worked.

Today

More than a hundred scrubber dryers and sweepers are spread across many sites. At one site a machine stands idle most of the month; at the next, a hall is cleaned by hand although the service specification calls for machine cleaning. Contracts are priced on machine output, but nobody checks whether that output is really delivered.

An example

Blank & Kamp services 140 sites with 160 cleaning machines. The agent shows that an SSM B 650 scrubber dryer in an office building in Essen ran only six hours in October. At a logistics center in Gladbeck, meanwhile, 9,000 m² of hall floor were cleaned by hand although the service specification calls for the machine, and the team needed 64 hours more than costed. Regional management moves the machine to Gladbeck.
Fictional company, typical workflow.

Your data, wherever it lives

Run times, area output and battery data sit in each manufacturer's telematics portal, sites, contracts and service specifications in the ERP, hours worked in time recording and repairs in spreadsheets. demi reads, understands and links them, with your rights, per machine and site. The AI sees in minutes where machines stand idle or are missing, and regional management decides what gets moved.

Where the data lives today

  • Telematics
  • Machines & sensors
  • ERP
  • Office files
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: the manufacturers' telematics portals, the ERP, time recording and spreadsheets. demi replaces nothing and links run time, area, battery data, location and repairs to machine and site, together with contract, service specification and hours worked per site.

  2. 2 · PermitPermission Layer

    Site managers see their sites and machines, regional management its region. Hours worked appear only per site, never per person, and you agree with the works council which analyses exist. Every relocation is recorded.

  3. 3 · ActIntelligence Layer

    The agent computes utilization and area output exactly from the telematics data and sets them against the target area and frequency in the service specification. It flags machines that stand idle, are missing or do not suit the area, and proposes relocations, battery replacements and maintenance, each with the figures behind it.

How it runs

  1. 1

    Telematics reports run time, area output, battery state and location for every machine.

  2. 2

    demi assigns each machine to its site and places the service specification and hours worked next to it.

  3. 3

    The agent flags machines that stand idle, are missing or do not suit the area.

  4. 4

    It proposes relocations, battery replacements and maintenance, each with the figures behind it.

  5. 5

    Regional management decides, and the following month the agent checks whether the move paid off.

What changes

  • Machines where they clean the most floor

  • Costing and actual use match

  • Fewer rental machines and wrong purchases

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.

Assumption, editable

Your numbers

Result

+192 hfreed per year

Assumptions and calculation

demi links telematics, service specification and hours worked per site; you decide what moves.

30 min → 18 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

80 site reviews × 30 min × 40% × 1.0 (manual) × 12 months = 11,520 min = 192 h

Value per year, before demi costs

Freed per year+192 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

+$12,480

gained per year

192 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 package

Questions about this use case

Does demi use this to monitor our cleaning staff?

No. The analysis is per machine and site, not per person. Hours worked are used only as a total per site. You agree with the works council which analyses exist and who sees them, and demi keeps to those rules.

Does it work with cleaning machines from different manufacturers?

Yes. demi takes the data from the manufacturers' telematics portals or exports and harmonizes it per machine. For machines without telematics, the hour meter is enough, for example as a photo of the display or from the service report. So every machine appears in one list with the same figures, whichever manufacturer built it.

How does the agent know how a site should be cleaned?

From the service specification in the ERP or the contract files: areas, floor types, frequency and whether cleaning is by machine or by hand. Every comparison shows the line item it comes from. If something is missing, the agent asks the site manager instead of estimating.

Who decides whether a machine is relocated?

Regional management. The agent proposes the move with run times, areas and costs, and an authorized person makes the decision. Afterwards the agent compares the month before and after, so you can see whether it paid off.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases