ERA - Technical Manual

NEO by ERA - Technical Manual
NEO by ERA
Technical Manual
Era a.s. This document is the property of and solely belongs to Era a.s. (Era). This
Průmyslová 387 document is being delivered on condition that it is to be used only for
530 03 Pardubice evaluation and review of its contents. As Era follows a policy of
Czech Republic continuous advancement and development, the specification herein may
Tel: + 420 467 004 253 be subject to change without notice. Neither this document, nor any of its
Fax: +420 467 004 555 contents, shall be in any way disclosed, duplicated or reproduced without
www.erabeyondradar.com prior written consent by a duly authorised representative of Era.
MSS Description
Table of Contents
1. INTRODUCTION .............................................................................................................................................. 8
1.1. NEO - NEXT GENERATION MULTILATERATION AND ADS-B SURVEILLANCE ................................................. 8
2. NEO OVERVIEW AND SPECIFIC APPLICATIONS .............................................................................................. 10
2.1. GENERIC SURVEILLANCE ARCHITECTURE ................................................................................................... 10
2.1.1. Processed Signals .................................................................................................................................... 11
2.1.2. Synchronisation Architecture .................................................................................................................. 11
2.1.3. Active and Passive NEO ........................................................................................................................... 13
2.2. SPECIFIC APPLICATION ARCHITECTURES .................................................................................................... 14
2.2.1. ADS-B Based Surveillance ........................................................................................................................ 15
2.2.2. Wide Area Multilateration ...................................................................................................................... 19
2.2.3. Surface Movement Surveillance ............................................................................................................. 21
2.2.4. Precision Runway Monitoring (PRM) ...................................................................................................... 22
2.2.5. Height Monitoring Unit (HMU) ............................................................................................................... 23
3. SYSTEM PERFORMANCE ............................................................................................................................... 25
3.1. ADS-B BASED SURVEILLANCE ...................................................................................................................... 25
3.1.1. Integrity and availability/continuity ........................................................................................................ 25
3.1.2. Time of Applicability Accuracy ................................................................................................................ 26
3.1.3. System Latency ....................................................................................................................................... 26
3.1.4. Update Rates ........................................................................................................................................... 26
3.1.5. System Capacity ...................................................................................................................................... 26
3.2. SURFACE MOVEMENT ................................................................................................................................ 26
3.2.1. Update Rate [ED-117 3.3.1] .................................................................................................................... 27
3.2.2. Probability of Update [ED-117 3.3.2] ...................................................................................................... 27
3.2.3. Position Accuracy [ED-117 3.3.3] ............................................................................................................ 27
3.2.4. Probability of MLAT Detection [ED-117 3.3.4] ........................................................................................ 28
3.2.5. Probability of Identification (PID) [ED-117 3.3.5] .................................................................................... 28
3.2.6. System Capacity [ED-117 3.3.6] .............................................................................................................. 28
3.2.7. Latency [ED-117 3.3.7] ............................................................................................................................ 29
3.2.8. Start - Up Time [ED-117 3.3.8] ................................................................................................................ 29
3.2.9. Track Initiation [ED-117 3.3.9] ................................................................................................................ 29
3.2.10. Probability of False Detection (PFD) [ED-117 3.3.10] ............................................................................. 29
3.2.11. Probability of False Identification [ED-117 3.3.11] ................................................................................. 29
3.2.12. Switchover Time [ED-117 3.3.12] ............................................................................................................ 30
3.3. WIDE AREA MULTILATERATION .................................................................................................................. 30
3.3.1. Update Interval [ED-142 3.3.1] ............................................................................................................... 30
3.3.2. Update of change aircraft information [ED-142 3.3.2] ........................................................................... 30
3.3.3. Probability of Position Detection [ED-142 3.3.3] .................................................................................... 31
3.3.4. Probability of Long Position Gaps (PLG) [ED-142 3.3.4] .......................................................................... 31
3.3.5. Probability of False Detection [ED-142 3.3.5] ......................................................................................... 31
3.3.6. Probability of Code Detection [ED-142 3.3.6] ......................................................................................... 31
3.3.7. Probability of False Code Detection [ED-142 3.3.7] ................................................................................ 31
3.3.8. Horizontal Position Accuracy [ED-142 3.3.8] .......................................................................................... 31
3.3.9. Target Report Time Stamp [ED-142 3.3.9] .............................................................................................. 31
3.3.10. Positional Resolution (Mode A/C) [ED-142 3.3.10] ................................................................................. 31
3.3.11. Processing delay [ED-142 3.3.11] ............................................................................................................ 32
3.3.12. Track Initiation [ED-142 3.3.12] .............................................................................................................. 32
3.3.13. Target Capacity [ED-142 3.3.13].............................................................................................................. 32
4. SYSTEM ARCHITECTURE AND DESIGN ........................................................................................................... 34
4.1. GROUND STATION ARCHITECTURE ............................................................................................................. 34
4.1.1. Receiving Unit (RXS) ................................................................................................................................ 34
4.1.2. Transmitting Unit (TXS) ........................................................................................................................... 35
4.1.3. Reference and Monitoring Transponder (RMTR) .................................................................................... 36
Commercial in Confidence Page 2 of 87

Use, duplication or disclosure of this sheet is subject to the restrictions given on the title page of this document
MSS Description
4.1.4. Other GS Assemblies ............................................................................................................................... 36

4.1.5. Ground Station Deployment ................................................................................................................... 36
4.1.6. Protection Areas ..................................................................................................................................... 38
4.2. CENTRAL PROCESSING STATION ................................................................................................................. 40
4.2.1. Target Processor [TP] .............................................................................................................................. 41
4.2.2. Management System [MS] ...................................................................................................................... 43
4.2.3. Communication Interface ....................................................................................................................... 44
4.3. REMOTE MANAGEMENT TERMINAL .......................................................................................................... 44
4.3.1. Engineering Display ................................................................................................................................. 45
4.4. NEO REDUNDANT CONCEPT ....................................................................................................................... 46
4.4.1. Ground station redundancy .................................................................................................................... 46
4.4.2. CPS Redundancy ...................................................................................................................................... 46
4.5. ENVIRONMENTAL CONDITIONS.................................................................................................................. 47
4.5.1. Indoor Climatic Conditions ...................................................................................................................... 47
4.5.2. Outdoor Climatic Conditions ................................................................................................................... 47
4.5.3. Storage Conditions .................................................................................................................................. 48
4.5.4. Transportability ....................................................................................................................................... 48
4.5.5. European Standards ................................................................................................................................ 48
5. MANAGEMENT SYSTEM ................................................................................................................................ 50
5.1. FUNCTIONS OF THE MANAGEMENT SYSTEM ............................................................................................. 50
5.1.1. Monitoring Functions .............................................................................................................................. 51
5.1.2. Control Functions .................................................................................................................................... 52
5.1.3. Maintenance Functions ........................................................................................................................... 53
5.2. NEO MODES ................................................................................................................................................ 53
5.2.1. Operational Mode ................................................................................................................................... 53
5.2.2. Maintenance Mode/Test Mode .............................................................................................................. 53
5.3. DATA RECORDING ....................................................................................................................................... 53
6. SYSTEM INTERFACES ..................................................................................................................................... 55
6.1. EXTERNAL INTERFACE ................................................................................................................................. 55
6.1.1. Input Signals ............................................................................................................................................ 56
6.1.2. Output Signals ......................................................................................................................................... 56
6.1.3. Time Synchronization .............................................................................................................................. 56
6.1.4. ATC Interface ........................................................................................................................................... 56
6.1.5. Control & Diagnostics.............................................................................................................................. 57
7. MAINTENANCE ............................................................................................................................................. 59
7.1. MAINTENANCE SCHEDULE .......................................................................................................................... 59
7.1.1. RM Maintenance ..................................................................................................................................... 60
7.1.2. M1 Maintenance ..................................................................................................................................... 60
7.1.3. M2 Maintenance ..................................................................................................................................... 60
7.2. REPLACEMENT OF ACCUMULATORS AND COMPUTERS............................................................................. 61
7.2.1. Preventive replacement of accumulators ............................................................................................... 61
7.2.2. Recommended replacement of computers ............................................................................................ 61
7.3. CORRECTIVE MAINTENANCE ...................................................................................................................... 61
8. RELIABILITY AND AVAILABILITY..................................................................................................................... 62
8.1. RELIABILITY FACTORS BACKGROUND ......................................................................................................... 62
8.1.1. Reliability ................................................................................................................................................. 62
8.1.2. Maintainability ........................................................................................................................................ 62
8.1.3. Availability ............................................................................................................................................... 63
8.2. SYSTEM RMA CALCULATION ....................................................................................................................... 64
8.2.1. Reliability ................................................................................................................................................. 64
8.2.2. Maintainability ........................................................................................................................................ 65
8.2.3. Initial Spare Holding - Probability of Nil Stock Out ................................................................................. 66
9. REFERENCE DOCUMENTS .............................................................................................................................. 68

MSS Description
10. ERA’S REFERENCE DOCUMENTS .................................................................................................................... 70
11. GLOSSARY ..................................................................................................................................................... 71

11.1. LIST OF ACRONYMS .................................................................................................................................... 71
APPENDIX A MULTILATERATION THEORY ....................................................................................................... 74
A.1. PRINCIPLE OF POSITION DETECTION - TIME DIFFERENCE OF ARRIVAL (TDOA) .......................................... 74
A.2. MLAT POSITION ACCURACY AND DILUTION OF PRECISION (DOP) ............................................................. 76
A.3. MULTI-RANGING ......................................................................................................................................... 78
APPENDIX B MLAT SIGNAL AND DATA PROCESSING ....................................................................................... 81
B.1. MODE S DATA PROCESSING........................................................................................................................ 82
B.2. MODE A/C DATA PROCESSING ................................................................................................................... 85
APPENDIX C AUTOMATIC DEPENDENT SURVEILLANCE - BROADCAST (ADS-B) ................................................ 86

MSS Description
List of Figures
Figure 1 NEO Typical Environment.............................................................................................................................. 9

Figure 2 Generic Multi-sensor Surveillance System .................................................................................................. 11
Figure 3 Stand-alone ADS-B processing .................................................................................................................... 16
Figure 4 Single Ground Station ADS-B Receiver Schematic ...................................................................................... 16
Figure 5 Centralised ADS-B processing Schematic .................................................................................................... 17
Figure 6 Upgraded ADS-B system + WAM validation ................................................................................................ 18
Figure 7 Upgrade ADS-B + WAM ............................................................................................................................... 18
Figure 8 Active Wide Area Multilateration NEO Architecture .................................................................................. 19
Figure 9 Passive Wide Area Multilateration NEO Architecture ................................................................................. 20
Figure 10 Active Surface Movement NEO Architecture ............................................................................................ 21
Figure 11 PRM Approach Scheme ............................................................................................................................. 22
Figure 12 Height monitoring by Multilateration ....................................................................................................... 24
Figure 13 An Example of a Ground Station Assembly .............................................................................................. 34
Figure 14 CT Receiving Unit Schematic ..................................................................................................................... 35
Figure 15 DT Receiver Unit Schematic ...................................................................................................................... 35
Figure 16 Transmitting Unit (TXS) Schematic ............................................................................................................ 36
Figure 17 Reference and Monitoring Transponder (RMTR) Schematic .................................................................... 36
Figure 18 Example of the Receiving station installation on the light pole ................................................................ 37
Figure 19 An example of AL1W antenna installation – long support holder ............................................................ 38
Figure 20 Signal chain for CT synchronisation NEO .................................................................................................. 40
Figure 21 Signal chain for DT synchronisation NEO .................................................................................................. 40
Figure 22 Schematic Block Diagram of CPS (Distributed time synchronization) ....................................................... 41
Figure 23 Era Display Application .............................................................................................................................. 45
Figure 24 Era Replay Application .............................................................................................................................. 46
Figure 25 Management System Concept .................................................................................................................. 50
Figure 26 Management System data flow ................................................................................................................ 51
Figure 27 NEO Interfaces .......................................................................................................................................... 55
Figure 28 SNMP Architecture .................................................................................................................................... 57
Figure 29 Formation of Time Difference of Arrival ................................................................................................... 74
Figure 30 2-D Cut of a Single hyperbola .................................................................................................................... 75
Figure 31 2-D Cut of a intersection of two hyperbolas ............................................................................................. 75
Figure 32 An Example of the Intersection of Three Hyperboloids ............................................................................ 76
Figure 33 HDOP ......................................................................................................................................................... 77
Figure 34 2-D Plot for a Simulation of Multilateration with Four Sensors – Target within Sensor Area .................. 78
Figure 35 2-D Plot for a Simulation of Multilateration with Four Sensors – Target outside Sensor Area ................ 78
Figure 36 Construction of Ellipsoids .......................................................................................................................... 79
Figure 37 2-D Plot combining Multilateration Hyperboloids and Multi-ranging Ellipsoid ........................................ 80

MSS Description
Figure 38 Signal and data processing flow ................................................................................................................ 81

Figure 39 Principle of target identification ............................................................................................................... 83
Figure 40 Mode S Target identification algorithm .................................................................................................... 84
Figure 41 ADS-B Principle .......................................................................................................................................... 86

MSS Description
List of Tables
Table 1 Processed Signals ......................................................................................................................................... 11

Table 2 Comparison between E-SCAN and NEO ....................................................................................................... 23
Table 3 Update rate for ADS-B system ...................................................................................................................... 26
Table 4 SAT Results for Asturias International Airport – Probability of Update [ED-117 3.3.2.1] ............................ 27
Table 5 SAT Results for Asturias International Airport – Probability of Update [ED-117 3.3.2.2] ............................ 27
Table 6 SAT Results for Budapest Airport - Position Accuracy [ED-117 3.3.3] .......................................................... 28
Table 7 SAT Results for Budapest Airport - Position Detection [ED-117 3.3.4]......................................................... 28
Table 8 SAT Results for Palma de Mallorca Airport – Track Initiation [ED-117 3.3.9] ............................................... 29
Table 9 SAT Results for Cape Town International Airport – Probability of False Detection [ED-117 3.3.10] ........... 29
Table 10 SAT Results for Cape Town International Airport – Probability of False Identification [ED-117 3.3.11] .... 30
Table 11 Positional Resolution ................................................................................................................................. 32
Table 12 Maintenance Time Schedule ...................................................................................................................... 59
Table 13 RM Maintenance ........................................................................................................................................ 60
Table 14 M1 maintenance Central Server................................................................................................................. 60
Table 15 M1 maintenance Ground Station ............................................................................................................... 60
Table 16 M2 maintenance Central Server................................................................................................................. 61
Table 17 M2 maintenance Ground Station ............................................................................................................... 61

MSS Description
1. Introduction
This document has been created to provide a high-level system description of the NEO by ERA. NEO by
Era represents a new, state of the art, certified, high-performance and cost-effective Multilateration
Surveillance System (MSS).
The document has seven main sections:
Section 2 - NEO Overview
Section 3 - System Performance
Section 4 - System Architecture and Design
Section 5 - Management System
Section 6 - System Interfaces
Section 7 - Maintenance
Section 8 - Reliability and Availability
1.1. NEO - Next Generation Multilateration and ADS-B Surveillance
NEO by Era is based on the proven Time Difference Of Arrival (TDOA) multilateration principle to
provide an accurate and reliable real-time location and identification of all aircraft, vehicles and other
objects equipped with a Mode A/C/S transponder. The system also decodes ADS-B signal (1090 ES)
according to all applicable standards (such as RTCA DO-260A) and can be configured as a stand-alone
network of redundant, ADS-B ground stations, capable of independent ASTERIX output.
The system is designed for continuous, automatic operation 24 hours per day 7 days per week with
low maintenance and high reliability.
NEO is flexible and expandable. Additional ground stations, interrogators and reference transponders
can be easily added to the system at expand the capability or to adapt to changing surveillance
requirements.
Era’s unique ability to combine distributed timing architecture with central timing architecture ensures
that each system can be optimised to the unique requirements and constraints of any solution, from
wide area to surface.

MSS Description
Figure 1 NEO Typical Environment
Era has developed a highly specialised Management System, which allows maintenance engineers to
monitor, control and maintain the NEO. Era’s management system consists of Management Terminals
and Management Servers that work seamlessly with the Integrated Control Units inside NEO. System
status is constantly transmitted in the specified output messages (e.g. ASTERIX) and also uses the
Simple Network Management Protocol (SNMP) to allow integration with other monitoring systems.
To ensure reliability, the system contains redundant parts and may be equipped with a UPS.
The NEO is compliant with ICAO Annex 10, EUROCONTROL SUR and EUROCAE MOPS ED-117 standards
and has been approved for ATC application in various countries.

