AIR TRAFFIC & DEFENSE
Avitech – ATS Interfacility Data
Communication Server
Connects Civil and Military Air Traffic Services Units
AIDC / OLDI
Supporting your implementation of the Flexible Use of
Airspace (FUA) concept
Reducing ground-to-ground direct telephone
coordination time
Taking different protection profiles for different
classification levels into account
Providing ICAO AIDC and regional adaptations, such
as On-Line Data Interchange (OLDI) for the EUR Region
Introduction
The Avitech ATS Interfacility Data Communication (AIDC) Server supports the automated notification of flights approaching
a Flight Information Region (FIR) or a Control Area (CTA) boundary, the coordination
of boundary-crossing conditions, and the
transfer of control. It is intended to be used
in Air Traffic Services Units (ATSU) and Air
Defense Units (ADU). Existing third-party
systems and Controller Working Positions
(CWP) can easily be interfaced. Regional adaptations of ICAO AIDC are accommodated.
Features
Detailed Product Description
External interfaces and protocols
The Avitech AIDC Server can be linked to
any ATSU or ADU via Flight Message Transfer Protocol (FMTP) over TCP/IP or TCP/IP.
It provides a pure FMTP 2.0, OLDI 4.2 connection using an ADEXP 3.1 structured
message format. In addition Avitech SWIM
messaging, an Avitech XML Java Client or a
REST interface can be used.
Exchange of messages via internal XML
file messaging
Supports ICAO ACP, LAM, MAC and PAC
Supports EUR ACT, BFD, CFD, COD, RJC,
SBY, XAP, XCM, XIN and XRQ
Single and multiple Control and Reporting Centre (CRC) configuration
Exchange of messages
The Avitech AIDC Server exchanges messages originated by or addressed to that
server from/to connected ATSU and ADU
CWP. It converts inbound AIDC messages
from the controlling ATSU (C-ATSU) into
XML files which are then read, processed
and sent to the receiving ATSU (R-ATSU)
via Avitech SWIM. The R-ATSU can be an
ADU with a third-party ADU system and/or
CWP. Conversely, the CWP application writes
outbound messages into XML files and
sends them to the Avitech AIDC Server.
The XML files are then converted into AIDC
messages and provided via TCP/IP and/or
FMTP to the partner ATSU or ADU.
Use Case for CIV-MIL 2-Way Interoperability
System requirements
The Avitech AIDC Server is 100% Javabased. The FMTP stack uses Java Native
Interface (JNI) with C/C++. It can run on
most common operating systems such as
RedHat Enterprise Linux 5 & 6, Debian
Linux 7, Solaris 10, HP Integrity and others.
MIL
AIDC / OLDI
ACC 2
(Avitech SWIM)
AIDC
OLDI
ACC 4
AIDC / OLDI Server
(Avitech)
FMTP over TCP / IP
or
TCP / IP
…
TWR APP Server
(3rd Party)
AIDC / OLDI
(Avitech SWIM)
CWP(s)
…
MIL TWR /APP (n)
TWR APP Server
(3rd Party)
CWP(s)
The Avitech AIDC Server is compliant with
the EU ATM Master Plan and the ICAO Manual on SWIM Concept (Doc 10039-AN/511).
It follows ICAO SARPS in PANS-ATM (Doc
4444) and the ICAO Manual on ATS Data Link
Applications (Doc 9694-AN/955), Part VI.
It conforms to Regulation (EU) 552/2004
and the EU Specifications FMTP 2.0 (Spec
0100), OLDI 4.2 (Spec 0106) and ADEXP 3.1
(Spec 0107).
www.avitech.aero
Avitech GmbH
Bahnhofplatz 1
88045 Friedrichshafen / Germany
Phone:+49 (0) 7541 282-0
Fax:+49 (0) 7541 282-199
[email protected]
Avitech s.r.o.
Prievozská 4
821 09 Bratislava / Slovakia
Phone:+421 (0) 2 55 64 28 01
Fax:+421 (0) 2 55 64 28 03
Avitech GmbH
Strahlenberger Weg 6
60599 Frankfurt a. M. / Germany
Phone:+49 (0) 69 60 60 98 94
Fax:+49 (0) 69 89 99 03 01
Avitech GmbH
Rudolf-Diesel-Straße 1 A
78467 Konstanz / Germany
Phone:+49 (0) 7531 69 63 55
Fax:+49 (0) 7531 69 63 15
SWIM ATM
Conformance Statement
MIL TWR /APP (1)
© 2015 Avitech GmbH
ACC 1
ACC 3
The AIDC Client
The AIDC Client for CWPs can be developed
by third parties and uses the Avitech XML
Java Client or REST interface to connect to
the Avitech AIDC Server.
04-04 Avitech-ATM-AIDC 15-05
CIV
The AIDC Server
The Avitech AIDC Server combines modern
software architecture with ground-ground
data link know-how for AIDC. It consistently
decouples client applications from services,
data providers and data consumers. It enables seamless service communication
irrespective of the service location and provides total communication flexibility. It can
be combined with a protection-profilesbased secure domain transition gateway,
which enables the connection of networks
with different classification levels. This
gateway is evaluated according to Common
Criteria (CC), Evaluation Assurance Level
(EAL) 4+, and certified by the German Federal Office for Information Security (BSI).