inshore vessel monitoring system (i-vms) device ... · system used on ships and by vessel traffic...

I-VMS function requirements specification (V2)

of 21

Inshore Vessel Monitoring System (I-VMS) Device: Specification of requirements 1. Definitions For the purposes of this Marine Management Organisation (MMO) I-VMS device functional requirements specification, unless the context otherwise requires, the following provisions shall have the meanings given to them below. Term Meaning 3rd country or third country A non-EU state. AES 256 Advanced Encryption Standard. AIS The Automatic Identification System is a tracking

system used on ships and by vessel traffic services for identifying and locating vessels by electronically exchanging data with other nearby ships and AIS base stations. AIS information supplements marine radar, which continues to be the primary method of collision avoidance for water transport.

CFP Common Fisheries Policy is the fisheries policy of the European Union (EU).

Defra Department of environment food and rural affairs EMC Electromagnetic Compatibility is defined by the

International Electrotechnical Commission (IEC) as; The ability of a device, equipment or system to function satisfactorily in its electromagnetic environment without introducing intolerable electromagnetic disturbances to anything in that environment.

EU VMS Vessel Monitoring System installed on vessels 12m and over. A statutory measure required by EC Council Regulation 1224/2009. Position reporting by satellite telecommunications.

Firmware Firmware is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices.

Geofence A geofence is a defined spatial perimeter for real-world geographic areas. In this specification it specifically relates to certain marine areas which require a level of monitoring, whether it is to protect certain marine features or habitats, or manage levels of fishing activity.

GPRS General Packet Radio Service is a packet oriented


of 21

Term Meaning mobile data service that operates over the 2G and 3G Global Systems for Mobile communications (GSM).

GNSS Global Navigation Satellite System, and is the standard generic term for satellite navigation systems that provide autonomous geo-spatial positioning with global coverage.

GSM Global System for Mobile communications. (originally Groupe Spécial Mobile)

HTTP Hypertext Transfer Protocol IFCA

Inshore Fisheries and Conservation Authority consist of ten separate authorities who have a duty to regulate, manage and enhance the inshore sea fisheries within the authorities’ district between 0 to 6 nautical miles seaward.

IP67 The protection classification offered by an enclosure is shown by the letter IP (Ingress Protection) and two digits. The first digit indicates two factors: 1. Protection for persons, 2. Protection for equipment. The second digit indicates the protection against water.

I-VMS Inshore Vessel Monitoring System. An MMO and IFCA approved ‘low cost’ system able to report vessel position using mobile phone technology in accordance with this specification

IP Internet Protocol ISO 9001 A family of standards related to quality management

systems and designed to help organisations ensure that they meet the needs of customers and other stakeholders while meeting statutory and regulatory requirements related to the product.

ISO 14001 A standard which formally specifies requirements for an environmental management system to enable an organisation to develop and implement a policy and objectives which take into account legal requirements and other requirements to which the organisation subscribes, and information about significant environmental aspects.

ISO 27001 A standard which formally specifies a management system that is intended to bring information security under explicit management control. Being a formal specification means that it mandates specific requirements. Organisations that claim to have adopted ISO/IEC 27001 can therefore be formally audited and certified compliant with the standard

Line Conditioner See Power Conditioner

Managed Areas Any area detailed through statutory or non-statutory legislation including, but not limited to byelaws, voluntary agreements and CFP measures

MMO Marine Management Organisation

http://en.wikipedia.org/wiki/Quality_management_system

http://en.wikipedia.org/wiki/Quality_management_system


of 21

Term Meaning MRCC Maritime Rescue and Coordination Centre. MPA Marine Protected Areas are areas in which human

activity may be placed under some restriction in the interest of conserving and/or maintaining the natural environment, its surrounding waters and the occupant ecosystems, and any cultural or historical resources that may require preservation or management.

National Reporting Position reports transmitted through GPRS utilising electronic vessel positioning devices set up by any UKFA or IFCA in accordance with relevant national and/or local regulations governing marine protected areas, IFCA districts and other management schemes at sea

