02 / Intermodal
For Trieste-origin cargo, port, rail and road transfers were merged into one multimodal plan.
Operation need
For cargo from northern Italy to Istanbul, the sea and road legs sat in separate bookings. When port discharge and rail booking were not synchronised, the arrival date slipped at every transfer.
When the ro-ro lane, terminal transfer and inland haulage were watched by different teams, the client could not see one arrival date.
Planning
The Trieste departure, rail slot and Istanbul last-mile booking were placed on one operations calendar. Each transfer point was defined as a visible step on the route.
Bookings were synchronised; when one step slipped, the next mode was read again.
Trieste–Istanbul multimodal plan created.
Transport model
Sea + rail + road
Ro-ro lane departed Trieste; rail transfer at the intermodal terminal; road last mile in Istanbul. Three modes tracked under one route identity.
When the mode changed, the language did not. Visibility lived with whoever decided at the transfer.
Coordination
Carrier, terminal operator and road haulier moved in one operational language. Port cut-off, rail slot and last mile updated on the same plan.
When a break became visible — delayed discharge or slot change — the next mode was rebuilt.
Operation process
Voyage booking locks.
Terminal transfer watched.
Slot and wagon booking synchronised.
Handover at intermodal terminal.
Road delivery starts on the same plan.
Delivery / Outcome
Port, rail and road transfers closed under one route identity. The client was informed in one operational language even at transfer.
Port, rail and last-mile delivery were tracked as one route, with bookings kept in sync.
Tangible outputs
Operation gallery
Related service
Other operations
Quote
Share your route and transfer points. We build the multimodal plan together.
