Plan Simulation Request Lifecycle¶

Legacy Lifecycle (Flag OFF)¶

sequenceDiagram
  participant UI as bf-bnl-ui
  participant Settings as bf-bnl-settings
  participant Compute as bf-bnl-schedule-analysis-compute
  participant Route as bf-route-modelling
  participant DT as bf-digital-twin
  participant S3 as aws s3
  participant DDB as aws dynamodb

  UI->>Settings: simulate request
  Settings->>Compute: trip analysis batch
  Compute->>Route: physics calculations
  Route-->>Compute: route/energy outputs
  Compute->>S3: write intermediate artifacts when configured
  Compute-->>Settings: trip outputs
  Settings->>S3: store scenario payloads and artifacts
  Settings->>DDB: store scenario metadata
  Settings->>DT: depot emulate
  DT-->>Settings: depot events/results
  Settings-->>UI: aggregated response

Digital Twin Lifecycle (Flag ON)¶

sequenceDiagram
  participant UI as bf-bnl-ui
  participant DT as bf-digital-twin
  participant Creator as bf-schedule-creator
  participant S3 as aws s3
  participant DDB as aws dynamodb

  UI->>DT: simulation request
  DT->>Creator: parse/upload if required
  Creator->>S3: persist schedule payloads
  DT->>S3: persist run and result artifacts
  DT->>DDB: persist run state metadata
  DT-->>UI: simulation run + results

Operational Implications¶

• Legacy failures often appear as downstream fan-out errors.
• Twin failures are usually concentrated in one service path and easier to trace.