What is an Alarm and Monitoring System, and why does it matter?

Why a vessel needs an Alarm and Monitoring System (AMS)

A vessel’s machinery runs around the clock, often in spaces where nobody is present. A typical engine room has hundreds or thousands of measuring points, for example temperatures, pressures, levels, flows and running signals from engines, generators, pumps and tanks.

No crew can follow all of this manually. And many faults start small: a temperature that creeps upwards, a pressure that slowly drops, a pump that takes longer than usual to start. The Alarm and Monitoring System (AMS) keeps an eye on all of it, all the time, and tells the crew when something needs attention, ideally long before it turns into a breakdown.

How an Alarm and Monitoring System (AMS) works

Collecting signals: An IO system collects signals from sensors, switches and other equipment, either as hardwired analogue and digital signals or over fieldbuses such as Modbus, NMEA, CAN and PROFIBUS.

Detecting abnormal conditions: Each signal can have its own alarm limits, for example a high temperature or a low pressure. Time delays can be added, so that a short spike does not cause a false alarm.

Alerting the crew: Alarms are shown on operator stations in the engine control room and often on the bridge, together with sound and light. Alarms have priorities, so the most critical ones stand out.

Keeping a record: Alarms and signal values are logged, so the crew can look at trends and alarm history to understand how a situation developed.

What an AMS does not do is act. It does not start pumps, open valves or change settings on board. When an alarm comes, the crew acts, either on the equipment’s local controls or through a separate control system. Adding control and automation to the AMS is what turns it into an Integrated Automation System (IAS).

• 
• 
• 
• 

View mode:

Dusk

Day

• 
• 
• 
• 

View mode:

Dusk

Day

• 
• 
• 
• 

View mode:

Dusk

Day

Unattended engine rooms and the E0 class notation

Many vessels operate with the engine room unattended for periods of time, for example at night. DNV’s class notation for this is E0, and other class societies use notations such as UMS or AUT. The principle is the same: the vessel must be as safe with the machinery spaces unattended as with them manned, typically for up to 24 hours at a time.

This is where the Extension Alarm System (EAS) comes in. It extends the alarm system from the engine control room to the rest of the vessel.

Watch responsibility: Before the engine room is left unattended, an engineer on duty is selected and the watch responsibility is transferred to the bridge. The system always shows who is on duty.

Alarms reach the right person: Alarms are routed to watch call panels in the duty engineer’s cabin, on the bridge and in public areas, for example the mess, so the engineer on duty is reached wherever he or she is on board.

Escalation: If an alarm is not attended to within a limited time, typically a few minutes, the system alerts further, so an alarm is never left unanswered.

Deadman alarm: When an engineer works alone in the machinery spaces, he or she must confirm at regular intervals. If no confirmation comes, an alarm is raised on the bridge.

Regular testing: Vessels with E0 follow an approved test plan, where the sensors and alarms that are essential for unattended operation are tested regularly and checked by class at the annual survey.

In the X‑CONNECT® AMS, the EAS is an integrated part of the alarm system. The engineers’ alarm, watch transfer and deadman system are handled in one system, and the watch call panels show current alarms in the same clear format as the operator stations.

What makes a good alarm system

More alarms do not mean more safety. A system that alarms constantly teaches the crew to acknowledge without looking. A good AMS helps the crew focus on what matters.

Clear priorities: Alarms are grouped by priority and colour, so the crew sees at a glance what needs action first.

Less noise: One fault can trigger a chain of follow-up alarms. When a generator is stopped, for example, its low-pressure alarms are no longer relevant. Alarm suppression keeps these out of the way, so the real cause is not buried.

From alarm to cause: The crew can move directly from an alarm to the signal, the component and the system mimic (the live graphical view of the system) it belongs to.

History that tells a story: Alarm history shown as a timeline, with filtering and an adjustable time scale, makes it easier to hand over a watch or understand what happened after an incident.

A system that watches itself: A monitoring system you cannot trust is worse than none. The AMS also monitors its own controllers, software, network and IO, and raises an alarm if any of them fails.

None of this happens by accident. It takes an alarm system that is carefully designed as a whole, with consistent logic, priorities and presentation, rather than one that is put together piece by piece for each project.

How the X‑CONNECT® AMS is built for the ship owner

A vessel operates for 20 to 30 years, and for a ship owner much of the cost of automation comes after delivery. The X‑CONNECT® AMS is built with that in mind.

Built to work with other suppliers: Engines, generators, thrusters and other equipment come from many different makers. The AMS collects their signals and alarms over standard interfaces, so the crew sees everything in one place instead of on separate panels. That requires suppliers who are willing to cooperate and exchange data in a good way, and X‑CONNECT® is built for exactly that.

Configured, not programmed: Signals, alarms and mimics are set up from tested standard components in one tool, X‑CONNECT® Studio, instead of being programmed from scratch for each vessel. Changes later in the vessel’s life are made in the configuration, not in someone’s code.

Hardware you can get hold of: Controllers and operator stations run on off-the-shelf, marine type-approved hardware that is available worldwide.

Software that keeps moving: X‑CONNECT® is in continuous development, with upgrade options and backward compatibility, so vessels already in operation can benefit from new functions. X‑CONNECT® is delivered and supported through a global network of partners.

What the X‑CONNECT® AMS gives the shipowner

Safety: Deviations are detected early, alarms are clearly prioritised, and the EAS makes sure the engineer on duty is reached when the machinery spaces are unattended. The X‑CONNECT® AMS holds DNV type approval for Cyber Security Essential (SP1), in line with IACS UR E26 and E27.

Operational reliability: Problems are caught while they are still small, and built-in diagnostics help the crew find the cause directly from the operator station.

Savings: A fault that is found early is usually cheaper to fix, and remote support and over-the-air updates reduce the need for service visits on board.

Modernity: The AMS can be extended into a full IAS on the same platform when the vessel needs more automation, without replacing what is already installed.

Read more about how X‑CONNECT® supports shipowners through the vessel's lifetime.

What the X‑CONNECT® AMS gives the system integrator

IO lists can be imported, alarms are configured rather than coded, and standard mimics reduce the drawing work. Alarm lists, signal lists and the bill of materials, as well as the product lifecycle management (PLM) register, are generated directly from the configuration, so documentation and system stay in step. A configuration built once can be reused on the next project.

Learn more about how X‑CONNECT® works for system integrators.

In short

An AMS is the vessel’s early warning system. It watches the machinery, alerts the right people and keeps a record of what happened. A good AMS is not the one with the most alarms, but the one that helps the crew see what matters and act in time, and that can be kept up to date for as long as the vessel is in operation.

Read more about how Alarm and Monitoring System (AMS) are in X‑CONNECT®