OpenVPP Docs
  • PROJECT OVERVIEW
    • Introduction
    • The $10T Problem OpenVPP is Solving
    • The OpenVPP Solution
    • Regulated Utility Vendor Distribution Model
    • Use Cases
    • Benefits for Utilities, Smart Device Vendors & Consumers
  • TECHNOLOGY OVERVIEW
    • Product Summary
    • Device Payment Rails & Stablecoin Customization Service
    • Routing Service
    • Registry Service
    • Integration Service
  • REGULATORY COMPLIANCE & ENVIRONMENTAL ACCOUNTING
    • Regulatory Compliance Use Cases
    • Environmental Credits & 24/7 Carbon Accounting
  • ONBOARDING PROCESS & PLATFORM USAGE
    • Platform User Journey
    • Onboarding & Integration
  • TOKENOMICS AND ROADMAP
    • $The OVPP Token
    • Tokenomics
    • Roadmap
Powered by GitBook
On this page
  1. ONBOARDING PROCESS & PLATFORM USAGE

Platform User Journey

PreviousEnvironmental Credits & 24/7 Carbon AccountingNextOnboarding & Integration

Last updated 11 days ago

CtrlK

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

  • It’s expected the $OVPP to connect would be in the $1-20 equivalent range, with value to the user per device around $100-1,000/year depending on the program and capability of the device.