Schedule performance measured on active bookings, with carrier, terminal and AIS sources kept separate and an owner assigned to every material change.

Shipment Control combines carrier schedules, terminal events, vessel and AIS observations and shipment milestones on the shipment record. Reported, observed and calculated states are stored separately, each with its source and time. A delay, a roll or a missed cut-off becomes an assigned action for a Skypace operator, with the evidence behind it available to the shipper.
Если нужно еще сильнее показать низ видео, замени: object-position: center 80% !important; на

How Skypace runs it

Skypace reconciles carrier, terminal and AIS observations and stores each signal with its source and time. Arrival, anchorage, berth and departure states remain separate. A material schedule change is connected to the next accountable operating action.

Every milestone with its source and its time

The tracker shows each milestone as carrier-reported, terminal-observed or AIS-observed, with the time it was recorded.

Gate-in, loading, departure, transshipment, arrival and discharge appear in sequence. Each one carries the source that produced it. Arrival, anchorage, berth and departure are separate states and are never merged into one. Milestones that have not yet been observed are marked as expected, not as done. The operator confirms a milestone by hand only when the carrier and terminal disagree.

Published departures beside observed departures

The vessel schedule shows the carrier's published rotation next to the departures and arrivals actually observed from AIS and terminal data.

For each port call the published ETD and ETA sit beside the observed ATD and ATA. The difference is calculated and shown in days. The shipper sees where the voyage is running behind before the carrier updates its schedule. Bookings on that vessel are listed under the voyage, so one late port call is read against the shipments it affects.

A delay recorded, attributed and assigned

A delay is written to the shipment with its source and cause, and becomes an action for the Skypace operator responsible for the booking.

The system compares the observed vessel position with the planned schedule and raises a delay when the gap crosses the threshold set for the account. The record shows the original ETA, the revised ETA, the port where the delay occurred and the evidence used. The operator confirms the cause, notifies the receiving site and records the next step. The shipper's team sees who owns the delay and what has been done.

A rolled booking turned into a rebooking step

When the carrier rolls the booking, the alert, the alternative sailing and the rebooking are handled on the same shipment record.

The carrier's roll notice is matched to the booking and raised as an alert with the original vessel, the new vessel offered and the change in arrival date. The operator checks the alternative against the contract terms, confirms the price and submits the rebooking. The shipper reads the alert, the decision and the new sailing in one place, with the free-time clock recalculated for the new arrival.

Houston, TX
Why it matters

Inbound timing drives every plan

A manufacturer plans production against inbound timing. A retailer plans inventory and receiving windows. An EPC project plans site work against material arrival. Sea-Intelligence reported global schedule reliability of 62.6% in June 2026 and an average 5.31-day delay for late vessel arrivals. Because the market average does not identify which bookings are exposed, Skypace measures the carrier promise against the physical and milestone evidence on the shipment record.

SOURCES • Sea-Intelligence, Global Liner Performance report 179, June 2026.

What this gives your program

Schedule reliability

Measure the carrier promise against the movement observed on program bookings.

Decision confidence

Know whether a timing state is carrier-reported, observed or calculated, so operations understands the strength of the signal.

Exception ownership

Assign a material schedule change while the freight is moving, so downstream action has a named owner.
2.2 million
As of September 15, 2026, the Skypace vessel and schedule layer holds 2.2 million historical position observations.
Source • Skypace vessel history and port-call tables.

Get Started Today

Review shipment control

Give Skypace the active bookings. The tracker returns each milestone with its source, and a Skypace operator owns every material change.

Answers to Your Questions

Program, operations and transactional detail
How should schedule reliability be measured for an ocean program?
Measure the program’s own bookings against promised departure and arrival and use market data as external context.
What happens when carrier schedule data and AIS disagree?
Both sources remain attributable. Skypace preserves the difference and resolves the operating state without presenting an observational signal as a carrier milestone.
When is a port event treated as observed?
The event requires the physical or terminal evidence defined by the shipment-state methodology. A published schedule alone does not create an observed departure or arrival.
What happens after a material schedule change is detected?

The changed state stays on the shipment record and the required follow-up is assigned to the responsible person or team.

Begin shipping with Skypace

Sign up or contact us, and our logistics experts will guide you through the entire process.
Dashboard mockup