Portside delay feed fields
📌 TL;DR / Quick Summary <div style="background: rgba(0,0,0,0.3); border: 1px dashed rgba(255,255,255,0.2); padding: 15px; border-radius: 8px; color: rgba(255,255,255,0.7); margin-bottom: 30px;"> Field list, refresh times and known gaps of the delay feed from Portside Analytics. Fictional partner. Written straight after 📞 Portside feed walkthrough on 16 June, while I still remembered which column lies. The commercial side is in 🤝 Portside Analytics - data integration partner. </div>
🛠️ Instructions / Core Material
| Field | What it says | What to know |
|---|---|---|
vessel_ref |
Which vessel | Their reference, not ours. Needs a lookup table |
terminal |
Which terminal | Four terminals; Greywater is one |
eta_original |
First published arrival time | Rarely changes. The honest baseline |
eta_current |
Latest revised arrival time | Moves, sometimes hourly |
ata |
Actual arrival | Empty until the vessel is alongside |
delay_minutes |
Lateness | Measured against eta_current. This is the column that lies |
delay_reason |
One of nine fixed reasons | Weather, congestion, labour, and six others. No free text |
updated_at |
When the row last changed | The only way to see a gap |
Refresh: four times a day, at 00:00, 06:00, 12:00 and 18:00. Not live, whatever a customer assumes.
What is not there: anything at the gate or beyond it. Soraya Nasser said so before I asked.
⚠️ Key Warnings / Constraints
- A vessel whose estimate is revised six times and which then arrives on the sixth estimate has a
delay_minutesof zero. For any real lateness, subtracteta_originalfromatamyself. - Down days are not marked. If no row has an
updated_atinside a six-hour window, the feed was down, and the silence must not be read as punctuality. - It knows late. It does not know made late. In 📂 Carrier Scorecards discovery that is the difference between a fair score and Gideon Asante's objection.
- Nothing from this feed goes in front of a customer until Mikkel Sørensen has joined it to our own arrival events and we have looked at one bad week together.
🔗 Related Entities & Resources
- 📞 Portside feed walkthrough: the call on 16 June this note was written after
- 🤝 Portside Analytics - data integration partner: the commercial side of the same feed
- 📂 Carrier Scorecards discovery: the project that would put these delays in a score