PGP Key Pretty Good Privacy is a data encryption and decryption computer program

Power Conditioner Also known as a line conditioner or power line conditioner. A component to improve the quality of the power that is delivered to the I-VMS device, e.g. a component that delivers a voltage at the correct level and with the correct characteristics to enable load equipment to function properly.

SMTP Simple Mail Transfer Protocol SOAP Simple Object Access Protocol is a protocol

specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on XML Information Set for its message format, and usually relies on other Application Layer protocols, most notably HTTP or SMTP, for message negotiation and transmission.

SSL Secure Sockets Layer UKFAs United Kingdom Fisheries Authorities which includes

the Welsh Government, Department of Agriculture & Rural Development NI, Isle of Man Department for Environment Fisheries & Agriculture, Marine Scotland, Marine Management Organisation, Dept. of Environment States of Jersey; Bailiwick of Guernsey.

URL Uniform Resource Locator UTC Co-ordinated Universal Time. VMS Vessel Monitoring System (see EU VMS and I-VMS for

further definition) VMS operational platform. Operational facilities provided for the UKFAs and the

IFCAs by a third party supplier, for receiving EU and National VMS position reports from UK and non- UK vessels, and issuing poll requests to UK vessels.

WSDL Web Services Description Language is an XML-based interface description language that is used for describing the functionality offered by a web service.


of 21

2. Introduction The purpose of this specification is to set out requirements for suppliers to provide to the fishing industry a type approved I-VMS device to satisfy MMO and IFCA management conditions. a) An I-VMS device must meet the functional requirements detailed in the 'Detailed

functional and non-functional requirements' below. The device must be able to provide position reporting requirements as laid out in management conditions from the MMO or IFCA in accordance with relevant national and/or local regulations governing MPAs, IFCA districts and other fisheries management schemes at sea (referred to as ‘national reporting’).

b) The supply and installation of I-VMS devices as detailed in the 'Detailed

functional and non-functional requirements' of this specification include; testing and approval of the I-VMS device model by the MMO and IFCA, in accordance with the Approval Programme documents which will be released to the MMO website in due course.

3. National reporting requirements In July 2012, the MMO, Devon and Severn and Southern IFCAs published a joint report about an I-VMS trial in the Lyme Bay and Torbay Site of Community Importance. The report can be viewed at www.marinemanagement.org.uk/protecting/conservation/lyme_bay.htm This report was followed up by a meeting with Defra in December 2012 to discuss the future direction and roll-out of such systems to aid fisheries and MPA management and control. Defra requested that the MMO should lead a project to co-ordinate the development of I-VMS as a potential management solution for inshore fisheries and MPAs in English waters. Vessel Monitoring Systems are an established tool for fisheries management in EC waters. Council Regulation (EC) 1224/2009 requires fishing vessels of 12m overall length or greater to be fitted with VMS. One of the distinguishing characteristics of I-VMS is the use of GSM/GPRS rather than satellite technology to transmit position reports, to reduce operating costs. Unlike the VMS requirements under Council Regulation (EC) 1224/2009 vessels which require an I-VMS to be fitted will only report within managed areas. Outside these areas the device will not send position reports to the MMO and IFCA monitoring hub. The future potential for similar low cost, high frequency reporting in the offshore zone (i.e. 12 nautical miles from the UK coastline) will be explored to enhance the existing EU VMS reporting requirement although no action would be taken without agreement of other member states who may fish in the area. The future potential for I-VMS systems operating in all marine waters where vessels operate will also be explored although no action would be taken without the agreements of the devolved administrations, other member states who may fish in

http://www.marinemanagement.org.uk/protecting/conservation/lyme_bay.htm


of 21

the area and where there is a risk vessel who have the devices fitted may be unfairly discriminated against. There is currently no agreement or timetable in place to extend the requirement for EU VMS satellite reporting to vessels below 12 metres in length. However, this project continues in the knowledge that such regulations could be introduced in future and it is without prejudice to any such developments. Therefore, suppliers wishing to apply for I-VMS device approval will wish to consider ensuring that their systems can be adapted to allow for position reporting via satellite telecommunications, should subsequent requirements for this facility arise.


