Most distributed energy operators cannot tell you the real-time state of their asset portfolio. Ask a commercial microgrid operator what their battery state of charge is right now across all sites, and you will typically get one of two answers: a number from the last dashboard refresh cycle — which may be minutes old — or an honest admission that they need to check individually.
This is not a data availability problem. The data exists. Every inverter, every battery BMS, every smart meter is generating telemetry continuously. The problem is aggregation. The data is siloed in vendor portals, each with its own refresh rate, its own data model, and its own access mechanism. Pulling a unified operational picture requires a human to open four different tabs and mentally reconcile the numbers.
The visibility gap has real costs. An operator who cannot see a developing battery fault across a multi-site portfolio until the next dashboard refresh cycle is an operator who is reacting to events rather than managing them. In demand response contexts, a 30-second visibility lag can mean the difference between a successful curtailment response and a penalty event.
The gap widens as asset portfolios grow. A five-site portfolio with manual dashboard reconciliation is manageable. A fifty-site portfolio is not. The operational overhead scales linearly with asset count when your tooling is built around polling individual vendor systems. The alternative — a unified event stream where every asset publishes state changes as they occur, to a single platform — scales sublinearly. The monitoring overhead does not grow with the portfolio.
This is the operational case for event-driven architecture that rarely gets made explicitly. The security and performance arguments are easier to articulate. But the visibility argument may be the most practically relevant for operators today: a platform that shows you what is happening across your entire portfolio in real time, without manual reconciliation, is worth implementing on operational grounds alone.
GridWatch was designed to close that gap. The platform aggregates telemetry from every asset type into a unified operational view — not by polling vendor portals, but by subscribing to the event stream each asset produces natively.