Terminal & appointmentsAutomated detention and demurrage recovery for Port Optimizer
San Pedro Bay port data from Port Optimizer as dispute context
- Sync
- Daily capture for the terminals and dates on open disputes
- Authentication
- Port Optimizer Control Tower user registration held by your team
- Data exchanged
- Truck turn times · Cargo arrival outlook · Context notes
How it connects
Port Optimizer is the Port of Los Angeles digital platform developed with Wabtec. Through its Control Tower, registered users can view tools such as Signal (a daily look at cargo arriving in Los Angeles, projected weeks out), Horizon (longer-range cargo forecasts) and Turn Times, which shows truck turn times by terminal across the San Pedro Bay complex.
ATAHSKIA uses the data you can access through Port Optimizer as port-level context for San Pedro Bay disputes. Truck turn times and congestion signals for the days a container was billed help explain why a box could not be picked up or returned, which supports incentive-principle arguments under 46 CFR § 545.5. Container-specific facts still come from terminal, carrier and appointment records.
Port Optimizer does not issue invoices or set free time, so it is never the basis of a Part 541 element check on its own. Its value is corroboration: a terminal-level record of conditions on the dates in dispute, from a source neither the billing party nor the billed party controls.
Data flows
Truck turn times
Reads
Terminal-level turn time data for San Pedro Bay terminals on the dates a container was billed.
Cargo arrival outlook
Reads
Signal and forecast views that document expected volume around a vessel's arrival.
Context notes
Writes
Port-level conditions summarized into the evidence file for San Pedro Bay disputes.
Field mapping
| ATAHSKIA | Port Optimizer | Note |
|---|---|---|
| Discharge terminal | Terminal in the Turn Times view | |
| Disputed dates | Dates in the Turn Times and Signal views | |
| Port-level congestion note | Turn time and volume data for those dates | Used as context only. |
| Vessel arrival | Vessel arrival information in Signal | |
| Port of discharge | Port of Los Angeles or Port of Long Beach terminal | |
| Evidence source | Port Optimizer Control Tower |
Setup
Register for Control Tower
Someone on your team registers for Port Optimizer Control Tower access with the Port of Los Angeles.
Choose the data to capture
Decide which views (Turn Times, Signal) to capture for disputes and how often.
Link to San Pedro Bay containers
ATAHSKIA attaches port-level data to containers discharged at Los Angeles and Long Beach terminals by date and terminal.
Review in the evidence file
Port-level context appears as a separate section of the dispute packet, labelled with its source and capture date.
What it recovers
Congestion around the last free day
Turn times at the discharge terminal spiked in the days before the last free day. That record supports a relief request alongside the trucker's appointment history.
Explaining a dwell pattern
When many of your containers at one terminal ran past free time in the same week, port-level data helps show it was a terminal condition, not your planning.
Context for charge complaints
For a § 41310 charge complaint compiled for submission by the billed party, independent port data adds weight to evidence that equipment could not move.
Port Optimizer integration FAQ
Does Port Optimizer cover Long Beach terminals?
Turn Times covers terminals across the San Pedro Bay complex, which includes Long Beach. Other tools are Los Angeles focused.
Can Port Optimizer data alone win a dispute?
No. It is context. Disputes rest on the invoice elements, the container's own timeline and appointment records.
Is ATAHSKIA affiliated with the Port of Los Angeles?
No. Your team uses its own Control Tower access and ATAHSKIA organizes the data into evidence.
Related connectors
Don't let your 30-day dispute window expire.
Send your recent D&D invoices for a free audit. We report what is recoverable within 48 hours.