SlideShare una empresa de Scribd logo
1 de 11
Descargar para leer sin conexión
LRIT (Long Range Identification and Tracking) 
ANOOP.R.NAIR, Registro Italiano Navale 
Abstract 
Since long time some global system to link all the maritime data regarding the vessels in operation was a 
need. Finally IMO has come up with the implementation of such a system onboard vessels which would 
help the identification, tracking and also sharing the information of ships. This article is intended to give 
an insight into the new regulation by the IMO regarding the introduction of LRIT as new navigational 
equipment on board ships as per SOLAS Reg.V/19-1. Regulation V/19-1.4.1 specifies that ships constructed 
on or after 31 December 2008 shall transmit LRIT information as from the date they enter service and for 
ships constructed before 31 December 2008 provides a phased-in implementation schedule which is 
dependant, inter alia, on the date on which the first survey of the radio installation of the ship becomes due 
after 31 December 2008 and in the case of ships which operate exclusively in sea area A4 after 1 July 
2009.This paper deals with the architecture of LRIT and also with the conformance testing of the shipboard 
equipment. This paper deals mainly with the parameters to be taken care of in a surveyors’ perspective. 
This paper also contains a Conformance test Checklist for the testing of the shipborne equipment which 
was prepared on the basis of MSC Circulars and IMO regulations. 
Introduction 
On 19 May 2006 the International Maritime Organization adopted resolution 
MSC.202(81) which required the establishment of an international system for the Long 
range Identification and Tracking of ships (LRIT). This resolution amends chapter V of 
the International Convention for the Safety of Life at Sea (SOLAS), regulation 19-1 and 
binds all governments which have contracted to the IMO. The regulation applies to ships 
engaged on international voyages, especially for all passenger ships including high speed 
crafts, cargo ships of 300 gross tonnage and above and Mobile Offshore Drilling Units. 
All vessels of 300 gross tonnage and above on international voyage will need to be 
compliant with LRIT regulations. Compliance to LRIT is important. Some Governments 
have indicated that they may not grant entry to their territorial waters, or to their ports, for 
vessels that do not comply with LRIT. 
The regulation entered into force on 1 January 2008 and is applicable to ships constructed 
on or after 31 December 2008 with a phased-in implementation schedule for ships 
constructed before 31 December 2008. LRIT is intended too be operational with respect 
to the transmission of LRIT information by ships as from 31 December 2008. There is an 
exemption for ships operating exclusively in sea area A1 from the requirement to 
transmit LRIT information, since such ships are already fitted with AIS. It also identifies 
which authorities may have access to LRIT information. These ships must automatically 
report their position to their Flag Administration at least 4 times a day. Other contracting 
governments may request information about vessels in which they have a legitimate 
interest under the regulation. 
Overview of LRIT 
The Long-Range Identification and Tracking (LRIT) system provides for the global 
identification and tracking of ships. The LRIT system consists of
a) The shipborne LRIT information transmitting equipment, 
b) The Communication Service Provider(s), 
c) The Application Service Provider(s), 
d) The LRIT Data Centre(s), including any related Vessel Monitoring System(s), 
e) The LRIT Data Distribution Plan and 
f) The International LRIT Data Exchange. 
Certain aspects of the performance of the LRIT system are reviewed or audited by an 
LRIT Coordinator acting on behalf of all Contracting Governments. Figure 1 provides 
an illustration of the LRIT system architecture. 
Figure-1 
LRIT information is provided to Contracting Governments and Search and rescue 
services entitled to receive the information, upon request, through a system of National, 
Regional, Cooperative and International LRIT Data Centres, using where necessary, the 
International LRIT Data Exchange. Each Administration should provide to the LRIT 
Data Centre it has selected, a list of the ships entitled to fly its flag, which are required to 
transmit LRIT information, together with other salient details and should update, without
undue delay, such lists as and when changes occur. Ships should only transmit the LRIT 
information to the LRIT Data Centre selected by their Administration 
a) The shipborne LRIT information transmitting equipment 
The shipborne radio equipment shall be a part of the global maritime distress and safety 
system (GMDSS) and for electronic navigational aids. The various requirements include. 
1) Be capable of automatically and without human intervention on board the ship 
transmitting the ship’s LRIT information at 6-hour intervals to an LRIT Data Centre 
2) Be capable of being configured remotely to transmit LRIT information at variable 
intervals 
3) Be capable of transmitting LRIT information following receipt of polling commands 
4) Interface directly to the shipborne global navigation satellite system equipment, or 
have internal positioning capability 
5) Be supplied with energy from the main and emergency source of electrical power 
6) Be tested for electromagnetic compatibility taking into account the recommendations 
developed by the organization 
7) To be type approved by the administration. 
Table-1 provides the functional requirements of a ship borne equipment. 
Table-1 
DATA TO BE TRANSMITTED FROM THE SHIPBORNE EQUIPMENT 
Parameter Comments 
Shipborne equipment 
Identifier 
The identifier used by the shipborne equipment 
Positional data 
The Global Navigation Satellite System (GNSS) position (latitude and 
longitude) of the ship (based on the WGS 84 datum). 
Position: The equipment should be capable of transmitting the GNSS 
position(latitude and longitude) of the ship (based on WGS 84 datum) as 
prescribed by regulation V/19-1, without human interaction on board the 
ship. 
On-demand(1) position reports: The equipment should be capable of 
responding to a request to transmit LRIT information on demand without 
human interaction on board the ship, irrespective of where the ship is 
located. 
Pre-scheduled(2) position reports: The equipment should be capable of 
being remotely configured to transmit LRIT information at intervals 
ranging from a minimum of 15 min to periods of 6 h to the LRIT Data 
Centre, irrespective of where the ship is located and without human 
interaction on board the ship. 
Time Stamp 1 The date and time(3) associated with the GNSS position. The equipment 
should be capable of transmitting the time(3) associated with the GNSS 
position with each transmission of LRIT information. 
Notes (1) On-demand position reports means transmission of LRIT information as a result of either 
receipt of polling command or of remote configuration of the equipment so as to transmit at 
interval other than the preset ones. 
(2) Pre-scheduled position reports means transmission of LRIT information at the preset 
transmit intervals. 
(3) All times should be indicated as Universal Coordinated Time (UTC).
The shipborne equipment should transmit the LRIT information using a communication 
system which provides coverage in all areas where the ship operates. The shipborne 
equipment should be set to automatically transmit the ship’s LRIT information at 6-hour 
intervals to the LRIT Data Centre identified by the Administration, unless the LRIT Data 
User requesting the provision of LRIT information specifies a more frequent transmission 
interval. When a ship is undergoing repairs, modifications or conversions in dry-dock or 
in port or is laid up for a long period, the master or the Administration may reduce the 
frequency of the transmission LRIT information to one transmission every 24-hour 
period, or may temporarily stop the transmission of such information.Figure-2 below 
shows a sample Shipboard equipment manufactured by Blue tracker. 
Fig-2 
Shipborne Equipment 
b) The Communication Service Provider(s) 
Communications Service Providers (CSPs) provide services which link the various parts 
of the LRIT system using communications protocols in order to ensure the end-to-end 
secure transfer of the LRIT information. This requirement precludes the use of non-secure 
broadcast systems. A CSP may also provide services as an ASP. 
c) The Application Service Provider(s) 
ASP s providing data to the National, regional or co-operative LRIT data centre should 
be recognised by the Contracting Government and to an International LRIT Data Centre 
should be recognized by the Committee. An ASP should provide a communication 
protocol interface between the Communication Service Providers and the LRIT Data 
Centre to enable the remote integration of the ship borne equipment into an LRIT Data 
Centre, automatic configuration of transmission of LRIT information, automatic 
modification of the interval of transmission of LRIT information, automatic suspension
of transmission of LRIT information, on demand transmission of LRIT information and 
automatic recovery and management of transmission of LRIT information. They should 
ensure that LRIT information is collected, stored and routed in a reliable and secure 
manner. The ASP where used should add the data identified in Table-2 to each 
transmission of LRIT information: 
Table-2 
DATA TO BE ADDED BY AN APPLICATION SERVICE PROVIDER 
AND AT THE LRIT DATA CENTRE 
Parameters Comments 
Ship Identity The IMO ship identification number and MMSI for the ship. 
Name of ship Name of the ship which has transmitted the LRIT information in the English 
language using latin-1 alphabet and UTF-8 encoding. 
Time Stamp 2 The date and time the transmission of LRIT information is received by the 
ASP (if used). 
Time Stamp 3 The date and time the received LRIT information is forwarded from the 
ASP (if used) to the appropriate LRIT Data Centre. 
LRIT Data Centre The identity of the LRIT Data Centre to be clearly indicated by a Unique 
Identifier Identifier. 
Time Stamp 4 The date and time the LRIT information is received by the LRIT Data 
Centre. 
Time Stamp 5 The date and time the transmission of LRIT information is forwarded from 
the LRIT Data Centre to an LRIT Data User. 
d) The LRIT data centre (s) 
They collect LRIT information from ships instructed by their Administrations to transmit 
the LRIT information to the centre. maintain a record of the ships which transmit LRIT 
information to the centre including name of ship, IMO Ship identification number, call 
sign and Maritime Mobile Service Identity (MMSI). The response delay should be 
a) for LRIT information archived within the last 4 days, send the LRIT information 
within 30 min of receiving a request. 
b) for LRIT information archived between 4 and 30 days previously, send the LRIT 
information within 1 h of receiving a request. 
c) for LRIT information archived more than 30 days previously, send the LRIT 
information within 5 days of receiving a request. 
A Contracting Government may establish a National LRIT Data Centre. A Contracting 
Government establishing such a centre should provide relevant details to the 
Organization and there after should, without undue delay, update the information 
provided as and when changes occur. A group of Contracting Governments may establish 
either a Regional or a Cooperative LRIT Data Centre. The arrangements for 
establishing such a centre should be agreed amongst the Contracting Governments 
concerned. One of the Contracting Governments establishing such a centre should 
provide relevant details to the Organization and thereafter should, without undue delay, 
update the information provided as and when changes occur. Upon request, National, 
Regional and Cooperative LRIT Data Centres may provide services to Contracting 
Governments other than those establishing the centre.
National, Regional and Cooperative LRIT Data Centres may also serve as a National, 
Regional or Cooperative Vessel Monitoring System (VMS) and may require, as VMS, 
the transmission from ships of additional information, or of information at different 
intervals, or of information from ships which are not required to transmit LRIT 
information. VMS s may also perform other functions. If a National, Regional or 
Cooperative LRIT Data Centre collects additional information from ships, it should 
transmit only the required LRIT information to the other LRIT Data Centres through the 
International LRIT Data Exchange. 
An International LRIT Data Centre recognized by the Committee should be 
established. Contracting Governments not participating in a National, Regional or 
Cooperative LRIT Data Centre, or Contracting Governments having an interest in the 
establishment of an International LRIT Data Centre should cooperate, under the 
coordination of the Committee, with a view to ensuring its establishment. 
e) The LRIT Data Distribution Plan 
The LRIT Data Distribution Plan should include a list indicating the unique LRIT 
identities of Contracting Governments, Search and rescue services entitled to receive 
LRIT information, LRIT Data Centres, the International LRIT Data Exchange, ASPs, the 
LRIT Data Distribution Plan server and the LRIT Coordinator. The LRIT Data 
Distribution Plan server should comply with the Technical specifications for LRIT Data 
Distribution Plan and with the relevant provisions of the Technical specifications for 
communications within the LRIT system provided by the MSC resolutions. 
The LRIT Data Distribution Plan server should: 
- allow the International LRIT Data Exchange, the LRIT Data Centres and the LRIT 
Coordinator to have access to the current version of the plan. 
- provide earlier versions of the LRIT Data Distribution Plan to the International LRIT 
Data Exchange, the LRIT Data Centres and the LRIT Coordinator upon request. 
- use a standard protocol for communications and agreed protocols to connect with the 
International LRIT Data Exchange and the LRIT Data Centres. 
- use a standard secure transmission method with the International LRIT Data Exchange 
and the LRIT Data Centres. 
- use a standard and expandable message format for communicating with the 
International LRIT Data Exchange and the LRIT Data Centres. 
- use reliable connections (e.g., TCP) to ensure that the information in the plan is 
successfully received by the International LRIT Data Exchange and the LRIT Data 
Centres 
- use industry standard file compression technology to reduce the size of the plan and its 
incremental updates when these are downloaded by the International LRIT Data 
Exchange and the LRIT Data Centres. 
- provide for the submission of the geographical areas in a standard industry format and 
use a consistent naming convention for the elements. 
- provide for uploading of the geographical areas in batch files in Geography Markup 
Language (GML) format.
- maintain a unique number for each published version of the plan, incrementing each 
time a new version of the plan is published. 
- provide for the downloading of the plan and its incremental updates by the LRIT Data 
centers and the International LRIT Data Exchange on the publishing of a new version of 
the plan. 
- archive all published versions of the plan and its incremental updates. 
- use a standard secure access method with the Contracting Governments and the LRIT 
Coordinator. 
- provide a web interface for the entry and amendment of information in the plan. 
f) The International LRIT Data Exchange 
The International LRIT Data Exchange should be connected to all LRIT Data Centres 
and the LRIT Data Distribution Plan server. It should route LRIT information between 
LRIT Data Centers using the information provided in the LRIT Data Distribution Plan. A 
standard secure access method should be used. 
LRIT system performance 
LRIT information should be available to an LRIT Data User within 15 min of the time it 
is transmitted by the ship. On-demand LRIT information should be provided to an LRIT 
Data User within 30 min of the time the LRIT Data User requested the information. 
The quality of service 
= Number of delivered LRIT information meeting latency requirements x 100 % 
Total number of LRIT information requests. 
It should be: 
- 95% of the time over any 24-hour period, and 
- 99% over any 1 month. 
LRIT Compliance 
The LRIT Compliance dates are mentioned in Table-3. 
Table-3 
LRIT COMPLIANCE DATES 
Construction Date Sea Areas Compliance Requirement 
On/After 31 Dec 2008 All Areas Initial Survey 
Before 31 Dec 2008 
A1 (AIS fitted) No to Comply 
A1 (AIS not fitted) 
Not later than the first radio survey after 
31 Dec 2008. 
A1+A2 
A1+A2+A3 
A1+A2+A3+A4 
A1+A2+A3+A4 
(exclusively A4) 
Not later than the first radio survey after 
01 July 2009.
Conformance Test Report 
A Conformance test report should be issued, on satisfactory completion of a conformance 
test, by the Administration or the ASP who conducted the test acting on behalf of the 
Administration.The Conformance test report should be considered as no longer valid if: 
1. There is a change in the ship borne LRIT equipment; 
2. The ship is transferred to the flag of another Contracting Government; 
3. The ASP which has issued the Conformance test report has notified the 
Administration or R.O. that is no longer in a position to attest the validity of the 
report; and 
4. The Administration has withdrawn the recognition or authorization of the ASP 
which conducted the test. 
All vessels should have the conformance test report on board. 
Conformance Test Checklist 
The test requirements, procedures and acceptance criteria for the ship borne equipment is 
given in Table-4
Table-4 
SHIPBORNE EQUIPMENT TEST CRITERIA 
CTN 
SHIPBORNE EQUIPMENT TEST 
Requirement Procedure Acceptance 
EL 1 Equipment activation into ASP system 
ASP issue activation command 
(only for transfer of flag) 
CSP Acknowledgement 
1 
Establish certified sea areas from 
certificates 
(SAFCON,SAFRAD,SAFPAS) 
Verify Administrative document Declaration from Ship Owner 
2 Automatic transmission of LRIT Verify at site Validate from CTN 9 results 
3 
Presence of equipment identity in received 
LRIT information 
Verify at site Validate from CTN 9 results 
4 a Latitude/Longitude present in information Verify at site Validate from CTN 9 results 
4 b GNSS position based on WGS84 datum Verify at site IMO guideline compliance 
5 a Date/Time in received information Verify at site Validate from CTN 9 results 
5 b 
The equipment date and time information 
is in UTC 
Verify at site 
ASP confirm based on message with 
time /date stamp(as per MEM code 11) 
5 c Transmits time stamp relative to position. Verify at site 
ASP confirm based on message with 
time /date stamp(as per MEM code 11) 
6 Type approved Verify Administrative document 
Statement of Conformity by ASP 
followed by certificate of compliance 
with administration. 
7 On board switch off 
ASP outbound Program-Stop 
command 
Nil LRIT information transmitted 
within 90 min 
8 Testing for electromagnetic compatibility 
Verify Administrative document 
(Refer Res.A.694(17),A.813(19)) 
Conformation from 
Manufacturer/technical Specification. 
9 a 
Re-configured to automatically transmit 
LRIT information at 15 min intervals 
ASP issuance of Start-15 min 
reporting command 
Confirm by receipt of 48 consecutive 
15-Min automatic transmission 
9 b 
Re-configured to automatically transmit 
LRIT information at 60 min intervals 
ASP issuance of Start-60 min 
reporting command 
Confirm by receipt of 12 consecutive 
60-Min automatic transmission 
9 c 
Automatically transmit LRIT information 
at 6-h intervals 
Verify Administrative document 
Conformation from Manufacturer / 
ASP/technical Specification. 
9 d 
Re-configured to automatically transmit 
LRIT information at 24-h intervals 
Verify Administrative document 
Conformation from Manufacturer / 
ASP/technical Specification. 
9 e 
Information available within 15 min of 
transmission. 
Comparison of UTC time stamp 
generated with UTC time stamp 
received 
Validate from CTN 9a and 9b results 
10 
ASP issues poll command and receipt of 
information within 30 min 
ASP issuance of a Send-Request 
for Position command 
Confirm receipt of 1 pole transmission 
within 30 min. 
11 
Interface with ship borne global 
navigation satellite / Internal Position 
capability 
Verify Administrative document 
Conformation from Manufacturer / 
ASP/technical Specification of 
GPS./Ship Owner if GPS is external 
12 
Energy from main and emergency power 
source (except for INMARSAT-C) 
Verify Administrative document Declaration from Ship Owner 
13 
Automatic and reliable transmission from 
ASP to CSP 
Verify Administrative document 
Verify with ASP (communication links 
from the terminal - satellite - CSP - 
ASP) 
EL 2 
Deactivated and released from LRIT 
system 
ASP issuance of deactivation 
command 
CSP declaration received
Duration of testing 
Based upon the equipment requirements testing matrix, the test requirements, the 
procedures, the acceptance criteria and the acceptable tolerances detailed in this annex, 
the Table-5 provides information on the estimated duration of the conformance testing: 
Table-4 
SHIPBORNE EQUIPMENT TEST CRITERIA 
CTN Tolerances Maximum Duration 
EL 1 3 attempts separated by a minimum of 15 min 45 min 
1-6 None 0 min 
7 3 attempts separated by a minimum of 15 min 45 min + wait 90 min 
8 None 0 min 
9 a 
3 attempts separated by a minimum of 15 min 
Acceptable results: a minimum of 40 out of 48 
45 min 
720 min (12 h) 
9 b 
3 attempts separated by a minimum of 15 min 
Acceptable results: a minimum of 10 out of 12 
45 min 
720 min (12 h) 
9 c-9 e None 0 min 
10 3 attempts separated by a minimum of 15 min 45 min 
EL 2 3 attempts separated by a minimum of 15 min 45 min 
TOTAL 30 h 
Conclusion 
With the implementation of LRIT, the IMO has taken a giant leap in bringing the entire 
maritime community under one roof. This regulation would help the growth of maritime 
world in a larger extent. By the introduction of such a tracking aid, all the vessels 
operating in the international waters could be tracked easily. Thus the fear of loss of a 
vessel suddenly in the deep waters would be a myth from now onwards, thus giving the 
owners something to cheer at. This paper succeeds at simplifying the Conformance 
testing of the ship borne equipment by preparation of a simplified Checklist (table-4), 
which also has a large scope of improvement in the future. 
Reference 
1. RINA Technical updating Meeting 2008,LRIT.ppt,Genova 12 Dec 2008,pp 1-30. 
2. IMO Resolution MSC.202 (81), LRIT Regulation, 19 May 2006, pp 1-6. 
3. IMO Resolution MSC.211 (81), LRIT Timely Establishment, 19 May 2006, pp 2. 
4. IMO Resolution MSC.263 (84), Revised performance standards and functional 
requirements for the LRIT of Ships, 16 May 2008, pp 3-19. 
5. IMO Circular MSC.1/Circ.1296, Guidance on the survey and certification of 
compliance of ships with the requirement to transmit LRIT information, 8 Dec 
2008, pp 8-18. 
6. IMO Circular MSC.1/Circ.1298, Guidance on implementation of LRIT system, 8 
Dec 2008, pp 2-9.
Nomenclature 
AIS Automatic Identification System 
ASP Application Service Provider 
CSP Communication Service Provider 
CTN Conformance Test Number 
EL Equipment Lifecycle 
GMDSS Global Maritime Distress Safety System 
GNSS Global Navigation Satellite System 
IMO International Maritime Organisation 
MMSI Maritime Mobile Service Identity 
MSC Maritime Safety Committee 
RO Recognised Organisations 
SAFCON Safety Construction 
SAFPAS Safety Passenger 
SAFRAD Safety Radio 
UTC Coordinated Universal Time 
UTF Unicode Transformation Format 
VMS Vessel Monitoring System 
WGS Wideband Global SATCOM