MSS Description
2. NEO Overview and specific applications

This section provides an overview and specific applications of the NEO by ERA.
NEO provides a cost effective alternative to conventional radar for the monitoring of cooperative
aircraft targets, and vehicles, both in the air and on the ground. NEO is a distributed system which
provides for both improved performance and enhanced reliability. A distributed system has a number
of sensors spread throughout the geographical coverage area, as distinct from a conventional radar
which has a single sensor which is typically located at the centre of the coverage area.
In a distributed system data is collected from an array of sensors and transmitted to a central
processor, which collates the sensor data and estimates position, using Multilateration processing (see
Appendix B). The data is then forwarded to the required Air traffic Control surveillance applications.
Data messages are compliant with the relevant ASTERIX standards.
An NEO can operate as either a passive sensor or an active sensor. In passive mode the sensor array
listens to the normal transmissions from aircraft. In an active system the NEO also initiates
transmissions from aircraft and vehicles.
2.1. Generic Surveillance Architecture
This sub-section provides an introduction to the concept of the NEO by ERA, through the description of
the generic architecture, as shown in Figure 2.
Radio frequency (RF) transmissions from an aircraft, or ground vehicle, are received at a number of
receiving ground stations, which in turn communicate aircraft identification and signal time of arrival
information to a central processing server (CPS). The central server collates this data, and if required
estimates the aircraft position. The pooled data is then communicated to the Air traffic Control (ATC)
surveillance application.
The particular radio frequency transmissions from an aircraft, or ground vehicle, are SSR Mode A/C or
Mode S transmissions. The signal transmission from the aircraft can be initiated by a Monopulse
Secondary Surveillance Radar (MSSR) interrogator, or an interrogator controlled by the NEO. In
addition, or alternatively, Automatic Dependent Surveillance – Broadcast (ADS-B) transmissions can be
used.
The ADS-B data message includes the aircraft position. As the ADS-B data message includes the aircraft
position it is possible to operate with a single ground station.
In general RF transmissions from an aircraft are collected by a distributed array of sensors which are all
connected to a central server. The central server collates the data and estimates aircraft position,
which is communicated to the ATC application using standard ASTERIX format data messages.
Performance of the NEO can be monitored and controlled locally or remotely via NEO Management
system.

MSS Description
Ground Ground Ground Ground

Station Station Station Station
Sensor Array
Central Processing
Server
ASTERIX
/SNMP
ATC RCMS
ATM System
Figure 2 Generic Multi-sensor Surveillance System
2.1.1. Processed Signals
The NEO processes all Mode S replies coming from conventional Mode S transponders and optional
Mode 3/A, with C replies coming from conventional Mode A/C only transponders. Both processes take
place according to the ICAO Annex 10 specification.
Full details of all the downlink formats (DF) that a multilateration system uses are given in ICAO Annex
10 Aeronautical Telecommunications Volume IV. The main civil formats of interest to multilateration
systems are given below. Please note that all Mode S formats include Mode S Identity and GND flag
information.
Downlink
Format Type of Information
Format (DF)
Mode A n/a Mode A Identity
Mode C n/a Barometric Altitude
Mode S squitter 11 Mode S Identity
Mode S extended squitter 17 ADS-B
Mode S extended squitter 18 ADS-B
Mode S short ACAS 0 Mode S Identity, Barometric Altitude
Mode S long ACAS 16 Mode S Identity, Barometric Altitude, air-air
coordination
Mode S short surveillance 4 Barometric Altitude
Mode S short surveillance 5 Mode A Identity
Mode S long surveillance 20 Barometric Altitude, Data Link
Mode S long surveillance 21 Mode A Identity, Data Link
Table 1 Processed Signals
2.1.2. Synchronisation Architecture
A Multilateration system such as NEO requires that the relative time of arrival of the same signal at
different locations is recorded. This data is then used to form pairs of Time Difference of Arrival
(TDOA) measurements. The implementation of accurate relative timing is achieved by time

MSS Description
synchronisation of the various receivers. The NEO can achieve this by using either a central timing or a
distributed timing approach, according to the relevant characteristics of the target system.
2.1.2.1. Central Timing
In a Central Timing (CT) implementation there is a single point of time reference, typically at the
central processor.
The primary advantage of a CT implementation is that the ground stations are relatively simple,
consisting of an antenna connected to a receiver. The receiver down-converts the received signal and
outputs a video signal which maintains the required timing information. This signal is received at a
central processing station, together with the other relevant ground station signals.
The signal delay associated with the transmission of the signal from each receiver to the central
processor must be known, and be constant, in order that this delay can be subtracted and the original
time of arrival estimated.
There are three suitable mediums for the transmission of real-time signal information:
 A dedicated microwave link

 A dedicated fibre optic link
 A dedicated coaxial link (for short distances only)
A fibre optic link is the most suitable option, particularly when an existing fibre optic installation is
available, or at least where suitable ducting is already present, such as in airport installations.
If a fibre optic installation is not available then a set of microwave links can be used.
2.1.2.2. Distributed Time
In a Distributed Time (DT) implementation the received signal is time-stamped in the ground station
receiver.
The primary advantage of a DT implementation is that there is no dependency on the latency, and in
particular any variation in latency, of the signal transmitted from the receiver to the central processor.
However, the ground station is more complex, as it not only has to down-convert the received signal,
but also digitises the signal and extract code and timing information, for onward transmission to the
central processor.
In order to maintain accurate relative time each ground station has to contain accurate clock and a
method of determining the relative timing between the various ground station clocks.
The NEO by ERA uses method called “Advanced GNSS Synchronisation” to maintain synchronisation of
a distributed clock system
2.1.2.2.1. Advanced GNSS Synchronisation
Accurate relative time can be derived from the signals transmitted from a Global Navigation Satellite
System (GNSS). The NEO by ERA uses propriety algorithms to calculate the relative, or differential,
timing between an array of ground stations, each of which can see the same constellation of GNSS
satellites.
As each ground station receives signals from the same satellites, often referred to as having a common
view, then the majority of system errors are common and cancel, thus yielding a high accuracy. In

MSS Description
theory sub-nanosecond relative timing accuracy is achievable, and in practice the timing accuracy is
better than 2 nano-seconds.
2.1.3. Active and Passive NEO
A distinction can be made between active and passive NEO: a passive system consists of receivers only
whereas an active system has one or more transmitting units in order to interrogate an aircraft’s SSR
transponder.
2.1.3.1. Passive NEO
There are two main benefits of passive NEO. Firstly no transmission license is required for the
installation and use of the system. Secondly there is no increase in the number of 1030 MHz
interrogations or 1090 MHz replies invoked by the NEO system.
2.1.3.2. Active NEO
The main advantage of an active NEO is that system is not dependent on other sources to trigger a
1090 MHz replies from aircraft. In active NEO the elliptical-hyperbolic method (see Multi-ranging) can
be used to calculate the range to the target. The interrogation function in NEO is ensured by
transmitting units (TXS) that are controlled by Central Processing Station via IP data links. The TXS are
capable of transmitting of two different signals:
 SSR interrogation 1030MHz,

 Transmission of replies 1090MHz.
2.1.3.2.1. Interrogation 1030 MHz
The transmission on 1030 MHz may include both Mode A/C (broadcast) interrogations and Mode S
addressed interrogations. The selection of interrogation modes is highly adaptable.
The NEO can be configured to provide both Elementary and Enhanced surveillance (EHS)1. The NEO
system is equipped with area management function that allows configuration and adaptation of each
interrogator in accordance to both requirements and local conditions.
The final setting of all interrogation / transmitting subsystem is part of the system adaptation on site
and it is subject of the system user approval.
2.1.3.2.2. Transmission on 1090 MHz
The transmission on 1090 MHz contains only transmission of Mode S extended non-transponder
squitters (DF=18). These squitters ensure three main functions:
1
Typically NEO complies with ED-117 or ED-142 requirements some of which are mandatory and others which
are optional. The optional functionality may not be supported as standard.

MSS Description
 Integrity check (back-up of reference transponders)

 On-line calibration
 Multiranging
Each NEO interrogator needs a Mode S address from the end user CAA to be possible to transmit on
1090 MHz.
2.1.3.2.3. 1030/1090 Spectrum Management
The important aim of the MLAT transmitting design is a suppression of the interference with the
surrounding SSR. In NEO the two types of interrogations may occur.
o The addressed Mode S interrogations

This interrogations type does not interfere with the existing SSR due to the character of Mode S.
o The Mode A/C interrogations

This interrogations type can interfere with the existing SSR. The interference is recognized as
additional FRUIT. To minimize this interference the NEO uses the following precaution:
 Low number of NEO interrogators that will interrogate in Mode A/C

 Very low number of Mode A/C interrogations - usually between 2 and 8
interrogations per interrogator per one second
 Using of Mode A/C interrogations with short P4 pulse that blocks Mode A/C replies
from Mode S transponders
Mode A/C interrogation comprises an interrogation pattern that is transmitted with a given frequency.
Both pattern and frequency are configurable for each transmitting unit. The Mode A/C interrogations
are always transmitted with short P4 pulse to minimize the impact on surrounding SSR. Interrogation
with short P4 pulse elicits a Mode A or Mode C reply from a Mode A/C only transponder while a Mode
S transponder recognizes the short P4 pulse and does not reply to this interrogation.
2.2. Specific Application Architectures
The generic NEO by ERA architecture can be readily configured to optimise performance for specific
applications. This sub-section details the principal applications:
ADS-B Based Surveillance
Surface Movement Surveillance
Wide Area Multilateration
Precision Runway Monitoring (PRM)
Height Monitoring Unit (HMU)
The NEO by ERA architecture is flexible and can be tuned to provide enhanced performance whilst also
minimising cost. One example of this flexibility is in the choice of where signals are time-stamped. In
some installations the time related measurements are undertaken at the central server, denoted as
central timing. Whilst in other installations the time-stamping is undertaken at each ground station
receiver, in this case the time related measurements are distributed throughout the receiver array,
denoted as distributed timing.

MSS Description
2.2.1. ADS-B Based Surveillance
ADS-B based surveillance represents the simplest NEO implementation.
Automatic Dependent Surveillance – Broadcast (ADS-B) is an important component of next generation

air traffic management. Similar to MLAT, ADS-B offers significant cost and operational benefits over
traditional radar. Aircraft equipped with ADS-B automatically and constantly transmit position
information derived from the onboard navigation system, typically linked to a Global Navigation
Satellite System (GNSS), together with other aircraft information such as altitude, heading, velocity
and identification data.
The future of air traffic control calls for aircraft and vehicles to be equipped with appropriate Mode S
transponders transmitting Mode S extended squitters with ADS-B messages. These transponder units
are co-located with onboard GNSS receivers, which are used as the source of position data. The
position information is then coded into an ADS-B message and transmitted from the target as a Mode
S signal.
There can be two (2) variants of ADS-B surveillance system architecture:
 Stand-alone ADS-B system

 Centralised ADS-B system
2.2.1.1. Stand-alone ADS-B Surveillance System
In this case all the ADS-B processing is performed at the ADS-B Ground station (GS) and each GS
provides ADS-B reports in the required ASTERIX Category format. The ADS-B GS output ASTERIX data
via a separated data-link.
The minimum ADS-B based surveillance system is a single ground station connected directly to the
customers ATC application. A single ground station can receive Mode S signals from aircraft over a
significant area. The Mode S message contains the aircraft position, and hence a single ground station
is adequate for positioning.
However, in order to provide surveillance over a large area, the multiple ground station ADS-B system
would be required. With multiple sensors the coverage areas of the individual sensors will partially
overlap, thus the loss of a single sensor will only result in degraded performance not total loss as
would be the case with conventional primary surveillance radar. The greatest advantages are provided
by a wide-spread system.
The simplified architecture is shown in Figure 3.

MSS Description
1090 MHz ES GPS Data
RXS RXS RXS

GS_00 GS_01 GS_nn
ASTERIX ASTERIX ASTERIX
RCMS ATC
ATM System
Figure 3 Stand-alone ADS-B processing

A ground station for this application would consist of a 1090 MHz receiver, a power supply and a
processor module. An optional back-up battery provides for continued operation during power
failures. An example of an ADS-B ground station is shown in greater detail in Figure 4.
The receiver extracts the received pulse stream and sends the resultant data as video data to the
processor module, which decodes the Mode S message. The processor module then sends the relevant
ASTERIX format messages directly to the customers ATC application, via a standard LAN connection.
The equipment identified above represents the absolutely basic system, and in a typical installation
dual units would be employed, in order to provide either for redundancy or to overcome mast
shielding, or both.
1090 MHz
1090 MHz GPS
ADS-B GS
1090 MHz Power Supply Battery

Site Monitor Processor Module
Receiver Module Module
Dual LAN Diagnostics
Figure 4 Single Ground Station ADS-B Receiver Schematic
2.2.1.2. Centralised ADS-B Surveillance System
In a Centralised ADS-B system the processing is distributed between ground stations and a central
processing server, which can optimise the processing by the use of:
 mutual check of the ADS-B messages between different channels (different remote
stations)
 complementary information from different channels

MSS Description
The server outputs the ADS-B reports in the required ASTERIX Category format.
The deployment of multiple sensors has several benefits. A wide-spread system, by its very nature, is
naturally resilient, as the loss of a single sensor the coverage is maintained by adjacent sensors.
The generic architecture is shown in Figure 5, below. The set of ground stations send processed Mode
S data (1090 ES) to a central server.
1090 MHz ES
GPS
RXS RXS RXS RXS

Central Processing
Server (CPS)
ASTERIX
/SNMP
ATC RCMS
ATM System
Figure 5 Centralised ADS-B processing Schematic

Please note that there is an optional upgrade of the Centralized ADS-B system to provide wide area
multilateration (WAM). Generally there are two (2) possible scenarios:
 ADS-B System + WAM target validation

 ADS-B system output + WAM output
2.2.1.2.1. Upgrade ADS-B System + WAM Validation
In this case the wide area multilateration is used for ADS-B position integrity check (in case the target
is visible only from two GS, a measured TDOA should be employed for checking the ADS-B position).
This independent position estimate increases data confidence, as it provides an alternative position to
that generated directly from the aircraft.
The NEO outputs ADS-B target position (ASTERIX CAT021) validated by multilateration, as shown on
following Figure 6:

MSS Description
1090 MHz ES
GPS
RXS RXS RXS RXS

Central Processing
Server (CPS)
ASTERIX (WAM validated)/

SNMP
ATC RCMS
ATM System
Figure 6 Upgraded ADS-B system + WAM validation
2.2.1.2.2. Upgrade ADS-B & WAM
This ADS-B system optional upgrade will serve both ADS-B and WAM surveillance. The NEO will
provide independent output on separate channels for WAM (Asterix CAT020) and ADS-B (Asterix
CAT021).
WAM can provide substantial advantages when combined with ADS-B:
 Multilateration works with existing (Mode A, Mode C, Mode S, ADS-B) transponders. There is
no need for new avionics for WAM to work. WAM will provide immediate coverage for 100%
of all aircraft which are visible to MSSR.
 All aircraft are visible to the combined ADS-B & WAM surveillance system, whether they have
ADS-B or not.
Generic architecture is shown on Figure 7 below, independent WAM and ADS-B reports are provided:
1090 MHz ES
Mode A/C/S GPS
RXS RXS RXS RXS

Central Processing Server

(CPS)
(ADS-B + WAM processing)
ASTERIX (WAM + ADSB)/

SNMP
ATC RCMS
ATM System
Figure 7 Upgrade ADS-B + WAM

MSS Description
2.2.2. Wide Area Multilateration
As described above Wide Area Multilateration (WAM) provides coverage of all aircraft equipped with
Mode A/C/S transponders and there is no need for new avionics. WAM has become an important tool
in the controlling and monitoring of aircraft in terminal manoeuvring areas, final approach and en-
route Air Traffic Control (ATC). As an independent, cooperative system, it is now a significant element
in ATC surveillance.
WAM systems are type certified in numerous countries against radar standards, such as ICAO ANNEX
10, and has been operationally certified for 3nm approach separation. Thus, NEO by Era is an excellent
MSSR replacement, providing high accuracy, greater update rates, better coverage and improved
reliability at a much lower cost.
NEO by Era is a completely modular system, easily adaptable to any terminal and wide area
requirements as well as all terrain challenges. For each deployment, the best architecture
configuration and related data link technology are carefully selected to meet the requirements of the
customer with optimal utilisation of the available infrastructure, e.g. copper wires, optical fibres,
wireless connections, etc. The system is also designed to be enhanced for full 3D air surveillance
within the entire TMA area.
In areas with sufficient Mode A/C/S interrogation provided by local MSSR or in areas with transponder
overloading problems, NEO by Era provides a fully passive solution and utilises all available SSR replies
to locate, identify and track aircraft. In this application, there is no need for additional transponder
interrogation.
Era’s system can also serve as a means for duplication, as it is mandated that en-route airspace and
terminal areas require duplication for surveillance. NEO has been fully certified to provide such
duplication for wide area and terminal surveillance solutions worldwide.
2.2.2.1. WAM Active Surveillance System
The basic components of an active Wide Area Multilateration System are shown in Figure 8, below.
Mode A/C/S
RXS TXS RXS RX TX

