The deadline stays on the screen after it has passed.

Ocean and air AMS records, the 24-hour deadline the shipment is counted against, and the name of whoever filed it. Every time on the screen says which clock it is on.

What it does

Three facts per house: the deadline, the filing, the filer.

Ocean and air both hold an AMS record. The deadline sits on it, the filing number sits on it when there is one, and a name sits beside that — because “the agent said they did it” is not a record.

Fig. 1 — Twenty-four hours before the cargo goes aboard.19 CFR §4.7(b) · lib/cutoff.ts

There is no such thing as a late AMS filing, so the line drawn here is not a deadline for the paperwork — it is the last moment the cargo can be on that vessel.

AMS — consolidation CONS-2609-0031 1 past deadline

Loading — Busan30 Aug 18:00 KST

24-hour deadline29 Aug 18:00 KST

HBL LAX-2609-0148 — filed by R. Okonjo29 Aug 09:14 KST

HBL LAX-2609-0152 — no filing number4 days past

The vessel sailed on 30 August. This line was due four days ago and it is still on the screen, because that is when it matters most.

Air AMS — MAWB 180-44921035Filed

Two clocks, both named

KST at the loading port, PT in the office. A time on this screen never appears without the clock it belongs to.

24 h

Before the cargo is loaded

Counted from what is on the record. If the loading date on the record is wrong, the deadline is wrong, and the screen shows the date it used.

Who filed it is part of the record

On a co-loaded consolidation the filing is often somebody else’s job, and the only thing worse than an unfiled AMS is two people each certain the other one filed it. So the name goes next to the filing, and an empty name reads as an empty name rather than as done.

The morning queue carries it

Customs deadlines are among the forty reads the queue makes before anyone opens a shipment, sorted by what costs the most to leave alone.

The rule this screen is built on

A warning that stops at today vanishes the moment it comes true.

This is one of the twenty checks that can stop a release at CBMGO, and it exists because the mistake is so easy to make and so hard to see.

check_deadline_floor

A deadline warning written the obvious way — showing what is due between now and Friday — quietly produces a screen where a filing that is four days late is invisible. It fell out of the bottom of the window on the day it went wrong. The queue looks calm, and the calm is the symptom.

So the check fails any build that clamps the low end of a deadline warning to today. Overdue is not a past state to be tidied away; it is the state that is costing money now.

check_clock

A second check fails any build that stamps a time without naming the clock it came from. A 24-hour deadline at a foreign loading port and a screen being read in Los Angeles are two different days, and “18:00” on its own is not information.

That check exists because of a real defect: a four o’clock delivery in Los Angeles appeared on a customer’s screen as 23:00 the next day. Nothing had crashed. The screen was confident and wrong.

What this does not do

Four things it will not do.

It does not transmit the AMS record

CBMGO builds it, holds the deadline against it and records who filed. The filing itself is done by the broker, the co-loader or whoever holds that role on the shipment.

It does not know the vessel sailed unless the record says so

The deadline is arithmetic on the loading date held on the record. A wrong sailing date makes a wrong deadline, so the screen shows the date it counted from rather than only the answer.

It does not file on somebody’s behalf and tell them later

There is no automatic filing anywhere in CBMGO. An unfiled AMS stays unfiled and stays visible until a person does something about it.

It does not hide the overdue line

There is no setting to clear old warnings off the queue. A filing that is four days late is worse than one that is due tomorrow, and it sorts accordingly.

Get a demo

A co-loaded consolidation makes a useful demonstration.

Particularly the kind where three parties each assume one of the others filed. The AMS records are built and the deadline put on them, and the next morning’s queue shows the result.

Get a demo Back to ABI