◈Dispatch

During a multi-day event, dispatchers coordinating dozens of chauffeured cars had no single picture of where each car was, who was driving it, whether it was free, and when it would arrive. Everything ran on phone calls.

• Fleet map with GPS tracking units and phone positions; every car stays in the roster even when its GPS is missing.
• Driver view: pick a destination, change it, mark yourself available, waiting, charging or on a break, end the shift.
• Dispatcher view: states with timers, destinations, saved routes and ETA with delay against the first estimate.
• TV kiosk for the dispatch room: eight-digit pairing, read-only access that expires and can be revoked instantly; Full HD, 4K and mobile layouts.

1. 01 FrontendStandalone Next.js app; map renderer shared with ReadyOps as a package
2. 02 BackendReadyOps NestJS API is the only backend, login service and GPS receiver
3. 03 RealtimeAuthenticated SSE invalidations, five-second checkpoints, polling as fallback
4. 04 ConsistencyRow locks, expected versions and partial unique indexes: a car or driver can never be in two active trips
5. 05 MapsMapbox GL, routing and collision-free labels at high marker density

Built quickly before a real deadline, so the risky parts were specified first: the state model, who may command which car, and what must never happen concurrently. Those rules live in PostgreSQL constraints and an integration test suite, so agent-written UI code cannot break them.

• ✓Used in production at NATO Days 2026 with 25 cars and drivers; dispatchers tracked the whole fleet live.
• ✓Running on the server alongside ReadyOps (checked Oct 2026).
• ✓Dedicated integration test suite for dispatch commands and concurrency rules.

• !The client is not named. Screenshots come from an isolated copy with a fictional demo event.