Más contenido relacionado

La actualidad más candente

Imo – the international maritime organization
Imo – the international maritime organizationImo – the international maritime organization
Imo – the international maritime organizationSazzad Zaman Anik
 
International Maritime Organization
International Maritime OrganizationInternational Maritime Organization
International Maritime OrganizationJay Tristan Taryela
 
The four pillars of international maritime law
The four pillars of international maritime lawThe four pillars of international maritime law
The four pillars of international maritime lawVistingFaculty
 
Autonomous ship
Autonomous shipAutonomous ship
Autonomous shipjamaju56
 
Maritime Labour Convention (MLC 2006)
Maritime Labour Convention (MLC 2006)Maritime Labour Convention (MLC 2006)
Maritime Labour Convention (MLC 2006)Yasser B. A. Farag
 
Bridge watchkeeping 2 lrg
Bridge watchkeeping 2 lrg Bridge watchkeeping 2 lrg
Bridge watchkeeping 2 lrg Lance Grindley
 
MARPOL Annex VI: Prevention of Air Pollution from Ships
MARPOL Annex VI: Prevention of Air Pollution from ShipsMARPOL Annex VI: Prevention of Air Pollution from Ships
MARPOL Annex VI: Prevention of Air Pollution from ShipsMohammud Hanif Dewan M.Phil.
 
