System Segment Design Document V3000

HITT V3000
Standard Vessel Traffic Management and

Information System (VTMIS)
System/Segment Design Document
Prepared by:
HITT Traffic
P.O. Box 717
7300 AS Apeldoorn
The Netherlands
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
© 2011 HITT B.V.

THIS INFORMATION CARRIER CONTAINS PROPRIETARY INFORMATION
WHICH SHALL NOT BE USED FOR OTHER PURPOSES THAN THOSE FOR
WHICH IT HAS BEEN RELEASED, NOR BE REPRODUCED OR DISCLOSED TO
THIRD PARTIES WITHOUT THE PRIOR WRITTEN CONSENT OF HITT B.V., THE
NETHERLANDS.
Page 2 of 63
HITT PROPRIETARY, subject to restrictive legend on page 2
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
HISTORY SHEET
REV DATE PCFno DESCRIPTION RESPONSIBLE

00 2006-07-05 First Issue R.A. Hogendoorn
01 2006-07-05 109894-1 Changed design VHF C.N. Lukassen
02 2007-10-11 Removed product version number from A. Bloemendal
titlesheet
03 2008-05-13 Removed product version numbers J.R. Bekkema
from document
04 2008-09-08 113872-1 Modifications made according to J.R. Bekkema
VTMIS 1.13.0
05 2009-09-15 Modifications made according to J.R. Bekkema
VTMIS 1.15.0
06 2009-11-23 EOS extension J.P.G. Wientjes
07 2010-02-26 Updated SSDD structure and content P. Ellenbroek
to match A3000
08 2010-09-06 Modifications made according to J.R. Bekkema
VTMIS 1.17.0
116428-13 AIS blocking mechanism added T.v.Olphen
116476-12 AIS low update rate added “
116726-4 AIS mail server added “
116800-5 GPE selection to TFP “
09 2010-10-14 Modified chapter 6 R.A. Hogendoorn
J.R. Bekkema
10 2010-10-26 117620-1 Modified Functional and Operational J.R. Bekkema
system overview
11 2011-03-02 117989-21 Add CDM user to V3000 T.v.Olphen
118241-2 EOS viewer “
Page 3 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
TABLE OF CONTENTS
1. INTRODUCTION................................................................................................ 8
1.1 Identification............................................................................................................................... 8
1.2 Scope......................................................................................................................................... 8
1.3 Document overview ................................................................................................................... 8
1.4 Referenced documents.............................................................................................................. 8
1.5 Terminology ............................................................................................................................... 9
1.6 System overview...................................................................................................................... 10
1.7 Operational concept................................................................................................................. 10
1.7.1 VTS operator .................................................................................................................... 11
1.7.2 Supervisor / planner ......................................................................................................... 11
1.7.3 Replay / analysis............................................................................................................... 12
1.7.4 Maintenance ..................................................................................................................... 13
1.7.5 Remote maintenance and support ................................................................................... 15
2. SYSTEM DESCRIPTION ................................................................................. 16

2.1 General .................................................................................................................................... 16
2.2 System functions ..................................................................................................................... 17
2.2.1 General............................................................................................................................. 19
2.2.2 Operational system functions ........................................................................................... 19
2.2.3 Supporting system functions ............................................................................................ 19
2.2.4 External sensor subsystems............................................................................................. 20
2.2.4.1 AIS............................................................................................................................. 20
2.2.4.2 Domestic signalling ................................................................................................... 20
2.2.4.3 Electro optical............................................................................................................ 20
2.2.4.4 Hydro/meteo.............................................................................................................. 20
2.2.4.5 Radar......................................................................................................................... 20
2.2.4.6 RDF ........................................................................................................................... 21
2.2.5 Other subsystems............................................................................................................. 21
2.2.5.1 Management information system .............................................................................. 21
2.2.5.2 VHF communication system ..................................................................................... 21
2.3 Redundancy concept ............................................................................................................... 21
2.3.1 Power redundancy............................................................................................................ 21
2.3.2 Network ............................................................................................................................ 21
2.3.3 HWCI / CSCI redundancy................................................................................................. 22
3. SYSTEM DESIGN............................................................................................ 23
3.1 Architecture.............................................................................................................................. 23
3.2 General .................................................................................................................................... 23
3.2.1 VTMIS network ................................................................................................................. 24
3.2.2 Sensor Site ....................................................................................................................... 25
3.2.2.1 General...................................................................................................................... 25
3.2.2.2 Sensor and Communication Modules ....................................................................... 25
3.2.2.2.1 Module AIS ............................................................................................................ 25
3.2.2.2.2 Module General ..................................................................................................... 25
3.2.2.2.3 Module Hydro/Meteo ............................................................................................. 26
3.2.2.2.4 Module Single Radar ............................................................................................. 26
3.2.2.2.5 Module Dual Radar................................................................................................ 26
3.2.2.2.6 Module Low-Cost Radar........................................................................................ 26
3.2.2.2.7 Module RDF .......................................................................................................... 26
3.2.2.2.8 Module VHF........................................................................................................... 27
3.2.2.2.9 Module EOS .......................................................................................................... 27
3.2.2.3 Computer Equipment ................................................................................................ 27
Page 4 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.2.2.3.1 Radar Data Processor ........................................................................................... 27

3.2.2.3.2 Radar Service Display ........................................................................................... 27
3.2.2.4 Network Equipment ................................................................................................... 27
3.2.2.5 Other Equipment ....................................................................................................... 27
3.2.3 VTS Centre Site................................................................................................................ 28
3.2.3.1 General...................................................................................................................... 28
3.2.3.2.1 Central Operational Processor .............................................................................. 29
3.2.3.2.2 Central Storage Processor .................................................................................... 29
3.2.3.2.3 Display Processor.................................................................................................. 29
3.2.3.2.4 Web server processor ........................................................................................... 29
3.2.3.3 Network Equipment ................................................................................................... 29
3.2.3.4 Other Equipment ....................................................................................................... 29
3.2.3.4.1 KVM....................................................................................................................... 29
3.2.3.4.2 Printer (PR)............................................................................................................ 29
3.2.3.4.3 Timeserver (TS) .................................................................................................... 29
3.2.4 Remote operator site ........................................................................................................ 30
3.2.4.1 General...................................................................................................................... 30
3.2.4.2.1 Display Processor.................................................................................................. 31
3.2.4.2.2 Enhanced Display Processor ................................................................................ 31
3.3 HWCI Description .................................................................................................................... 33
3.3.1 VHF .................................................................................................................................. 33
3.3.1.1 Radio ......................................................................................................................... 33
3.3.1.2 Antenna ..................................................................................................................... 33
3.3.2 AIS .................................................................................................................................... 33
3.3.2.1 Base station (BS) ...................................................................................................... 33
3.3.2.2 Antennas ................................................................................................................... 33
3.3.3 Radar ................................................................................................................................ 33
3.3.3.1 Transceiver................................................................................................................ 33
3.3.3.2 Antenna ..................................................................................................................... 33
3.3.3.3 Video Processor ........................................................................................................ 34
3.3.4 Time Server (TS) .............................................................................................................. 34
3.3.4.1 Antenna ..................................................................................................................... 34
3.3.5 Computer Systems ........................................................................................................... 34
3.3.5.1 Server Computer ....................................................................................................... 34
3.3.5.1.1 Tape Drive ............................................................................................................. 34
3.3.5.2 KVM Switch (KVM) .................................................................................................... 34
3.3.5.3 Server Cabinet .......................................................................................................... 34
3.3.5.4 Workstation Computer .............................................................................................. 34
3.3.5.4.1 LCD Screen ........................................................................................................... 34
3.3.5.5 Printer (PR) ............................................................................................................... 34
3.3.6 Network ............................................................................................................................ 34
3.3.6.1 Switch (SW) .............................................................................................................. 34
3.3.6.2 Router (RT) ............................................................................................................... 34
3.4 VTMIS Core Subsystems and CSCI description ..................................................................... 35
3.4.1 Operational data flow diagram.......................................................................................... 35
3.4.2 Main Operational Components and Data Flows............................................................... 36
3.4.3 Traffic Analysis and Replay .............................................................................................. 36
3.4.4 System Management and Control .................................................................................... 36
3.4.5 Radar Data Processor ...................................................................................................... 37
3.4.5.1 HTP ........................................................................................................................... 37
3.4.5.2 RACOMS................................................................................................................... 37
3.4.6 Central Operational Processor ......................................................................................... 37
3.4.6.1 Surveillance and Alerting........................................................................................... 38
3.4.6.1.1 Multisensor Target Tracking (TARGHITT) ............................................................ 38
3.4.6.1.2 Dead Reckoning (DR) ........................................................................................... 38
3.4.6.1.3 TFP: Identification.................................................................................................. 38
3.4.6.1.4 TFP: Alerting.......................................................................................................... 38
3.4.6.1.5 Grounding Prediction (GPE).................................................................................. 38
3.4.6.2 Route Management (ROSE) ..................................................................................... 38
3.4.6.3 AIS Router................................................................................................................. 39
3.4.6.4 ATI............................................................................................................................. 39
Page 5 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.4.6.5 AMS........................................................................................................................... 39
3.4.6.6 CMSAIS..................................................................................................................... 39
3.4.6.7 RDFINP ..................................................................................................................... 39
3.4.6.8 HYME ........................................................................................................................ 39
3.4.6.9 PLMMIS..................................................................................................................... 39
3.4.6.10 NEXUS ...................................................................................................................... 39
3.4.6.11 ARGOS manager ...................................................................................................... 39
3.4.6.12 ARGOS proxy............................................................................................................ 39
3.4.7 Display Processor............................................................................................................. 39
3.4.7.1 ARAMIS..................................................................................................................... 40
3.4.7.2 HYME GUI................................................................................................................. 40
3.4.7.3 EOS viewer ............................................................................................................... 40
3.4.7.4 RADAR GUI .............................................................................................................. 40
3.4.7.5 AIS GUI ..................................................................................................................... 40
3.4.7.6 CMS RDF GUI........................................................................................................... 40
3.4.7.7 CMS portal (Web browser)........................................................................................ 40
3.4.8 Central Storage Processor ............................................................................................... 40
3.4.8.1 LOGITREC ................................................................................................................ 41
3.4.8.2 LOGITREP ................................................................................................................ 41
3.4.8.3 ARCHIT ..................................................................................................................... 41
3.4.8.4 SICO.......................................................................................................................... 41
3.4.9 Web server processor subsystem .................................................................................... 42
3.4.9.1 DisplayLite (operational)............................................................................................ 42
3.4.9.2 COTRAX ................................................................................................................... 42
3.4.9.3 Advanced Data Server (operational) ......................................................................... 42
3.4.9.4 ADS Gateway (operational)....................................................................................... 42
3.4.9.5 Logit Data Recorder .................................................................................................. 42
3.4.9.6 ISURE ....................................................................................................................... 43
3.4.9.7 Logit Data Player ....................................................................................................... 43
3.4.9.8 ADS Gateway (replay)............................................................................................... 43
3.4.9.9 Advanced Data Server (replay) ................................................................................. 43
3.4.9.10 DisplayLite (replay).................................................................................................... 43
3.4.9.11 Portal ......................................................................................................................... 43
3.4.10 Portable Replay Processor ........................................................................................... 43
3.4.11 Enhanced Display Processor ........................................................................................ 44
3.4.12 MIS subsystem ............................................................................................................. 46
3.4.12.1 DataBase Client Processor ....................................................................................... 46
3.4.12.2 DataBase Server Processor...................................................................................... 47
3.4.12.3 Voyage Planning ....................................................................................................... 47
3.4.12.4 Resource Management............................................................................................. 48
3.5 Tools Definition ........................................................................................................................ 48
3.5.1 Reference System Processor........................................................................................... 48
3.5.2 Sensor Performance Analysis and Simulation ................................................................. 48
3.5.3 Network Tools................................................................................................................... 48
3.5.4 Configuration Tools .......................................................................................................... 48
3.6 Internal Interfaces .................................................................................................................... 49
3.6.1 Communication Protocols ................................................................................................ 49
3.6.2 Network Configuration Data ............................................................................................. 49
3.6.3 External Data Streams ..................................................................................................... 49
3.6.4 Internal Data Streams....................................................................................................... 49
3.6.5 Maps and Parameter Data Files....................................................................................... 49
3.6.6 Change Notifications ........................................................................................................ 50
4. SYSTEM STATES AND MODES..................................................................... 51
5. PROCESSING RESOURCES.......................................................................... 52
5.1 Processing resources .............................................................................................................. 52
5.2 Operating system..................................................................................................................... 52
5.3 Supported browsers................................................................................................................. 52
5.4 Log file location ........................................................................................................................ 52
Page 6 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
6. QUALITY FACTOR COMPLIANCE ................................................................. 53

