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
Internal Application Diagrams
Initializing search
    bf-dev
    • Home
    • Product Capabilities
    • Process
    • Current Work
    • System Design
    • Software Reference
    • Operations
    bf-dev
    • Home
      • Overview
      • Manage
      • Overview
      • Product Engineering Workflow
      • Product Engineering Delivery
      • Product Engineering Workflow in Linear
        • GitLab Feature Flags
        • In-App Docs Authoring
        • Release Notes
      • Templates
      • Publishing
      • Workflow Companions
      • Overview
      • Active Artifacts
      • Backlog Artifacts
      • Archived Artifacts
      • Overview
      • Microgrid
      • OSCP
        • Challenge
        • Specification
        • Spec
        • Architecture
        • Overview
        • Script Runtime Model
        • Compose Profiles and Modes
        • Repo Topology
        • CI and Release Integration
        • Overview
        • Internal Application Diagrams
          • Overview
          • Web Model
          • Core Model
        • Service Interaction Flows
        • Data and State
          • Index
          • bf-manage-web
          • bf-manage-core
          • bf-manage-connect
          • bf-manage-sitepwrmon
          • bf-manage-incidents
          • bf-telematics
          • bf-depot-sim
          • bf-manage-roaming
          • bf-support-microsite
          • bf-digital-twin
          • bf-schedule-creator
        • Overview
        • Internal Application Diagrams
          • Legacy Simulation Lifecycle
          • Digital Twin Simulation Lifecycle
          • Settings Service Internal Shape
          • Compute Service Internal Shape
          • Digital Twin Internal Shape
          • Schedule Creator Internal Shape
        • Migration and Flags
        • Simulation Request Lifecycle
          • Index
          • bf-bnl-ui
          • bf-bnl-settings
          • bf-bnl-schedule-analysis-compute
          • bf-route-modelling
          • bf-schedule-creator
          • bf-digital-twin
        • Overview
        • Secrets and Env Strategy
        • Vendors and Local Dependencies
        • ADRs
        • Service Matrix
        • Cloud Dependencies
        • Ports and URLs
      • Onboarding
      • Daily Operations Runbook
        • Overview
        • Staging Hotfix Release
        • Production Hotfix Release
        • Terraform Plan Dry Runs
      • Troubleshooting
      • Testing Guide
    • Legacy Simulation Lifecycle
    • Digital Twin Simulation Lifecycle
    • Settings Service Internal Shape
    • Compute Service Internal Shape
    • Digital Twin Internal Shape
    • Schedule Creator Internal Shape

    Plan Internal Application Diagrams¶

    Legacy Simulation Lifecycle¶

    sequenceDiagram
      participant UI as bnl ui
      participant Settings as bnl settings
      participant Compute as schedule analysis compute
      participant Route as route modelling
      participant Twin as digital twin depot
    
      UI->>Settings: submit simulation
      Settings->>Compute: compute trip and charging data
      Compute->>Route: route and physics calculations
      Route-->>Compute: physics outputs
      Compute-->>Settings: computed scenario data
      Settings->>Twin: run depot emulation
      Twin-->>Settings: depot outputs
      Settings-->>UI: merged response

    Digital Twin Simulation Lifecycle¶

    sequenceDiagram
      participant UI as bnl ui
      participant Twin as digital twin
      participant Creator as schedule creator
      participant S3 as aws s3
      participant DDB as aws dynamodb
      participant Core as manage core
    
      UI->>Twin: submit simulation
      Twin->>Creator: parse or load schedule data when required
      Twin->>Core: fetch shared platform context when required
      Twin->>Twin: run simulation phases
      Twin->>S3: persist run artifacts and outputs
      Twin->>DDB: persist run state and metadata
      Twin-->>UI: run response

    Settings Service Internal Shape¶

    flowchart TD
      Api[settings routers] --> Resources[resource modules]
      Api --> Scenarios[schedule analysis scenario modules]
      Api --> SettingsV2[settings v2 domains]
      Scenarios --> Downstream[compute and digital twin clients]
      Resources --> Storage[data stores]
      Storage --> S3[(aws s3)]
      Storage --> DDB[(aws dynamodb)]

    Compute Service Internal Shape¶

    flowchart TD
      Ingress[fastapi app] --> Schedule[schedule analysis]
      Ingress --> Charging[charging analysis]
      Ingress --> Depot[depot analysis]
      Ingress --> Soh[soh analysis]
      Schedule --> Helpers[compute helpers and stats]
      Charging --> Helpers
      Depot --> Helpers
      Soh --> Helpers
      Helpers --> S3[(aws s3)]

    Digital Twin Internal Shape¶

    flowchart TD
      App[fastapi app] --> PlanApp[plan application layer]
      PlanApp --> PlanDomain[plan domain layer]
      PlanApp --> PlanAdapters[plan adapters]
      App --> ServiceModules[service modules]
      App --> OutputModules[output service modules]
      OutputModules --> MlModels[ml model loaders]
      App --> Core[manage core integration]
      App --> Connect[manage connect integration]
      App --> SitePwr[site power monitor integration]
      App --> S3[(aws s3 persistence)]
      App --> DDB[(aws dynamodb persistence)]

    Schedule Creator Internal Shape¶

    flowchart LR
      Api[api routes] --> Formatter[input formatter]
      Formatter --> Parser[schedule parser]
      Parser --> Plugins[enrichment plugins]
      Plugins --> Gtfs[gtfs and transxchange sources]
      Parser --> Outputs[schedule and route outputs]
      Outputs --> S3[(aws s3)]
    Made with Material for MkDocs