VTIS - 64 FDS Functional Design Specification

COMMERCIAL-IN-CONFIDENCE
VTIS System for TOTAL E&P - Balikpapan
Functional Design Specification
VTIS CDRL#64
TENDER CTBM001293-NH
Prepared for :
JETEC Engineering
Graha Surya Internusa
Jl. Rasuna Said Kav.X-0
Jakarta 12950
Prepared by :
THALES Air Systems

3, Avenue Charles Lindbergh
94628 Rungis Cedex
FRANCE
Doc No :61 980 551 - 558 Rev : - 1/42
Filename: VTIS_64 FDS (rev -).doc CAGE: F8224 Paper size: A4 Template: LFG50.dot
Ce document et les informations qu’il contient sont confidentiels et sont la propriété All information contained in this document remains the sole and exclusive
exclusive de THALES Group. Ils ne doivent être communiqués qu’aux personnes property of THALES Group. No part of it may be copied, or disclosed by the
ayant à en connaître et ne peuvent être reproduits ni divulgués à toute autre personne recipient to third persons, without the prior written consent of THALES Air
sans l’autorisation préalable écrite de THALES Air Systems. Systems; nor shall it be used for any purpose other than in connection with an
agreement or proposed agreement with THALES Air Systems.
VTIS System for TOTAL E&P Functional Design Specification 23 Mai 2011
CHANGES
Revision Description of changes
Revision - A B C D
Rev. Date 23 Mai 2011
Written by F. Lupinski
Checked by A. Kellenberger
Approved by P.Condette
Quality JL. Pilot

Stamp
Authorised for use Approved by
THALES Air Systems Customer
Date Date
F8224 Doc No :61 980 551 - 558 Rev: - 2/42
Ce document et les informations qu’il contient sont confidentiels et sont All information contained in this document remains the sole and exclusive property of
la propriété exclusive de THALES Group. Ils ne doivent être THALES Group. No part of it may be copied, or disclosed by the recipient to third persons,
communiqués qu’aux personnes ayant à en connaître et ne peuvent without the prior written consent of THALES Air System; nor shall it be used for any purpose
être reproduits ni divulgués à toute autre personne sans l’autorisation other than in connection with an agreement or proposed agreement with THALES Air
préalable écrite de THALES Air Systems. Systems.
TABLE OF CONTENTS
1. OVERVIEW .......................................................................................................................................7
1.1 SCOPE.......................................................................................................................................7
1.1.1 Identification .........................................................................................................................7
1.1.2 Project Overview ..................................................................................................................7
1.1.3 Scope of the document ........................................................................................................9
1.1.4 Structure of this Document...................................................................................................9
1.1.5 Configuration Management Issues for this Document.........................................................9
2. REFERENCED DOCUMENTS .......................................................................................................10
2.1 CONTRACTUAL DOCUMENTS..............................................................................................10
2.2 THALES DOCUMENTS ...........................................................................................................10
2.3 OTHER DOCUMENTS ............................................................................................................10
3. SYSTEM DESCRIPTION ................................................................................................................12
3.1 VTIS SYSTEM PRESENTATION ............................................................................................12
3.2 PRESENTATION OF THE SEAKER .......................................................................................12
3.2.1 Summary of the Seaker technical characteristics: .............................................................15
3.2.2 Seaker Hardware Configuration.........................................................................................16
3.2.3 Seaker Software Configuration ..........................................................................................17
3.3 PRESENTATION OF THE AIS RECEIVER (ON THE SEAKER SITES).................................17
3.3.1 AIS receiver Hardware configuration ................................................................................17
3.3.2 AIS receiver Software configuration...................................................................................18
3.4 PRESENTATION OF THE CW10............................................................................................18
3.4.1 Summary of the CW10 technical characteristics: ..............................................................19
3.4.2 CW10 Hardware configuration...........................................................................................20
3.4.3 CW10 Software configuration ............................................................................................22
3.5 PRESENTATION OF THE VHF RADIO DATA-LINK ..............................................................22
3.5.1 VHF Radio Hardware configuration ...................................................................................22
3.5.2 VHF Radio Software configuration.....................................................................................23
3.6 PRESENTATION OF THE OPERATOR POSITIONS .............................................................23
3.6.1 Presentation of the C2 .......................................................................................................23
3.6.1.1 Roles of the C2 Operators..........................................................................................23
3.6.1.2 Capabilities of the C2 Operational Mode....................................................................23
3.6.1.3 C2 Hardware Configuration ........................................................................................27
3.6.1.4 C2 Software Configuration .........................................................................................28
4. INTERFACE REQUIREMENTS SPECIFICATION .........................................................................29
4.1 GENERAL OVERVIEW............................................................................................................29
4.2 COMMUNICATION CONSTRAINTS .......................................................................................29
4.3 INTERFACE PROTOCOL STACK ..........................................................................................32
4.4 PHYSICAL LAYER (LAYER 1).................................................................................................33
4.4.1 Physical Layer Specification...............................................................................................33
4.4.2 Interface point inventory.....................................................................................................33
4.4.3 Interconnection Data flows Inventory .................................................................................34
4.5 DATA LINK LAYER (LAYER 2)................................................................................................35
4.5.1 Data Link Layer Specification.............................................................................................35
4.6 NETWORK LAYER (LAYER 3)................................................................................................35
4.6.1 Network Layer Specification...............................................................................................35
4.6.2 Telecommunications Network IP addresses Definition......................................................35
4.7 TRANSPORT LAYER (LAYER 4) ............................................................................................36
4.7.1 Transport Layer Specification .......................................................................................36
4.8 SESSION LAYER (LAYER 5) ..................................................................................................36
4.9 PRESENTATION LAYER (LAYER 6) ......................................................................................36
F8224 Doc No :61 980 551 - 558 Rev: - 3/42
4.10 APPLICATION LAYER (LAYER 7)..........................................................................................36

4.10.1 Data and messages transferred ...................................................................................36
4.10.2 Specification.....................................................................................................................36
4.11 DEFINITION OF THE WORK SHARE BETWEEN THALES AND JETEC.............................36
4.11.1 THALES part ......................................................................................................................36
4.11.2 JETEC part.........................................................................................................................37
5. QUALITY ASSURANCE CLAUSES ...............................................................................................39
5.1 GENERAL ................................................................................................................................39
5.1.1 Responsibility for tests .......................................................................................................39
5.1.2 Special Tests And Examinations .......................................................................................39
APPENDIX 1: LIST OF ACRONYMS AND DEFINITIONS ................................................................40
F8224 Doc No :61 980 551 - 558 Rev: - 4/42
LIST OF FIGURES
FIGURE 1- VTIS ARCHITECTURE .........................................................................................................8
FIGURE 2 – VIEW OF A SEAKER RADAR ON ITS TRIPOD ...............................................................12
FIGURE 3 – EXAMPLE OF RADAR UNIT.............................................................................................13
FIGURE 4 – EXAMPLE OF OPERATOR UNIT .....................................................................................13
FIGURE 5 – EXAMPLE OF BIT RESULT .............................................................................................14
FIGURE 6 – FA-30 AIS REVEIVER .......................................................................................................18
FIGURE 7 – VIEW OF THE CW10.........................................................................................................19
FIGURE 8 – CW10 RADAR SUB-SYSTEM ARCHITECTURE (CONNECTED TO VTIS SERVER AND
CONSOLES) ...................................................................................................................................21
FIGURE 9 – VHF RADIO .......................................................................................................................23
FIGURE 10 – EXAMPLE OF MSP WITH DISPLAYED SYSTEM TRACKS .........................................24
FIGURE 11 – DETAILED FORMAT OF TRACKS................................................................................24
FIGURE 12 – EXAMPLE OF SYSTEM TRACKS SYMBOLS ...............................................................25
FIGURE 13 – EXAMPLE OF MODIFIED ROUTE ACCORDING TO WAY POINTS ............................25
FIGURE 14 – EXAMPLE OF ETA (ESTIMATED TIME OF ARRIVAL) COMPUTATION.....................26
FIGURE 15 – DIFFERENT KINDS OF FENCES ...................................................................................26
FIGURE 16 – EXAMPLE OF SYSTEM AND OPERATIONAL ALERTS LIST ......................................27
FIGURE 17 – BOUNDARIES BETWEEN THALES AND JETEC .........................................................30
FIGURE 18 –SIMPLIFIED VIEW OF VTIS NETWORK.........................................................................31
F8224 Doc No :61 980 551 - 558 Rev: - 5/42
LIST OF TABLES
TABLE 1 – SEAKER CHARACTERISTICS...........................................................................................15
TABLE 2- CW10 CHARACTERISTICS .................................................................................................19
TABLE 3 – PROTOCOL STACK TABLE ..............................................................................................32
TABLE 4 – TRANSPORT PROTOCOLS AND ASSOCIATED PORTS TABLE ...................................32
TABLE 5 – INTERFACE ACCESS POINTS INVENTORY....................................................................33
TABLE 6 – END TO END DATA FLOWS INVENTORY TABLE...........................................................34
TABLE 7- IP HOST MACHINES ADDRESSEES ..................................................................................35
TABLE 8 – ACRONYMS........................................................................................................................40
F8224 Doc No :61 980 551 - 558 Rev: - 6/42
1. OVERVIEW
1.1 SCOPE
1.1.1 Identification
Project Name: VTIS System for TOTAL E&P
Document Name: Functional Design Specification
Doc. Short Name: VTIS FDS
THALES Number 61 980 551 - 558
Revision: -
Revision Date: 23 Mai 2011
File Reference VTIS FDS (rev -)
1.1.2 Project Overview