PPt Presentation on CNS (AAI)
PPt Presentation on CNS (AAI)PPt Presentation on CNS (AAI)
PPt Presentation on CNS (AAI)Abhishek Raj
 
SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...
SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...
SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...Augustine Aling
 
An Introduction to Maritime Search and Rescue
An Introduction to Maritime  Search and RescueAn Introduction to Maritime  Search and Rescue
An Introduction to Maritime Search and RescueVR Marine Technologies
 
Traffic Alert and collision avoidance system (TCAS)
Traffic Alert and collision avoidance system (TCAS)Traffic Alert and collision avoidance system (TCAS)
Traffic Alert and collision avoidance system (TCAS)ARVIND KUMAR SINGH
 
Responsibilities of the oow lrg
Responsibilities of the oow  lrgResponsibilities of the oow  lrg
Responsibilities of the oow lrgLance Grindley
 

La actualidad más candente (20)

Imo – the international maritime organization
Imo – the international maritime organizationImo – the international maritime organization
Imo – the international maritime organization
 
International Maritime Organization
International Maritime OrganizationInternational Maritime Organization
International Maritime Organization
 
The four pillars of international maritime law
The four pillars of international maritime lawThe four pillars of international maritime law
The four pillars of international maritime law
 
Autonomous ship
Autonomous shipAutonomous ship
Autonomous ship
 
