What an energy data layer does — and where it stops
A unified energy data layer pulls readings from everything on site — the utility meter, the inverters, sub-meters, sometimes the generator controller — into one screen, so you stop logging into five vendor portals. That is real value: one place, one login, live numbers.
But aggregation is not the same as trust. Putting five feeds on one dashboard tells you what each device reported; it does not tell you whether the totals add up, which source actually served a given hour, or what any of it cost. The hard part was never displaying the data — it was deciding when the data can be trusted.
Reconciliation: the harder job
Reconciliation takes those feeds and turns them into quantities a business can act on: grid import net of solar export, peak versus off-peak, and generator energy kept separate from grid energy — with every aggregate’s parts made to sum to the whole and tie back to the meter’s own lifetime register.
When the numbers cannot be reconciled, an honest platform says so instead of filling the gap. That is the line between a dashboard that looks complete and a figure you can put on an invoice.
- Sources separated (grid / solar / generator), never blended.
- Solar export netted against grid import.
- Time-of-use windows applied per business.
- Every total reconciled to the meter’s lifetime register — or labelled unknown.
The generator gap
Most energy-data platforms are built for grid-plus-solar markets. They rarely account for a diesel generator running several hours a day — which is the norm for a Pakistani factory. Blend the generator’s units into the grid’s and the cost picture is already wrong, because a diesel unit and a grid unit cost very different amounts.
Reconciliation keeps the generator on its own line, counts its runs, and attributes cost to the right source. Without that, “unified data” quietly hides the most expensive electricity on the site.
Data layer vs reconciliation, side by side
Both start from the same feeds. Only one produces a number you can defend to a CFO.
| Energy data layer | Energy reconciliation (WattEY) | |
|---|---|---|
| Job | Collect readings in one place | Turn them into one trustworthy cost number |
| Trust model | Trusts the incoming data | Checks the parts sum to the meter’s register |
| Sources | Often blended | Grid / solar / generator kept separate |
| Missing data | Filled or hidden | Labelled unknown, never invented |
| Output | A dashboard | A number you can bill from |
“A dashboard that shows five feeds is not a number you can bill from. Reconciliation is the difference — it either ties to the meter’s own register, or it tells you it doesn’t know.”— Engr. Reyyan Niaz Khan, founder, BijliBachao.pk
Why this is a Pakistan problem first
A commercial or industrial site here runs on grid, rooftop solar and a diesel generator at once, under net billing and time-of-use tariffs, and receives one confusing bill. That is exactly the mess reconciliation was built for — and it is why a generic data layer designed for a stable, grid-plus-solar market misses the point.
This is the category behind WattEY: not another place to look at data, but the layer that decides what the data means and what it cost.
