Intelligent Dispatch Board (Resource Roster)

The central operational interface for dispatchers. Provides a visual timeline for assigning vehicles and crew to service legs, with real-time conflict detection and drag-and-drop resource management.

Visual Paradigm

The dispatch board uses a horizontal Gantt timeline as the primary view. Each row represents a resource (vehicle or crew member), and colored blocks represent assigned ServiceLegs across a configurable time range (day, week, month).

Layout

┌─────────────┬──────────────────────────────────────────────────────┐
│  Resources  │  Timeline (scrollable, zoomable)                    │
├─────────────┼──────────────────────────────────────────────────────┤
│ 🚌 Bus 01   │ ████ Tyrol Tour Leg 1 ████  ░░░░  ████ Leg 2 ████  │
│ 🚌 Bus 02   │ ████████ Bavaria Day Trip █████████                 │
│ 🚌 Bus 03   │ (available)                                        │
├─────────────┼──────────────────────────────────────────────────────┤
│ 👤 Klaus    │ ████ Tyrol Tour Leg 1 ████  ⚠️ REST ░░░░░░░░░░░░░  │
│ 👤 Sarah    │ ████████ Bavaria Day Trip █████████                 │
│ 👤 Thomas   │ 🏖️ VACATION                                        │
└─────────────┴──────────────────────────────────────────────────────┘

Resource Panel (Left)

• Grouped by type: Vehicles first, then crew members.
• Status indicators: Available (green), assigned (blue), unavailable (red — maintenance, leave, rest).
• Quick filters: By vehicle type, crew qualifications, availability window.
• Search: Filter resources by name, license plate, or qualification.

Timeline Panel (Right)

• Zoom levels: Day (hourly resolution), Week (daily), Month (weekly).
• Block colors: Coded by TourOffering or ServiceLeg.leg_type.
• Capacity badges: Each vehicle block shows booked_pax / capacity (e.g., "47/49").
• Rest periods: Rendered as hatched/striped blocks between assignments.

Drag-and-Drop Interactions

Assigning Resources

1. Drag a vehicle from the resource panel onto a ServiceLeg gap → creates a LegAssignment.
2. Drag a crew member onto a vehicle's row within a leg block → assigns the driver to that leg.
3. Drag to reschedule: Move an existing assignment block horizontally to adjust timing.

Conflict Detection on Drop

On every drag-and-drop action, the system performs real-time validation before confirming the assignment:

Conflict Type	Data Source	Visual Signal
Insufficient rest time (EG 561/2006)	Evaluated by Backoffice Observability against CrewDutyLog	🔴 Red border + modal: "Klaus needs 11h rest. Next available: 06:00"
Crew qualification mismatch	crew_qualifications	🟡 Yellow warning: "Klaus lacks Module 95 — expires 2026-03-01"
Vehicle restriction	crew_qualifications	🟡 Warning: "Klaus restricted to automatic transmission"
Capacity overflow	SeatReservation count vs Vehicle.capacity	🔴 Red badge: "52 pax on 49-seater"
Vehicle maintenance due	vehicle_inspections	🟡 Warning if upcoming. 🔴 Hard block if blocks_dispatch = true (overdue HU/SP).
Crew on leave	crew_absences	🔴 Block: "Klaus on vacation 04/10 – 04/17"
Visa/border restriction	crew_qualifications (visa entries)	🟡 Warning: "Klaus missing UK visa for this route"

Behavior: Warnings (🟡) allow override with confirmation. Hard blocks (🔴 — rest time, leave) prevent assignment entirely.

Contextual Warnings ("Dispohinweise")

Each CrewMember carries structured restrictions. When the dispatcher drags a crew member near a ServiceLeg, the board overlays contextual badges:

• Transmission restriction: "⚙️ Auto only" → blocks assignment to manual-transmission vehicles.
• License expiry: "📋 License expires in 14 days" → warning if trip falls after expiry.
• Border restrictions: "🛂 No UK visa" → blocks assignment to UK-bound legs.

The system sources these restrictions from the crew_qualifications table — see schema-backoffice.md and PRODUCT_schema-feature-gaps.md §3.