of 21

Detailed functional and non-functional requirements 1. General requirements ............................................................................................. 7

1.1 Configuration .................................................................................................... 7 1.2 Certification requirements................................................................................. 7 1.3 Physical requirements ...................................................................................... 7 1.4 Power arrangements ........................................................................................ 8

2. Position monitoring and output requirements ......................................................... 9 2.1 Positional requirements .................................................................................... 9 2.2 Geofencing ....................................................................................................... 9 2.3 Status code list ............................................................................................... 10 2.4 Positional data outputs ................................................................................... 11 2.5 Non-positional data outputs ............................................................................ 11

3. Communication ..................................................................................................... 12 3.1 General communication requirements ............................................................ 12 3.2 Report transmissions ...................................................................................... 12 3.3 Communications interface between supplier and the VMS operational platform ............................................................................................................................. 12

4. Optional requirements (non-mandatory) ............................................................... 13 4.1 Use of other communication service(s) through the I-VMS device ................. 13 4.2 Additional destinations for National VMS position reports .............................. 13

5. Supply, installation and support ............................................................................ 14 5.1 Supply ............................................................................................................ 14 5.2 Installation ...................................................................................................... 15 5.3 Support ........................................................................................................... 15

Annex A: Standard format for the geofence upload .................................................. 17 Annex B: Contact details .......................................................................................... 18 Annex C: List of UK ports ......................................................................................... 19 Annex D: WSDL definition ........................................................................................ 21


of 21

1. General requirements 1.1 Configuration a) As set out in the introduction, the I-VMS device is to provide transmission of

position reports to the VMS operational platform using non-satellite communication services (e.g. GPRS/GSM) in accordance with national reporting requirements.

b) If the supplier wishes, the I-VMS device may also provide other functions and

services. Any additional costs incurred in activating any of these functions/services must be highlighted to industry, must not interfere with the functions described within this specification, and must be included on the I-VMS device when presented for type approval to ensure they do not interfere with the mandatory functions. Note that data parameters may also be set by the MMO and IFCAs. The only exception to this is for safety at sea, where a Maritime Distress button is provided; any distress at sea message must take priority over all other messaging, however, it must not be directed to the VMS operational platform. Any such messages must go to the appropriate safety authorities. Please note that safety at sea matters are not the responsibility of the MMO or the IFCAs and thus fall outside the scope of this project. Please refer to section 4.1.

1.2 Certification requirements a) Suppliers submitting their I-VMS device for type approval must provide the

approval panel evidence of the following certificates:

• IP67certification (IP minimum) • ISO 9001:2008 • ISO 14001:2004 • ISO/IEC 27001:2005

b) Equipment must meet the full requirements for distribution in the EEA 1.3 Physical requirements a) All goods, wiring and connections to be built with materials able to withstand

normal conditions at sea and to meet EU safety requirements and standards as appropriate for maritime installation.

b) Any part of the I-VMS device or antennas exposed to the elements must provide

acceptable service in the marine environment and be waterproof to IP67 standard as a minimum.

c) Each I-VMS device must have a unique serial number indelibly marked on the

outer casing e.g. embossed, or laser engraved or on a metal security tag that must be visible after the installation is complete.

d) In addition the unique serial number of the I-VMS device must be stored in its

Firmware in such a way that does not allow deletion or amendment.


of 21

e) The external casing of the I-VMS device must be physically sealed before being installed, and the means provided to detect any unauthorised opening or other physical interference or ingress of the I-VMS device. As a minimum, this must consist of a sensor in the device that detects when it is opened and transmits a position report with the appropriate event status code when the communication link(s) are re-established.

f) Once the I-VMS device is sealed, any adjustments or reconfiguration to scripts,