The VTIS System for TOTAL E&P is a maritime surveillance system installed in the area of the off-
shore Bekapaï and Peciko platforms and the on-shore Senipah plant.
The main purpose of this system is to protect the gas installations against the risks of vessel collisions.
It includes:
- A Seaker radar associated to an AIS receiver installed on Bekapai platform ,
- A CW10 radar with an integrated AIS receiver installed in Senipah plant,
- A C2 (Surveillance and Control system) with two operator positions installed in the control
room of the Senipah plant,
- A VHF transmitter used to deport the Martime Situation Picture (MSP) from the C2 in Senipah
to a patrol boat moving in the 15 NM area of interest,
- A VHF receiver and a C2 operator position in the patrol boat.
It is a concurrent project of the VTIS System for TOTAL E&P radar system.
The following figure describes a candidate architecture.
F8224 Doc No :61 980 551 - 558 Rev: - 7/42
VTIS GENERAL ARCHITECTURE Key:
BEKAPAI PLATFORM - TELECOMMUNICATION MAST SENIPAH PLANT – RADIO SHELTER (OUTDOOR) PATROL BOAT – MAST (OUTDOOR)
(OUTDOOR)
JETEC or CFE
provision
THALES
provision
Coaxial cable
Coaxial cable
Seaker Interface Box
Coaxial cable
BEKAPAI PLATFORM – VTIS EXISTING RADIO CABINET SENIPAH PLANT – RADIO SHELTER (INDOOR) PATROL BOAT – CABINET/DRAWER (INDOOR)
Power supply Coaxial cable Coaxial cable
cable
VTIS Console
cabinet
Ethernet cable
24V DC CW10
AIS AIS
Power Processing RECEIVER
RECEIVER
Supply unit
Ethernet Ethernet
Cable Cable 400 V AC
Power Supply
Bekapaï Platform WAN Access point – RADAR SWITCH 1 Senipah Plant WAN Access point – RADAR SWITCH 2
and FO converter
WAN
(Part of the Overall Telecommunications Network
based upon microwaves and optical fibres)
Senipah PABX Room WAN Access point – RADAR SWITCH 3 (Part of the VTIS C2 provision)
Ethernet cable
Ethernet
Ethernet
Ethernet
cable VTIS Consoles for
cable
Cable cabinet
complete maritime
situation display
SEAKER
Processing VTIS Server
unit
SENIPAH PABX ROOM - SMK TELECOM CABINET SENIPAH CONTROL ROOM

SENIPAH PLANT
Figure 1- VTIS architecture
F8224 Doc No :61 980 551 - 558 Rev: - 8/42
Ce document et les informations qu’il contient sont confidentiels et sont la propriété exclusive de THALES All information contained in this document remains the sole and exclusive property of THALES Group. No part of it may be copied, or disclosed
Group. Ils ne doivent être communiqués qu’aux personnes ayant à en connaître et ne peuvent être reproduits by the recipient to third persons, without the prior written consent of THALES Air System; nor shall it be used for any purpose other than in
ni divulgués à toute autre personne sans l’autorisation préalable écrite de THALES Air Systems. connection with an agreement or proposed agreement with THALES Air Systems.
1.1.3 Scope of the document

This document applies only to the VTIS System for TOTAL E&P Project.
1.1.4 Structure of this Document

This document is structured as follows:
Section 1 presents an overview of the project and gives the scope of the document.
Section 2 lists all related and applicable documents.
Section 3 describes the system (functions, hardware and software)
Section 4 describes the interface requirements specifications and identifies the providers
responsibilities.
Section 5 outlines the quality assurances clauses for this interface.
Appendix 1 identifies the acronyms and definitions used in this document.
1.1.5 Configuration Management Issues for this Document

Upon change request, this document will be updated by THALES and submitted to customer approval.
This document shall be maintained under configuration control. It may change as the project evolves.
F8224 Doc No :61 980 551 - 558 Rev: - 9/42
Ce document et les informations qu’il contient sont confidentiels et sont All information contained in this document remains the sole and exclusive property of THALES
la propriété exclusive de THALES Group. Ils ne doivent être Group. No part of it may be copied, or disclosed by the recipient to third persons, without the
communiqués qu’aux personnes ayant à en connaître et ne peuvent être prior written consent of THALES Air System; nor shall it be used for any purpose other than in
reproduits ni divulgués à toute autre personne sans l’autorisation connection with an agreement or proposed agreement with THALES Air Systems.
préalable écrite de THALES Air Systems.
2. REFERENCED DOCUMENTS
2.1 CONTRACTUAL DOCUMENTS

Refer to Project Purchase Order Ref.[1]
[1] Pre Bid Agreement Revision 6
(Ref. Tender CTBM001293-NH)
[2] VTIS GENERAL ARCHITECTURE drawing
(Ref. ID-VT-GE-JTC-TE-2-100)
2.2 THALES DOCUMENTS

[3] CRDL#63A : CW10 Radar Specification for VTIS System for TOTAL E&P Balikpapan
(Ref. TR6/SR/RNG-313/11 )
[4] CRDL#63B : Seaker Coastal Surveillance and Security Radar Product Description
(Ref : 9505 302 963 PRD 02-001)
[5] SQUIRE External Data Link Interface Requirement Specification
(Ref : 9505 002 284 IRS-001 04)
[6] SQUIRE External Data Link Interface Design Document
(Ref : 9505 302 417 IDD-001 01)
[7] Interface Requirement Specification (IRS) for the Coastal Surveillance centre (CSC) of the
Coastal Surveillance Radars (Ref : 61 979 500 – 506 Rev A)
[8] AIS receiver : FA30_20 Manual from FURUNO
[9] VHF RADIO :TAIT TM 8115 Data Sheet
(Ref : SM8115-100909.90)
[10] CRDL#63C : C2-System-Subsystem-Specification- (C2 SSS)
2.3 OTHER DOCUMENTS

