OpenADR 3.0: The evolution of a smarter, simpler protocol

OpenADR 3.0 represents a significant step forward in demand response (DR) and energy management technology. It reflects the growing need for interoperability, reduced complexity, and greater flexibility in modern energy ecosystems. With a focus on standardization and extensibility, OpenADR 3.0 addresses challenges faced by developers and utilities, ensuring the protocol remains relevant as energy systems evolve to incorporate distributed energy resources (DERs), virtual power plants (VPPs), and grid flexibility initiatives. 

By adopting the ‘convention over specification’ approach, OpenADR 3.0 reduces the need for extensive custom configurations, allowing users to rely on defaults and conventions. 

Key feature changes in OpenADR 3.0

OpenADR 3.0 introduces a range of enhancements designed to simplify energy management and improve the flexibility of Demand Response programs. These updates focus on making implementation easier for developers and energy managers while ensuring the protocol meets the evolving needs of modern energy systems. 

1. Program management 

A new feature in OpenADR 3.0 is introducing a “program” construct. This allows users to describe metadata for Demand Response (DR) offerings in a standardized way. Energy providers can offer detailed and consistent information about their DR services by organizing and defining programs. 

2. VEN and resource management 

While enrollment remains an out-of-band process, OpenADR 3.0 introduces a dedicated API for Virtual End Nodes (VENs) and their associated resources. This makes it easier for Virtual Top Nodes (VTNs) to manage relationships with individual resources and VENs, streamlining communications and reducing manual intervention. 

3. Push via subscription 

OpenADR 3.0 continues to support bi-directional data exchange but now allows for communication through webhooks. 

4. Event priorities 

With OpenADR 3.0, VTNs can offer multiple programs simultaneously and assign priority levels to each event. This ensures critical programs receive the attention they need while allowing less urgent programs to run in parallel without conflict. 

Objects: Creating and managing

OpenADR 3.0 introduces a refined and structured methodology for handling energy system objects, designed to make implementation straightforward. Key components are organized into clearly defined categories to provide structure and clarity. 

OpenADR 3.0 includes a variety of objects designed for specific tasks: 

  • Program: Defines energy-saving initiatives. 
  • Event: Details actions within a program. 
  • Report: Shares energy usage data. 
  • Subscription: Handles notifications for real-time updates. 
  • VEN: Represents devices in the system. 
  • Resource: Refers to individual assets managed by a VEN. 

Each object has a unique ID to ensure consistency in component relationships, like associating an event with its program. These objects also have human-readable names and descriptions. 

Event participation management

In OpenADR 2.0b, the handling of “opt” functionality required a separate mechanism for declaring plans of participation or withdrawal from events. OpenADR 3.0 has modified this process by integrating opt-like behaviors into event definitions. 

VTNs can now define a program or event that specifies reporting requirements. For example, a VTN might require a VEN to report its predicted load shed capacity before the event starts. This approach simplifies use cases where opt information is not required. At the same time, it retains the flexibility to implement the same level of detail as before by embedding opt-like functionality directly within reports associated with event and program constructs. 

The extensibility features

OpenADR 3.0 allows for model extensions in the form of the addition of custom constructs to existing models, enabling users to extend standard definitions as required. Unrecognized extensions are ignored by VTNs, ensuring that standard operations are not disrupted, even if custom extensions are introduced. 

Custom values, called private strings, can be added to object fields with mutual agreement between VTNs and clients. This feature allows systems to accommodate additional data without altering the core behaviors of the protocol, while addressing specific operational requirements. 

Changes in security

OpenADR 3.0 moves away from specifying custom security requirements, instead adopting widely accepted standards. 

Mutual TLS is no longer necessary for securing communications. Now, only the server (VTN) is required to provide a certificate, simplifying the setup and configuration. Additionally, the TLS requirements have been adjusted to reduce complexity while maintaining secure connections. 

In the new security model, VENs receive their credentials out-of-band. The protocol recommends using JWT bearer tokens for authentication, supporting a standardized and secure credential exchange process. 

Documentation and testing

OpenADR 3.0 provides documentation and tools to facilitate implementation with minimal reliance on detailed specifications. 

The User Guide and Definitions documents offer examples and explanations to clarify the protocol’s structure for deployment. The API in YAML format supports integration and enables program management. Additionally, a Testing & Certification Tool is available for OpenADR members to verify compliance with OpenADR 3.0 standards. 

Conclusion: OpenADR as a key to success

OpenADR 3.0 offers a flexible implementation process with a structured framework. The protocol focuses on extensibility, clarity, and supportive documentation, allowing developers to create customized solutions while ensuring compliance. These updates make this protocol a practical tool for modernizing energy management and adapting to the evolving needs of the energy sector. 

Take the next step toward smarter integration

OpenADR 3.0 sets a new standard for efficient and flexible energy management, paving the way for smarter demand response solutions. If you’re ready to streamline your energy programs, enhance interoperability, and adapt to evolving grid requirements, Codibly can support you every step of the way. With deep expertise in energy technology and a commitment to innovation, we can help you implement the protocol seamlessly and unlock its full potential.

Contact us today to explore how OpenADR 3.0 can empower your business and drive energy innovation forward.