Delphi job planning: fleet API and offline sync for field work

Planning state and map teams drifted apart

Dispatch had run reliably in Delphi on office PCs for years. Field teams used smartphone maps with positions from an external fleet portal.

Without a proper interface this meant duplicate entry, estimated arrivals, and stale status in the planning screen.

Connectivity gaps and long days outdoors

Outside stable mobile coverage, sync must not block or lose data. Evening catch-up had to merge without corrupting orders.

REST adapter with a local queue

We wrapped the fleet API in a module with retries, timeouts, and structured errors. Each planning workstation keeps a local queue: updates enqueue and upload idempotently when online.

Delphi remains the source for jobs and priorities; map data is read-only and surfaced as clear status text.

Conflict rules and monitoring

Explicit rules decide whether office or last field update wins. Lightweight monitoring shows pending jobs and failed calls—support from East Frisia can intervene precisely.

Fewer calls, more reliable ETAs

Dispatch and field share mileage and arrival times without replacing the core system. Regional rollout validated queue behaviour.

Capacity and routes can be aligned on shared data; training stayed lean because the UI did not change.