Background on OpenADR
Automated grid flexibility is critical to a renewable energy powered grid by ensuring electricity is used when it is cleanest and cheapest. Automating via Open Standards reduces implementation costs and improves interoperability of programs, which means more money can go towards incentivizing the participation and innovation necessary to support the clean energy transition.
Top open standards for load shifting include OpenADR, DNP3, IEEE 2030.5, and a number of others that are used in specialized scenarios. OpenADR is the most mature and typical go-to option for demand response / load shifting programs.
As a device manufacturer or aggregator, implementing OpenADR unlocks participation in load shifting programs and a way to monetize your load flexibility. California has also mandated implementation for certain device types through its title 24 building codes, and other states are following suit. Check out our growing list of programs that use or require OpenADR to see where it is being used, incentivized and/or required.
As a utility, using OpenADR avoids vendor lock-in, since the end device connections can be transferred to a different OpenADR server. In fact, OpenADR has been around long enough that we have seen this in action: utilities such as PG&E, Hawaiian Electric and Austin Energy have transferred over their device controls server (their VTN, in OpenADR-lingo) without having to re-engineer device connections. This is a big win for utilities and for program interoperability.
For all companies providing grid flexibility, standardization around OpenADR leads to lower implementation costs and hassle, so we can focus more on increasing customer participation, device controls logic, and, ultimately, enabling load flexibility to be an integral part of the clean energy transition.
GridFabric’s products allow companies to implement OpenADR on their platforms and gain certification with the OpenADR alliance, faster and more cost effectively than doing it themselves.
With two product lines Plaid (Client) and Canvas (Server) - which together facilitate communication between power consuming, internet connected products and utilities or load aggregators, respectively. Plaid and Canvas do not both need to be present for successful programs: both products will be able to add value individually or together in any demand response or load shifting program that implements OpenADR.
Canvas: Canvas implements a Virtual Top Node (VTN), the server side of the OpenADR protocol. It is used by Grid Operators and Aggregators to administrate load shifting programs.
Plaid: Plaid implements a Virtual End Node (VEN), the client side of the OpenADR protocol. It is used by controls and IoT product companies to participate in load shifting programs.
Buy Vs Build
We minimize integration cost with a microservice implementation and flexible HTTP integration with the microservice, allowing most customers to implement in a "just in time" manner - integrate just the parts you need now. This also keeps operating costs down: since the integration between the microservice and our customers platforms is simple, there isn't too much to do to update it.
We keep our cost structure simple, so customers can easily compare the cost to buy our solution vs the time and opportunity cost of building and operating themselves.
Our philosophy in offering an option to buy protocol implementations rather than build is simple: our customers are in the business of providing valuable solutions to their customers, not implementing protocols. Protocol implementation is table stakes, not a competitive advantage. By taking the protocol out of their hands and making it simple to implement while being as close to the "perfect internal tool" as possible, we help them focus on what they do best.
For more information on GridFabric’s products, complete the request form or visit gridfabric.io. To learn more about load shifting, OpenADR and how GridFabric’s products work, please visit our blog at gridfabric.io/blog.