The existing SOLAS Reg. V/19.2.4(effective 1st July 2002) requires AIS installation on new and existing ships. The applicability date for existing ships on international voyages is spread over a period from 1 July 2003 to 1 July 2007 depending on ship type and size.
Existing SOLAS Chapter XI "Special Measures to Enhance Maritime Safety" renumbered as XI-1; with amendments to Reg. 3 "Ship identification number" and addition of a new Reg. 5 "Continuous synopsis record".
Reg. 3 amendment - Ship identification number to be marked permanently (on existing ships at 1st scheduled dry-dock after 1 July 2004) in a visible and in an easily accessible place.New Reg. 5 - All ships to be issued with a continuous synopsis record intended to provide an on-board record of the history of the ship. On existing ships, the record shall provide history, at least, as from 1 July 2004.
Continuous Synopsis Record
The new Chapter XI-2 titled " Special Measures to Enhance Maritime Security" Has 13 regulations on security-related requirements for ships and ports. Refers to the ISPS Code Parts A and B
ADMs shall set security levels and ensure that information on security levels is provided to ships under their flag.CGs shall set security levels and ensure that information on security levels is provided to port facilities within their territory, and to ships prior to entering a port or whilst in a port within their territory.
Companies and ships
Company to ensure that the master has available onboard information through which officers duly authorized by CG can establish
Required to be provided on
CGs shall, for ships operating in or having communicated an intention to enter their territorial sea
Master shall not be constrained, by the Company or others, from taking or executing any decision which, in his professional judgment, is necessary to maintain the ship's safety and security. This includes denial of access to persons (except those identified as duly authorized by a CG) or their effects, refusal to load cargo including containers or other closed cargo transport units.
May be required to provide relevant information to officers duly authorized, before entering the port. Such information includes the following
PFs to comply with relevant parts of this chapter and ISPS Code Part A; guidance in ISPS Code Part B to be taken into account
CGs to ensure that
CGs may conclude in writing, bilateral or multilateral agreements with other CGs on alternative security arrangements covering short international voyages on fixed routes between port facilities within their territories. Such agreements shall not compromise the level of security of other ships or of port facilities not covered by the agreement. Any ship covered by such an agreement shall not conduct any ship-to-ship activities with any ship not covered by the agreement.
Other security measures equivalent to and at least as effective as those prescribed in this chapter or in Part A of ISPS Code may be allowed
Contracting governments shall, not later than 1 July 2004, communicate to IMO certain relevant information and thereafter update such information as and when necessary. IMO shall circulate such particulars to other CGs for the information of their officers
To establish An international framework involving co-operation between CGs, Govt agencies, local administrations and shipping & port industries to detect security threats and take preventive measures. To establish respective roles and responsibilities of CGs, Govt agencies, local administrations and shipping & port industries.
Gathering & assessing information on security threats & exchanging it with appropriate CGs.Requiring maintenance of communication protocols for ships & PFsPreventing unauthorized access to ships, PFs & their restricted areas. Preventing the introduction of unauthorized weapons, incendiary devices or explosives to ships or PFs.Providing means for raising alarm in reaction to security incidents. Requiring ship & PF security plans based upon security assessments. Requiring training, drills and exercises to ensure familiarity with security plans and procedures.
CGs have the overall responsibility for maritime security regime in their areas of jurisdiction. For port facilities, CGs will identify the organization(s) or the administration(s), within the Contracting Government, as"designated authority".
Maritime Administrations would normally have the responsibilities in respect of security of ships under their flag.
CGs shall set security levels & provide guidance for protection from security incidents. Factors to be considered in setting levels
Declaration of security
Ensure that the Company and ships comply with relevant requirements of SOLAS Chapter XI-2 and of Part A of the ISPS Code, taking into account the guidance given in Part B of the ISPS Code. Ensure that compliance by ships is verified and certified as provided for in part A of ISPS Code.
Designate a company security officer (CSO).
Designate a ship security officer (SSO) on each ship.
Ensure that CSO, appropriate shore-based Company personnel and the SSO receive the necessary training.
Ensure availability with ship's Master, at all times, of following information (updated and kept current)
ADM to approve
RSO may prepare SSP for a specific ship
ADM may entrust review & approval of SSP or its amendments to RSO ( Provided that RSO is not involved in either preparing the SSA or SSP or amendments)
Shall be available onboard and protected from unauthorized access or disclosure
Not subject to inspection under control & compliance measures
Records of following activities addressed in SSP shall be maintained on board
CSO and SSO
Drills shall be carried out at appropriate intervals to ensure effective implementation of the SSP, taking into account
Port facility security
Port Facility Security Assessment
Port Facility Security Plan
Port Facility Security Officer
To ensure effective implementation of the PFSP, drills shall be carried out at appropriate intervals, taking into account
CG may issue an appropriate SoCPF, indicating
|1||Local Notice to Mariners No.5/2021||2.1 MB|
|2||Local Notice to Mariners No.4/2021||829 KB|
|3||Local Notice to Mariners No.3/2021||682 KB|
|4||Local Notice to Mariners No.2/2021||11.7 MB|
|5||Corrigendum to Local Notice to Mariners No.1/2021||896 KB|
|6||Local Notice to Mariners No.1/2021||1267 KB|
|7||Local Notice to Mariners No.10/2020||647 KB|
|8||Local Notice to Mariners No.9/2020||332 KB|
|9||Local Notice to Mariners No.8/2020||729 KB|
|10||Local Notice to Mariners No.7/2020||314 KB|
|11||Local Notice to Mariners No.6/2020||293 KB|
|12||Local Notice to Mariners No.5/2020||332 KB|
|13||Local Notice to Mariners No.4/2020||294 KB|