Elvo CPMS Manual View as:
Section 0.1 · All tiers

About this manual

Updated · 3 min read
On this page
  1. 01 What this manual covers
  2. 02 How the manual is organized
  3. 03 How to use this manual
  4. 04 Source of truth

The Elvo CPMS Platform is a multi-tenant SaaS dashboard for managing EV charging infrastructure: stations, locations, drivers, RFID authorizations, tariffs, energy management, and billing. This manual covers the day-to-day operations an operator performs in the web platform.

What this manual covers

The manual is split into eleven Parts. Each Part focuses on one area of the platform:

  • Part 0 — Introduction & Getting Started. Orientation, audience, tiers, first login, password change, glossary.
  • Part 1 — Dashboard. Accessing the Dashboard, adding and configuring widgets, widget interactions, and removing widgets.
  • Part 2 — Charging Sessions. The cross-station sessions view, filters, column configuration, navigating from a session to its related entities, and generating consumption reports.
  • Part 3 — Error Logs. Accessing the error log, filtering and analyzing events, and exporting data.
  • Part 4 — Locations. Managing locations, adding and editing them, and the interactive map view.
  • Part 5 — Stations: onboarding. The stations control panel, importing single and multiple stations, activating them, and list filtering.
  • Part 6 — Stations: advanced operations. Per-station tabs: Connectors, Details, Pricing, Location settings, Reset (soft/hard), Auto-start, Card access restrictions, Firmware update, Sessions, and Event Logs.
  • Part 7 — Energy Management. Weekly charging profiles and load-balancing groups for smart charging.
  • Part 8 — CRM. RFID Cards (Authorizations), Drivers, and Tariff plans.
  • Part 9 — Billing. Driver invoices and their export options.
  • Part 10 — Administration. Adding administrators and a high-level overview of roles and permissions.

How the manual is organized

  • Parts are numbered 0 through 10. Each Part is a top-level chapter.
  • Sections inside a Part are numbered as <part>.<index> (for example, 4.2 Adding a new location). Each section lives on its own page in the HTML build.
  • Tier badge. Every section header carries a tier badge — All tiers, Enterprise + Partner, or Enterprise only — that tells you which tier the content applies to. The same badge is also used to filter the manual to a single tier in the HTML build’s top-right selector. Tiers are explained in section 0.2.
  • Inline tier callouts. When the UI differs by tier at the step level, the relevant step is annotated with {tier: enterprise}, {tier: partner}, or {tier: client} so the variation is visible without leaving the section.
  • Cross-references. Sections that build on another section’s content link to it by Part/section number (for example, “see section 6.6”).
  • Glossary. Section 0.5 defines terms used throughout the manual. When a term appears for the first time inside a section, that section may bold it for emphasis; the canonical definition always lives in the glossary.

How to use this manual

  • Reading top to bottom is not required. Each section is self-contained; pick the Part that matches your task and jump directly there.
  • First-time users should at least read Part 0 in full and skim Part 1 (Dashboard) and Part 4 (Locations) before adding stations in Part 5.
  • Search. The HTML and PDF builds are searchable; the chatbot knowledge base (built from the same source files) is also searchable in natural language.
  • Screenshots were taken on the Elvo demo environment with the locale set to English. Your tenant may apply a different logo, color palette, or brand name (see section 0.2), but the layout and labels of the platform itself are the same.

Source of truth

This manual reflects platform behavior as documented in the Elvo CPMS specification (Document 1 — Product scope and structural rules, Document 2 — Shared UI patterns, Document 3 — Flow specifications). When a behavior in this manual diverges from what you see in the live platform, raise an issue so the documentation can be corrected — never assume the manual is wrong.