Long Range Identification &

Tracking (LRIT)
What is LRIT?
The LRIT system provides for global identification and tracking of ships utilizing the
INMARSAT Satellite system. It is a system that requires vessels to automatically
transmit their identity, position and date/time of the position at 6-hourly intervals.

LRIT Regulations
• SOLAS Chapter V, Regulation 19-1 on LRIT requires that vessels automatically
transmit their identity, position and date/time of the position at 6-hourly
intervals. The LRIT system is designed in such a way as to limit direct cost to
shipping or search and rescue services with Member States bearing the cost
of the system.
• The Regulation applies to ships engaged on international voyages, including
1. all passenger ships including high speed craft
2. cargo ships, including high speed craft of 300 gross tonnage and above
3. mobile offshore drilling units.
• Compliance with the LRIT requirement is important. Some governments
have indicated that they may not grant entry to their waters or ports, for
vessels that do not comply with LRIT requirement.
• Ships operating exclusively in Sea Area A1 and fitted with AIS are exempt
from LRIT requirements. Coastal trade vessels are also exempt but if they
proceed to an international port for any reason [e.g., dry-dock] they
must fully comply or receive exemption for that voyage.
• Ships operating in sea area A2 and not fitted with Sat-C are required to have
a dedicated LRIT terminal.
• Ships operating in sea area A4 will require a dedicated LRIT terminal that
operates in conjunction with an approved low-earth orbiting satellite
communication service provider.
PURPOSE OF LRIT:
1. To allow Member States to receive position reports from vessels operating
under their flag.
2. To allow Member States to receive position reports from vessels seeking entry
to a port within their territory
3. To allow Member States to receive position reports from vessels operating in
proximity to the State’s coastline.

There are two aspects to LRIT:

• The ‘reporting’ aspect where vessels to which LRIT applies, report their
identity and position, with a date/time stamp, every six hours (four times per
day).

• The ‘receiving’ aspect where coastal states can purchase reports when
vessels are within 1000 NM, or port states can purchase reports when
vessels seeking entry to a port at a pre-determined distance or time from
that port (usually up to 96-hour pre-entry).

In simple terms, LRIT is a collection and distribution system for basic information on
vessels.

MODES OF OPERATION:
The LRIT system operates in two modes.
1. APR mode: Ship LRIT equipment must be capable of transmitting at 6H
intervals, information set in an Automatic Position Report (APR), which
includes:
• identity of the ship
• position of the ship
• date and time of the position report

2. Polled Mode: This involves a request and response processes. The

equipment must be able to respond to poll requests for an on-demand
position report and be able to immediately respond to instructions to modify
the APR interval to a frequency of a maximum of one every 15 minutes.
LRIT Conformance Test:

• The equipment requirement may be met through existing GMDSS

equipment, or other compliant equipment.
• The system must be tested and a conformance certificate issued and held on
board.
• The system must have an emergency power source.
• The LRIT conformance test certificate has no expiration date as long as the
equipment remains the same. However if the status is changed a retest may
be required due to the following reasons:
1. Ship changes or upgrades the LRIT equipment (Antenna, Motherboard,
etc.)
2. The vessels changes Flag.
• IMO has appointed the International Mobile Satellite Organisation (IMSO) as
LRIT Coordinator, who will undertake the audit and oversight functions.

COMPONENTS OF THE LRIT SYSTEM:

The LRIT system consists of

1. Shipborne LRIT information transmitting equipment: Sends APR’s, receives

poll requests and updates the APR frequency accordingly.

2. Communication Service Provider (CSP): It provides the communication

infrastructure and services to ensure end-to-end secure transfer of the LRIT
message (APR) between the ship and the Application Service Provider (ASP)

3. Application Service Provider (ASP): It converts the data to a common data

format and sends it to the LRIT data centre.

4. LRIT Data Center: It stores and processes the data and determines which
reports are to be sent to other coastal/port states via the International Data
Exchange based on the data distribution plan. Member states can deploy
one of the three styles:

• National Data Center: to service their own flagged vessels only.

 • Regional/Cooperative Data Center: to service two or more member
state’s flagged vessels.
• International Data Center: to service vessels of those Member States that
are not using any of the above two.

Also, Vessel Monitoring System [VMS] – providing tracking and data centre
services.

5. LRIT Data Distribution Plan (DDP): It verifies that the Member State
requesting information must be provided with the same or not. It specifies
which are the parties authorised to receive LRIT data.

6. International LRIT Data Exchange (IDE): It routes data to the authorised

receiving parties.

LRIT information is provided to Contracting Governments and SAR services entitled

to receive the information, upon request, through a system of National,
Regional/Cooperative & International LRIT Data Centres using the International
LRIT Data Exchange.

Each Administration should provide to the LRIT Data Centre it has selected, a list of
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.

WORKING OF LRIT:
LRIT data is automatically transmitted every 6 hours through the following route:

1. Ship to Satellite
2. Satellite to CSP
3. CSP to ASP
4. ASP to LRIT Data Center.
5. The LRIT Data Center forwards this information to applicable parties via the
International Data Exchange and after receiving feedback from DDP.
• Information transmitted by ships through APR is available to the vessel’s Flag
State at all times. For another Flag State to access the information, they will
send a request to the IDE.
• Linked to IDE is the Data Distribution Plan (DDP) that will have the ‘routing
rules’ and this will verify that the ‘requestor’ can access the information.
• Each contracting government will provide these routing rules to the IMO, who
have developed the DDP.
• The DDP ensures that LRIT data flows according to the wishes of a contracting
government – i.e. providing information on vessels within 1,000 nautical miles,
or 96 hours out from port.
• If the DPP verifies that the information request is valid, the IDE will then act as a
link to the requesting data centre and the providing data centre.

ACCESS TO LRIT INFORMATION:

• Flag State: Full access to all ships under their flag.
• Coastal State: Access to enhanced LRIT information & reports. Coastal state
can poll and track ships upto 1000nm from their coast, but not if the vessel is
in territorial waters of another State.
• Port state: Access to enhanced LRIT information & reports. Port state can
poll & track ships at any distance following a notice-of-port-call (usually up to
96H pre-entry), but not if the vessel is in territorial waters of another State.
• Shipowner: Access restricted to own ships.
• Surveyors: Restricted access to verify LRIT conformance tests.
• Agents and charterers: Selective access if granted by shipowner.
• Piracy prevention task forces – access via a special format.
• SAR services – Authorised SAR services may request and receive LRIT data
for vessels within their SAR area, without any cost. However, the cost for
communication and data transfer will be borne by Flag of the vessel from
which the data was requested.
• International Data Exchange: Full access to all data so that it can distribute
as required.
NOTE:
• Communications Service Provider [CSP] for India is TATA Communications
• Applications Service Provider [ASP] for India is at the National Data Centre
[NDC] at DG Shipping [developed by Antrix/SAC]
• LRIT Data Centre [LDC or DC] for India is the National Data Centre [NDC] at
DG Shipping

AIS V/S. LRIT

AIS LRIT
AIS operates in the VHF band with line LRIT is a Satellite based system and has
of sight transmission and has therefore "global" coverage.
"local” coverage only.

