Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

TandemDrive general

Instance

A TandemDrive instance refers to a fully isolated deployment of the TandemDrive platform, for clients who have a Software-as-a-Service (SaaS) agreement. Each instance operates independently, ensuring complete data and operational isolation for its users.

Sellers

A seller is the entity responsible for offering electric vehicle (EV) services, which can include Mobility Service Providers (MSPs) and Charge Point Operators (CPOs).

Within a TandemDrive instance, multiple sellers can coexist, allowing for flexible service offerings and branding strategies.

Administrations

An administration in TandemDrive is a method of organizing and structuring data within a single instance. Administrations can be set up based on criteria like organization, country, or brand, creating distinct segments within the platform, each with its own operational rules. The use of separate administrations has several key implications:

  • Each administration operates with a single currency.
  • Billing configurations are unique to each administration. For instance, invoicing series are not shared between administrations.
  • Administrations are linked to a specific seller, though multiple administrations can share the same seller.
  • Subscription plans are managed independently within each administration.
  • API access can be limited to one or more administrations, enabling tailored data visibility and security controls.

Some information can be shared across multiple administrations under certain conditions:

  • MSP rate plans can be shared between administrations, provided they use the same currency.
  • Customers are primarily associated with one administration to facilitate API segmentation but can hold subscriptions in multiple administrations. The billing for these subscriptions is processed according to the rules of its administration.
  • The Roaming setup is shared across administrations.

Parties and Customers

In TandemDrive, parties represent entities (referred to as “accounts” or “relations” in other systems) that hold predefined roles, such as Customer or Roaming partner. Parties share a unified data structure, allowing them to participate in billing activities.

However, when using the TandemDrive Console or API, you often interact with more specific concepts like Customer or Roaming partner, rather than directly with the broader concept of a Party.

A Customer is a specific type of Party that utilizes one or more services managed within TandemDrive. These services might include token subscriptions, reimbursements, and charge point subscriptions.