reporting frequencies and other software functionality must only be possible via a communications link by the approved supplier and by engineers authorised by the supplier opening the I-VMS device on board the vessel.

1.4 Power arrangements a) The I-VMS device must have the capability of being continuously powered directly

from the vessel’s primary power supply. b) The I-VMS device must be able to cope with power fluctuations likely to be

experienced on board fishing vessels without any degradation to performance. These arrangements must include provisions for:

• working across a range of voltages typically in use by fishing vessels at sea,

as a minimum coping with variations between 8 to 36 volts, allowing a nominal supply of 12V or 24V DC;

• protection from: voltage surge, voltage spiking, and reverse polarity events; • power conditioner (also known as a line conditioner or power line conditioner)

c) The device must display external electronic indicators to indicate to the vessel

master that a vessel’s I-VMS primary power supply is connected to the device. d) A rechargeable battery, together with a recharging facility, must be provided

within the I-VMS device to provide the capability when primary power is lost or not available. The purpose of this requirement is to enable the I-VMS device to:

• transmit an appropriate status code to the VMS operational platform with

position report indicating change in power status; • maintain its settings throughout the period of primary power loss, and • to provide up to 1,000 national or local VMS reporting transmissions to the

VMS operational platform, whilst in port and at sea, when relying upon battery power alone;

• allow fishing vessels which do not have sufficient on board power supply to fit an I-VMS device and operate permanently on the I-VMS rechargeable battery. These vessels will be responsible for ensuring the device is recharged where required.

e) When the rechargeable battery power falls below the level required to sustain

transmissions, the I-VMS device must maintain its settings at that point. f) When primary power is restored the I-VMS device must:


of 21

• recommence normal functioning with the settings in place at loss of power and not with any default factory settings;

• transmit a position report immediately to the VMS operational platform, with an appropriate event status code, see section 2.3.

2. Position monitoring and output requirements 2.1 Positional requirements a) The I-VMS device must employ a GNSS augmentation accurate to +/- 5m to meet

national reporting requirements. b) There is to be no external input to the positioning system, such that it must not be

possible to change the positional fix by manual intervention. c) Positional data reports can only be reported to the operational hub when the

vessel is within a managed area or if the device owner/vessel master has given permission for regulators to view vessel position reports outside these areas

d) The I-VMS device must transmit position reports individually and automatically in

real time, where a communication link is available, at the specified intervals within managed areas.

e) The I-VMS device must provide the correct date and time in UTC for all position

reports f) Following a break in the communications at the time a position report is required

to be transmitted, the report must be stored and then batched and forwarded on restoration of the communication link. See section 3.1(d)

g) The I-VMS device is to have the capability to vary the frequencies of recording

position reports and of transmitting these reports to the VMS operational platform for areas including but not limited to all MPAs (EU and UK) and IFCA districts. Coordinates for these areas, along with the associated rules (e.g. reporting interval, duration) will be managed and submitted to the approved suppliers, ahead of any area controls being introduced; changes to existing areas and controls will also be submitted ahead of implementation.

2.2 Geofencing a) It will be the responsibility of the approved suppliers to download these

coordinates and recreate these areas (and associated rules) in the form of geofences for onwards transmission to, or local loading and activation on, the I-VMS device.

• Data will be provided to the supplier in a standard format. Detailed in Annex A

of this document b) The I-VMS device must be capable of downloading, remotely via a

communication link these predefined specific area coordinates in the form of geofences. They may also be loaded locally by engineers authorised by the supplier. It must be possible to delete or temporarily suspend these geofences


of 21

and the associated rules remotely. They may also be deleted by engineers authorised to do so by the supplier.

c) Each geofence is to consist of the following data items:

• name of geofence and its associated reference number; • area defined as a polygon in latitude and longitude coordinates (based on

WGS84 datum) • reporting interval (expressed in minutes) • optional rule: condition based on minimum speed below which increased

reporting shall apply; • optional rule: condition based on period for which the geofence applies:

o start date/time o end date/ time.

d) It is anticipated that there may eventually be upwards of 2,000 geofences

