Core Domain Training¶

This training path explains the BetterFleet ontology through two coordinate axes:

Problem-domain orientation: the eight domains and their sub-domains. This is the main orientation.
Physical orientation: the physical reality being modelled: vehicles, chargers, EVSEs, connectors, sites, depots, grid connections, microgrids, meters, storage, generation, people, and time.

Operational, commercial, protocol, service, UI, and reporting material maps into those two axes.

It is written for product, engineering, support, delivery, and commercial teams who need a shared mental model before reading feature specs or service-specific docs.

Learning Outcomes¶

After this path, a reader should be able to:

explain the core BetterFleet ontology without starting from service names
use the system topology as a navigational map across assets, standards, domains, and product surfaces
use domains and sub-domains as the main driver for classifying product work
map any concept to a problem coordinate and a physical coordinate
map OCPP, OCPI, OICP, OSCP, OpenADR, ISO 15118, VDV standards, and schedule formats to product domains
explain the different purposes of VDV 452, VDV 453, VDV 454, VDV 463, and related schedule or real-time feeds
explain how physical assets overlap with several product domains without merging their meanings
explain energy-management concepts such as microgrid, operating envelope, tariffs, cost, carbon, and grid flexibility
describe how a physical charging session becomes an operational session, a report row, and a billable commercial record
explain CPO, eMSP, roaming hub, fleet operator, grid, and depot-management roles
trace raw evidence through projections, domain decisions, reports, support views, and audit trails
connect charge planning for buses, logistics, and other fleets to the generic work -> energy requirement -> charging -> delivery model

Modules¶

How To Use This Material¶

Read the modules in order for onboarding. For project work, start with the matrix and jump to the module that matches the domain under discussion.

The training pack links back to the source reference pages rather than duplicating every service detail. Use these source pages when you need the deeper design or API context:

End-To-End Coordinate Model¶

flowchart LR
  Problem["Problem-domain axis<br/>8 domains + sub-domains"]
  Physical["Physical axis<br/>vehicle, charger, EVSE, connector, site, grid, time"]
  Concept["Core concepts<br/>work, fleet, vehicle, energy requirement, energy system, charging"]
  Evidence["Evidence and standards<br/>OCPP, OCPI, OICP, OSCP, OpenADR, VDV, ISO 15118, meters, telemetry"]
  Implementation["Implementation<br/>services, APIs, UI, reports"]
  Outcome["Outcome<br/>readiness, cost, carbon, uptime, settlement"]

  Problem --> Concept
  Physical --> Concept
  Evidence --> Concept
  Concept --> Implementation
  Implementation --> Outcome

The central idea is simple: BetterFleet helps a fleet do its work by matching required energy to available energy through time, then making the physical, operational, and commercial evidence clear enough to act on.

Core Operating Flow¶

flowchart LR
  Work["Work<br/>routes, blocks, jobs, shifts"]
  Requirement["Energy requirement<br/>target SoC, kWh, deadline, margin"]
  Fleet["Fleet and vehicle<br/>asset, capability, state"]
  Energy["Energy system<br/>grid, site, microgrid, charger, limits"]
  Charging["Charging<br/>intent, control, session, outcome"]
  Commercial["Commercial record<br/>tariff, token, CDR, invoice"]
  Insight["Reporting and insight<br/>cost, carbon, performance, compliance"]

  Work --> Requirement
  Fleet --> Requirement
  Requirement --> Charging
  Energy --> Charging
  Charging --> Fleet
  Charging --> Commercial
  Charging --> Insight
  Work --> Insight
  Energy --> Insight
  Commercial --> Insight