SAI SIR Section J.1 12.27.23.docx

Federal Aviation Administration Air Traffic Organization Minimum Requirements Document For Surface Awareness Initiative

1.

1. Scope This document contains the Minimum Operational Performance for the Surface Awareness Initiative (SAI) to be considered for inclusion on a Qualified Product List (QPL) wherein the Federal Aviation Administration (FAA) or other governing entities (e.g., local airport authorities) may independently acquire such solutions as appropriate.

This document describes the minimum performance initially required for SAI solutions. Capabilities beyond what is identified herein are anticipated in the future and will be defined as part of follow-on efforts under the QPL.

The requirements within this scope may be updated on a periodic basis in accordance with Section H (to be released for the Final SIR).

Introduction A safe and efficient National Airspace System (NAS) begins and ends on the airport surface. Separation services that are provided by Air Traffic Controllers (ATC) in the sky, are also paramount on runways, taxiways, and other airport surface movement areas. Giving ATC the tools necessary to improve their situational awareness on the surface is key for the future of surface safety. SAI will deliver innovative, cost-effective technological solutions to airports without existing surface surveillance capabilities to expand ATC’s surface situational awareness.

Program Description SAI solutions will leverage Automatic Dependent Surveillance – Broadcast (ADS-B) as the primary surveillance source to detect aircraft position both on the surface and in airport arrival and departure corridors. These ‘targets’ will be displayed over an airport surface map that will, at a minimum, also depict runways, taxiways, hold ramps, and other movement areas. In addition to aircraft targets, any vehicles that are equipped with ADS-B Out capabilities will also be displayed on the map.

Document Structure Section 1 of this document provides a brief background and overview of the SAI program.

Section 2 of this document provides high level program information and Concept of Operation (CONOPS) scenarios to illustrate how SAI solutions would be utilized in an operational setting.

Section 3 contains the minimal functional and performance requirements.

Note, terms that are defined in the Glossary are written in Italic.

CAPABILITY DESCRIPTION AND PROGRAM INFORMATION

Initial Assumptions and Constraints Assumptions

· SAI solutions are supplemental in nature, providing discretionary information for situational awareness only.

· Domain of interest is the Surface, which includes the approach and departure corridors as specified in the requirements below.

· SAI solutions will be deployed at ATC facilities where ADS-B Out is required.

Constraints

· Aircraft and vehicles that are not broadcasting out their position via ADS-B may not be displayed.

· Any interface / network connection to NAS systems must be inbound to SAI only and through a security gateway or a publicly available access point.

Concept of Operation SAI solutions contribute to the goal of enhancing runway safety by providing enhanced situational awareness to airports that currently do not have a surface surveillance capability. SAI solutions will provide surface surveillance of ADS-B equipped aircraft and vehicles and depict their position on a display(s) in an Air Traffic Control Tower (ATCT) and/or another tactical operations environment. The SAI display is an optional tool to be used by operators such as ATC to complement existing means of observations and situational awareness of the surface domain. Below are four scenarios to illustrate how an SAI system might be used.

Scenario 1 – Push Back During the afternoon rush several aircraft are being pushed back from their gate in preparation for departure. The pilots enable transmission of their aircraft’s ADS-B. As each aircraft approaches the airport movement area, the SAI display depicts individual icons representing each aircraft along with an associated data block. Additionally, depicted is a vehicle icon from an airport operations Foreign Object Debris (FOD) inspection truck equipped with ADS-B out traversing the taxiway on the far end of the airfield. The local controller pans the SAI display such that the airport operations vehicle is centered on the screen.

