ADMAR

ADMAR ( Remote presentation of MADAP radar data) is software that is available for authorities and organizations with security tasks (BOS ) on the coordination and control of air traffic. It was the precursor to CIMACT.

Introduction

ADMAR could accommodate the available in European airspace civilian radar track data, location data and flight schedules of different data sources, IT - based process, taped together to form an air situation picture and pose with selected Air Traffic Control functions.

History

ADMAR was developed on behalf of the Ministry of Defence by EUROCONTROL and constantly updated. In connection with the previous versions are ADKAR ( Remote presentation of KARLDAP radar data ) and GAME ( ( GEADGE ( German Air Defence Ground Environment ) / ADKAR Message Exchange ) ).

ADMAR last version

With the last version ADMAR 2000, the operational command of the Air Force service ( EinsFüDstLw ) decreed the first time an independent by then FüWES ARKONAPLATZ second air layer, which gained in the context of aviation safety as a backup system in the control of aircraft operational readiness. MADAP (Maastricht Automatic Data Processing System) and KARLDAP (Karlsruhe Automatic Data Processing System ) served as ADMAR data sources.

ADMAR was developed exclusively for the German Air Force and was used in the stationary Control and Reporting Centre ( CRC) of mission control areas. Other users were the NLFZ SiLuRa, Air Force Office, PCC, AFSBw and JG 71 through the IT Office the transition to CIMACT was decreed. The Air Force Office, later the material command of the Air Force and then ultimately the WaSysKdo Lw, Support Management were responsible for the in- service.

Functionality

Available at Maastricht UAC or in the DFS civilian radar track data has been transferred to the ADMAR users and combined to form an air situation picture. There the flight schedules of aircraft were linked to the tracks of the air situation picture. ADMAR learned increasingly gaining acceptance and has been for the German Air Force ultimately indispensable.

Messaging

The data transfer to the ADMAR applications made ​​immediately via EUROCONTROL MAASTRICHT UAC, DFS KAARLSRUHE or direct data connection to the next property of the DFS. The transmission medium X25 data channels, ISDN, or the AutoFüFmNLw were used. For reasons of availability and to improve the survivability of the data transfer of sensor data and flight plan data was carried out to separate EinsFüDstLw separate data connections. For non- users ranged generally from a data connection. Due to the relatively small volume of air traffic also only data rates up to 64 kbit / s were to be expected. Data connections for mobile use were NOT provided.

Model change ADMAR - CIMACT

ADMAR had also in the last version still disadvantages that required a qualitatively new approach to the overall design, with particular emphasis. Examples of some disadvantages:

• The proprietary software was generally on standard hardware ( COTS ) is not executable.
• The ADMAR Map Drawing tool was outdated.
• The user interface ( HMI) included significant differences for civilian air traffic control.
• The user demand for mobile use were not met.
• Lack of Mode S capability and limited functionality " radar data Recording and Replay" ( RRR).

Since 2003, other countries, NATO, Federal Ministry of Defence and BMI as well as German authorities and organizations were increasingly interested with security post at the functionality of ADMAR. In addition ADMAR was still essential in EinsFüDstLw. Therefore, the development, the integration of additional functionalities and finally the model change to CIMACT were no alternative.