Maritime Labour Convention (MLC 2006)
Maritime Labour Convention (MLC 2006)Maritime Labour Convention (MLC 2006)
Maritime Labour Convention (MLC 2006)
 
Bridge watchkeeping 2 lrg
Bridge watchkeeping 2 lrg Bridge watchkeeping 2 lrg
Bridge watchkeeping 2 lrg
 
Marpol annexes
Marpol annexesMarpol annexes
Marpol annexes
 
80920328 vdr
80920328 vdr80920328 vdr
80920328 vdr
 
MARPOL Annex VI: Prevention of Air Pollution from Ships
MARPOL Annex VI: Prevention of Air Pollution from ShipsMARPOL Annex VI: Prevention of Air Pollution from Ships
MARPOL Annex VI: Prevention of Air Pollution from Ships
 
PPt Presentation on CNS (AAI)
PPt Presentation on CNS (AAI)PPt Presentation on CNS (AAI)
PPt Presentation on CNS (AAI)
 
SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...
SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...
SOLAS - Chapter II-2 - Construction - Fire protection, fire detection and fir...
 
Maritime law certificate and documents
Maritime law  certificate and documentsMaritime law  certificate and documents
Maritime law certificate and documents
 
A short note on marpol annex vi
A short note on marpol annex viA short note on marpol annex vi
A short note on marpol annex vi
 
An Introduction to Maritime Search and Rescue
An Introduction to Maritime  Search and RescueAn Introduction to Maritime  Search and Rescue
An Introduction to Maritime Search and Rescue
 
Traffic Alert and collision avoidance system (TCAS)
Traffic Alert and collision avoidance system (TCAS)Traffic Alert and collision avoidance system (TCAS)
Traffic Alert and collision avoidance system (TCAS)
 
Solas assigment
Solas  assigmentSolas  assigment
Solas assigment
 
A short note on SOLAS 74
A short note on SOLAS 74A short note on SOLAS 74
A short note on SOLAS 74
 
Responsibilities of the oow lrg
Responsibilities of the oow  lrgResponsibilities of the oow  lrg
Responsibilities of the oow lrg
 
Blind pilotage lrg
Blind pilotage lrgBlind pilotage lrg
Blind pilotage lrg
 
Loadline
LoadlineLoadline
Loadline
 

Destacado

Lesson 12 Navigational Instruments
Lesson 12 Navigational InstrumentsLesson 12 Navigational Instruments
Lesson 12 Navigational InstrumentsGuilherme Azevedo
 
Soundwaves 100212173149-phpapp02
Soundwaves 100212173149-phpapp02Soundwaves 100212173149-phpapp02
Soundwaves 100212173149-phpapp02Abhinav Yadav
 
Doppler radar project Speed Detector
Doppler radar project Speed DetectorDoppler radar project Speed Detector
Doppler radar project Speed Detectoree_hirzallah
 
14. doppler radar and mti 2014
14. doppler radar and mti 201414. doppler radar and mti 2014
14. doppler radar and mti 2014Lohith Kumar
 
Longitudinal and transverse waves
Longitudinal and transverse wavesLongitudinal and transverse waves
Longitudinal and transverse waveshmsoh
 
Principles of Doppler ultrasound
Principles of Doppler ultrasoundPrinciples of Doppler ultrasound
Principles of Doppler ultrasoundSamir Haffar
 
Basics of echo & principles of doppler echocardiography
Basics of echo & principles of doppler echocardiographyBasics of echo & principles of doppler echocardiography
Basics of echo & principles of doppler echocardiographyabrahahailu
 
Waves ppt.
Waves ppt.Waves ppt.
Waves ppt.hlayala
 
Navgard bnwas presentation
Navgard bnwas presentationNavgard bnwas presentation
Navgard bnwas presentationmartekmarine
 
ILMI Allegheny River Navigation Chart
ILMI Allegheny River Navigation ChartILMI Allegheny River Navigation Chart
ILMI Allegheny River Navigation ChartJon Walker
 
Restricted visibility lrg
Restricted visibility lrgRestricted visibility lrg
Restricted visibility lrgLance Grindley
 
Bridge Navigational Watch Alarm System
Bridge Navigational Watch Alarm SystemBridge Navigational Watch Alarm System
Bridge Navigational Watch Alarm SystemNojh Lrae Red
 

Destacado (20)

Lesson 12 Navigational Instruments
Lesson 12 Navigational InstrumentsLesson 12 Navigational Instruments
Lesson 12 Navigational Instruments
 
Soundwaves 100212173149-phpapp02
Soundwaves 100212173149-phpapp02Soundwaves 100212173149-phpapp02
Soundwaves 100212173149-phpapp02
 
Doppler radar project Speed Detector
Doppler radar project Speed DetectorDoppler radar project Speed Detector
Doppler radar project Speed Detector
 
Doppler
DopplerDoppler
Doppler
 
14. doppler radar and mti 2014
14. doppler radar and mti 201414. doppler radar and mti 2014
14. doppler radar and mti 2014
 
Doppler effect
Doppler effectDoppler effect
Doppler effect
 
Longitudinal and transverse waves
Longitudinal and transverse wavesLongitudinal and transverse waves
Longitudinal and transverse waves
 