Central Processing
Server
ASTERIX
/SNMP
ATC RCMS
ATM System
Figure 8 Active Wide Area Multilateration NEO Architecture

MSS Description
An array of ground station receivers are deployed throughout the desired coverage area. Each ground
station receiver intercepts transmissions from target aircraft, these transmissions being triggered by
either nearby Secondary Surveillance Radar (SSR), or an interrogator controlled by the NEO. The SSR
transmissions include Mode A, Mode C and Mode S.
An active NEO can also be used to calculate the range to the target in a similar way that MSSR and
ACAS systems do.
Distributed time (DT) synchronisation is a common implementation for WAM applications as it is

advantageous to reduce the data bandwidth, with respect to communications between the array of
ground station receivers and the central processor.
2.2.2.2. WAM Passive Surveillance System
The basic components of a totally passive Wide Area Multilateration System are shown in Figure 9,
below.
Mode A/C/S
RXS RXS RXS RXS

Central Processing
Server
ASTERIX
/SNMP
ATC RCMS
ATM System
Figure 9 Passive Wide Area Multilateration NEO Architecture
The passive system outlined above intercepts responses from existing interrogators, and hence, has
the advantage that it does not require a transmission licence. The second attendant advantage is that
signal density is not increased as there is no increase in either interrogations at 1030 MHz or replies at
1090 MHz.
A passive system is suitable for areas where there is adequate activation of transponders. A passive
system can include an interrogator, which is only switched on when a local MSSR interrogator fails.
This arrangement ensures reliable coverage even when an attendant MSSR fails.
This example of a passive WAM system is a distributed time NEO configuration, as described in the
previous sub-section.

MSS Description
2.2.3. Surface Movement Surveillance
Era NEO is an invaluable addition to surface surveillance with its ability to work as part of an Advanced
Surface Movement Guidance and Control System (A-SMGCS) or can be also deployed as a stand-alone
sensor providing surveillance data directly to ATM system.
The A-SMGCS provides controllers with complete situational awareness. A-SMGCS provides both
location and identification of all suitably equipped aircraft and vehicles within the manoeuvring area.
The introduction of a secure and high-quality monitoring system not only increases safety, but also
improves efficiency and airport throughput.
In conditions of restricted or reduced visibility the benefits of the system are even greater, as
controllers are still able to “see” the location of all aircraft and vehicles. An additional level of safety is
also added through an automated alerting facility which identifies potential conflicts on the runway.
The A-SMGCS is only made possible with the highly detailed surveillance provided by multilateration.
Key benefits of A-SMGCS are:
 Improved Surveillance
 Improved Safety
 Increased Airport Throughput
 Increased Efficiency
 Secure Labelling for uninterrupted identification of aircraft and vehicles
 Enhanced procedures to make best use of improved surveillance capabilities
 Runway incursion alert system
The following sub-section details a typical surface movement surveillance system.
2.2.3.1. Surface Movement Active Surveillance System
An active surface movement NEO architecture is shown in Figure 10.
Mode A/C/S
RXS TXS RXS RX TX

Central Processing
Server
ASTERIX
/SNMP
ATC RCMS
ATM System
Figure 10 Active Surface Movement NEO Architecture

MSS Description
An array of ground station receivers are deployed throughout the desired coverage area. Each ground
station receiver intercepts transmissions from target aircraft, these transmissions being triggered by
either nearby Secondary Surveillance Radar (SSR), or an interrogator controlled by the NEO. The SSR
transmissions include Mode A, Mode C and Mode S.
The Era interrogator/transmitter (TXS) is a simpler and smaller device than a conventional MSSR
interrogator. The TXS uses either a fixed omni-directional antenna or a sectored antenna, as there is
no need for a rotating antenna, as is the case for a conventional MSSR.
An active NEO can also be used to calculate the range to the target, in a similar way that MSSR and
TCAS systems do.
2.2.4. Precision Runway Monitoring (PRM)
Independent parallel operations during Instrument Meteorological Conditions are typically limited by
current radar surveillance to runways separated by 4,300 feet or more. PRM provides Air Traffic
Control (ATC) with a display of arrivals along an extended centreline. In the event that an aircraft flies
towards the adjacent runway’s extended centreline, a PRM system automatically alerts ATC.
By taking advantage of PRM displays and high accuracy and update rate surveillance techniques,
runway separations of 3,400 feet can be safely supported for independent parallel operations, as is
provided by the PRM E-scan system.
CAA organisations are committed to buying several PRM E-scan systems and plan to install them at
heavily used airports that have closely spaced parallel runways. The surveillance sensor cost
constitutes a high percentage of the overall system cost. Consequently, the CAA organisations (like
FAA) has been evaluating alternative surveillance techniques including multilateration/ADS-B that
promise to be as capable, if not more, at a much lower cost.
Era’s PRM application at Palma de Mallorca, Spain demonstrated that Mode A/C/S multilateration
accuracy, coverage and update rate exceeded the current FAA PRM requirements.
Figure 11 PRM Approach Scheme

MSS Description
Comparison between E-SCAN and MSS is summarised below:
Parameter PRM Raytheon Specification NEO-PRM ERA Specification

Type Monopulse secondary Surveillance Multilateration surveillance system (WAM) for
radar (MSSR) for civil air traffic control civil air traffic control
Function Interrogates Mode A & C transponders, Interrogates Mode A, C, S transponders; and
determines aircraft range and azimuth employs transponder responses excited by other
angle, displays target information on interrogators. Processes Mode S squitters and
high-resolution display with audible and Mode S ES ADS-B messages. Determines aircraft
visual alerts 3D position, displays target information on high-
resolution display with audible and visual alerts.
System Electronically scanned beam over 360 Set of 4 (or more) receiving stations deployed
configuration degrees around aerodrome area. Interrogator at 1030
MHz optionally.
Frequency 1030 (transmit), 1090 (receive) 1030 (transmit - optional), 1090 (receive)
Antenna size Circular 17.1 ft diameter (5.2 m), 5.1 ft Receiving antenna: omnidirectional, vertical
high (1,6 m) dipole, length 769 mm
Transmitting antenna: omnidirectional, vertical
dipole, length 825 mm (Optional, only if
interrogator used)
Antenna 3.2 degrees (AZ) search, 1.6 degrees N.A.
beamwidth (AZ) track; 11 degrees (EL)
Azimuth Within 0.057 degrees (1 milliradian); Within 0.0057 degrees (0.1 milliradian) or 10 m
Accuracy over 360 degrees of horizontal coverage (whichever is greater); over 360 degrees of
horizontal coverage
Range Greater than 32 NM (59 km), Greater than 32 NM (59 km), expandable beyond
coverage expandable to 200 NM (370 km) 200 NM (150 km)
Range Less than 0.1 NM (185 m) Less than 0.03 NM (60 m) (depends on geometry)
resolution
Target More than 40 targets at 1.0-second More than 200 targets at 1.0-second update rate
tracking update rate while searching for new while searching for new targets
targets
Built-in Test Full BIT initiated at power up; in every YES, Extensive Management system with BITE
(BIT) second, a minimum of 450 ms
Table 2 Comparison between E-SCAN and NEO
2.2.5. Height Monitoring Unit (HMU)
Reduced Vertical Separation Minima (RVSM) is used to describe the vertical separation reduction from
2,000 ft to 1,000 ft for aircraft flying between FL 290 and FL 410. With few exceptions, the vast
majority of aircraft that operate in European skies required certification to operate in RVSM airspace
and were measured against very exacting criteria.
To prove the aircrafts capability of maintaining an accurate height position, a height monitoring unit
was needed with an accurate surveillance capability, a software process to establish the total vertical
errors and an interface to a central database to correlate the information.

MSS Description
The only system capable of providing independent 3D data is multilateration. Era’s multilateration
system, was subsequently chosen to support Eurocontrol’s height monitoring unit. The vertical
trajectory, measured and maintained by the airborne systems (barometers, automatic pilots) is
reported to the ground by 1090MHz data link (Mode C, Mode S). This is then compared to the
geometric height measurement using the principle of localisation by multilateration. The parameters
that ensure the quality of the vertical measurement are the dispersion of the receivers and the
truncation of the vertical coverage at high levels.
Figure 12 Height monitoring by Multilateration
In 1999 Era was awarded the contract to deliver height measuring equipment to Eurocontrol to be
integrated into the Linz HMU, the first HMU in the Eurocontrol region.
Highly accurate and effective ATC surveillance was essential for this project. In selecting Era as the
supplier and design authority for the HME, Eurocontrol was ensuring they had the very best
technology available in the global ATC marketplace. Era has been selected in another two recent
tenders to supply HMU for Strumble region, UK (NATS) and Okayama region, Japan (JCAB).

MSS Description
3. System Performance
This section describes the NEO performance, with reference to the relevant EUROCAE specification.
The various configurations of the NEO by ERA typically exceed the requirements of the specification for
the respective applications:
o ADS-B Based Surveillance: ED126 ‘SAFETY, PERFORMANCE AND INTEROPERABILITY

REQUIREMENTS DOCUMENT FOR ADS-B-NRA APPLICATION’
o Surface Movement: ED117 ‘Minimum Operational Performance Specification for

Mode S Multilateration Systems for use in Advanced Surface
Movement Guidance and Control (A-SMGCS)’, section 3.3
o Wide Area Multilateration: ED142 ‘Technical Specification for Wide Area Multilateration
System’, section 3.3
3.1. ADS-B Based Surveillance
This sub-section details the NEO performance as relevant to the specific application of, as defined in
section 3.5.2 of EUROCAE document ED126/DO-303 ‘SAFETY, PERFORMANCE AND INTEROPERABILITY
REQUIREMENTS DOCUMENT FOR ADS-B-NRA APPLICATION, see document [2].
The Performance requirements have been grouped into four major areas:
 functional integrity and availability/continuity of the ADS-B GSys;

 timing requirements on the processing and distribution of the information;
 update intervals;
 ground monitoring requirements.
The update interval and the Time to alert requirements are defined for the following separation
minima separately:
 5NM in En-route airspace;

 3NM in TMA (terminal airspace).
3.1.1. Integrity and availability/continuity
The NEO reliability and availability is explained in chapter 8 of this document.
3.1.1.1. Data Integrity
The probability that NEO corrupts ADS-B information (through the reception, processing or delivery of
data) is  5e-06 per ATSU hour.
3.1.1.2. System Reliability
The probability that NEO does not provide updated ADS-B surveillance reports for more than one
aircraft (from which ADS-B messages are being received) is  5e-06 per ATSU hour
The probability that NEO does not provide updated ADS-B surveillance reports for one aircraft (from
which ADS-B messages are being received) is  1e-04 per ATSU hour

MSS Description
3.1.2. Time of Applicability Accuracy
In NEO the Time of Applicability conveyed in the ADS-B Surveillance Report has an absolute accuracy
relative to UTC of +/- 0.2s or less.
Each type of the ADS-B Surveillance Report (Position, Identity, Emergency/SPI) contains a time of
applicability.
3.1.3. System Latency
The 95% latency for ADS-B Surveillance Reports is  0.5s
The maximum latency from the time of receipt of an ADS-B message from an aircraft to the output of
the corresponding ADS-B report is 0.5 seconds. This apply to all the event-driven ADS-B reports (not to
the reports generated in the periodic mode)
3.1.4. Update Rates

Performance Airspace type
Description
Requirements TMA En-route
The update interval between successive Surveillance
Position Reports for any single aircraft is no longer T 5s T  10 s
Update than T [s] with a probability of 95%.
Interval The update interval between successive Surveillance
Identity Reports for any individual aircraft shall be no T  100 s T  100 s
longer than T [s] with a probability of 95%.
Time to Alert The time to alert for a change in Surveillance
Emergency/SPI Reports shall be no longer than T [s] T  5 s T  10 s
with a probability of 95%.
Table 3 Update rate for ADS-B system
3.1.5. System Capacity
The capacity of the NEO is to simultaneously process ADS-B messages from at least 500 targets and
output corresponding ADS-B reports for each target at the maximum update rate of four ADS-B reports
per target per second. The NEO processor time do not exceed 50%.
The NEO continuously monitor the number of simultaneously tracked targets. When the number of
targets exceeds a configurable maximum target capacity threshold an overload mechanism is applied:
 the overflow indicator (ODP bit) is set in item I023/100 of ASTERIX Category 023 reports
 according to the current settings either the "NOGO" status or the "Degraded" or the "Failed"
service status shall be reported.
3.2. Surface Movement
This sub-section details the NEO performance as relevant to the specific application of A-SMGCS, as
defined in chapter 3.3. of EUROCAE document ED117 ‘Minimum Operational Performance
Specification for Mode S Multilateration Systems for use in Advanced Surface Movement Guidance
and Control (A-SMGCS)’, 2003, see document [1].

MSS Description
3.2.1. Update Rate [ED-117 3.3.1]
The minimum update rate for any target in the coverage area is designed to be 1 per second average,
based on the squitter rate of mode S transponders. This update rate will not always be possible, due to
some transmissions not being detected. The acceptable probabilities of this are stated in 3.2.2 [ED-117
3.3.2].
3.2.2. Probability of Update [ED-117 3.3.2]
3.2.2.1. Apron [ED-117 3.3.2.1]
The probability of achieving a 1 second average update rate for any Mode S transmitting target in the
apron area is at least 0.7.
This parameter is dependent on the number and location of ground stations in the system design. In
many deployments an Era NEO performs significantly better than the requirements of ED-117; a typical
result is presented in Table 4, below.
Applicable Range Evaluated Result
≥ 70% 99.53% OK
Table 4 SAT Results for Asturias International Airport – Probability of Update [ED-117 3.3.2.1]
3.2.2.2. Stand [ED-117 3.3.2.2]
stand area is at least 0.5.
≥ 70% 99.52% OK
Table 5 SAT Results for Asturias International Airport – Probability of Update [ED-117 3.3.2.2]
3.2.2.3. Manoeuvring Area [ED-117 3.3.2.3]
manoeuvring area is at least 0.95.
3.2.2.4. Airborne Targets [ED-117 3.3.2.4]
The probability of achieving a 1 second average update rate for any airborne Mode S transmitting
target in the coverage area is at least 0.95.
3.2.3. Position Accuracy [ED-117 3.3.3]

MSS Description
Sector Applicable Range Evaluated Result

Manoeuvring Area ≤ 7.5 m with confidence level of 95% 4.69 m OK
Stands ≤ 20 m with confidence level of 95% 6.29 m OK
Table 6 SAT Results for Budapest Airport - Position Accuracy [ED-117 3.3.3]
3.2.3.1. Manoeuvring Area
The NEO calculates the horizontal positions of targets detected on the runways, taxiways and centre
lines of the apron areas to within 7.5 m with a confidence level of 95% and to within 12 m with a
confidence level of 99%.
3.2.3.2. Stands
The NEO calculates the horizontal positions of targets detected on Stands to within 20 m averaged
over a period of 5 seconds.
3.2.3.3. Airborne Targets
The NEO calculates the horizontal positions of airborne targets detected at a range of less than 2.5 Nm
from the runway threshold to within 20 m to a confidence level of 95%.
The NEO calculates the horizontal positions of airborne targets detected at a range between 2.5 Nm
and 5 Nm from the runway threshold to within 40 m to a confidence level of 95%.
3.2.4. Probability of MLAT Detection [ED-117 3.3.4]
The NEO detects and calculates a position for each active Mode S transponder on runways and
taxiways within any two-second period with a probability of detection better than 99.9%. For each
active Mode S transponder in the stands it will be within any 5-second period with a probability of
detection better than 99.9%.
Sector Applicable Range Evaluated Result
Manoeuvring Area ≥ 99.9% 99.99% OK
Stands ≥ 99.9% 99.99% OK
Table 7 SAT Results for Budapest Airport - Position Detection [ED-117 3.3.4]
The NEO probability of multiple targets detection is less than 10-4.
3.2.5. Probability of Identification (PID) [ED-117 3.3.5]
The NEO provides the correct target identity with a probability of better than 99.9%.
3.2.6. System Capacity [ED-117 3.3.6]
The NEO is able to support more than 250 targets at a time creating one target report each per second
within the given operational radio environment.
The NEO reports to the user if the system capacity is being exceeded to prevent unreliable data from
being used operationally.