Passenger Reassignment ("Umbesetzung")

A dedicated sub-view accessible from any ServiceLeg block, for moving passengers between vehicles when capacity conflicts arise or breakdowns occur.

Interaction Flow

1. Dispatcher clicks a capacity-conflicted leg block → opens Split View.
2. Left panel: Current vehicle's passenger manifest + seat map.
3. Right panel: Target vehicle's manifest + seat map.
4. Dispatcher drags individual passengers, groups (by Booking), or entire boarding points from left to right.
5. On drop, the system:
   • Remaps SeatReservation to equivalent positions on the target vehicle's seat_map_layout.
   • Preserves all linked Booking, Payment, and PassengerProfile references.
   • Queues an automated notification to affected passengers (via Communications schema).
   • Logs the reassignment in change_events audit trail.

Bulk Actions

• "Move Boarding Point": Reassign all passengers from a specific BoardingPoint to the target vehicle.
• "Swap Vehicles": Exchange the full manifest between two vehicles (useful for breakdown scenarios).

Algorithmic Feeder/Shuttle Suggestions

When a TourOffering has multiple BoardingPoints with geographically dispersed passengers, the board can suggest feeder vehicle clustering:

1. System groups passengers by BoardingPoint.geo_coordinates proximity.
2. Calculates optimal pickup route using the routing service.
3. Suggests the minimum required vehicle size per cluster (minivan vs. coach).
4. Dispatcher approves → system creates ServiceLeg entries with leg_type: TRANSFER for feeder routes.

This is conceptual and depends on the routing service maturity. Tag as V2 feature.

Real-Time Updates

The dispatch board is a live view powered by Hasura GraphQL Subscriptions:

• New bookings: Capacity badges update in real-time as passengers book.
• Incident alerts: Flashing overlay on affected ServiceLeg blocks when a driver creates an Incident via the Driver App.
• ETA changes: Updated arrival times propagate from TelemetryPoint data.
• Duty log updates: Rest period blocks adjust when CrewDutyLog entries arrive from the Driver App (manual input). [Phase 2] Operators who enable the TACHOGRAPH integration receive real-time updates from tachograph IoT hardware — see EU-561 research §3.3.

Charter Quote Pipeline

The dispatch board includes a Kanban sidebar for tracking CharterQuote lifecycle:

┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐
│  DRAFT   │→ │   SENT   │→ │ ACCEPTED │→ │SCHEDULED │
│          │  │          │  │          │  │          │
│ Corp X   │  │ Agency Y │  │ Club Z   │  │ (on      │
│ 3-day    │  │ Airport  │  │ Weekend  │  │  board)  │
│ charter  │  │ shuttle  │  │ trip     │  │          │
└──────────┘  └──────────┘  └──────────┘  └──────────┘

• DRAFT → SENT: Generates PDF quote, sends to reseller.
• SENT → ACCEPTED: Reseller confirms → system auto-generates a TourOffering from the CharterQuote.
• ACCEPTED → SCHEDULED: Dispatcher assigns vehicle + crew on the Gantt board, making it operational.

Data Dependencies

Entity	Schema	Role
ServiceLeg	Operations	The blocks on the timeline
LegAssignment	Operations	Created/modified by drag-and-drop
Vehicle	Backoffice	Resource rows (top section)
CrewMember	Backoffice	Resource rows (bottom section)
CrewDutyLog	Operations	Rest time validation
crew_qualifications	Backoffice	Qualification conflict checks
vehicle_inspections	Backoffice	Maintenance warnings and dispatch blocking
crew_absences	Backoffice	Leave blocking
SeatReservation	Commerce	Capacity badges
Incident	Operations	Real-time alert overlays
CharterQuote	Backoffice	Kanban pipeline sidebar
BoardingPoint	Backoffice	Passenger reassignment grouping

NOTE

Subcontracted legs: When a LegAssignment has supplier_id set (and no internal vehicle/crew), the dispatch board renders it as a distinct "Outsourced" row below internal resources. Styling: dashed border, supplier name label, muted palette. Subcontracted legs cannot be drag-drop edited — they require explicit reassignment via the LegAssignment API.