[11] ISO/IEC 8802-3 (MAC) – Information Technology – Local and metropolitan area networks –
Part 3 : 1993 Carrier sense multiple access with collision detection (CSMA /CD) access
method and physical layer specifications
[12] ISO/IEC 8802-3u (Fast Ethernet) – Supplement to Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method and Physical Layer Specification : Media
Access Control (MAC) Parameters, Physical Layer, Medium Attachment, and Repeater for
100Mb/s Operation, Type 100 Base-T. Product type : Standard – 26 Oct 1995
[13] ISO/IEC 8877 (RJ45) – 1992 Information technology – Telecommunications and information
exchange between systems – Interface connector and contact assignments for ISDN Basic
Access Interface located at reference points S and T
[14] RFC 791 (IP) – Internet Architecture Board , Official Protocol Standard - Internet Protocol,
September 1981, Status : Required/Standard
[15] RFC 792 (ICMP) – Internet Architecture Board, Official Protocol Standard - Internet Control
Message Protocol, September 1981, Status : Required/Standard
[16] RFC 826 (ARP) – Internet Architecture Board, Official Protocol Standard - Address
Resolution Protocol, November 1982, Status : Elective/Standard.
[17] Standard: RFC 793: Internet Architecture Board, Official Protocol Standard Transmission
Control Protocol, September 1981, Status: Required/Standard
F8224 Doc No :61 980 551 - 558 Rev: - 10/42
[18] Standard: RFC 768: Internet Architecture Board, Official Protocol Standard User Datagram
Protocol, August 1980, Status: Required/Standard
[19] RFC 1305 "Network Time Protocol", Network Working Group, University of Delaware, March
1992
[20] Maritime navigation and radio communication equipment and systems – Digital interfaces –
Part 1 (Ref : IEC 61162-1 ) (aligned with NMEA 0183 version 2.30)
[21] Maritime navigation and radio communication equipment and systems – Digital interfaces –
Part 2 (Ref : IEC 61162-2 ) (aligned with NMEA 0183 version 2.30)
F8224 Doc No :61 980 551 - 558 Rev: - 11/42
3. SYSTEM DESCRIPTION
3.1 VTIS SYSTEM PRESENTATION

The following sections present the detailed characteristics of the VTIS system components.
3.2 PRESENTATION OF THE SEAKER
Figure 2 – View of a Seaker radar on its tripod
A Radar (Radio Detection And Ranging) is an equipment that uses radio waves for the detection and
the determination of the geographical position of moving targets like satellites, aircraft, ships, clouds
and rainy areas (for meteorological radar).
The Transmitter of the Radar sends radio signals that are reflected by the target and detected in return
by a Receiver generaly co-localized with the Transmitter. The target position is estimated with the time
spent between the signal emission and the echo (name of the response signal) reception. The target
speed is measured by the freqency change between the transmitted signal and the received echo by
the way of the Doppler processing.
The Seaker is a costal surveillance Radar dedicated for the automatic detection of surface targets
(ships) and aircraft flying at low elevations. It can operate day and night on manned as well as un-
manned sites.
It uses the FMCW (Frequency Modulated Continuous Wave) principle - it emits a continuous signal
with frequency modulation and not pulses- combined with a high resolution Doppler processing that
offers an excellent detection capability under heavy sea clutter conditions. Sea clutter are unwanted
echoes due to the responses of the moving sea waves crests : they can be eliminated by the Doppler
processing to keep only the interesting echoes. Moreover the Doppler processing offers the capability
to separate closely spaced targets with different speeds and results in good target discrimination.
It is made of two units : the Radar unit (fully solid state technology) and the Operator (or Display) unit
(PC-based laptop) connected each other through a LAN with TCP/IP protocol for a local or a remote
use.
F8224 Doc No :61 980 551 - 558 Rev: - 12/42
Figure 3 – Example of Radar Unit
The Radar unit can be easily installed on a platform on a simple mast due to its extremely low weight
(17,8 kg), single-unit design (Transmitter and receiver are integrated in the full solid state antenna) and
its low consumption (up to 50 W) enabling 24V DC battery operation.
It scans the space around the platform in a 15 NM range and a sector of 360° of Azimuth in 25 or 50 s
according to the chosen speed (possible scanning rate : 7° or 14° per second).
It operates with an Operator unit remotely installed in the Senipah Radio shelter (Radar cabinet) that
transmits the Seaker tracks to the Command & Control system part (VTIS server) of the VTIS to
generate the global Maritime Situation Picture.
The Operator Unit is two-fold:

- It is used for Radar setting-up during the installation for the tuning to the specific local
circumstances as well as environmental conditions of the platform,
- It is used during operation for the echoes and plots processing and for the display of a filtered
maritime situation where the objects tracks are positionned on a map layout with their bearing,
speed vector and a possible identification performed manually by the Operator.
In the frame of VTIS, the Seaker Operator Unit is used during the installation phase and for
maintenance purpose. It is an industrial PC installed in the VTIS server cabinet.
The Seaker and the CW10 tracks are currently displayed on the VTIS consoles.
Figure 4 – Example of Operator unit
F8224 Doc No :61 980 551 - 558 Rev: - 13/42
The Radar unit sends the radar echoes detected during the scan of the area of interest to the Operator
unit.
In first hand, the Operator unit performs the sea clutter processing to eliminate the un-wanted echoes
and extract the radar plots. The radar echoes are reported in a radar reference called the range cell
whereas the radar plots positions are reported in a geographical reference. After the sea clutter
processing comes the tracking processing to integrate the radar plots from scan to scan to form a
unique radar track per object and to deliver the radar situation to the operator.
In VTIS, the Seaker tracks are displayed on the VTIS consoles on the adequate layout (Geographical
maps) to present a comprehensible maritime situation.
In particular, alarm zones can be defined on the layout, an audio alarm and a visual alarm can be
generated in the case of a vessel penetrates a restricted or a prohibited area.
For more details, refer to section 3.6 dedicated to the Operator positions.
The Seaker provides three modes of operation useful for VTIS:
Stand-by mode:
The Seaker performs a selftest (BIT) at switch on before entering the Stand-by mode. The BIT result
is presented in a graphical way with colours indicating the equipment status (Green: correct
functioning, Yellow: Non-critical failure, Red: critical failure). Furthermore, the North-alignment is
performed, the position data is entered and the radar settings are adjusted. In this mode all system
functions are available and ready for immediate action.
The following figure gives an example of BIT result that can be displayed on the Seaker Operator Unit
Figure 5 – Example of BIT result
Surveillance mode:
In the surveillance mode, the Seaker automatically scans a sector. On the Operator position a map of
the sector can be presented, giving an overview of the obstacles, vessels, shoreline, non-moving
targets and blind areas.
Classification mode:
The operator can point out a target position on the Operator position. The co-ordinates of the selected
target are automatically displayed and the antenna will be pointed towards the assigned target
direction.
The Doppler sound characteristics of the target can then be heard by the operator through the
headphone. By means of this audio information, the operator can classify the target.
F8224 Doc No :61 980 551 - 558 Rev: - 14/42
During the time the Seaker is in stand-alone configuration without the integration on the display of the
AIS identification, the Doppler signature can be used as a mitigation to identify the type of trespassing
vessel.
This mode is mainly used with a stand-alone Seaker and is not useful in VTIS where AIS receivers and
a CW10 are parts of the system : it is only reminded for memory.
3.2.1 Summary of the Seaker technical characteristics:

The Seaker Radar provides its best performance for targets just above sea level.
The following table summarizes the main characteristics of the Seaker.
Table 1 – Seaker Characteristics
Seaker Performance and Technical Data

