GROUND ASAS EQUIPMENT Michel Procoudine Gorsky ASAS TN

GROUND ASAS EQUIPMENT Michel Procoudine Gorsky ASAS TN 2 – Workshop 5 Toulouse 17 th-20 th September 2007 Air Systems Division

Outline Introduction Ground Surveillance Applications n NRA : the simple case ? n Next steps ASAS n What about automation systems ? 08/03/2021 Conclusion 2 Air Systems Division

Introduction Ground Surveillance Applications (GSA) are forerunners of ADSB implementation ASAS is considered as a key enabler in future generation ATM systems n SESAR n Next. Gen ASAS are also considered as new functions in some areas n TMA: USA UPS - Merging and Spacing 08/03/2021 n En-Route: Australia - ITP 3 Air Systems Division

Question A key question is to determine what is the impact of implementing GSA and then ASAS on ground systems The current RFG work (OSED, SPR, INTEROP) includes an allocation of safety and performance requirements to airborne and ground domains 08/03/2021 However, in this context, performance allocation for ground domain is limited to ADS-B ground station. Done on purpose to avoid increased complexity in an already difficult exercise 4 Air Systems Division

Outline Introduction Ground Surveillance Applications n NRA : the simple case ? n Next steps ASAS n What about automation systems ? 08/03/2021 Conclusion 5 Air Systems Division

ADS-B-NRA : the simple case ? Accommodating new surveillance technologies will have an impact on the ATM System n New surveillance source impact the elaboration of the air situation Surveillance processing function (eg tracking) n Controller Working Position (eg target symbol) n n Data link capabilities (Aircraft Derived Parameters) impact the elaboration of the air situation, alerts capability, controller tools Surveillance processing function (eg tracking) n Alerts management function n Controller Working Position (eg target symbol, target data) n 08/03/2021 n The solution to integrate new surveillance means may differ depending on the capabilities and age of the ATM system 6 Air Systems Division

Initial ADS-B-NRA : principle of priority tracks system Radar Tracks ADS - B tracks ADS- C tracks (FANS 1/A datalink) Flight Plan tracks If an aircraft is seen by a radar, the displayed track will be based on radar even if the ADS-B information is available for this aircraft Then this principle can be applied for several surveillance sources: n Priority 1: Radar n Priority 2: ADS-B (or WAM) n Priority 3: ADS-C n Priority 4: Flight Plan 08/03/2021 Facilitates the safety case Not the most efficient (at 200 NM from the radar an ADS-B track is better than the radar track) 7 Air Systems Division

Implementation of ADS-B NRA : modified components Additional hardware and software: ADS-B processing chain n ADS-B Front Processor n ADS-B Data Processing n ADS-B By-pass Additional hardware and software: RAIM Outage prediction n RAIM prediction tool n RAIM server 08/03/2021 Modified software n Safety Nets Manager n Controller Working Position n Ancillaries (simulator, recording, …) RAIM: Receiver Autonomous Integrity Monitor 8 Air Systems Division

Example of priority tracks implementation Op LAN 2 Op LAN 1 Serv LAN 3 ADSB BYPASS ADS-B Operational Data From Ground Stations ADS-B Lan Dual FDPCV ADSB FP Dual FDP ADSBP FDP RAIM PREDICTION SYSTEM RAIM Server RAIM PREDICTION Every 12 hours Or on NANU Modified Radar Data 08/03/2021 New 9 Air Systems Division FDP SNMAP FP MTP FPFP FP RTP MMI FDP: Flight Data Processor FP: Front-Processor MTP: Multi-Tracking Processor RTP: Radar Tracking Processor SNMAP: Safety Net Manager Processor

Next Step : Fused Tracks Display A fused track system makes the best estimate from available surveillance sources Fused System Tracks • single system track for all sensors • fusion of all relevant downlinked data • more accurate tracking Configuration with 1 radar Configuration with 4 radars Configuration with fused ADS-B and 4 radars System track multi-radar not updated by ADS-B : Segment in blue color System track multi-sensor updated by ADS-B : Segment in blue color ADS-B report: Plot in pink color 08/03/2021 Cap Town: Multi-Radar tracking 10 Air Systems Division

