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.

#	Carrier	Schedule Support	CY cut-off	VMG cut-off	DG Cut-off	SI Cut-off	Voyage Numbers
1	AKKON LINES	YES	NO	NO	NO	NO	YES
2	ANL (part of CMA)	YES	YES	YES	YES	YES	YES
3	APL (part of CMA)	YES	YES	YES	YES	YES	YES
4	CNC	YES	YES	YES	YES	YES	YES
5	CMA	YES	YES	YES	YES	YES	YES
6	COSCO	YES	YES	YES	YES	YES	YES
7	CROWLEY	YES	NO	NO	NO	NO	YES
8	EMIRATES SHIPPING LINE	YES	NO	NO	NO	NO	YES
9	EVERGREEN	YES	YES	NO	NO	NO	YES
10	HAMBURG	YES	YES	YES	NO	YES	YES
11	HAPAG	YES	YES	YES	YES	YES	YES
12	HEUNG-A	YES	YES	YES	NO	NO	YES
13	HYUNDAI	YES	NO	NO	NO	NO	YES
14	ICL	YES	NO	NO	NO	NO	YES
15	INTERASIA	YES	NO	NO	NO	NO	YES
16	JSV	YES	NO	NO	NO	NO	NO
17	KMTC	YES	YES	YES	NO	YES	NO
18	MAERSK	YES	YES	YES	NO	YES	YES
19	NAMSUNG	YES	YES	NO	NO	YES	YES
20	MATSON	YES	NO	NO	NO	NO	YES
21	MSC	YES	YES	YES	YES	YES	YES
22	ONE	YES	YES	YES	NO	YES	YES
23	OOCL	YES	NO	NO	NO	NO	YES
24	PIL	YES	NO	NO	NO	NO	YES
25	SEALAND	YES	YES	YES	NO	YES	YES
26	SINOKOR	YES	YES	YES	NO	YES	YES
27	SITC	YES	NO	NO	NO	NO	YES
28	SINOLINES	YES	NO	NO	NO	NO	YES
30	SMLINE	YES	NO	NO	NO	NO	YES
31	TS LINE	YES	NO	NO	NO	NO	YES
32	WANHAI	YES	NO	NO	NO	NO	YES
33	YANG MING	YES*	YES	NO	NO	YES**	YES
34	ZIM	YES	YES	YES	YES	YES	YES

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.