Executive Intelligence
The questions that get asked once a year, and are normally answered from memory.
Sidonia answers them from the days you actually had, in the words they were actually said in.
/01
When delays occurred, what was the context?
Every delay keeps the exchange that produced it: who called, what was said, and what the boat and the berth were doing in that minute. The context is attached to the delay, not filed somewhere away from it.
/02
Do some vessels take longer to move than others?
You will see which ones, and by how much. Know it, and make the best decision on when those calls are taken. Then it stops being an executive hunch and becomes operational for the dispatcher.
/03
Were some delays agreed with the carrier?
Agreed delays are marked as agreed at the moment they are agreed, by the person who agreed to them. Months later, the difference between a delay you caused and one the carrier agreed to is the conversation that produced it.
/04
Did a client push back multiple times and then take an overbooked slot?
The pushbacks are in the record with their dates and their words. You know the details specifically, and you can show them the diligence instead of describing it.
Go into the annual deal meeting knowing exactly why delays occurred, and exactly what you weren’t at fault for.
Bottom up, with no reporting layer in between.
The record is made by the people doing the work, in the course of doing it. Nothing is retyped for management, and nothing is reconstructed at the end of the month, so what management reads is what happened.
Measured
- Arrival error, underway
- ~4 min median
- Arrival error, cold departure
- ~12 min median
- Job duration
- within ~7 min
Tug side. Measured against 2,100+ real harbor transits replayed from public AIS, and 248 out-of-sample jobs.
Your best operators become visible, because their days are visible.
Performance is read off the days themselves rather than off what anyone remembers about them. Incentives can sit on something real instead of on a recollection of a good quarter.
Prepare for autonomy
Monitoring is passive. Command is active.
This is what the record compounds into. Every day it keeps is a day the operation can be read back from, and an operation you can read is one you can run from further away.
Watching a screen and waiting to intervene is not the same job as understanding an operation well enough to decide before the problem forms: why the boat is where it is, what the next two hours of port choreography require, where the weather window closes, which berth conflicts are coming, and what the contingencies are.
Whatever ends up steering the boat, the operation still has to be commanded. The layer built here is what makes remote command possible, rather than remote monitoring necessary.
Why did an experienced operator hold a vessel back when its route appeared clear?
Sidonia captures the context behind that decision, turning human judgment into data for autonomous vessels, empowering them to make the same efficient choices.
Every decision today is intelligence for the autonomous fleet of tomorrow. Every decision today becomes measurable for executives tomorrow.
Read your own year back.
Bring a month of dispatch and the questions you could not answer last April. We'll show you where the answers would have been.