Performance Data
Intrumented Range Up to 48 km
Typical detection Range 20-25 km
Number of tracks > 200
Technical Data
Antenna Type Dual patch antenna
Antenna Polarisation Horizontal
Transmitter Output power 1 Watt Continuous Wave (typical)
Frequency Band I-J Band ( also called X-Band)
Sweep repetition frequency Staggered Pattern
Number of range cells in Signal Processing 512
Maximum Doppler speed 300 km/h
Doppler Resolution 0.5 m/s
Instrumented Range 6, 12, 24 or 48 km
Reliability 20000 hours
F8224 Doc No :61 980 551 - 558 Rev: - 15/42
Dimensions and weight for Radar unit Width : 650 mm

(Typical data) Height : 470 mm
Depth : 230 mm
Weight : 17,8 kg
Dimensions and weight for Operator unit Width : 350 mm
Depth : 70 mm
Weight : 3,6 kg
Power requirements Voltage :24V DC
Power consumption : 50 W
3.2.2 Seaker Hardware Configuration

Radar Unit :
- Antenna,
- Transmitter (integrated in the antenna block),
- Receiver (integrated in the antenna block),
- Radar Processing with LAN interface (integrated in the antenna block),
- Azimuth drive,
- Radar interface box
Operator Unit :
For VTIS, an industrial PC is used and is integrated within the server cabinet. The laptop is delivered
for maintenance purpose if needed.
F8224 Doc No :61 980 551 - 558 Rev: - 16/42
3.2.3 Seaker Software Configuration

The Seaker includes three software units:
- Seaker SEA MODE: this unit performs the sea clutter filtering to eliminate the un-wanted
echoes and extract the radar plots.
It is a part of the Seaker MMI and it is developed in Java.
- Seaker tracking: this tracking processing integrates the radar plots from scan to scan to form
a unique radar track per object.
It is connected to the Seaker MMI on a socket level. Its executable size is approximately 2Mb
and its is developed in C/C++.
- Seaker MMI: it is the HMI of the Seaker in charge of the maritime situation display and the
operator actions management.
It is developed in Java and its executable size is approximately 30 Mb.
For VTIS, this software runs on an undustrial PC installed in the VTIS server cabinet . It transmits the
Seaker tracks to the VTIS server to generate the whole Maritime Situation Picture.
3.3 PRESENTATION OF THE AIS RECEIVER (ON THE SEAKER SITES)
The AIS (Automatic Identification System) is an automated tracking system used on vessels and by
maritime traffic surveillance stations for identifying and locating vessels by electonically exchanging
data with other near-by vessels and surveillance stations.
It accordingly supplements a coastal surveillance radar, which remains the primary equipment used
for collision avoidance in maritime transport.
AIS transponders automatically broadcast information, such as their position, speed, and navigational
status, at regular intervals via a VHF transmitter built into the transponder. They use normal marine
VHF radio communications with GMSK modulation. The information originates from the ships
navigational sensors, typically its global navigation satellite system (GNSS) receiver and gyrocompass.
Other information, such as the vessel name and VHF call sign, is programmed when installing the
equipment and is also transmitted regularly. The signals are received by AIS receivers fitted on other
ships or on land based systems. The received information can be displayed on a screen or chart
plotter, showing the other vessels positions in must the same manner as a radar display.
The AIS equipment provided in the frame of the VTIS System for TOTAL E&P project is a receiver
used to get the information broadcast by the AIS-equipped ships. In addition to the receiver, it includes
a whip VHF antenna and an Ethernet cable for the data transmission to the Senipah Control room.
The AIS messages are sent in NMEA 0183 format through an Ethernet link with UDP/IP protocol. The
messages are decoded, associated to the relevant radar tracks and displayed on the global Maritime
Situation Picture on the VTIS consoles.
3.3.1 AIS receiver Hardware configuration

It is a COTS provided by FURUNO. Refer to document Ref. [8] .
F8224 Doc No :61 980 551 - 558 Rev: - 17/42
Figure 6 – FA-30 AIS reveiver
3.3.2 AIS receiver Software configuration

It is a COTS provided by FURUNO with its embedded software. Refer to document Ref. [8] for
software setting up.
3.4 PRESENTATION OF THE CW10

The Coastwatcher 10 (shortly named CW10) is a medium range coastal surveillance radar, designed
for unmanned round the clock operation.
Its main mission is to detect the maritime traffic up to 40 NM and has therefore been designed for an
optimized detection of a wide variety of surface targets ranging from small fishing boats or rubber boat
up to cargo ships. It works in X-band with 9410 MHz frequency with a high range resolution and uses
the Pulse Repetition Frequency principle.
• The CW10 is built around FURUNO FAR 2157 radar head and THALES signal and data
processors.
• The CW10 features advanced signal and data processing algorithms, resulting from THALES
research and development policy in both civilian and military fields.
It integrates an AIS receiver (same as the one presented here-above) for the target identification.
It can be operated from a Control Centre and sends its tracks (plots integration through a scan to scan
processing) in EUROCONTROL ASTERIX format on an IP link using the UDP protocol.
In VTIS, it is remotely controlled.
It is equipped with a BIT, which diagnoses are displayed on its Local Radar Console (LRC) or
transmitted to the Control Centre.
The CW10 is installed at the top of a telecommunication mast in Senipah.
F8224 Doc No :61 980 551 - 558 Rev: - 18/42
Figure 7 – View of the CW10
3.4.1 Summary of the CW10 technical characteristics:

The following table summarizes the main characteristics of the CW10.
Table 2- CW10 Characteristics
CW10 Performance and Technical Data

Performance Data
Intrumented Range Up to 40 NM
Typical detection Range 10 –15 NM
Number of tracks > 500
Technical Data
Antenna Type Slotted waveguide array
Antenna Polarisation Horizontal
Transmitter Output power 50 kW crête +/- 10% (typical)
Frequency Band I-J Band ( also called X-Band)
Sweep repetition frequency PRF staggering, false pulse rejector
Number of range cells in Signal Processing about 500
Reliability (MTBF) 2000 hours
F8224 Doc No :61 980 551 - 558 Rev: - 19/42
Dimensions and weight for the Aerial (Typical Antenna size : 3210 mm x 135 mm
data) Height : 635 mm
Weight : 80 kg
Dimensions and weight for the Radar cabinet Width : 650 mm
Depth : 800 mm
Weight : < 110 kg
Power requirements CW10 without LRC
Voltage :400 VAC
Frequency : 50 Hz
Power : 5 kVA max
LRC
Voltage : 230 VAC
Frequency : 50/60 Hz
Power consumption : 0,5 kVA max
3.4.2 CW10 Hardware configuration

The CW10 product is described in details in the document ref.[3].
The aim of the following section is only to describe the CW10 configuration delivered for VTIS.
F8224 Doc No :61 980 551 - 558 Rev: - 20/42
RADAR CW10 Sub-System in SENIPAH Key:
RADIO SHELTER (OUTDOOR TOWER) – ANTENNA and RADAR HEAD JETEC or CFE
provision
AIS ANTENNA
THALES provision
RADAR HEAD SIGNAL

CONTROL and VIDEO
PRE-
PROCESSING
Radar and AIS tracks, Operator Controls,

Optical Fibre Network
Time Distribution
VTIS
RADIO SHELTER server
INTERCONNECTION SIGNAL and DATA

UNIT PROCESSING AIS
RECEIVER VTIS Switch + FO converter
Local Radar Console
(for installation and
maintenance)
TELECOM CABINET
POWER DISTRIBUTION UNIT
RADIO SHELTER - RADAR CABINET
AC
MAINS VTIS VTIS
400 VAC
230 VAC Console Console
AC
MAINS
400 VAC
RADIO SHELTER – POWER SUPPLY
CONTROL ROOM
Figure 8 – CW10 Radar sub-system architecture (connected to VTIS server and Consoles)
F8224 Doc No :61 980 551 - 558 Rev: - 21/42
The here-above figure describes the CW10 architecture.