6.1 Introduction .............................................................................................................................. 53
6.2 Operational and Environmental Conditions for the Analysis.................................................... 53
6.3 Analysis and Mathematical Model ........................................................................................... 54
6.3.1 Reliability .......................................................................................................................... 54
6.3.2 Maintainability ................................................................................................................... 55
6.3.3 Availability......................................................................................................................... 55
6.4 Data Sources ........................................................................................................................... 55
6.5 Results of the Analysis............................................................................................................. 56
7. REQUIREMENTS TRACEABILITY ................................................................. 59
APPENDIX A LIST OF FIGURES............................................................................. 60
APPENDIX B LIST OF TABLES .............................................................................. 61
APPENDIX C ABBREVIATIONS .............................................................................. 62
APPENDIC D LIST OF DESIGN REQUIREMENTS ................................................. 63
Page 7 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
1. INTRODUCTION
1.1 Identification
Title: System/Segment Design Document
Subject: Standard Vessel Traffic Management and Information System (VTMIS)
Mnemonic: SSDD
Revision: 11
Status: Approved
6NC code: 00-08-22
Creation date: 2006-04-23
Revision date: 2011-03-07
1.2 Scope
This document contains the general design of a V3000 VTMIS system. When this design is used in a
particular project, an additional, project-specific design document describes the exact implementation of
this design for that particular project and details the project-specific deviations from this general design.
1.3 Document overview

The SSDD specifies the architecture and allocates requirements to subsystems for the V3000 VTMIS
system. After approval and authentication of the project-specific design document, this SSDD, in
conjunction with the project-specific design document, becomes the Allocated Baseline for the project.
1.4 Referenced documents
Refer. Title Identification code

[CGM] Information Processing Systems--Computer ANSI/ISO 8632-1992, ISO
Graphics Metafile for the Storage and Transfer of 8632-4 Part 4: Clear Text
Picture Description Information Encoding
[IALA-VTS] IALA Vessel Traffic Service Manual VTS Manual, 2002
[ISO-9126-1] Software Engineering – Product Quality – Part 1: ISO/IEC 9126-1:2001
Quality Model
[NTP-v3] Network Time Protocol (Version 3) Request for Comment 1305
Specification, Implementation and Analysis
[RAD-CID] - Software Interface Specification for TC3 and 262020 SI
Connected Units
- Interface Requirements Specification for the 00-03-96.IRS, 1998
Video Extractor Mk3
[S-52] Specifications for chart content and display aspects IHO Special Publication 52
of ECDIS
[S-57] IHO Transfer Standard for Digital Hydrographic Data IHO Special Publication 57
[PELCO-CID] Pelco Engineering “D” Protocol Manual TF-0001 Version 4 Rev. 1
[FS] V3000 VTMIS Functional Specification 00-08-22.FS
[SPA] V3000 VTMIS Specification Administration 00-08-22.SPA
[AIS-CID] AIS Transponder Interface 00-08-22.CID-AIS
[HYME-CID] HYME interface description 00-08-22.CID-HYME
[RDF-CID] V3000 VTMIS Interface Document for the RDF 00-05-46.CID-RDF
[VHFCOM-CID] V3000 VTMIS CID - VHF Sub-System 00-08-22.CID-VHF
[MIS-CID] CID-HITT VTS-KSG MIS 00-05-81.CID-MIS
[MIS-FS] MIS - Management Information System 00-08-45.FS-MIS
[LODI] V3000 VTMIS List of deliverable items 00-08-22.LODI
[IFHITT] Interface Requirements Specification for IFHITT 00-02-31
[INI] Software User Manual for INIFILE 00-01-62.SUM.INIFILE
[VDD] V3000 VTMIS Version Description Document 00-08-22.VDD
Page 8 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
For versions of V3000 VTMIS documents, please refer to the Version Description Document [VDD].
1.5 Terminology
The following terminology is used throughout the document:
HWCI
A HardWare Configuration Item. For example, a workstation computer, a radar transmitter/receiver or a
network switch.
CSCI
A Computer Software Configuration Item, for example Aramis MkII or TargHITT.
Application
An executable computer program. It is a part of a CSCI.
Subsystem
A combination of HWCIs and CSCIs to implement a logical group of functions. For example, the DP
subsystem consists of a HWCI (the workstation computer) and a set of CSCIs (Aramis MkII, MIS and so
on) and implements the functionality of a VTMIS working position. Another example of a subsystem is a
radar (transceiver, antenna, gear box, etc.).
Product
A set of subsystems that implement a well-defined set of functions. For example, the V3000 VTMIS
Product implements the functions, as defined in the V3000 VTMIS Functional Specification [FS], by means
of sensors, networks, DPs, COPs etcetera.
Page 9 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
1.6 System overview

A V3000 VTMIS system consists of a number of subsystems (figure 1). These subsystems can be divided
into the VTMIS Core subsystems, i.e. the subsystems that are delivered with every instantiation of a V3000
VTMIS system and optional subsystems. There are two reasons for a subsystem being optional: one
reason is that the system is already present and will not be replaced, for example, an existing
Communication Subsystem. In that case, the subsystem will be integrated as a project-specific option.
Another reason is that not all customers will need every subsystem as depicted in figure 1. This applies, in
particular, to the Electro-Optical (EO) Subsystem (e.g. CCTV) and the Domestic Subsystem.
Figure 1 VTMIS Subsystems Overview
Another reason to make the distinction between the VTMIS Core Subsystems and the other subsystems in
figure 1 is that the other subsystem are mostly or completely off-the-shelve systems. The V3000 VTMIS
system is designed to interface with all these subsystems. Obviously, the descriptions, specification- and
implementation details of these subsystems are vendor-specific. Where necessary, a reference will be
made to this documentation.
In the following sections, the VTMIS Core subsystems will be described in more detail as well as the
integration of the VTMIS Core subsystems with
• the Radio Direction Finder Subsystem.
• the AIS Subsystem.
• the Hydro/Meteo Subsystem.
• the Communication Subsystem.
• the Management Information Subsystem.
• the Radar Subsystem. and
• the Electro Optical Subsystem.
1.7 Operational concept

The purpose of a V3000 VTMIS system is to support a Vessel Traffic Services (VTS) Centre in its task to
deliver [IALA-VTS]
• Information Service.
• Navigational Assistance Service.
• Traffic Organisation Service.
Obviously, the target level of service of the VTS Centre determines the level of sophistication of the (to be)
realised VTMIS system. The full V3000 VTMIS system covers all functionality that is needed for the highest
level of service, i.e. the Traffic Organisation Service.
Page 10 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
The implementation of the required functionality (as presented in [FS]) is driven by the way different users
interact with the system. Within the V3000 VTMIS system, there are several different types of working
positions; the type of working position determines which Human/Machine Interface (HMI) elements are
available and how they will be presented to the user. Since the primary task of the VTS Centre is to support
the on-board navigational decision making, the key working positions are the VTS Operator working
positions. These working positions are described first.
1.7.1 VTS operator

The VTS Operator working position is the main working position in the VTMIS system. It provides VHF
communication and presents a traffic overview to the VTS Operator. The number of VTS Operator working
positions is determined by the extent and responsibility of the VTS centre. The minimum number of working
positions in the system is two: one operational and one fall-back.
Each working position is designed to support the operational role with a minimum amount of operator
interaction. The working position screen layout is depicted in Figure 2. Operator items are indicated in blue.
Figure 2 VTS Operator Working Position

The VTS Operator working position supports the following capabilities:
• traffic monitoring:
• Traffic Presentation
• Track Identification
• Dead Reckoning
• Alerting per track
• Sector selection.
• traffic planning:
• View vessel details.
• View job and voyage and status.
• Notifications
• Actual Time of Arrival
• Incidents registration
• Hydro / meteo, i.e. the actual measurement of
• wind
• air
• precipitation
• water
• wave height.
1.7.2 Supervisor / planner

The Supervisor working position supports the same functions as a VTS Operator working position, but with
the following additional capabilities:
Page 11 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• traffic monitoring:
• Edit maps.
• Modify the default alerting settings.
• traffic planning:
• Create and edit vessel details.
• Create and edit jobs, voyages and their status.
• Cargo management.
• Maritime Pollution monitoring.
The Supervisor/Planner working position is shown in Figure 3; Supervisor/Planner items are indicated in
yellow.
Figure 3 Supervisor / Planner Working Position
1.7.3 Replay / analysis

The replay / analysis working position provides the tools for analysing recorded VTMIS data. The first type
of analysis is the replay of an operational situation. The control of the replay consists of the selection of a
particular date and time at which replay will start and the speed at which the replay takes place (real-time or
fast-time). The different types of recorded data streams are replayed synchronized with each other, i.e.
• the traffic image
• Hydro / Meteo data
Page 12 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Figure 4 Replay / Analysis Working Position
The fact, that the data is replayed as it occurred at the time of recording, makes some functionality
unavailable during replay, e.g. identification of tracks is part of the recording and can not be (re-)done by
the replayer. The replayer can, however, change sectors, zoom and pan the traffic image to analyse the
replayed traffic situation in more detail. Replay/Analysis items are displayed in green.
The second type of analysis concerns the planning information that is contained within the MIS database.
The analyser can query the database to get reports and audit trails for in-depth analysis of voyages and
voyage-related information that is stored in the database.
Alternatively, a portable replay working position is available. This notebook based node offers standalone
replay capabilities for operator convenience.
1.7.4 Maintenance
Figure 5 Maintenance Working Position

The maintenance working position has the same capabilities as the supervisor position. Additionally, the
maintenance working position has access to the more technical configuration of the VTMIS system.
Maintenance items are indicated in rose. The maintenance working position includes the following
capabilities:
• traffic display:
• Creation and editing of routes, zones, lines.
• raw sensor data evaluation:
• Radar video
Page 13 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• Radar plots
• AIS tracks
• Surveillance tracks.
• administration:
• Creation of berths, locations, waypoints.
• Backup / restore database information.
• Archive system recordings.
• control and monitoring:
• Monitoring the status of the entire system.
• Monitoring the status of subsystems.
• Starting and stopping of computers throughout the system.
• Configuration of sensors
- Radar
- AIS
- RDF
- Hydro/meteo
- EOS (ARGOS)
• Control over the automatic archiving.
• maintenance terminal access:
• Access to system logs.
• Remote login to computer nodes.
• Low-level configuration changes.
• Administration of the Operating System.
Page 14 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
1.7.5 Remote maintenance and support
Figure 6 Remote Maintenance Working Position

