SSAS (Ship Security Alert System)
medium
4 models total
A Ship Security Alert System sends a covert distress signal to the flag state and company, not to nearby ships — it is built to look and sound exactly like nothing is happening on the bridge.
Read more — SSAS (Ship Security Alert System) explained ▾
What sets SSAS apart
SSAS is deliberately the quiet cousin of the ship's other distress systems. A DSC distress call or an EPIRB is meant to be loud and obvious, alerting everyone in range. SSAS does the opposite: activating it gives no audible or visible indication anywhere on the ship, so a crew member can trigger it during a hijacking or piracy attack without the attackers knowing. The alert goes only to the company's designated security contact point and the flag state administration, who then decide how to respond, including notifying nearby naval or coast guard assets. It is a security tool, not a general distress system, and it is required precisely because SOLAS-regulated ships are considered a piracy and terrorism target class of their own.
Main components
Activation points
At least two covert activation points are required, typically one on the bridge and one in another location such as the master's cabin or engine control room, so that a single compromised location does not defeat the system.
Ship security alert unit
The core unit that generates the alert message, containing the ship's identity, position and a security alert code, and transmits it via a satellite communication terminal independent of the ship's normal, visible communications traffic.
Communication link
Usually piggybacks on the Inmarsat or other satellite terminal already fitted for GMDSS, but the transmission itself produces no on-board indication, unlike a normal distress alert which triggers audible alarms throughout the ship.
Shore-side reception
The alert routes to a pre-programmed list of recipients — the company security officer and the flag administration — who verify the alert and coordinate a response, rather than the message going out over open distress frequencies.
Regulations and class
SSAS is mandated under SOLAS Chapter XI-2, Regulation 6, part of the ISPS Code framework. All passenger ships, cargo ships of 500 gross tonnage and above, and mobile offshore drilling units engaged on international voyages must carry it. Flag state administrations set the specific programming and testing procedures; the system's activation points, transmission testing, and the confidentiality of its wiring diagram are all subject to verification during ISSC (International Ship Security Certificate) audits, and unauthorized crew must not be able to identify where the activation points are from documentation left in plain view.
Typical faults
| Fault | Consequence |
|---|---|
| Activation point wiring exposed or documented in accessible manuals | Defeats the covert design; an attacker familiar with the ship can disable it |
| Satellite terminal antenna fault shared with other communications | SSAS transmission fails silently along with normal comms, with no on-board alarm to flag it |
| Test alerts not properly coded as tests | Triggers a real security response ashore, including possible naval tasking, for a routine drill |
| Contact list at the company or flag state not kept current | Genuine alert reaches an outdated recipient, delaying any response |
What to look for in a supplier
- A clean installation that keeps activation point wiring separate from documentation available to unauthorized personnel.
- Confirmed compatibility with the ship's existing satellite communication terminal rather than a separate, conspicuous antenna.
- A tested procedure for coded test transmissions that will not be mistaken for a live alert ashore.
Confirm the flag state's test procedure with the company security officer before every SSAS test — an uncoded test alert has sent real responses to sea before now.
4 manufacturers · 4 models
GMDSS AT
1
SSAS
Satellite-based
· Navigation Data / Sensor
· Satellite-based SSAS
Technology
Satellite
Isps required
ja
Common Failures & Inspection Points
- Sensor, camera or input failure causes missing data, blank images or channel alarms
- Power-supply, UPS or network faults cause system restart, loss of recording or unavailable remote status
- Storage-media or recorder faults cause gaps in retained data or failed self-tests
- Incorrect time, configuration or interface data causes inconsistent records or false alarms
- Control, acknowledgment or communication faults cause unavailable watchkeeping or security functions
Service: Review self-tests, event logs, time synchronization, power supplies, storage status and connected sensor channels. Verify required alarms and communication paths under the approved procedure without sending unauthorized security alerts. Check data quality and retention status where applicable. Refer to manufacturer and statutory documentation for the exact figure for test and retention criteria.
Spare Parts: Carry approved storage or recorder modules where supported, power supplies, network interfaces, camera parts, fuses and backed-up configuration data.
Strengths
- Low acquisition cost compared with premium SSAS units
- Simple installation and integration with existing bridge systems
- Meets minimum IMO/GMDSS functional requirements for security alerts
- ISPS compliance flag indicated as required
Weaknesses
- Limited satellite service network may affect signal reliability in remote regions
- Reported variability in hardware quality and component durability
- Testing and certification compliance can be problematic with some flag states
- Potentially fewer redundancy features than higher‑end models
Typical Vessels:
General cargoCoastal tankerOffshore supply vesselSmall container feederFishing vessels (larger)
Decision Guide: Choose if: you need a cost‑effective SSAS for vessels operating in well‑covered satellite zones and the flag state accepts basic GMDSS compliance. Avoid if: your operation requires high reliability, extensive global coverage, or strict flag approvals that demand higher‑grade hardware.
Use Cases: Voyage recording, bridge watchkeeping, onboard surveillance and statutory security functions.
JRC
1
SSAS
Inmarsat-C based
· Navigation Data / Sensor
· Inmarsat-C
Technology
Inmarsat-C
Isps required
ja
Common Failures & Inspection Points
- Sensor, camera or input failure causes missing data, blank images or channel alarms
- Power-supply, UPS or network faults cause system restart, loss of recording or unavailable remote status
- Storage-media or recorder faults cause gaps in retained data or failed self-tests
- Incorrect time, configuration or interface data causes inconsistent records or false alarms
- Control, acknowledgment or communication faults cause unavailable watchkeeping or security functions
Service: Review self-tests, event logs, time synchronization, power supplies, storage status and connected sensor channels. Verify required alarms and communication paths under the approved procedure without sending unauthorized security alerts. Check data quality and retention status where applicable. Refer to manufacturer and statutory documentation for the exact figure for test and retention criteria.
Spare Parts: Carry approved storage or recorder modules where supported, power supplies, network interfaces, camera parts, fuses and backed-up configuration data.
Strengths
- Integrated into JRC GMDSS console – saves panel space and simplifies wiring.
- Dual covert activation buttons provide redundancy for manual triggering.
- Automatic transmission of ship position and identity to shore via Inmarsat‑C.
- Meets SOLAS Chapter XII‑1 requirements for SSAS on all applicable vessels.
- Remote test capability through the console interface.
Weaknesses
- Reported integration issues with other JRC Inmarsat equipment, requiring careful system engineering.
- Covert activation buttons can be hard to locate or reach in emergencies.
- Test procedure is considered cumbersome and may need additional crew training.
- Limited to Inmarsat‑C satellite service; no fallback to alternative constellations.
- Requires an approved International Ship Security Plan (ISPS) registration before activation.
Typical Vessels:
TankerContainer shipBulk carrierPassenger ferryCruise shipOffshore supply vessel
Certifications:
IMO SOLAS Type Approval (SSAS)USCG Type ApprovalDNV Classification
Decision Guide: Choose if: you need a compact, console‑integrated SSAS that complies with SOLAS and already use JRC GMDSS equipment; you value dual covert activation points for redundancy. Avoid if: your vessel relies on multiple satellite providers or you prefer a system with simpler manual activation and testing procedures.
Use Cases: Voyage recording, bridge watchkeeping, onboard surveillance and statutory security functions.
Pole Star
1
SSAS
Multi-satellite
· Navigation Data / Sensor
· multi-satellite SSAS/LRIT unit
Technology
Multi-satellite
Isps required
ja
Lrit capable
ja
Common Failures & Inspection Points
- Sensor, camera or input failure causes missing data, blank images or channel alarms
- Power-supply, UPS or network faults cause system restart, loss of recording or unavailable remote status
- Storage-media or recorder faults cause gaps in retained data or failed self-tests
- Incorrect time, configuration or interface data causes inconsistent records or false alarms
- Control, acknowledgment or communication faults cause unavailable watchkeeping or security functions
Service: Review self-tests, event logs, time synchronization, power supplies, storage status and connected sensor channels. Verify required alarms and communication paths under the approved procedure without sending unauthorized security alerts. Check data quality and retention status where applicable. Refer to manufacturer and statutory documentation for the exact figure for test and retention criteria.
Spare Parts: Carry approved storage or recorder modules where supported, power supplies, network interfaces, camera parts, fuses and backed-up configuration data.
Strengths
- Combined SSAS and LRIT functionality reduces equipment footprint and installation cost
- Multi‑satellite connectivity offers near‑global coverage and redundancy
- ISP‑required encryption provides secure transmission of alerts and tracking data
- Proven manufacturer with field experience in both security and LRIT services
Weaknesses
- Performance can be degraded by antenna obstruction or poor line‑of‑sight to satellites
- Battery backup has been reported to fail if not regularly tested or maintained
- Configuration and integration require careful setup; misconfiguration can disable alerts
- Dependence on an external ISP for secure communications may limit use in remote areas
Typical Vessels:
Container shipTankerBulk carrierCruise linerOffshore support vesselGeneral cargo vessel
Certifications:
IMO SOLAS Chapter IX (SSAS)DNV class approval
Decision Guide: Choose if you need a single, space‑saving unit that delivers both mandatory SSAS alerts and LRIT tracking with global satellite coverage. Avoid if your vessel operates in regions with limited ISP connectivity, has constrained antenna placement, or cannot guarantee regular battery maintenance.
Use Cases: Voyage recording, bridge watchkeeping, onboard surveillance and statutory security functions.
Sailor / Cobham
1
SSAS
Inmarsat-C based
· Navigation Data / Sensor
· Inmarsat-C
Technology
Inmarsat-C
Isps required
ja
Common Failures & Inspection Points
- Sensor, camera or input failure causes missing data, blank images or channel alarms
- Power-supply, UPS or network faults cause system restart, loss of recording or unavailable remote status
- Storage-media or recorder faults cause gaps in retained data or failed self-tests
- Incorrect time, configuration or interface data causes inconsistent records or false alarms
- Control, acknowledgment or communication faults cause unavailable watchkeeping or security functions
Service: Review self-tests, event logs, time synchronization, power supplies, storage status and connected sensor channels. Verify required alarms and communication paths under the approved procedure without sending unauthorized security alerts. Check data quality and retention status where applicable. Refer to manufacturer and statutory documentation for the exact figure for test and retention criteria.
Spare Parts: Carry approved storage or recorder modules where supported, power supplies, network interfaces, camera parts, fuses and backed-up configuration data.
Strengths
- Integrated with the Sailor 6110 Inmarsat‑C terminal for seamless installation
- Global satellite coverage ensures alerts can be sent from any location
- Covert activation button allows discreet distress signalling
- Automatic transmission of GPS position and vessel identity to authorities
- Meets SOLAS Chapter XI‑2 and ISPS Code requirements without additional hardware
Weaknesses
- Relies entirely on the Inmarsat‑C link; loss of service disables the alert function
- Covert button placement can be difficult for crew to locate under stress
- Annual functional test is mandatory and may fail if not properly maintained
- One‑way messaging only – no acknowledgment from the monitoring centre
- Requires a separate subscription and power supply beyond the main bridge systems
Typical Vessels:
Passenger shipsCruise linersFerriesOffshore support vesselsTankersContainer ships
Certifications:
SOLAS Chapter XI‑2
Decision Guide: Choose if the vessel must comply with mandatory SSAS requirements, already uses a Sailor Inmarsat‑C terminal, and values a discreet, integrated alert solution. Avoid if reliable satellite coverage cannot be guaranteed, the crew prefers a dual‑mode (satellite + VHF) system, or budget constraints limit subscription costs.
Use Cases: Voyage recording, bridge watchkeeping, onboard surveillance and statutory security functions.