In the case of long range AIS (Satellite LRIT permits bi-directional

based), the satellite system is uni- communication and authorised
directional and can only receive data but requesting authority can poll and
cannot send data or instructions to the instruct the ships system to change its
ships AIS. APR frequency, increasing it to upto
every 15 minutes.

AIS is a continuously on system, LRIT is a continuously on system,

updating its Static, Dynamic, Voyage normally broadcasting an APR only once
data at intervals of a few seconds. every 6 hours.

AIS is a broadcast system, i.e. public, LRIT data is only available to parties that
available to all ships, nearby VTS or are entitled to the information as per
coast AIS stations. The information is the DDP and information must be
free of cost to all. purchased. (except own flag and SAR
services)

AIS is primarily a collision avoidance LRIT is a reporting System that assists

system mandated by the IMO and is of concerned parties like Flag State,
great use to nearby vessels and VTS Coastal State, Port State and SAR
systems. authorities in identifying and tracking
their own vessels as well as vessels
entering or plying within their waters.
AIS provides navigational information of LRIT provides only vessels identity,
a vessel as well as data regarding the position and date/time information.
type of vessel, her dimensions, draft,
cargo, destination, etc in four msg forms
- Static, Dynamic, Voyage-related and
Safety related.

In AIS, other than Static data, the user In LRIT there is no user intervention.
must manually update Dynamic (nav.
status), Voyage and Safety related data.

There is display onboard for AIS There is no display for LRIT.

AIS data is not stored anywhere. LRIT data is stored and available on
demand.

SWITCHING OFF LRIT:

Systems and equipment used to meet the LRIT requirements shall be capable of
being switched off on board or be capable of ceasing the distribution of LRIT
information:

1. where international agreements, rules or standards provide for the

protection of navigational information; or
2. in exceptional circumstances and for the shortest duration possible where
the operation is considered by the master to compromise the safety or
security of the ship.

In such a case, the master shall inform the Administration without undue delay and
make an entry in the Log Book setting out the reasons for the decision and
indicating the period during which the system or equipment was switched off.
PERFORMANCE STANDARDS & FUNCTIONAL REQUIREMENTS FOR LRIT:
RESOLUTION MSC.263(84) (adopted on 16 May 2008) as amended by RESOLUTION
MSC.331(90) (adopted on 25 May 2012) and as amended by RESOLUTION MSC.400(95)
(Adopted on 8 June 2015)

1. Shipborne equipment

The shipborne LRIT equipment should comply with the following minimum
requirements:

• 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;
• be capable of being configured remotely to transmit LRIT information at
variable intervals;
• be capable of transmitting LRIT information following receipt of polling
commands;
• interface directly to shipborne GNSS equipment, or have internal positioning
capability.
• be supplied with energy from the main and emergency source of electrical
power
• be tested for electromagnetic compatibility.

2. Data To Be Transmitted From The Shipborne Equipment

• Identity - The identifier used by the shipborne equipment.

• Position - The GNSS position (latitude & longitude) of the ship (based on
WGS84 datum).
• Time Stamp -The date and time associated with the GNSS position. (all time
in UTC)

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.
3. Data to be added by the ASP & at the LRIT Data Center:

• Ship Identity: The IMO number, MMSI and Name of ship and type of the ship
using pre-defined codes.
• Time Stamp: Date and time the transmission of LRIT information is received
by the ASP (if used). Also, the date and time the received LRIT information is
forwarded from the ASP (if used) to the appropriate LRIT Data Centre.
• LRIT Data Centre Identifier: The identity of the LRIT Data Centre to be clearly
indicated by a Unique Identifier.
• Time Stamp: The date and time the LRIT information is received by the LRIT
Data Centre. Also, the date and time the transmission of LRIT information is
forwarded from the LRIT Data Centre to an LRIT Data User.

4. Communications Service Providers (CSP)

CSP’s 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. It prevents the use of non-secure broadcast systems. A CSP may
also provide services as an ASP.

5. LRIT Data Centre

All LRIT Data Centres should:

• Establish and continuously maintain systems which ensure, at all times, that
LRIT Data Users are only provided with the LRIT information they are
entitled to receive.
• Collect LRIT information from concerned ships for the Administration
• Obtain, when requested, LRIT information from other LRIT Data Centres
through the International LRIT Data Exchange
• make available, when requested, LRIT information to other LRIT Data
Centres through the International LRIT Data Exchange
• Execute or relay requests for polling of LRIT information or for change
transmission frequency, through the IDE as applicable.
• Upon request disseminate to LRIT Data Users the LRIT information they are
entitled to receive in accordance with the agreed arrangements.
 • Notify the LRIT Data User and the Administration when a particular ship
stops transmitting LRIT information.
• Archive LRIT information from ships which, for at least one year and in such a
way that the archived LRIT information should provide a complete record
between two consecutive annual audits of its performance.
• For LRIT information archived within the last 4 days, send the LRIT
information within 30 min of receiving a request
• For LRIT information archived between 4 and 30 days previously, send the
LRIT information within 1 h of receiving a request
• For LRIT information archived more than 30 days previously, send the LRIT
information within 5 days of receiving a request.
• Ensure that LRIT information is backed-up at regular intervals, stored at
suitable off-site location and available when needed.
• Maintain a record of the ships which transmit LRIT information to the centre.
• Use a standard protocol for communications and agreed protocols to
connect with IDE and DDP server.
• Use a secure authentication method with LRIT Data Users.
• Add the appropriate data to the LRIT information if not done by the ASP.
• Have access to the current LRIT DDP and to earlier versions of the plan.
• Publish its charges, in a currency to be decided by the Contracting
Government(s) and in SDR (special drawing rights) together with the date
from which the charges are effective.

The performance of all LRIT Data Centres should be audited by the LRIT
Coordinator.

6. International LRIT Data Exchange:

The International LRIT Data Exchange should:

•Route LRIT information between LRIT Data Centres using the information
provided in the LRIT Data Distribution Plan
• Be connected to all LRIT Data Centres and the LRIT Data Distribution Plan
server
• Use a “store and forward-buffer” to ensure LRIT information is received
 • Automatically maintain journals containing message header information to
be used only for invoicing and audit purpose.
• Archive journals, for at least one year and in such a way that the archived
journals should provide a complete record of the exchange activities
between two consecutive annual audits of its performance.
• Receive journals from LRIT Data Centres & combine these journals with its
own journals.
• Use a standard protocol for communications to connect to LRIT Data
Centres and DDP.
• Use a standard secure access method with the LRIT Data Centres and the
DDP server.
• Not have the capability to archive LRIT information.
• Not have the capability to view or access the LRIT information.
• Have access to current LRIT DDP and to earlier versions of the plan.
• Receive information from LRIT Data Centres in relation to the charges they
levy for the transfer.
• Create a master list of charges for all LRIT Data Centres and transmit the
master list of charges to an LRIT Data Centre on request.

The performance of the IDE should be audited by the LRIT Coordinator.

7. LRIT Data Distribution Plan

IMO has established the LRIT Data Distribution Plan (DDP) and maintains the DPP
and its server. The DDP should include:

