1. Home
  2. Protected: OceanIO
  3. Protected: Use cases
  4. Using Vessel Schedules

Using Vessel Schedules

Using Vessel Schedules

The OceanIO platform offers schedules to let you choose the Carrier with the most suited schedule. Schedules can be used utilized in various ways. For instance:

  • To determine which schedule to select in a planning situation

  • To check a given vessels schedule

  • To receive updates when a Schedule changes (ETA/ETD/port Calls added/removed)

 

Supported Carriers for Vessel Schedules

The OceanIO platform supports the following carriers for Vessel Schedules.

# CarrierSchedule SupportCY cut-offVMG cut-offDG Cut-offSI Cut-offVoyage Numbers
1AKKON LINESYESNONONONOYES
2ANL (part of CMA)YESYESYESYESYESYES
3APL (part of CMA)YESYESYESYESYESYES
4CNCYESYESYESYESYESYES
5CMAYESYESYESYESYESYES
6COSCOYESYESYESYESYESYES
7CROWLEYYESNONONONOYES
8EMIRATES SHIPPING LINEYESNONONONOYES
9EVERGREENYESYESNONONOYES
10HAMBURGYESYESYESNOYESYES
11HAPAGYESYESYESYESYESYES
12HEUNG-AYESYESYESNONOYES
13HYUNDAIYESNONONONOYES
14ICLYESNONONONOYES
15INTERASIAYESNONONONOYES
16JSVYESNONONONONO
17KMTCYESYESYESNOYESNO
18MAERSKYESYESYESNOYESYES
19NAMSUNGYESYESNONOYESYES
20MATSONYESNONONONOYES
21MSCYESYESYESYESYESYES
22ONEYESYESYESNOYESYES
23OOCLYESNONONONOYES
24PILYESNONONONOYES
25SEALANDYESYESYESNOYESYES
26SINOKORYESYESYESNOYESYES
27SITCYESNONONONOYES
28SINOLINESYESNONONONOYES
30SMLINEYESNONONONOYES
31TS LINEYESNONONONOYES
32WANHAIYESNONONONOYES
33YANG MINGYES*YESNONOYES**YES
34ZIMYESYESYESYESYESYES
Schedule data availability per Carrier
* Yang Ming: Supported for the following ports: Vancouver (deltaport), Prince Rupert, Jarkata, Surbaya, Southampton, Felixstowe, London Port.
** Yang Ming: Supported for the following ports: Jarkata, Surbaya

Check schedules for a port pair

To check which schedules are available between a port of loading and port of destination use the GET /schedules endpoint. This endpoint returns all possible schedules between 2 ports.

Three different options to return the schedules are supported:

  • CURRENT: When using this option only active schedules will be displayed, which means that the given origin event has to be in the past i.e “ACT”. And the given destination must be in the future, i.e “EST”

  • NEXT: If this option is used both the given origin and destination events has to be in the future, i.e “EST”. So only schedules which is going to happen will be returned here.

  • TIMEINTERVAL: for timeinterval a begin_datetime and end_datetime is needed and then only schedules within that timeframe is shown.

Besides these options, a filter with a carrier scac code can be used. This means that only schedules for that specific carrier will be shown, given that the carrier scac code is supported by GH.

Check schedules for a port pair with transshipments *BETA endpoint

To check which schedules are available between a port pair with transshipment use the GET /point-to-point-schedules endpoint. This endpoint returns all possible schedules between 2 ports including possible transshipments.

Check schedule for a specific Vessel

To check a schedule for a specific vessel use the GET /schedules/{vessel_IMO_Number} This endpoint returns the schedules for the specific vessel requested. Here it is possible to filter for a specific carrier scac code if it is supported by GH.

FAQ:

  1. Q: For which time frame am I getting schedules?
    A: For a minimum of 4 weeks and a maximum of 8 weeks ahead
  2. Q: How many ports within the schedule service are you supporting?
    A: The schedule service supports all ports for all supported Carriers
  3. Q: How many Carriers am I getting schedules for?
    A: Vessel schedules are currently provided for 32 carriers incl. their subsidiary companies. These are all listed here.

Schedules with transshipment:

  1. Q: How is the output sorted?
    A: Firstly the Carriers are sorted alphabetically and for each carrier we are sorting the total transit time between each port. Shortest transit time comes first.
  2. Q: How is the output limited?
    A: When a Carrier is defined in the request, the service limits the output to contain maximum 10 schedules and without Carrier limitation the service limits the output to max. 3 schedules per carrier.