MSS Description
The NEO performance degrades gracefully in the event of an overload.
To determine the system capacity limit, it is assumed that all receivers contribute to each target
position calculation.
The NEO design has potential for increased capacity due to airport growth.
3.2.7. Latency [ED-117 3.3.7]
The delay between Mode S signal reception and outputting the target report from the MLAT system
does not exceed 0.5 seconds.
3.2.8. Start - Up Time [ED-117 3.3.8]
The NEO CPS is fully operational within 3 minutes of initial start-up or re-start including instances of
main power loss.
After a start-up or restart the system runs with the last known configuration setting and in the last
know Mode of operation.
3.2.9. Track Initiation [ED-117 3.3.9]
The NEO initiates a track on a properly equipped aircraft within 5 seconds of either initial transponder
turn on or upon entering the coverage area.
≤5s 3.8 s OK
Table 8 SAT Results for Palma de Mallorca Airport – Track Initiation [ED-117 3.3.9]
3.2.10. Probability of False Detection (PFD) [ED-117 3.3.10]
The probability of the NEO outputting False Targets is less than 10-4.
≤ 0.1% 0.0% OK
Table 9 SAT Results for Cape Town International Airport – Probability of False Detection [ED-117 3.3.10]
3.2.11. Probability of False Identification [ED-117 3.3.11]
The probability that the NEO incorrectly identifies a target that correctly announces its identity is less
than 10-6 over any 5-second period per target.
The Era NEO exceeds the requirements of ED-117; a typical result is presented in Table 9, below.

MSS Description
many deployments an Era NEO performs significantly better than the requirements of ED-117. As an
example SAT result from Cape Town is presented in Table 10, below.
≤ 0.001% 0.0% OK
Table 10 SAT Results for Cape Town International Airport – Probability of False Identification [ED-117 3.3.11]
3.2.12. Switchover Time [ED-117 3.3.12]
For systems configured with redundant target processor systems the time for switchover from primary
to backup shall be < 3 seconds with no loss of target data.
The time for switchover from primary to backup target processor is < 3 seconds with no loss of target
data, where an NEO has been configured with redundant target processors.
3.2.13. System Resolution
System resolution ability is the resolution to which the NEO is able to process and output the target
position, target velocity or target time.
The NEO target report position resolution is 1 [m].
The NEO target velocity resolution is 1 [knot] (1.851 km/h).
The NEO target time stamp resolution is ≤ 10 ms (exactly 1/128 s).
3.3. Wide Area Multilateration
This sub-section details the NEO performance as relevant to the specific application of Wide Area
Multilateration (WAM), as defined in chapter 3.3 of EUROCAE document ED142 ‘Technical
Specification for Wide Area Multilateration System’, see document [4].
The performance specified in this section are applicable to the targets located within the defined
operational coverage volume of the system.
3.3.1. Update Interval [ED-142 3.3.1]
The NEO is designed to meet the specified performance requirements at the defined Update Interval.
The defined Update Interval does not exceed the following:
 8 seconds for the En-route application

 5 seconds for the TMA application
3.3.2. Update of change aircraft information [ED-142 3.3.2]
The NEO output changes in the ACID and Mode A code (where required by user) within 3 times the
maximum Update Interval (24 seconds for the En-route application and 15 seconds for the TMA
application) with a probability of 95%.
The NEO output changes in the Emergency codes and SPI (where required) within the maximum
Update Interval (8 seconds for the En-route application and 15 seconds for the TMA application) with a
probability of 95%.

MSS Description
3.3.3. Probability of Position Detection [ED-142 3.3.3]
The NEO detects and calculates position for any target within the defined Update Interval with the
probability better than or equal to 97%.
3.3.4. Probability of Long Position Gaps (PLG) [ED-142 3.3.4]
The probability of long position gap for more than 3 times the maximum Update Interval +10% (26.4
seconds for En-route application and 16.5 seconds for TMA application) is less than or equal to 0.1%.
3.3.5. Probability of False Detection [ED-142 3.3.5]
The probability of the NEO outputting False Target is less than or equal to 0.1%
3.3.6. Probability of Code Detection [ED-142 3.3.6]
The NEO provides the correct ICAO 24bit aircraft address with a probability greater than or equal to
99%.
The NEO provides a correct and validated Mode A code with a probability greater than or equal to
98%.
The NEO provides a correct and validated Mode C code with a probability greater than or equal to
96%.
3.3.7. Probability of False Code Detection [ED-142 3.3.7]
The probability of the NEO outputting False Mode S address, Mode A, Mode C or aircraft identification
is less than or equal to 0.1%.
3.3.8. Horizontal Position Accuracy [ED-142 3.3.8]
MLAT Position accuracy heavily depends on system geometry, see Appendix A.2. The proposed system
is designed to do not exceed:
 350 m RMS for the En-route application

 150 m RMS for the TMA application
3.3.9. Target Report Time Stamp [ED-142 3.3.9]
The NEO provides time-stamping of target position synchronized with UTC. NEO can use multiple time
sources as time reference. This allows using all available combination of time sources: supplied NTP
servers or external provided NTP servers. The time sources are selected by the (S)NTP clients, based on
priority.
The timing error between the time stamp (UTC Time of Day) associated with a target report and the
Time of Applicability of the target report is less than or equal to 100 ms.
3.3.10. Positional Resolution (Mode A/C) [ED-142 3.3.10]
Positional resolution is specified for two close targets equipped with the Mode A/C transponders
within two horizontal separations, according the following table:

MSS Description
Horizontal Airspace type

Separation En-route service TMA service
Separation 1 3500 m (2 NM) 1200 m (0.6 NM)
Separation 2 7000 m (4 NM) 3500 m (2 NM)
Table 11 Positional Resolution
3.3.10.1. Positional Resolution - Position Detection [ED-142 3.3.10.1]
The NEO detects and calculates position of two different targets equipped with Mode A/C transponder
within defined Update Interval with the probability greater than or equal to:
 60% at Separation 1
3.3.10.2. Positional Resolution - Mode A/C Code Detection [ED-142 3.3.10.2]
Detection of correct Mode A and C code of two different targets equipped with Mode A/C
transponder, within defined Update Interval is done with probability greater than or equal to:
3.3.11. Processing delay [ED-142 3.3.11]
The NEO can output data in both Data Driven and Periodic mode.
In Data Driven Mode, the processing delay is less than or equal to 1 second measured from the time of
reception of the target signal at a receiving unit to the WAM system outputting a target report.
Note: It is assumed, that the delay of the communication infrastructure used within the WAM system
will not exceed 500 ms.
In Periodic mode, when the Predicted Position at time of output is transmitted, the maximum
processing delay shall be 0.5 second.
3.3.12. Track Initiation [ED-142 3.3.12]
This parameter is dependent on the number and location of ground stations in the system design.
The NEO track initiation time of aircraft with an active transponder is less than or equal to 5 times the
defined Update Interval of either initial transponder turn on or upon entering the coverage area. This
track initiation time is met with the probability of 99%.
For the systems designed to detect aircraft during the take-off the time from initial transponder turn
on or upon entering the coverage area to the to the output of the first position target report is less
than or equal to 3 times the defined Update Interval with the probability of 99%
3.3.13. Target Capacity [ED-142 3.3.13]
It is assumed that all receivers contribute to each target position calculation.
The overall tracking capacity of the NEO system is 500 automatically tracked targets, out of them, a
maximum of 100 Mode A/C only targets.

MSS Description
Target overload conditions are detected and displayed on the Management System. When the NEO
tracker detects a target overload condition it is reported by the Management System. When the
system is in overload data is lost until the overload situation is recovered
The NEO design has potential for increased capacity due to air traffic growth.

MSS Description
4. System Architecture and Design

This section provides a description of the architecture and design of the NEO by ERA system.
NEO is characterized with modular concept and it can comprise following units:
Ground stations (GS) – utilise generic modules and selection of antennas that can be combined in such
a way as to provide solutions to specific applications. It can be configured as a receiving unit (RXS),
transmitting unit (TXS), receiving/transmitting unit (RXTXS), reference transponder RMTR, etc.)
Central Processing Station (CPS) – the CPS is the heart of the system and performs multilateration
calculation, target, data and system management and sending ASTERIX output data into upper system
Remote Monitoring Terminal (RMT) – it enables remote access to the NEO Management System that is
running on redundant Management Servers. This terminal allows maintenance engineers to monitor,
control and administrate the whole system. The RMT also enables to display and replay output data of
the NEO.
4.1. Ground Station Architecture
Era has developed a unique modular universal ground station design concept. This means that all of
the specific remote ground stations (RXS, TXS, combined RXTXS, Reference Transponder, etc.) are
readily configured in a standard enclosure using a range of standard modules.
Figure 13 An Example of a Ground Station Assembly
Each module is enclosed in an aluminium alloy box. Modules are mounted into a cabinet (made up of a
stainless steel and fibreglass composite) by slip–on holders and locked by fastening screws. The
cabinet, as a whole, is prepared for installation onto a mast, wall or other construction.
4.1.1. Receiving Unit (RXS)
There are two different Receiving Units (RXS) arrangements, dependant upon the timing architecture
deployed (see section 2.1.1):
 Central Time (CT) Receiving Unit

 Distributed Time (DT) Receiving Unit
4.1.1.1. CT Receiving Unit

MSS Description
The SSR signals are extracted, from the 1090 MHz carrier, by the receiver which outputs a pulse stream
maintaining both the timing information and data content of the SSR transmission. In this application
central time measurement is implemented. The pulse stream, from the receiver, is communicated to
the central server via a suitable communication link (typically fibre optic). The typical component
modules of a CT Receiving Unit are shown in Figure 14, below.
1090 MHz
RXS
Power Supply 1090 MHz

Battery Module
Module Receiver
Figure 14 CT Receiving Unit Schematic F/O
4.1.1.2. DT Receiving Unit
In a distributed time NEO the Time of Arrival (TOA) measurement of SSR signals is undertaken in the
individual receivers.
The SSR signals are extracted, from the 1090 MHz carrier, by the receiver which outputs a pulse stream
maintaining both the timing and data of the SSR transmission. In this application distributed time
measurement is implemented. The pulse stream, from the receiver, is fed to the processor module.
The processor module decodes the pulse stream and time stamps the leading edge of the pulse
stream. The data, aircraft ID, etc, and timing data are then transmitted to the CPS.
The typical components of a DT Receiving Unit are shown in Figure 15, below.
1090 MHz
RXS
Power Supply Processing Receiving

Battery Module
Module Module Module
Figure 15 DT Receiver Unit Schematic LAN
4.1.2. Transmitting Unit (TXS)
The components of a transmitting unit (TXS) are shown in Figure 16. The primary element is the
interrogator, supported by a power supply and its associated battery. The TXS is controlled from the
CPS, via a LAN.

MSS Description
1030/1090
MHz
TXS
Power Supply Transmitting

Battery Module
Module Module
Figure 16 Transmitting Unit (TXS) Schematic LAN
4.1.3. Reference and Monitoring Transponder (RMTR)
Reference transponder (RMTR) is used for integrity and system accuracy checking. It periodically
transmits short Mode S squitter and Mode S replies to selective interrogation. The Transponder
module is typically based on standard COTS Mode S transponders. It can be designed as a standalone
station or can be integrated with the receiving unit (RXS). The functions of RMTR can be replaced by
transmitting station (TXS) or by site monitor.
The components of an RMTR are shown in Figure 17, below.
1030/1090
MHz
RMTR
Power Supply Transponder

Battery Module
Module Module
Figure 17 Reference and Monitoring Transponder (RMTR) Schematic
4.1.4. Other GS Assemblies
Thanks to the unique modular concept, as described above, there can be various types of GS
configuration. Below are listed only some other typical examples:
 Dual receiving unit (RXRX);

 Receiving/transmitting unit (RXTXS);
 Receiving/transponder unit (RXRMTR).
4.1.5. Ground Station Deployment
Each system deployment depends on the extent of the surveillance area and on the required levels of
accuracy. At least four sensors should be able to “see” each part of the surveillance area in order to
detect target, see Appendix A. Whilst the geometry of the design has a significant impact on solution
accuracy, the best results are when the aircraft is surrounded by the sensors. For these reasons, a
typical solution will consist of a “ring” of number of ground stations. To provide redundancy in the
solution the typical NEO comprises more ground stations than necessary to achieve the required
accuracy.

MSS Description
When deciding where to place sensors, outside factors must be taken into account. For example:
 Ground Stations need power and communications connections, therefore existing

sites or buildings with these connections are preferred.
 An environment that is secure from malicious damage is desirable. Existing navigation
aid sites may be used.
Signals emitted by aircraft can be received by suitable antennas up to 250Nm away from the source.
However, one must take into account that signals are easily blocked by hills, buildings and even trees.
In effect, the signal reception requires a “line-of-sight” to the area under surveillance, therefore sites
should be chosen in elevated positions, away from obstructions and with good views to the horizon.
Mobile phone towers are often particularly appropriate locations to install Ground Stations, with
connections, security and a tower already available to improve visibility.
4.1.5.1. Physical Mounting
GS cabinets are prepared for installations onto a mast, wall or other construction. The cabinet, as a
whole, is fixed to the ground construction at dedicated points. An example of a CT Receiving station
installation is depicted in the following figure.
Figure 18 Example of the Receiving station installation on the light pole
4.1.5.2. Antenna Location
Antennas must be high enough so that they provide a line-of-sight reception of aircraft transponder
transmissions. Generally, the higher they are the better. The receiving or transmitting antenna can be
installed on the holder placed on the top of a mast or on the roof of a building. An example of an
AL1W antenna installation is given in the following figure.

MSS Description
SSR antenna holder long

EX0200A00408 (welded nuts)
EX0200A00445 (without welded
nuts)
M12 19mm
36Nm
Reduction
Bolt M12
M12 19mm
52Nm
Screw M6x35
Lock washer Antenna mounting
tube on tower
M6 Hex
key no.5
6 Nm
Screw M6x16
Lock washer
Figure 19 An example of AL1W antenna installation – long support holder
4.1.5.3. Lightning and Surge Protection
Era has extensive experience implementing multilateration systems in locations with unreliable power
supplies (Armenia, Latvia) and with challenging weather conditions involving frequent thunderstorm
activity (Singapore, Kuala Lumpur).
The following components ensure lightning and surge protection of the Ground station equipment:
 The power supply module is equipped with two-stage, single-phase surge protection
devices with a high-frequency filter and thus provides surge protection from power
network to the other modules of the ground station.
 Lightning rods installed on the top of the antenna mast (Antenna AL4W has
embedded lightning rod).
 The 1030-1090MHz over-voltage protection installed in receiving module to protect
all electric equipment against atmospheric surge and the secondary effect of
lightning.
 When antenna cables pass through the wall inside the building the extra overvoltage
protections are installed. Typically the overvoltage coaxial protective element 1030-
1090 MHz for MLAT antennas and protection KO-3GN (Hakel) for GNSS antennas is
used.
4.1.6. Protection Areas
Here defined protective areas apply to all omnidirectional antennas positions of the NEO
system. The compliance with it is necessary for proper system operation.
4.1.6.1. Protective sector A
Sector A is a circle of radius 10 m centered on the fundamental point of protection area. This
point corresponds with antenna’s foot (mounting flange). In this sector, there is a prohibition of
constructions, overhead lines, railway lines and metal fences. At the level of the base point and

MSS Description
below it there must not be any continuous horizontal metal surfaces greater than 0.5 m2.
Flashing of the attic of the width to 0.3 m is permitted within a distance of 2m and only in the
cutting direction.
Location of other radio equipment in this sector should be assessed with regard to their
interaction.
Collecting rod of the lightening conductor can be placed at a distance of 0.6 meters from the
antenna centre.
4.1.6.2. Protective sector B
Sector B has the shape of circular ring of radius r1 = 10 m and r2 = 50 m and is centered on a
basic point of protective area. In this sector are permitted only: constructions or their parts
which do not contain metal structures, metal roofing and metal fencing.
Location of other radio equipment in that the sector needs to be assessed with regard to their
mutual interaction.
Objects must not exceed the conical surface with a peak at the end of the sector A, rising away
from the device at an angle of 2 °.
4.1.6.3. Protective sector C
Sector C has the shape of circular ring of radius r1 = 50 m and r2 = 100 m and is centered on the
basic point of protective area. In this sector are not permitted industrial buildings such as
warehouses, silos and hangars with metal shell.
Objects must not exceed the conical surface with a peak at the end of the sector B, rising away
from the device at an angle of 2 °.
Fig. Obstruction protective area of an omnidirectional antenna