The Remote Maintenance Working Position has the same capabilities as the Maintenance Working
Position, described earlier. It is primarily intended for second-line support, i.e. resolution of problems that
require specialist support. The Remote Maintenance Working Position is actually hosted on the VTMIS
system itself. The HMI is accessed through a thin client architecture. This makes it possible to access the
system across a possibly low-bandwidth network link. The remote maintenance engineer can either initiate
a separate session or access an existing session at a designated Maintenance Working Position.
Note that this remote session is running across an encrypted link and requires special authorisation.
Page 15 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
2. SYSTEM DESCRIPTION
2.1 General
The following sections describe the system from a functional component point of view. A functional
component is a set of logically related functions like, for instance, alerting. First, the most important
functional components of the system are described. Next, each of the functional components will be
mapped on relevant configuration items.
Page 16 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
2.2 System functions
Page 17 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Figure 7 V3000 Functions and their Relations
Page 18 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
2.2.1 General
Figure 7 shows a fairly abstract overview of the V3000 VTMIS system functions. These functions are
described in more detail in the next section. Note that the HMI functions, that are displayed separately here,
are usually integrated, i.e. they are displayed at the same screens (multi-function display). The arrows in
figure 7 indicate a “uses” relation.
Some functions, such as routing and alerting, rely on the results of underlying functions, in particular the
surveillance and identification functions. These underlying functions are always part of a V3000 VTMIS
system. Other functions are more or less independent, e.g. communications, analysis & replay and the
voyage and resource planning (MIS), or represent optional functionality, like routing. These functions could
be replaced by already existing or alternative solutions that either need to be integrated into the V3000
VTMIS at the customer's discretion or be left out entirely if an option is not exercised by the customer.
The V3000 VTMIS standard product assumes that all functions will be available and, by default, integrated
in the system.
2.2.2 Operational system functions

The operational system functions in figure 7 are:
• Video processing.
This function performs measurement extraction (if not done in the respective sensor subsystem) from
the radar. Input is radar video. Output are plots and digitised video.
• Interface software.
This function performs duplication removal and the necessary data validation, format conversion and
protocol conversion for sensor data.
• Tracking.
Based on sensor measurements, a consistent traffic image is constructed. For tracked targets, at least,
actual positions and speed vectors are maintained.
• Identification.
Based on either manual input from Operators, data from the MIS or AIS data, received from the target,
targets are identified with the ship name, call sign or a designated text.
• Alerting.
Provide notifications to the VTS Operator about unusual and/or potentially dangerous situations.
• Routing.
A ship can be attached to a defined route. The routing functions provide scheduling information and
notifications on route deviations.
• MIS Voyage and Resource Planning.
The VTMIS system maintains planning and identification information in the MIS database.
• Communication Interfaces.
Controls the VHF radios and interfaces voice data with the radios.
• Communications HMI.
The control of the VHF radios.
• Traffic planning HMI.
The interface with the MIS.
• Traffic display (operator).
The actual overview of the traffic situation.
• EOS viewer
A mosaic of images of a number of cameras.
2.2.3 Supporting system functions

The supporting system functions in figure 7 are:
• Recording.
The VTMIS data processing information is logged to disk.
Page 19 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• Replay.
Logged VTMIS data processing information can be replayed to designated working positions for
analysis purposes.
• Archiving
Logged VTMIS data processing information can be archived to a tape and can be retrieved from the
tape for replaying purposes.
• Control and Monitoring (CMS)
System status reporting and system maintenance.
• CDM support. Support CDM users with the actual overview of the traffic situation.
2.2.4 External sensor subsystems
2.2.4.1 AIS
The Automatic Identification System (AIS) is a VHF-based transponder system. It reports the ship's position
at regular (but variable) time intervals. Additionally, AIS allows for two-way communication between ship
and shore by means of short messages. AIS is increasingly becoming more important for traffic
surveillance because the AIS position reports the target identity as well as its position.
AIS is sensitive to disturbances of the Global Positioning System (GPS) signals, which may result in
reported positions that are way off the real position. Another important source of errors is transponder
configuration. This may affect both the reported identity and reported positions of ships. AIS base stations
are used to send and receive the AIS messages. The AIS base station complies to [AIS-CID].
2.2.4.2 Domestic signalling

Domestic signalling mainly concerns
• doors opened/closed
• presence of (maintenance) personnel at a given location
• fire alarms
• ambient temperature.
2.2.4.3 Electro optical

Electro Optical (EO) sensors are cameras, e.g. daylight cameras, thermal imaging cameras or laser gated
cameras. The EOS subsystem is called ARGOS within the V3000 system.
The cameras can be mounted on a fixed position or on a controllable pan/tilt unit. The PTZ information will
be depicted on the traffic display.
2.2.4.4 Hydro/meteo
There is a large variety of hydrographical and meteorological sensors that can provide information to the
VTS Operator, e.g.
• thermometers
• wind direction and wind speed sensors
• water level sensors
• water current meters.
The Hydro/Meteo subsystem complies to [HYME-CID].
2.2.4.5 Radar
Radar sensors are the primary means of traffic surveillance. VTMIS radar sensors generally operate in the
X-band. Radar sensors provide
• a real-time radar video image of the radar coverage area
• position and size of potential targets.
VTMIS radar sensors do not provide target identifications of any kind.
Page 20 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Note that radar measurements may be disturbed by breaking waves, reflections and adverse weather
conditions. The communications with the radar transceiver comply to [RAD-CID].
2.2.4.6 RDF
Radio Direction Finders report the direction of received VHF signals. So, whenever a ship uses its VHF
radio, the intersection of RDF lines on the traffic display will indicate the (approximate) position of the ship.
This provides the VTS Operator with a basic means to identify ships on a traffic situation display. The RDF
interface complies to [RDF-CID].
2.2.5 Other subsystems
2.2.5.1 Management information system

The Management Information System (MIS) is a complete and separate system that can be integrated into
the V3000 VTMIS system. The MIS-VTMIS interface specification is detailed in [MIS-CID].
2.2.5.2 VHF communication system

The primary means of ship-to-shore communication is VHF radio. Each VTS Operator has to have access
to VHF radio at the relevant channels for his area of responsibility. As such, the VHF Communications
subsystem is an important element of a V3000 VTMIS system. The VHF Communication System
(VHFCOM) is a complete and separate system that can be integrated into the V3000 VTMIS system. The
VHFCOM-VTMIS interface specification is detailed in [VHFCOM-CID].
2.3 Redundancy concept

The VTMIS system contains a number of redundancy provisions that help increase the system's availability.
The following types of redundancy are provided:
• power redundancy
• network equipment redundancy
• HWCI / CSCI redundancy.
These types of redundancy are described in the following paragraphs.
2.3.1 Power redundancy

A critical factor for the availability of the V3000 VTMIS system is the provision of stable mains power at the
equipment sites, including the VTS centre. Especially in the case of frequent power interruptions and/or
noisy mains power, Uninterruptable Power Supplies (UPSs) must be used to maintain the target availability
figures of the V3000 VTMIS equipment. This is a project-specific issue.
2.3.2 Network
The V3000 VTMIS system uses an Ethernet network to interconnect its various subsystems. Remote sites
are connected via a Wide-Area Network (WAN). The type of WAN is a project-specific design issue,
depending on the required bandwidth between local- and remote sites, but also on the possible
infrastructure (consider e.g. a radar located on an island). The network redundancy, discussed here,
applies to the V3000 VTMIS LANs.
Page 21 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Figure 8.Basic fault-tolerant networking concept

By default, V3000 VTMIS distributes the servers and clients over the switches in such a way, that:
• if a LAN segment to a client (display) fails, the system will continue full operation, losing only one
display.
• if a LAN segment to a server fails, the system will switch over, preserving its functionality. However the
clients (displays) connected to the switch with the faulty LAN segment will not operate any more. The
clients that were connected to the faulty switch can be made available again by re-connecting them to
the operating switch.
The concept described above is simple and effective and commonly used. The reliability of LAN-cables is
very high (typically more than 200,000 hours), which makes a switch-over as a result of failure of a LAN
segment very rare. As such the concept above provides a cost effective, proven and reliable solution for
most situations.
2.3.3 HWCI / CSCI redundancy

Redundancy of computer hardware can be realised in any of the following ways:
• hot standby.
In this configuration two or more computer nodes with the same application are running in a
configuration where one application is online and the other(s) are offline. The online application
produces output. The online and offline applications listen to each other's heartbeat. If the offline
application notices that the online application fails, it decides to become online itself. This mechanism
requires that the online application informs the offline application about a number of critical aspects for
synchronisation, allowing a fast switch-over.
HITT uses this hot standby technique particularly for its Central Operational Processing (COP), which
houses the most critical functionality.
• multiple computation.
In this configuration two or more computer nodes of the same type are running in parallel without
mutual synchronisation. This mechanism is used in situations where data can be processed
independently or when replication of data is allowed. The advantage of this mechanism is its simplicity,
since no switch-over is required. Adding more computer nodes of the same type can increase the
availability. HITT applies this concept for example for radar data processing and for recording and
replay.
• pooled resources.
In this case more instances of the same resource are used in a pool. Pooled resources can be used to
provide a contingency area, to be used for example to continue centre operation in case of an
emergency situation, that requires an evacuation of the operational area.
A typical example of a pooled resource is the operator working position. Pooled resources can only be
applied on the client side of the client-server architecture.
These mechanisms can be combined with geographical redundancy by placing the redundant equipment
on different locations and with overlapping sensor coverages by adding sensors such that critical areas are
covered by more than one sensor. In this way local power failures will have less impact on the overall
performance of the system.
Page 22 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3. SYSTEM DESIGN
3.1 Architecture
3.2 General
Figure 9 shows a possible V3000 VTMIS system with two remote sensor locations, one VTS centre, one
remote operator site, and a remote maintenance position. The remote locations are connected to the VTS
Centre via wide-area networks (WANs). The type of WAN is a project-specific item. It can be a dedicated
fibre optic link, a microwave link or even an ISDN telephone link, depending on the required bandwidth
between remote location and VTS Centre. Note that, for the design of the V3000 VTMIS system, it is not
really relevant what the exact type of WAN is, only the fact that there is a data link with certain
characteristics.
Figure 9 Location Overview
The following sections detail the site-specific networks that are part of this specification.
Page 23 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.2.1 VTMIS network
Figure 10 Example V3000 VTMIS Network Configuration
Page 24 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.2.2 Sensor Site
3.2.2.1 General
Figure 11 shows the architecture of a sensor site with a modular configuration. Based on the configuration,
the site combines different sensors, all reporting their measurements to the VTS centre. The most obvious
reason to combine these several sensors is to reduce the cost of infrastructure. Site configurations can be
made simpler by omitting particular modules. Modules may also be included more than once, to allow for,
for example, multiple hydro/meteo sensors on one site.
Figure 11 Modular configuration Sensor Site

The computer equipment, base stations and network switch are placed in a 19” cabinet.
3.2.2.2 Sensor and Communication Modules
3.2.2.2.1 Module AIS

The AIS module of figure 11 incorporates AIS base stations for transmitting and receiving AIS messages.
The AIS configuration consists of
• a base station with VHF and GPS antennas
• a second, redundant base station (optional, not displayed).
3.2.2.2.2 Module General

