Operational governance
Liner & tramp scheduling runs under Asyad controls with documented handoffs, risk reviews, and audit-ready reporting.
Liner & tramp scheduling
Frequency planning with cut-offs aligned to port clusters.
Scope
Frequency planning with cut-offs aligned to port clusters.
Scheduled strings and inducement calls
Operating features
Corridor integration
Synchronized with shipping systems across Oman and partner hubs for milestone visibility.
Commercial clarity
Contract pattern recurring with regional scope and named account coverage.
Delivery steps
- 1
Scope intake
Confirm volumes, lanes, compliance triggers, and service windows with a coordinator.
- 2
Mobilization
Allocate terminal, yard, fleet, or network capacity against the agreed operating plan.
- 3
Execution
Scheduled strings and inducement calls with live status, exception handling, and customer-visible milestones.
- 4
Settlement
Invoicing, KPI review, and improvement actions logged for the next cycle.
Commercial specifications
| Dimension | Contract | Geography | Lead time |
|---|---|---|---|
| Commercial pattern | recurring | regional | 5–12 business days |
| Primary scope | Scheduled strings and inducement calls | regional | Desk-led |
| Data exchange | API / EDI optional | regional | Integration window |
| Escalation | 24/7 bridge | Oman GCC | Duty roster |