Principles of Doppler ultrasound
Principles of Doppler ultrasoundPrinciples of Doppler ultrasound
Principles of Doppler ultrasound
 
Basics of echo & principles of doppler echocardiography
Basics of echo & principles of doppler echocardiographyBasics of echo & principles of doppler echocardiography
Basics of echo & principles of doppler echocardiography
 
Waves ppt.
Waves ppt.Waves ppt.
Waves ppt.
 
radar technology
radar technologyradar technology
radar technology
 
Radar ppt
Radar pptRadar ppt
Radar ppt
 
Pulse Doppler Radar
Pulse Doppler RadarPulse Doppler Radar
Pulse Doppler Radar
 
Navgard bnwas presentation
Navgard bnwas presentationNavgard bnwas presentation
Navgard bnwas presentation
 
Electronic charts lrg
Electronic charts lrgElectronic charts lrg
Electronic charts lrg
 
ILMI Allegheny River Navigation Chart
ILMI Allegheny River Navigation ChartILMI Allegheny River Navigation Chart
ILMI Allegheny River Navigation Chart
 
Visibility lrg
Visibility lrgVisibility lrg
Visibility lrg
 
Restricted visibility lrg
Restricted visibility lrgRestricted visibility lrg
Restricted visibility lrg
 
Bridge Navigational Watch Alarm System
Bridge Navigational Watch Alarm SystemBridge Navigational Watch Alarm System
Bridge Navigational Watch Alarm System
 
Bridge management lrg
Bridge management lrgBridge management lrg
Bridge management lrg
 

Similar a LRIT(Long Range Identification and Tracking)- shipstechnic edition no.25 2009

Automatic-identification system gr1.pptx
Automatic-identification system gr1.pptxAutomatic-identification system gr1.pptx
Automatic-identification system gr1.pptxMarkFrenlyLompot
 
presentations-amp_imo_presentation
presentations-amp_imo_presentationpresentations-amp_imo_presentation
presentations-amp_imo_presentationJeff Douglas
 
REQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESREQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESbutest
 
REQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESREQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESbutest
 
REQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESREQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESbutest
 
O - Transportation Event Data Recorders
O - Transportation Event Data RecordersO - Transportation Event Data Recorders
O - Transportation Event Data RecordersRobert McElroy
 
DRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdf
DRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdfDRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdf
DRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdfAlexanderBaziotis
 
GLONASS and GSM based Vehicle Tracking System
GLONASS and GSM based Vehicle Tracking SystemGLONASS and GSM based Vehicle Tracking System
GLONASS and GSM based Vehicle Tracking SystemIRJET Journal
 
Centralized Fault Management of Docks in Marine Sensor Networks
Centralized Fault Management of Docks in Marine Sensor NetworksCentralized Fault Management of Docks in Marine Sensor Networks
Centralized Fault Management of Docks in Marine Sensor NetworksIOSR Journals
 

Similar a LRIT(Long Range Identification and Tracking)- shipstechnic edition no.25 2009 (20)

Msc.1 circ.1367
Msc.1 circ.1367Msc.1 circ.1367
Msc.1 circ.1367
 
Automatic-identification system gr1.pptx
Automatic-identification system gr1.pptxAutomatic-identification system gr1.pptx
Automatic-identification system gr1.pptx
 
presentations-amp_imo_presentation
presentations-amp_imo_presentationpresentations-amp_imo_presentation
presentations-amp_imo_presentation
 
REQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESREQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURES
 
REQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESREQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURES
 
REQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURESREQUEST FOR PROPOSAL PROCEDURES
REQUEST FOR PROPOSAL PROCEDURES
 
O - Transportation Event Data Recorders
O - Transportation Event Data RecordersO - Transportation Event Data Recorders
O - Transportation Event Data Recorders
 
Ais guide
Ais guideAis guide
Ais guide
 
IFR flight plan equipment.pdf
IFR flight plan equipment.pdfIFR flight plan equipment.pdf
IFR flight plan equipment.pdf
 
DRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdf
DRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdfDRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdf
DRWG17_2019_3_EN-Inmarsat_SafetyNET_Manual-30.09.2018-Clean.pdf
 
75346996 a-is
75346996 a-is75346996 a-is
75346996 a-is
 
Topic for Midterm
Topic for Midterm Topic for Midterm
Topic for Midterm
 
report
reportreport
report
 
69116166 iamsar
69116166 iamsar69116166 iamsar
69116166 iamsar
 
i-ship brochure
i-ship brochurei-ship brochure
i-ship brochure
 
iShip Inlecom Systems
iShip Inlecom SystemsiShip Inlecom Systems
iShip Inlecom Systems
 
GLONASS and GSM based Vehicle Tracking System
GLONASS and GSM based Vehicle Tracking SystemGLONASS and GSM based Vehicle Tracking System
GLONASS and GSM based Vehicle Tracking System
 
ATOC-Duties
ATOC-DutiesATOC-Duties
ATOC-Duties
 
F010133036
F010133036F010133036
F010133036
 
Centralized Fault Management of Docks in Marine Sensor Networks
Centralized Fault Management of Docks in Marine Sensor NetworksCentralized Fault Management of Docks in Marine Sensor Networks
Centralized Fault Management of Docks in Marine Sensor Networks
 

Último

Breaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path MountBreaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path MountPuma Security, LLC
 
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure serviceWhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure servicePooja Nehwal
 
Google AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAGGoogle AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAGSujit Pal
 
SQL Database Design For Developers at php[tek] 2024
SQL Database Design For Developers at php[tek] 2024SQL Database Design For Developers at php[tek] 2024
SQL Database Design For Developers at php[tek] 2024Scott Keck-Warren
 
Slack Application Development 101 Slides
Slack Application Development 101 SlidesSlack Application Development 101 Slides
Slack Application Development 101 Slidespraypatel2
 
IAC 2024 - IA Fast Track to Search Focused AI Solutions
IAC 2024 - IA Fast Track to Search Focused AI SolutionsIAC 2024 - IA Fast Track to Search Focused AI Solutions
IAC 2024 - IA Fast Track to Search Focused AI SolutionsEnterprise Knowledge
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerThousandEyes
 
Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024The Digital Insurer
 
Scaling API-first – The story of a global engineering organization
Scaling API-first – The story of a global engineering organizationScaling API-first – The story of a global engineering organization
Scaling API-first – The story of a global engineering organizationRadu Cotescu
 
Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 365
Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 365Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 365
Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 3652toLead Limited
 
Handwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed textsHandwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed textsMaria Levchenko
 
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdfThe Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdfEnterprise Knowledge
 
Data Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonData Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonAnna Loughnan Colquhoun
 
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Drew Madelung
 
A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)Gabriella Davis
 
CNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of ServiceCNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of Servicegiselly40
 
04-2024-HHUG-Sales-and-Marketing-Alignment.pptx
04-2024-HHUG-Sales-and-Marketing-Alignment.pptx04-2024-HHUG-Sales-and-Marketing-Alignment.pptx
04-2024-HHUG-Sales-and-Marketing-Alignment.pptxHampshireHUG
 
A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024Results
 
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...shyamraj55
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Miguel Araújo
 

Último (20)

Breaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path MountBreaking the Kubernetes Kill Chain: Host Path Mount
Breaking the Kubernetes Kill Chain: Host Path Mount
 
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure serviceWhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
WhatsApp 9892124323 ✓Call Girls In Kalyan ( Mumbai ) secure service
 
