Onboarding & Integration

A typical device aggregator or utility interaction for connecting to the OpenVPP Integration Service:

• Device aggregator or utility identifies which protocols their server can speak, server addresses and join requirements, and the capabilities within those protocols

  • Device aggregators also share the device types, models, and certificate structure

  • Utilities share their territory and program mappings, and their program details

• The servers connect to the Integration Service using OpenVPP APIs

  • Test exchange of Registry data

  • Test protocol and capabilities of the devices and utility control

  • Test exchange of certificates

• Device aggregator and utilities integrate the Routing Service APIs to their program web pages allowing for the connection of a device to a utility

  • The OpenVPP website will also have a routing page which would allow device aggregators and utilities to avoid this integration step if they do not want to invest in a branded experience

OpenVPP lowers the barrier for connectivity to one connection for device manufacturers and utilities. With one connection, unlock the entire world of connections.

Create a stable, secure, and unified global connection with OpenVPP through a global registry for all DERs. An open-source layer 1 or layer 2 blockchain will be studied as a technology that could help democratize, coordinate, and support unique DERs across the world through standardized industry protocols:

Asset Type	VPP Standard
Inverter	IEEE 2030.5
Heat pumps, pool pumps, thermostats	OpenADR2.0, 3.0
Electric Vehicles	OCPP 1.6J and OCPP 2.0

Through a unified, Web3 based VPP, devices and programs, utilities and aggregators will be able to join devices with programs through a distributed consensus based on validator approval. This ensures security and longevity for devices subscribed into consumer programs.