ArticlesRight-Sizing Software and Services for Distribution-Connected Battery Storage
The headlines belong to gigawatt-scale battery projects. But a meaningful share of near-term development activity sits below 20 MW, connected at the distribution level rather than transmission.
New York’s Value of Distributed Energy Resources (VDER) tariff is the clearest example already in motion, having built a real pipeline of sub-5 MW BESS sited to relieve local distribution constraints. Illinois’s newly signed Clean and Reliable Grid Affordability Act points to where more states may be headed: its first procurement is utility-scale, but the Act also directs the Illinois Power Agency toward a future distribution-oriented storage program. Wherever a state lands on the specifics, a distribution-connected project’s economics, interconnection requirements, and operational model differ from a transmission-connected one. Too many of these projects are being built with either transmission-scale service stacks that erode thin project economics, or stripped-down monitoring that looks fine on a pro forma and fails in year two.
The two mistakes come from different assumptions. The first assumes operating a smaller BESS is just operating a bigger one, scaled down. The second reaches for a first-of-a-kind, home-made, or adapted-from-elsewhere solution that is poorly suited to BESS specifically.
The services are the same. The service levels are not.
Distribution and transmission-connected projects need the same four operational functions. SCADA has to capture and interpret the data volume a modern BESS generates, since availability and equipment protection depend on it. Monitoring has to catch performance and alarm conditions in real time, not after a site visit reveals them. Reporting has to track performance against OEM warranty terms so defects get caught before they become expensive. And remote operations has to execute a dispatch or respond to a trip without rolling a truck.
Where the two scales diverge is service level, not service scope. A transmission-connected asset carrying NERC CIP obligations may need a 10-minute response window on manual dispatch instructions and the compliance infrastructure to prove it. VDER caps projects at 5 MW, but the same logic generally extends up to roughly 20 MW: NERC’s Bulk Electric System definition typically excludes distribution-connected generating resources at that scale, so most sub-20 MW projects don’t carry CIP obligations, regardless of which state’s program they sit under. Building to that standard anyway means paying for compliance overhead the project will never need. The inverse failure is just as costly: a distribution project with no real-time alarming that misses a performance window can lose a significant portion of its yearly value under performance-based tariffs, with no path to recover it until the next compensation period.
Why this matters more as the sub-20 MW pipeline scales
Sub-20 MW BESS economics are tighter than utility-scale from the outset, so every dollar of operating cost has to be justified against the revenue it protects. A developer who procures a package sized for the vendor’s transmission-connected fleet pays for overhead the project can’t support. A developer who procures the cheapest available monitoring, with no eye to what the tariff penalizes, is exposed to the one bad hour that erases much of the value in the year.
The projects most likely to underperform aren’t the ones with too little technology or too much. They’re the ones where there is a mismatch between the operational build to the project’s actual revenue mechanics and compliance obligations.
As distribution-connected BESS moves to a real asset class, that mismatch is the risk to underwrite at the design stage, not discover after commercial operation. Workbench Energy’s portfolio spans over 1,000 MW of BESS in North America, from multi-hundred MW transmission-connected projects to smaller distribution-connected systems, and scopes SCADA, monitoring, reporting, and remote operations to what each project actually carries.