Google AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAGGoogle AI Hackathon: LLM based Evaluator for RAG
Google AI Hackathon: LLM based Evaluator for RAG
 
SQL Database Design For Developers at php[tek] 2024
SQL Database Design For Developers at php[tek] 2024SQL Database Design For Developers at php[tek] 2024
SQL Database Design For Developers at php[tek] 2024
 
Slack Application Development 101 Slides
Slack Application Development 101 SlidesSlack Application Development 101 Slides
Slack Application Development 101 Slides
 
IAC 2024 - IA Fast Track to Search Focused AI Solutions
IAC 2024 - IA Fast Track to Search Focused AI SolutionsIAC 2024 - IA Fast Track to Search Focused AI Solutions
IAC 2024 - IA Fast Track to Search Focused AI Solutions
 
How to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected WorkerHow to Troubleshoot Apps for the Modern Connected Worker
How to Troubleshoot Apps for the Modern Connected Worker
 
Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024Finology Group – Insurtech Innovation Award 2024
Finology Group – Insurtech Innovation Award 2024
 
Scaling API-first – The story of a global engineering organization
Scaling API-first – The story of a global engineering organizationScaling API-first – The story of a global engineering organization
Scaling API-first – The story of a global engineering organization
 
Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 365
Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 365Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 365
Tech-Forward - Achieving Business Readiness For Copilot in Microsoft 365
 
Handwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed textsHandwritten Text Recognition for manuscripts and early printed texts
Handwritten Text Recognition for manuscripts and early printed texts
 
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdfThe Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
The Role of Taxonomy and Ontology in Semantic Layers - Heather Hedden.pdf
 
Data Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonData Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt Robison
 
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
 
A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)
 
CNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of ServiceCNv6 Instructor Chapter 6 Quality of Service
CNv6 Instructor Chapter 6 Quality of Service
 
04-2024-HHUG-Sales-and-Marketing-Alignment.pptx
04-2024-HHUG-Sales-and-Marketing-Alignment.pptx04-2024-HHUG-Sales-and-Marketing-Alignment.pptx
04-2024-HHUG-Sales-and-Marketing-Alignment.pptx
 
A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024A Call to Action for Generative AI in 2024
A Call to Action for Generative AI in 2024
 
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
 

