Implementing OpenADR with NOVA


The nebland software NOVA VEN stack provides our customers a fast path to a compliant OpenADR 2.0b VEN. Dozens of companies have implemented NOVA on device or in the cloud. Some of our customers manufacture or manage thermostats, car chargers, lights and lighting controllers, energy management gateways and other devices, while others offer energy management/building management solutions. This wide customer base shows both the broad applicability of OpenADR, and also the flexibility of our software to integrate with customer systems.

How is this flexibility achieved? Through a microservice architecture.

Integrating with a Microservice

NOVA is a microservice which runs as a standalone executable. It exposes an API for sending messages to NOVA, and uses a customer written communication plugin for communicating to the external system.

Here are two benefits of a microservice approach:

  1. Microservice integration is language agnostic. The external system can be written in any language using any tools with the only requirement being that it expose an API.
  2. With the OpenADR driver running separate from the external system, there’s a clean separation of concerns. Microservices promote loose coupling, allowing the two systems to be tested and developed independently.

Companies that have demand response capabilities are able to implement NOVA very quickly. We’ve helped companies from inception to implementation to compliance testing in as little as 2 weeks, but time frames from 1 to 2 months are more typical.

Implementing an OpenADR VEN 2.0b w/NOVA

NOVA provides a complete implementation of OpenADR and it’s certified by the OpenADR alliance. ALL of the OpenADR logic resides within NOVA. The customer system integrates with NOVA by implementing business logic: namely determining what devices to control and what type of control to perform during an event, and collecting telemetry data for reports. This functionality touches on two OpenADR services: EiEvent and EiReport.

There are many conformance rules that govern the interaction between a VEN and VTN regarding events and reports. Our customers don’t have to worry about any of them. Instead, requirements for implementing OpenADR are slimmed down to the following:

  1. Start control when an event starts
  2. End control when an event ends
  3. Query report data
  4. Asynchronous opt in/out of an event

That’s it! To implement OpenADR, the customer creates a simple communication plugin using simple APIs while the complex OpenADR logic, XML message formatting, and communication to the VTN is completely hidden and handled within NOVA.

Looking for More?

For information about OpenADR, visit the OpenADR Alliance website and see our OpenADR Overview presentation.

If you’d like to learn more about NOVA, contact us through the form below.

Posted in NOVA, OpenADR.