On April 30, 2026, the SunSpec Alliance and Codibly — a SunSpec Authorized Test Lab — co-hosted a webinar on how IEEE 2030.5 is shaping the next generation of grid flexibility. The session moved beyond protocol theory into how standardized DER communication is actually being deployed by utilities, aggregators, and OEMs, and why adoption is spreading from California into international markets.

Spencer Borison, US President at Codibly, and Patryk Bober, Senior Technical Consultant at Codibly, presented alongside the SunSpec Alliance.

Webinar highlights

1. 2030.5 is the connective tissue for DER
The standard gives utilities, aggregators, and distributed resources — solar, storage, EV charging — a common language, and it is increasingly mandated under frameworks such as California’s Rule 21.

2. Policy is pulling adoption forward
Grid modernization and regulatory mandates are accelerating the need for standardized DER communication well beyond California’s early lead.

3. The hard part is integration, not the protocol
Most of the implementation effort lies in aligning with utility-specific requirements and validating end to end — not in the protocol specification itself.

4. Real architectures, real complexity
Server and client architectures for utilities and aggregators must translate grid signals into reliable asset control; this boundary is where deployments succeed or stall.

5. Multi-protocol support reduces risk
Because 2030.5 coexists with standards like SunSpec Modbus, OEMs that support multiple protocols widen the range of utility programs and platforms their products can serve.

6. Certification testing exposes shortcuts
A rigorous test suite reveals where an implementation cut corners — making certification a proxy for production-grade quality, not a box-ticking exercise.

Watch the full webinar below:

Looking ahead

IEEE 2030.5 is steadily leaking out of California into other US states and international markets. The next frontier is moving from device-level certification to validating entire systems of systems, where utility-specific customization and operational complexity decide whether flexibility scales.

For the written deep-dive on where the protocol actually lives in production systems, see Where the IEEE 2030.5 Protocol Actually Lives.