• A list indicating the unique LRIT identities of Contracting Governments, SAR

services entitled to receive LRIT information, LRIT Data Centres, the IDE,
ASPs, the LRIT DDP server and the LRIT Coordinator.
• A list of geographical coordinates of points, based on the WGS 84 datum
defining the geographical area so as to measure the required distances from
baseline.
• A list of ports and port facilities and places under each Contracting
Government together their coordinates in which ships may enter or proceed
to.
 • A list indicating which LRIT Data Centre is collecting and archiving LRIT
information for each of the Contracting Governments together with the
related LRIT identifies
• A list indicating the URL’s of each LRIT Data Centre, the IDE and DDP servers.
• A list indicating the ASPs providing services to each LRIT Data Centre
together with the related LRIT identifies
• The contact details of Contracting Governments for LRIT-related matters
• The contact details of SAR services entitled to receive LRIT information
• Information in relation to each LRIT Data Centre and IDE and their points of
contact.
• Information in relation to the LRIT Coordinator, and its contact details
• Information in relation to the DDP and its server and contact details of IMO
officials to be contacted for operational matters and maintenance of DDP.
• A record of all previous versions of the plan together with the dates (period
in force)

8. 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 given by:

No. of delivered LRIT information meeting latency requirements x 100 %

Total number of LRIT information requests

should be:
1. 95% of the time over any 24-hour period; and
2. 99% over any 1 month
9. Administrations

• Each Administration should

(i) Decide to which LRIT Data Centre their ships are required to transmit LRIT
information.
(ii) Provide to the selected LRIT Data Centre the ship’s information i.e. Name,
IMO number, Call sign, MMSI Number and type of ship.
(iii) Update the LRIT Data Centre as and when there are changes to the
information provided.

• When there is transfer of flag, the new Administration should provide, without
undue delay, to the selected LRIT Data the following information: Name, IMO
number, Call sign and MMSI Number, type of ship, the effective date and time
(UTC) of transfer and the State whose flag the ship was previously flying, if
known.
• Upon the transfer of the flag or when ship is to be taken permanently out of
service, the Administration whose flag the ship was entitled to fly till now,
should provide, without undue delay, to the LRIT Data Centre the following
information: Name, IMO number, Call sign, MMSI Number, type of ship, the
effective date and time (UTC) of transfer or when the ship will be taken
permanently out of service and the State to which the flag of the ship has been
transferred, if known.

10. Search and rescue services

• When SAR services wish to receive LRIT information, they should indicate to
the LRIT Data Centre the criteria for receiving such information.
• A SAR service should request the provision of LRIT information only via the
LRIT Data Centre serving the Contracting Government in whose territory the
service is located.

*********
 MSC 106/19/Add.1
Annex 18, page 1

ANNEX 18

RESOLUTION MSC.263(84)/REV.1
(adopted on 7 November 2022)

PERFORMANCE STANDARDS AND FUNCTIONAL REQUIREMENTS FOR THE

LONG-RANGE IDENTIFICATION AND TRACKING OF SHIPS

THE MARITIME SAFETY COMMITTEE,

RECALLING Article 28(b) of the Convention on the International Maritime Organization

concerning the functions of the Committee,

RECALLING ALSO resolution A.886(21) on Procedure for the adoption of, and amendments
to, performance standards and technical specifications, by which the Assembly resolved that
the function of adopting performance standards and technical specifications, as well as
amendments thereto, shall be performed by the Maritime Safety Committee,

BEARING IN MIND the provisions of regulation V/19-1 of the International Convention for the
Safety of Life at Sea, 1974 (the Convention), relating to the long-range identification and
tracking of ships, and the Revised performance standards and functional requirements for the
long-range identification and tracking of ships (Revised Performance Standards), adopted by
resolution MSC.263(84), as amended by resolutions MSC.330(90) and MSC.400(95),

HAVING CONSIDERED, at its 106th session, the recommendation made by the

Sub-Committee on Navigation, Communications and Search and Rescue at its ninth session,

1 ADOPTS the revised Performance standards and functional requirements for the
long-range identification and tracking of ships, set out in the annex to the present resolution;

2 REVOKES resolutions MSC.263(84), MSC.330(90) and MSC.400(95);

3 AGREES that any reference to resolution MSC.263(84), as amended, should be read

as reference to the present resolution;

4 INVITES Contracting Governments to the Convention to bring the enclosed

revised performance standards to the attention of all parties concerned.
MSC 106/19/Add.1
Annex 18, page 2

ANNEX

PERFORMANCE STANDARDS AND FUNCTIONAL REQUIREMENTS FOR THE

LONG-RANGE IDENTIFICATION AND TRACKING OF SHIPS

1 Overview

1.1 The Long-range Identification and Tracking (LRIT) system provides for the global
identification and tracking of ships.

1.2 The LRIT system consists of the shipborne LRIT information transmitting equipment,
the Communication Service Provider(s), the Application Service Provider(s), the LRIT Data
Centre(s), including any related vessel monitoring system(s), the LRIT Data Distribution Plan
and 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 system architecture

Contracting Government ... Contracting Government ... Contracting Government ...

flag State flag State flag State

Contracting Government H Contracting Government O Contracting Government W
port State port State port State
flag State flag State flag State
Contracting Government G Contracting Government M Contracting Government U
coastal State coastal State coastal State
port State port State port State
flag State flag State flag State
Contracting Government A Contracting Government
SAR serviceF Contracting Government
SAR serviceN Contracting Government
SAR serviceT The standard for data format, set of
coastal State coastal State coastal State possible commands, security and user
port State port State port State
flag State flag State flag State flag State
SAR service SAR service SAR service interface may vary from place to place
coastal State coastal State coastal State
port State port State port State port State
SAR service SAR service SAR service
coastal State coastal State coastal State coastal State
SAR service SAR service SAR service SAR service International
routing
rules

National Regional Cooperative International

LRIT LRIT LRIT LRIT

Data Centre Data Centre Data Centre Data Centre LRIT
or or or or Data Distribution Plan
VMS VMS VMS VMS server

D/B D/B D/B D/B

One standard for data format,

set of commands, security
International LRIT Data Exchange and quality of service
Journal

1.3 LRIT information is provided to Contracting Governments and search and rescue
services1 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.

1
The term "search and rescue service" is defined in regulation V/2.5.
 MSC 106/19/Add.1
Annex 18, page 3

1.4 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.

1.5 The obligations of ships to transmit LRIT information and the rights and obligations of
Contracting Governments and of search and rescue services to receive LRIT information are
established in regulation V/19-1 of the 1974 SOLAS Convention.

2 Definitions

2.1 Unless expressly provided otherwise:

.1 Convention means the International Convention for the Safety of Life at

Sea, 1974, as amended.
.2 Regulation means a regulation of the Convention.

.3 Chapter means a chapter of the Convention.

.4 LRIT Data User means a Contracting Government or a search and rescue

(SAR) service which opts to receive the LRIT information it is entitled to.

.5 Committee means the Maritime Safety Committee.

.6 High-speed craft means a craft as defined in regulation X/1.3.