required for national reporting regimes at any given time, so a capacity to store a minimum of 100,000 latitude/longitude points would be required. However, a consideration could be made where the supplier produces alternative proposals to manage these geofences (e.g. based on their location, specific regional geofences supplied to the specific regional inshore fleets). Details of these proposals must be submitted to the MMO and accepted prior to the device being approved.

e) Where two or more geofences overlap, the I-VMS device must send a single

report at the shortest intervals represented by the two or more geofences (the report will then be appropriately forwarded by the approved supplier’s service).

2.3 Status code list As a minimum, the following event status codes must be provided from the device to the VMS operational platform with an appropriate position report (if within a managed area) for national reporting requirements: • Geofence reference number indicating entry and exit of a geofence • loss of primary power/switch to battery (when lost); • restoration of primary power (when restored); • loss of connection with the GSM/GPRS network (when restored); • upon opening the I-VMS device; • antenna blockage or no position fix obtained at appointed time (when restored); • stored position forwarded; • low battery alert; • a break or disconnection of the cable(s) from the I-VMS device and GPRS/GSM

antenna All relevant event status codes must be transmitted to the VMS Operational hub both inside and outside managed areas.


of 21

2.4 Positional data outputs Positional data reports can only be reported to the operational hub when the vessel is within a managed area or if the device owner/vessel master has given permission for regulators to view vessel position reports at all times a) Each transmitted position report for I-VMS reporting is to contain:

• national report flag to indicate this report is as a result of national reporting regulations (not EU regulations)

• most recent geographical position of the fishing vessel to 5 decimal places (in WGS84);

• date and time (in UTC) of the fixing of the said position; • instant speed and course of the vessel (equivalent to 0.1 knots and course

expressed in degrees (true not magnetic) to 0.1 degree); • unique serial number of transmitting I-VMS device • status code (as listed above in section 2.3); • Geofence reference number.

b) These data exchanges and formats are to use XML files and delivered using web

services description language (WSDL) from the supplier’s hub – see section 3.3 for further details.

2.5 Non-positional data outputs All event status codes must be transmitted to the VMS operational hub both inside and outside managed areas. When a device reports a status code outside of a managed area, only the following data outputs will be provided to the operational hub: • status code;

o loss of primary power/switch to battery (when lost); o restoration of primary power (when restored); o loss of connection with the GSM/GPRS network (when restored); o upon opening the I-VMS device; o antenna blockage or no position fix obtained at appointed time (when

restored); o low battery alert; o a break or disconnection of the cable(s) from the I-VMS device and

GPRS/GSM antenna • date and time (in UTC) of the status code message; • instant speed and course of the vessel (equivalent to 0.1 knots and course

expressed in degrees (true not magnetic) to 0.1 degree); • unique serial number of transmitting I-VMS device No positional information to be supplied into the VMS operational platform outside of managed areas unless there is prior agreement between the device owner and the MMO and IFCA.


of 21

3. Communication 3.1 General communication requirements a) The I-VMS device must provide GSM/GPRS based communications through a

transceiver embedded within the I-VMS device to transmit position reports. The antenna may also be contained within the I-VMS device or be mounted externally.

b) All data transmissions must be secure and encrypted to AES256 standard c) The service used must enable roaming across international networks. d) Following a break of the communication link, at the time a position report is

required to be transmitted, the report to be sent must be stored. On restoration of the link, the I-VMS device must be capable of:

• immediately transmitting reports that provide the current position along with an

appropriate status code to indicate there had been a broken link; • and then transmitting all stored reports between those times, earliest first.

e) As a minimum the I-VMS device must be capable of taking position fixes every 1

minute. Further, the I-VMS device must store each of these position fixes on an internal log for a minimum rolling period of 3 months.

f) The supplier hub must have contingencies in place for disaster recovery and

power failure g) Where the I-VMS device employs a GNSS week number rollover programme to

express the dates and times, details of the rollover must be provided to the MMO and IFCAs