The general module contains equipment which will likely be employed at every sensor site. It includes:
Domestic signalling (DOM)
Domestic signalling concerns registration of the following on-site events:
Page 25 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• doors opened/closed
• fire alarms
• personnel present/not present.
Note that the radar hardware has a limited number of inputs for domestic signalling. It is usually not
necessary to have dedicated domestic signalling hardware at a sensor site.
Uninterruptible power supply (UPS)
Computer equipment, communication equipment and low powered sensors benefit from an uninterruptible
power supply to bridge short power failures. Controlled shutdown of computer equipment allowed by the
uninterruptible power supply is not required by the robustness of the hardware and software that is used.
Power Supply Switch (PSS)
With a secure, remotely controllable power supply switch, specific equipment may be turned on or off, in
case maintenance servicing said equipment warrants it.
Ethernet Switch (SW)
A layer 2 Ethernet switch connects all relevant equipment to the network of the VTS.
3.2.2.2.3 Module Hydro/Meteo

Hydro/Meteo equipment is often combined with other sensor modules, such as RDF, radar, or AIS. The
Hydro/Meteo subsystem is equipped with an Ethernet network interface. It consists of one or more sensors
and, if necessary, one or more thin terminal servers (TTS) to provide the Ethernet interface.
3.2.2.2.4 Module Single Radar

The single radar configuration consist of
• a rotating radar antenna with motor, gear box and wave guides.
• a single radar Transmitter/Receiver.
• a Radar Service Display.
• a single Radar Data Processor.
• an LCD keyboard, video, mouse switch.
3.2.2.2.5 Module Dual Radar

The dual radar configuration consist of
• a rotating radar antenna with motor, gear box and wave guides.
• a dual, redundant radar Transmitter/Receiver.
• a Radar Service Display.
• a dual, duplicated Radar Data Processor.
• an LCD keyboard, video, mouse switch.
3.2.2.2.6 Module Low-Cost Radar

The Low-Cost radar configuration consist of
• a rotating radar antenna with motor, gear box and transmitter/receiver.
• an LMS/PC interface adapter.
• a single Radar Data Processor.
• a keyboard, mouse and monitor
3.2.2.2.7 Module RDF

The RDF configuration in figure 11 consists of a RDF with an Ethernet network interface. If necessary, a
thin terminal server is used to provide the Ethernet interface.
Page 26 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.2.2.2.8 Module VHF

The VHF radio including interface equipment is connected to the IP network.
3.2.2.2.9 Module EOS

The EOS camera is connected to the IP network, through a dedicated video encoder. The module consists
of
• a pan / tilt unit
• a daylight camera with zoom lens
Optional the EOS module can be extended with:

• a thermal imaging camera
• laser gated camera
• stable eyes unit
• video tracking unit
3.2.2.3 Computer Equipment
3.2.2.3.1 Radar Data Processor

The Radar Data Processor (RDP) subsystem is a server computer with dedicated hardware and software
for the digitisation of the returned radar signal (video) and the extraction of plots, i.e. potential targets, from
the radar video. The RDP also contains the remote control interface to the radar transceiver. The RDP is
single or duplicated. The RDP is connected to the LAN by two separate Ethernet connections; one for main
operational use, and one connected to the server’s ILO port, in order to allow remote maintenance through
this feature.
3.2.2.3.2 Radar Service Display

The Radar Service Display (RSD) subsystem is a computer with radar-vendor specific software for data
display, control and tuning of the radar transmitters/receivers and antenna.
3.2.2.4 Network Equipment

The server computers, base stations, RDF- and Hydro/Meteo interfaces are connected to a switch. The
switch is connected to the VTS LAN or a WAN. In the latter case, the switch may be able to act as a router
or a separate router is required. This is a project-specific design issue.
3.2.2.5 Other Equipment

The server computers are connected to a KVM switch with a display, keyboard and mouse.
Page 27 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.2.3 VTS Centre Site
3.2.3.1 General
Figure 12 shows a typical VTS centre site with the 5 typical working positions, as described in section 2.2.
The remote maintenance working position is not normally part of the delivery of a V3000 VTMIS system
(hence the shading), but is, nevertheless, part of the design. A remote maintenance position is generally
connected to the V3000 VTMIS system via a Virtual Private Network (VPN) on an as-needed basis.
The number of working positions can be adapted to fit the needs of a particular VTS area (see also [IALA-
VTS]). The minimum number of working positions is three:
• A maintenance working position in the equipment room.
• Two VTS operator working positions in the operational room.
One VTS operator working position is the operational position. The second working position can be used as
• spare VTS operator working position
• supervisor/planner working position
• replay/analysis working position
Figure 12 VTS Centre Site
The computer and network hardware is placed into two 19” cabinets. Redundant equipment is distributed
across the two cabinets. Each cabinet is equipped with a KVM with a display to operate the server
computers. The cabinets and a maintenance working position are located in a dedicated equipment room
that guarantees proper environmental conditions for the equipment (a project-specific design issue).
Page 28 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.2.3.2.1 Central Operational Processor

The Central Operational Processor (COP) is a server computer with software to track targets of interest,
based on sensor measurements, and also serves to interface the various sensor data and the plan data
from MIS with the data processing software. The COP is delivered in a dual, redundant configuration with
one COP in each cabinet (COP01 and COP02). Each server is connected to the LAN by its Ethernet port of
the LAN adapter, as well as its ILO Ethernet port.
3.2.3.2.2 Central Storage Processor

The Central Storage Processor (CSP) is a server computer with software to record and replay traffic data,
and to monitor and control the status of subsystems and applications within the V3000 VTMIS system. The
CSP is delivered in a dual, redundant configuration with one CSP in each cabinet. Control and monitoring
functions are kept on the CSP01 only. Each server is connected to the LAN by its Ethernet port of the LAN
adapter, as well as its ILO Ethernet port.
3.2.3.2.3 Display Processor

The Display Processor (DP) is a workstation computer with software to display the traffic situation, to
display the EOS camera video, to access the MIS database, replay and analyse traffic situations and to
monitor and control the V3000 VTMIS system. The actual applications that are presented to the user
depend on the role of the working position.
There are three working positions with large, dual LCD displays (DP01, DP02 and DP03) for traffic situation
display and one working position with one LCD display for maintenance (DP04)
3.2.3.2.4 Web server processor

The web server processor (WSP) is a server computer with software to provide the CDM users the traffic
situation picture. It includes software for recording and replay and user authentication and authorization.
The WSP is delivered in a single configuration WSP01.
3.2.3.3 Network Equipment

The server computers in each cabinet are connected to a switch, located in the same cabinet as the
servers (SW01 and SW02). The central layer 3 switch, SW01 also acts as a central router for the entire
network.
3.2.3.4 Other Equipment
3.2.3.4.1 KVM
The server computers in each cabinet are connected to a KVM switch with a display (KVM01 and KVM02).
3.2.3.4.2 Printer (PR)

A printer for printing reports and screen dumps is attached to the VTS centre LAN.
3.2.3.4.3 Timeserver (TS)

The timeserver is equipped with a GPS antenna and is used to accurately synchronise the time on the
computer systems in the V3000 VTMIS.
Page 29 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.2.4 Remote operator site
3.2.4.1 General
The figure below shows a remote operator site. This is a site not on the same physical site as the VTS
centre, but where operators are active, working with the system. It consists of one or more working
positions, connected to the V3000 VTMIS system via the WAN. This way, the centrally generated traffic
image can be available to various operator, positioned potentially hundreds miles apart.
Figure 13 Remote operator site
Page 30 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Alternatively, the remote operator position can consist of one workstation that, besides display of the
centrally generated traffic image, also has local tracking capabilities, separately available from the centrally
generated traffic image. Based on one or more local sensor sites, which are also connected to the central
location, this working position has a fallback capability for tracking.
Figure 14 Remote operator site
3.2.4.2.1 Display Processor

The Display Processor (DP) is a workstation computer with software to display the traffic situation, to
display the EOS camera video, to access the MIS database, replay and analyse traffic situations and to
monitor and control the V3000 VTMIS system. The actual applications that are presented to the user
depend on the role of the working position.
3.2.4.2.2 Enhanced Display Processor

Instead of opting for a standard Display processor, an Enhanced Display Processor may be used. The
Enhanced Display Processor (EDP) is a workstation computer with software to display the traffic situation,
to access the MIS database, replay and analyse traffic situations and to monitor and control the V3000
VTMIS system. The actual applications that are presented to the user depend on the role of the working
position.
Besides that, the EDP performs local tracking, based on predefined remote sensor sites, with radar and/or
AIS, which offers a subset of the total traffic image, available on the working position as a fallback option in
case the link to the central site should fail. Examples of implementations of such a working position may be
Page 31 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
a remote island with local sensors, with a wireless or sea-line link, which may be difficult to quickly restore.
In such cases, local tracking can guarantee a minimum of disturbance for operational personnel.
Page 32 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.3 HWCI Description

The following sections describe the various hardware items that are used in the V3000 system. This is a
generic description. A detailed description and specification of hardware items is given in the “List of
Deliverable Items”.
3.3.1 VHF
3.3.1.1 Radio
A project-specific item.
3.3.1.2 Antenna
A project-specific item.
3.3.2 AIS
3.3.2.1 Base station (BS)

An AIS base station
• receives identified ship positions from an AIS transponder over a VHF link.
• receives ship static data over a VHF link.
• sends and receives safety-related messages over a VHF link.
• sends AIS control messages over the VHF link.
• sends and receives application-specific binary data over the VHF link.
• Provides AIS transponders with DGPS position correction information.
A base station is compliant with standards documents as defined by [AIS-CID].
3.3.2.2 Antennas
An AIS base station requires two antennas:
• a GPS antenna
• a VHF antenna.
Optionally, base stations can be delivered in a redundant configuration; in that case, each base station may
have its own antennas or the antennas may be shared via a splitter.
3.3.3 Radar
3.3.3.1 Transceiver
The preferred radar transceiver is a X-band, 25kW transceiver. Note that, in areas with expected heavy
rainfall, a S-band radar may be more appropriate. The transceiver can be duplicated to increase the MTBF
figure. In such a case, the transceivers share the same antenna using a wave guide switch.
The interface of the radar transceiver is described in [RAD-CID].
3.3.3.2 Antenna
The preferred radar antenna is 18ft, has an fan-beam antenna pattern and horizontal polarisation. The
antenna rotation speed is approximately 20 RPM.
Note that radar performance requirements are very much dependent on the antenna characteristics.
Available antenna options include
• size, e.g. 18ft or 21ft.
• polarisation, i.e. linear (horizontal or vertical), circular or switchable.
•
2
antenna pattern (fan-beam or inverse cosec ).
Page 33 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.3.3.3 Video Processor

The Video Processor is a dedicated processor board for signal processing and digitisation of the radar
receiver signals, i.e. the analogue or digital video signal, the azimuth and north signals and the radar
synchronisation. The VP operates in conjunction with the HITT extractor software HTP.
3.3.4 Time Server (TS)

The time server receives GNSS signals and uses these to calculate a very accurate time reference. The
time reference is distributed using the standard NTP time protocol [NTP-v3].
3.3.4.1 Antenna
A time server requires a GPS antenna.
3.3.5 Computer Systems
3.3.5.1 Server Computer

A server computer system is the default computing platform.
3.3.5.1.1 Tape Drive

A tape drive is used for backup and restoration of recorded operational data and MIS database images.
3.3.5.2 KVM Switch (KVM)

A KVM switch is used in server cabinets to monitor and control the servers with a single keyboard, pointing
device and display. The KVM switch is mounted on a sliding rail and has a closable lid with a LCD screen
3.3.5.3 Server Cabinet

Server computers and the KVM switch are mounted in a 19” cabinet. Front- and back doors can be locked
and, optionally, be monitored for access.
3.3.5.4 Workstation Computer

Workstation computers are used for HMI applications. A workstation computer supports up to 2 display
screens.
3.3.5.4.1 LCD Screen

Depending on the presentation requirements, one or two 24” LCD screens are used: one screen, in case of
a maintenance working position, and two screens, in case of working positions where vessel traffic is
presented.
3.3.5.5 Printer (PR)

