Transport Operations¶
Transport operations is the core MYConnect workflow. It covers the work from order intake to dispatch, driver assignment, status tracking, exceptions, POD review, and billing preparation.
What Operators Get¶
- Job creation and import.
- Customer, pickup, dropoff, cargo, pricing, and instruction fields.
- Driver, vehicle, and trailer assignment.
- Job detail and timeline.
- Exception capture.
- Admin-side POD handoff and review.
- Completed-job billing export.
Why It Matters¶
Many SME hauliers already know what must happen. The problem is that each step sits in a different place: customer order in one spreadsheet, driver assignment in WhatsApp, vehicle movement in a GPS portal, POD in a phone gallery, and billing export in another file.
MYConnect connects those steps so operations can see what happened and finance can trust the export.
Current Build Proof¶
The current MYConnect build has local route evidence for:
| Route | Capability |
|---|---|
/jobs | List, create, and import tenant jobs through guarded transport operations APIs. |
/jobs/{jobId} | Show persisted job detail, timeline, telemetry evidence, POD, and billing records. |
/dispatch | Assign driver, vehicle, trailer, subcontractor capacity, status, and admin POD handoff. |
/exceptions | Create and list persisted job exceptions with owner, severity, and status. |
/billing-export | Generate persisted billing export batches and CSV artifacts from billing-ready jobs. |
Current proof is local route/API evidence. Full driver mobile device smoke, accounting integration, production POD evidence retention, finance approval, and production/staging rollout remain later gates.