3.2 Report transmissions a) All data transmitted from the vessel is to be captured by the approved supplier

and transmitted from the supplier hub to the VMS operational platform. The supplier hub must be continuously available with 24hr coverage for receiving, encoding and transmitting reports from its installed I-VMS devices, to the VMS operational platform. For further information on the communications interface between the supplier and the MMO see section 3.3

b) The I-VMS device must be able to support national reporting frequencies that

may range from a maximum of 6 hours, down to every minute. These frequencies will be managed using pre-defined geofences within managed areas.

c) Arrangements are to be put in place to enable the vessel owner to be charged for

the communication of all transmitted reports 3.3 Communications interface between supplier and the VMS operational platform a) The communications interface between the supplier and the VMS operational

platform will use WSDL specified as follows:


of 21

• all position reports transmitted by the device will be exchanged as XML files and shall be based on web services using either the communication protocol SOAP v1.2 over HTTPS internet protocol, or through SMTP Email Gateway.

Using communication protocol SOAP:

• for each communication two asynchronous one-way message connections are established between each SOAP node: one with the message and one with the acknowledgement;

• the UK VMS operational platform will acknowledge all data reports from the supplier using the SOAP protocol;

• the supplier shall monitor that any sent message to the UK VMS operational platform is acknowledged;

• for security a 2-way SSL shall be used when an internet connection (HTTPS) is established;

• 128-bit encryption will be used when a communication is established; • data security, based on a two way certification using PKI digital keys, URL and

IP addresses, is required for all communications over the internet between the supplier and UK VMS operational platform.

Using SMTP Email Gateways:

• for each communication the supplier will send an email with the message as an attachment encoded using the PGP key supplied for the UK VMS operational platform;

• the UK VMS operational platform will respond with an acknowledgment email for each email message received, also encrypted using the same key;

• the supplier will monitor that any sent email message to the UK VMS operational platform is acknowledged;

• 2048 bit PGP keys will be used for all email encryption; • as a minimum the supplier shall use firewalls in conjunction with the

encryption of data for data security. b) Each individual data report to be available at the VMS operational platform, no

more than one minute after the data report has been received by the supplier; 4. Optional requirements (non-mandatory) 4.1 Use of other communication service(s) through the I-VMS device Where additional features have been provided for safety at sea such as a distress button, man overboard or AIS functionality, the destination for these transmissions must be the appropriate emergency and Coastguard services. 4.2 Additional destinations for National VMS position reports a) With the agreement of the vessel owner (and where appropriate at the owner’s

expense), and the MMO and IFCAs, the I-VMS device may be configured to transmit national/local I-VMS reports, to additional destinations, (e.g. vessel owner, their agent, or producer organisation systems) as long as such transmissions do not interfere with the priorities for reporting to the VMS operational hub and, if provided for, safety at sea reporting. Provision of this


of 21

service is the sole responsibility of the supplier. Data parameters may be set by the MMO and IFCAs and data protection provisions will apply.

b) Alert system for vessel owners With the agreement of the vessel owners (and where appropriate the owner’s expense) and the MMO and IFCA, the I-VMS device supplier server may be configured to monitor the reporting of the unit within parameters set by the MMO and IFCA. If the device fails to report within an agreed timescale the supplier hub may transmit a notification (via mobile phone or email address) to the vessel owner or agreed party. 5. Supply, installation and support 5.1 Supply a) The supplier must provide two I-VMS devices for approval testing through an

independent, external organisation and against the VMS operational platform. During this period the supplier will work with the VMS operational platform provider and MMO/IFCA to agree the test and verification schedule which will broadly be divided into:

• Certification (for such requirements as ISO standards and Ingress Protection); • Functional testing (such as geofencing and communications); • Observation (such as visible serial numbers, constraints on visible displays); • Supplier declaration (such as 24 availability of the hub

An outline test schedule is provided in the approval programme documents which will be available on the MMO website in due course. The test schedule will set out the type of test for each requirement. Device suppliers will be required to provide access to their supplier hubs to the MMO, IFCA and the independent testing organisation during the approval process. Test devices submitted to the MMO will also be provided to this organisation. b) Manufacture and production must be in line with quality procedures certified to