For printing reports and traffic situations, a colour laser printer is used.
3.3.6 Network
3.3.6.1 Switch (SW)

A switch is used to connect workstations and servers at a given location. Depending on the model of the
switch, it may have routing capabilities. This eliminates the need for a separate router. The switch is a
SNMP-manageable device. As an option to improve the MTBF figure, switches may be duplicated. This
means that connected systems will have duplicated network interfaces.
3.3.6.2 Router (RT)

Routers are used to interconnect different locations, e.g. a radar site with the VTS centre.
IP multicasting is used extensively within VTMIS; therefore, the router shall support multicast functions.
The router is a SNMP-manageable device. There are various options for the WAN-side of the router,
depending on the availability of existing WAN links and the needed data rate between the connected sites.
Page 34 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.4 VTMIS Core Subsystems and CSCI description
3.4.1 Operational data flow diagram
Figure 15 Operational data flow diagram

Page 35 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.4.2 Main Operational Components and Data Flows

Figure 15 shows the mapping of the functions of a V3000 VTMIS system onto component nodes. Each
such a component node is a subsystem. The figure also shows the main operational data flows between
the subsystems. Please note that there are more data connections than those that are depicted in this
diagram. The diagram displays only the main connections.
The subsystems involved are:

• Radar Data Processor (RDP). Processes the radar returns and generates a digitised radar image and
plots.
• MIS subsystem; control and data entry for the voyage / resource planning database, and MIS
application.
• Central Operational Processor (COP). Processes AIS, Hydro/Meteo, RDF and EOS messages.
Converts these message to VTMIS internal format. Surveillance data processing (radar- and AIS data),
routing and alerting.
• Display Processor (DP). Executes HMI applications.
• Enhanced Display Processor (EDP). Offers a mix of functionality of the COP, CSP, and DP. Is used
mainly as minimal VTS or as a backup VTS.
All of these subsystems are described in more detail in this chapter. The requirements of the VTMIS
Functional Specification are mapped onto these subsystems. This mapping is described in the Specification
Administration document [SPA]. The SPA document is part of the V3000 VTMIS system specification.
3.4.3 Traffic Analysis and Replay

Traffic Analysis and Replay are functions that are not directly needed for operational vessel traffic
management, but are required for such tasks as (near) incident investigation and statistics gathering.
These are the, so-called, system support functions.
A standard function of the system is to record the internal data streams and preserve these recordings for,
at least, a pre-defined amount of time. Relevant data can be replayed and, if needed, copied to a more
permanent storage location (e.g. tape). The recording and replay functions are allocated to the CSP.
Replay sessions are executed at the replay/analysis working position(s).
In addition to the operational data, display commands, like zoom and pan, are recorded as well to allow
replay of relevant operator actions on the traffic display.
Statistics collection concerns the recording of line passage and area entry/exit events, as well as planning-
related events (actual times of arrival/departure, waypoint passage) and registration of “unusual” events
(e.g. a collision warning).

• Central Storage Processor (CSP). Records and replays surveillance, voice, meteo and other date and
allows the data to be played back on a maintenance Display Processor (DP)
• Display Processor (DP). Provides applications and HMIs for the control of the playback and the
displaying of the recorded data. (Maintenance functions)
• Portable Replay Processor (PRP). Is a combination of the replaying part of the CSP and the DP and
provides means to replay the recorded data offline on a portable system.
3.4.4 System Management and Control

Another support function is System Management and Control. The system components are required to
provide status information and, if needed, to provide an interface for the control of software running on the
component and/or hardware connected to that particular component. If relevant, these statuses are
collected by the Control and Monitoring System application (CMS), executing on the CSP node. Control
commands are also routed through the CSP.
The System Management and Control HMI function is executed by the Display Processor (configured as a
System Management and Control Working Position).
Page 36 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07

• Central Storage Processor (CSP). Has a system monitoring and control function and provides access
for CMS portal (web clients)
• Display Processor (DP). Allows the maintainer to watch the system status, using a web browser.
(Maintenance functions)
3.4.5 Radar Data Processor

The Radar Data Processor subsystem (RDP) performs the following functions:
• Radar Control and Monitoring, i.e. make the main radar status and control accessible via SNMP
• Hit and Threshold Processing, i.e.
• control the Video Processor.
• receive digitised video, azimuth, north and radar sync information.
• extract plot positions and plot attributes.
The RDP subsystem executes on a server computer that contains a Video Processor board (indicated in
pink in Figure 15).
The RDP uses the Video Processor (VP) board to interface with the radar sensor. The VP board digitizes
the radar video and mixes the radar azimuth and sync.
The following CSCIs are part of the RDP
3.4.5.1 HTP
HTP calculates video threshold information from clutter measurements in the video and uses video-
extractor masks and the threshold information to generate “hits”. HTP uses hits to create radar video. It
also creates plots from the radar video. The plots are a simplified image with a length, width and
orientation.
3.4.5.2 RACOMS
RACOMS is used to monitor and control the radar. Messages, that concern the hit and threshold
processing, are passed on to HTP.
Note that, technically, the RDP is part of the Radar Subsystem (figure 1) since it only performs radar-
related functions and there will be no RDPs in the V3000 VTMIS system if no radars are used. This is very
unusual for a VTS system, though (see [IALA-VTS]).
3.4.6 Central Operational Processor

The Central Operational Processor subsystem (COP) is used for the following functions:
• multi-sensor target tracking using radar and AIS measurements (TargHITT/TargHITTINT)
• track identification and identification guarding (TFP)
• alerting (TFP)
• track grounding prediction (GPE)
• track dead reckoning (DR)
• route management (ROSE/ROMAS)
• interface, control and monitor with AIS
• interface, control and monitor with RDF
• interface with hydrographical and meteorological sensors
• interface with external plan system
• interface with EOS cameras
Page 37 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
The Central Processor subsystem executes on a server computer. The CSCIs that are part of the COP
subsystem, are described in more detail in the next section.
3.4.6.1 Surveillance and Alerting
3.4.6.1.1 Multisensor Target Tracking (TARGHITT)

The main surveillance component is the multisensor target tracker TargHITT. TargHITT uses
measurements from multiple radars and AIS to maintain a consistent traffic image. Tracking uses (Joint)
Probabilistic Data Association and Interacting Multiple-Model filters to estimate the track state vector. At the
same time, TargHITT maintains estimates of the probability of detection and clutter density in the radar
coverage area, as well as estimates of the sensor misalignments.
3.4.6.1.2 Dead Reckoning (DR)

Dead reckoning will predict a track position for every track that is lost in a dead-reckon area. The VTS
Operator can initiate a track to be dead-reckoned or the system can start dead-reckoning for tracks, lost in
a specified area. DR will simulate the track from the lost position using either the last reported speed and
course or the last reported speed and the route that is coupled to the track (resulting in a dead-reckoned
track). Note that the VTS Operator can change these settings. Dead reckon tracks are merged into the
system tracks data stream by the TFP CSCI.
3.4.6.1.3 TFP: Identification

The Identification function of the Track Fusion Processing (TFP) CSCI adds identification information to the
system tracks. The VTS Operator can set, change, swap and terminate a track identification. The
Identification function can identify buoys and couple sailing plans to tracks when a track matches an
expected departure or arrival. When an identified track is lost within predefined areas, the Identification
Guard function tries to find unidentified tracks in the neighbourhood of the old track to recover the
identification. Identifications are normally derived from the MIS and/or AIS; the VTS Operator may enter his
own identification when needed.
3.4.6.1.4 TFP: Alerting

The Alerting function of the Track Fusion Processing consists of a set of guarding functions, each covering
a distinct situation:
• buoy guarding
• anchor guarding
• track loss
• track guarding
• potential collision
• route adherence monitoring
• speed monitoring
• zone- and line guarding
• prohibit anchoring
Track Fusion Processing is performing the track selection for GPE. Tracks are selected for GPE if they are
within predefined areas unless the track is coupled to a route and is on that route. When such a track
leaves the route, it will automatically be predicted like the tracks that are not coupled to a route.
3.4.6.1.5 Grounding Prediction (GPE)

The grounding prediction warning function GPE uses depth information from ENC charts. GPE sends an
alarm containing the grounding location and polygon (in case the grounding object is a polygon (depth
contour), not a point object) to indicate a possible grounding event.
3.4.6.2 Route Management (ROSE)

Route management (ROSE) adds route navigation information, to the system tracks for display purposes
and ETA calculation. Note that sailing plans, as obtained from MIS, also contain route information at a more
Page 38 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
global level. The ROSE routes are more detailed than the MIS routes because they contain all the
waypoints a ship has to pass; the MIS routes contain only “major” waypoints.
3.4.6.3 AIS Router

The AIS router (AISROUTER) serves as a concentrator for multiple AIS shore-based resources. These
resources can be AIS base stations or AIS networks. The main function of the AIS router is to determine
which AIS resource should be used to transmit AIS messages to a particular vessel. The AIS Router can
also filter duplicate received messages.
3.4.6.4 ATI
The AIS Transponder Interface (ATI) processes the position reports, received from AIS base stations or
networks. ATI will automatically request the AIS ship static data report, in case the position report is
received from an, as yet, unknown ship.
Class A reports (normal update rate) and class B reports (low update rate) are sent on different channels.
ATI processes the AIS blocking data and makes the blocking statuses and thresholds persistent.
3.4.6.5 AMS
The AIS mail server (AMS) processes the text telegrams and safety related messages, broadcast as well
as addressed, received from AIS base stations or networks and from ARAMIS.
Also the acknowledgements for the addressed messages are processed.
The messages are distributed to the concerning users. All messages are stored for at least one year.
3.4.6.6 CMSAIS
CMSAIS is used to control and monitor AIS base stations connected to the AIS router.
3.4.6.7 RDFINP
Radio Direction Finder Interface Processing (RDFINP) reads the bearing information, as sent by the Radio
Direction Finder (RDF)-sensors, and translates it into the V3000 VTMIS internal data format.
3.4.6.8 HYME
HYME receives the hydro/meteo data in NMEA-formatted messages from connected sensors. HYME will
report hydro- and meteo data at (adjustable) time intervals. For the wind sensors, HYME calculates the
average wind speed and wind direction during the last 2 minutes.
3.4.6.9 PLMMIS
The Plan Management Services (PLMMIS) is responsible for the interface with MIS. MIS manages the
voyage-plans. PLMMIS receives messages from MIS in XML format and translates them into V3000 VTMIS
internal data format and vice versa. Also, route data is sent to the MIS, whenever it is updated, or when MIS
requests specific route data.
3.4.6.10 NEXUS
The IVEF converter (NEXUS) is responsible for output of system tracks and sailing plans in the system, by
means of the Inter-VTS Exchange Format (IVEF). This XML based format is a leading standard for
information exchange between different VTS systems, or other interested parties. IVEF is also the standard
HITT uses to interface with other HITT products, for seamless integration.
3.4.6.11 ARGOS manager

The EOS control (ARGOS manager) is responsible for the assignments of EOS cameras to the operator
positions. Furthermore ARGOS manager handles EOS tracking functions.
3.4.6.12 ARGOS proxy

For each EOS camera an ARGOS proxy interface converts the HITT camera commands and settings to
camera proprietary commands and settings e.g. as described in [PELCO-CID].
3.4.7 Display Processor

