The Alert You Did NOT Get Is The One That Costs You
Shipping is complex, fast-moving, and changes continuously. ETAs move. Bunker deliveries shift. Ports become congested. Vessel reports arrive late. Costs move away from estimate. Freight becomes overdue. Voyage economics change. The challenge isn’t not knowing that these things matter. Experienced operators, charterers, and commercial teams already know what they need to watch.
The challenge is knowing when something has changed enough to matter and to require action.
At 3:17 on a Tuesday afternoon, an ETA changes by three hours. It isn't dramatic. Nobody's vessel is in danger. Nobody sends an emergency email. But three hours can affect a berth window, bunker planning, laytime, the next cargo commitment, and it can definitely affect the economics of a voyage. If the change is identified early, the team has more time to assess the impact and respond. If nobody notices the change until the next morning, the available options may already be narrower.
Every voyage starts with assumptions around time, cost, consumption and revenue. As the voyage progresses, those assumptions change.
The job is not to react to every change. It is to identify when the variance has become material enough to require attention.
That's where custom alerts become powerful. They turn your team's operational knowledge into something the VMS can watch continuously, so the system keeps looking for the signals that matter while your people focus on what to do about them.
The best alerts match how your teams actually work
Different teams define an exception differently. An operator may want to know:
- “Tell me if the ETA moves by more than two hours.”
- “Tell me if bunker consumption goes above estimate.”
- “Tell me if a departure or noon report is missing.”
- “Tell me if projected ROB falls below a minimum level.”
A commercial team may care about:
- “Tell me if TCE falls below a certain threshold.”
- “Tell me if projected voyage P&L drops below budget.”
- “Tell me if the revised arrival puts the next cargo laycan at risk.”
- “Tell me if voyage costs move materially above estimate.”
Finance may want:
- “Tell me when freight becomes overdue.”
These areas of interest reflect operational and commercial experience: knowing which changes matter, which can wait, and which can have consequences if they're missed. An ETA movement is a data point. An ETA movement that puts the next cargo laycan at risk is a decision signal. Higher bunker consumption is a data point. Higher bunker consumption combined with deteriorating TCE may be a decision signal.
These distinctions matter. Not every change is an exception. And not every exception requires a decision. The useful alert is the one that surfaces a change when it meets the conditions your team has defined as commercially or operationally relevant.
Where custom alerting can become complicated
As alert requirements become more specific, configuration can become more complex. For compound alerts, that can mean understanding data structures, conditions, joins, or custom expressions.
The challenge is not that the system cannot support the alert. The challenge is that the person who knows what should trigger the alert is not always the person who knows how to configure it. This can create an extra step between identifying a useful business condition and putting it into operation. Operators, commercial teams, and IT all bring different expertise. The aim should be to make it easier to translate the operational requirement into something the system can monitor.
The technical capability may be there. But there can still be friction between the person who understands the operation and the system that is supposed to support it.
The person who spots the risk today shouldn't have to wait for the person who knows how to configure the system tomorrow.
Sedna VMS starts with the business requirement
With Sedna VMS's AI-powered Alert Generator, users describe what they want the system to watch in plain language. Instead of starting with the technical configuration, they start with the operational or commercial requirement.
For example:
- “Alert me when ETA changes by two or more hours.”
- “Notify me when a bunker order delivery date changes.”
- “Alert me when TCE falls below my threshold.”
The Alert Generator translates that request into the underlying alert script required to create the alert, including more complex, multi-condition logic. Users don't need to write the script themselves or understand the VMS data model. They describe the business conditions. Sedna VMS handles the complexity behind it. This ease of use is not limited to simple threshold alerts.
Go beyond simple alerts
Shipping decisions rarely depend on one data point in isolation. Time affects cost. Consumption affects earnings. A delay affects the next commitment. This is where compound alerts become particularly useful.
Example 1:
“Alert me when bunker consumption is more than 10% above estimate AND voyage TCE has fallen below USD 15,000 per day.”
A bunker variance may not require action on its own. A lower TCE may still be acceptable. However, TOGETHER they may indicate that the voyage is moving materially away from plan.
Example 2:
“Alert me when the vessel's ETA slips by more than six hours AND the revised arrival puts the next cargo laycan at risk.”
Here, the useful signal is not simply that the ETA changed. It is that the schedule change now has a commercial consequence. The same principle can apply to operational reporting:
Example 3:
“Alert me when the vessel has departed AND no departure report has been received within six hours AND the voyage is still marked as in port.”
The important signal is not simply that a departure report is missing. It is that the vessel has departed, six hours have passed, and the voyage is still marked as in port. TOGETHER, these conditions surface a discrepancy between what is happening and what the system says is happening, so the team can investigate before it affects downstream planning or reporting.
Simple alerts monitor individual conditions. Compound alerts allow teams to define when several conditions together should trigger attention.
The Alert Generator lets users describe that business logic in plain language, while Sedna VMS handles the complexity behind the underlying alert script. No developer or coding knowledge is required at all.
Turn experience into repeatable rules
Shipping businesses depend heavily on experience. An operator may know which ETA movements deserve attention on a particular trade. A commercial manager may know what level of TCE deterioration warrants investigation. A finance team may know when overdue freight should be escalated.
If those thresholds exist only in people's heads, the organisation depends on individuals remembering to apply them consistently. Turning them into repeatable alerts helps make that operating knowledge easier to apply across voyages, vessels, and teams.
The objective is not to replace judgement. It is to make sure the information requiring judgement reaches the right person at the right time.
Less checking, earlier action
The value of an alert is not the notification itself. It is what the team can do because the information reached them in time.
For example:
- An ETA changes and the team reviews the next commitment.
- Bunker consumption rises above estimate and the operator investigates.
- TCE falls below the expected threshold and commercial reviews the voyage economics.
- Freight becomes overdue and finance takes action.
Without alerts, teams have to keep checking whether something has changed. With custom alerts, Sedna VMS monitors the conditions the team has defined as important and surfaces the exception when those conditions are met.
AI does not make the operational or commercial decision. It makes it easier to translate the team's expertise into something the VMS can monitor continuously. The person responsible still decides what happens next.
This is the broader idea behind how we describe the Sedna Platform, namely, the Intelligent Operating System for Shipping. It's about connecting information, workflows, and people around the same voyage so teams can act without losing sight of the wider operational and commercial picture.
Focus on the changes that matter
Shipping will always involve change. The aim is not to react to every change. It is to define the conditions that matter to your operation, and to surface the exception while there is still time to respond.
Every voyage starts with assumptions. Sedna VMS helps teams monitor when actual performance reaches the thresholds that they have defined as important.
The result is not simply more alerts. The result is less manual checking, more consistent operating discipline, and earlier visibility of the exceptions that can affect the commercial outcome.
- You define what matters.
- Sedna VMS watches for it.
- Your team decides what happens next.
See how custom and compound alerts can turn your team's expertise into action: Book a Sedna VMS demo.