.7 Mobile offshore drilling unit means a mobile offshore drilling unit as defined
in regulation XI-2/1.1.5.

.8 Organization means the International Maritime Organization.

.9 Vessel monitoring system means a system established by a Contracting

Government or a group of Contracting Governments to monitor the
movements of the ships entitled to fly its or their flag. A vessel monitoring
system may also collect from the ships information specified by the
Contracting Government(s) which has established it.

.10 LRIT information means the information specified in regulation V/19-1.5.

2.2 The term "ship", when used in the present performance standards, includes mobile
offshore drilling units and high-speed craft as specified in regulation V/19-1.4.1 and means a
ship which is required to transmit LRIT information.

2.3 Terms not otherwise defined should have the same meaning as the meaning attributed
to them in the Convention.

3 General provisions

3.1 It should be noted that regulation V/19-1.1 provides that:

Nothing in this regulation or the provisions performance standards and functional

requirements adopted by the Organization in relation to the long-range identification
and tracking of ships shall prejudice the rights, jurisdiction or obligations of States
under international law, in particular, the legal regimes of the high seas, the exclusive
MSC 106/19/Add.1
Annex 18, page 4

economic zone, the contiguous zone, the territorial seas or the straits used for
international navigation and archipelagic sea lanes.

3.2 In operating the LRIT system, recognition should be given to international conventions,
agreements, rules or standards that provide for the protection of navigational information.

3.3 The present performance standards should always be read together with regulation V/19-1
and the technical specifications for the LRIT system.2

4 Shipborne equipment

4.1 In addition to the general requirements contained in resolution A.694(17) on

Recommendations on general requirements for shipborne radio equipment forming part of the
Global Maritime Distress and Safety System (GMDSS) and for electronic navigational aids, the
shipborne equipment should comply with the following minimum requirements:

.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;3 and

.6 be tested for electromagnetic compatibility taking into account the

recommendations4 developed by the Organization.

4.2 In addition to the provisions specified in paragraph 4.1 above, the shipborne
equipment should provide the functionality specified in table 1.

2
Refer to the Long-range identification and tracking system - Technical documentation (Part I)
(MSC.1/Circ.1259, as revised).
3
This provision should not apply to ships using for the transmission of LRIT information any of the radio
communication equipment provided for compliance with the provisions of chapter IV. In such cases, the
shipborne equipment should be provided with sources of energy as specified in regulation IV/13.
4
Refer to resolution A.813(19) on General requirements for electromagnetic compatibility of all electrical and
electronic ship's equipment.
 MSC 106/19/Add.1
Annex 18, page 5

Table 1

Data to be transmitted from the shipborne equipment

Parameter Comments
Shipborne equipment
The identifier used by the shipborne equipment.
identifier
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
Positional data 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 hours to the LRIT
Data Centre, irrespective of where the ship is located and without
human interaction on board the ship.
The date and time(3) associated with the GNSS position.
Time Stamp 1 The equipment should be capable of transmitting the time(3) associated
with the GNSS position with each transmission of LRIT information.
(1)
Notes: 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 intervals 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.3 The shipborne equipment should transmit the LRIT information using a communication
system which provides coverage in all areas where the ship operates.

4.4 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.

4.4.1 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.
MSC 106/19/Add.1
Annex 18, page 6

5 Application Service Providers

5.1 Application Service Providers (ASPs) providing services to:

.1 a National LRIT Data Centre, should be recognized by the Contracting

Government establishing the centre;

.2 a Regional or a Cooperative LRIT Data Centre, should be recognized by the

Contracting Governments establishing the centre. In such a case, the
arrangements for recognizing the ASPs should be agreed amongst the
Contracting Governments establishing the centre; and

.3 an International LRIT Data Centre, should be recognized by the Committee.

5.2 Contracting Governments should provide to the Organization a list with the names and
contact details of the ASPs they recognize together with any associated conditions of recognition
and thereafter should, without undue delay, update the Organization as changes occur.

5.2.1 The Organization should communicate information it receives pursuant to the

provisions of paragraph 5.2 and information in relation to the ASP(s) recognized by the
Committee for providing services to the International LRIT Data Centre and any changes
thereto to all Contracting Governments, all LRIT Data Centres, the International LRIT Data
Exchange and the LRIT Coordinator.

5.3 An ASP function should:

.1 provide a communication protocol interface between the Communication

Service Providers and the LRIT Data Centre to enable the following minimum
functionality:

.1 remote integration of the shipborne equipment into an LRIT Data

Centre;

.2 automatic configuration of transmission of LRIT information;

.3 automatic modification of the interval of transmission of LRIT

information;

.4 automatic suspension of transmission of LRIT information;

.5 on-demand transmission of LRIT information; and

.6 automatic recovery and management of transmission of LRIT

information;

.2 provide an integrated transaction management system for the monitoring of

LRIT information throughput and routeing; and

.3 ensure that LRIT information is collected, stored and routed in a reliable and
secure manner.
 MSC 106/19/Add.1
Annex 18, page 7

5.4 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(1) The IMO ship identification number(1) and MMSI for the ship.
Name of the ship which has transmitted the LRIT information in the
Name of ship
English language using Latin-1 alphabet and UTF-8 encoding.
Type of the ship which has transmitted the LRIT information using a
Type of ship(2)
predefined code.
The date and time(3) the transmission of LRIT information is received
Time Stamp 2
by the ASP (if used).
The date and time(3) the received LRIT information is forwarded from
Time Stamp 3
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.
The date and time(3) the LRIT information is received by the LRIT Data
Time Stamp 4
Centre.
The date and time(3) the transmission of LRIT information is forwarded
Time Stamp 5
from the LRIT Data Centre to an LRIT Data User.
(1)
Notes: See regulation XI-1/3 and resolution A.1078(28) on IMO Ship Identification Number Scheme.
(2) Types of ships to be used in LRIT messages are outlined in LRIT Technical documentation, part I
(MSC.1/Circ.1259, as revised).
(3) All times should be indicated as Universal Coordinated Time (UTC).

5.5 In addition to the provisions of paragraph 5.3, Administrations, Contracting

Governments and the Committee may establish, in relation to the ASPs seeking their
recognition, specific requirements as a condition of recognizing a particular ASP.

6 Communication Service Providers

6.1 Communication 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.

6.2 A CSP may also provide services as an ASP.

MSC 106/19/Add.1
Annex 18, page 8

7 LRIT Data Centre

7.1 All LRIT Data Centres should:

.1 establish and continuously maintain systems which ensure, at all times, that
LRIT Data Users are only provided with the LRIT information they are entitled
to receive as specified in regulation V/19-1;

.2 collect LRIT information from ships instructed by their Administrations to

transmit the LRIT information to the centre;

.3 obtain, when requested to provide LRIT information transmitted by ships

other than those which transmit the information to the centre,
LRIT information from other LRIT Data Centres through the International
LRIT Data Exchange;

.4 make available, when requested to provide LRIT information transmitted by

ships which transmit the information to the centre, LRIT information
transmitted to the centre to other LRIT Data Centres through the International
LRIT Data Exchange;

