One record per voyage
Charter terms, nominations, port calls and timestamps from the statement of facts are joined into a single voyage record, so laytime can be counted automatically and the same way every time.
Supply chain & logistics analytics
Demurrage optimization analytics
Demurrage is charged once a vessel overstays the laytime in its charter party, and it is usually discovered after the fact, on an invoice. We bring together port congestion, vessel speeds and the real loading and discharge rates at each berth, so you can see which voyages are heading for a claim and change the plan while there is still time.
Typical first version
6 – 10 weeks
Stated as a range. The two-week assessment narrows it.
The problem
Where it hurts today
- Laytime is calculated by hand from statements of facts, weeks after the vessel has sailed.
- Nobody can say in advance which of this month’s cargoes is likely to run over.
- Claims are paid or disputed one by one, with no picture of which ports, berths or terminals cause them.
Data we bring together
- Charter party terms and laytime clauses
- Notices of readiness and statements of facts
- Port line-ups and berth queues
- AIS vessel positions and speeds
- Historical loading and discharge rates by berth
- Demurrage invoices and claim outcomes
How Azico builds it
Four stages, each one usable on its own
Berth-by-berth history
Real pumping and cargo-handling rates are measured for each terminal and berth, alongside how long vessels actually wait at anchor in each season.
Exposure forecast
For every open voyage, a model estimates the likely time at port and the chance of exceeding laytime, with a stated range rather than a single number.
Alerts and what-ifs
When a voyage’s exposure rises, the operator is told. They can test options such as adjusting speed to arrive when the berth is free, or changing the discharge sequence.
What your team sees
- +Open voyages ranked by expected demurrage exposure
- +Laytime clock per vessel, calculated from the statement of facts
- +Port and berth league tables of waiting time and handling rates
- +Claims register: invoiced, disputed, recovered
Questions it answers
- “Which cargo this month is most likely to go on demurrage?”
- “Is it cheaper to slow down and arrive later than to wait at anchor?”
- “Which terminals consistently pump below the warranted rate?”
What we need from you
- Charter parties or a summary of their laytime terms
- Statements of facts for recent voyages
- Access to your AIS or port-agent data, or a budget for a provider
- One operator who can review the first forecasts
Supply chain & logistics analytics
Other solutions in this group
Insights
Related insights
Perspective · 5 min read
Prevent demurrage before it becomes a logistics problem
Most of the data that decides a demurrage bill exists before the vessel arrives. Combined, it turns surprise claims into forecastable exposure.
Read now →Explainer · 6 min read
What is a data pipeline?
How a data pipeline carries figures from plant, terminal and trading systems into one reliable store, and the signs that your business needs one.
Read now →Explainer · 5 min read
Do you need a data warehouse?
Why a single governed warehouse matters once production, trading and finance data live in separate systems, and when to build one.
Read now →Talk to us about demurrage optimization analytics.
Azico Analytics is a Bangalore-based team of experienced data professionals. Share how your data is managed today, how your reports are produced and the challenges you face. We will assess your requirements objectively and set out where we can add value, with a practical approach tailored to your business.