Singapore Operations Office:
10 Anson Road #25-16, International Plaza, Singapore 079903
Tel: (65) 6224 2345 Fax: (65) 6227 2345
Email:
[email protected] Website: www.tvship.com
MARINE CIRCULAR
MC-3/2010/12/3
10/2020
FOR: Ship Owners, Ship Managers, Ship Operators, Ship Masters, Ship Officers, Classification
Societies
SUBJECT: SHIP SECURITY ALERT SYSTEM (SSAS)
DEFINITIONS:
The following abbreviations stand for:
▪ “CSO” – Company Security Officer
▪ “CSSRC” – Cargo Ship Safety Radio Certificate
▪ “GMDSS” – Global Maritime Distress and Safety System
▪ “GMT”/”UTC”: – Greenwich Mean Time / Coordinated Universal Time
▪ :GNSS: – Global Navigation Satellite System
▪ “GT” – Gross Tonnage in accordance to ITC 69
▪ “MODU” – Mobile Offshore Drilling Unit
▪ “IMO” – International Maritime Organization
▪ “ISM Code” – International Management Code for the Safe Operation of Ships and for Pollution
Prevention
▪ “ISPS Code” – International Ship and Port Facility Security Code implemented through chapter XI-
2 Special measures to enhance maritime security in SOLAS.
▪ “ISSC” – International Ship Security Certificate
▪ “ITC 69” – International Convention on the Tonnage Measurement of Ships, 1969
▪ “PSCO” – Port State Control Officer
▪ “RSO” – Recognized Security Organization
▪ “SOLAS” – International Convention for the Safety of Life at Sea (SOLAS), 1974, as amended
▪ “SSA” – Ship Security Alert
▪ “SSAS” – Ship Security Alert System
▪ “SSAS-SC” – Self-Contained SSAS
▪ “SSO” – Ship Security Officer
▪ “SSP” – Ship Security Plan
▪ “SSRS” – Ship Security Report System
▪ “UPS” – Uninterruptible Power Supply
The term “Administration” shall mean the Tuvalu Ship Registry.
PURPOSE:
This Marine Circular serves to provide administrative information and technical guidance to ship owners
/ operators and RSOs on the requirements of SOLAS Chapter XI-2, Regulation 6 on SSAS.
Page 1 of 8
REFERENCES:
(a) SOLAS Chapter XI-2, Regulation 6
(b) IMO Resolution MSC.136(76), as amended by MSC.147(77), adopted on 11 December 2002,
Performance standards for a ship security alert system
(c) IMO MSC/Circ.1072, dated 26 June 2003, Guidance on provision of ship security alert systems
(d) IMO MSC/Circ.1155, dated 23 May 2005, Guidance on the message priority and the testing of ship
security alert
(e) IMO MSC/Circ.1190, dated 30 May 2006, Guidance on the provision of Information for identifying
ships when transmitting Ship Security Alerts
(f) Tuvalu Marine Circular MC-8/2011/1, Contact details for recipients of maritime security related
communications
(g) Tuvalu Marine Circular MC-4/2010/12/2, Updates to Issues relating to piracy and armed robbery
against ships in waters off the Coast of Somalia and other High Risk Areas (revokes 35/2010)
APPLICATION:
SSAS applies to the following types of vessels on international voyages:
(a) Passenger ships, including high-speed passenger craft;
(b) Cargo ships, including high-speed craft, of 500 gross tons and upwards; and
(c) Mechanically propelled MODUs as defined in SOLAS Chapter IX, Regulation 1.
CONTENTS:
1. Implementation
SOLAS Chapter XI-2, Regulation 6, requires all ships to be provided with a SSAS, which will transmit
a SSA to a designated competent authority when activated in an emergency situation.
1.1. All vessels shall be provided with an SSAS as follows:
1.1.1. Ships constructed on or after 1 July 2004;
1.1.2. Passenger ships, including high-speed passenger craft, constructed before 1 July
2004 - not later than the first survey of the radio installation after 1 July 2004;
1.1.3. Oil tankers, chemical tankers, gas carriers, bulk carriers and cargo high speed craft,
of 500 GT and upwards constructed before 1 July 2004 - not later than the first survey
of radio installation after 1 July 2004; and
1.1.4. Other cargo ships of 500 GT and upwards and MODUs constructed before 1 July 2004
- not later than the first survey of radio installation after 1 July 2006.
1.2. Regarding compliance with the additional functional requirements of MSC/Circ.1190, vessels
shall be provided with a compliant or upgraded SSAS and tested as follows:
1.2.1. Ships constructed on or after 1 July 2006 - before the ship enters service; and
1.2.2. Ships constructed before 1 July 2006 - not later than the first survey of the radio
installation on or after 1 July 2006.
1.2.3. All SSAs generated by a SSAS shall be sent to the “Security Department” of this
Administration and the CSO.
1.3. The CSSRC is not affected as the SSAS is not considered a radio equipment and is therefore
not covered by the Safety Radio Survey. Any deficiency in the SSAS is however considered a
failure in compliance with the ISPS Code and potentially the ISM Code.
Page 2 of 8
2. Competent Authority
2.1. A competent authority is an organization that receives an alert from a vessel and forwards it
to the Administration and the CSO. A competent authority must demonstrate the capability to
receive an SSA at any time from a vessel and to immediately forward it.
2.2. Some providers of asset tracking services, such as Globe Wireless, PurpleFinder, Transas,
Iridium, etc., incorporating SSAS capabilities, are suitable to take on the role of the competent
authority.
2.3. Companies or organizations desiring to provide SSAS services for Tuvalu flagged vessels
should provide the Administration with a detailed description of the equipment to be installed
or modified and a coordinated communications plan for acting as the competent authority. The
details of the system encompassing the equipment, coverage area, and communications plan,
should also be submitted to the RSO for review.
2.4. Companies desiring to send SSAs directly to the Administration and the CSO or organizations
desiring to act as competent authorities for the forwarding of SSAs to the Administration and
the CSO should confirm the technical arrangements for delivering SSAs to the Administration
at the contact details in Tuvalu Marine Circular MC-8/2011/1.
3. SSP
3.1. Ship Owners / Operators of SOLAS vessels are to request their RSO to review their vessel’s
SSAS equipment and procedures in conjunction with the review of the vessel’s SSP.
3.2. If the vessel already has an approved SSP, it must be amended to address the SSAS, and
affected parts must be available on board for review and approval during the compliance audit
following initial installation. This should include documentation of any equipment that may be
installed to comply with the SSAS.
3.3. The location of the second activation point may be specified in the SSP and remain confidential.
However, in order to avoid the possibility of compromising the objective of the SSAS, this
Administration recommends that this information be kept elsewhere on board in a document
known only to the Master, SSO and other senior ship’s personnel as may be decided by the
CSO.
3.4. The ISSC shall confirm, among other things, compliance with the installation of an effective
SSAS by the applicable Safety Radio Survey implementation date irrespective of when the
vessel may be due for ISPS Code intermediate or renewal audit.
4. System Requirements
4.1. Performance standards for SSASs can be found in IMO Resolution MSC.136(76) as amended
by MSC.147(77), while MSC/Circ.1072 and MSC/Circ.1155 give further guidance on the design
and functional requirements of SSASs.
4.2. The SSAS may be a component of the vessel’s existing radio installations so long as it does
not interfere with the normal function of that equipment. If the SSAS uses any new or modifies
existing radio transmission equipment, then it should be certified by the manufacturer to comply
with the relevant sections of IEC 60945 that are identified as being required for all equipment
categories.
4.3. A suitable alternate source of power, or dedicated battery backup, should be provided if the
SSAS uses the ship’s main source of electrical power, for e.g. systems with an UPS or similar
device that is powered from the ship’s main power can be considered an alternate source of
power.
Page 3 of 8
5. Application
5.1. The transmission of a SSA should not be included with any other routine reporting that the ship
may conduct. The message transmission should be generated automatically with no input from
the operator other than the activation of the system. Cellular telephones may not be sufficiently
automated to satisfy this requirement. To comply with MSC/Circ.1190, the SSA received by a
competent authority should include:
5.1.1. Name of ship;
5.1.2. IMO Ship Identification Number;
5.1.3. Call Sign;
5.1.4. Maritime Mobile Service Identity;
5.1.5. GNSS position (latitude and longitude) of the ship
5.1.6. Date and time of the GNSS position
5.1.7. Course and Speed;
5.1.8. Email Address and Inmarsat number of the vessel for Administration to respond to;
5.1.9. Name of CSO, Email Address and 24/7 mobile phone number for Administration to
respond to;
5.1.10. Name of alternate CSO, Email Address and 24/7 mobile phone number for
Administration to respond to; and
5.1.11. Message stating that the SSAS has been activated and indicating the ship is under
threat or it has been compromised.
Please refer to sample SSA in the annex for programming of the SSAS.
5.2. If vessel engages asset tracking services for SSAS, then an active hyperlink to the monitoring
agency is to be provided in the message. The hyperlink should operate either automatically or
be accessible to the Administration by use of a unique userID and password assigned to the
Administration. This information will expedite the Administration’s ability to contact the nearest
Coastal State Designated Authority and the CSO when a security alert message is received.
5.3. The security alert transmission must be capable of reaching the Administration and the CSO
from any point along the vessel’s intended route. This alert should not be transmitted as a
general distress call but should be directed solely to the Administration and the CSO. As
mentioned earlier, this may be accomplished through a competent authority.
5.4. Line-of-sight transmissions such as encrypted radio transmissions will be closely evaluated,
and may be accepted depending on the route of the vessel.
6. Initial Installation and Type Approval
6.1. Ship Owners / Operators are to notify the RSO prior to installing a SSAS.
6.2. There are generally two (2) types of SSASs commonly known as “Normal SSAS” or “SSAS-
SC. Ship Owners / Operators should be aware of which type of SSAS is fitted to their ships so
that the appropriate software and interfaces are provided to assure that the competent authority
receives all the required information listed in sub-section 5.1 above.
6.3. “Normal SSAS”:
6.3.1. This is a system which requires interface with, and/or depends on input from, radio
and/or navigational equipment required by SOLAS IV and V to meet the performance
standards required by SOLAS Regulation XI-2/6. The SSAS is a requirement of
SOLAS Chapter XI-2 and is not subject to Safety Radio Certification.
6.3.2. In all cases, the RO responsible for the issue of the CSSRC shall be responsible for
the initial installation inspection and testing of the SSAS by an approved radio
technician. A copy of the radio technician’s report, demonstrating compliance with
Page 4 of 8
SOLAS XI-2/6 Paragraphs 2-4 inclusive and MSC/Circ.1190, shall be left on board for
use by the RSO at the next scheduled audit. A comment such as “The SSAS as fitted
meets the requirements of SOLAS Regulation XI-2/6, paragraphs 2-4 inclusive and
MSC/Circ.1190.” shall be entered into the Record of Approved GMDSS Radio
Installation. It should be noted that the record of equipment for Form “R” of the CSSRC
shall not include details of the SSAS. The SSAS installation shall be subject to annual
inspection by an approved radio technician.
6.4. All SSASs shall be reviewed and approved by the RSO during the vessel’s SSP review. A list
of RSOs with links to their website can be found at https://tvship.com/ro.
6.5. “SSAS-SC”:
This is a system which does not require any interface with, and/or depends on input from, radio
and/or navigational equipment required by SOLAS IV and V to meet the performance standards
required by SOLAS XI-2/6. However, software revisions may be necessary on existing
installations to bring the system in compliance with the added information required by
MSC/Circ.1190. This equipment is installed and initiated by the ship and no initial installation
survey is required.
7. Shipboard Verification
7.1. At the next ISPS shipboard audit following the initial installation of a SSAS, the RSO auditor
shall review and approve the related provisions in the SSP, witness a complete SSA test and
verify the implementation of the operational requirements of the SSAS in accordance with the
requirements of ISPS Code A/9.4.17 to A/9.4.18 and sight the Record of Approved GMDSS
Radio Installation, the Statement of Compliance or equivalent (for the case of “Normal SSAS”).
7.2. At each subsequent ISPS shipboard audit, the RSO auditor shall examine the records of
activities on the SSAS specified in ISPS Code A/10.1.10, witness a complete SSA test, verify
the operational requirements of the SSAS, and sight the Record of Approved GMDSS Radio
Installation, the Statement of Compliance or equivalent (for the case of “Normal SSAS”).
7.3. A “complete” SSA test shall require the sending of a test message to the CSO and the
Administration.
8. SSAS Test
8.1. Following the initial installation of the SSAS, the Company has the responsibility:
8.1.1. to ensure that the system is tested and maintained to satisfy operational requirements
according to the approved SSP; and
8.1.2. to keep on board the system records specified in ISPS Code A/10.1.10.
8.2. The system shall be capable of being tested to verify proper operation. The testing should
include the entire alert system, from activation to CSO receipt of the alert.
8.3. The unit should also be capable of being tested in the presence of a PSCO upon request, but
ONLY from the required navigation bridge location and with appropriate prior notification of the
CSO and the Administration.
Page 5 of 8
8.4. The procedures for this testing, including the appropriate Administration’s maritime security
contact details (refer to Tuvalu Marine Circular MC-8/2011/1), should be outlined in the vessel’s
SSP or in a separate document available only to the Master, SSO or other entrusted senior
ship’s personnel.
8.5. The Administration should be notified 24 hours in advance of any test that will result in a SSA
message being sent to the Administration. The date and time of SSA test shall be reported in
GMT/UTC. The SSA test should be conducted during our office operations hours.
Our office operation hours:
Time Zone: Singapore, GMT +08:00 hrs
Monday to Friday: 0900 hrs to 1800 hrs (Lunch Hours: 1300 hrs to 1400 hrs)
Saturday: 0900 hrs to 1300 hrs
Sunday and Public Holiday: Closed
8.6. CSOs are reminded that the Administration should only be receiving test alerts on the following
occasions:
8.6.1. Installation of the SSAS;
8.6.2. Intermediate Audit/Survey for ISSC Certification; and
8.6.3. Renewal Audit/Survey for ISSC Certification.
8.7. The test message should clearly indicate “THIS IS A SSA TEST” on the subject title and/or on
the message body.
8.8. The SSA test shall be properly logged in the ship’s Official Log Book.
9. SSAS Activation
9.1. The activation of a SSA should only require a single action, excluding the opening of protective
covers. There must be at least two (2) activation points. One (1) must be located on the
navigation bridge and at least one (1) other in an area where it would normally be immediately
accessible, e.g., engine room control, master’s stateroom, crew lounge, etc. The activation
points must not be capable of deactivating the alarm once initiated and must be protected
against inadvertent operation. The activation points shall not be protected by seals, lids or
covers that must be broken to activate the alarm since a broken seal would indicate that the
alarm has been tripped. Spring loaded covers or similar devices that provide no indication of
the status of the alarm is acceptable.
9.2. Once activated, the system should continue to transmit the security alert at a frequency of not
less than once every 30 minutes until the status of the alert is confirmed by the CSO and
authorization is given by the CSO for the alarm to be reset or deactivated. There should be a
confidential procedure to properly verify the status of the alert and any resetting or deactivation
of the system. The vessel should initiate the deactivation of the system, unless it can be done
remotely by the CSO.
9.3. When the Administration receives a SSA of which the status cannot be readily confirmed with
the CSO, the Administration will immediately notify the Coastal State(s) in the vicinity of which
the ship is presently operating. It is therefore imperative that the CSO verify immediately the
status of each SSA with the Administration in order to avoid false alarms.
Page 6 of 8
10. Ship Security Report System (SSRS)
Ship Owners / Operators are authorized and strongly recommended to subscribe to the SSRS
because it provides a real-time link between ship operations and naval operations thereby
enhancing the counter-piracy effectiveness of the existing SSAS. Refer to MC-4/2010/12/2 for
details.
Yours sincerely,
Deputy Registrar
Tuvalu Ship Registry
Page 7 of 8
Annex: Sample SSA received by Administration
Sent: Sunday, dd MMM yyyy, hh:mm
To:
[email protected]; CSO 1 <
[email protected]>; CSO 2
<
[email protected]>; Name of ship <
[email protected]>
Subject: < Name of ship> SSAS ALERT REPORT. THIS IS AN SSA TEST
--- SSAS ALERT MESSAGE ---
THIS IS AN SSA TEST.
Vessel Name: Name of ship as shown on Ship Radio Station Licence
IMO Number: IMO Ship Identification Number as assigned by IHS Markit on behalf of the IMO
Call Sign: Call sign as shown on Ship Radio Station Licence
MMSI Number: MMSI number as shown on Ship Radio Station Licence
LAT: Deg Min N/S
LON: Deg Min E/W
Date: dd mmm yyyy (GMT/UTC)
Time: hh:mm (GMT/UTC)
Course: XXX deg
Speed: XXX knots
Vessel Contact: Email: [email protected], Inmarsat : +870 123 456 789 (+870 + Inmarsat
Number)
CSO1: Name of CSO1, Email: [email protected], Mobile: +65 1234 5678
(Country Code + Area Code + Mobile Number),
CSO2: Name of CSO2, Email: [email protected], Mobile: +65 8765 4321
(Country Code + Area Code + Mobile Number)
Remarks: SSAS has been activated and the ship is under threat or it has been compromised.
Fields to be programmed into SSAS.
Fields automatically obtained from GNSS.
Page 8 of 8
Singapore Operations Office:
10 Anson Road #25-16, International Plaza, Singapore 079903
Tel: (65) 6224 2345 Fax: (65) 6227 2345
Email: [email protected] Website: www.tvship.com
MARINE CIRCULAR
MC-8/2011/1
02/2020
FOR: Ship Owners, Ship Managers, Ship Operators, Ship Masters, Ship Officers, Recognized Security
Organizations
SUBJECT: CONTACT DETAILS FOR RECIPIENTS OF MARITIME SECURITY RELATED
COMMUNICATIONS
PURPOSE:
This Marine Circular is to inform all concerned parties on the updated Flag Administration contact details
for receiving maritime related security communications.
REFERENCES:
(a) MSC/Circ.1155 – Guidance on the Message Priority and the Testing of Ship Security Alert Systems
(b) MSC/Circ.1190 – Guidance on the Provision of Information for Identifying Ships when Transmitting
Ship Security Alerts
CONTENTS:
Ship Security Alert System (SSAS) Flag State Contact Point Details:
Tuvalu Ship Registry
Address : 10 Anson Road, #25-16 International Plaza, Singapore 079903
Name : Mr. Wong Ye Cheng
Designation : Safety and Security Officer
Mobile No. : +65 8288 6698
Tel : +65 6224 2345 (24 hours)
Fax : +65 6227 2345
E-mail :
[email protected]Note: Please send the SSAS alert message to the above e-mail address with copy to our fax as an
alternate means if necessary.
Yours sincerely,
Deputy Registrar
Tuvalu Ship Registry
Page 1 of 1
INTERNATIONAL MARITIME ORGANIZATION
4 ALBERT EMBANKMENT
LONDON SE1 7SR E
Telephone: 020 7735 7611
Fax: 020 7587 3210
IMO
Ref. T2-MSS/2.11.1 MSC/Circ.1155
23 May 2005
GUIDANCE ON THE MESSAGE PRIORITY AND THE TESTING
OF SHIP SECURITY ALERT SYSTEMS
1 The Maritime Safety Committee (the Committee), at its seventy-eighth session (12 to
21 May 2004), instructed the Sub-Committee on Radiocommunications and Search and Rescue
(COMSAR Sub-Committee) to consider questions relating to the message priority and the testing
of ship security alert systems and to develop, if necessary, guidance to this end.
2 The COMSAR Sub-Committee, at its ninth session (7 to 11 February 2005), considered
the matter and submitted its recommendations on the issue to the Committee.
3 The Committee, at its eightieth session (11 to 20 May 2005), considered the
recommendation of the COMSAR Sub-Committee and approved the Guidance on the message
priority and the testing of ship security alert systems (the Guidance), as set out at annex.
4 SOLAS Contracting Governments are invited to bring the Guidance to the attention of all
parties concerned with matters relating with ship security alerts and systems.
5 SOLAS Contracting Governments, international organizations and non-governmental
organizations with consultative status which encounter difficulties with the implementation of the
Guidance should bring, at the earliest opportunity, the matter to the attention of the Committee
for consideration of the issues involved and decision on the actions to be taken.
***
I:\CIRC\MSC\1155.doc
MSC/Circ.1155
ANNEX
GUIDANCE ON THE MESSAGE PRIORITY AND THE TESTING
OF SHIP SECURITY ALERT SYSTEMS
I Message priority
1 The Committee, being aware of the message priority requirements applicable to satellite
communications, and given the diversity of ship security alert systems, agreed that there was no
need to develop a message priority requirement for ship security alerts.
2 Ship security alert system communication service providers should deliver the ship
security alert messages without delay so as to permit the relevant competent authorities to take
appropriate action.
3 Ship security alerts may be addressed to more than one recipient, as designated by the
Administration, in order to enhance the resilience of the ship security alert system.
4 The Committee urged once more those SOLAS Contracting Governments that had yet to
establish criteria for the delivery of ship security alerts, to do so as a matter of priority.
5 SOLAS regulation XI-2/13.1.3 requires SOLAS Contracting Governments to
communicate to the Organization and to make available to Companies and ships the names and
contact details of those who have been designated to be available at all times (twenty-four hours
a day seven days a week) to receive and act upon ship security alerts.
6 Administrations should ensure that their designated recipients of ship security alerts are
capable of processing the information received with the highest priority and taking appropriate
actions.
II Testing
1 The Committee agreed that there was a need for ship security alert systems to be subject
to testing.
2 However, given the multiplicity of ship security alert systems and the fact that a number
of systems in use already had test procedures in place, the Committee decided that it would be
impractical to develop a test protocol to cover all systems.
3 The Committee thus agreed that the development of procedures and protocols for testing
ship security alert systems were a matter for individual Administrations.
4 Ships, Companies, Administrations and recognized security organizations should ensure
that when ship security alert systems are to be tested those concerned are notified so that the
testing of the ship security alert system does not inadvertently lead to unintended emergency
response actions.
5 When the ship security alert system accidentally transmits, during testing, a ship security
alert, ships, Companies, Administrations and recognized security organizations should act
expeditiously to ensure that all concerned parties are made aware that the alert is false and that no
emergency response action should be taken.
______________
I:\CIRC\MSC\1155.doc
INTERNATIONAL MARITIME ORGANIZATION
4 ALBERT EMBANKMENT
LONDON SE1 7SR E
Telephone: 020 7587 3152
Fax: 020 7587 3210
IMO
Ref. T2-MSS/2.11.1 MSC.1/Circ.1190
30 May 2006
GUIDANCE ON THE PROVISION OF INFORMATION FOR
IDENTIFYING SHIPS WHEN TRANSMITTING
SHIP SECURITY ALERTS
1 The Maritime Safety Committee (the Committee), at its eighty-first session
(10 to 19 May 2006), noted reports that in a number of cases, when the competent authorities
designated by Administrations received ship security alerts (SSAs), the information provided to
them for identifying the ships1 transmitting the alert were not adequate and they could not easily
identify the ships concerned.
2 The Committee recognized that, if ship security alert systems were to function in an
effective and efficient manner so as to provide the security-related benefits for which they were
envisioned, there was a need to ensure a harmonized and consistent implementation of the
provisions of SOLAS regulation XI-2/6 on Ship security alert systems and of the associated
performance standards2. As a result the Committee approved the Guidance on the provision of
information for identifying ships when transmitting ship security alerts (the Guidance) set out
at annex.
3 SOLAS Contracting Governments are invited to bring the Guidance to the attention of
owners and of Companies operating ships entitled to fly their flag, of those they have recognized,
authorized or approved to provider services in relation to SSAs and of the recognized
organizations and the recognized security organizations they have authorized to act on
their behalf.
4 SOLAS Contracting Governments, international organizations and non-governmental
organizations with consultative status which encounter difficulties with the implementation of the
Guidance should bring, at the earliest opportunity, the matter to the attention of the Committee
for consideration of actions to be taken.
***
1
The term “ship” in this circular refers to the ships which are subject to the provisions of SOLAS chapter XI-2
and of the ISPS Code.
2
Resolution MSC.136(76) on Performance standards for a ship security alert system and resolution MSC.147(77)
on Adoption of the Revised performance standards for a ship security alert system.
I:\CIRC\MSC\01\1190.doc
MSC.1/Circ.1190
ANNEX
GUIDANCE ON THE PROVISION OF INFORMATION FOR IDENTIFYING
SHIPS WHEN TRANSMITTING SHIP SECURITY ALERTS
INTRODUCTION
1 SOLAS regulation XI-2/6 and the associated performance standards3 specify that the ship
security alert system, when activated, shall, inter alia, initiate and transmit a ship-to-shore
security alert (SSA) to a competent authority designated by the Administration (the designated
recipient) identifying the ship, its location, the date and time of the position and indicating that
the security of the ship is under threat or it has been compromised.
2 Administrations have accepted, recognized or approved a variety of equipment and
systems to perform the function of the ship security alert system (SSAS) some of which include
communication (CSP) and application (ASP) service providers. However, in some cases when
the SSA is received by the designated recipient, it does not clearly identify the ship which
transmitted the alert.
INFORMATION TO BE PROVIDED TO THE COMPETENT AUTHORITIES
3 When the SSA is delivered to the designated recipient the SSA should include the
following information:
.1 Name of ship;
.2 IMO Ship identification number;
.3 Call Sign;
.4 Maritime Mobile Service Identity;
.5 GNSS position (latitude and longitude) of the ship; and
.6 Date and time of the GNSS position.
4 Depending on the equipment, system and arrangements used, the name, the IMO Ship
identification number, the Call Sign and the Maritime Mobile Service Identity of the ship may be
added to the signal or message transmitted by the shipborne equipment, by the CSP or the ASP,
before the SSA is delivered to the designated recipient.
TRANSITIONAL PROVISIONS
5 To bring into line the performance of SSASs, these should be tested as follows:
.1 ships constructed before 1 July 2006, not later than the first survey of the radio
installation on or after 1 July 2006; and
.2 ships constructed on or after 1 July 2006, before the ship enters service;
to verify that, when the SSAS is activated, the information specified in paragraph 3 above and the
indication that the security of the ship is under threat or it has been compromised are received by
the designated recipient. However, if the arrangements established by the Administration are in
compliance with paragraph 3 above such additional tests are not required.
3
Resolution MSC.136(76) on Performance standards for a ship security alert system and Resolution
MSC.147(77) on Adoption of the Revised performance standards for a ship security alert system.
I:\CIRC\MSC\01\1190.doc
MSC.1/Circ.1190
ANNEX
Page 2
TRANSFER OF FLAG
6 As from 1 July 2006, upon the transfer of the flag of a ship from another State or another
SOLAS Contracting Government, the receiving Administration should test the SSAS to ensure
that when the SSAS is activated, the information specified in paragraph 3 above and the
indication that the security of the ship is under threat or it has been compromised are received by
the designated recipient.
TESTING
7 When testing SSASs, the provisions of paragraphs II.3 and II.4 of the annex to
MSC/Circ.1155 on Guidance on the message priority and the testing of ship security alert
systems should be observed.
Related provisions: SOLAS regulation XI-2/6, resolutions MSC.136(76) and MSC.147(77),
MSC/Circ.1072 and MSC/Circ.1155.
___________
I:\CIRC\MSC\01\1190.doc