The CW10 is mainly composed of:
- A Radar head (Antenna and Transmitter/ Receiver assembly) based upon a COTS FURUNO
FAR 2157,
- An AIS antenna and receiver based upon a COTS (FA-30) from FURUNO,
- A signal and data processing based upon industrial PC (open architecture),
- A power distribution unit and transformer,
- A local radar console,
- A set of cables.
The indoor assemblies are installed in an equipped cabinet, which caracteristics are identified in
section 3.4.1
3.4.3 CW10 Software configuration

The CW10 includes three software units:
- Signal Processing and Extractor: this function group the elementary detections to generate
the radar plots corresponding to the interesting targets and also to particular points due to the
radar environment named false alarms.
- Data processing: this function integrates the radar plots from scan to scan to form a a unique
radar track per target. These tracks are transmitted to the Control and Command Centre to
build the Maritime Situation Picture.
- LRC processing: the LRC is used for the installation and maintenance of the CW10 on the
radar site. It can be used also to control the CW10 in case there is no Control and Command
Centre.
3.5 PRESENTATION OF THE VHF RADIO DATA-LINK

The Maritime Situation can be deported from the C2 installed in Senipah to a patrol boat sailing in the
area of interest with the help of a VHF radio data-link. The situation is displayed on a VTIS Console
installed in the patrol boat.
The data-link is performed with a COTS TM 8115 provided by the TAIT company.
The TM8115 is a robust, software-flexible radio, which is ideal for a wide range of voice and data
applications. The TM8115 comes with 100 conventional channels and a two-digit display.
It has an intuitive interface (easy to read display, four programmable function keys, microphone and
built-in loudspeaker) and flexible communications : it supports 1200/2400 bauds in FFSK in standard
configuration but up to 19200 bauds on WB channels with the software modem option).
3.5.1 VHF Radio Hardware configuration

The following figure depicts the Radio transceiver used for the data-link between the C2 and the patrol
boat.
F8224 Doc No :61 980 551 - 558 Rev: - 22/42
Figure 9 – VHF Radio
3.5.2 VHF Radio Software configuration

It is a COTS provided by TAIT with its embedded software. The installation and the setting-up will be
performed in conformance with the user manual.
3.6 PRESENTATION OF THE OPERATOR POSITIONS
3.6.1 Presentation of the C2

The C2 is an integrated coastal surveillance system from detection to response. It provides solutions
for missions such as prevention of collision and creates for the Operators a common situation
awareness picture of the maritime activity with the data transmitted by the connected radars
(Coastwatcher 10 and Seaker) and the AIS receivers. It delivers a Maritime Situation Picture, which
results in the fusion of the tracks provided by the radars displayed on a geographical map of the area
of interest. It can also deport the common situation picture through a data-link to a remote centre or to
a patrol boat (implemented in the VTIS).
3.6.1.1 Roles of the C2 Operators

The different roles of the Operator can be: Controller, Supervisor, Administrator, Trainer and Trainee.
The training Capability is not available on the VTIS configuration.
Controller Role:
Most operators log in as a Controller. The main task of the controller is to perform monitoring of the
maritime situation picture to check that there is no risk of collision in the vicinity of the platforms
otherwise follow-up actions can be initiated.
Supervisor role:
The Supervisor is the next higher role above the Controller. The Supervisor manages the Controllers,
and coordinates all the Controllers’ activities of the C2 when relevant.
Administrator:
The Administrator of the C2 manages all systems aspects in the centre, i.e. the operator positions, the
servers, the network equipment, the data backup/restore and any other responsibilities. The
Administrator has to ensure that the equipment are well managed and are in good operational state.
3.6.1.2 Capabilities of the C2 Operational Mode
In the operational mode, the Operator has access to the following capacities: Display Management,
Track Management and Data Fusion, Track Analysis, Geo-fencing, Record and Replay Management,
Alerts and Alarms Management, System Management.
Display Management Capability:

Display Management is the Human Machine Interface (HMI). It presents the Maritime Situation Picture
and the other different screen elements and receives Operator commands through the operator
console’s keyboard and mouse.
F8224 Doc No :61 980 551 - 558 Rev: - 23/42
500nm 450nm 400nm 350nm 300nm 250nm 200nm 150nm 100nm 50nm 50nm 100nm 150nm 200nm 250nm 300nm 350nm 400nm 450nm 500nm
Figure 10 – Example of MSP with displayed system tracks
Track Management and Data Fusion Capability:

The Track Management and Data Fusion is the Capability that maintains the track information received
from the radars and provides correlation between them. It performs data fusion that means the
merging of tracks coming from the Seaker, the CW10 or the AIS receivers to up-date a unic system
track).
Figure 11 – Detailed format of tracks
F8224 Doc No :61 980 551 - 558 Rev: - 24/42
Figure 12 – Example of system tracks symbols
Track Analysis Capability:

Track Analysis assists Operators in predicting the maritime situation picture and in driving interception
of vessels. It considers geographical obstructions and navigational channels for computing predictions
and sends the results to the Operator console. The result of computation is returned only to the
Operator that requests the computation.
The following figures represent two examples of analysis:

- To modify a proposed maritime route by imposing specific waypoints,
- To predict the time of arrival at a way point.
Figure 13 – Example of modified route according to way points
F8224 Doc No :61 980 551 - 558 Rev: - 25/42
Figure 14 – Example of ETA (Estimated Time of Arrival) computation
Geo-fencing Capability:
Geo-fencing provides Operators with a few fencing facilities for easy and effective track surveillance
and area protection.
Geo-fencing Capability allows the Operator to create, delete, activate the monitoring fences and alerts
the Operator when a track enters/exits the fences.
When a fence is activated, Geo-fencing capability shall issue a notification for any system track
matching the fence warning criteria.
The notification leads to a visual alert message including the following information:
- Alert title,
- Alert type,
- Alert priority,
- Alert description.
The alert message is described in the following figure.
Figure 15 – Different kinds of fences
Record and Replay Management Capability:
F8224 Doc No :61 980 551 - 558 Rev: - 26/42
Record and Replay Management records and replays information exchanged within C2 during the
operation of the system. This includes plots, source tracks, system tracks, fences, Operator actions,
and alerts. This recorded information can then be replayed to show the historical Maritime Situation
Picture and related controllers actions. It enables the storage and retrieval of real time track data and
operator interactions with the system.
Alerts and Alarms Management Capability:

Alerts and Alarms Management supports the Operators in their tasks. The C2 issues automatic
alerting functions to warn for (potentially) dangerous situations and conflicts in identification of tracks.
The alerts are classified into 2 types:
- Operational Alerts: Alerts pertaining to the track operations (for example: speeding track).
Critical alerts are generated due to the operational environment,
- System Alerts: Alerts pertaining to C2 administration (for example: hard-disk quota reached).
Monitoring or technical alerts are issued in case of malfunction of the C2.
Figure 16 – Example of System and Operational Alerts list
System Management Capability:

System Management will maintain the access control, rights of each individual user of the C2 and
provides the following functions: User authentication, User/role management, System status
monitoring, Communication between Operators.
C2 Server Capability:
In the frame of the VTIS, the server provides :
- The connectivity and the communication with the radar CW10 (with its integrated AIS
receiver) installed in Senipah , the Seaker, the AIS receiver installed in Bekapaï and the patrol
boat (Gateway Capability),
- The multi-sensor tracking Capability.
It is responsible for all the communications and the time synchronization between the Seaker, the
CW10 and the C2 using NTP (Network Time Protocol). The time synchonisation is performed with the
internal clock of the server.
For more details, refer to document ref. [10].
3.6.1.3 C2 Hardware Configuration

The C2 is able to run on commercial-of-the-shelf (COTS) Intel-based servers and workstation or PC-
based machines, running Microsoft Windows and LINUX operating systems.
The C2 operator position (VTIS consoles) runs on a PC (typically DELL T3500 PC).
F8224 Doc No :61 980 551 - 558 Rev: - 27/42
The C2 server (VTIS server) is typically a NEC 5800.

