ARTAS (ATM SuRveillance Tracker And Server)



ARTAS is a system designed by Eurocontrol in order to help in Aerial surveillance and Air traffic control. It can establish an accurate Air Situation Picture of all traffic over a well-defined geographical area (e.g. ECAC), and to distribute the relevant surveillance information to a community of user systems.
ARTAS users
A User of ARTAS in a general sense is defined in this context as any ATC subsystem having a requirement to receive at defined instants the best and most up-to-date estimate of all or selected aircraft state vector elements for all air traffic of interest to this User, e.g.:
  • Operator Display System,
  • Flight Data Processing System,
  • ATC Tools,
  • Flow-Control Management System,
  • Sequencing and Metering system,
  • Remote TMA’s,
  • Military Units, etc.
ARTAS is a distributed system composed of a number of identical subsystems co-operating together. Each subsystem, called an ARTAS Unit, will process all radar data reports to form a best estimate of the current Air Traffic situation within a given Domain of Interest.
Adjacent ARTAS Units will co-ordinate their tracks to build a unique, coherent and continuous Air Situation Picture over the complete area.
ARTAS unit groups
Four groups of main functions are implemented in an ARTAS Unit:
  • The TRACKER processes the radar input data and maintain the latest air situation represented in the Track Data Base.
  • The SERVER carries out the Track and Sensor Information Services, i.e. the management of all requests from Users and the transmission of the relevant sets of track/sensor data to these Users, and the so-called inter-ARTAS co-operation functions
  • The ROUTER BRIDGE handles the external interfaces to the Normal Users, the Broadcast Users, the Adjacent ARTAS Units and the surveillance sensors. It also implements the Radar Input Processing function.
  • The SYSTEM MANAGER carries out the functions related to the supervision and management of the ARTAS Unit.

ARTAS Architecture

ARTAS is developed as a regional system concept consisting of individual surveillance data processing and distribution units, which together will operate as one entity. Each subsystem, called an ARTAS Unit, processes all surveillance data reports - i.e. radar reports, including Mode S, ADS reports, and Multilateration reports to form a best estimate of the current Air Traffic situation within a given Domain of Interest.
The system operates on the basis of defined blocks of airspace known as "domains". Each ATM Surveillance Unit (ASU) tracks all traffic in its own defined airspace, known as a "Domain of Operation". The domains of operation of adjacent units overlap. In the areas of overlap, inter-unit track coordination functions take place, ensuring system tracking continuity. In this manner, adjacent ARTAS Units can co-ordinate their tracks to build a unique, coherent and continuous Air Situation Picture over the complete area.
The seamless integration of all Units permits the application of 5NM separation minima throughout the total covered area, also at transfers of traffic from one ATC unit to the next one. 3NM separation can be done following an in-depth operational evaluation of the ARTAS behaviour in the local environments.
Through a User/Server type of interface, the systems connected to ARTAS (e.g. local display system, remote users like Terminal Areas without own Radar Data Processing System, Flow Management Units, etc.) may, in a very flexible way, define exactly the modalities of the track services to be provided, e.g., the area (domain) for which it wishes to receive a specific sub-set of processed surveillance data. The flexibility of the system is such that the Domain of the user is not limited to the Domain of Operation of the Unit in which the user is situated, but may encompass airspace in the Domains of Operation of several adjacent ATM Surveillance Units.
In addition to the so-called Track State vector elements (position, speed, Mode-of-Flight, etc.), maintained by the Tracker, the served tracks comprise other information of interest for the user systems, including Flight Plan related information, provided by the Flight Data Processing Systems users of ARTAS (Callsign, departure/arrival airports, type of aircraft, etc.).

ARTAS Service Management and Actors 