ISO Quality standards ISO 9001; these quality standards must be in place throughout the supplier’s organisation. The supplier is required to confirm to the MMO and IFCA the production processes used, the location of production and provide assurances that the quality is maintained at all stages of production.

c) Records must be kept by the supplier and made available to the MMO and IFCA

if requested, showing the unique serial numbers and part numbers of the components of the I-VMS device for each fishing vessel fitted.

d) Full user-guides (such as a ‘how to use’ guide for the fishing industry covering its

operation at sea and a full guide on its functionality for the MMO and IFCA) are to be made available in document and electronic form.

e) A technical specification is to be provided, in electronic format, for the MMO and

IFCA, including updates through the life of the approval to reflect agreed changes.


of 21

5.2 Installation a) The I-VMS device may be installed in the wheelhouse, on the deck, wheelhouse

super-structure or on the mast. b) External electronic indicators must be located where clearly visible to the master

while helming the vessel (e.g. inside the wheelhouse), to indicate that the vessels I-VMS primary power supply is connected to the device (see section 1.4c)

c) All I-VMS device mechanisms (such as software, communication scripts and I-

VMS device serial numbers) for reporting and other functionality must be pre-loaded before the I-VMS device is sealed and installed.

d) It must be possible to securely fit the components of the I-VMS device to the

infrastructure of the vessel. If not internal to the I-VMS device the antennas must be installed externally in a sealed unit.

e) The antennas connected to the I-VMS device are not to be obstructed,

disconnected or blocked in any way. f) The supplier will be required to install I-VMS devices at fishing ports throughout

the UK. Sub-suppliers may be used by the supplier provided they are trained in the I-VMS device installation process. The majority of vessels will be located at UK ports listed in Annex C. Arrangements must also be allowed for installations in other UK locations and at ports outside of the UK.

g) If engineers from sub-suppliers are used for installation and repair of the I-VMS

device the supplier must ensure that these personnel are authorised in order to maintain security for the I-VMS devices.

h) The supplier will be required to decommission I-VMS devices from fishing vessels

that no longer require the I-VMS device. A full audit trail will be required for this process. The supplier may re-issue said I-VMS devices as long as they can demonstrate a full audit trail.

5.3 Support a) The I-VMS device firmware, software, communication scripts, geofencing etc.

must be upgradeable over the communication links as well as from shore-side engineer visits.

b) Where the supplier is aware of a planned suspension of communications service

to a particular vessel, for example where a vessel owner communications fee has not been paid, the supplier must inform the MMO and IFCAs using the contact details provided in Annex B five working days in advance of termination of the service to the vessel.

c) Where the supplier is aware of an interruption of the GSM/GPRS communications

service, the supplier must communicate this to the MMO and IFCAs at the earliest opportunity. The relevant contact details are detailed in Annex B


of 21

d) It will be the responsibility of the supplier to finance, manage and implement any necessary technical changes to all I-VMS devices fitted to ensure continuity of service.

e) On commencement of the MMO and IFCA approval the supplier is to nominate a

device manager to be the main point of contact in dealing with the MMO and IFCAs.

f) The device manager will be requested to attend meetings as needed with the

MMO and IFCAs for regular updates on the continuation management of MPAs and inshore fisheries.

g) The supplier may be required to provide an expert witness service (providing

witness statement and court appearance) for I-VMS device functionality and operation to the MMO and IFCAs. The supplier must indicate to the MMO their costs for this service provision prior to approval.

I-VMS function requirements specification (V2) Annex A: Standard format for the geofence upload

Request Form Date Geofence Owner

Geofence Reference Number Geofence Location

Geofence Reference Name

Reporting Interval (expressed in minutes)Real Time or Store and Forward

Optional condition 1: Minimum Speed Knots