.5 execute requests received from LRIT Data Users for polling of LRIT
information or for change(s) in the interval(s) of transmission of LRIT
information by a ship or a group of ships transmitting the information to the
centre;

.6 relay, when required, requests received from LRIT Data Users through the
International LRIT Data Exchange to the other LRIT Data Centres for polling
of LRIT information or for change(s) in the interval(s) of transmission of LRIT
information by a ship or a group of ships not transmitting the information to
the centre;

.7 execute requests received through the International LRIT Data Exchange

from other LRIT Data Centres for polling of LRIT information or for change(s)
in the interval(s) of transmission of LRIT information by a ship or a group of
ships transmitting the information to the centre;

.8 upon request disseminate to LRIT Data Users the LRIT information they are
entitled to receive in accordance with the agreed arrangements and notify
the LRIT Data User and the Administration when a particular ship stops
transmitting LRIT information;

.9 archive LRIT information from ships which transmit the information to the
centre, for at least one year and until such time as the Committee reviews
and accepts the annual report of the audit of its performance by the
LRIT Coordinator. However, the archived LRIT information should provide a
complete record of the activities of the centre between two consecutive
annual audits of its performance;

.10 for LRIT information archived within the last four days, send the LRIT
information within 30 min of receiving a request;

.11 for LRIT information archived between four and 30 days previously, send the
LRIT information within one hour of receiving a request;
 MSC 106/19/Add.1
Annex 18, page 9

.12 for LRIT information archived more than 30 days previously, send the LRIT
information within five days of receiving a request;

.13 ensure, using appropriate hardware and software, that LRIT information is
backed-up at regular intervals, stored at suitable off-site location(s) and
available as soon as possible in the event of disruption to ensure continuity
of service;

.14 maintain a record of the ships which transmit LRIT information to the centre
including name of ship, IMO ship identification number, call sign, maritime
mobile service identity (MMSI) and type of ship;

.15 use a standard protocol for communications and agreed protocols to connect
with the International LRIT Data Exchange and the LRIT Data Distribution
Plan server;
.16 use a standard secure transmission method with the International LRIT Data
Exchange and the LRIT Data Distribution Plan server;

.17 use a secure authentication method with LRIT Data Users;

.18 use a standard and expandable message format for communicating with the
International LRIT Data Exchange and the LRIT Data Distribution Plan
server;

.19 use reliable connections (e.g. TCP) to ensure that the LRIT information is
successfully received by the LRIT Data Centres;

.20 add the appropriate data identified in table 2 to each transmission of LRIT
information collect by the centre; and

.21 have access to the current LRIT Data Distribution Plan and to earlier
versions of the plan.

7.2 All LRIT Data Centres should comply with the relevant provisions of the Technical
specifications for communications within the LRIT system5 and of the Technical specifications
for the LRIT Data Distribution Plan and should take into account the relevant provisions of the
technical specifications for the International LRIT Data Exchange.

7.3 All Regional or Cooperative LRIT Data Centres and the International LRIT Data
Centre should only internally route LRIT information transmitted by ships entitled to fly the flag
of the Contracting Governments establishing or participating in such centres and should
automatically maintain journal(s) for all of the internally routed LRIT information. The journal(s)
should only contain message header information which should be used for audit and invoicing
purposes. The journal(s) should be transmitted to the International LRIT Data Exchange at
regular intervals in order to be combined with the journal(s) maintained by the International
LRIT Data Exchange.

7.4 Each LRIT Data Centre should settle its financial obligations vis-à-vis the LRIT Data
Centres which provide to it LRIT information and the International LRIT Data Exchange in a
timely manner in accordance with the arrangements they have agreed.

7.5 The performance of all LRIT Data Centres should be audited by the LRIT Coordinator.

5
Refer to the Long-range identification and tracking system - Technical documentation (Part I)
(MSC.1/Circ.1259, as revised).
MSC 106/19/Add.1
Annex 18, page 10

7.5.1 All LRIT Data Centres should cooperate and make available to the LRIT Coordinator
the information required to enable the satisfactory completion of an audit of their performance.

7.5.2 All LRIT Data Centres should settle their financial obligations vis-à-vis
the LRIT Coordinator in a timely manner in accordance with the arrangements they have
agreed.

7.6 When providing LRIT information to LRIT Data Users, other than to a SAR service,
LRIT Data Centres should:

.1 in case such information are not archived, utilize the current version of the
LRIT Data Distribution Plan;

.2 in case such information is archived, utilize the version(s) of the LRIT Data
Distribution Plan which were applicable at the time the archived LRIT
information requested was originally received; and

.3 apply the geographical areas specified by the Contracting Governments

concerned in the LRIT Data Distribution Plan and should not endeavour to
resolve any issues which may arise when such areas are either not specified
or overlap geographical areas specified by other Contracting Governments.

7.7 Notwithstanding the provisions of paragraph 7.1 and subject to the provisions of
paragraph 17.2, all LRIT Data Centres should provide to SAR services LRIT information
transmitted by all ships located within the geographical area specified by the SAR service
requesting the information so as to permit the rapid identification of ships which may be called
upon to provide assistance in relation to the search and rescue of persons in distress at sea.
The LRIT information should be provided irrespective of the location of the geographical area
and should be provided even if the geographical area is outside the search and rescue region
associated with the SAR service requesting the information (regulation V/19-1.12 refers).

8 National, Regional and Cooperative LRIT Data Centres

8.1 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
thereafter should, without undue delay, update the information provided as and when
changes occur.

8.2 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.

8.3 Upon request, National, Regional and Cooperative LRIT Data Centres may provide
services to Contracting Governments other than those establishing the centre.

8.3.1 The arrangements for providing services should be agreed between the LRIT Data
Centre and the Contracting Government requesting the provision of the services.
 MSC 106/19/Add.1
Annex 18, page 11

8.3.2 The Contracting Government establishing the National LRIT Data Centre or one of
the Contracting Governments establishing the Regional or Cooperative LRIT Data Centre
should, if the centre provides services to Contracting Governments other than those which
established the centre, provide relevant details to the Organization and thereafter should,
without undue delay, update the information provided as and when changes occur.

8.4 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. VMSs may also
perform other functions.

8.4.1 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.

9 International LRIT Data Centre

9.1 An International LRIT Data Centre recognized by the Committee should be

established.

9.2 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.

9.3 Ships, other than those which are required to transmit LRIT information to either a
National, Regional or Cooperative LRIT Data Centre, should transmit the required LRIT
information to the International LRIT Data Centre.

9.4 An International LRIT Data Centre may, upon request, collect additional information
from ships entitled to fly the flag of an Administration on the basis of specific arrangements
concluded with the Administration concerned.

9.5 In addition to the provisions of section 7, the International LRIT Data Centre should
comply with the provisions of the technical specifications for the International LRIT Data
Centre.6

10 International LRIT Data Exchange

10.1 An International LRIT Data Exchange recognized by the Committee should be

established.

10.2 Contracting Governments should cooperate, under the coordination of the

Committee, with a view to ensuring the establishment of the International LRIT Data Exchange.

10.3 The International LRIT Data Exchange should:

.1 route LRIT information between LRIT Data Centres using the information
provided in the LRIT Data Distribution Plan;