All changes in ARTAS are done under control of the ARTAS User Group (AUG).ARTAS maintenance is shared between CAMOS(Centralised ARTAS Maintenance and Operational Support) and LAMOS (Local ARTAS Maintenance and Operational Support). CAMOS services do not include hardware support, but if required by the users, the Agency may decide to propose a service for the ARTAS hardware support as well. In the context of CAMOS, the EUROCONTROL Agency (ARTAS Product Manager) acts as AUG representative and provides directives to the service provider on behalf of the AUG.
Maintenance Activities
The activities of maintenance and support are currently performed by the Agency where EUROCONTROL experts in conjunction with industrial partners ensure support to the operational ARTAS units as well as the Pilot Units. A Service Level Agreement has been agreed with ARTAS users. Performance Indicators are used to provide targets and to request improvements to the Service Provider.
ARTAS Support
The Agency technical support team is located at Brussels HQ, however, the software maintenance and development is subcontracted to Comsoft Solutions GmbH, which is part of Frequentis AG.[1] At present ARTAS is in operation at thirty-one ATC Centres in Europe and under evaluation in many other European states. In total, around 100 ARTAS units are currently implemented or in the course of implementation, at more than 40 European sites.  https://en.wikipedia.org/wiki/ARTAS


    External links


    ATM suRveillance Tracker and Server (ARTAS)

    How does ARTAS work?

    What differentiates ARTAS from any other tracker system is the overall concept of a distributed system, consisting of an assembly of identical units which can all coordinate together and act as one region-wide integrated surveillance system.
    The various surveillance sensors are connected to a Regional Surveillance WAN (wide area network) and the units are also connected to this network. Each ARTAS unit processes surveillance data received on the network and acts as a server through the surveillance data distribution (SDD) systems, providing continuous aircraft radar data to the ATC units and other systems (e.g. terminal areas, military, flow management units, etc.) which are connected to the network.
    The seamless integration of all units allows for the application of 5NM separation minima throughout the covered area, including during transfers of traffic from one ATC unit to the next. 3NM separation can also be applied following an in-depth operational evaluation of the ARTAS behaviour in local environments.

    Type of data provided

    In addition to the so-called “Track-State-vector elements”, that is position, speed, mode-of-flight, etc., which are maintained by the Tracker, the served tracks comprise other data of interest for the system users, including information relating to flight plans, provided by the flight data processing systems users of ARTAS, i.e. call sign, departure/arrival airports, type of aircraft, etc.

    ARTAS Architecture

    The ARTAS architecture consists of two machines and is based on software developed specifically for the purpose of the project - ARTAS Middleware (MW). The architecture is based on the so-called ARTAS unit - a system, consisting of software and hardware resources, designed to meet all the functional and performance requirements.

    Software

    The ARTAS software, comprising online and offline components, middleware and application software, represents a total of about 2.1 million lines of source code, written in Ada, C, Java, Python and shell scripts.
    There are currently two different software versions of ARTAS, viz. V8A (end of Support in October 2016) and V8B. Each version is installed on two hardware platforms.
    ARTAS has four groups of main functions (computer software configuration item, or CSCI):
    TRACKER (TRK)
    processes the sensor input data and maintain the latest air situation represented in the Track Data Base
    SERVER (SRV)
    carries out the Track and Sensor Information Services, i.e. the management of all requests from users and the transmission of the relevant sets of track/sensor data to these Users, and the so-called inter-ARTAS co-operation functions
    ROUTER BRIDGE (RBR)
    Handles the external interfaces to the normal users, the broadcast users, the adjacent ARTAS Units and the surveillance sensors. It also implements the Sensor Input Processing function
    SYSTEM MANAGER (MMS)
    carries out the functions related to the supervision and management of the ARTAS Unit
    ARTAS features a set of on-line and off-line tools:
    Online
    A_COM
    A set of Common Packages that define those functions/procedures used by more than a single CSCI.
    BASIC SYSTEM
    Many functionalities of ARTAS (e.g. most of users’ requests like start/stop node) are implemented in a great number of shell scripts.
    SUPERVISION FACILITY (SUP)
    Two ARTAS SNMP agents allow the remote supervision (i.e. via network SNMP request/traps) over all the ARTAS functionalities.
    Offline
    DAF CSCI
    The purpose of this CSCI is to provide the data analysis facilities, in order to analyse a previous operational situation, to verify a posteriori the correct system operation, to assist in the system tuning and improvement.
    SIM CSCI
    Simulator functions are meant to simulate ARTAS USERS (basic Users and FPPS Users).
    PATCH INSTALLER  TOOL
    The Patch Installer tool is a set of Shell / Python scripts which installs/de-installs a patch (a solution for an ATR/ACP) in a common (i.e. a patch is installed in the same way in any ARTAS site) and safe (i.e. all prerequisites of the patch are verified before applying any change) way on any ARTAS system.

    Hardware

    With the ARTAS V8B Version, the ARTAS unit is hosted at one ARTAS station (AS). A dual ARTAS system consists of two identical computers and their associated peripherals. The internal LAN (Ethernet/Bonding) is part of the system. The TRK, SRV, RBR, MMS and REC CSCIs of each chain are executed on only one node.

    Interface

    In the latest ARTAS V8B release (as from ARTAS V8B3) the MMS CSCI integrates a modern, ergonomic and flexible user interface based on a client/server architecture, replacing other commercial off-the-shelf products related to the database (Ingres), and the graphic user interface (Ilog Wave).

    Support service

    The Central ARTAS software Maintenance and Operational Support (CAMOS) service was created to support ARTAS pre-operational or operational versions.  CAMOS collects the ARTAS system data and parameters needed to ensure the exchanges of surveillance data between the States implementing ARTAS. In addition, it provides software enhancements to the commonly developed ARTAS system – a necessary evolution due to changes in the technical environment or common user needs.

    Responsibilities

    The EUROCONTROL CAMOS Team located at Brussels HQ:
    • Provides a Helpdesk service, answering questions raised by ARTAS users, normally ANSP representatives
    • Processes ARTAS Trouble Reports (ATRs) and ARTAS Change Proposals (ACPs), including reproducing ATRs on CAMOS reference platforms and discussing technical matters with users and subcontractors
    • Follows developments performed by subcontractors
    • Tests patches and new versions delivered by Industrial Partners
    • Publishes ARTAS documentation (One Sky Team) and delivers patches (FTP site)
    • Reviews technical documentation
    • Participates in factory acceptance tests
    • Distributes new ARTAS releases to ARTAS users
    The LAMOS team is in charge of Local ARTAS Maintenance and Operational Support and therefore shares the ARTAS maintenance with the CAMOS Team at HQ. The LAMOS team is in charge of the day-to-day maintenance of the ARTAS systems. The following list describes some of the tasks of the LAMOS team:
    • Verifying system behaviour
    • Recording any anomalies
    • Collecting evidence related to anomalies
    • Reporting to CAMOS any troubles or anomalies at HQ
    • Deploying, testing and validating patches, updates or new releases of the ARTAS system in strict cooperation with the CAMOS team at HQ
    The Industrial Partners involved in CAMOS activities perform the following tasks:
    • Software maintenance and development (incl. documentation and COTS software)
    • Compliance with Software Assurance Level 3
    • ARTAS software configuration and control management
    • Factory acceptance testing
    • Advice to the CAMOS Team, including enhancement proposals
    • Provision of training courses for maintenance and upgrade purposes.


    Comments

    Post a Comment

    Popular posts from this blog

    ADEXP (ATS Data Exchange Presentation)

    ADEXP is a format, not a protocol. No restrictions are imposed on the transmission media or protocols to be used, other than that of the character set. ADEXP provides a format for use in on-line, computer to computer message exchange and for message exchange over switched messaging networks (e.g. AFTN, CIDIN, AMHS).
    Read more

    ASTERIX (ATC standard)

    ASTERIX  (short for  All Purpose Structured Eurocontrol Surveillance Information Exchange ) is a standard for the exchange of  air traffic services  (ATS) information. It is developed and maintained by the  European  ATS organization  Eurocontrol . ASTERIX not only stands for All-Purpose Structured Eurocontrol  Surveillance   Infor mation  Exchange but also represents a state-of-the-art surveillance  data  format which is nearly being adopted by the world users  community  as the universal  standard  in this  domain  today
    Read more

    EOBT-TOBT-TTOT-TSAT-CDM

    EOBT is Estimated Off Blocks Time : The flight plan time for the flight to be ready for departure. ATC usually allow a tolerance of +/- 15 minutes. TOBT, Target Off Blocks TIme , is a more accurate measure, usually within +/- 5 minutes, which tells the local CDM system and NMOC Brussels when the airline believes a flight will be ready. From this, a TTOT is calculated (Target Take Off Time) , which may be adjusted to allow for departure separations, CTOT etc, and then working backwards will provide a TSAT (Target Start Approval Time) which will provide both ATC and the airline the most suitable start up time given all the factors that the local CDM system takes into account.
    Read more