Loading
Rooftop solar, batteries and EV charging turned customers into suppliers. CIS, MDM and the billing engine were built when power only went one direction. We connect them so meter to cash still works when the meter runs backwards.
FOUR SYSTEMS • ONE METER POINT
Where it breaks
A customer with panels and a battery is a consumer at eight in the morning and a supplier at one in the afternoon. Almost everything downstream of the meter was designed on the assumption that this never happens.
Export, net metering and time-of-use tariffs are handled as adjustments rather than as first-class events. Someone in revenue reconciles the difference, and the customer receives a bill they have to be talked through.
We carry import and export as separate measured quantities on the same meter point, priced by the tariff that applied at the time.
Interval reads land continuously while settlement runs on a cycle. Gaps get estimated to keep the run moving, and the estimate quietly becomes the number everyone works from.
We make validation and estimation a visible step, marking every figure measured or estimated and recording why.
SCADA registers the fault, the outage management system works the restoration, and the contact centre finds out when the calls start. Customers are told less than the utility already knows.
We publish outage events to customer channels as they are confirmed, so the first message comes from you rather than from a neighbour.
How it works
We normalise, validate and settle the reads, match grid events to the premises they affect, and every figure keeps the reads behind it.
Scroll the diagram sideways →
DLMS and MQTT from the meters, a CIM aligned model in the middle, REST and events for the enterprise. When a meter fleet or a tariff changes, you change a mapping and leave the architecture alone.
The runtime can sit regionally. It collects and buffers reads when the link to the centre drops, and settles them when it returns. Nothing about billing depends on a network being perfect.
Read completeness, estimation rate by route, settlement lag and failed publishes all land on one dashboard, so you spot a quiet meter fleet before the billing run does.
Products
MetricMonitor and DwaniAI read the same meter point and account model, so the figure a customer is told matches the one your settlement team is looking at.
Read completeness, estimation rates, settlement lag, asset health and integration status on one screen, with alerts before a billing run inherits the problem.
Explore MetricMonitor →Bill explanations, usage questions, outage status and service requests over voice and chat, in the languages your customers use. It escalates when the answer needs a person.
Explore DwaniAI →How we work
A wrong bill at utility scale is not one unhappy customer. It is a regulatory conversation. Every consumption figure we publish carries the reads it was built from and whether each one was measured or estimated.
It is included in every engagement. The new settlement path runs beside the existing one for a full billing cycle before anything switches.
An estimate stays visibly an estimate, with the method and the reason attached, and we replace it when the real read arrives. A disputed bill becomes a query rather than an investigation.
Grid integration reads from the operational side. We do not create a new inbound route to a control network, and restoration never waits on us.
Recent work
Anonymised at the client's request
A utility had rooftop solar arriving faster than its systems could account for it. Export was handled as a manual credit, estimation covered the gaps in interval data, and nobody could say how much of a bill was measured.
We put import and export on the same meter point as separate measured quantities, made validation and estimation a visible step, and published outage events to the customer channels as they were confirmed. The CIS was not replaced.
Talk to us about your estate →Questions
The integration layer goes in alongside, and the existing billing run keeps producing invoices throughout. New settlement runs in parallel for a full cycle so you can compare invoice by invoice before anything switches. There is no shutdown window, and the CIS is not modified.
Get started
Tell us where meter data enters your estate and where it stops being trusted. An integration architect reviews it and comes back within two working days.