6
Refer to the Long-range identification and tracking system - Technical documentation (Part I)
(MSC.1/Circ.1259, as revised).
MSC 106/19/Add.1
Annex 18, page 12

.2 be connected to all LRIT Data Centres and the LRIT Data Distribution Plan
server;

.3 use a store and forward-buffer to ensure LRIT information is received;

.4 automatically maintain journal(s) containing message header information

only which may be used for:

.1 invoicing functions and settlement of invoicing disputes; and

.2 audit purposes;

.5 archive journal(s), for at least one year and until such time as the Committee
reviews and accepts the LRIT Coordinator's annual report of the audit of its
performance. However, the archived journal(s) should provide a complete
record of the activities of the exchange between two consecutive annual
audits of its performance;

.6 receive journal(s) from Regional, Cooperative and the International LRIT

Data Centre and combine these journal(s) with its own journal(s);

.7 prepare, as necessary, performance-related statistical information based on

the information contained in the journal(s);

.8 use a standard protocol for communications agreed protocols to connect with

LRIT Data Centres and the LRIT Data Distribution Plan server;

.9 use a standard secure access method with the LRIT Data Centres and the
LRIT Data Distribution Plan server;

.10 use a standard and expandable message format for communicating with the
LRIT Data Centres and the LRIT Data Distribution Plan server;

.11 use reliable connections (e.g. TCP) to ensure that the LRIT information is
successfully received by the LRIT Data Centres;

.12 not have the capability to archive LRIT information;

.13 not have the capability to view or access the LRIT information;

.14 have access to the current LRIT Data Distribution Plan and to earlier versions
of the plan; and

.15 receive pricing information from LRIT Data Centres.

10.4 The International LRIT Data Exchange should comply with the provisions of the
technical specifications for the International LRIT Data Exchange7 and with the relevant
provisions of the technical specifications for communications within the LRIT system and of
the technical specifications for the LRIT Data Distribution Plan.

7
Refer to the Long-range identification and tracking system - Technical documentation (Part I)
(MSC.1/Circ.1259, as revised).
 MSC 106/19/Add.1
Annex 18, page 13

10.5 The International LRIT Data Exchange should provide to:

.1 the LRIT Coordinator offline access to all journals; and

.2 Contracting Governments and LRIT Data Centres offline access only to their
share of the journals which relates to the LRIT information they have
requested and were provided with.

10.6 The performance of the International LRIT Data Exchange should be audited by the
LRIT Coordinator.

10.6.1 The International LRIT Data Exchange should cooperate and make available to the
LRIT Coordinator the information required to enable the satisfactory completion of an audit of its
performance.

10.6.2 The International LRIT Data Exchange should settle its financial obligations vis-à-vis
the LRIT Coordinator in a timely manner in accordance with the arrangements they have
agreed.

11 LRIT Data Distribution Plan

11.1 The Organization should establish and maintain the LRIT Data Distribution Plan.
The Organization should also host, build, operate and maintain the LRIT Data Distribution Plan
server.

11.2 The LRIT Data Distribution Plan should include:

.1 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;

.2 for the purpose of the implementation of the provisions of

regulation V/19-1.8.1, for each Contracting Government a list of geographical
coordinates of points, taking into account the related provisions of the
technical specifications for the LRIT Data Distribution Plan,8 based on the
WGS 84 datum defining the geographical area:

.1 of the waters9 landward of the baselines for measuring the breadth

of the territorial sea of the Contracting Government concerned in
accordance with international law;

.2 of the territorial sea10 of the Contracting Government concerned in

accordance with international law;

8
Refer to the Long-range identification and tracking system - Technical documentation (Part I)
(MSC.1/Circ.1259, as revised).
9
The baselines for measuring the breadth of the territorial sea of the Contracting Government concerned in
accordance with international law, the lines of delimitation between the Contracting Governments concerned
and States with adjacent coasts and the coast of the Contracting Government concerned including any
landward waters within which any ship which is required to comply with the provisions of regulation V/19-1
is able to navigate.
10
The baselines for measuring the breadth of the territorial sea and the outer limit of the territorial sea of the
Contracting Government concerned in accordance with international law and the lines of delimitation of the
MSC 106/19/Add.1
Annex 18, page 14

.3 between the coast of the Contracting Government concerned and a

distance of 1,000 nautical miles from its coast. The Contracting
Government concerned may, in lieu of defining the aforesaid area
with reference to the geographical coordinate points defining its
coast, define the area with reference to the geographical coordinate
points of the baselines for measuring the breadth of the territorial
sea of the Contracting Government concerned in accordance with
international law; and

.4 within which the Contracting Government concerned is seeking the

provision of LRIT information pursuant to the provisions of
regulation V/19-1.8.1.3, if other than that defined under
sub-paragraph .3 above;

.3 for the purpose of the implementation of the provisions of

regulation V/19-1.9.1 the following information:

.1 the name of the Administration (together with its associated unique

LRIT identity) which opts to exercise its right under the provisions of
regulation V/19-1.9.1;

.2 the name(s) of the Contracting Government(s) (together with their

associated unique LRIT identities) to which LRIT information about
ships entitled to fly the flag of the aforesaid Administration shall not
be provided pursuant to the provisions of paragraph V/19-1.8.1.3
together with the date and time as from which the decision of the
Administration applies and any particulars thereof stated in the
related communication to the Organization;

.3 in case of amendment, suspension or annulment of such decisions

by the aforesaid Administration, the salient details; and

.4 the date and time the Organization has received the related
communication, including related amendment, suspension or
annulment and the date and time the Organization has informed all
Contracting Governments pursuant to the provisions of
regulation V/19-1.9.2;

.4 a list of ports and port facilities located within the territory and a list of places
under jurisdiction of each Contracting Government together with the
associated geographical coordinates of points (based on WGS 84 datum) in
which ships that are required to comply with the provisions of
regulation V/19-1 may enter or proceed to;

.5 a list indicating which LRIT Data Centre is collecting and archiving

LRIT information for each of the Contracting Governments together with the
related LRIT identities;
.6 a list indicating the Uniform Resource Locator/Uniform Resource Identifier
(URL/URI) (Web Service Endpoint) of each LRIT Data Centre, the
International LRIT Data Exchange and the LRIT Data Distribution Plan
server;

territorial sea between the Contracting Governments concerned and States with opposite or adjacent coasts
in accordance with international law.
 MSC 106/19/Add.1
Annex 18, page 15

.7 a list indicating the ASPs providing services to each LRIT Data Centre
together with the related LRIT identities;

.8 the contact details of Contracting Governments for LRIT-related matters;

.9 the contact details of search and rescue services entitled to receive

LRIT information for LRIT-related matters;

.10 information in relation to the ASPs recognized by each Contracting

Government together with any conditions attached to such recognitions, and
their points of contact;

.11 information in relation to each National, Regional and Cooperative LRIT Data
Centre, the International LRIT Data Centre and the International LRIT Data
Exchange, and their points of contact;

.12 information in relation to the LRIT Coordinator, and its contact details;

