> For the complete documentation index, see [llms.txt](https://openvpp.gitbook.io/openvpp-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://openvpp.gitbook.io/openvpp-docs/onboarding-process-and-platform-usage/platform-user-journey.md).

# 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
* 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.