The server and the consoles use a Gigabit Ethernet LAN (typically a CISCO 2960-24 switch) for their
internal communication.
3.6.1.4 C2 Software Configuration

The C2 architecture is a client /server architecture.
The C2 server runs under LINUX (Red Hat Entreprise 5.4 or better).
The C2 operator positions (VTIS consoles) run under Windows XP Professional.
PostgresSQL is the relational database system used to manage the C2 objects database (radar tracks,
AIS data, system tracks, way points, fences, alerts…).
The external messages are sent through UDP/IP in binary format for the CW10 Radar data and
UDP/IP in NMEA 0183 format for the AIS data associated to the Seaker.
The Seaker tracks are sent to the C2 in TCP/IP .
TCP/IP is the protocol used for the communications between the C2 and the patrol boat (remote
centre).
XML is used for the C2 internal message exchanges and is supported by the COTS ActiveMQ.
Most of the software applications are developed in C++.
F8224 Doc No :61 980 551 - 558 Rev: - 28/42
4. INTERFACE REQUIREMENTS SPECIFICATION
This section describes all the requirements necessary to interface the THALES surveillance system in
the existing overall telecommunications network (named WAN here-after in the document for
simplification purpose) and states the work share of each provider.
It does not specify the equipment provided by THALES but the requirements needed for their
interfaces with the WAN to insure the good operation of the overall surveillance system.
The equipment requirements stand in the dedicated equipment documentation identified in section 2.2
and are referenced all along the present document when necessary for understanding.
4.1 GENERAL OVERVIEW

The interface requirements is as far as possible described in relation to the Open System
Interconnection (OSI) seven layer reference model. The following sections provide detailed
information, where necessary, about individual layers, defining applicable options and parameter
values.
Therefore specific options and parameter values for the various protocols that are used will only be
specified when an ambiguity has to be fixed or in the case of a deviation from a standard.
4.2 COMMUNICATION CONSTRAINTS

The Radar CW10 and Seaker, the AIS receivers, the VTIS server and consoles are provided by
THALES.
The 24 VDC and 230 VAC power supplies and the WAN (excepted for some IP switches supplied by
THALES) are provided by JETEC.
Therefore, on top of the equipment from its own responsibility THALES will provide the cables for their
connection to the existing telecommunications access points (namely switches or existing
telecommunications cabinets).
The following figure depicts the boundaries between THALES and JETEC provisions.
F8224 Doc No :61 980 551 - 558 Rev: - 29/42
CONTROL Room
VTIS Consoles
BEKAPAI Platform
Eth.
SEAKER Radar switch
WAN Eth.
switch
VTIS
AIS Receiver Server
PABX Room
SENIPAH Radio
Shelter
CW10 Radar and AIS Receiver
Seaker Processing
unit
THALES THALES
Responsibility Responsibility
JETEC
Responsibility
SENIPAH Building
Figure 17 – Boundaries between THALES and JETEC
F8224 Doc No :61 980 551 - 558 Rev: - 30/42
BEKAPAI Platform
CONTROL Room
VTIS Consoles
Eth.
Switch
SEAKER Radar
n°1 Wiring & Cabinets
FO adapt.
Microwave
Link
AIS Receiver
Eth.
Switch
VTIS Server
n°3
PABX Room
Eth.
Switch
n°2
CW10 Radar and AIS Receiver
SENIPAH Radio Shelter Seaker Processing unit
SENIPAH Building
JETEC or CFE
Key: provision
THALES provision
Figure 18 –Simplified view of VTIS network
F8224 Doc No :61 980 551 - 558 Rev: - 31/42
4.3 INTERFACE PROTOCOL STACK

The whole interface profile is made up by a stack which can be described in terms of layers, each with
a mapping to the seven layer OSI reference model as presented in the following table.
Table 3 – Protocol Stack table
OSI layer Protocol
Layer 7 Binary Proprietary protocol for Seaker, CW10 and VHF radio
NMEA 0183 for AIS receiver associated to Seaker
Layer 6 None
Layer 5 None
Layer 4 TCP and UDP
Layer 3 IP (Ipv4)
Layer 2 MAC
Layer 1 Fast Ethernet/RJ45
Table 4 – Transport Protocols and Associated Ports table
Application/Protocole Transport Number of Ports Dest1 Number of Ports Dest2

Dest1 Dest2
Seaker Radar unit
Seaker Processing unit
Proprietary protocol TCP Any: GPS position, North 4099: System status,
position, North Alignment, Surveillance flow,
External Track Classification flow, BIT flow,
Antenna Position Flow,
Marker flow, Jamming
Flow, Track Data Flow
Seaker Processing unit C2
TCP Any TBD 2 by THALES: Seaker

Track Data Flow
AIS Receiver C2
NMEA 0183 Standard 2.30 UDP Any TBD 3 by THALES: AIS

Track Data Flow
CW10 C2
Asterix 10, 34, 240, 253 UDP Any 60012:Controls and

(Radar information data) Responses
Acknowledgements
60020: Tracks, Plots,
Strobes, Stobes analysis,
End of Sectors, North
60026: Range Profile
F8224 Doc No :61 980 551 - 558
Ce document et les informations qu’il contient sont confidentiels et sont la propriété exclusive de THALES All information contained in this document remains the sole and exclusive propert
Group. Ils ne doivent être communiqués qu’aux personnes ayant à en connaître et ne peuvent être reproduits by the recipient to third persons, without the prior written consent of THALES A
Application/Protocole Transport Number of Ports Dest1 Number of Ports Dest2

Dest1 Dest2
Asterix 10, 34, 240, 253 UDP Any 60001: Radar Controls
(Radar controls) and Requests from the
Operator (to the CW10)
TDS (VTIS Server internal clock) Seaker ,CW10, VTIS consoles
NTP V3 UDP Any 123: NTP messages
C2 Patrol Boat (Internal interface for memory only)
TCP Any 34581: Tracks Information

34582: Replay commands
/Information
34583: Alerts, System
Monitoring,
34584: Radar
Information/Controls
34585: Miscellaneous
messages
4.4 PHYSICAL LAYER (LAYER 1)
4.4.1 Physical Layer Specification

This layer conforms to standard Ethernet 100 Base-TX Full Duplex: IEEE 802.3u Physical Layer
specification for Ethernet 100 Mb/s on twisted pair.
4.4.2 Interface point inventory

Regarding each interface, the interface point is defined in the following table based upon the VTIS
general architecture drawing (Refer to document ref.[2]) :
Table 5 – Interface access points inventory
THALES equipment Site- Localisation Interface point

Seaker Radar unit Bekapaï in the existing MW cabinet F/O patch panel
AIS receiver Bekapaï in the existing MW cabinet F/O patch panel
Seaker Processing unit Senipah PABX Room FO converter at the input of the Radar
switch 3 (Port n°2)of the VTIS system
CW10 + AIS Senipah Radio shelter Straight RJ45 (DTE) female socket on
the existing Radar switch 2 (Port n°2)
VTIS server Senipah PABX Room Straight RJ45 (DTE) female socket on
the existing Radar switch 3 (Port n°1)
The Switch numbers are compliant with Figure 1- VTIS architecture.
F8224 Doc No :61 980 551 - 558 Rev: - 33/42
4.4.3 Interconnection Data flows Inventory

