BTS port statistics measure throughput—not shipment delay
The federal program provides nationally consistent capacity and throughput measures for U.S. seaports, with datasets that differ in coverage and currency. Those facility-level measures do not establish what happened to a particular shipment.
Editorial figure by Supply Chain Signal. Source context: U.S. BTS Port Performance Freight Statistics.
A port measure is not a shipment trace
BTS organizes the program around nationally consistent measures of port capacity and throughput. Those statistics can describe facility activity and provide context for network planning, but they do not follow a purchase order, container, conveyance, or customer commitment from origin to destination. A port-level change cannot by itself explain whether one shipment was delayed or why.
A supply-chain system should preserve the level of observation with every metric. Port, vessel class, traffic direction, time period, unit, source dataset, refresh date, and applicable boundary should travel with the value. Joining an aggregate port measure to a shipment record can support analysis, but the interface must not relabel that context as a shipment event.
The program contains datasets with different clocks
The BTS page links weekly berthing statistics, monthly TEU series, annual reports, port profiles, and other sources whose published coverage periods are not identical. A dashboard that displays them side by side needs to show each series' last observation, release cadence, revision state, and unit. A current page does not make every linked dataset current to the same day.
Comparisons should also preserve whether a value is an average, median, count, weight, TEU total, or other measure. An increase in vessel calls, for example, is not interchangeable with an increase in full inbound containers. Normalizing unlike measures into a single congestion score introduces a model whose assumptions need their own documentation and review.
Berthing time has a bounded operational meaning
Average and median vessel berthing times describe a defined part of a port call. They do not, without additional evidence, establish anchorage wait, terminal dwell, customs release, drayage availability, rail connection, warehouse receipt, or final delivery. Each downstream claim requires the relevant operational source and a compatible time and entity key.
A useful control-tower demonstration should allow an analyst to move from an aggregate port signal to the affected lanes and then to current shipment events. It should keep inference labels visible, show when no shipment-level confirmation exists, and let the analyst dismiss a contextual signal without deleting the public observation.
Boundary definitions belong in the evidence record
BTS notes that port boundaries applied by one related official source may differ from boundaries in other program sources. That warning is a practical data-governance requirement. A port name alone is not always a stable join key, and a trend can change when geography, facility grouping, commodity coverage, or reporting population changes.
Teams should retain dataset identifiers, definitions, transformations, and query dates with derived metrics. When a boundary or series changes, the system should version the calculation and flag affected comparisons rather than silently restating history. BTS data can strengthen network context only when its statistical scope remains intact.
Enterprise buyer test
Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.
A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.
What we will watch next
Supply Chain Signal will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.