MSS Description
4.2. Central Processing Station
The Central Processing Station (CPS) is the heart of the NEO. Generally in NEO there are two different
CPS configurations, depending on system time synchronization used (Central Time – CT
synchronization or Distributed Time – DT synchronization).
The following Figure 20 and Figure 21 clearly show chain of SSR signal detection and processing for
both cases. The first figure depicts signal chain for central time (CT) synchronization architecture
whereas second picture represents distributed time (DT) synchronization.
Digitization Synchro Data

Signal reception Data Transfer Target processing Data transfer Target interrogation
Time stamping nization transfer
RX Custom datalink MU PCI TP Custom datalink T02-XX

(Sync)
RXS CPS TXS
Figure 20 Signal chain for CT synchronisation NEO
Digitization Synchro Target

Signal reception Data transfer Data transfer Data transfer Target interrogation
Time stamping nization processing
RX Videosignal MU + PC LAN/WAN TP LAN/WAN T02-XX

(Sync)
RXS CPS TXS
Sync
signal
Figure 21 Signal chain for DT synchronisation NEO
The CPS ensures the following main functions:
 Reception of the measured SSR data from all connected Receiving Stations (RXS) and
Receiving/Transmitting Stations (RXTXS),
 [TOA measurement of all received data – for CT only],
 [SSR signals code content detection – for CT only],
 Time correlation and synchronization of all received data,
 MLAT data processing,
 System time synchronization with the UTC time,
 Output of the data processing results as target messages in ASTERIX to LAN,
 Control of the Transmitting subsystem,
 System diagnostic, monitoring and management,
 Communication with external environment.,
 Output of the system status as periodic status message in ASTERIX to LAN.
The Central Processing Station is housed in a COTS 19-inch indoor rack and the rack type is chosen to
allow easy extension. Moreover all critical parts of the CPS that ensure signal processing are fully
backed-up. The rack is powered through a two-stage power switch, which enables the station to be
disconnected from the main electricity supply and minimise the risk of electrical shock to engineering
personnel.
The exact configuration of the CPS depends on the requirements for respective project. The following
list shows typical CPS components:

MSS Description
 Target Processors/Management Server (TP/MS) – typically redundant,

 Communication Interface –network components, media converters, NTP servers, etc.,
 Power Distributor with optional UPS,
 Maintenance monitor and keyboard (KVM Switch),
 Internal cables of CPS,
 Mechanical and auxiliary units.
Figure 22 Schematic Block Diagram of CPS (Distributed time synchronization)
4.2.1. Target Processor [TP]
The target processor provides the following functionality:
 Collation of sensor data, data decoding, etc,

 Target position calculation – Multilateration processing,
 Target tracking,
 Generation of output target messages,
 Control of interrogators and transponders,
 Ground station diagnostic monitoring,
 Data recording.
The following sub-sections detail the target processor interfaces and data processing.
4.2.1.1. Target Processor Software

MSS Description
The Target Processor software is primarily represented by an operating system.
The TP 3rd party software ensures the hard disk back-up on DVD, file management and user GUI for
remote management.
The TP application software developed and produced by ERA ensures data processing functions
introduced in 4.2.1. The application software is based on a multi-process architecture with an internal
message bus. The software is realized by several independent processes that run concurrently.
The TCP/IP protocol set is used for the communication with other computers and components in the
local network. The system is tuned for 24/7 operation.
4.2.1.2. Target Processor Data Processing
The target processor undertakes various data processing tasks, such as data decoding, multilateration
calculations, target tracking, evaluation of operational statistics, etc.
The particular data processing depends upon the target application:
 ADS-B,
 Airport Surface Movement,
 Wide Area Multilateration.
Decoded data, such as target identification code and barometric altitude, are provided to a target
tracker, together with an estimated position, derived from the TOA timings from individual receivers. A
four stage Kalman filter is used is used for target tracking.
The first stage in estimating a target position is the determination of Time Differences of Arrival
(TDOA), from pairs of receivers. The target position is then estimated from the intersection of multiple
hyperbolas, as determined the constituent TDOA measurements.
4.2.1.3. Target Processor Interface
The target processor provides remote access, monitoring and management, through the following
applications:
 FTP server,
 Telnet server,
 SNMP agent,
 NTP Daemon.
The FTP server provides access for data transfer, which amongst other uses facilitates software
upgrade.
The Telnet server provides secure remote access, facilitating remote computer management via
command line arguments.
The SNMP agent provides access to diagnostic information via the SNMP protocol.
The NTP Daemon provides a NTP client service facilitating accurate time distribution.

MSS Description
4.2.2. Management System [MS]
The management system controls the entire NEO and provides the following functionality:
 Manages control requests from RCM Terminals,

 Evaluates the status of the Ground Station and presents the results to the RCM
Terminals,
 Manages user access,
 Evaluates long-term operational statistics and presents the results,
 Allows the co-operation and information exchange between the Active and Backup
Management Server,
 Alarms the user, e.g. by visual notification or e-mail,
 Allows customizations, e.g. by making notes and changing rules preferences,
 Stores alarm logs in a database for a period of time.
The comprehensive BITE functionality built into each intelligent module is monitored by the
management system.
4.2.2.1. Management System Software

The Management System software is primarily represented by an operating system. The Management
System is tuned for 24/7 operation.
There are two types of 3rd party software. The first group ensures the hard disk backup on a DVD and
file management whereas the second group ensures management functionality.
The Management System application software developed and produced by ERA ensures the following
functions:
 Continuous evaluation of the system diagnostic data,

 Storing and management of the system diagnostic data in MySQL database,
 Periodically generate system state reports via web pages, based on a content of the
MySQL diagnostic database,
 Distribution commands from the User Interface to relevant executive parts of the
NEO System.
The application software is based on a multi-process architecture with an internal message bus. The
software is realized by several independent processes that run concurrently.
4.2.2.2. Management System Interface
The Management System provides remote access, monitoring and management, through the same
applications as in the case of the Target Processor, 4.2.1:
 FTP server,
 Telnet server,
 SNMP agent,
 NTP Daemon.

MSS Description
4.2.3. Communication Interface
Depending on particular project requirements and system timing synchronization architecture used
(CT or DT) the various communication units and network components can be installed in CPS:
 Ethernet Switches or Routers,

 F/O Receivers,
 Media Converters,
 NTP servers, etc.
4.3. Remote Management Terminal
The RCMS functionality is ensured via

Remote Management Terminal (RMT) that
provides a human machine interface
between the NEO user and the NEO
Management System.
The RMT can be based on the desktop

workstation or on the mobile maintenance
notebook. It can be located on the same
LAN as the Management Server or can be
located on any remote network that is
interconnected with the Management Server LAN.
The Management Terminals provide the following principal functions:

 Display current system status
 Provide GUI for system control and parameter changes
 Provide GUI of the Failure Localisation Expert System
 Communicate with the Management Server
 Present Alarm Notifications (visual, acoustic)
 Allow Printing
The RMT software is represented by a COTS WEB browser, Mozilla Firefox, with additional plug-ins.
The WEB browser runs the PHP scripts on an Apache HTTP server on the Management Server via LAN
and HTTP and displays web pages that are generated by SVG graphics, based on content from the NEO
diagnostic, MySQL database. All NEO Management Systems are run by redundant systems.
Access to the Management Server is based on a user name and password. While modifications are
performed on one of the RMT, the other stations receive a notification. As soon as the modification is
finished, all other terminals receive a notification that reflects the changes performed.
Changes to the system are possible only from the active Management Server. The RMT do not have to
distinguish the active and backup Management Server, because their operation is transparent. The
requests are sent in a virtual direction that corresponds to the active Management Server.
The RMT the state and status information in diagrams that reflect the different levels of the NEO
architecture: global system, station, system, subsystem, equipment, unit, card, etc. The diagram at
each level contains all the managed objects of the level immediately bellow and their relation.

MSS Description
Whenever values are presented, they appear with the real value and are accompanied by its
tolerances (where applicable).
4.3.1. Engineering Display
The Engineering Display enables an on-line display of the NEO output data or replay NEO recorded
data (both raw data and output data). The Engineering Display functionality can be either installed on
RMT or can be provided as a separate COTS PC (desktop or laptop). The application software is based
on a multi-process architecture, i.e. the software is realised by several independent processes running
concurrently.
The application processes have the following function:
 DISPLAY
Situational display of the airport and TMA and related functions for displaying real-time target
data on the map background. Other functions are - the display of the table of tracked targets
and their parameters; and the possibility to print map windows and tables. The user can
select from a range of backgrounds and layers to be displayed on the screen, as shown on
Figure 23 below
Figure 23 Era Display Application
 REPLAY
Controls the replay of the recorded NEO output data that is stored on both TP and can be
downloaded on RCMT/Display HDD. The program can replay the data in real time or faster
(speed selectable in several steps). The Replay program can also filter the output data
according to message category numbers and target parameters.

MSS Description
Figure 24 Era Replay Application
4.4. NEO Redundant Concept
The reason for Hot Backup concept is to increase the NEO reliability. The impact of a Single Point of
Failure (SPF) is significantly addressed as a result of this approach.
This approach allows one or more subsystems to fail or be removed/repaired during operation without
data loss (i.e. hot swap concept). Owing to this concept, the maintenance and repair of the system
may be performed during operation.
4.4.1. Ground station redundancy
Typically the NEO system is designed with redundancy in the number of GS. Moreover the data link
connection between each GS and CPS can be dualled. This approach results in the fact that any of the
ground stations can fail without making the system performance degraded below required level.
4.4.2. CPS Redundancy
Typically all critical parts of the CPS that ensure signal processing are fully backed-up. All servers are
equipped with 2 independent power supplies and support hot swap concept, which enable exchange
of memory, HDD, fans, and power supply when running.
 Target processing SW is dual redundant, running on two separate servers and provides
independently data to the LAN as an independent sensor with its own LAN address.
 Management system runs also on dual redundant servers. Typically server 1 is active and server
2 is back-up. Data and system management can be provided either by server 1 or server 2.
 All servers are equipped with 2 independent power supplies.
 Redundant components inside HP servers (Power; RAM;HD - Raid 0+1 )
 All servers support the hot swap concept. This enables memory, HDD, fans, and power supply
exchange whilst running.

MSS Description
4.4.2.1. Target Processor Redundancy
Target Processors (TP) are dual redundant. Typically each Target Processor provides independently
data to LAN as an independent sensor with its own LAN address. Both Target Processors are working in
parallel way and produce the target reports (ASTERIX reports). The main advantage of this approach is
that in case of a failure of one Target Processor, the target reports are continuously produced without
any interruption by the other Target Processor. Thus no loss of data reported to the Air Traffic Control
Systems.
Alternatively the TP can be master and slave. The switchover is based on distributed data processing
and decides on the presence and quality of each TP. The switchover timeout is tuned based on the
data produced by the system and is typically around 2x period of the output data.
4.4.2.2. Management System Redundancy
There are two Servers in MSS where Management processes are running concurrently. One of them is
running in ‘Active’ mode the other one in ‘Backup’ mode. Both are evaluating diagnostic information
but only active one is writing the information into the database. When the status of active MS is
evaluated as not sufficient the backup MS becomes active and vice versa. This switchover is done
within less than one second. It can happen there is diagnostic information dropout for this second but
the impact for the whole diagnostic subsystem is not important.
4.4.2.3. Communication Interface Redundancy
The network components (switches, routers, etc.) can be dualled and NEO can also use multiple time
sources as time reference. This allows using all available combination of time sources: supplied NTP
servers and customer-provided NTP servers. The time sources are selected by the (S)NTP clients, based
on priority.
4.5. Environmental Conditions

4.5.1. Indoor Climatic Conditions
Climatic conditions for the system parts operating indoor, typically CPS:
Temperature range +10 °C to +35 °C
Humidity range 5 % to 95 %
Altitude range 0 m to 3000 m
4.5.2. Outdoor Climatic Conditions
Climatic conditions for the system parts operating outdoor:

Temperature range -40 °C to +60 °C (individual modules)
Humidity range 5% to 100%
Salinity resistance according to MIL-STD-810
up to 50 m/s (constant wind)
Wind resistance
up to 63 m/s (short wind gust)
Rainfall resistance up to 60 mm/h
Hail resistance up to diameter of 12 mm at wind up to 18 m/s
Icing up to 15 mm thick
Altitude range 0 m to 3000 m

MSS Description
Ground station cabinets are made of stainless steel, passivated and coated by polyurethane paint. All
metallic accessories is made of stainless steel.
Antennas are made of aluminum alloys with very good corrosion resistivity; radoms are made of
fiberglass (used in marine yachts). Assembly is treated with polyurethane paint.
Supporting structures (antenna brackets, beams, cantilevers etc.) are made either of aluminum alloys
with very good corrosion resistivity coated by polyurethane or of hot-dip galvanized (zinc) steel. Fixing
clamps and coupling material are made of stainless steel.
4.5.3. Storage Conditions
It is recommended to store the NEO system in dry and ventilated rooms at the temperature range
from –20 °C to +60 °C.
Under these conditions, the system may be stored for 2 years.
4.5.4. Transportability
The system has been designed as a stationary installation. After the installation on the site, no further
transport of the equipment is intended.
The equipment has been tested for resistance from shock and vibrations that may occur:
 during the transportation and manipulation with equipment at installation;
 after installation by wind, aircraft engines vibrations, etc.
The equipment is properly packed in transport cases for shipment to the place of installation. Packed
equipment can be transported by road, rail, or air. During transportation the equipment must be
placed in a dry space and protected from rain.
4.5.5. European Standards
The NEO complies with all current EU regulatory standards including:
2006/95/EC Electrical Equipment - Low Voltage Directive (LVD)
2004/108/EC Electromagnetic compatibility (EMC)
1999/5/EC Directive on radio equipment and telecommunications terminal equipment and the
mutual recognition of their conformity, 9 March 1999
552/2004/EC OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 10 March 2004 on the
interoperability of the European Air Traffic Management network
EN 60950-1 Safety for Equipment of Information Technology, 2006
EN 61000-6-2 Electromagnetic compatibility (EMC) - Part 6-2: Generic standards - Immunity for
industrial environments, 2006
EN 61000-6-4 Electromagnetic compatibility (EMC) - Part 6-4: Generic standards - Emission

standard for industrial environments, 2007.

MSS Description
EN55022, class B Information technology equipment - Radio disturbance characteristics - Limits and
methods of measurement
ETS 300 019-1-3 Environmental conditions and environmental tests for telecommunications
equipment - Part 1-3: Classification of environmental conditions - Stationary use at
weather protected locations, 1997
equipment - Part 2-3: Specification of environmental tests - Stationary use at
equipment - Part 1-4: Classification of environmental conditions - Stationary use at
non-weather protected locations, 1997
equipment - Part 2-4: Specification of environmental tests. Stationary use at non-

MSS Description
5. Management System
A detail description of all the Management System is a subject of the Era Management System User
Guide, see /B/. This section provides just a high level overview of the Management System.
5.1. Functions of the Management System
The Management System allows managing the local and remote subsystems of the system. It is a web-
based, user friendly, interface with separate area for both remote control and for monitoring
functions. The user will use the Management System on the Management Terminal configured with
appropriate tool set. The management functions are defined in three basic groups: Monitoring,
Control, and Maintenance:
 Monitoring: Functions concerning diagnostics and on-line monitoring of state, status and
parameters of the NEO.
 Control: Functions concerning modification of NEO parameters and control of NEO operation.
Access to these functions requires necessary permissions, implemented using user profiles.
 Maintenance: Functions concerning ensuring the functionality of the NEO and the
Management System.
The Management System consists of the Management Server, the Management Terminals (local and
remote), and the management functions of the managed subsystems realized by their Integrated
Control Units. The concept is based on unattended operation of the managed subsystems. The
architecture is flexible to allow multiple Management Terminals and it can be extended to include
other functions, like displaying the target data of the current air and ground situation.
Figure 25 Management System Concept
In order to allow manual interventions of the technical staff, the Management System is designed to
run in two modes: automatic operation and manual operation. The operation scenarios allow for two
regimes: local and remote regime. The local regime has higher priority over the remote regime, so that
critical operations can be performed without unwanted remote influence.

MSS Description
The main functions of the Management System are:
 Remote and local control of the main subsystems and parameters.

 Automatic reconfiguration of elements of the system in case of failure of the main