Table 6 – End to End data flows Inventory table
Flow WAN Access WAN Access MeanTransfer Peak Packets Maximal Latency Availability MTU THALES
Number Number 1 Number 2 Rate Transfer loss Transmissio Time Eq.
Rate rate n Delay Variation
1 Bekapaï Senipah O : < 40 kb/s 100 kb/s < 1% < 500 ms <6s > 99,995% 1500 Seaker
platform SMK Telecom (radar data) (typical) bytes
MW cabinet cabinet I : < 10 kb/s (radar
controls)
2 Bekapaï Senipah O : < 10 kb/s 10 kb/s < 1% < 500 ms <6s > 99,995% 1500 AIS
platform SMK Telecom (identification (typical) bytes
cabinet data)
MW cabinet
3 Senipah Radio Senipah O : about 128 kb/s N/A < 1% < 500 ms <6s > 99,995% 1500 CW10
shelter SMK Telecom (radar data) (typical) bytes
+
cabinet I : < 32 kb/s (radar
AIS
controls)
4 Senipah Senipah O : < 32 kb/s 200 kb/s < 1% < 500 ms <6s > 99,995% 1500 VTIS
SMK Telecom SMK Telecom (radar controls) (typical) bytes
cabinet cabinet I : < 40+10+ 128
kb/s (Radar tracks
and AIS)
5 Senipah Radio Senipah < 10 kb/s (NTP N/A < 1% < 500 ms <6s > 99,995% 1500 TDS
shelter SMK Telecom time) (typical) bytes
cabinet
-6
Note : 1% of packets loss matches with a BER (Bit Error Rate) of 10 .
F8224 Doc No :61 980 551 - 558 Rev: - 34/42
Ce document et les informations qu’il contient sont confidentiels et sont la propriété exclusive de THALES All information contained in this document remains the sole and exclusive property of THALES Group. No part of it may be copied, or
Group. Ils ne doivent être communiqués qu’aux personnes ayant à en connaître et ne peuvent être disclosed by the recipient to third persons, without the prior written consent of THALES Air System; nor shall it be used for any purpose
reproduits ni divulgués à toute autre personne sans l’autorisation préalable écrite de THALES Air Systems. other than in connection with an agreement or proposed agreement with THALES Air Systems.
VTIS System for TOTAL E&P – Functional Design Specification 23 Mai 2011
4.5 DATA LINK LAYER (LAYER 2)
4.5.1 Data Link Layer Specification

This layer conforms to the ISO/IEC 8802-3 (MAC) standard (Refer to document Ref. [11]) with
untagged frame format.
JETEC network shall be able to transport Unicast MAC.
4.6 NETWORK LAYER (LAYER 3)
4.6.1 Network Layer Specification

For the network layer, the following rule applies: one IP address will be defined with the following
format: W.X.Y.Z/AA where W, X, Y and Z represent 8 bits of the address in decimal value and AA the
sub-net mask value which gives in decimal the number of bits set to “1” inside the mask.
The network layer used is the IP v4 (Internet Protocol version 4).
The following Internet protocols shall be supported by the interface:
• IP RFC 791 Internet Protocol (Refer to document Ref. [14])
• ICMP RFC 792 Internet Control Message Protocol (Refer to document Ref. [15])
• ARP RFC 826 Address Resolution Protocol (Refer to document Ref. [16])
The IP and MAC addresses shall be unic in the overall system.

The dynamic addressing and routing is forbidden in the overall system.
4.6.2 Telecommunications Network IP addresses Definition

Warning:The network address transporting the data shall be defined in the IP Plan (or other
document) provided by JETEC.
Table 7- IP Host machines addressees
Site Number Site Host Machine IP Host Machine address

Identification
1 Bekapaï platform Radar Interface box Network @ (TBD by JETEC)
Machine @ 1
2 Bekapaï platform AIS receiver Network @ (TBD by JETEC)
Machine @ 2
3 Senipah PABX Room Seaker processing Network @ (TBD by JETEC)
Machine @ 3
4 Senipah Radio shelter CW10 radar processing Network @ (TBD by JETEC)
Machine @ 4
5 Senipah PABX Room VTIS server Network @ (TBD by JETEC)
Machine @ 5
6 Senipah Control Room Console n°1 Network @ (TBD by JETEC)
Machine @ 6
7 Senipah Control Room Console n°1 Network @ (TBD by JETEC)
Machine @ 7
F8224 Doc No :61 980 551 - 558 Rev: - 35/42
Note 1: The IP addresses for the Radars, the AIS receiver and the VTIS sub-system shall be defined
in their respective configuration documentation.
4.7 TRANSPORT LAYER (LAYER 4)
4.7.1 Transport Layer Specification

The transport layer for Radar data transmission conforms to TCP (Transmission Control Protocol –
Refer to document Ref.[18]).
The transport layer for AIS data conforms to UDP (User datagram Protocol – Refer to document Ref.
[17]).
4.8 SESSION LAYER (LAYER 5)

Not Applicable.
4.9 PRESENTATION LAYER (LAYER 6)

Not Applicable.
4.10 APPLICATION LAYER (LAYER 7)
4.10.1 Data and messages transferred
4.10.2 Specification
The Seaker data messages sent from Bekapaï Platform to the remote Operator position in Senipah
Radio shelter conforms to the documents IRS Ref. [5]and IDD Ref.[6] .
The AIS messages sent from Bakapaï Platform to the VTIS server in Senipah Control Building
(Telecom cabinet) conforms to the document IRS Ref.[8] (TBC).
The CW10 data messages sent from Senipah Radio shelter to the VTIS server in Senipah Control
Building (Telecom cabinet) conforms to the document IRS Ref. [7].
4.11 DEFINITION OF THE WORK SHARE BETWEEN THALES AND JETEC
4.11.1 THALES part

THALES is responsible for:
LAYER 1:
− The use of Fast Ethernet as described here-above to exchange data between the concerned
areas,
− The provision of the straight RJ45 male socket terminated cable (of max. 50 meters) to be
connected from the Seaker Radar interface box to the Radar switch 1 in the existing radio trunked
cabinet of the Bekapaï platform (Refer to documents ref. [2] and figure Figure 1- VTIS
architecture),
connected from the AIS receiver to the same Radar switch 1 (Refer to document ref. [2] and figure
Figure 1- VTIS architecture),
F8224 Doc No :61 980 551 - 558 Rev: - 36/42
connected from the Seaker Processing unit to the Radar switch 3 in Senipah PABX Room (Refer
to document ref. [2] and figure Figure 1- VTIS architecture),
− The switches 1 and 3 (Refer to figure Figure 1- VTIS architecture).
For the connection to the 24 V DC power supply :

− The provision of the power cable 24V DC (of max. 50 meters) to be connected to the Seaker
Radar processing unit to the 24V Power Supply in the existing radio trunked cabinet of the Bekapaï
platform,
− The provision of the power cable 24V DC (of max. 10 meters) to be connected to the AIS receiver
to the 24V Power Supply in the existing radio trunked cabinet of the Bekapaï platform, ),
LAYER 2:
− The use of MAC ISO/IEC 8802.3 standard with untagged frame format.
LAYER 3:
− The configuration of the IP addresses of the host machines connected to the telecommunications
network respecting the rules of section 4.6.1,
− The use of TCP according to the standard RFC 793 and the parameters (IP address and Port
numbers identified in the present document and the IP Plan),
− The use of UDP according to the standard RFC 768 and the parameters (IP address and Port
numbers identified in the present document and the IP Plan).
LAYER 7:
− The implementation of the IRS Ref. [5],Ref. [7] and Ref.[8] and IDD Ref. [6] identified in the
delivered software of the Radar and the Operator position.
4.11.2 JETEC part