Example of fused tracks implementation Op LAN 2 Op LAN 1 Serv LAN 3 ADSB BYPASS ADS-B Operational Data From Ground Stations ADS-B Lan Dual FDPCV ADSB FP Dual FDP ADSBP FDP RAIM PREDICTION SYSTEM RAIM Server RAIM PREDICTION Every 12 hours Or on NANU Modified 08/03/2021 New 11 ADS-B Radar WAM Data Air Systems Division FDP SNMAP FP MTP FPFP FP MSTP MMI FDP: Flight Data Processor FP: Front-Processor MTP: Multi-Tracking Processor MSTP: Multi Sensor Tracking Processor SNMAP: Safety Net Manager Processor

Use of Multiple Surveillance Data and DAP allow to enhance existing functions or add new functions Existing alert functionality may be enhanced: è Short Term Conflict Alert è Cleared Level Monitoring è Route Adherence Monitoring è Minimum Safe Altitude Warning and è Danger Area Infringement Warning New alerts may be defined: è Inconsistency between data from various surveillance sources è Inconsistency between surveillance data and flight plan data 08/03/2021 Controller Access Parameters : display DAP to the controller Improvement of Trajectory Prediction (Flight Plan) 12 Air Systems Division

Outline Introduction Ground Surveillance Applications n NRA : the simple case ? n Next steps ASAS n What about automation systems ? 08/03/2021 Conclusion 13 Air Systems Division

ASAS : the controller is still there ! Rules and procedures for implementing ASAS will depend on environment, application, national rules The primary focus is to define at which extent the controller is involved in the application and what are his responsibilities and limitations => purpose of the OSED (prepared by the Requirement Focus Group) 08/03/2021 Key objective of ASAS is to contribute to safety, efficiency and capacity improvement. To achieve this, tools will be necessary to support the controller: n In identifying ASAS capable aircrafts n In assessing the impact of ASAS clearances (“what if”) and monitoring the clearance (alerting) OSED: Operational Services and Environmental Description 14 Air Systems Division

Automation Systems : Technical Requirements Available OSEDs address impact of application on automation systems (e. g. ADS-B-NRA, ADS-B-RAD, ATSA-ITP, …) Generally through high level operational requirements and recommendations on the Controller Working Position or automation system as a whole However operational requirements are not clearly transformed into technical requirements in the SPR/INTEROP process n Limited to the ground stations 08/03/2021 n Capabilities of modern automations systems are not considered (in term of contribution to performance, safety, …) SPR: Safety and Performance Requirements INTEROP: Interoperability Requirements 15 Air Systems Division

Other considerations New ground systems functions are considered in the scope of ASAS: n TIS-B infrastructure (server, uplink stations) n ADS-B rebroadcast (dual link environment) Data elaborated and distributed by these new functions will be used on-board n Globally agreed requirements and interfaces must be developed to ensure interoperability In future generation systems, ASAS will have to interface with other ATM functions: n Trajectory management 08/03/2021 n Tactical Air Traffic Flow Management 16 Air Systems Division

Outline Introduction Ground Surveillance Applications n NRA : the simple case ? n Next steps ASAS n What about automation systems? 08/03/2021 Conclusion 17 Air Systems Division

Last slide ! An remarkable work is being carried out by the Requirement Focus Group to support a global definition of ASAS applications To avoid increased complexity, ground domain is limited to ADS-B Ground Stations as far as SPR / Interop is concerned However to ensure a timely implementation of ASAS, automation systems must be considered in the definition of operational, safety and performance requirements 08/03/2021 This should include: -Which functions are expected from automation systems -What are the associated safety and performance requirements -What standards need to be prepared to ensure interoperability 18 Air Systems Division

Thank you for your attention For more information, contact michel. procoudine@thalesatm. com Air Systems Division