The Display Processor subsystem (DP) is used for data presentation and human interaction with the V3000
VTMIS. The working position configuration, i.e. the available applications and the screen layout, depends
Page 39 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
on the assumed role of the user. The DP may be configured to automatically start with a previously defined
default username, or the user is required to manually login on the DP with the desired role. The following
usernames are defined:
• operator
• supervisor
• replay
• maintenance
The following CSCIs are part of the DP:
3.4.7.1 ARAMIS
The traffic monitoring HMI ARAMIS displays the traffic situation image. This image consists of radar video,
system tracks, RDF lines and EOS camera field of views projected on a map of the system area. ARAMIS
allows users to identify tracks, i.e. a manual identification or an identification from the MIS database, query
information on tracks and assign tracks to routes for monitoring purposes.
3.4.7.2 HYME GUI

The Hydro/Meteo HMI HYMEGUI displays the actual values of various hydrographic and meteorological
sensors.
3.4.7.3 EOS viewer

The EOS viewer displays a mosaic of camera video images. The control of the cameras can be done from
the concerned camera window.
VDS00012 EOS viewer window dressing

The EOS viewer operates in one window, which supports the normal window dressing commands:
minimize, maximize, move, resize, full screen and noborder.
VDS00013 EOS camera window full screen

A camera window of a mosaic can be displayed full screen.
3.4.7.4 RADAR GUI

The CMS Radar HMI is used to monitor and control the operation of the radar antennas and transceivers.
3.4.7.5 AIS GUI

The CMS AIS HMI is used to monitor and control the operation of AIS base stations.
3.4.7.6 CMS RDF GUI

The CMS RDF HMI is used to monitor and control the operation of radio direction finders.
3.4.7.7 CMS portal (Web browser)

The CMS portal displays the actual statuses and status messages of the different V3000 VTMIS data
processing applications (Radar, AIS and RDF sensor processing and surveillance data processing),
through a web browser.
3.4.8 Central Storage Processor

The Central Storage Processor subsystem (CSP)
• Records VTMIS surveillance data streams.
• Records voice data.
• Replays recorded data.
Page 40 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• Handles off-line data storage and retrieval.

• Control and Monitoring System (CMS) server function
• Access point for CMS portal (using a Web browser)
The CSP subsystem executes on a server computer that contains a tape drive unit.
The CSP records the VTMIS internal data streams. The data is time-stamped and stored on disk for later
retrieval. The data is stored in files that cover 1-minute time intervals, ie. Each minute of data is stored in a
separate file. This includes sensor data, track data and voice data. Furthermore, track events are collected
for (later) statistical analyses. Examples of track events are line crossings and area entry or exit.
The CMS application receives status information from applications and subsystems. These messages are
used by CMS to monitor both the technical status and the operational status of the system. The technical
status includes errors/warnings and the operational status indicates whether the subsystem is fully
operational or not.
VDS00005 CMS monitored components
CMS can monitor the status of the following components:

• nodes;
• application processes;
• switches;
• video processor;
• time server;
• time synchronization;
• fire wall;
• printer;
• RAID-disk; and
• AIS interface.
The following CSCIs are part of the CSP:
3.4.8.1 LOGITREC
The LOGITREC recording application
3.4.8.2 LOGITREP
The LOGITREP data replay application
3.4.8.3 ARCHIT
The ARCHIT archiving application
3.4.8.4 SICO
The SICO track event collection application collects information about tracks based on events. These
events are stored
On-line recordings are done on a separate disk. The estimated amount of recording data determines the
size of the disk. This size covers at least the minimum on-line storage period as requested by the customer
(default is two weeks). As soon as size of the recordings reaches a certain threshold, older recordings will
be overwritten by new ones. Selected parts of the recorded data may be saved on a separate disk for later
analysis.
The CSP tape drive unit is used for off-line archiving and restoring of the recorded data.
Page 41 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.4.9 Web server processor subsystem

The web server processor subsystem (WSP) is used for the following functions:
• recording of system tracks and plans streams;
• replay of system tracks and plans streams;
• user authentication and authorization and
• traffic overview distribution (tracks data) to CDM users.
VDS00009 Use of HTTP protocol.

The communication of the WSP with the client computer for downloading and running DisplayLite applet is
HTTP.
VDS00010 CDM Traffic picture update rate

The traffic picture is continuously updates with the update rate of the system tracks.
The following CSCIs are part of the WSP:
3.4.9.1 DisplayLite (operational)

DisplayLite is the CDM Traffic viewer, a java applet which is downloaded from the WSP and is running on
the client computer.
Main functionalities:
• Visualize traffic data
• Filter data
• Search object
• Send/receive admin messages to/from ADS gateway
• Send/receive login messages to/from ADS gateway
In order to visualise the traffic situation the traffic monitor uses Java Runtime Environment Version 6. This
java plug-in must be available on the client computers.
VDS00007 Java runtime environment handling

If the correct JRE version can not be detected, the user is instructed how to acquire the correct version.
3.4.9.2 COTRAX
• converts system tracks and flight plan data into the XML format.
3.4.9.3 Advanced Data Server (operational)

• Handle user authentication
• Provide clients with data
• Handle user settings
3.4.9.4 ADS Gateway (operational)

This functionality is implemented as a servlet and it part of the DisplayLite CSCI.
• Receives and handles the login and administrator messages from the DisplayLite (operational)
applet.
• Handle user settings
• Receives the traffic data from ADS (operational) using a dedicated TCP/IP port and send it to
DisplayLite (operational) using HTTP communication.
3.4.9.5 Logit Data Recorder

• Record inputs data (for analysis purposes)
• Record output of COTRAX (for replay purposes)
Page 42 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• As soon as the size of the recordings reaches a certain threshold, older recordings will be
overwritten by new ones.
3.4.9.6 ISURE
• User interface to update the LDAP user administration
3.4.9.7 Logit Data Player

• Replays the recorded output of COTRAX
• Receives and handles the replay commands as received from ADS Gateway.
3.4.9.8 ADS Gateway (replay)

This functionality is implemented as a servlet and it part of the DisplayLite CSCI.
• Receives and handles the login and administrator messages from the DisplayLite (replay) applet.
• Receives the traffic data from ADS (replay) using a dedicated TCP/IP port and send it to
DisplayLite (replay) using HTTP communication.
• Handles the replay commands from DisplayLite (replay) applet and send it to the Logit Data Player.
• Handles the replay responses received from the Logit Data Player and send it to the DisplayLite
(replay) applet.
3.4.9.9 Advanced Data Server (replay)

• Handle user authentication for replay
• Provide clients with replay data
• Handle user settings for replay
3.4.9.10 DisplayLite (replay)

Different functionalities with respect to operational DisplayLite applet:
• Replay gui for entering replay commands and showing the replay responses.
3.4.9.11 Portal
Script application to provide a web based user interface for login:
3.4.10 Portable Replay Processor

The Portable Replay Processor subsystem (PRP) is primarily used for data presentation and human
interaction with the V3000 VTMIS. The working position configuration, i.e. the available applications and the
screen layout, depends on the assumed role of the user. The PRP may be configured to automatically start
with a previously defined default username, or the user is required to manually login on the PRP with the
desired role. The following usernames are defined:
• operator
• supervisor
• replay
• maintenance
Section 2.2, specifies in detail which functions are available for each role. This concerns the following
functions:
• Display the vessel traffic situation,
• Edit charts and alerts (supervisor),
• Display sensor evaluation data (supervisor & maintenance),
• Display hydro/meteo data,
• Display camera video,
Page 43 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• Replay and analyse traffic situations and

• Control and monitor the system.
Besides standard DP functionality, the PRP offers local replay capability. Using loggings made by the
CSP’s, PRPs are able to replay previously recorded sensor data, track data, voice data and camera video
data. The PRP can do so separate from the VTS system; for ease of use in legal cases or practical
situations.
The Portable Replay Processor subsystem executes on a laptop system.
Figure 16 PRP main processes and data flows

The PRP offers a mix between functionality of the Recording and Replay Processor, and the Display
Processor. Refer to the CSCI description of these nodes.
3.4.11 Enhanced Display Processor

The Enhanced Display Processor subsystem (EDP) is primarily used for data presentation and human
interaction with the V3000 VTMIS. The working position configuration, i.e. the available applications and the
screen layout, depends on the assumed role of the user. The EDP may be configured to automatically start
with a previously defined default username, or the user is required to manually login on the EDP with the
desired role. The following usernames are defined:
• operator
• supervisor
• replay
• maintenance
Section 2.2, specifies in detail which functions are available for each role. This concerns the following
functions:
• Display the vessel traffic situation.
• Edit charts and alerts (supervisor).
• Display sensor evaluation data (supervisor & maintenance).
• Display Hydro/Meteo data.
• Replay and analyse traffic situations.
• Control and monitor the system.
Page 44 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Besides standard DP functionality, the EDP offers local tracking capability, based on radar and/or AIS input.
This local capability can be employed in two manners:
• Main tracking functionality for a minimal VTS system, based on one EDP, working in conjunction with
RDP’s for any radar which may be present.
• Backup tracking functionality servicing, for example, manned remote sites. In case tracking is offline, in
the central system, due to a faulty network link for example, local tracks can be enabled by the
operator, which uses the local tracking capability to ensure tracking information is available to the user,
based on, for example, but not limited to, local sensors.
The Enhanced Display Processor subsystem executes on a workstation system.
Page 45 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Figure 17 EDP main processes and data flows

The EDP offers a mix between functionality of the Central Tracking processor, Interface Processor, Control
and Monitoring Processor, and the Display Processor. Refer to the CSCI description of these nodes.
3.4.12 MIS subsystem
3.4.12.1 DataBase Client Processor

The DataBase Client Processor subsystem (DBCP) consists of one or more Management Information
System (MIS) user interface clients (MISCLIENT). These are accessed remotely (via a terminal server
process).
Page 46 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
The MIS client is aware of the logic to create, view and manipulate planning information. It maintains a
user’s identity. The extent of the user actions is restricted to the maximum access level of the user.
The DataBase Client Processor subsystem executes on a server computer.
Figure 18 DBCP main processes and data flows
3.4.12.2 DataBase Server Processor

The DataBase Server Processor subsystem (DBSP) performs the following functions:
• ship voyage planning and status monitoring
• vessel characteristics storage and retrieval
• cargo details storage and retrieval
• resource management (pilots, tugs and berths).
The DataBase Server Processor subsystem executes on a server computer.
Figure 19 DBSP main processes and data flows
3.4.12.3 Voyage Planning

The following voyage planning elements are supported by MIS:
• pilots
• tugs
• vessels
• job and voyage details
• job and voyage status
• cargo
• maritime pollution prevention
• incidents.
Page 47 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
3.4.12.4 Resource Management

The following resources can be managed in MIS:
• pilots
• tugs
• berths.
For more detail regarding MIS refer to [MIS-FS].
3.5 Tools Definition
3.5.1 Reference System Processor

The Reference System Processor subsystem (RSP) is an integration and demonstration subsystem. It
contains a surveillance processing chain and a traffic display. The RSP subsystem executes on a
workstation system. The following CSCIs are part of the RSP:
• recording processing (LOGITREC),
• replay processing (LOGITREP),
• replay HMI (REPLAYGUI),
• AIS interface processing (ATI),
• plan management interface (PLAMAS),
• hydro-meteo interface (HYME),
• hydro-meteo data processing and distribution (HYMESET),
• multi-sensor tracking (TARGHITT/TARGHITTINT),
• track identification and alerting (TFP) and
• traffic situation display (ARAMIS MkII).
3.5.2 Sensor Performance Analysis and Simulation

The following tools are used for performance analysis and test scenario generation:
• VPSIM. VPSIM generates a radar analogue video signal for simulated targets.
• TRASIM. TRASIM generates radar and AIS sensor reports for simulated targets.
• RADSIM. RADSIM is a radar video simulator. It is a combination of a hardware radar video driver and
software to generate radar video test data.
3.5.3 Network Tools