Scenario 2 – Runway Crossing In the late afternoon prior to the evening push, a line of thunderstorms approaches the terminal area. A ground stop is issued so all departures are delayed. One of the departing aircraft must return to the gate due to crew time out. The delayed departures in the holding pen, as well as the aircraft returning to the gate are depicted on the SAI display. Meanwhile, there are four aircraft approaching the airport. As the first aircraft approaches the runway threshold, the aircraft returning to the gate requests clearance to cross runway 28R, which is the active runway. The controller working both ground and local approach positions visually locates the aircraft requesting to cross through the heavy precipitation now falling over the airfield. The controller also views the SAI display for affirmation of the location of the aircraft and instructs the pilot to hold at their current position as they are not cleared to cross. Once the arriving aircraft lands and exits the runway, the controller contacts the aircraft returning to the gate and provides clearance to proceed across the runway.

After the line of convective weather moves off, the ground stop is lifted. Aircraft awaiting departure that had been in the holding pen are cleared to depart. While issuing instructions to the departing aircraft, the controller glances at the SAI display and notices it is consistent with aircraft viewed through the tower windows as expected.

Scenario 3 - Maintenance The SAI status monitoring capability detects a parameter outside of normal values and a fault condition is generated. The SAI display indicates a degraded state. ATC notices the indicator but the seamless movement of aircraft on the surface is not impacted. Facility personnel contact the prescribed help desk. Service provider technicians responsible for resolving the fault condition do so and the SAI display again indicates a normal state. 15 minutes upon returning to normal, ATC notices that the aircraft indicated on the SAI display are consistent with their position on the surface.

Scenario 4 – Conflict Avoided In the early morning hours, the airport experiences very poor visibility of ¼ statute mile in freezing fog with an indefinite ceiling of 200’ vertical visibility. The reported Runway Visual Ranges on runway 18L are 1400’ at touchdown, 600’ at mid-point and 1800’ at rollout. A Boeing 767 is on the Category 3 Instrument Landing System (CAT III ILS) approach to runway 18L. The B767 checks in with local control and local control issues a landing clearance to the B767. The controller’s view from the tower cab, which is 200’ above ground level, is like being inside a cloud. A Boeing 737 taxis toward runway 18L for takeoff. The taxiing aircraft is not visible to the ATC due to the poor weather conditions. The B737 reports holding short of runway 18L and ready for takeoff. Noting the position of the approaching B767 on the tower’s Standard Terminal Automation Replacement System (STARS) display, the controller issues a takeoff clearance to the B737. After 30 seconds, the controller glances at the SAI display and notes that the 737 has not yet begun its takeoff roll. The controller calls the B737 for confirmation that he has not begun his takeoff roll. Based on the confirmation, the controller then cancels the takeoff clearance of the B737 and issues go-around instructions to the 767.

1. Requirements Functional Requirements Display System The SAI system must include display(s) running surface awareness applications that provide increased situational awareness to ATC personnel. Note: The quantity of displays will be based on individual site surveys.

The surface awareness application must display Targets that are detected by the SAI system and are within the defined Coverage Volume.

The surface awareness application must differentiate aircraft from vehicles.

The surface awareness application must include a map that accurately depicts the:

a. Runways, taxiways, and other areas of an airport/heliport which are utilized for taxiing/hover taxiing, air taxiing, takeoff, and landing of aircraft.

b. Gates, ramps, parking areas, and other areas of an airport where aircraft may be present.

The surface awareness application must be user interactive, including the following basic functions:

c. Pan

d. Zoom

e. Selectable Data Blocks for displayable Targets

f. System Time

g. Rotate the map The surface awareness application must display the current System State.

Surveil Target The source of SAI Target information must be derived from ADS-B data.

The SAI system must detect actively transmitting ADS-B equipped aircraft.

The SAI system must detect actively transmitting ADS-B equipped ground vehicles (e.g., trucks).

The display of Targets must be configurable based on location and altitude.

Equipment The SAI display used in the tower cab must have mounting options compatible with existing tower configurations, including VESA and freestanding mounting.

The display presentation must be discernable in all lighting conditions.

The display equipment must provide user controls for brightness, contrast, and sharpness.

The display must have a diagonal viewing size of at least 20 inches.

The SAI system must provide its own communication networks independent of the FAA networks.