equipment and later reestablishment of the service after the solution of the problem.
This function includes, if it is necessary, a reconfiguration for a degraded operation of
the system.
 Continuous control of quality of the main elements and control of parameters.
 Transmission of the configuration of the system, the main parameters, and alarms to
the remote terminals.
 Management of the presentation and storage of the operative parameters of the
system.
 Management of the communications between the elements of the Management
System and the managed systems.
 Guidance of the maintenance engineer in the detection, localisation and correction of
failures down to the level of LRU.
 Centralised management of the NEO, including the analysis of results and the
prevention of failures.
The data flow in Management System is depicted on the following figure:
Figure 26 Management System data flow
5.1.1. Monitoring Functions
Functions concerning diagnostics and on-line monitoring of state, status and parameters of the NEO
represent the monitoring functions of the Management System.
The monitoring messages are divided into the following categories:

MSS Description
 STATUS (STAT) - State and Status Messages. They inform about state and status of the
monitored subsystem.
 CHANGE (CHNG) - State and Status Change Alarms. They inform about the state and
status changes of the monitored subsystem.
 DEGRADED (DEGR) - Degraded Function Alarms. They inform about failures that do
not affect the function of the system or the system parameters, but lower the system
redundancy.
 ERROR (ERR) - Failure Alarms. They inform about failures that affect critical functions
of the system.
5.1.1.1. Alarms
The Management Server analyzes the information received from the various Integrated Control Units
in the state and status messages and alarms. The purpose of this analysis is to relate the information
coming from the different Integrated Control Unit to obtain the global system monitoring information.
The analysis takes into account the hierarchy of alarms:
1. ERROR (the highest)

2. DEGRADED
3. WARNING
4. REPORT (the lowest)
The implications of the combination of alarms of different hierarchy are considered. Additionally, the
integrity of the monitoring messages is checked on all communication channels, including the number
of messages in each communication channel.
Alarm management and changes of operative state both precede state information changes. They are
triggered automatically and can be either confirmed by the maintenance engineer or by an automatic
procedure, like a timeout.
The Management Terminal presents to the user the alarm information in the following way:
 Acoustic alarm that can be disabled by the user once accepted.

 Error message to the tail of alarm list that can be displayed at any moment.
 A window that describes the failure.
 Possibility of printing the error message or the list of messages.
The presentation of the alarms is based on the defined hierarchy; an alarm can not alter the
presentation of the alarm of higher priority; in case of equal priority the alarms appear ordered by
date and time. The elimination of the alarms can be made manually by the maintenance engineer or
after a specified period of time.
5.1.2. Control Functions
The Manager Server is in charge to receive, to decode, to interpret the control messages, and to
control the Integrated Control Units. The control interface to the maintenance engineer is presented
by Maintenance Terminal.
The control functions include:
 Restart of an ICU
 Restart of ICU software

MSS Description
 Switching ON/OFF of several functions of the system (depends on system

configuration)
5.1.3. Maintenance Functions
Maintenance functions cover functions necessary for correct operation of the Management System
and functions increasing the information value of the data provided. They include the following:
 Management of the users

 Management of the user rights
 Management of user notes
 Management of alarms
 Management of the database
 Management of the on-line user guides
 Updates of the configuration databases of the Management System
5.2. NEO Modes
NEO has the following modes which are controlled from the Management Server.
5.2.1. Operational Mode
When in Operational Mode the NEO system marks ASTERIX data as GO bit in the system output.
Normal users cannot modify parameters that are operationally significant in this mode.
5.2.2. Maintenance Mode/Test Mode
All functions available in Operational Mode are also available in Maintenance Mode.
The system can be configured by an administrator through user-friendly HMI interface whether or not
to send any output data in maintenance mode.
Any output data sent in Maintenance Mode is marked with the NOGO bit in the ASTERIX output.
An authorised user can modify system parameters in Maintenance Mode.
If a redundant component is put into maintenance mode it has no impact on the operational
unit/system.
5.3. Data Recording
The NEO system automatically record both raw data from all ground stations and ASTERIX output data
on the Target Processor. The Management Servers record the diagnostic logs.
The recorded binary format files (raw data) are called primary data records. Primary data records are
an important source of information for NEO system program to analyze the performance of target
processing software or overall system performance. The size of the primary data record is very large so
the maximum period for which the data is stored depends on available disk space.
The output data are recorded to the files that are named accordingly to the recording date and hour
(e.g 200905052200.ast) and typically the new file is created each hour. Thus the file names are

MSS Description
automatically sequenced. The amount of storage space required for output records are very modest.
Based on experiences from other NEO sites, the Asterix data files should not take up more than 60MB
per day per output stream.
Detailed description of the Management system is given in the “Era Management System User Guide”
document, see /B/.

MSS Description
6. System Interfaces
6.1. External Interface
An NEO receives off-air signals from aircraft and vehicles and from these signals derives identity and
position. The resultant data is then communicated to Air Traffic Control (ATC) systems, using defined
ASTERIX protocols.
The system also receives timing data from either a Global Navigation Satellite System (GNSS) or a local
time server.
The system also provides diagnostic data.
All of the possible external interfaces are shown in Figure 27.

SSR
SSR SSR
Reference
Replies Interrogations
replies
(1090 MHz) (1030 MHz) GNSS
(1090 MHz)
MSS
Time Diagnostics
(NTP) ASTERIX (SNMP)
Data
Figure 27 NEO Interfaces
The external interfaces can be conveniently split into one of four types:
o Input Signals
 SSR transponder signals (1090 MHz)

 GNSS signals
 Server Time
o Output Signals
 SSR interrogation 1030 MHz

 SSR Reference replies 1090 MHz
o ATC Interface
o Control & Diagnostics

MSS Description
6.1.1. Input Signals
The principal input signals are Mode A, C and S SSR signals from aircraft and vehicles. The NEO decodes
these signals, and timestamps the leading edge of the pulse stream.
The other input to a NEO is GNSS signal and server time. This can be derived from internal time server
(from GNSS transmission) or from an external time server.
6.1.2. Output Signals
An NEO may output both SSR interrogations and transponder replies.
In an active NEO targets can be interrogated by the system.
In addition, an NEO may contain one or more SSR transponders which can be used for system
validation.
6.1.3. Time Synchronization
NEO can use multiple time sources as time reference. This allows using all available combination of
time sources: supplied NTP servers and customer-provided NTP servers. The time sources are selected
by the (S)NTP clients, based on priority.
Time synchronization messages are transmitted using the NTP protocol according to RFC 1361 and RFC
2030.
6.1.4. ATC Interface
The NEO can communicate with various ATC systems, including Multi-sensor Data Fusion systems and
centralised Control and Monitoring Systems.
Communication with these systems is based on standard ASTERIX protocols.
The ASTERIX output messages are transferred via the LAN in the network, using either TCP or UDP
protocols. Multicast, broadcast or unicast IP addressing can be used.
The Era NEO allows minimally 8 independent output channels to be configured, with the flexibility for
ASTERIX data to be configured independently for each output channel.
A typical NEO outputs messages on two data channels: Operational and Non-operational. The
Operational port contains data output from the active Target Processor while the Non-operational port
contains data of the Target Processor in its backup state. The channels can be distinguished by
destination IP address, TCP or UDP port number and SAC/SIC, etc.
Typically the following ASTERIX versions are used:
ADS-B
 ASTERIX Cat 021, [16]

Airport Surface Movement

MSS Description

Wide Area Multilateration

The various ASTERIX documents describe messages which are constructed from various data items,
some of which are mandatory and others which are optional. Optional data items may not be
supported as standard.
Optionally Era can provide other ASTERIX categories and versions if required. For example under
ASTERIX Categories (e.g. CAT 010 [12], CAT 034 [18] and CAT 048 [19]).
6.1.4.1. Data Output Modes for WAM application
The NEO system can output the data using one of the following methods:
 Data driven mode

A target report is output for a target when valid data is received. A configurable
timeout is used to prevent too many updates being generated for a given target.
 Periodic mode – predicted

A target report is output for a target at the end of the configured output interval. The
target position is extrapolated to its predicted position at the output time. There is a
configurable timeout on how long the extrapolation is maintained.
6.1.5. Control & Diagnostics
Control and diagnostic information transfer is implemented using the Simple Network Management
Protocol (SNMP), see document [20].
SNMP is a standard of the Internet Protocol Suite, commonly known as TCP/IP, after the first
implementation.
The basic elements of SNMP are shown in Figure 28, below.
Figure 28 SNMP Architecture
The NEO central server is a Network Element, on which will run a software module known as an agent.
One or more Network Management Stations (NMS) can monitor and control one or more Network
Elements.

MSS Description
This flexible architecture means that not only can a single central server be monitored and controlled
from multiple locations, e.g. customer and supplier, but that more than one central server, Network
Element, can be monitored from a single location.
SNMP provides a range of standard data types, which can be used to implement application specific
data messages.

MSS Description
7. Maintenance
In common with all electrical systems an NEO requires routine maintenance in order to ensure that the
system is consistently performing at optimal levels. The Era NEO, however, is designed to perform
optimally with only a minimal and unobtrusive maintenance schedule. The maintenance plan is site
specific and comprehensive.
Typically, the maintenance tasks are often divided between the customer and the manufacturer.
During the warranty period, the manufacturer often performs all maintenance with regard to the
software and data adaptation files. This can be undertaken remotely, ensuring no customer
disturbance. All changes will be directly reported to the customer using Informational Bulletins.
7.1. Maintenance Schedule
A typical maintenance schedule is divided into three categories:
o RM
o M1
o M2
These categories are explained in detail below.
It must be noted, however, that this does not include the maintenance of equipment that is in
constant use, such as keyboards, mice, display screens, etc., and that their maintenance should be
performed on an as needed basis.
Maintenance Category To be performed Duration time per station2
RM Daily NA (CMS supervision)
M1 Every 6-12 months 0,5h3
M2 Every 12-18 months 1h3
Table 12 Maintenance Time Schedule
The example maintenance plan is only provided as an illustration and each plan will be tailored to suite
the environmental needs of the specific site. In many cases, the ground stations will only need to be
checked once every year.
2
This time period does not include the time for transport on the site
3
This time period does not include the time for the UPS check. The UPS check shall be performed according to
the manufacturer’s instructions.

MSS Description
7.1.1. RM Maintenance
No. Activity Note
Checking the function of the system using the
1
Management System program.
It shall be carried out as
Current examination of CPS, RCM terminal and
necessary and in
2 MNB, and removing dust and other
accordance with local
contaminants from their surface, if needed.
conditions.
Table 13 RM Maintenance
7.1.2. M1 Maintenance
The M1 maintenance plan is targeted at locations which experience extended periods of sub-zero
temperatures. M1 maintenance is not applicable for tropical and subtropical climates, as defined by
category A under STANAG2895. In many cases, M1 is only an extension of M2 and is performed on an
annual basis.
M1 maintenance is performed at the central server, see Table 14, and ground stations, see Table 15.
M1 maintenance should only be undertaken by specially trained personnel. On the days when M1
Maintenance takes place, RM maintenance does not need to occur, as the RM actions are included in
the M1 Maintenance.
No. Activity
CPS
Check the logs with the long term statistic information about the
1
system alarms at Management System log archives.
Check the status of communication among the system parts of NEO at
2
Management System.
Table 14 M1 maintenance Central Server
No. Activity
Visual inspection of the remote site
1
Antenna system and electronical units for impurities, freeze up, etc.
2 Record into the Operation Records Book.
Table 15 M1 maintenance Ground Station
7.1.3. M2 Maintenance
The M2 maintenance plan is undertaken annually, and includes an inspection of the entire NEO
system.
The extent of the interruption to the NEO system depends on both the inter site transport facilities
and the number of personnel performing the maintenance.

MSS Description
No. Activity
1 Inspection of the fans at the NEO computers.
2 Perform the backup of the system partition of all NEO computers.
3 Perform the backup of the adaptation data of all NEO computers.
Table 16 M2 maintenance Central Server
No. Activity
1 Perform the M1 steps for all remote stations.
2 Record into the Operation Records Book.
Table 17 M2 maintenance Ground Station
Details of procedures are described in Technical documentation that is prepared and provided for each
individual delivery.
7.2. Replacement of accumulators and computers
Aside from the maintenance plan above, there are certain other maintenance tasks that must take
place (preventive replacement of accumulators) or tasks that are recommended (replacement of
computers) to ensure longevity of the system.
7.2.1. Preventive replacement of accumulators
Battery module comprises long life batteries of Genesis suitable to harsh environment and
temperature, the life expextancy is 15 years (at 20°C). It is recommended to check them within the M1
maintenance and replace them earlier if the result of the check is negative.
7.2.2. Recommended replacement of computers
With the current rate of computers development, it is estimated that approximately 5 years after an
instillation, utilised computers will become “obsolete”. Spare parts will become more expensive and in
some cases will become nearly impossible to locate. Thus, the customer may come to the conclusion
that the current computers should be replaced with new computers. It is recommended to order such
replacements with the system manufacturer. He/she can guarantee maintaining, and in some cases
even enhancing, the system specifications.
7.3. Corrective Maintenance
The modular concept of NEO ensures easy corrective maintenance and change of faulty modules
(LRUs). The system is typically delivered with initial set of spare parts.
The maintenance procedures (up to 2nd line) that can be performed by trained technical personnel are
described in operational and technical documentation that is part of delivery. Repairing of faulty LRUs
is performed by ERA or by delegated service organization.

MSS Description
8. Reliability and Availability

Era has been building high reliability systems for ATC and military customers since 1995. The methods
described here have been developed, refined and validated based on industry best practise and
decades of experience fielding specialist surveillance equipment.
8.1. Reliability factors Background
8.1.1. Reliability
Reliability is generally defined (e.g. IEC60050-191, [22]) as the probability of a system or a product
being able to perform in a satisfactory manner for a period of time when used under specified
operating conditions.
The definition of reliability requires a number of concepts to be addressed, in particular the functions
of the system in question, the system performance required to support the operation and definitions
of failure, in particular what loss of function or degradation in performance will constitute a system
failure.
It is also important to ensure that the equipment is adequately designed for the environmental
conditions in which an item is used and stored, together with the way it is operated and maintained, as
these conditions will have a major impact on its reliability.
For the majority of electronic equipments during their useful life (i.e. following early life failures or
“burn-in” and prior to wear out failures) a background of “random” failures occur, which is generally
described as exhibiting a constant failure rate. The failure rate for a system is the total number of
failures preventing the system from achieving its defined functions at the required performance during
a given time interval, divided by that time interval. It is often expressed as failures per million hours
(fpmh) and represented as the symbol lambda (λ).
As a measure of equipment reliability, the concept of Mean Time Between Failure (MTBF) is also often
applied. This is defined as the average time between failures within the equipment or unit under
consideration. For the conditions described above, this is equivalent to 1/ λ.
Given an underlying random failure model, the reliability over time (t) has been shown to follow the
traditional exponential distribution, as follows:
Where: λ = failure rate

M = MTBF
t = defined time interval
8.1.2. Maintainability
Maintainability of an item is generally defined (e.g. IEC 60050-191, [22]) as the ability for the item to
be retained in, or restored, to a state in which it can perform as required, under given conditions of
use and maintenance strategy.
This definition covers both “preventive” maintenance (retaining in its functioning state) and
“corrective” maintenance (restoring the item to a functioning state). Once again, the functions and

MSS Description
performance of the system must be considered in determining what constitutes a system failure,
which would lead to corrective maintenance.
It is important that the system, and equipment, is adequately designed to facilitate maintenance or
repair as necessary to support its operational usage. The maintenance and sparing strategy for the
equipment was established during system design, and has been based on having extensive Built in Test
Equipment (BITE), and a modular design, with common field replaceable units.
Operational factors, or logistic delays, such as waiting time for spares or maintainers, time to travel to
the equipment location and the level of training of individual maintainers are beyond the control of
the designer. For this reason, the maintainability is generally defined in terms of “active” repair times.
These are the times it should take a trained maintainer, with appropriate manuals, adequate spares
and test equipment to:
 Locate a failure (detect and diagnose);
 Repair it (component, module replacement, etc); and
 Restore the item to a fully functioning state.