LRIT(Long Range Identification and Tracking)- shipstechnic edition no.25 2009

  • 1. LRIT (Long Range Identification and Tracking) ANOOP.R.NAIR, Registro Italiano Navale Abstract Since long time some global system to link all the maritime data regarding the vessels in operation was a need. Finally IMO has come up with the implementation of such a system onboard vessels which would help the identification, tracking and also sharing the information of ships. This article is intended to give an insight into the new regulation by the IMO regarding the introduction of LRIT as new navigational equipment on board ships as per SOLAS Reg.V/19-1. Regulation V/19-1.4.1 specifies that ships constructed on or after 31 December 2008 shall transmit LRIT information as from the date they enter service and for ships constructed before 31 December 2008 provides a phased-in implementation schedule which is dependant, inter alia, on the date on which the first survey of the radio installation of the ship becomes due after 31 December 2008 and in the case of ships which operate exclusively in sea area A4 after 1 July 2009.This paper deals with the architecture of LRIT and also with the conformance testing of the shipboard equipment. This paper deals mainly with the parameters to be taken care of in a surveyors’ perspective. This paper also contains a Conformance test Checklist for the testing of the shipborne equipment which was prepared on the basis of MSC Circulars and IMO regulations. Introduction On 19 May 2006 the International Maritime Organization adopted resolution MSC.202(81) which required the establishment of an international system for the Long range Identification and Tracking of ships (LRIT). This resolution amends chapter V of the International Convention for the Safety of Life at Sea (SOLAS), regulation 19-1 and binds all governments which have contracted to the IMO. The regulation applies to ships engaged on international voyages, especially for all passenger ships including high speed crafts, cargo ships of 300 gross tonnage and above and Mobile Offshore Drilling Units. All vessels of 300 gross tonnage and above on international voyage will need to be compliant with LRIT regulations. Compliance to LRIT is important. Some Governments have indicated that they may not grant entry to their territorial waters, or to their ports, for vessels that do not comply with LRIT. The regulation entered into force on 1 January 2008 and is applicable to ships constructed on or after 31 December 2008 with a phased-in implementation schedule for ships constructed before 31 December 2008. LRIT is intended too be operational with respect to the transmission of LRIT information by ships as from 31 December 2008. There is an exemption for ships operating exclusively in sea area A1 from the requirement to transmit LRIT information, since such ships are already fitted with AIS. It also identifies which authorities may have access to LRIT information. These ships must automatically report their position to their Flag Administration at least 4 times a day. Other contracting governments may request information about vessels in which they have a legitimate interest under the regulation. Overview of LRIT The Long-Range Identification and Tracking (LRIT) system provides for the global identification and tracking of ships. The LRIT system consists of
  • 2. a) The shipborne LRIT information transmitting equipment, b) The Communication Service Provider(s), c) The Application Service Provider(s), d) The LRIT Data Centre(s), including any related Vessel Monitoring System(s), e) The LRIT Data Distribution Plan and f) The International LRIT Data Exchange. Certain aspects of the performance of the LRIT system are reviewed or audited by an LRIT Coordinator acting on behalf of all Contracting Governments. Figure 1 provides an illustration of the LRIT system architecture. Figure-1 LRIT information is provided to Contracting Governments and Search and rescue services entitled to receive the information, upon request, through a system of National, Regional, Cooperative and International LRIT Data Centres, using where necessary, the International LRIT Data Exchange. Each Administration should provide to the LRIT Data Centre it has selected, a list of the ships entitled to fly its flag, which are required to transmit LRIT information, together with other salient details and should update, without
  • 3. undue delay, such lists as and when changes occur. Ships should only transmit the LRIT information to the LRIT Data Centre selected by their Administration a) The shipborne LRIT information transmitting equipment The shipborne radio equipment shall be a part of the global maritime distress and safety system (GMDSS) and for electronic navigational aids. The various requirements include. 1) Be capable of automatically and without human intervention on board the ship transmitting the ship’s LRIT information at 6-hour intervals to an LRIT Data Centre 2) Be capable of being configured remotely to transmit LRIT information at variable intervals 3) Be capable of transmitting LRIT information following receipt of polling commands 4) Interface directly to the shipborne global navigation satellite system equipment, or have internal positioning capability 5) Be supplied with energy from the main and emergency source of electrical power 6) Be tested for electromagnetic compatibility taking into account the recommendations developed by the organization 7) To be type approved by the administration. Table-1 provides the functional requirements of a ship borne equipment. Table-1 DATA TO BE TRANSMITTED FROM THE SHIPBORNE EQUIPMENT Parameter Comments Shipborne equipment Identifier The identifier used by the shipborne equipment Positional data The Global Navigation Satellite System (GNSS) position (latitude and longitude) of the ship (based on the WGS 84 datum). Position: The equipment should be capable of transmitting the GNSS position(latitude and longitude) of the ship (based on WGS 84 datum) as prescribed by regulation V/19-1, without human interaction on board the ship. On-demand(1) position reports: The equipment should be capable of responding to a request to transmit LRIT information on demand without human interaction on board the ship, irrespective of where the ship is located. Pre-scheduled(2) position reports: The equipment should be capable of being remotely configured to transmit LRIT information at intervals ranging from a minimum of 15 min to periods of 6 h to the LRIT Data Centre, irrespective of where the ship is located and without human interaction on board the ship. Time Stamp 1 The date and time(3) associated with the GNSS position. The equipment should be capable of transmitting the time(3) associated with the GNSS position with each transmission of LRIT information. Notes (1) On-demand position reports means transmission of LRIT information as a result of either receipt of polling command or of remote configuration of the equipment so as to transmit at interval other than the preset ones. (2) Pre-scheduled position reports means transmission of LRIT information at the preset transmit intervals. (3) All times should be indicated as Universal Coordinated Time (UTC).
  • 4. The shipborne equipment should transmit the LRIT information using a communication system which provides coverage in all areas where the ship operates. The shipborne equipment should be set to automatically transmit the ship’s LRIT information at 6-hour intervals to the LRIT Data Centre identified by the Administration, unless the LRIT Data User requesting the provision of LRIT information specifies a more frequent transmission interval. When a ship is undergoing repairs, modifications or conversions in dry-dock or in port or is laid up for a long period, the master or the Administration may reduce the frequency of the transmission LRIT information to one transmission every 24-hour period, or may temporarily stop the transmission of such information.Figure-2 below shows a sample Shipboard equipment manufactured by Blue tracker. Fig-2 Shipborne Equipment b) The Communication Service Provider(s) Communications Service Providers (CSPs) provide services which link the various parts of the LRIT system using communications protocols in order to ensure the end-to-end secure transfer of the LRIT information. This requirement precludes the use of non-secure broadcast systems. A CSP may also provide services as an ASP. c) The Application Service Provider(s) ASP s providing data to the National, regional or co-operative LRIT data centre should be recognised by the Contracting Government and to an International LRIT Data Centre should be recognized by the Committee. An ASP should provide a communication protocol interface between the Communication Service Providers and the LRIT Data Centre to enable the remote integration of the ship borne equipment into an LRIT Data Centre, automatic configuration of transmission of LRIT information, automatic modification of the interval of transmission of LRIT information, automatic suspension
  • 5. of transmission of LRIT information, on demand transmission of LRIT information and automatic recovery and management of transmission of LRIT information. They should ensure that LRIT information is collected, stored and routed in a reliable and secure manner. The ASP where used should add the data identified in Table-2 to each transmission of LRIT information: Table-2 DATA TO BE ADDED BY AN APPLICATION SERVICE PROVIDER AND AT THE LRIT DATA CENTRE Parameters Comments Ship Identity The IMO ship identification number and MMSI for the ship. Name of ship Name of the ship which has transmitted the LRIT information in the English language using latin-1 alphabet and UTF-8 encoding. Time Stamp 2 The date and time the transmission of LRIT information is received by the ASP (if used). Time Stamp 3 The date and time the received LRIT information is forwarded from the ASP (if used) to the appropriate LRIT Data Centre. LRIT Data Centre The identity of the LRIT Data Centre to be clearly indicated by a Unique Identifier Identifier. Time Stamp 4 The date and time the LRIT information is received by the LRIT Data Centre. Time Stamp 5 The date and time the transmission of LRIT information is forwarded from the LRIT Data Centre to an LRIT Data User. d) The LRIT data centre (s) They collect LRIT information from ships instructed by their Administrations to transmit the LRIT information to the centre. maintain a record of the ships which transmit LRIT information to the centre including name of ship, IMO Ship identification number, call sign and Maritime Mobile Service Identity (MMSI). The response delay should be a) for LRIT information archived within the last 4 days, send the LRIT information within 30 min of receiving a request. b) for LRIT information archived between 4 and 30 days previously, send the LRIT information within 1 h of receiving a request. c) for LRIT information archived more than 30 days previously, send the LRIT information within 5 days of receiving a request. A Contracting Government may establish a National LRIT Data Centre. A Contracting Government establishing such a centre should provide relevant details to the Organization and there after should, without undue delay, update the information provided as and when changes occur. A group of Contracting Governments may establish either a Regional or a Cooperative LRIT Data Centre. The arrangements for establishing such a centre should be agreed amongst the Contracting Governments concerned. One of the Contracting Governments establishing such a centre should provide relevant details to the Organization and thereafter should, without undue delay, update the information provided as and when changes occur. Upon request, National, Regional and Cooperative LRIT Data Centres may provide services to Contracting Governments other than those establishing the centre.
  • 6. National, Regional and Cooperative LRIT Data Centres may also serve as a National, Regional or Cooperative Vessel Monitoring System (VMS) and may require, as VMS, the transmission from ships of additional information, or of information at different intervals, or of information from ships which are not required to transmit LRIT information. VMS s may also perform other functions. If a National, Regional or Cooperative LRIT Data Centre collects additional information from ships, it should transmit only the required LRIT information to the other LRIT Data Centres through the International LRIT Data Exchange. An International LRIT Data Centre recognized by the Committee should be established. Contracting Governments not participating in a National, Regional or Cooperative LRIT Data Centre, or Contracting Governments having an interest in the establishment of an International LRIT Data Centre should cooperate, under the coordination of the Committee, with a view to ensuring its establishment. e) The LRIT Data Distribution Plan The LRIT Data Distribution Plan should include a list indicating the unique LRIT identities of Contracting Governments, Search and rescue services entitled to receive LRIT information, LRIT Data Centres, the International LRIT Data Exchange, ASPs, the LRIT Data Distribution Plan server and the LRIT Coordinator. The LRIT Data Distribution Plan server should comply with the Technical specifications for LRIT Data Distribution Plan and with the relevant provisions of the Technical specifications for communications within the LRIT system provided by the MSC resolutions. The LRIT Data Distribution Plan server should: - allow the International LRIT Data Exchange, the LRIT Data Centres and the LRIT Coordinator to have access to the current version of the plan. - provide earlier versions of the LRIT Data Distribution Plan to the International LRIT Data Exchange, the LRIT Data Centres and the LRIT Coordinator upon request. - use a standard protocol for communications and agreed protocols to connect with the International LRIT Data Exchange and the LRIT Data Centres. - use a standard secure transmission method with the International LRIT Data Exchange and the LRIT Data Centres. - use a standard and expandable message format for communicating with the International LRIT Data Exchange and the LRIT Data Centres. - use reliable connections (e.g., TCP) to ensure that the information in the plan is successfully received by the International LRIT Data Exchange and the LRIT Data Centres - use industry standard file compression technology to reduce the size of the plan and its incremental updates when these are downloaded by the International LRIT Data Exchange and the LRIT Data Centres. - provide for the submission of the geographical areas in a standard industry format and use a consistent naming convention for the elements. - provide for uploading of the geographical areas in batch files in Geography Markup Language (GML) format.
  • 7. - maintain a unique number for each published version of the plan, incrementing each time a new version of the plan is published. - provide for the downloading of the plan and its incremental updates by the LRIT Data centers and the International LRIT Data Exchange on the publishing of a new version of the plan. - archive all published versions of the plan and its incremental updates. - use a standard secure access method with the Contracting Governments and the LRIT Coordinator. - provide a web interface for the entry and amendment of information in the plan. f) The International LRIT Data Exchange The International LRIT Data Exchange should be connected to all LRIT Data Centres and the LRIT Data Distribution Plan server. It should route LRIT information between LRIT Data Centers using the information provided in the LRIT Data Distribution Plan. A standard secure access method should be used. LRIT system performance LRIT information should be available to an LRIT Data User within 15 min of the time it is transmitted by the ship. On-demand LRIT information should be provided to an LRIT Data User within 30 min of the time the LRIT Data User requested the information. The quality of service = Number of delivered LRIT information meeting latency requirements x 100 % Total number of LRIT information requests. It should be: - 95% of the time over any 24-hour period, and - 99% over any 1 month. LRIT Compliance The LRIT Compliance dates are mentioned in Table-3. Table-3 LRIT COMPLIANCE DATES Construction Date Sea Areas Compliance Requirement On/After 31 Dec 2008 All Areas Initial Survey Before 31 Dec 2008 A1 (AIS fitted) No to Comply A1 (AIS not fitted) Not later than the first radio survey after 31 Dec 2008. A1+A2 A1+A2+A3 A1+A2+A3+A4 A1+A2+A3+A4 (exclusively A4) Not later than the first radio survey after 01 July 2009.
  • 8. Conformance Test Report A Conformance test report should be issued, on satisfactory completion of a conformance test, by the Administration or the ASP who conducted the test acting on behalf of the Administration.The Conformance test report should be considered as no longer valid if: 1. There is a change in the ship borne LRIT equipment; 2. The ship is transferred to the flag of another Contracting Government; 3. The ASP which has issued the Conformance test report has notified the Administration or R.O. that is no longer in a position to attest the validity of the report; and 4. The Administration has withdrawn the recognition or authorization of the ASP which conducted the test. All vessels should have the conformance test report on board. Conformance Test Checklist The test requirements, procedures and acceptance criteria for the ship borne equipment is given in Table-4
  • 9. Table-4 SHIPBORNE EQUIPMENT TEST CRITERIA CTN SHIPBORNE EQUIPMENT TEST Requirement Procedure Acceptance EL 1 Equipment activation into ASP system ASP issue activation command (only for transfer of flag) CSP Acknowledgement 1 Establish certified sea areas from certificates (SAFCON,SAFRAD,SAFPAS) Verify Administrative document Declaration from Ship Owner 2 Automatic transmission of LRIT Verify at site Validate from CTN 9 results 3 Presence of equipment identity in received LRIT information Verify at site Validate from CTN 9 results 4 a Latitude/Longitude present in information Verify at site Validate from CTN 9 results 4 b GNSS position based on WGS84 datum Verify at site IMO guideline compliance 5 a Date/Time in received information Verify at site Validate from CTN 9 results 5 b The equipment date and time information is in UTC Verify at site ASP confirm based on message with time /date stamp(as per MEM code 11) 5 c Transmits time stamp relative to position. Verify at site ASP confirm based on message with time /date stamp(as per MEM code 11) 6 Type approved Verify Administrative document Statement of Conformity by ASP followed by certificate of compliance with administration. 7 On board switch off ASP outbound Program-Stop command Nil LRIT information transmitted within 90 min 8 Testing for electromagnetic compatibility Verify Administrative document (Refer Res.A.694(17),A.813(19)) Conformation from Manufacturer/technical Specification. 9 a Re-configured to automatically transmit LRIT information at 15 min intervals ASP issuance of Start-15 min reporting command Confirm by receipt of 48 consecutive 15-Min automatic transmission 9 b Re-configured to automatically transmit LRIT information at 60 min intervals ASP issuance of Start-60 min reporting command Confirm by receipt of 12 consecutive 60-Min automatic transmission 9 c Automatically transmit LRIT information at 6-h intervals Verify Administrative document Conformation from Manufacturer / ASP/technical Specification. 9 d Re-configured to automatically transmit LRIT information at 24-h intervals Verify Administrative document Conformation from Manufacturer / ASP/technical Specification. 9 e Information available within 15 min of transmission. Comparison of UTC time stamp generated with UTC time stamp received Validate from CTN 9a and 9b results 10 ASP issues poll command and receipt of information within 30 min ASP issuance of a Send-Request for Position command Confirm receipt of 1 pole transmission within 30 min. 11 Interface with ship borne global navigation satellite / Internal Position capability Verify Administrative document Conformation from Manufacturer / ASP/technical Specification of GPS./Ship Owner if GPS is external 12 Energy from main and emergency power source (except for INMARSAT-C) Verify Administrative document Declaration from Ship Owner 13 Automatic and reliable transmission from ASP to CSP Verify Administrative document Verify with ASP (communication links from the terminal - satellite - CSP - ASP) EL 2 Deactivated and released from LRIT system ASP issuance of deactivation command CSP declaration received
  • 10. Duration of testing Based upon the equipment requirements testing matrix, the test requirements, the procedures, the acceptance criteria and the acceptable tolerances detailed in this annex, the Table-5 provides information on the estimated duration of the conformance testing: Table-4 SHIPBORNE EQUIPMENT TEST CRITERIA CTN Tolerances Maximum Duration EL 1 3 attempts separated by a minimum of 15 min 45 min 1-6 None 0 min 7 3 attempts separated by a minimum of 15 min 45 min + wait 90 min 8 None 0 min 9 a 3 attempts separated by a minimum of 15 min Acceptable results: a minimum of 40 out of 48 45 min 720 min (12 h) 9 b 3 attempts separated by a minimum of 15 min Acceptable results: a minimum of 10 out of 12 45 min 720 min (12 h) 9 c-9 e None 0 min 10 3 attempts separated by a minimum of 15 min 45 min EL 2 3 attempts separated by a minimum of 15 min 45 min TOTAL 30 h Conclusion With the implementation of LRIT, the IMO has taken a giant leap in bringing the entire maritime community under one roof. This regulation would help the growth of maritime world in a larger extent. By the introduction of such a tracking aid, all the vessels operating in the international waters could be tracked easily. Thus the fear of loss of a vessel suddenly in the deep waters would be a myth from now onwards, thus giving the owners something to cheer at. This paper succeeds at simplifying the Conformance testing of the ship borne equipment by preparation of a simplified Checklist (table-4), which also has a large scope of improvement in the future. Reference 1. RINA Technical updating Meeting 2008,LRIT.ppt,Genova 12 Dec 2008,pp 1-30. 2. IMO Resolution MSC.202 (81), LRIT Regulation, 19 May 2006, pp 1-6. 3. IMO Resolution MSC.211 (81), LRIT Timely Establishment, 19 May 2006, pp 2. 4. IMO Resolution MSC.263 (84), Revised performance standards and functional requirements for the LRIT of Ships, 16 May 2008, pp 3-19. 5. IMO Circular MSC.1/Circ.1296, Guidance on the survey and certification of compliance of ships with the requirement to transmit LRIT information, 8 Dec 2008, pp 8-18. 6. IMO Circular MSC.1/Circ.1298, Guidance on implementation of LRIT system, 8 Dec 2008, pp 2-9.
  • 11. Nomenclature AIS Automatic Identification System ASP Application Service Provider CSP Communication Service Provider CTN Conformance Test Number EL Equipment Lifecycle GMDSS Global Maritime Distress Safety System GNSS Global Navigation Satellite System IMO International Maritime Organisation MMSI Maritime Mobile Service Identity MSC Maritime Safety Committee RO Recognised Organisations SAFCON Safety Construction SAFPAS Safety Passenger SAFRAD Safety Radio UTC Coordinated Universal Time UTF Unicode Transformation Format VMS Vessel Monitoring System WGS Wideband Global SATCOM