Note: Access to the FAA Admin / Mission Support networks may be granted for client-side display of targets via a web browser.

SAI equipment installed outdoors must be protected from the environment.

SAI equipment installed inside of FAA facilities must not interfere with operations or existing equipment.

SAI equipment connected to facility power must comply with the power quality requirements of FAA-G-2100J, Electronic Equipment, General Requirements, Paragraph 3.1.1.2.

SAI solutions must adhere to FAA spectrum management requirements in accordance with FAA Order 6050.32, Spectrum Management Regulations and Procedures Manual, and FAA Order 6050.19E, Radio Spectrum Planning.

System Monitor and Control The SAI solution must include an interface(s) that provides control AND monitoring of the service to the service provider.

The SAI system must automatically collect service performance data in support of the Technical Performance Measures Report (TPMR).

The SAI system must automatically monitor the health of subsystems to determine the System State.

The SAI system must periodically synchronize its system time to Coordinated Universal Time (UTC).

The timestamps in all messages must be relative to UTC.

Information Systems Security The SAI solution must include Information Systems Security (ISS) controls that address confidentiality, integrity, availability, and security.

Note: This requirement allows for various ISS approaches based on industry and/or Government standards (e.g., ICAO Doc-9985, ISO/IEC 27001, NIST 800-53).

Performance Requirements The SAI system must detect ADS-B equipped Targets located on the airport surface and within 5 nautical miles of each runway threshold greater than or equal to 99 percent of the time.

The SAI system must be capable of receiving AND decoding all ADS-B messages, including both 1090 Mega Hertz (MHz) and 978 MHz sources, in accordance with DO-260B AND DO-282B.

The maximum latency between the receipt of the last bit of a valid ADS-B position message at the ground station and the display of the Target on the controller application must be less than or equal to 1.0 seconds 99% of the time.

All Targets within the defined Coverage Volume must be updated and maintained on the display at least every:

1.0 second 95% of the time for non-stationary 1090ES Targets

5.5 seconds 85% of the time for stationary 1090ES Targets

1.3 seconds 95% of the time for UAT Targets.

The Registration of the display map must have an accuracy of at least 20 feet relative to the airport surface.

The SAI system Adjusted Service Availability must be greater than or equal to 0.99 over the preceding 12 months.

The SAI system must have a Mean Time-to-Repair (MTTR) less than or equal to 0.5 hours.

The SAI system Target loading capacity must be greater than or equal to 200 Targets located anywhere within the coverage area.

Appendix A – Acronyms

Appendix B – Glossary Definitions provided in the Glossary are considered part of the requirements in which the associated term is used.

Uptime is defined as the element of time during which the service provider’s system is performing its required service functions. Downtime is the element of time during which the service provider’s system is not performing its required service functions. The sum of Uptime and Downtime is the total time the service is planned to be provided by the Service Provider. It excludes time for testing and integration prior to the service being made available for operational use.

Because certain types of service outages do not count against the service provider, Adjusted Service Availability (Aadj) is used in the computation of the TPMs. Adjusted Service Availability is defined as:

Notes:

1. Downtimeexcused is defined as service outages due to:

· Scheduled outages (i.e., maintenance scheduled with the FAA with the potential outages specified and coordinated)

· Failure of GFE required for the service, (e.g., power outage at FAA facility, GFE telecommunications outage)

· Failures arising from causes beyond the control of the service provider as defined in AMS Clause 3.10.6-7

2. Downtimeunexcused = Any downtime that is not excused

3. Downtimetotal = Downtimeexcused + Downtimeunexcused

· For aircraft, this may include (but is not limited to): flight identification, beacon code, barometric altitude, emitter category, or velocity.

· For vehicles, this may include (but is not limited to): call sign, emitter category, or velocity

· Online: indicates that the system is fully functioning

· Degraded: indicates that the system is functional, but a fault had been detected

· Offline: indicates that the system is not available for operational use image1.png