| Odoo |
Commercial (CRM / ERP) |
System of record for commercial transactions: customers, products, pricing, sales orders, payments, invoices, and subscriptions (see 5.6 Odoo Models). |
| ABS (Asset Backoffice System) |
Asset / Entitlement |
System of record for assets, entitlements, BSS services, bundles, plans, and usage events. Handles smart asset operations and pool management (see 5.7 ABS Models). |
| DIRAC |
Analytics / Orchestration |
Emerging platform for advanced analytics, ML, and cross-system orchestration across Odoo and ABS (see 1.6 Dirac-Odoo-ABS). |
| OVApp |
Client / Frontend |
Customer and agent application that drives sales and service flows by calling Odoo and ABS APIs. In SA-governed contexts, this same surface is the Portal App (PA), not a separate app. Never a system of record (see 5.8 OVApp Workflows). |
| CRM (Customer Relationship Management) |
Commercial Model |
Discipline and tooling for managing customer data, interactions, and sales pipelines; in this project, primarily implemented in Odoo. |
| ARM (Asset Relationship Management) |
Asset Model |
Discipline and tooling for managing smart assets, their lifecycle, and customer entitlements; in this project, primarily implemented in ABS. |
| Product-Unit (PU) |
Commercial Model |
Atomic quid pro quo unit ("this for that") with a defined metric and unit (e.g. piece, day, count, kWh). Recorded as line items in Odoo (see 1.1–1.2 Product-Unit Model and 2-Product-Unit Library). |
| Physical Product-Unit |
Odoo / ABS |
PU representing a tangible asset (e.g. motorbike model). Odoo tracks inventory; ABS tracks concrete asset items and lifecycle. |
| Service Product-Unit |
Odoo / ABS |
PU representing access or usage of a service (e.g. Battery Circulation, Swap Network, Swap Count, Electricity). Mapped to ABS service objects (see 2.2 Service Product-Units). |
| Contract Product-Unit |
Odoo / ABS |
PU representing a contractual entitlement (e.g. Swap Privilege, Warranty, Rental, Lease, Asset-Assignment contract). Coupled to ABS plan and entitlement logic (see 2.4 Contract Product-Units). |
| Digital Product-Unit |
Odoo / ABS (future) |
PU category reserved for future digital/media offerings delivered over the network. |
| Composite Product-Unit |
Odoo |
⚠️ Superseded (2026-09-10, Composition Rule in Reference Terminology): composition via Odoo BoM/pack order lines is retired. An Offer is a singular service product; compositional elements are defined in the associated Product Profile (ADR 0015). Historical entry retained: PU in Odoo that combines other PUs using a BoM/pack mechanism. |
| Bundle (ABS Bundle) |
ABS |
ABS-domain construct grouping interdependent BSS services into a coherent offer (e.g. swap access + battery circulation). Bundles are never mirrored as products in Odoo (see 3.3 BSS Bundles and 8.2 BSS Setup Data Types). |
| Setup Data (BSS Setup Data) |
ABS |
Configuration data in ABS defining BSS services, bundles, terms, and plans that operationalize the commercial model (see 8.2 BSS Setup Data Types). |
| BSS (Battery Swap Service) |
ABS / Business Model |
Foundational business model for battery swapping, built from ABS services and bundles (network access, swap count, energy, asset-assignment, etc.) (see 3-Product-Bundle Library). |
BSS Service (service) |
ABS |
ABS setup object defining a single service dimension (e.g. network access, swap count, electricity, asset-assignment) with metric, unit, and asset reference (see 8.2 BSS Setup Data Types). |
Terms (terms) |
ABS |
ABS setup object defining duration, period, and commercial conditions applied to a plan (e.g. 30 days, 12 months). |
Service Plan Template (plan) |
ABS / Odoo |
ABS plan + terms definition for a generic offer (no customer). Per ADR 0015, the template reference is encapsulated in the Odoo Product Profile (ov.product_profile), not stored on a Subscription/Contract PU. |
Service Plan Instance (plan_instance) |
ABS |
Per-customer instance of a plan. Per ADR 0014, initialized by ABS from the Entitlement (ov.service_entitlement), not directly from the Odoo order; ABS owns delivery states (see Reference Terminology). |
| Entitlement |
Odoo (ADR 0014) |
⚠️ Definition revised (2026-09-10): the durable contract object ov.service_entitlement conferred on the purchaser when an Offer is bought; the SO is the receipt. Typed: entitlement / privilege / warranty / assignment. (Earlier usage — ABS-side rights record created from orders — is superseded; ABS now receives the entitlement and initializes its Service-Plan instance from it. See Reference Terminology.) |
| Offer |
Odoo (ADR 0014) |
Catalog definition of something sold: a service product + Product Profile + conditions. See Reference Terminology. |
| Entitlement Handshake |
Odoo ↔ ABS Integration |
Integration pattern where Odoo order/subscription confirmation and deposit receipt trigger ABS entitlements and asset allocation while Odoo remains system of record for money (see Pattern 2 in 8.1 Odoo Integration). |
| Asset-Assignment Service |
ABS / Odoo |
ABS service that binds a specific vehicle ITEM to a contract (e.g. 12-month pairing). Linked to Contract PUs in Odoo for long-term swap privileges. |
| Vehicle-Pairing Service |
ABS / Service PU |
Access-type ABS service that pairs a specific vehicle to swap eligibility for a defined duration; must be duration-aligned with bundled swap access services (see 3.3 BSS Bundles). |
| Fleet |
ABS / Operations |
Managed collection of vehicles under ABS control (e.g. MotBat fleet). Distinct from the swap network; vehicles belong to the fleet, not the network. |
| Network (Swap Network) |
ABS / Service PU |
Collection of physical swap locations (stations) that provide swap service; modeled as a service in ABS and as outlets/sites in Odoo. |
| Battery Circulation |
ABS / Service PU |
Service and operational concept for the dynamic pool of batteries circulating across the swap network and fleet, distinct from static inventory. |
| Odoo–ABS Object Mapping |
Integration Model |
Agreed mapping between Odoo models (e.g. product.template, sale.order, res.partner) and ABS objects (services, bundles, plans, entitlements, sites) documented in the Odoo ↔ ABS correspondence table (see 8.1 Odoo Integration). |
Sales Order (sale.order) |
Odoo |
Core commercial transaction document backing retail and subscription flows. Line items are PUs; order confirmation triggers ABS entitlement creation. |
| Sales Session |
OVApp / ABS / Odoo |
Frontend retail session that wraps a draft sale.order in Odoo and, upon confirmation, results in ABS plan_instance and entitlement creation. |
| Channel Partner |
Odoo / ABS |
Organisation selling on behalf of OVES, modeled as res.partner in Odoo and referenced as channel in ABS plans/entitlements (see 5.3 Sales Channel). |
| Outlet |
Odoo / ABS |
Retail location where sales and swaps occur. Modeled as ov.outlet + res.partner site in Odoo; mirrored as site/station in ABS (see 5.3 Sales Channel). |