.13 information in relation to the LRIT Data Distribution Plan and its server and
contact details of official(s) of the Organization who may be contacted for
matters relating to the operation or maintenance of the plan or its server or
for seeking help in relation to issues relating to or arising from the operation
of the plan or its server; and

.14 a record of all previous versions of the plan together with the dates and times
between which each version was in effect.

11.3 The LRIT Data Distribution Plan server should:

.1 allow the International LRIT Data Exchange, the LRIT Data Centres and the
LRIT Coordinator to have access to the current version of the plan;

.2 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;

.3 use a standard protocol for communications and agreed protocols to connect

with the International LRIT Data Exchange and the LRIT Data Centres;

.4 use a standard secure transmission method with the International LRIT Data
Exchange and the LRIT Data Centres;

.5 use a standard and expandable message format for communicating with the
International LRIT Data Exchange and the LRIT Data Centres;

.6 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;

.7 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;
MSC 106/19/Add.1
Annex 18, page 16

.8 provide for the submission of the geographical areas in a standard industry

format and use a consistent naming convention for the elements;

.9 provide for uploading of the geographical areas in batch files in

Geography Markup Language (GML) format;

.10 maintain a unique number for each published version of the plan,
incrementing each time a new version of the plan is published;

.11 provide for the downloading of the plan and its incremental updates by
the LRIT Data Centres and the International LRIT Data Exchange on the
publishing of a new version of the plan;

.12 archive all published versions of the plan and its incremental updates;

.13 use a standard secure access methods with the Contracting Governments
and the LRIT Coordinator; and

.14 provide a web interface for the entry and amendment of information in the
plan.

11.4 The LRIT Data Distribution Plan server should comply with the technical specifications
for the LRIT Data Distribution Plan11 and with the relevant provisions of the technical
specifications for communications within the LRIT system.

12 LRIT system security

12.1 LRIT communications using landline links should provide for data security using
methods such as:

.1 authorization: Access should only be granted to those who are authorized to

see the specific LRIT information;

.2 authentication: Any party exchanging information within the LRIT system

should require authentication before exchanging information;

.3 confidentiality: Parties running an application server should protect the

confidentiality of the LRIT information to ensure that it is not disclosed to
unauthorized recipients when it travels across the LRIT system; and

.4 integrity: Parties exchanging LRIT information should ensure that the

integrity of the LRIT information is guaranteed and that no data has been
altered.

13 LRIT system performance

13.1 LRIT information should be available to an LRIT Data User within 15 min of the time it
is transmitted by the ship.

13.2 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.

11 Refer to the Long-range identification and tracking system - Technical documentation (Part I)
(MSC.1/Circ.1259, as revised).
 MSC 106/19/Add.1
Annex 18, page 17

13.3 The quality of service:

Number of delivered LRIT information meeting latency requirements x 100%

Total number of LRIT information requests

should be:

.1 95% of the time over any 24-hour period; and

.2 99% over any one month.

14 LRIT Coordinator

14.1 The LRIT Coordinator should be appointed by the Committee.

14.2 The LRIT Coordinator should assist in the establishment of the International LRIT
Data Centre and/or International LRIT Data Exchange by:

.1 participating in the development of any new technical specifications for

the LRIT system or of any amendments to existing ones taking into account
the provisions of regulation V/19-1, the present performance standards, the
existing technical specifications and any related decisions of the Committee;

.2 issuing, when requested by the Committee, requests for the submission of

proposals for the establishment and operation of the International LRIT Data
Centre and/or the International LRIT Data Exchange;

.3 evaluating the management, operational, technical and financial aspects of

the proposals received taking into account the provisions of
regulation V/19- 1, the present performance standards, the technical
specifications for the LRIT system and any other related decisions of the
Committee and submitting its recommendations in this respect for
consideration by the Committee; and

.4 participating, as and when requested by the Committee, in their testing and

integration into the LRIT system and reporting its findings in this respect for
consideration by the Committee.

14.3 The LRIT Coordinator should, taking into account the provisions of regulation V/19- 1,
the present performance standards, the technical specification for the LRIT system and any
related decisions of the Committee:

.1 upon request, by any party concerned or the Committee, undertake the

investigation of operational or technical disputes or invoicing difficulties and
make recommendations for their settlement to the parties concerned and the
Committee, as appropriate;

.2 participate, as and when requested by the Committee, in the testing and

integration of LRIT Data Centre(s) into the LRIT system and report its finding
in this respect for consideration by the Committee; and
MSC 106/19/Add.1
Annex 18, page 18

.3 participate, as and when requested by the Committee, in the testing of new

or modified procedures or arrangements for communications between the
International LRIT Data Exchange, the LRIT Data Centres and the LRIT
Data Distribution Plan server and report its finding in this respect for
consideration by the Committee.

14.4 The LRIT Coordinator should undertake a review of the performance of the LRIT
system taking into account the provisions of regulation V/19-1, the present performance
standards, the technical specification for the LRIT system and any related decisions of the
Committee and should report its findings to the Committee at least annually. In this respect,
the LRIT Coordinator should on an annual basis:

.1 review the performance of ASPs (or CSPs when they act as ASPs) providing
services to the International LRIT Data Centre;
.2 audit the performance of all LRIT Data Centres based on archived
information and their fee structures;

.3 audit the performance of the International LRIT Data Exchange and its fee
structure, if any; and

.4 verify that Contracting Governments and search and rescue services receive
only the LRIT information they have requested and are entitled to receive.

14.5 In addition to reporting to the Committee on the performance of the LRIT system
including any identified non-conformities, the LRIT Coordinator may make recommendations
to the Committee, based on an analysis of its findings, with a view to improving the efficiency,
effectiveness and security of the LRIT system.

14.6 The LRIT Coordinator should, for the purpose of performing the functions specified in
paragraphs 14.2.4 and 14.3 to 14.5:

.1 be given the required level of access, by the LRIT Data Centres and the
International LRIT Data Exchange, to management, and to charging,
technical and operational data;

.2 collect and analyse samples of LRIT information provided to LRIT Data

Users;

.3 collect and analyse statistics compiled by LRIT Data Centres and the
International LRIT Data Exchange; and

.4 be given access to the current LRIT Data Distribution Plan and to earlier
versions of the plan.

14.7 The LRIT Coordinator should establish and communicate to the Committee the
charges it would be levying in order to recover the expenditure it incurs for providing the
services specified in paragraphs 14.2 to 14.5.

14.7.1 The related charges should be paid to the LRIT Coordinator in accordance with
agreed arrangements – taking into account the laws of the Contracting Government(s)
concerned – as follows:

.1 in relation to the evaluation of proposals for the establishment of the

International LRIT Data Centre and/or the International LRIT Data Exchange
(paragraph 14.2.3), by those submitting the related proposals;
 MSC 106/19/Add.1
Annex 18, page 19

.2 when participating in the testing and integration of the International

LRIT Data Centre and/or the International LRIT Data Exchange into the
LRIT system (paragraph 14.2.4), by the International LRIT Data Centre
and/or the International LRIT Data Exchange as the case may be;

.3 when undertaking the investigation of operational or technical disputes or

