Google Sign-In Required

Use your company Google account to access the BetterFleet private content.

Back to private home

BetterFleet Support Private
Skip to content
BetterFleet Dev Wiki
System Topology
Initializing search
    bf-dev
    • Home
    • Process
    • Products
    • Reference
    • Decisions
    • Work
    • Operations
    bf-dev
    • Home
      • Process Handbook
      • BetterFleet Workflow Map
      • Product Development System
      • Product Engineering Workflow
        • Process Workflows
        • Work Intake and Weekly Planning
        • Product Engineering Workflow in Linear
        • Product Engineering Delivery
        • Agent Guidance
        • Workflow
        • Skills
        • Skill Sources
        • Process Guides
        • GitLab Feature Flags
        • In-App Docs Authoring
        • Release Notes
        • Process Templates
        • Release Plan: <title>
      • Process Publishing
      • Product overview
        • General Reference
          • Core Domain Training
          • System Topology
            • Navigational Topology
            • How To Navigate From A Question
            • Mental Model
          • Two-Axis Ontology Model
          • Ontology Primer
          • Worked Example
          • Evidence, Ownership, and Lineage
          • Energy Management
          • Standards and Protocol Map
          • Charging, Roaming, and Commercial Model
          • Charge Planning and Operations
          • Cross-Cutting Domains
          • Domain Coverage Matrix
        • BetterFleet Product Ontology
        • Core Operations Data Ontology
        • BetterFleet R&D Plan
        • Index
        • Architecture
        • Manage Product Capabilities
        • Manage Data and State
        • Manage Service Interaction Flows
        • Manage Reference
        • Manage Internal Application Diagrams
          • Manage Authorization And Permissions
          • bf-manage-core Auth and Authorization Model
          • Manage Authorization and Permissions
          • bf-manage-web Auth and Permission Model
          • Manage Service Catalog
          • bf-depot-sim
          • bf-digital-twin (Manage Role)
          • bf-fleet-health
          • bf-manage-connect
          • bf-manage-core
          • bf-manage-incidents
          • bf-manage-roaming
          • bf-manage-sitepwrmon
          • bf-manage-web
          • bf-schedule-creator (Manage Role)
          • bf-support-microsite
          • bf-telematics
        • Index
        • Architecture
        • Plan Reference
        • Plan Internal Application Diagrams
        • Plan Migration and Flags
        • Plan Simulation Request Lifecycle
          • Plan Service Catalog
          • bf-bnl-schedule-analysis-compute
          • bf-bnl-settings
          • bf-bnl-ui
          • bf-digital-twin (Plan Role)
          • bf-route-modelling
          • bf-schedule-creator (Plan Role)
      • Where to Ask Product Questions
      • Reference
        • Platform Reference
        • Platform Architecture
        • Script Runtime Model
        • Compose Profiles and Modes
        • Repository Map
        • Monolithic Git Transition FAQ
        • Monolithic Git Sizing
        • CI and Release Integration
        • Shared Reference
        • Shared Infrastructure Architecture
        • Secrets and Env Strategy
        • Vendors and Local Dependencies
        • System Reference
        • Cloud Data Dependencies
        • Ports and URLs
        • Service Matrix
          • API Docs
          • OCPI API Docs
          • OCPP API Docs
          • OSCP API Docs
          • VDV API Docs
          • Yard State API Docs
        • System Design
        • System Design: BBA Microgrid Controller Generic Packet Translation
        • System Design: Depot Simulation
        • System Design: IoT Sensor Packet
        • System Design: Microgrid Energy Orchestration
          • System Design: OCPP Profile 3 And ISO 15118 PKI
          • Architecture: BetterFleet OCPP Profile 3 and ISO 15118 PKI
          • Specification: BetterFleet OCPP Profile 3 and ISO 15118 Certificate Lifecycle Management
          • System Design: On-Prem Control
          • Challenge
          • Specification: BetterFleet On-Prem Continuity Control
          • System Design: OSCP
          • OSCP Protocol Documentation
          • Depot Sim Testing Requirements
          • System Design: OSCP Flexibility Provider Domain
      • Decisions
        • Architecture Decision Records
        • 0001 - Record architecture decisions
        • 0002 - Cognito for Authentication and Authorisation
        • 0003 - AWS Amplify for Authentication
        • 0004 - DynamoDB for default database
        • 0005 - Data Persistence
        • 0006 - Trunk-Based Development
        • 0007 - Generalised principle for automation
        • 0008 - Naming Repositories, Services, and URLs
        • 0009 - Use Timezone Aware DateTimes and UTC
        • 0010 - Use semantic release
        • 0011 - Centralized feature flag repository
        • 0012 - Use Named Exports in Storybook
        • 0013 - RESTful TITLE GraphQL
        • 0014 - Service Granularity
        • 0015 - Async/co-routine exception handling pattern
        • 0016 - Logging & log levels
        • 0017 - Instantiated Models
        • 0018 - Repository Pattern for Database Access
        • 0019 - Use of Design Tokens in TypeScript React Application
        • 0020 - API backwards compatibility and versioning
        • 0021 - Alembic Migration strategy
        • 0022 - Consistent react-hook-form usage
        • 0023 - Domain Event-Driven Architecture
        • 0024 - Domain Event Bus Tech Stack
        • 0025 - No enum types in DB table columns
        • 0026 - In-Memory Ormar Stores for Repository testing
        • 0027 - Storing Tab State in Query and Local Storage
        • 0028 - Adopt OpenTelemetry Semantic Conventions for Structured Logging
        • 0029 - Adopt RFC 9457 for HTTP Error Responses
        • 0030 - Use GitLab registry and Terraform state for ECS services
        • 0031 - Adopt DDD, Hexagonal Architecture, and CQRS for Python Domain Services
      • Work
        • Active Work
          • Work: Bba Microgrid Controller
          • Implementation Specification: BBA Microgrid Controller
          • BBA Microgrid Controller Deliverables (Stories)
          • Work: BFDev Monolithic Git
          • Challenge
          • Specification: BFDev Monolithic Git v2
          • BFDev Monolithic Git v2 Stories
          • Work: Complex Circuit Load Balancing
          • Implementation Specification: Complex Circuit Load Balancing
          • Complex Circuit Load Balancing Deliverables (Stories)
            • COR-10 and COR-11 Consolidation Review
          • Work: Dispatch Reliability and Reconciliation
          • Challenge
          • Specification: Dispatch Reliability and Reconciliation
          • Dispatch Reliability and Reconciliation (Unit User Stories)
            • Dispatch populated vehicle cards grey surface snapshot
            • Dispatch Visual Review
          • Work: Enable Scheduled Managed Charger Access
          • Challenge: Enable Scheduled Managed Charger Access
          • Specification Exploration Dossier: Enable Scheduled Managed Charger Access
          • Specification Review: Enable Scheduled Managed Charger Access
          • Specification: Enable Scheduled Managed Charger Access
          • Work: Guided Cut-Off and Release Orchestration
          • Specification: Guided Cut-Off and Release Orchestration
          • Guided Cut-Off and Release Orchestration (Unit User Stories)
          • Work: Production Deployment Validation
          • Challenge
          • Work: Scheduled Report Parity
          • Specification: Scheduled Report Parity
          • Work: Telematics
          • Telematics EventBridge Path
          • Telematics Ingress Architecture
          • Specification: Telematics Migration into bf-manage-core with 5-Minute Freshness and Health Visibility
          • Telematics Core Migration MVP (Implementation-Time BDD)
          • Work: Vector Derms
          • Implementation Specification: Vector DERMS
          • Vector DERMS Deliverables (Stories)
          • Work: Visiting Vehicle Charging Visibility
          • Specification: Visiting Vehicle Charging Visibility
          • Visiting Vehicle Charging Visibility (Unit User Stories)
          • Work: Workspace Owned Stripe Roaming
          • Specification: Workspace-Owned Stripe Credentials for Roaming Payments
        • Backlog Work
          • Work: Microgrid
          • Microgrid Backlog Stories
          • Work: Mobile Ops Companion
          • Challenge
          • Specification: Mobile Operations Companion v1
          • Mobile Operations Companion Deliverables (Stories)
          • Work: Oscp
          • OSCP Backlog Stories
        • Archived Work
          • Work: Code Canonical Orchestration
          • Challenge
          • Specification: Product Engineering Workflow
          • Product Engineering Workflow Deliverables (Unit User Stories)
          • Work: Release Notes Automation
          • Release Plan: Release Notes Automation
          • Release Notes Automation Backlog Stories
      • Operations
      • Onboarding Runbook
        • Operations Runbooks
        • Production Hotfix Release
        • Staging Hotfix Release
        • Manage Staging Release Validation
        • Terraform Plan Dry Runs
        • Operations Tooling
        • Code Indexing
        • Operations Evidence
        • Database Restoration Test Report
      • Daily Operations Runbook
      • Testing Guide
      • Troubleshooting
    • Navigational Topology
    • How To Navigate From A Question
    • Mental Model
    1. Home
    2. Products
    3. General
    4. Core Domain Training
    general reference

    System TopologyΒΆ

    This topology is the map to use before opening a service repo, protocol document, or feature spec. It shows how physical assets, external standards, core ontology concepts, product domains, and user-facing surfaces fit together.

    Read it from the outside inward:

    1. External systems and physical assets create evidence or intent.
    2. Standards describe the exchange boundary.
    3. BetterFleet projects that input onto the core ontology.
    4. Product domains own decisions over those concepts.
    5. Services, screens, reports, and support workflows expose the result.

    Navigational TopologyΒΆ

    flowchart TB
      subgraph Sources["External intent, evidence, and constraints"]
        WorkSources["Work sources<br/>schedules, dispatch, ITCS, DMS, FMS"]
        PhysicalAssets["Physical assets<br/>vehicles, chargers, EVSEs, connectors, depots, meters"]
        GridActors["Grid and energy actors<br/>DSO, DERMS, tariff, market, aggregator"]
        CommercialActors["Commercial actors<br/>CPO, eMSP, roaming hub, payment provider"]
        Users["Users<br/>operator, fleet manager, energy manager, support, driver"]
      end
    
      subgraph Standards["Standards and integration boundaries"]
        TransportStandards["VDV, GTFS, TransXChange, SIRI<br/>work and operations context"]
        ChargingStandards["OCPP, ISO 15118, IEC 61851, IEC 62196<br/>charging and charger state"]
        EnergyStandards["OSCP, OpenADR, IEC 61850, IEEE 2030.5<br/>capacity and flexibility"]
        RoamingStandards["OCPI, OICP, OCMF<br/>access, tariffs, CDRs, meter proof"]
      end
    
      subgraph Ontology["Core ontology"]
        Work["work"]
        Fleet["fleet"]
        Vehicle["vehicle"]
        Requirement["energy requirement"]
        EnergySystem["energy system"]
        Charging["charging"]
        Activity["vehicle activity<br/>projection"]
        Commercial["commercial record<br/>projection"]
      end
    
      subgraph Domains["Problem domains"]
        Ops["Operations & Dispatch"]
        Smart["Smart Charging"]
        Energy["Energy & Cost Management"]
        Roaming["Roaming & Shared Charging"]
        Incidents["Incidents & Notifications"]
        Reports["Reporting & Insights"]
        Trust["Resilience & Security"]
        UX["Accessibility & Usability"]
      end
    
      subgraph Surfaces["BetterFleet surfaces and implementation"]
        Plan["Plan<br/>simulation, schedule analysis, scenarios"]
        Manage["Manage<br/>live depot, control, visibility"]
        Connect["Connect<br/>charger integration boundary"]
        RoamingApp["Roaming services<br/>access and settlement"]
        Reporting["Reports and dashboards"]
        Support["Help docs and support workflows"]
      end
    
      WorkSources --> TransportStandards
      PhysicalAssets --> ChargingStandards
      PhysicalAssets --> EnergyStandards
      GridActors --> EnergyStandards
      CommercialActors --> RoamingStandards
      Users --> Surfaces
    
      TransportStandards --> Work
      TransportStandards --> Activity
      ChargingStandards --> Charging
      ChargingStandards --> Activity
      EnergyStandards --> EnergySystem
      RoamingStandards --> Commercial
    
      Work --> Requirement
      Fleet --> Vehicle
      Vehicle --> Activity
      Requirement --> Charging
      EnergySystem --> Charging
      Charging --> Vehicle
      Charging --> Commercial
      Charging --> Activity
    
      Work --> Ops
      Fleet --> Ops
      Vehicle --> Ops
      Requirement --> Ops
      Requirement --> Smart
      EnergySystem --> Energy
      EnergySystem --> Smart
      Charging --> Smart
      Charging --> Roaming
      Commercial --> Roaming
      Activity --> Incidents
      EnergySystem --> Incidents
      Charging --> Reports
      Commercial --> Reports
      Activity --> Reports
      Charging --> Trust
      EnergySystem --> Trust
      Users --> UX
    
      Ops --> Plan
      Ops --> Manage
      Smart --> Manage
      Smart --> Connect
      Energy --> Manage
      Energy --> Plan
      Roaming --> RoamingApp
      Incidents --> Manage
      Reports --> Reporting
      Trust --> Manage
      UX --> Support

    How To Navigate From A QuestionΒΆ

    If the question starts with... Start with this domain Then inspect Common standards
    What work must this vehicle do? Operations & Dispatch work, fleet, vehicle, vehicle activity VDV 452, VDV 462/NeTEx, GTFS, TransXChange
    Will the vehicle be ready? Operations & Dispatch energy requirement, vehicle activity, charging VDV 463, VDV 454, SIRI, OCPP
    What should charge now? Smart Charging energy requirement, energy system, charging OCPP, ISO 15118, OSCP-derived envelopes
    What can the site safely supply? Energy & Cost Management energy system, topology, limits, envelope, telemetry OSCP, OpenADR, IEC 61850, IEC 63110
    Who may charge here? Roaming & Shared Charging token, contract, location, EVSE, connector OCPI, OICP, ISO 15118
    What should be billed or settled? Roaming & Shared Charging tariff, CDR, invoice, payment, signed meter value OCPI, OICP, OCMF
    What is broken or at risk? Incidents & Notifications status, fault, stale telemetry, missed readiness OCPP, telemetry feeds, VDV real-time feeds
    What happened and can we prove it? Reporting & Insights projections, lineage, meter evidence, session history OCPP, OCMF, OCPI CDRs, schedules, telemetry
    Who or what can act? Resilience & Security identity, certificate, role, audit, safe fallback auth, OCPP security, ISO 15118 PKI, OpenADR/OSCP trust
    How does a user understand this? Accessibility & Usability task, screen, help path, support evidence help docs, UI state, permissions, audit evidence

    Mental ModelΒΆ

    Use this compact model in project discussions:

    flowchart LR
      Intent["Operational intent<br/>work, target, deadline"]
      Constraint["Supply constraint<br/>site, grid, tariff, fault"]
      Decision["Product decision<br/>domain owner chooses action"]
      Action["Control or workflow<br/>command, plan, alert, report"]
      Evidence["Evidence trail<br/>event, meter, projection, CDR"]
      Learning["Operational learning<br/>readiness, cost, carbon, reliability"]
    
      Intent --> Decision
      Constraint --> Decision
      Decision --> Action
      Action --> Evidence
      Evidence --> Learning
      Learning --> Intent

    The useful habit is to ask: what is the intent, what constraint changes it, who owns the decision, and what evidence proves the outcome?

    Made with Material for MkDocs
    BFDev Docs Assistant
    New conversation?
    Ask one focused question at a time, this helps the assistant provide accurate answers about what's been implemented in BetterFleet.