The common term used to describe this property of system modules or units is “Mean Time To Repair”
(MTTR).
Given the above caveat about the use of active repair times, where it is necessary to evaluate the
overall reliability or availability of a complex system involving active redundancy, estimates of logistic
delays need to be included. In this situation, a common term used to describe this property of system
modules or units is “Mean Down Time” (MDT).
8.1.3. Availability
Availability of an item is generally defined (e.g. IEC 60050-191, [22]) as the ability to be in a state to
perform as required, under given conditions, at any given instant, or over a given time interval.
In its simplest form, for an item which is operating continuously, Availability (A) can be calculated as:
Uptime
A
Uptime  Downtime
Where Downtime can be made up of preventative maintenance, active repair, awaiting repair (logistic
delay) and other downtime arising from external factors.
As indicated above, the system designer is not directly able to control a number of these contributors
to system downtime, hence it is more usual to define Intrinsic Availability which includes only the
downtime under the control of the designer. In this situation Intrinsic Availability (Ai) may be
calculated as:
MTBF
Ai 
MTBF  MTTR
Where the MTBF and MTTR figures relate to the system and take account of design, in particular the
inclusion of redundant components or equipments.

MSS Description
8.2. System RMA Calculation
Evaluation of Reliability, Maintainability and Availability (RMA) of complex systems is not

straightforward, especially where the system is designed for reliability and hence contains redundant
components or modules. A commonly used technique used to represent such systems is to establish a
model known as a Reliability Block Diagram (RBD), which comprises blocks of known RMA
characteristics which are linked in series (where the overall function is dependant on the operation of
each series block) or in parallel (where the overall function is dependant on the operation of one of
more of the parallel, redundant, blocks).
An example of a simple RBD is shown in the Figure below, where blocks A and B are in series with the
parallel redundant (1 out of 2) blocks C and D. In order for the ‘system’ to operate block C OR D must
be working along with blocks A and B.
A B 1/2
The calculation of system RMA characteristics will often require use of computer modelling
techniques, such as Monte-Carlo simulation, however it is possible to provide a mathematical solution
based upon certain simplifying assumptions.
The following mathematical solutions have been employed to calculate the proposed system RMA
characteristics. These were originally based upon UK and NATO Defence Standards (DEF-STAN 00-41
and ARMP-2), as now described in GR-77 (Part D, Chapter 6).
Key assumptions made are:

 The system is in a steady operating state, with active redundancy
 Repairs are always initiated, without queuing, upon a failure
 Failure and repair times are constant, i.e. do not vary with time
Redundant blocks are equal, i.e. have the same failure and repair characteristics.
8.2.1. Reliability
The Mean Time Between Failure (ms) for a series of N unequal blocks in the Reliability Block Diagram is
given by:

MSS Description
1
ms  N
λ
i 1
i
Where i is the item number

1
i 
MTBF i
The Mean Time Between Failure (ms) for N parallel equal blocks, of which M have to be operating to
provide the overall function, is given by:
AS m  N! 
mS   N CM  
M N CM AM Q N  M   N  M !.M ! 
Where As is determined using the general M out of N with equal Block Reliability equation, but
substituting As and A for the Rs and R, as follows:
N M
AS   Ci A N i  1  A n!
i
N given Ci 
(n  1)!.i!
n
0
and m = MTBF of each block

A = Availability of each block
Q = Unavailability (= 1 - A)
It should be noted in this case that As is the System Availability, and hence block availability (A) must
include logistic delays, i.e. the Mean Down Time for the individual block.
8.2.2. Maintainability
A general expression for the calculation of the Mean Time To Repair (rs) is given by:
m S 1  A S 
rS 
AS
For a series of N unequal blocks in the Reliability Block Diagram, the parameters As and ms in the
general expression are given by (using previous reliability equations):
1
N
ms 
AS  Π Ai N
i 1 and λ
i 1
i
For N parallel equal blocks, of which M have to be operating to provide the overall function, the
parameters As and ms in the general expression are given by the previous stated reliability equations,
substituting As and A for Rs and R:

MSS Description
N M
Ci A N i  1  A
AS m
AS   0
N
i
and mS 
M N C M A M Q NM
For N parallel non-equal blocks, of which k have to be operating to provide the overall function, the
following formula can be used:
Where
n = number of components in the system
k = minimum number of components that must work for the k-out-of-n system to work
pi = reliability of component i,i = 1, 2, . . . , n
8.2.2.1. Common Mode/Common Cause Failures
The calculation of reliability given above assumes the blocks involved are independent and hence
random hardware failures are not inter-connected. In practice, some failures (i.e. common mode or
common cause) will affect multiple blocks. These may result from a systematic fault or an external
influence and have the potential to cause a dependant failure of redundant modules or components.
Since such failures affect multiple items, the probability of common cause or common mode failure
will often dominate the overall reliability of equipment, in particular where the items are located in a
single, common physical location and subject to common maintenance.
IEC 61508, Part 6, Annex D, [23] provides “A methodology for quantifying the effect of hardware-
related common cause failures in E/E/PE systems”. The methodology provides a means to calculate a
value for a β-factor, as frequently used in the modelling of common cause failures. This is used to
estimate the rate of common cause failures applicable to two or more systems operating in parallel
resulting from the random hardware failure rate of one of those systems.
The standard provides Tables (D.1 to D.4) with a checklist of questions which are used to provide an
estimate of a β-factor. For the Era NEO, the checklist elements for a ‘Logic Subsystem’ have been
applied where appropriate, in order to establish a β-factor.
8.2.3. Initial Spare Holding - Probability of Nil Stock Out
Based upon modules MTBF and maintenance policy, it is possible to determine the likelihood of a
stock-out for any given spare, based upon the following equations.
The Probability of having particular item in stock can be calculated as follows:

MSS Description
Where P = probability of having a spare of a particular item available when required

S = number of spare parts carried in stock
R = composite reliability (probability of survival) defined as
and K = quantity of parts used of a particular type

λ = failure rate (1/MTBF)
t = time when spare part required available
In order to estimate the recommended spares holding, it is necessary to define the time at risk (t),
which will depend on the selected maintenance policy. For example, where failed modules are
returned to the manufacturer, the time at risk will be equivalent to the restocking time, which is likely
to be of the order of 4 to 6 weeks.
In consideration of sparing to cover a return to manufacturer maintenance strategy, the stock-out risk
will be the choice of the customer, but would be anticipated to be of the order of 95% to 99% for any
individual item, based upon the calculated failure rates. However, applying a similarly high confidence
level for deriving a recommended spares inventory for a ‘life-time’ buy has, in ERA’s experience,
generated excessively high numbers of spared items compared to practical usage.
This is believed to be due to a combination of factors, for example the fact that not all replaced items
are in practice thrown away. Even if only a small number of these are ultimately repairable (e.g. 20-
30%) this significantly reduces the required spares holding. In addition, the long term reliability of NEO
modules, provided the equipment is well looked after and left undisturbed apart from necessary
maintenance, has been found to improve with time (compared to the initial failure rates) until
component wear out mechanisms start to dominate (e.g. corrosion, material breakdown, fatigue, etc)
which generally occur beyond the useful life of the equipment.
Based on these factors, it is recommended that ‘life-time’ sparing based on a stock-out of the order of
60% provides a reasonable and practical level of sparing for any individual item. However, the level of
confidence applied, and period of time to be covered by such calculations will ultimately be dependant
on any individual customer expectations and specific requirements.

MSS Description
9. Reference Documents
[1]. ED-117, Minimum Operational Performance Specification for Mode S
Multilateration Systems for use in Advanced Surface Movement Guidance and
Control Systems (A-SMGCS), EUROCAE, November 2003.
[2]. ED-126, Safety, Performance and Interoperability Requirements Document for ADS-
B – NRA Application, EUROCAE, December 2006
[3]. ED-129, Technical Specification for a 1090 MHz Extended Squitter ADS-B Ground
Station, EUROCAE, June 2010
[4]. ED-142, Technical Specification for a Wide Area Multilateration (WAM) System,
EUROCAE, September 2010
[5]. EUROCONTROL Standard Document for Radar Surveillance in En-Route Airspace and
Major Terminal Areas, SUR.ET1.ST01.1000-STD-01-01, Edition 1.0, March 1997.
[6]. ICAO Annex 10, Volume IV (Surveillance Radar and Collision Avoidance Systems),
Second Edition of Volume IV – April 2003.
[7]. Manual on Mode S specific services ICAO DCO 9688-AN/952
[8]. RTCA DO-242A, Minimum Aviation System Performance Standards for Automatic
Dependent Surveillance Broadcast (ADS-B), RTCA, Issued 6-25-02, Prepared by SC-
189, Supersedes DO-242
[9]. RTCA DO-260/EUROCAE ED-102 Minimum Operational Performance Standards for

1090 MHz Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic
Information Service (TIS-B)
[10]. DO- 286 Minimum Aviation System Performance Standards (MASPS) for Traffic
Information Service - Broadcast (TIS-B), RTCA, Issued 4-10-03, Prepared by SC-186
[11]. RTCA DO-260A Minimum Operational Performance Standards for 1090 MHz
Automatic Dependent Surveillance – Broadcast (ADS-B) and Traffic Information
Services (TISB), RTCA, Issued 4-10-03, Prepared by SC-186, Supersedes DO-260
[12]. EUROCONTROL Standard Document for Surveillance Data Exchange, Part 7:

Category 010, Transmission of Monosensor Surface Movement Data,
SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.
Category 019, Multilateration System Status Messages, SUR.ET1.ST05.2000-STD-18-
02
[14]. EUROCONTROL Standard Document for Surveillance Data Exchange, Part 14

Category 020, Multilateration Target Reports, SUR.ET1.ST05.2000-STD-14-02,
Category 020, Multilateration Target Reports, SUR.ET1.ST05.2000-STD-14-02

MSS Description
Category 021, ADS-B Reports, SUR.ET1.ST05.2000-STD-12-01
Category 23, CNS/ATM Ground Station Service Messages, SUR.ET1.ST05.2000-STD-
16-01
[18]. EUROCONTROL Standard Document for Surveillance Data Exchange. Part 2b:
Category 034, Transmission of Monoradar Service Messages. Edition 1.27, May 2007
[19]. EUROCONTROL Standard Document for Surveillance Data Exchange. Part 4:

Category 048, Transmission of Monoradar Target Reports. Edition 1.15, April 2007
[20]. A Simple Network Management Protocol (SNMP), RFC 1157, Network Working
Group, May 1990.
[21]. Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI, RFC 2030,
Network Working Group, October 1996.
[22]. IEC 60050-191 ed1.0, International Electrotechnical Vocabulary. Chapter 191:

Dependability and quality of service, 1990
[23]. IEC 61508-6, 1st edition 2000-2004, Functional safety of electrical/electronic/

programmable electronic safety-related systems

MSS Description
10. ERA’s Reference Documents

/A/. NEO Components Catalogue or Data Sheets
/B/. ERA Management System User Guide
/C/. Preliminary Design Document

MSS Description
11. Glossary
11.1. List of Acronyms
ACAS Airborne Collision Avoidance System

ADS-B Automatic Dependent Surveillance - Broadcast
ADS-X Automatic Dependent Surveillance - Extended
A-SMGCS Advanced Surface Movement Guidance and Control System
ASTERIX All purpose STructured EuRocontrol surveillance Information eXchange
ATC Air Traffic Control
ATCRBS Air Traffic Control Radar Beacon System
ATM Air Traffic Management
ATSU Air Traffic Service Unit
BITE Built-in-Test
BVIM Block of Video signal Inputs
CAA Civil Aviation Authority
CEP Circular Error Probability
CMS Control Monitoring System
COTS Commercial off the Shelf
CPR Compact Position Reporting
CPS Central Processing Station
CRC Cyclic Redundancy Check
CT Central Time
CTR Control Zone
DF Downlink Format
DME/N Distance Measuring Equipment/Narrow Spectrum
DOP Dilution of Precision
DT Distributed Time
EUROCAE Th EURopean Organisation for Civil Aviation Equipment
FAA Federal Aviation Authority
FTP File Transfer Protocol
GND Ground
GNSS Global Navigation Satellite System
GPS Global Positioning System
GS Ground Station
GUI Graphic User Interface
HDD Hard disk

MSS Description
HDOP Horizontal Dilution of Precision

HME Height Measurement Equipment
HMU Height Monitoring Unit
HTTP Hypertext Transfer Protocol
ICAO International Civil Aviation Organisation
IP Internet Protocol
KVM Keyboard, Video, Mouse
LAN Local Area Network
LCD Liquid Crystal Display
LRU Line-replaceable unit
MLAT Multilateration
MNB Maintenance Notebook
MSS Multi-sensor Surveillance System
MSSR Monopulse Secondary Surveillance Radar
MTBF Mean Time Between Failure
MTTR Mean Time to Repair
MySQL My Structured Query Language
N.A. Non Applicable
NMS Network Management Stations
NTP Network Time Protocol
PCD Probability of Code Detection
PD Probability of Detection
PDOP Position Dilution of Precision
PHP Hypertext Preprocessor
PRM Precision Runway Monitoring
RCMS Remote Control and Monitoring System
RMS Root Mean Square
RMTR Reference and Monitoring Transponder
RTCA Radio Technical Commission for Aeronautics
RVSM Reduced Vertical Separation Minima
RXS Receiving Unit
RXTXS Receiving/Transmitting Unit
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SSR Secondary Surveillance Radar
TCP/IP Transmission Control Protocol/Internet Protocol

MSS Description
TDOA Time Difference Of Arrival

TIS-B Traffic Information Services – Broadcast
TMA Terminal Area
TOA Time of Arrival
TP Target Processor
TTL Transistor-Transistor Logic
TXS Transmitting Unit
UDP User Datagram Protocol
UFE Unified Format ERA
UPS Uninterruptible Power Supply
UTC Coordinated Universal Time
UTP Unshielded Twisted Pair
VDOP Vertical Dilution of Precision
WAM Wide Area Multilateration
WGS World Geodetic System

MSS Description
Appendix A Multilateration Theory

A.1. Principle of Position Detection - Time Difference of Arrival (TDOA)
The NEO by ERA utilizes Multilateration in order to estimate aircraft and vehicle position.
Multilateration, or hyperbolic positioning, is the process of locating a target based on the Time
Difference Of Arrival (TDOA) of a signal emitted from a target to spatially separated sensors.
When a signal is transmitted from a target, it is received by two spatially separated receiver sites at
slightly different times. This slight time difference of signal detection is given by the distance between
the target and each sensor and creates “time difference of arrival – TDOA“, see Figure 29. For a pair of
receivers with known positions these set of measured distances defines hyperbola (in 2D) or
hyperboloid (in 3D) on which target is located.
The TDOA for a pair of receivers is shown in Figure 29. In this case the distance “d1” from the aircraft to
Rx1 is greater than the distance “d2” to Rx2. The TDOA is the difference between signal time of arrival
at these two receivers (TOARx1 and TOARx2).
d2
d1
Comm. Tower
Rx 2
TDOA1-2
d2
d1
Comm. Tower
Rx 1
T0 TOARx2 TOARx1
Figure 29 Formation of Time Difference of Arrival
A hyperbola for the TDOA resulting from the differences in distance from sensors Rx1 and Rx 2 is
shown in Figure 30.

MSS Description
Figure 30 2-D Cut of a Single hyperbola
A second TDOA measurement from another pair of sensors provides a second hyperbola. The
intersection of these two hyperbolas describes a curve on which the target lies.
Figure 31 2-D Cut of a intersection of two hyperbolas
A third TDOA measurement from another pair of sensors provides a third hyperbola. The intersection
of the resulting third hyperbola with the curve already found with the other three receivers defines a
unique point in airspace (real 3D position of the target). The target's location is therefore fully
determined in 3D.
In reality (3D space), there are 3-dimensional objects (hyperboloids) instead of hyperbolas. The
target’s position is at the intersection point of the hyperboloids.
An example of three intersecting hyperboloids is shown in Figure 32.

MSS Description
Figure 32 An Example of the Intersection of Three Hyperboloids
A.2. MLAT Position Accuracy and Dilution of Precision (DOP)
The global and local accuracy properties of the NEO are basically defined by its geometrical
configuration (actual deployment of the receiving station at the current region). The quality (error
dispersion) of the TDOA measurements play very important role for estimation of the actual specific
values of NEO accuracy, but global figure of the accuracy distribution and its mutual local relations are
given only by geometrical configuration of the NEO.
The variation in estimated position accuracy with target position relative to the geometry of the
sensors is known as Position Dilution of Precision (PDOP). It is defined as:
PDOP(x,y,z) = √(σx2 + σy2 + σz2) / (c * σTDOA), [ 1 = m / (m/ns * ns)]
where
σx2, σy2, σz2 is error dispersion of target coordinates x, y and z)
σTDOA is the standard deviation of the time measurement at receivers
c is velocity of signal propagation
Similarly it can be introduced Horizontal Dilution of Precision (HDOP) for horizontal plane or Vertical
Dilution of Precision (VDOP) for vertical plane.
HDOP(x,y,z) = √(σx2 + σy2) / (c * σTDOA), [ 1 = m / (m/ns * ns)]
VDOP(x,y,z) = σz / (c * σTDOA), [ 1 = m / (m/ns * ns)]
From the above definitions it is clear that influence of the primary TDOA measurements are eliminated
by dividing term c * σTDOA, therefore VDOP, HDOP and PDOP depend only on geometry configuration
of the NEO.
The following figures illustratively depict the horizontal error in Cartesian space and its dependence on
the mutual target position and NEO configuration. The key role in this case plays the angle between

