Today
Energy suppliers, grid operators and metering operators exchange large volumes of market messages every day. Rejected messages and metering exceptions pile up and are solved by hand. The same master data errors keep coming back.
An example
A metering operator in Lusatia runs meters made by Wattaris. The grid operator rejects a meter reading message, and the agent finds why: after a meter change, the customer record still holds the old meter number instead of ZM-40712 (MID). It drafts the master data correction and the new message, and the case worker approves both.
Your data, wherever it lives
Today contracts, master data and billing sit in the ERP, meters and readings in the meter data management system, market messages and rejections come in by e-mail and through portals, and open cases are tracked in spreadsheets. demi reads, understands and links them per metering location with its full history, with your rights. The AI finds the contradiction behind a rejected message in minutes instead of after a long search and drafts the correction and the reply, and your case worker approves both.
Where the data lives today
- ERP
- Databases
- E-mails
- Web & portals
- 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: ERP, portal, e-mail and spreadsheets. demi replaces nothing and keeps each metering location as one record with its full history of market messages, meters, readings, contracts and master data. demi writes back only after approval.
- 2 · PermitPermission Layer
Case workers decide on every case and approve every master-data correction and every reply message. This is recorded with its reason.
- 3 · ActIntelligence Layer
The agent classifies each error and finds the inconsistency by checking the message against master data and readings by fixed rules. It drafts the correction and the reply message from the recorded data, with its source.
How it runs
- 1
A rejected message or an exception comes in.
- 2
The agent classifies the case and looks for the cause in the data.
- 3
The case worker sees cause, correction and draft reply, with evidence.
- 4
Once approved, demi writes the master data correction back.
- 5
Recurring error patterns are collected and reported.
What changes
Smaller backlog of open cases
Cases resolved faster
Fewer recurring errors
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
+360 hfreed per year
Assumptions and calculation
demi assigns each error message and finds the cause in the master data; you approve the fix.
15 min → 9 min per case
How we calculate
300 error messages × 15 min × 40% × 1.0 (manual) × 12 months = 21,600 min = 360 h
Value per year, before demi costs
Freed per year+360 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
+$23,400
gained per year
360 h ÷ 1,760 h per role = 0.2 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
Which message types does demi cover?
demi checks messages, for example on supplier changes, master data changes and meter readings, that arrive in your systems and mailboxes. You decide which processes to connect first, based on where most of your cases come from. Your market communication system stays in place.
How are corrections approved?
Every master data correction starts as a proposal with its cause and evidence. The case worker approves or edits it, and only then does it go back. demi writes back only after approval. Who approved what and when is recorded.
Can the agent read meter readings and metering data?
Yes. Readings and metering data from the ERP, portals and spreadsheets are attached to their metering location. That way the agent can see, for example, whether a value was recorded before or after a meter change.
Does the agent send messages to the market itself?
Not without approval. It drafts the reply, and the case worker checks and approves it. The message then goes out through your existing system as before.