invoicing difficulties (paragraph 14.3.1), by the party requesting the service;

.4 when participating in the testing and integration of LRIT Data Centre(s) into
the LRIT system (paragraph 14.3.2), by the LRIT Data Centre(s) being tested
or integrated;
.5 when participating in the testing of new or modified procedures or
arrangements for communications between the International LRIT Data
Exchange, the LRIT Data Centres and the LRIT Data Distribution Plan server
(paragraph 14.3.3), by the International LRIT Data Exchange and/or the
LRIT Data Centre(s);

.6 when reviewing the performance of ASPs (or CSPs when they act as ASPs)
providing services to the International LRIT Data Centre (paragraph 14.4.1),
by the ASPs concerned;

.7 when auditing the performance and fee structures of LRIT Data Centres
(paragraph 14.4.2), by the LRIT Data Centre concerned; and

.8 when auditing the performance and fee structure of the International LRIT
Data Exchange (paragraph 14.4.3), by the International LRIT Data
Exchange.

14.7.2 The Organization should not be required to make any payments to the LRIT
Coordinator for any work the LRIT Coordinator may be required to carry out pursuant to any
of the provisions of paragraphs 14.2 to 14.5; or for reporting or making recommendations to
the Committee pursuant to any of the provisions of paragraphs 14.2 to 14.5.

14.7.3 Contracting Governments should not be responsible for making any direct payments
to the LRIT Coordinator for the services it may be required to provide pursuant to any of the
provisions of paragraphs 14.2 to 14.5. However, without prejudice as to the relations between
Contracting Governments and the LRIT Data Centres the services of which may use,
Contracting Governments may be required by LRIT Data Centres to pay fees for the LRIT
information they request and receive which may contain elements to offset the charges paid
by LRIT Data Centres to the LRIT Coordinator for the functions it performs. Notwithstanding
the aforesaid, the Contracting Government which requests directly from the LRIT Coordinator
the provision of a specific service should pay the LRIT Coordinator the relevant charges for
the service it has requested.

15 Administrations

15.1 Each Administration should decide to which LRIT Data Centre ships entitled to fly its
flag are required to transmit LRIT information.

15.2 Each Administration should provide to the selected LRIT Data Centre the following
information for each of the ships entitled to fly its flag which is required to
transmit LRIT information:

.1 name of ship;
MSC 106/19/Add.1
Annex 18, page 20

.2 IMO ship identification number;

.3 call sign;

.4 maritime mobile service identity; and

.5 type of ship.

15.3 Upon the transfer of the flag of a ship which is required to transmit LRIT information
from another State, the Administration whose flag the ship is now entitled to fly should provide,
without undue delay, to the selected LRIT Data Centre in addition to the information specified
in paragraph 15.2 the following information:

.1 the effective date and time (UTC) of transfer; and

.2 the State whose flag the ship was formally entitled to fly, if known.

15.4 Administrations should, without undue delay, update the LRIT Data Centre as and
when changes to the information they have provided under paragraphs 15.2 and 15.3 occur.

15.5 Upon the transfer of the flag of a ship which is required to transmit LRIT information
to another State or when the ship is to be taken permanently out of service, the Contracting
Government of the State whose flag the ship was entitled to fly hitherto should provide, without
undue delay, to the LRIT Data Centre the following information:

.1 name of ship;

.2 IMO ship identification number;

.3 the effective date and time (UTC) of the transfer, or when the ship was, or
will be, taken permanently out of service; and

.4 the State to which the flag of the ship has been transferred, if known.

15.6 Administrations should either provide the ASP(s) they recognize with relevant
information taking into account the provisions of 15.2 to 15.5 or should make the necessary
arrangements for the aforesaid information to be provided to the ASP(s) concerned by the
selected LRIT Data Centre.

16 Contracting Governments

16.1 Each Contracting Government should:

.1 obtain the LRIT information to which it is entitled under the provisions of

regulation V/19-1, and has requested, from the LRIT Data Centre designated
under paragraph 15.1. Contracting Governments which have no ships
entitled to fly their flag may receive the LRIT information they are entitled to
under the provisions of regulation V/19-1 from any one of the LRIT
Data Centres but should select one LRIT Data Centre from which they wish
to receive the information. In such cases, the Contracting Government
concerned should, after reaching an agreement with the LRIT Data Centre
the services of which it would be using, inform accordingly the Organization
and, without undue delay, update the information they have provided as and
when it changes;
 MSC 106/19/Add.1
Annex 18, page 21

.2 if it wishes to receive LRIT information pursuant to the provisions of

regulation V/19-1.8.1.1, indicate to the LRIT Data Centre the criteria for
receiving such information. If so decided the Contracting Government may
give the LRIT Data Centre a standing order regarding the criteria for
receiving LRIT information;

.3 if it wishes to receive LRIT information pursuant to the provisions of

regulation V/19-1.8.1.2, indicate to the LRIT Data Centre the name and
the IMO ship identification number of the particular ship and either:

.1 the distance from a port; or

.2 a point in time,

from when it requires the provision of LRIT information transmitted by the ship.
If so decided the Contracting Government may give the LRIT Data Centre a
standing order regarding the criteria for receiving LRIT information.
If the standing order is a distance from a port, the Contracting Government also
has to inform the centre of the name of the port each ship is proceeding to;

.4 if it wishes to receive LRIT information pursuant to the provisions of

regulation V/19-1.8.1.3, indicate the distance from its coast within which it
requires the provision of LRIT information transmitted by ships. If so decided,
the Contracting Government may give the LRIT Data Centre a standing order
regarding the criteria for receiving LRIT information;

.5 cooperate with a view to resolving any issues in connection with which flag
a particular ship is entitled to fly; and

.6 ensure either the destruction of all received LRIT information which is no

longer in use or its archiving in a secure and protected manner.

16.2 In accordance with regulation V/19-1.8.2, Contracting Governments are obliged to

communicate to the Organization and enter into the LRIT Data Distribution Plan the information
specified in paragraph 11.2 and thereafter update such information as and when changes
occur before requesting the provision of LRIT information pursuant to the provisions of
regulation V/19-1.8.1.

16.3 Contracting Governments are advised that the LRIT system would not apply any
restrictions pursuant to the provisions of either regulations V/19-1.8.2 and V/19-8.1.3 in relation
to ships located within the waters landward of baselines or regulation V/19-18.1.4 in relation
to ships located within territorial seas until such time that they have communicated to the
Organization and provided in the LRIT Data Distribution Plan the required information.

17 Search and rescue services

17.1 Subject to the provisions of paragraph 7.7, a search and rescue service when it
wishes to receive LRIT information pursuant to the provisions of regulation V/19-1.12 should
indicate to the LRIT Data Centre the criteria for receiving such information.

17.2 A search and rescue service should request the provision of LRIT information only via
the LRIT Data Centre serving the Contracting Government in whose territory the service is
located.
MSC 106/19/Add.1
Annex 18, page 22

17.3 Subject to the provisions of the national legislation of the Contracting Government
concerned, search and rescue services should provide information when requested by the
LRIT Coordinator to enable the holistic review of the performance of the LRIT system and for
the investigation of any disputes.

***