MSS Description
normals of the hyperboloids at current point of target position. This angle directly determines the
shape of the error body and its value corresponds (linearly) to the error dispersion σTDOA of the TDOA
measurements.
Intersection of 2 hyperbolas (good HDOP) Intersection of 2 hyperbolas (good HDOP) - detail
Intersection of 2 hyperbolas (bad HDOP) Intersection of 2 hyperbolas (bad HDOP) - detail
Figure 33 HDOP
Generally, the good HDOP is within the polygon defined by the ground stations deployment and poor
outside of this area. This is presented in following figures where each pair of coloured lines represents
the hyperbolas for a pair of sensors. The separation between the lines indicates the measurement
error and hence the uncertainty in position. The intersection of the hyperbolas is highlighted in the
zoomed in view.
The first figure represents target located within the deployment. The hyperboloids cross each other in
a small area and hence the area between the hyperboloids is small which indicates high accuracy.

MSS Description
Figure 34 2-D Plot for a Simulation of Multilateration with Four Sensors – Target within Sensor Area
The second figure shows hyperbolas for a target outside of a polygon defined by the four sensors is
presented in Figure 35. In this case the hyperboloids cross each other over an extended area.
Therefore, the area over which the target is located much less well defined.
Figure 35 2-D Plot for a Simulation of Multilateration with Four Sensors – Target outside Sensor Area
A.3. Multi-ranging
Multi-ranging is an advanced technique that Era uses in NEO to improve the positional accuracy and
integrity of target position calculations. It can also increase the redundancy of the solution or reduce
the number of stations required to achieve the same result.
The basic Multilateration technique uses time differences between the times of a signal’s reception at
remote ground stations to calculate hyperboloids in space. A hyperboloid is generated for each pair of
ground stations which receive the signal and the intersection of three or more hyperboloids (from 4 or
more ground stations) provides the target position, see Appendix A.2.

MSS Description
In addition to this standard technique, Era accurately times the interrogation from an active ground
station (interrogaters). By correlating the time of interrogation to the time of arrival of the replies
received at multiple ground stations the round trip time to and from the target is established. For each
interrogator/receiver pair an ellipsoid is described, which estimates the target position. The
interrogator and receiver form the foci of the ellipsoid. Because the reply to a single interrogation is
received at multiple sites, multiple ellipsoids are generated for each interrogation. This is called multi-
ranging and is shown in Figure 36, in 2-D for simplicity.
MH z
1030
Repl
tion
roga
Inter
y 109
0 MH
z
Synchronization by DF18 1090 MHz
F1 º TX F2 º RX
F1,2  focal poins of ellipse
Figure 36 Construction of Ellipsoids
With two receivers the target position will be at the intersection of the ellipsoids.
Multi-ranging is complementary to Multilateration. The greatest benefit is derived when the two are
used in combination. Multilateration provides high accuracy when the target is located within the area
bounded by the sensors, see Appendix A.2.
A 2-D plot from a simulation combining Multilateration and Multi-ranging is shown in Figure 37. As
described in Appendix A.2 the location accuracy for Multilateration is poor, but when combined with
Multi-ranging then the area enclosed by both the hyperboloids and the ellipsoid is much smaller.
The combination of ellipsoid and hyperboloid data provides the position estimation algorithm more
information from which to accurately and unambiguously calculate target position.
The error characteristics of the hyperbolic and elliptical techniques are complimentary, significantly
increasing location accuracy when both techniques are used in combination.

MSS Description
Figure 37 2-D Plot combining Multilateration Hyperboloids and Multi-ranging Ellipsoid
Multi-ranging improves the both the probability of detection for the system, the coverage and
redundancy. If a reply is corrupted at one receiver then it is still possible to calculate a full 3D position
with replies from three other receivers and the range measurement. This also means that if one
receiver is lost the system can continue to produce positions by using the remaining receivers for
TDOA combined with the ellipses from multi-ranging. Alternatively fewer receivers can be used to
achieve the same level of redundancy saving on lifecycle costs for the system.
The multi-ranging method used by Era ensures that NEO is the highest performing multilateration
solution on the market. The majority of other manufactures rely solely on the standard TDOA solution.
This means they are only accurate within the baseline of their sensors. One other manufacturer uses a
simple ranging technique. They have a combined interrogator and receiver unit and measure a simple
range as part of the interrogation. This produces a single sphere that the target could lie on instead of
multiple ellipses. It is an improvement on the TDOA only solution but it does not offer the same degree
of accuracy or the integrity and redundancy benefits of the Era multi-ranging solution.

MSS Description
Appendix B MLAT Signal and Data Processing

Localization of all targets (aircrafts equipped with Mode A/C/S transponders, cars equipped with Mode
S squitters etc.) is primary based on signal and data processing. The SSR signal from target is received
in receiver and this electromagnetic signal is converted to electric form. Than this electrical signal is
time stamped and decoded. Resulting data are lead to the Target processor where target processor
software simultaneously evaluates data from all Ground stations and provides target localization.
The signal and data processing chain is depicted on the following figures:
109
0 MH
z
Hz
0M
Signal
103
Hz Data Transfer
0M Reception
109
Digitization
Interrogation
Time stamping
Target
Data Transfer Data Transfer
Processing
Multisensor
Data Transfer
Data Fusion
Figure 38 Signal and data processing flow
For target tracking the 4-stages Kalman filter is used. The target initiation, target tracking and track
termination parameters are configured in the adaptation data, where, for example, various initiation
and termination timeouts can be set and conditions of transition among tracking stages are
configured. The setup is controlled by the Management System. In case the track is terminated, an
“end-of-track” message is output.
Permanent evaluation of the accuracy of the NEO is based on measuring of the reply rate and the
exactly known position of reference transmitters. These values are then compared with predefined
thresholds. The reference transmitters have to be installed at positions where the system accuracy is
reasonably good.
The results of the integrity check can be displayed by the Management System.
Information on the system accuracy is also included in each target report – in the covariance matrix
elements. The covariance matrix is calculated from statistical evaluation of the history of the measured
target’s positions and it contains horizontal and vertical standard deviations of the position. Plot
reports, whose accuracy exceed the predefined accuracy thresholds for the specific area, are not
validated and are by default not being output (can be optionally enabled).

MSS Description
B.1. Mode S Data Processing
Reply preamble is detected in the case of replies in Mode S. TOA of the preamble pulses, data contents
of Mode S reply and additional information are transferred to computer in several words.
The NEO gets a unique 24 bit address as well as information about the transponder’s capabilities from
Mode S short squitters that are transmitted spontaneously (approximately once per second) by an on-
board Mode S transponder.
The Mode S address is then used by the NEO system to selectively interrogate the aircraft in order to
obtain:
 The Mode A code from the level 1 transponders
 The aircraft identification from the transponders level 2 and above.
 The Mode C altitude
 Flight Status (GND)
The IC code and UF formats to be used are configured as part of the system adaption process.
NEO can process Enhanced Surveillance data from Mode S and ADS-B. Comm-B data is forwarded as
received in the replies from the aircraft to downstream systems for processing.
The Mode S downlink formats processed are selectable as part of the system adaptation.
Mode S parameters are decoded according to the format specifications in the following documents:
 ICAO Annex 10, volume III and IV;
 Manual on Mode S specific services ICAO DCO 9688-AN/952;
 RTCA DO – 260/260A, volume I and II;
 RTCA DO – 286.
The address of the target is evaluated from the short Mode S squitter. The identification (Mode A) and
barometric height (Mode C) is evaluated from the replies to the addressed interrogations.
To obtain the Mode A code from the Mode S target on the ground, the NEO must have a Mode S
interrogation capability. The Mode S interrogation is provided by the TXS.
The technique of target identification on the ground is shown in the following image:

MSS Description
Figure 39 Principle of target identification
The processing part of the NEO transfers Mode S addresses decoded from short and/or extended
squitter to the Transmitting Unit. The Transmitting Unit transmits direct addressed interrogations to
the selected target to acquire its Mode A code.
In order to minimise interference with other systems sharing the frequency band or with on-board
transponders, the interrogations are transmitted with controlled output power and with low
interrogation repetition frequency within the coverage area. Mode S lockout is not used.
The target identification algorithm is shown on the following figure:

MSS Description
Figure 40 Mode S Target identification algorithm

MSS Description
B.2. Mode A/C Data Processing
Detection of replies in modes A/C is based on presence of frame pulses F1 and F2 with distance of 20.3
μs. Detection tolerance and reply rejection conditions are adjustable by program. In case of detection
of these frame pulses the time of their arrival (TOA of F1 and TOA of F2) and reply data contents is
transferred to computer. Measuring of interleaved replies is available.
In the passive mode of operation (without NEO interrogation), the NEO extracts Mode A/C codes from
the received SSR replies and uses statistical methods to distinguish the Mode A code from the Mode C
codes. Together with the coding rules used for Mode C, the multilateration (measured) height, altitude
“tracking” and other additional information is utilised.
For VFR flights the system can process and output multiple Mode A codes with the same value.
For Mode S only environments the Mode A/C data can be included or excluded as part of the system
adaptation. Where it is included the system can process all aircraft with the same Mode A code.
In the active mode of operation, the NEO interrogates targets in Mode A and Mode C and correlates
the codes similarly to the SSR or ACAS. The interrogation pattern, rate and which codes are
interrogated are configured as part of system adaption.
Intermode (“All call A/C only”) and/or “Whisper/Shout” techniques are used to diminish possible
garbling.
The NEO can optionally use its own Mode A/C interrogation for the following reasons:
 Poor or no coverage from SSR radars in low flight levels and on approach.
 To ensure required target report update rate.
 To ensure satisfactory accuracy in areas with bad PDOP by using multi-ranging.
 To keep the computer and data link load as low as possible by using elliptical
filtration.
The typical configuration of Mode A/C interrogation is as follows:
 Every second, one of the installed transmitting stations transmits the adjustable
specific Mode S squitter, followed by the specific Mode A/C interrogation pattern.
 The Transmitted Mode S squitter enables the use of multi-ranging algorithms because
it informs all receiving stations and target processor about the exact time of the start
of the Mode A/C interrogation start.
 The Mode A/C pattern is independently selectable for every transmitting station and,
for example, can be defined in the following way: AAACAAAC, f = 100 Hz, where the
letter A means Mode A interrogation, the letter C means Mode C interrogation, and
expression f=100 Hz specifies repetition frequency of interrogations. The repetition
frequency follows the ICAO Annex 10 and it is selectable up to 450 Hz.

MSS Description
Appendix C Automatic Dependent Surveillance - Broadcast (ADS-B)

Aircraft equipped with Automatic Dependent Surveillance – Broadcast (ADS-B) equipment continuously
and automatically transmit position information, derived from the on-board navigation system. In
addition, other information such as altitude, heading, velocity and identification data is also
transmitted. All of this information can be received and decoded by other aircraft. By deploying a
network Era’s NEO Ground Stations, this information can also be made available to air traffic control
systems.
ADS-B is an important component of next generation air traffic management because, like MLAT, ADS-
B offers significant safety, cost and operational benefits over traditional surveillance radar. Era’s NEO
consists of an antenna, an electronic unit with a receiver and a target processor. A cable, which feeds
the unit and ensures data transmission, is connected to a water resistant connector and a site
monitor(s) delivers important integrity information.
Figure 41 ADS-B Principle
The future of air traffic control calls for aircraft and vehicles to be equipped with appropriate Mode S
transponders transmitting Mode S extended squitters containing ADS-B messages. These transponder
units are integrated with the onboard aircraft navigation system, which typically utilises a GNSS
receiver. The position information is then coded into an ADS-B message and transmitted from the
target as a Mode S signal.
Era’s Ground Station collects Mode S signals through an antenna and receiving module.
The NEO Ground Station decodes and time-stamps ADS-B messages (DF-17, DF-18, and DF-19) in
accordance with the following documents and data formats and complies with all applicable ICAO and
Eurocontrol standards.

MSS Description
 DO-260A Minimum Operational Performance Standards for 1090 MHz Automatic

Dependent Surveillance – Broadcast (ADS-B) and Traffic Information Services (TIS-B),
RTCA, Issued 4-10-03, Prepared by SC-186, Supersedes DO-260
 DO-242A, Minimum Aviation System Performance Standards for Automatic Dependent

Surveillance Broadcast (ADS-B), RTCA, Issued 6-25-02, Prepared by SC-189, Supersedes
DO-242
 Surveillance and Conflict Resolution System Panel (SCRSP). Surveillance Systems Working
Group-B. WP/B/6-05 SARPs CP for Global Decoding of the ES Surface Format
For Airborne and surface position DF17 messages, ground stations use the CPR decoding algorithm
defined in Annex A.7 of ED-102 / DO-260 and Annex A.1.7. of DO-260A to decode WGS84 position.
Only messages that pass Cyclic Redundancy Checks (CRC) are processed. As well, the ground station
employs Lincoln Laboratory specified error detection and decoding techniques.
A geographic filter may be applied to screen out ADS-B targets that are not of interest, including
ground vehicles and ASTERIX Category 21 messages. Output from the System can be limited to only
contain aircraft information decoded from Mode S DF 17 and DF 18 messages.


ERA - Technical Manual

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ERA - Technical Manual

Загружено:

Авторское право:

Доступные форматы

NEO by ERA - Technical Manual

Commercial in Confidence Page 2 of 87

4.1.4. Other GS Assemblies ............................................................................................................................... 36

Commercial in Confidence Page 3 of 87

10. ERA’S REFERENCE DOCUMENTS .................................................................................................................... 70

11. GLOSSARY ..................................................................................................................................................... 71

Commercial in Confidence Page 4 of 87

Figure 1 NEO Typical Environment.............................................................................................................................. 9

Commercial in Confidence Page 5 of 87

Figure 38 Signal and data processing flow ................................................................................................................ 81

Commercial in Confidence Page 6 of 87

Table 1 Processed Signals ......................................................................................................................................... 11

Commercial in Confidence Page 7 of 87

The document has seven main sections:

Section 2 - NEO Overview

Section 3 - System Performance

Section 4 - System Architecture and Design

Section 5 - Management System

Section 6 - System Interfaces

Section 8 - Reliability and Availability

1.1. NEO - Next Generation Multilateration and ADS-B Surveillance

Commercial in Confidence Page 8 of 87

Figure 1 NEO Typical Environment

Commercial in Confidence Page 9 of 87

2. NEO Overview and specific applications

Commercial in Confidence Page 10 of 87

Ground Ground Ground Ground

Figure 2 Generic Multi-sensor Surveillance System

2.1.1. Processed Signals

2.1.2. Synchronisation Architecture

Commercial in Confidence Page 11 of 87

2.1.2.1. Central Timing

 A dedicated microwave link

2.1.2.2. Distributed Time

2.1.2.2.1. Advanced GNSS Synchronisation

Commercial in Confidence Page 12 of 87

2.1.3. Active and Passive NEO

2.1.3.1. Passive NEO

2.1.3.2. Active NEO

 SSR interrogation 1030MHz,

2.1.3.2.1. Interrogation 1030 MHz

2.1.3.2.2. Transmission on 1090 MHz

Commercial in Confidence Page 13 of 87

 Integrity check (back-up of reference transponders)

2.1.3.2.3. 1030/1090 Spectrum Management

o The addressed Mode S interrogations

o The Mode A/C interrogations

 Low number of NEO interrogators that will interrogate in Mode A/C

2.2. Specific Application Architectures

Commercial in Confidence Page 14 of 87

2.2.1. ADS-B Based Surveillance

ADS-B based surveillance represents the simplest NEO implementation.

Automatic Dependent Surveillance – Broadcast (ADS-B) is an important component of next generation

There can be two (2) variants of ADS-B surveillance system architecture:

 Stand-alone ADS-B system

The simplified architecture is shown in Figure 3.

Commercial in Confidence Page 15 of 87

1090 MHz ES GPS Data

RXS RXS RXS

ASTERIX ASTERIX ASTERIX

Figure 3 Stand-alone ADS-B processing

1090 MHz GPS