Platform User Journey

The typical user journey on OpenVPP would go as follows:

User Connection into VPP:

• User lands on a utility or device vendor hosted web page

• User enters qualification information into the web page

• Device make, model, and identifier (e.g. serial number)

• Address and other site data if needed (may be pre-populated by the device vendor or utility)

• Payment is gathered if needed (depending on program, the cost may be paid by the device vendor or utility instead of the user)

Enrollment

• Enrollment request is passed to the OpenVPP Routing Service via API

• Connectivity parameters, certificate, and any other data needed for authentication are returned

• Device connects to utility server

User Successfully Connected Device to Utility

• Any other utility side program enrollment continue ̈

• User device can now be controlled and compensated for based on terms of the program

• Connecting a device requires a one-time protocol fee, paid in $OVPP or in stablecoins/fiat. Separately, device owners may earn compensation from the utility programs they enroll in, such as demand response payments. Those payments come from the program, not from the token.