Optional condition 2: Date Period Active Start Date TimeActive End Date Time

Geofence referred in Byelaw:Additional Files:

Coordinates in WGS84 unless otherwise stated:Coordinate format: eg. dd.ddddd

Coordinates (Latitiude and Longitude)

Geofence Request Form Template

of 21


of 21

Annex B: Contact details I-VMS project contact details (for MMO and all IFCAs) Primary telephone: 0191 376 2514 (MMO) Secondary telephone: 0191 376 2705 (MMO) Email: [email protected] Website: www.marinemanagement.org.uk/protecting/ivms/index.htm

mailto:[email protected]

http://www.marinemanagement.org.uk/protecting/ivms/index.htm


of 21

Annex C: List of UK ports Please note this is not an exhaustive list. • Aldburgh (beach) • Aldingham • Amble • Appledore • Arnside • Axmouth • Bardsea • Barling • Barling • Barnstaple • Barrow • Beer • Bembridge • Bideford • Blakeney • Blyth • Bognor Regis • Boscastle • Boston • Bradwell • Brancaster • Branscombe • Braunton • Brightlingsea • Brighton • Brightton & Selsey • Brixham • Broadstairs • Bude • Budleigh Salterton • Burham-on-Crouch • Cadgwith • Caister (beach) • Chapel Point

(beach) • Charlestown • Chichester Harbour • Church Cove • Clacton (beach) • Cley (beach) • Clovelly • Coverack • Cowes

• Cromer (beach) • Dartmouth • Deal (beach) • Dover • Dungeness • Dungeness (beach) • East Runton(beach) • Eastbourne • Exmouth • Falmouth Est • Faversham • Felixstowe Ferry • Flookburgh • Folkestone • Foulney Island • Fowey • Gibraltar Point • Gillan • Gorleston • Gorran Haven • Gosport • Grange-over-sands • Gt. Yarmouth • Hamble • Harrington • Harwich • Hastings • Haverigg • Hayle • Helford • Herne Bay • Heysham • Holehaven Creek • Hythe • Hythe (beach) • Ilfracombe • Instow • Ipswich • Keyhaven • Kings Lynn • Knott End • Lancaster • Langstone

• Leigh-on-Sea • Littlehampton • Lizard • Looe • Lowestoft • Lyme Regis • Lymington • Lynmouth • Maldon • Manningtree • Margate • Maryport • Mevagissey • Milbrook • Millom, (Lancashire) • Minehead • Morecambe • Morston • Mousehole • Mudeford • Mullion • Mundesley (beach) • Newbigging • Newhaven • Newlyn • Newquay • North Shields • Orford • Overstrand (beach) • Padstow • Paglesham • Pakefield (beach) • Par • Parton • Peel Island • Penberth • Penzance • Plymouth • Polkerris • Polperro • Poole • Port Gaverne • Port Isaac


of 21

• Port Loe • Port Quin • Porthgwarra • Porthoustock • Portland • Portleven • Portreath • Portscatho • Portsmouth • Pothallow • Potheras Cove • Queenborough • Ramgate • Ramsgate • Ravenglass • Roa Island • Rochester • Rochester • Rock • Roosebeck • Rye

• Salcombe • Sandwich • Seahouses • Sea Palling (beach) • Seascale • Selsey Bill • Sennen • Sheerness • Sheringham (beach) • Shoreham-by-Sea • Silloth • Sizewell (beach) • Southend-on-sea • Southend-on-Sea

(beach) • Southwold • St Agnes • St Ives • Sussex • Swanage • Teignmouth • Thornham

• Torquay • Trenow • Ulverston • Wallasea • Walney • Walton • Watchet • Watermouth • Wells • West Bay • West Mersea • Weybourne (beach) • Weymouth • Whitehaven • Whitstable • Winterton-on-Sea

(beach) • Wivenhoe • Workington • Yarmouth


of 21

Annex D: WSDL definition To be supplied

inshore vessel monitoring system (i-vms) device ... · system used on ships and by vessel traffic...

Documents