The following tools are used for secure remote access, network integration and application testing:
• secure shell (ssh) – remote access.
• COMMSTLS – application testing.
• Wireshark – network testing.
3.5.4 Configuration Tools

The following tools are system configuration tools:
• CFHITT is used for the maintenance of global system parameters.
• VES is the Video Extractor Scope, which displays the received radar signal versus time or distance and
facilitates the tuning of the video extractor detection threshold
Page 48 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
VDS00006 Video extractor scope.
VES is a GUI running on the DP. It receives a VES line from ARAMIS and requests information from a
sweep, specified by the VES line, from the HTP. The received sweep report is visualised on the screen.
VES is started manually, one VES for each HTP to be evaluated.
• COCO is used for geographical coordinate conversions.
VDS00002 Data distribution by means of “auto/changes” mechanism.
Distribution of changed data files in CFHITT will be done by means of the “auto/changes” mechanism.
This means that changed data files are put at a central place from where they are distributed when a node
configuration is performed.
3.6 Internal Interfaces
3.6.1 Communication Protocols

The V3000 VTMIS system uses the Ethernet IP protocol; in particular the following transport layer
protocols:
• ICMP for monitoring equipment
• UDP and multicast UDP for real-time sensor- and surveillance data
• TCP for point-to-point control-related communication
• SCTP for duplicated point-to-point communication.
3.6.2 Network Configuration Data

The V3000 VTMIS network configuration data consists of
• network definitions, i.e. the different local networks present in the V3000 VTMIS system.
• routing data, including router configurations, firewall configuration and Virtual Private Network (VPN)
configuration.
• network interface addresses.
• network service and multicast stream definitions.
At present, these configurations are all project-specific.
3.6.3 External Data Streams

The V3000 VTMIS system converts external data formats into VTMIS internal formats (at the COP
component node). The exact external data formats that are used may be project-specific. Data formats that
are supported are
• NMEA for Hydro/meteo equipment, AIS base stations and (D)GPS position reports.
• NTP v3 for time synchronisation.
• SNMP v2 for status monitoring of equipment.
3.6.4 Internal Data Streams

The V3000 VTMIS internal data formats are described in the IFHITT interface description document
[IFHITT].
3.6.5 Maps and Parameter Data Files

The V3000 VTMIS system supports map data in the following formats:
• Electronic Navigational Charts (ENC) in S-57 format [S-57]
• text-based Computer Graphics Metafile (CGM) format [CGM]
The HITT application software uses three file formats for parameter files:
• .INI file format [INI]
Page 49 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• XML
• SNMP MIB.
3.6.6 Change Notifications

Map file changes and parameter file changes can be distributed across component nodes. Software
applications that use these files are notified and will re-read the (modified) files. The distribution of data and
the generation of change events is handled by the OFM CSCI.
Page 50 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
4. SYSTEM STATES AND MODES

The V3000 VTMIS system does not have global system states and modes. The selection of states and
modes is more fine-grained and pertains to the component nodes. The most important nodes are
duplicated and can have states
• duplicated
• single.
The difference being that, in duplicated mode, nodes will exchange state information, whereas, in single
mode, they will not.
Additionally, the component nodes in the V3000 VTMIS system recognize the following modes:
• operational mode
• test mode
• technical replay mode.
The normal mode is operational. The test and technical replay modes are used for system maintenance,
test and integration. The test and technical replay modes use different communication channels to avoid
interference with the parts of the system that are running in operational mode.
By putting duplicated components in the single state and, then, selecting either test mode or technical
replay mode, it is possible to run 2 parallel systems that use the same network without disturbing each
other (save for network load). This makes it possible to upgrade/replace and test new CSCIs or HWCIs
without affecting the operational system.
The difference between test mode and technical replay mode is the use of live or replayed sensor input.
Test mode uses the live sensor data from the operational part of the system, whereas technical replay
mode uses the data, stored on disk, and replayed in real-time or fast-time. The latter allows maintenance
personal to feed the system with well-defined sensor input, e.g. to tune system software and to analyse
system performance.
VDS00004 Technical replay mode

Technical replay gives the integrator the possibility to replay data recorded at the input of the system. The
system functions are executed again during technical replay and can be evaluated therefore with recorded
life data.
The following data is used as input for technical replay (and has to be recorded):
• digitized radar video;
• htp plots;
• AIS data;
• hydro meteo data;
• EOS camera video;
• flight plans;
The nodes in the configuration for technical replay are the COP, CSP and DP or the RSP.
Please note that the technical replay mode is completely different from “operational replay”, the latter is
used when the system is in operational mode and affects only the Analysis/Replay Working Position.
VDS00001 Increased replay speed during technical replay
During technical replay it is possible to increase the speed of the replayed data without missing data. This is
an addition to the operational available fast forward scan, where part of the data is skipped during the fast
forward replay.
Page 51 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
5. PROCESSING RESOURCES
5.1 Processing resources

The V3000 VTMIS system makes use of commonly available computer hardware. A characteristic of the
computer hardware market is the fast pace of change in available models. Therefore, the hardware list is
maintained in a separate document [LODI]. The processing resources are chosen to match the
requirements from the Functional Specification [FS].
5.2 Operating system

The operating system is Linux. It is versatile and provides all features that are needed by the functional
requirements of HITT systems.
Linux is distributed by a number of companies and is also freely available on the Internet.
HITT uses the openSUSE distribution which has guaranteed support in case of problems and for future
versions of the OS.
5.3 Supported browsers
VDS00008 Supported browsers

The following browsers are supported by A3000 web based applications:
• Microsoft Internet Explorer 6.0, 7.0 or 8.0,
• Firefox 3.x on Windows XP, Vista and
• Firefox 3.x on openSUSE Linux.
5.4 Log file location
VDS00011 Log files location

All applications are storing there log files on the same directory, hittsys/log.
Page 52 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
6. QUALITY FACTOR COMPLIANCE

This section describes the reliability, availability and maintainability calculations of the A3000 system.
6.1 Introduction
Purpose of the analysis
The purpose of the analysis is to predict the Reliability, Availability and Maintainability (RAM) of the system
for specification purposes.
Scope of the analysis

Included in the analysis is all hardware of the subsystem, used to perform the operational functions under
analysis.
Reliability
Reliability is the probability that an item can perform a required function under given conditions for a given
time interval (t1, t2). It is generally assumed that the item is in a state to perform this required function at
the beginning of the time interval.
Nominal inherent MTBF (Mean Time Between Failures) is given for the operational system functions.
Maintainability
Maintainability is the probability that a given active maintenance action, for an item under given conditions
of use can be carried out within a stated time interval, when the maintenance is performed under stated
conditions and using stated procedures and resources.
Nominal inherent MTTR (Mean Time to Repair) is given for the operational system functions (as a mean
time to restore the function).
Availability
Availability is the probability that an item is in a state to perform a required function under given conditions
at a given instant of time, assuming that the required external resources are provided.
Nominal availability is given for the operational system functions. The availability is defined as follows:
MTBF
A=
MTBF + MTTR
6.2 Operational and Environmental Conditions for the Analysis

Quality / reliability program
The equipment is considered to be in its useful life time period. Early failures and wear-out effects will not
be taken into account for the prediction of the Reliability Availability and Maintainability figures.
Operational conditions
For the analysis, the parts of the equipment, necessary to perform the operational function under analysis
are taken into account.
Definition of maintenance actions

Only the effect of corrective maintenance actions will be taken into account for the Availability calculation.
It is assumed that corrective maintenance will be performed according to the maintenance concept.
Preventive maintenance conditions

It is assumed that preventive maintenance actions will take place according to the maintenance concept
and in consultation with the operational staff.
Corrective maintenance resources

For the purpose of these analysis ideal corrective maintenance resources will be assumed.
Preventive maintenance resources

For the purpose of this analysis an ideal preventive maintenance support will be assumed.
Page 53 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
6.3 Analysis and Mathematical Model

In order to determine the RAM-figures of the operational functions a mathematical model representing the
considered functions has been developed. This includes a reliability block diagram with associated
predictions for all items in each reliability block.
System
Radar Site Video
Working Position
Processor
Antenna work-
unit server
station
A
Radar
KVM Video
extender Extractor
Video
B Processor KVM
extender
C switch monitor
Centre
Central Central
D Processor Processor
E switch
F WP1 WP2 WP3 WP4 SP
Figure 20 Reliability structure model
The reliability structure models of the specified operational functions are described in the diagrams.
6.3.1 Reliability
The Mean Time Between Failures for a series of n blocks in the reliability structure diagram is calculated as
follows:
1
MTBFs = n −1
∑λ
i=0
i
where λi is the failure rate of block i ( λi = 1 )

MTBFi
The Mean Time Between Failures for n identical parallel blocks, of which k have to be operating to perform
the system function, is calculated with:
n−k
n
∑  i  (λ µ )
i
MTBF p =
i =0  ,
n
kλ  (λ µ )
n−k
k 
Page 54 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
where λ = 1 MTBF and µ =1

MTTR
for one single block.
6.3.2 Maintainability
The Mean Time To Repair for a series of n blocks in the reliability structure diagram is calculated with:
n −1
∑ λ .MTTR
i i
MTTRs = i =0
n −1
∑λ
i =0
i
The Mean Time To Repair for n identical parallel blocks, of which k have to be operating to perform the
system function, is calculated with:
MTTR
MTTR p = ,
n − k +1
where MTTR is the Mean Time To Repair of one single block.
6.3.3 Availability
The nominal availability is calculated as follows:
MTBFi 1
Ai = =
MTBFi + MTTRi 1 + λi .MTTRi
The availability for a series of n blocks is calculated as follows:

n −1
As = ∏ Ai ,
i =0
where Ai is the availability of block i.
The availability for n parallel blocks, of which at least one has to be operating to perform the system
function, is calculated as follows:
n −1
A p = 1 − ∏ (1 − Ai )
i =0
The availability for n identical parallel blocks, of which k have to be operating to perform the system
function, is calculated as follows:
k −1 n−k n
n i  
A p = 1 − ∑   A (1 − A) = ∑   (1 − A) A n−i ,
n −i
 
i
i =0  i  i =0  i 
where A is the availability of one single block.
6.4 Data Sources

The availability data for the individual components are shown in Table 1. The Mean Time To Repair
(MTTR) is the addition of the Mean Repair Time (MRT) and the Mean Logistical Delay Time (MLDT). In
Table 2, the effect of a non-zero MLDT is shown; the MLDT is assumed to be 2.0 hours. MTBF, MTTR and
MRT are specified in hours.
Reliability figures are based on:

• component failure-rates
• other failure-rate data of literature, symposia, as well as manufacturer data.
Page 55 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
• Mechanical parts have been taken into account. However, under conditions of preventive
maintenance, the failure rates of most mechanical parts are so low that they will hardly affect the
system reliability.
Maintainability figures are based on:

• experience with similar equipment of same complexity during system tests in factory
• data collected during factory and field tests,
• direct repair of each failure.
6.5 Results of the Analysis

Based upon the reliability structures and the availability data, the results of the availability calculations are
as indicated in Table 1. The figures given herein shall be handled as best engineering estimates.
The dominant factor in the availability of the system is the availability of the radar/antenna system since the
main system has a high level of redundancy.
The RAM figures given in this paragraph have been calculated by using:
• the function definitions;
• the environmental/ operational conditions;
• the mathematical models; and
• the data sources.
The figures given herein shall be handled as best engineering estimates.
Page 56 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Table 1. Results of a Hardware Availability Calculation for a Basic VTS System
Availability VTS
Down-
Failure time/
Equipment description MTBF MRT MLDT MTTR Availability rate year
Sensors
Antenna unit 125 000 1 0.0 1.00 0.999992 8.00E-06 0:04:12