JETEC is responsible for:
− The provision of the WAN compliant with its IP Plan respecting the rules of section 4.6.1 including
the Radar switch 2 where THALES CW10 and associated AIS will be connected,
− The Mechanical support for installation kits,
− The absence of viruses etc… on the part of the overall network shared between the CCTV system
and the THALES system,
− The use of Fast Ethernet as described here-above to exchange data between concerned areas,
− The use of MAC ISO/IEC 8802.3 standard with untagged frame format.
− The provision of the IP addresses for the THALES machines connected to the WAN provided by
JETEC in compliance with Table 7,
connected from the CW10 to the Radar switch 3 in Senipah PABX Room (Refer to document ref.
[2] and figure Figure 1- VTIS architecture ),
For the connection to the 400 VAC power supply:
F8224 Doc No :61 980 551 - 558 Rev: - 37/42
- The provision of the power cables (of max. 10 meters) to connect the CW10 Radar cabinet (PDU)
to the 400VAC Power Supply and the LRC to the 230VAC Power Supply (Refer to figure Figure 1-
VTIS architecture) in the Senipah Radio Shelter. ),
F8224 Doc No :61 980 551 - 558 Rev: - 38/42
5. QUALITY ASSURANCE CLAUSES
5.1 GENERAL
This section deals with verification requirements related to the characteristics specified in Section 3.
Verification of these interface requirements is performed at system level.
5.1.1 Responsibility for tests

THALES and JETEC shall ensure that the interfaces comply to stated requirements in this document
and that the interfaces are adequately tested by both parties as defined in the Interface Responsibility
Definition sections of this FDS.
5.1.2 Special Tests And Examinations

Not Applicable.
F8224 Doc No :61 980 551 - 558 Rev: - 39/42
APPENDIX 1: LIST OF ACRONYMS AND DEFINITIONS

Table 8 – Acronyms
A
ASCII American Standard Code for Information Interchange
ASTERIX All-purpose Structured Eurocontrol Radar Information Exchange
B
BER Bit Error Rate
BIT Built-In-Test
C
CFE Customer Furnished Equipment
COTS Commercial Off The Sheff
CSCI Computer Software Configuration Item
CW10 CoastWatcher 10
D
DB25 Type of connector plug (25 pins)
DTE Data Terminal Equipment
EBCDIC Extended Binary Coded Decimal Interchange Code
EIA Electronic Industries Alliance
FFSK Fast Frequency Shift Keying
GIF Graphics Interchange Format
H
HDLC-UI High-level Data Link Control – Unnumbered Information
HTTP HyperText Transfer Protocol
I
ICD Interface Control Document
ICMP Internet Control Message Protocol
HMI Human Machine Interface
IO Input/Output
IP Internet Protocol
F8224 Doc No :61 980 551 - 558 Rev: - 40/42
ISO International Standards Organisation
ITU International Telecommunication Union
J
JPEG Joint Photographic Experts Group
L
LAN Local Area Network
LOS Line Of Sight
MAC Media Access Control
MPEG Moving Picture Experts Group
MSP Maritime Situation Picture
MTU Maximum Transmission Unit
MW Microwave
N/A Not Applicable
NMEA National Marine Electronics Association
NTP Network Time Protocol
OSI Open System Intercommunication
PC Personal Computer
PPP Point to Point Protocol
R
RJ45 Registered Jack 45
S
SIU Server Interface Unit
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
SSDD System Segment Design Document
SSS System Segment Specification
F8224 Doc No :61 980 551 - 558 Rev: - 41/42
TBC To Be Confirmed
TBD To Be Defined
TCP Transmission Control Protocol
Telnet Terminal NETwork ou TELecommunication NETwork
U
UDP User Datagram Protocol
UTC Universal Time Coordinated
V
VTIS Vessel Traffic Information System
WAN Wide Area Network
WB Wide band
X
XML Extensible Markup Language
F8224 Doc No :61 980 551 - 558 Rev: - 42/42

VTIS - 64 FDS Functional Design Specification

Uploaded by

Document Information

Original Description:

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

VTIS - 64 FDS Functional Design Specification

Uploaded by

Copyright:

Available Formats

COMMERCIAL-IN-CONFIDENCE

VTIS System for TOTAL E&P - Balikpapan

Functional Design Specification

THALES Air Systems

Doc No :61 980 551 - 558 Rev : - 1/42

Revision Description of changes

Rev. Date 23 Mai 2011

Quality JL. Pilot

Authorised for use Approved by

THALES Air Systems Customer

F8224 Doc No :61 980 551 - 558 Rev: - 2/42

F8224 Doc No :61 980 551 - 558 Rev: - 3/42

4.10 APPLICATION LAYER (LAYER 7)..........................................................................................36

F8224 Doc No :61 980 551 - 558 Rev: - 4/42

FIGURE 1- VTIS ARCHITECTURE .........................................................................................................8

FIGURE 2 – VIEW OF A SEAKER RADAR ON ITS TRIPOD ...............................................................12

FIGURE 3 – EXAMPLE OF RADAR UNIT.............................................................................................13

FIGURE 4 – EXAMPLE OF OPERATOR UNIT .....................................................................................13

FIGURE 5 – EXAMPLE OF BIT RESULT .............................................................................................14

FIGURE 6 – FA-30 AIS REVEIVER .......................................................................................................18

FIGURE 7 – VIEW OF THE CW10.........................................................................................................19

FIGURE 8 – CW10 RADAR SUB-SYSTEM ARCHITECTURE (CONNECTED TO VTIS SERVER AND

FIGURE 9 – VHF RADIO .......................................................................................................................23

FIGURE 10 – EXAMPLE OF MSP WITH DISPLAYED SYSTEM TRACKS .........................................24

FIGURE 11 – DETAILED FORMAT OF TRACKS................................................................................24

FIGURE 12 – EXAMPLE OF SYSTEM TRACKS SYMBOLS ...............................................................25

FIGURE 13 – EXAMPLE OF MODIFIED ROUTE ACCORDING TO WAY POINTS ............................25

FIGURE 14 – EXAMPLE OF ETA (ESTIMATED TIME OF ARRIVAL) COMPUTATION.....................26

FIGURE 15 – DIFFERENT KINDS OF FENCES ...................................................................................26

FIGURE 16 – EXAMPLE OF SYSTEM AND OPERATIONAL ALERTS LIST ......................................27

FIGURE 17 – BOUNDARIES BETWEEN THALES AND JETEC .........................................................30

FIGURE 18 –SIMPLIFIED VIEW OF VTIS NETWORK.........................................................................31

F8224 Doc No :61 980 551 - 558 Rev: - 5/42

TABLE 1 – SEAKER CHARACTERISTICS...........................................................................................15

TABLE 2- CW10 CHARACTERISTICS .................................................................................................19

TABLE 3 – PROTOCOL STACK TABLE ..............................................................................................32

TABLE 4 – TRANSPORT PROTOCOLS AND ASSOCIATED PORTS TABLE ...................................32

TABLE 5 – INTERFACE ACCESS POINTS INVENTORY....................................................................33

TABLE 6 – END TO END DATA FLOWS INVENTORY TABLE...........................................................34

TABLE 7- IP HOST MACHINES ADDRESSEES ..................................................................................35

F8224 Doc No :61 980 551 - 558 Rev: - 6/42

Document Name: Functional Design Specification

Doc. Short Name: VTIS FDS

THALES Number 61 980 551 - 558

Revision Date: 23 Mai 2011

File Reference VTIS FDS (rev -)

1.1.2 Project Overview

F8224 Doc No :61 980 551 - 558 Rev: - 7/42

VTIS GENERAL ARCHITECTURE Key:

SENIPAH PABX ROOM - SMK TELECOM CABINET SENIPAH CONTROL ROOM

Figure 1- VTIS architecture

F8224 Doc No :61 980 551 - 558 Rev: - 8/42

1.1.3 Scope of the document

1.1.4 Structure of this Document

1.1.5 Configuration Management Issues for this Document

F8224 Doc No :61 980 551 - 558 Rev: - 9/42

2.1 CONTRACTUAL DOCUMENTS

2.2 THALES DOCUMENTS

2.3 OTHER DOCUMENTS

F8224 Doc No :61 980 551 - 558 Rev: - 10/42

F8224 Doc No :61 980 551 - 558 Rev: - 11/42

3.1 VTIS SYSTEM PRESENTATION