-
-
Notifications
You must be signed in to change notification settings - Fork 0
Transport Overview
The Transport Overview screen (/transport) is the live operations view of all device tasks
managed by the flow-orchestrator — every conveyor/ASRS/AMR/AutoStore movement in one place, with
all UUIDs resolved to human-readable codes.
Backed by GET /api/flow/device-tasks (flow-orchestrator, port 8085).
RBAC: DEVICE_VIEW required.
The screen opens on "Open + finished today" — the operator's working set: everything still running plus anything that completed today. Switch from the Show dropdown:
| Scope | Rows shown |
|---|---|
| Open + finished today (default) | Active tasks (REQUESTED / DISPATCHED) + anything that finished today |
| Open (active) only | Active tasks only |
| Completed | COMPLETED tasks |
| Failed | FAILED tasks |
| All recent | The full 500-task backend window |
Scope is applied client-side against a single 500-task newest-first backend window. Changing the scope does not trigger a new backend request. The equipment-family filter and equipment picker apply server-side (they do trigger a reload).
Click any row to open the detail + trace dialog for that transport.
| Field | Resolved from |
|---|---|
| HU | Payload huCode
|
| Origin |
useCatalog (location code) or listWorkplaces (GTP station code) |
| Destination | Same |
| Next hop | Same; falls back to destination for ASRS/AMR/AutoStore direct-delivery tasks |
| Equipment | Equipment catalog label |
| Actor |
actor field on the task |
When a task carries a correlation id — set by the flow-orchestrator to link multiple device
tasks in one logical transport (e.g. an ASRS RETRIEVE followed by a CONVEY to a GTP station) — the
dialog fetches the full ordered trace via GET /api/flow/device-tasks?correlationId= and renders
each step as a numbered list with status badge, family + command, origin → destination, and
timestamp. The task that was clicked is highlighted.
Tasks with no correlation id stand alone and show only themselves in the trace section.
The raw payload and result JSON (if non-empty) are pretty-printed at the bottom of the dialog — useful for diagnosing FAILED tasks.
Upcoming — per-HU transport trace (ADR 0007 R4, Phase 3c-1): a new append-only
hu_transport_tracetable in flow-orchestrator will record a timestamped row for every function point an HU passes — retrieved from slot, inducted, conveyor divert / merge / recirculate, arrived, queued, presented, stored back — each with the decision made. The click-to-trace dialog will switch from the current coarse device-task list (one row per dispatched task) to this full material-flow timeline, queryable by HU. The emulator will report conveyor decision points back to flow via the §3b callback channel.
Close with ✕, the Close button, or Escape.
| Column | Notes |
|---|---|
| Status | REQUESTED → DISPATCHED → COMPLETED / FAILED |
| Family | Equipment type: CONVEYOR · ASRS · AMR · AUTOSTORE
|
| Command | e.g. CONVEY · STORE · RETRIEVE · TRANSPORT
|
| HU | Resolved handling-unit code |
| Origin / Destination | Resolved location code or GTP station code |
| Next hop | Resolved; falls back to destination for direct deliveries |
| Equipment | Resolved label from the equipment catalog |
| Correlation | Short id; hover for the full id and explanation |
| Created | Timestamp |
The search box matches id, status, family, command, HU code, resolved origin/destination, equipment label, and correlation id simultaneously. Auto-refresh runs every 4 s; toggle with the Auto-refresh switch in the header.
openWCS — open-source Warehouse Control System · summarized from build.md & docs/AS-BUILT.md (the repo docs are authoritative).
Design
Flows
- Areas
- Inbound and Inventory
- Slotting and Replenishment
- Goods-to-Person Stations
- Outbound Flow
- Equipment Integration
- Transport Overview
- Process Designer
- Mobile Process Designer
- Hardware Visualisation
- Host Integration
Reporting & Dashboards
Operations