Single transceiver 25 321 0.28 0.0 0.28 0.999989 3.95E-05 0:05:49
Complete radar sensor 21 056 0.40 0.999981 4.75E-05 0:10:01
Server 120 000 0.75 0.0 0.75 0.999994 8.33E-06 0:03:17

Video extractor 176 000 0.50 0.0 0.50 0.999997 5.68E-06 0:01:30
Video Processor 71 351 0.65 0.999991 1.40E-05 0:04:47
Switch 2960 402 926 0.50 0.0 0.50 0.999999 2.48E-06 0:00:39
Radar Site 15 627 0.46 0.999971 6.40E-05 0:15:27
VTS Centre
LCD Monitor 30 000 0.50 0.0 0.50 0.999983 3.33E-05 0:08:46

KVM extender 57 500 0.50 0.0 0.50 0.999991 1.74E-05 0:04:34
Server 120 000 0.75 0.0 0.75 0.999994 8.33E-06 0:03:17
Dual server 9 600 120 000 0.38 1.000000 1.04E-10 0:00:00

Switch 3560 326100 0.5 0.0 0.50 0.99999847 3.07E-06 0.00056
2x LCD Monitor 15000 0.50 0.99996667 6.667E-05 0.012175

2x KVM extender 28750 0.50 0.99998261 3.478E-05 0.006352
Display Processor (DP) 40000 0.75 0.0 0.75 0.99998125 0.000025 0.006848
Working Position 7 908 0.55 0.999931 1.26E-04 0:36:32
4 out of 5 Working Positions 5 693 485 0.27 1.000000 1.76E-07 0:00:02
Centre 308 424 0.49 0.999998 3.24E-06 0:00:50
3 out of 3 Radar Sites 5 209 0.46 0.999912 1.92E-04 0:46:22

3 out of 4 Radar Sites 44 316 045 0.23 1.000000 2.26E-08 0:00:00
System (3 out of 3 radars) 5 123 0.46 0.999910 1.95E-04 0:47:12

Page 57 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
Table 2. Effect of Logistics Delay on Availability of a Basic VTS System

Availability VTS
Down-
Failure time/
Equipment description MTBF MRT MLDT MTTR Availability rate year
Sensors
Antenna unit 125 000 1 2.0 3.00 0.999976 8.00E-06 0:12:37

Single transceiver 25 321 0.28 2.0 2.28 0.999910 3.95E-05 0:47:21
Complete radar sensor 21 056 2.40 0.999886 4.75E-05 0:59:59
Server 120 000 0.75 2.0 2.75 0.999977 8.33E-06 0:12:03

Video extractor 176 000 0.50 2.0 2.50 0.999986 5.68E-06 0:07:28
Video Processor 71 351 2.65 0.999963 1.40E-05 0:19:31
Switch 2960 402 926 0.50 2.0 2.50 0.999994 2.48E-06 0:03:16
Radar Site 15 627 2.46 0.999843 6.40E-05 1:22:45
VTS Centre
LCD Monitor 30 000 0.50 2.0 2.50 0.999917 3.33E-05 0:43:50

KVM extender 57 500 0.50 2.0 2.50 0.999957 1.74E-05 0:22:52
Server 120 000 0.75 2.0 2.75 0.999977 8.33E-06 0:12:03
Dual server 2 618 301 818 1.38 1.000000 3.82E-10 0:00:00

Switch 3560 326100 0.5 2.0 2.50 0.99999233 3.07E-06 0.0028
2x LCD Monitor 15000 2.50 0.99983336 6.667E-05 0.060865

2x KVM extender 28750 2.50 0.99991305 3.478E-05 0.031758
Display Processor (DP) 40000 0.75 2.0 2.75 0.99993125 0.000025 0.025109
Working Position 7 908 2.55 0.999678 1.26E-04 2:49:30
4 out of 5 Working Positions 1 228 554 1.27 0.999999 8.14E-07 0:00:33
Centre 257 673 2.24 0.999991 3.88E-06 0:04:35
3 out of 3 Radar Sites 5 209 2.46 0.999528 1.92E-04 4:08:12

3 out of 4 Radar Sites 8 280 557 1.23 1.000000 1.21E-07 0:00:05

Page 58 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
7. REQUIREMENTS TRACEABILITY
The requirement traceablity matrix maps the requirements from the [FS] on the HWCIs/CSCI s of the
standard system. This matrix is covered by the [SPA] document.
Page 59 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
APPENDIX A LIST OF FIGURES

Figure 1 VTMIS Subsystems Overview.................................................................................................. 10
Figure 2 VTS Operator Working Position............................................................................................... 11
Figure 3 Supervisor / Planner Working Position .................................................................................... 12
Figure 4 Replay / Analysis Working Position.......................................................................................... 13
Figure 5 Maintenance Working Position ................................................................................................ 13
Figure 6 Remote Maintenance Working Position................................................................................... 15
Figure 7 V3000 Functions and their Relations ....................................................................................... 18
Figure 8.Basic fault-tolerant networking concept ................................................................................... 22
Figure 9 Location Overview.................................................................................................................... 23
Figure 10 Example V3000 VTMIS Network Configuration ..................................................................... 24
Figure 11 Modular configuration Sensor Site ......................................................................................... 25
Figure 12 VTS Centre Site ..................................................................................................................... 28
Figure 13 Remote operator site ............................................................................................................. 30
Figure 14 Remote operator site ............................................................................................................. 31
Figure 15 Operational data flow diagram ............................................................................................... 35
Figure 16 PRP main processes and data flows ..................................................................................... 44
Figure 17 EDP main processes and data flows ..................................................................................... 46
Figure 18 DBCP main processes and data flows................................................................................... 47
Figure 19 DBSP main processes and data flows................................................................................... 47
Figure 20 Reliability structure model ...................................................................................................... 54
Page 60 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
APPENDIX B LIST OF TABLES

Table 1. Results of a Hardware Availability Calculation for a Basic VTS System .................................. 57
Table 2. Effect of Logistics Delay on Availability of a Basic VTS System .............................................. 58
Table 3: Abbreviations............................................................................................................................ 62
Page 61 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
APPENDIX C ABBREVIATIONS
Table 3: Abbreviations
AIS Automatic Identification System
CCTV Closed-Circuit Television
CGM Computer Graphics Metafile
CI Configuration Item
CID Consolidated Interface Description
COP Central Operational Processor
CSCI Computer Software Configuration Item
CSP Central Storage Processor
DP Display Processor
EO Electro Optical (e.g. CCTV or infrared)
EDP Enhanced Display Processor
GPS Global Positioning System
GUI Graphical User Interface
HMI Human/Machine Interface
HWCI Hardware Configuration Item
IALA International Association of Marine Aids to Navigation Lighthouse Authorities
ICMP Internet Control Message Protocol
ISDN Integrated Services Digital Network
KVM Keyboard, Video, Mouse switch
LAN Local Area Network
MF Medium Frequency
MIB Management Information Base (in SNMP context)
MIS Management Information System
MTBF Mean Time Between Failure
MTRT Mean Time to Test Relay
MTTR Mean Time To Repair
NMEA National Marine Electronics Association
NTP Network Time Protocol
PR Printer
PSS Power Supply Switch
PRP Portable Replay Processor
PTZ Pan Tilt Zoom
RDF Radio Direction Finder
RDP Radar Data Processor
SCTP Stream Control Transmission Protocol
SNMP Simple Network Management Protocol
TCP/IP Transmission Control Protocol/Internet Protocol
TS Timeserver
TTS Thin Terminal Server
UDP User Datagram Protocol
UPS Uninterruptible Power Source
VHF Very High Frequency
VoIP Voice Over IP
VPN Virtual Private Network
VTMIS Vessel Traffic Management Information System
VTS Vessel Traffic Services
WAN Wide Area Network
XML eXtensible Markup Language
Page 62 of 63
00-08-22.SSDD– 2006-04-23 – Volume 1 of
Rev. 11 Approved – 2011-03-07
APPENDIC D LIST OF DESIGN REQUIREMENTS
ID Title ............................................................................................................................. Page

VDS00001 Increased replay speed during technical replay...........................................................51
VDS00002 Data distribution by means of “auto/changes” mechanism. ......................................49
VDS00004 Technical replay mode ....................................................................................................51
VDS00005 CMS monitored components..........................................................................................41
VDS00006 Video extractor scope. ....................................................................................................49
VDS00007 Java runtime environment handling..............................................................................42
VDS00008 Supported browsers........................................................................................................52
VDS00009 Use of HTTP protocol......................................................................................................42
VDS00010 CDM Traffic picture update rate .....................................................................................42
VDS00011 Log files location .............................................................................................................52
VDS00012 EOS viewer window dressing.........................................................................................40
VDS00013 EOS camera window full screen ....................................................................................40
Page 63 of 63

System Segment Design Document V3000

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Segment Design Document V3000

Uploaded by

Copyright:

Available Formats

HITT V3000

Standard Vessel Traffic Management and

© 2011 HITT B.V.

REV DATE PCFno DESCRIPTION RESPONSIBLE

2. SYSTEM DESCRIPTION ................................................................................. 16

3.2.2.3.1 Radar Data Processor ........................................................................................... 27

4. SYSTEM STATES AND MODES..................................................................... 51

6. QUALITY FACTOR COMPLIANCE ................................................................. 53

7. REQUIREMENTS TRACEABILITY ................................................................. 59

APPENDIX A LIST OF FIGURES............................................................................. 60

APPENDIX B LIST OF TABLES .............................................................................. 61

APPENDIX C ABBREVIATIONS .............................................................................. 62

APPENDIC D LIST OF DESIGN REQUIREMENTS ................................................. 63

1.3 Document overview

1.4 Referenced documents

Refer. Title Identification code

1.6 System overview

Figure 1 VTMIS Subsystems Overview

1.7 Operational concept

1.7.1 VTS operator

Figure 2 VTS Operator Working Position

1.7.2 Supervisor / planner

Figure 3 Supervisor / Planner Working Position

1.7.3 Replay / analysis

Figure 4 Replay / Analysis Working Position

Figure 5 Maintenance Working Position

1.7.5 Remote maintenance and support

Figure 6 Remote Maintenance Working Position

2.2 System functions

Figure 7 V3000 Functions and their Relations

2.2.2 Operational system functions

2.2.3 Supporting system functions

2.2.4 External sensor subsystems

2.2.4.2 Domestic signalling

2.2.4.3 Electro optical

2.2.5 Other subsystems

2.2.5.1 Management information system

2.2.5.2 VHF communication system

2.3 Redundancy concept

2.3.1 Power redundancy

Figure 8.Basic fault-tolerant networking concept

2.3.3 HWCI / CSCI redundancy

Figure 9 Location Overview

3.2.1 VTMIS network

Figure 10 Example V3000 VTMIS Network Configuration

3.2.2 Sensor Site

Figure 11 Modular configuration Sensor Site

3.2.2.2 Sensor and Communication Modules

3.2.2.2.1 Module AIS

3.2.2.2.2 Module General

Domestic signalling (DOM)

Domestic signalling concerns registration of the following on-site events:

3.2.2.2.3 Module Hydro/Meteo

3.2.2.2.4 Module Single Radar

3.2.2.2.5 Module Dual Radar

3.2.2.2.6 Module Low-Cost Radar

3.2.2.2.7 Module RDF

3.2.2.2.8 Module VHF

3.2.2.2.9 Module EOS

Optional the EOS module can be extended with:

3.2.2.3 Computer Equipment

3.2.2.3.1 Radar Data Processor

3.2.2.3.2 Radar Service Display