An alarm and monitoring system retrofit is open-heart surgery on a working vessel: hundreds of signals, safety obligations, and a patient that keeps sailing. The playbook that keeps it boring:
The phases
1. Deep survey first. Every existing signal walked from sensor to alarm channel and recorded — tag, cable, terminal, alarm setpoint, class role. Old AMS documentation lies gently; the survey is the truth the whole project stands on. This is also where dead channels, bridged alarms and thirty years of “temporary” fixes surface into the open.
2. Engineering and staging ashore. New I/O layout mirroring the survey, cabinet pre-build, database (channels, setpoints, alarm texts in the crew’s working language) prepared and simulated — a factory acceptance with signal simulators saves days aboard, exactly the office-vs-site economics of every commissioning.
3. Migration in slices, alongside normal operations where the vessel’s schedule demands (as in our Piraeus retrofit): section by section, old and new running in parallel per zone, each slice’s signals verified live (real sensor exercised, alarm witnessed) before the old channel dies. The non-negotiable: at every moment, some system holds each class-required alarm — the migration plan proves it on paper before class and crew believe it.
4. Handover as a project phase: crew training on the new philosophy, updated cause-and-effect documents on the bridge and ECR, spares aboard, and the as-migrated database archived ashore and aboard.
FAQ
Typical duration? Survey and engineering in weeks; onboard migration commonly staged across port stays or one longer availability — the slicing is designed around the ship’s trade, not the integrator’s preference.
Keep any old panels? Occasionally as repeaters during transition; ending state should be clean — hybrid permanent installations age into unmaintainable folklore.
Zone Otomasyon retrofits AMS installations alongside port operations — see the M/V Aegean Star project. Marine retrofits.