Vessel Alert System: Sensor Rules, Severity and Event Log

MANTRAZ includes a vessel alert system that turns onboard sensor readings into alerts for the people who need to act on them. Rules such as exhaust temperature or RPM above a limit, and a device that stops sending data, raise alerts with Critical, Warning or Info severity, delivered in the app and by email. It is built for fleet managers and office teams who cannot watch every vessel's data all day.

Data nobody is looking at

Monitoring only helps if someone sees the problem in time. An exhaust temperature that keeps climbing, an engine run above its limit or a device that goes quiet can sit unnoticed on a screen for hours. By the time it turns up in a report or a phone call, the moment to act on it has often passed.

How the vessel alert system works

MANTRAZ watches the readings coming from the vessel and checks them against rules. A rule can be set on an onboard sensor reading, for example:

• exhaust temperature above a limit
• RPM above a limit

A device that stops sending data raises an alert as well, so silence from a vessel is treated as something to look into rather than something to overlook.

Critical, Warning or Info

Every alert carries a severity: Critical, Warning or Info. That lets the team tell what needs attention right away from what can wait for the next review, instead of treating every notification the same way.

In the app and by email

Alerts reach your team in the MANTRAZ app and by email. People in the office see them where they already work, and those away from the dashboard still hear about them.

Event log and alert history

Every alert is recorded. The event log and alert history show when each alert triggered, when it cleared and how long it lasted. That record answers questions a single notification cannot:

• Was this a brief spike or a problem that lasted for hours?
• Has the same alert come up on this vessel before?
• How long did it take for the condition to clear?

Over time, the alert history becomes a picture of which vessels and which readings need the most attention.

Who uses it

Fleet managers use alerts to hear about problems across the fleet without watching every screen. Technical teams use the rules and the history to follow engine conditions such as exhaust temperature and RPM. Operations teams use device alerts to know when a vessel has stopped sending data. The aim is simple: problems reach the right people while there is still time to act.

See it on the map

The alerts chapter on the MANTRAZ homepage shows demo alerts triggering and clearing over a day at sea. To set up alert rules for your own vessels, contact the team for a demo.