Container History

Market Analysis

Client Analysis

---

What it does

Captures container movements as an explicit time-ordered history (events).
Current status/location is derived from the latest movement event.

Why it matters operationally

• Preserves history (avoids “silent overwrites”)
• Supports traceability and review
• Makes sharing more reliable across people and locations

Data from spreadsheets to DSLCore database

sequenceDiagram
  autonumber
  participant Ops as Operator
  participant Ingest as Ingestion
  participant Hist as Container History
  participant View as Derived View

  Ops->>Ingest: Updated spreadsheet
  Ingest->>Hist: Append movement event
  Hist->>View: Derive current status
  View-->>Ops: Current view + full history