Skip to content
Quality, standards & complianceWater & Environment

Check drinking-water results against limits

An exceedance shows as soon as the lab result arrives, and the notification is already prepared.

Today

Lab results, plant readings and operator notes sit in separate files. When a limit is exceeded it has to be reported fast, and someone writes the operating log by hand at the end of the shift. Exactly when time matters, it is lost to searching.

An example

A municipal water association runs a waterworks with membrane filtration (0.1 µm) and UV disinfection (254 nm), both supplied by Aldevo Wassertechnik. The result from the north reservoir shows 3 coliform bacteria per 100 ml against a stored limit of 0. The agent flags it, places the last 12 samples from that point and the day's UV logs beside it and drafts the notification for the plant manager.
Fictional company, typical workflow.

Your data, wherever it lives

Today lab results arrive as LIMS exports or as PDFs by e-mail, plant readings come from the control system, limits and operator notes sit in spreadsheets, and someone writes the operating log by hand at the end of the shift. demi reads, understands and links them per sampling point, with your rights. As soon as a result is in, demi checks every value against its limit, the AI shows the point's history and drafts the notification with no searching when time matters most, and the responsible manager approves.

Where the data lives today

  • Databases
  • PDFs
  • E-mails
  • Machines & sensors
  • 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

    The case needs data from the LIMS, SCADA export, spreadsheets and e-mail. demi replaces nothing and ties every result, with readings, notes and the stored limit and action values, to its sampling point and that point's history. demi only writes back after approval.

  2. 2 · PermitPermission Layer

    Operators record readings and notes. Only the responsible manager approves a notification to the authority, and every approval is recorded.

  3. 3 · ActIntelligence Layer

    The agent compares every result deterministically with its limit, flags exceedances with context and drafts the notification. Every statement points to its result and sampling point.

How it runs

  1. 1

    The lab result arrives as an export or by e-mail

  2. 2

    demi maps every value to its sampling point and its limit

  3. 3

    The agent flags exceedances and shows the sampling point's history

  4. 4

    The manager reviews the draft notification and releases it

  5. 5

    The daily log entry is done, with sources

What changes

  • Exceedances visible as soon as the result arrives

  • A complete operating log without catch-up writing

  • Notifications prepared, the decision stays with the manager

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

+120 hfreed per year

Assumptions and calculation

demi checks each lab value against its limit and keeps the log; you decide on any deviation.

10 min → 6 min per case

How does it run today?

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

How we calculate

150 lab results × 10 min × 40% × 1.0 (manual) × 12 months = 7,200 min = 120 h

Value per year, before demi costs

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

+€7,800

gained per year

120 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

Which limit values does demi use?

The ones you store: legal limits, values from your permits and your own warning or action levels per parameter and sampling point. demi never invents a limit. When a value changes, the responsible person updates it and the change is recorded.

Can demi read our lab exports?

Yes. Results often exist as a LIMS export, a CSV file or a PDF by e-mail. demi reads parameter, unit, sampling point and date from the file and maps them. Values that cannot be mapped with certainty go to the operators for review instead of slipping into the record.

Who sends the notification to the authority?

Always a person. The agent drafts the notification with the result, the history and the actions taken. The responsible manager reviews it, edits if needed and releases it. Nothing goes out without that release.

Does demi replace our operating log?

No, it fills it. The agent drafts the daily entry from readings, results and notes, and the operators complete and confirm it. The log stays where you keep it today, and demi writes back only after approval.

What happens at night and at weekends?

The check runs as soon as a result arrives, outside working hours too. You decide per parameter who is alerted when a limit is exceeded, for example the on-call operator.

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