When a shipment slips, Horizon traces the delay to the sites, lines and orders it affects and proposes a response for your team to review.
Illustrative scenario with demo data. An AIS update moves the ETA of the vessel from Gothenburg to Port of Hamburg from Tue 06:00 to Fri 06:00, 3 days late. It carries bearings for Kassel Pump Plant, line 2. Horizon checks the process model, the supply agreement's 2-day buffer and the ERP, where safety stock covers 1.5 days. It proposes pulling bearings from Lyon DC and resequencing line 2. Your team reviews it and creates a ServiceNow incident; write-back covers ServiceNow incidents only and is in beta. The inbound logistics team books the stock transfer, 2,400 bearings arrive Tue 06:10, and line 2 keeps running.
Illustrative scenario with demo data: delayed delivery.
AIS positions, port congestion, weather and news land on the Globe next to your sites and lanes.
Shipments link to their legs and to the flows on your enterprise map, so a vessel leads to the shipments on board.
An ETA past the planned arrival, a customs hold or stale tracking raises a finding with its source attached.
Agents draft a response, such as a proposal to reroute orders through another warehouse. A person approves or declines it.
Events from AIS, news, weather, fire detection and supplier filings pass a relevance check. What touches your network comes out as a proposal with links to the events behind it.
Run Research on a supplier location in Horizon. Cited findings come back as a briefing draft that a person accepts or rejects.
Five facts from the seeded demo tenant on one time axis: a Heartbeat schedule, two voyages, a customs hold and the length of a lead-to-cash case.
ETA slip on MV Atlantic Motor Star
The carrier moved the arrival 45 hr past the planned window and cites weather and port congestion. A watchpoint on the lane turns the slip into a finding, with the carrier feed as its source.
Bring a lane you ship on. We show where its signals land in Horizon and who gets the proposal.
