Amazon Cortex
Routes, TPIDs, future work buckets and same-day assignments.
Mode
Authorised browser bridge
Sync
Every 30 min
Sites
All permitted
Last test
Not tested
Connections
The connector boundary is now mapped to the route/data paths already proven in the LDH Cortex intake.
Routes, TPIDs, future work buckets and same-day assignments.
Mode
Authorised browser bridge
Sync
Every 30 min
Sites
All permitted
Last test
Not tested
Van checks, inspection completion and AI damage deltas.
Mode
API
Sync
Every 30 min
Sites
All permitted
Last test
Not tested
Road alerts, reattempts and manager notifications
LDH-derived Cortex wiring
These are source paths and response shapes already used by the LDH Cortex harvester, narrowed to operational data only.
Operations → Routes
Same-day and historical route truth: route assignment, TPID, route type, departure, progress and completion.
Cadence: Every 30 minutes + manual scan
Operations → DAs
Driver/route cross-check and itinerary detail when the route summary needs a second Amazon source.
Cadence: Daily + manual reconciliation
Scheduling → Monthly Plan
Future work buckets for roster planning, service type, wave/start time and offered/assigned route quantities.
Cadence: Daily refresh + when roster planning is opened
Work Summary Tool → choose site/week → Weekly Export
TPID-level scheduling/actual work context, nursery level and qualifications that can support roster decisions.
Cadence: Daily or weekly support sync
Performance → Delivery Associate
Authoritative Amazon driver-name ↔ Transporter ID identity source for matching People to Cortex route records.
Cadence: Daily identity refresh and on unmatched TPID
Site/service-area mapping and connector settings can be prepared here. Amazon passwords, session cookies and API tokens are not persisted in browser storage. The live bridge will keep authentication server-side or use an authorised existing browser session.