Attachment 2 - Draft SIR - Section J - SMR4 SSD (Release).docx

Surface Movement Radar, Model 4 (SMR4) System Specification Document

U.S. Department of Transportation Federal Aviation Administration

Surface Movement Radar, Model 4 (SMR4) System Specification Document (SSD)

FAA-E-XXXX

Revision Draft

September 12, 2022

Federal Aviation Administration 600 Independence Avenue, SW Washington, D.C. 20591

Date:

William Kaplan, Program Manager, AJM-4210

Table of Contents

List of Figures Figure 1–1: SMR Block Diagram 2

Document Version Control Log

1. Scope This document details the requirements for the Surface Movement Radar, Model 4 (SMR4) system that the Federal Aviation Administration (FAA) will acquire under the Airport Surface Detection Equipment, Model 3 (ASDE-3) Surface Movement Radar (SMR) Replacement (3SR) project. This specification identifies the functional and performance requirements of a non-cooperative radar system that will replace existing ASDE-3 SMRs. The SMR4 will provide non-cooperative surveillance of aircraft and vehicles on the airport movement area as a fully integrated subsystem of the FAA’s existing Surface Surveillance Systems. The existing Surface Surveillance Systems include Airport Surface Detection Equipment, Model X (ASDE-X), and Airport Surface Surveillance Capability (ASSC).

Introduction The Federal Aviation Administration is dedicated to the goal of enhancing runway safety while maximizing operational efficiency and ensuring airport capacity. The reduction of runway incursions has been identified as one of the most important aviation safety initiatives and is crucial for the improvement of runway safety. The FAA Surface Surveillance Systems are currently deployed at larger airports throughout the National Airspace System (NAS) to provide the surface surveillance capability that enhances situational awareness for air traffic controllers. The safety logic incorporated into these systems aids in the real-time detection and alerting of potential runway collisions.

The FAA Surface Surveillance Systems use cooperative and non-cooperative surveillance sensors to detect and track aircraft and vehicles within the airport movement area. Cooperative surveillance sensors rely on aircraft transponder and vehicle transmitter transmissions to determine position and identity. Non-cooperative surveillance sensors are not reliant on any type of active transmission from a target via transponder/avionics for position determination.

ASDE-3 SMRs are currently used for non-cooperative target detection at 18 ASDE-X and 9 ASSC airports. These SMR subsystems have been operational in the NAS for 20 to 30 years. They are now approaching end-of-life and several obsolescence and supportability issues have been identified. Due to these issues, the ASDE-3 SMRs are no longer sustainable, requiring a full replacement with newer technology that can meet the operational requirements of the FAA. The 3SR project will replace ASDE-3 SMRs with a new, sustainable commercial SMR, designated as the SMR4.

The SMR4 will provide the technological updates necessary to maintain the current levels of performance, availability, and reliability of the surface surveillance solutions deployed today. Without this service, there will be gaps in surveillance coverage which may create potential hazards. Sustaining the non-cooperative surveillance capability will play a significant role in maintaining the current level of safety and efficiency at airports with an ASDE-X or ASSC system.

Description The ASDE-X and ASSC systems are used by Air Traffic to augment visual observation of aircraft and vehicles on runways and taxiways, or other parts of the movement area, as well as airborne aircraft on approach or departure. The SMR4 equipment will be deployed throughout the NAS and will interface with the Multi-Sensor Data Processor (MSDP) processor of the installed Surface Surveillance System in the same manner as the currently fielded SMRs. The SMR4 will provide the technological updates necessary to maintain the current levels of performance, availability, and reliability of the deployed surface surveillance solutions.

At each Surface Surveillance System, one or more SMRs provide target reports to the MSDP subsystem through ethernet interfaces with a redundant Local Area Network (LAN) communications system. The MSDP fuses the SMR data with Multilateration (MLAT) and Airport Surveillance Radar (ASR) sensor data, as well as ADS-B position information from Surveillance Broadcast Services (SBS), for display of aircraft and vehicles on air traffic controller displays. The MSDP also performs safety logic processing to alert controllers of potential collisions. Figure 1–1 shows a simplified block diagram of the current SMR subsystems.

Figure 1–1: SMR Block Diagram Constraints There are two (2) different Surface Surveillance Systems that the SMR4 will need to interface and be integrated with:

· Airport Surface Detection Equipment, Model X (ASDE-X)

· Airport Surface Surveillance Capability (ASSC).

To minimize interruptions in service to the greatest extent practicable during installation and Site Acceptance Testing (SAT), the SMR4 will interface with an FAA provided test system. These test systems are referred to as either a mini ASDE-X or a mini ASSC.

Applicable documents General The documents listed in Section 2 contain the references from requirements in Section 3. Any documents referenced outside of Section 3 are not listed in Section 2 and are for additional information. While every effort has been made to ensure the completeness of this list, users are cautioned that they are required to meet all specifications cited in Section 3.

a) Requests for security related documents should be addressed to the FAA Contracting Officer (CO). Requests should fully identify material desired and cite the solicitation or contract number.

b) Military Standards and Specifications can be ordered from the Department of Defense Single Stock Point (DODSSP), Building 4/Section D, 700 Robbins Avenue, Philadelphia, PA 19111-5098.

c) Copies of EUROCONTROL documents may be obtained through the web site: http://www.eurocontrol.int/ Government Documents, TBD

1.

Non-Government Documents, TBD

1.

2.

Order of Precedence The above documents form a part of this System Specification to the extent specified herein. In the event of conflict between the documents referenced herein and the contents of this System Specification, this System Specification will be considered the superseding requirement.

Requirements This document uses ‘must’ as the mandatory imperative in requirement statements. Use of ‘must’ as the mandatory imperative complies with Federal Plain Language Guidelines, March 2011 Revision 1, May 2011 and the FAA Plain Language Toolkit accessible from FAA Plain Language Website: https://www.faa.gov/about/initiatives/plain_language.

Within the requirements of this specification, when the words “AND” and “OR” appear in capital letters, they are being used as logical operators defined as follows:

· AND – all the conditions of the requirement must be mandatory

· OR – one or more of the conditions in the requirement must be mandatory. Additionally, all permutations must be exercised Within the requirements of the SMR4 specification, when an element of a document is referenced such as a Subsection, Section, Paragraph, or Chapter, all subordinate Subsections, Sections, Paragraphs, or Chapters to the referenced element are applicable.

Terms that are capitalized and italicized (e.g., Operational State, Unplanned Interrupts, etc.) within the requirements in this document are defined in the Glossary in Appendix B. Definitions provided in the Glossary are considered a part of the requirements in which the associated term is used.

Functional Requirements This section provides the SMR4 functional requirements.

Detection and Processing Target Detection The SMR4 must detect Targets that are in the Airport Movement Area AND are within the Coverage Volume specified in Section 3.2.1.

The SMR4 must detect Targets during weather conditions that include any form of Atmospheric Moisture.

Noise and Clutter Rejection The SMR4 must include processing that prevents the generation of Target Reports from Static Clutter of any size within the Coverage Volume specified in Section 3.2.1.

The SMR4 must maintain the Target Detection performance specified in Section 3.2.2 in areas where Static Clutter is being suppressed.

The SMR4 must prevent the generation of Target Reports from Multiple Time Around Returns.

The SMR4 must maintain the Target Detection performance specified in Section 3.2.2 in areas where Multiple Time Around Returns are being suppressed.

The SMR4 must prevent the generation of Target Reports from Time Sidelobes when pulse compression techniques are utilized.

The SMR4 must maintain the Target Detection performance specified in Section 3.2.2 in areas where Time Sidelobes are being suppressed.

The SMR4 must prevent the generation of Target Reports resulting from Transients in the system.

Weather Processing The SMR4 must meet the Target Detection performance specified in Section 3.2.2 at transitions between clear weather and Atmospheric Moisture.

The SMR4 must meet the Target Detection performance specified in Section 3.2.2 through transitions of gradient Atmospheric Moisture.

The SMR4 must meet the False Tracks performance specified in Section 3.2.7 at transitions between clear weather and Atmospheric Moisture.

The SMR4 must meet the False Tracks performance specified in Section 3.2.7 through transitions of gradient Atmospheric Moisture.

Interference The SMR4 must meet all Performance Requirements in Section 3.2 while operating in an environment with other sources of radio frequency interference.

Multipath Detection and Reports The SMR4 must identify multipath False Targets while maintaining Target Detection requirements in Section 3.2.2.

The SMR4 multipath algorithms must be adaptable using both Global Parameters AND Region Based Parameters.

The SMR4 must be configurable to either enable or disable the dissemination of Target Reports for plots that have been identified as multipath False Targets by radar data processing.

When a plot has been identified as multipath, the SMR4 must set the ASTERIX Category 010 GHO bit to a value of 1 in the Target Report.

Suppression and Blanking The SMR4 must be site adaptable to suppress the processing of radar signal returns within user defined Suppression Regions.

The SMR4 Maintenance Terminal must provide a graphical user interface for definition of Suppression Regions.

SMR4 Suppression Regions must have a resolution equal to one Radar Cell.

The SMR4 must be site adaptable to inhibit radio frequency transmission when the peak of the antenna’s transmit beam is within a user defined transmitter blanking sector.

The SMR4 Maintenance Terminal must provide a graphical user interface for definition of transmitter blanking sectors.

The SMR4 must provide at least 8 individual transmitter blanking sectors located anywhere within the 360 degrees of antenna coverage.

The SMR4 transmitter blanking sectors must have an azimuth resolution equal to one Pulse Repetition Interval (PRI).

Plot Detection The SMR4 must extract Plot Data from processed Raw Video.

The SMR4 plot extraction must be site adaptable.

The SMR4 plot extraction must include Region Based Parameters.

SMR4 plot extraction must be adaptable based on the amplitude of the Raw Video.

SMR4 plot extraction must be adaptable based on the size of contiguous Radar Cells exceeding Plot detection thresholds.

Target Tracking The SMR4 tracker must be site adaptable.

The SMR4 must use Plot Data to initiate tracks on all newly detected Targets within the Coverage Volume specified in Section 3.2.1.

The SMR4 must use Plot Data to update tracks on all existing Targets within the Coverage Volume specified in Section 3.2.1.

The SMR4 must assign a unique track number to each Confirmed Target under track.

The SMR4 tracker must maintain a track that loses Plot Data for an adaptable number of missing updates before terminating the track.

The SMR4 must prevent Split Tracks from being disseminated as multiple Target Reports.

Multiple Surface Movement Radar Configuration The SMR4 design must support a multiple Surface Movement Radar configuration consisting of up to four SMR4s installed as subsystems of a single Surface Surveillance System.

In a multiple Surface Movement Radar configuration, each SMR4 must meet all Performance Requirements in Section 3.2.

In a multiple Surface Movement Radar configuration, each SMR4 system must be stand-alone without sharing Operational Hardware.

In a multiple Surface Movement Radar configuration, each SMR4 system must include a unique system identifier in each external message.

In a multiple Surface Movement Radar configuration, each SMR4 must be individually addressable from any common Control Point.

External Interfaces The SMR4 must interface with the existing FAA Surface Surveillance Systems in accordance with the SMR4 to Surface Surveillance System Interface Requirements Document (IRD).

Existing System Network The SMR4 must support Internet Protocol Version 4 (IPV4).

The SMR4 must support Internet Protocol Version 6 (IPV6).

The SMR4 must communicate with the Surface Surveillance Systems over their redundant Internet Protocol networks.

SMR4 Internet Protocol address assignment(s) must be site configurable.

SMR4 Internet Protocol Port number assignment(s) must be site adaptable.

Time Synchronization The SMR4 must receive Coordinated Universal Time (UTC) from the connected Surface Surveillance System via their redundant IP networks using Network Time Protocol (NTP).

The SMR4 must synchronize its subsystem components to the Coordinated Universal Time (UTC) provided by the Surface Surveillance System.

Data Outputs Messages The SMR4 must timestamp all messages with an accuracy of less than or equal to 10 milliseconds relative to Coordinated Universal Time (UTC) time.

All messages from the SMR4 to the Surface Surveillance System must be output simultaneously on both redundant Internet Protocol networks.

Processed Digital Video The SMR4 must output processed Monobit Video to the Surface Surveillance System as ASTERIX Category 240 Radar Video Transmission messages in accordance with the EUROCONTROL ASTERIX Category 240 Specification, EUROCONTROL-SPEC-0149-240, Edition 1.3, dated 13/05/2015.

The SMR4 Monobit Video data must have a resolution equal to one Radar Cell.

Radar Target Reports The SMR4 must output Target Reports to the Surface Surveillance Systems as ASTERIX Category 010 Monosensor Surface Movement Data messages (CAT10) in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must include all Data Items identified as mandatory for Message Type 001, Target Report, in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The Time of Day reported in the SMR4 Target Report must be the time that the Plot was detected.

The SMR4 Target Report must include Data Item I010/042, Position in Cartesian Coordinates, expressed in the Radar Plane as defined in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

Cartesian Coordinates reported in the SMR4 Target Report must be the measured Plot position centroid.

Cartesian coordinates reported in the SMR4 Target Report must be relative to the radar center.

Cartesian coordinates reported in the SMR4 Target Report must be based on slant range.

Cartesian coordinates reported in the SMR4 Target Report must be relative to local geographic north.

The SMR4 Target Report must include Data Item I010/161, Track Number, as defined in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must include Data Item I010/202, Calculated Track Velocity in Cartesian Coordinates, as defined in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must include Data Item I010/270, Target Size and Orientation, as defined in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must include Data Item I010/170, Track Status, as defined in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must utilize the CNF field in Data Item I010/170, Track Status, in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must utilize the CST field in Data Item I010/170, Track Status, in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must provide Plot data without extrapolation.

The SMR4 Target Report must set the CST field in Data Item I010/170, Track Status, to a value of 0.

The SMR4 Target Report must utilize the TRE field in Data Item I010/170, Track Status, in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must utilize the MAH field in Data Item I010/170, Track Status, of the Target Report in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must utilize the TCC field in Data Item I010/170, Track Status, of the Target Report in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must set the TCC field in Data Item I010/170, Track Status, to a value of 0.

The SMR4 Target Report must utilize the STH field in Data Item I010/170, Track Status, of the Target Report in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must set the STH field in Data Item I010/170, Track Status, to a value of 0.

The SMR4 Target Report must utilize the DOU field in Data Item I010/170, Track Status, in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 Target Report must utilize the GHO field in Data Item I010/170, Track Status, in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

When SMR4 Target Reports are derived from multiple Plots, up to 7 of these Plots, in order of their probability, must be included in the Target Report using Data Item SP, Special Purpose Field, in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

An SMR4 Target Report including multiple Plots must include a probability rating for each Plot in the special purpose field.

An SMR4 Target Report including multiple Plots must include the range bounds of each plot relative to the SMRs position in the special purpose field.

An SMR4 Target Report including multiple Plots must include the azimuth bounds of each plot relative to the SMRs position in the special purpose field.

North Mark Message The SMR4 must send a North Mark Message to the Surface Surveillance System each time the antenna boresight passes True North.

The SMR4 North Mark Message must be formatted as an ASTERIX Category 10 Start of Update Cycle service message in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

The SMR4 North Mark Message must include all Data Items identified as mandatory for Message Type 002, Start of Update Cycle, in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007.

Operational Status Reports The SMR4 Operational Status Report musts be formatted as ASTERIX Category 010 Periodic Status Messages in accordance with the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007 or as ASTERIX Category 253 Remote Monitoring and Control messages in accordance with the EUROCONTROL Category 253 Specification, Edition 11, dated 08 February 2021.

The SMR4 Operational Status Report must include all Data Items identified as mandatory for Message Type 003, Periodic Status Message, in the EUROCONTROL Category 010 Specification, SUR.ET1.ST05.2000-STD-07-01, Edition 1.1, March 2007 The SMR4 must output Operational Status Reports to the Surface Surveillance System at a rate of once per second.

The SMR4 Operational Status Report must contain status information indicating the Operational Health of each system Line Replaceable Unit.

The SMR4 Operational Status Report must contain status information indicating the Operating Status of all Redundant Elements.

System Control Startup Initialization The SMR4 must automatically initialize all Operational Parameters to the current locally stored site adaptation during System Startup.

The SMR4 antenna rotation must remain unchanged during System Startup until a rotation command is manually initiated.

The SMR4 transmitter must be disabled during System Startup until a transmit start command is manually initiated.

System Status during Startup The SMR4 must perform system diagnostics to verify System Integrity during System Startup.

The SMR4 System Status must be NOGO during System Startup until the system has reached an Operational State.

Command and Control The SMR4 must process control commands received from the Control Point in control of the radar system.

The SMR4 must reject control commands received from Control Points not in control of the radar system.

Maintenance Terminal The SMR4 must provide a Maintenance Terminal for control AND monitoring of the radar system.

The SMR4 must provide a local Maintenance Terminal workstation co-located with the transceiver equipment.

The SMR4 must allow remote access to all Maintenance Terminal functionality over the Internet Protocol interface with the Surface Surveillance System.

The SMR4 Maintenance Terminal must provide a graphical user interface for controlling system operations.

The SMR4 must obtain secondary verification from the user before performing any command issued from the Maintenance Terminal that alters radar performance.

The SMR4 Maintenance Terminal graphical user interface must provide feedback to the user indicating the success/failure of all commands.

If the SMR4 includes a rotating antenna, the SMR4 Maintenance Terminal graphical user interface must include antenna rotation controls.

The SMR4 Maintenance Terminal graphical user interface must include radio frequency transmit controls.

The SMR4 Maintenance Terminal graphical user interface must include processor reset controls.

The SMR4 Maintenance Terminal graphical user interface must include processor reboot controls.

The SMR4 Maintenance Terminal graphical user interface must include processor shutdown controls.

The SMR4 Maintenance Terminal graphical user interface must include controls to clear system faults.

If the SMR4 includes multiple encoders, the Maintenance Terminal graphical user interface must include encoder selection controls.

If the SMR4 includes Redundant Elements, the Maintenance Terminal graphical user interface must include element selection controls.

The SMR4 Maintenance Terminal graphical user interface must include Antenna Waveguide Switch controls.

External Controls The SMR4 must receive control commands from the Surface Surveillance System in messages formatted in accordance with the EUROCONTROL ASTERIX Category 253 Specification, Edition 11, dated 08 February 2021.

If the SMR4 includes a rotating antenna, the SMR4 must process antenna rotation commands received from the Surface Surveillance System.

The SMR4 must process transmit commands received from the Surface Surveillance System.

The SMR4 must process reset commands received from the Surface Surveillance System.

The SMR4 must process reboot commands received from the Surface Surveillance System.

The SMR4 must process shutdown commands received from the Surface Surveillance System.

The SMR4 must process clear fault commands received from the Surface Surveillance System.

If the SMR4 includes redundant encoders, the SMR4 must process encoder switch commands received from the Surface Surveillance System.

If the SMR4 includes Redundant Element, the SMR4 must process Redundant Element switch commands received from the Surface Surveillance System.

The SMR4 must process Antenna Waveguide Switch commands. received from the Surface Surveillance System.

Command Processing When the SMR4 receives a reset command it must restart the applications running on the specified processor(s).

When the SMR4 receives a reboot command it must reboot the indicated processor(s).

When the SMR4 receives a shutdown command it must shutdown the indicated processor(s).

When the SMR4 receives a clear fault command it must clear all SMR4 subsystem faults.

When the SMR4 receives an encoder switch command it must switch to the indicated encoder.

When the SMR4 receives a Redundant Element switch command it must switch to the indicated Redundant Element.

Closed Regions The SMR4 must receive Closed Region messages from the Surface Surveillance System in messages formatted in accordance with the EUROCONTROL ASTERIX Category 253 Specification, Edition 11, dated 08 February 2021.

The SMR4 must process Closed Region messages received from the Surface Surveillance System.

When the SMR4 receives a Closed Region add command, it must create a target inhibit region using the information contained within the Closed Region message.

The SMR4 must inhibit the dissemination of Target Reports for any target track that falls within any target inhibit region.

The SMR4 must maintain target inhibit regions until a Closed Region delete message is received from the Surface Surveillance System.

When the SMR4 receives a Closed Region delete message, it must delete the target inhibit that matches the region identification in the Closed Region message.

System Monitoring Performance Monitoring The SMR4 must perform real-time automatic system performance monitoring.

The SMR4 Maintenance Terminal graphical user interface must display all system performance monitoring data.

The SMR4 must report system performance monitoring data to the Surface Surveillance System in the Operational Status Reports.

SMR system performance monitoring must include a Transceiver Performance Monitor.

SMR system performance monitoring must include an Antenna Performance Monitor.

SMR system performance monitoring must include a Processor Performance Monitor.

The SMR4 must report the results of all automated system performance tests in the system performance monitoring data.

Status Monitoring The SMR4 must include a System Integrity check to determine System Status.

The SMR4 Maintenance Terminal graphical user interface must display System Status.

The SMR4 must report System Status to the Surface Surveillance System in the Operational Status Report.

The SMR4 must use a monitoring function to determine the status of each Line Replaceable Unit.

The SMR4 Maintenance Terminal graphical user interface must display the Operating Status of Line Replaceable Units.

The SMR4 must use a monitoring function to determine the status of all Redundant Elements.

The SMR4 Maintenance Terminal graphical user interface must display the Operating Status of Redundant Elements.

Fault Detection and Isolation The SMR4 must provide Built-in Test (BIT) functionality that automatically detects failures to the Line Replaceable Unit level.

The SMR4 Built-in Test (BIT) functionality must include checksum monitoring of the system adaptation.

The SMR4 Built-in Test (BIT) functionality must include checksum monitoring of the system software.

If the SMR4 Built-in Test (BIT) detects a checksum mismatch, it must declare a critical fault.

The SMR4 Maintenance Terminal graphical user interface must display the Operational Health of Line Replaceable Units as determined by the Built-In Test functionality.

The SMR4 must implement Fault Isolation Test (FIT) functionality to isolate faults detected by Built-In Test to the Line Replaceable Unit level.

The SMR4 Maintenance Terminal graphical user interface must display results of Fault Isolation Tests.

The SMR4 Maintenance Terminal graphical user interface must display System Fault Data.

Failover If the SMR4 includes Redundant Elements, it must automatically failover to the standby element when a failure is detected in the online element.

If an SMR4 failover causes clutter processes to restart, the System Status must be NOGO until the system has reached an Operational State.

If the SMR4 allows multiple failovers without a maintenance action, it must include site adaptable failover limits.

SMR4 site adaptable failover limits must be specified as an adaptable number of failovers allowed within an adaptable time.

SMR4 site adaptable failover limits must allow for a minimum of one failover.

Data Logging The SMR4 must automatically record System Status changes to a system status log.

The SMR4 must retain recorded System Status data in the system status log for a minimum of 45 days.

The SMR4 must automatically record System Fault Data to a system fault log.

The SMR4 must retain recorded System Fault Data in the system fault log for a minimum of 45 days.

The SMR4 log files must include a date for every record corresponding to the date of declaration of the event.

The SMR4 log files must include a Coordinated Universal Time (UTC) timestamp for every record corresponding to the time of declaration of the event.

The SMR4 must include a timestamp in all messages using Coordinated Universal Time (UTC).

The SMR4 must include a timestamp in all recorded data using Coordinated Universal Time. (UTC) Antenna and Transmitter Controls Antenna Interlocks The SMR4 must include Antenna Subsystem interlocks for the safety of maintenance personnel.

The SMR4 must include a key interlock.

The SMR4 key interlock must activate when it is removed from its mounting location.

The SMR4 key interlock must remain active until the key is restored to its mounting location.

The SMR4 must include a hatch interlock.

The SMR4 hatch interlock must activate when the tower hatch is opened.

The SMR4 hatch interlock must remain active until the tower hatch is secured.

If the SMR4 includes a rotating antenna, the SMR4 must include a stow pin that can be used to mechanically prevent antenna rotation.

If the SMR4 includes a rotating antenna, the SMR4 must include a stow pin interlock.

If the SMR4 includes a rotating antenna, the SMR4 stow pin interlock must activate when the stow pin is in use.

If the SMR4 includes a rotating antenna, the SMR4 stow pin interlock must remain active while the stow pin is in use.

Antenna Rotation The SMR4 must automatically disable antenna rotation when the Antenna Performance Monitor detects conditions that may damage the Antenna Subsystem.

SMR4 antenna rotation must be disabled upon detection of any activated Antenna Subsystem interlock.

SMR4 antenna rotation must be inhibited while there is an active Antenna Subsystem interlock.

When the SMR4 antenna has been disabled, antenna rotation must remain disabled until a start rotation command is manually initiated.

When the SMR4 receives a start antenna rotation command it must initiate antenna rotation unless rotation is inhibited.

When the SMR4 receives a stop antenna rotation command it must disable antenna rotation.

Transmitter The SMR4 must automatically stop radio frequency transmissions through the antenna whenever the antenna rotation is disabled.

SMR4 radio frequency transmissions must be inhibited while there is an active Antenna Subsystem interlock.

When the SMR4 transmitter is disabled, it must remain disabled until a transmit start command is manually initiated.

When the SMR4 receives a transmit start command, it must start radiating transmit pulse(s) unless transmission is inhibited.

When the SMR4 receives a transmit stop command, it must disable radio frequency transmissions.

When the SMR4 receives an Antenna Waveguide Switch command it must switch the transceiver to the dummy load or antenna as specified in the command.

System Configuration and Utilities Optimization, Verification and Certification The SMR4 must provide all system software necessary to support in-the-field optimization of the radar system.

The SMR4 must provide all system software necessary to support Performance Verification of the radar system.

The SMR4 must provide all physical test points necessary to support System Certification of the radar system.

The SMR4 must provide all system software necessary to support System Certification of the radar system.

The SMR4 must include a directional coupler installed in line with the waveguide to support manual radio frequency measurements at the transceiver.

The SMR4 directional coupler must permit the user to measure transceiver forward power output to the Antenna Subsystem.

The SMR4 directional coupler must permit the user to measure the reflected power at the transceiver from the Antenna Subsystem.

The SMR4 must include a dummy load capable of withstanding the full radiating power of the transmitter.

The SMR4 must include an Antenna Waveguide Switch.

The SMR4 operational status report must include status of the Antenna Waveguide Switch position as either antenna OR dummy load.

The SMR4 Maintenance Terminal graphical user interface must indicate the position of the Antenna Waveguide Switch.

Adaptation The SMR4 must provide Adaptable Parameters that allow an installed system to be optimized to meet Performance Requirements specified in Section 3.2 while accounting for site specific conditions.

The SMR4 must store a digital copy of all Adaptable Parameters on an internal local storage drive in one or more site adaptation files.

The SMR4 must provide the capability to transfer all site adaptation files between the SMR4 and an external source over the Internet Protocol interface with the Surface Surveillance System.

The SMR4 must be adaptable to operate in a multiple Surface Movement Radar environment consisting of up to four radars operating within the same frequency band.

If the SMR4 design includes Sensitivity Time Control (STC), Sensitivity Time Control functionality must be site configurable.

If the SMR4 design supports multiple Pulse Repetition Frequencies, selection of the operating Pulse Repetition Frequency must be site configurable.

Adaptation Editor The SMR4 Maintenance Terminal must include an adaptation editor.

The SMR4 adaptation editor must provide a graphical user interface for viewing all Global Parameters.

The SMR4 adaptation editor must provide a graphical user interface for modifying all Global Parameters.

The SMR4 adaptation editor must permit the user to load the adaptation currently being utilized by the system.

The SMR4 adaptation editor must permit the user to overwrite the adaptation currently being utilized by the system.

The SMR4 adaptation editor must permit the user to save its current loaded adaptation to a local file.

The SMR4 adaptation editor must permit the user to load a local adaptation file.

Before overwriting any adaption in use by the system, the SMR4 adaptation editor must Adaptation Validation of the adaptation being loaded.

Map Editing Utility The SMR4 must include a map editing utility permitting the user to define AND modify all processing map regions.

The SMR4 must include a map editing utility permitting the user to define AND modify all processing map parameters.

The SMR4 map editing utility must permit the user to display airport maps as an overlay with the selected processing map(s).

The SMR4 map editing utility must permit the user to save local copies of the processing maps.

The SMR4 map editing utility must permit the user to load local copies of the processing maps.

The SMR4 map editing utility must permit the user to upload processing maps to the system.

The SMR4 map editing utility must permit the user to download processing maps from the system.

Data Utilities Recording The SMR4 must include a Recording Utility.

The SMR4 Recording Utility must permit the user to record all data and information necessary to support optimization AND verification of the radar performance.

The SMR4 Maintenance Terminal must provide a graphical user interface for user control of the Recording Utility.

The SMR4 Recording Utility must permit the user to start a recording.

The SMR4 Recording Utility must permit the user to stop an active recording.

The SMR4 Recording Utility must permit the user to specify the base file name of a data recording.

The SMR4 Recording Utility must permit the user to specify the total time duration for a data recording.

The SMR4 Recording Utility must permit the user to specify the time duration for each data recording segment.

Upon a data recording segment reaching the user specified maximum time duration, the SMR4 Recording Utility must continue the recording in a new file using the base file name appended with a sequence number.

The SMR4 Recording Utility must permit the user to select the Recorded Data Types to record.

The SMR4 Recording Utility must write all recorded files to an internal local storage drive.

The SMR4 must have enough internal local drive space capacity to store up to 15 days of continuously recorded data files, including all Recorded Data Types except for Raw Video.

The SMR4 Recording Utility must allow the user to record to an external storage device.

The SMR4 Recording Utility must prevent data recording files from exceeding 90 percent of the maximum disk space capacity.

Except for Raw Video, the SMR4 data recordings must include a Coordinated Universal Time (UTC) timestamp for every record corresponding to the time of occurrence.

The SMR4 must permit the user to download all recorded data files to an external location.

Reprocessing The SMR4 must include a Reprocessing Utility.

The SMR4 Reprocessing Utility must permit the user to reprocess all data and information necessary to support optimization AND verification of the radar performance.

The SMR4 Maintenance Terminal must provide a graphical user interface for user control of the Reprocessing Utility.

The SMR4 Reprocessing Utility must permit the user to select the data type to reprocess.

The SMR4 Reprocessing Utility must permit the user to start a reprocessing session beginning at any stage of the radar processing supported by the recorded data.

The SMR4 Reprocessing Utility must permit the user to end a reprocessing session.

The SMR4 Reprocessing Utility must allow reprocessing of recorded data throughout the Coverage Volume.

The SMR4 Reprocessing Utility must allow reprocessing of recorded data using modified site adaptation.

When the SMR4 is reprocessing data, the Operational Status Report must include an indication that Target Reports are from reprocessed data.

The SMR4 Recording Utility must be functional while the Reprocessing Utility is reprocessing recorded data.

Data Viewer The SMR4 Maintenance Terminal must include a graphical surveillance display showing Surveillance Data within the Coverage Volume The SMR4 surveillance display must permit the user to view live Surveillance Data in real-time.

The SMR4 surveillance display must permit the user to view reprocessed Surveillance Data in real-time.

The SMR4 surveillance display must permit the user to view recorded Surveillance Data.

The SMR4 surveillance display must permit the user to control local playback of recorded Surveillance Data.

The SMR4 surveillance display must permit the user to display airport maps as an overlay with the Surveillance Data being viewed.

The SMR4 surveillance display must permit the user to display processing maps as an overlay with the Surveillance Data being viewed.

The SMR4 surveillance display must permit the user to zoom the view window.

The SMR4 surveillance display must permit the user to pan the view window The SMR4 surveillance display must include cursor feedback that identifies the location of cursor on the map in range AND azimuth.

When viewing Raw Video, the SMR4 cursor feedback must include the amplitude of the Radar Cell relative to the cursor.

Operating System The operating system on all SMR4 data processors must be RedHat Linux 9 OR later.

Optional Heated Array At FAA designated sites, the SMR4 must include a heated antenna array to prevent ice buildup.

When installed with a heated array, the SMR4 must automatically enable the array heaters when outside air temperatures at the array are between adaptable thresholds.

When installed with a heated array, the SMR4 must automatically disable the array heaters when outside air temperatures at the array are outside of adaptable thresholds.

When installed with a heated array, the SMR4 Maintenance Terminal graphical user interface must indicate when the array heater is enabled.

When installed with a heated array, the SMR4 Maintenance Terminal graphical user interface must include manual array heater controls.

When installed with a heated array, the SMR4 must process manual array heater control commands received from the Surface Surveillance System.

When the SMR4 receives a manual array heater command, it must enable OR disable the array heater as specified in the command When installed with a heated array, the SMR4 array heater manual controls must override the automatic temperature sensor controls.

The SMR4 must meet all Performance Requirements in Section 3.2 when installed with a heated array.

Performance Requirements Coverage Volume Surface Surveillance Coverage Volume The SMR4 must provide surface surveillance coverage at slant ranges from 500 feet to 14,000 feet.

The SMR4 must provide surface surveillance coverage from ground level to at least 200 feet above ground level for tower heights from 75 to 400 feet.

The SMR4 must provide surface surveillance coverage in all azimuths.

Extended Surveillance Coverage Volume The SMR4 must provide extended surveillance coverage at slant ranges from 14,000 feet to 18,000 feet.

The SMR4 must provide extended surveillance coverage from ground level to at least 200 feet above ground level for tower heights from 75 to 400 feet.

The SMR4 must provide extended surveillance coverage in all azimuths.

Target Detections The SMR4 Probability of Detection in clear weather conditions must be greater than or equal to 95 percent for all Targets having a radar cross section greater than or equal to 1 m2 at any location on the Airport Movement Area within the Surface Surveillance Coverage Volume, specified in Section 3.2.1.1.

The SMR4 Probability of Detection during weather conditions with Atmospheric Moisture between the radar and the target resulting in radio frequency losses less than or equal to those associated with rainfall rates of 16 mm per hour must be greater than or equal to 90 percent for all Targets having a radar cross section greater than or equal to 1 m2 at any location on the Airport Movement Area within the Surface Surveillance Coverage Volume, specified in Section 3.2.1.1.

The SMR4 Probability of Detection requirements must be met for all operating Pulse Repetition Frequencies (PRFs) of the radar.

Resolution The SMR4 must resolve, through extraction of separate Plots, two 3 m2 radar cross section targets located at the same azimuth and separated in slant range by 40 feet, throughout the Coverage Volume specified in Section 3.2.1, at least 90 percent of the time The SMR4 must resolve, through extraction of separate Plots, two 3 m2 radar cross section targets located at the same range and separated by 70 feet in azimuth at a slant range of 7,000 feet at least 90 percent of the time.

The SMR4 must resolve, through extraction of separate Plots, any two targets of 30 dB or less differential radar cross section, when separated by 85 feet in azimuth, at a slant range of 7,000 feet where the smaller of the two targets is 3 m2 radar cross section, at least 90 percent of the time.

Accuracy The SMR4 accuracy relative to ground truth must be within ±25 feet for the 95th percentile at any location on the Airport Movement Area within the Surface Surveillance Coverage Volume specified in Section 3.2.1.1.

Target Dynamics The SMR4 must provide surveillance coverage for all Targets with a radar cross section of a 1 m2 or larger with velocities less than or equal to 210 knots.

The SMR4 must detect target movements of 20 feet or greater at slant ranges less than or equal to 7,000 feet.

The SMR4 must detect target movements beyond 7,000 feet in accordance with the movement sensitivity out to 7,000 feet AND the 3 dB azimuth beamwidth of the Antenna.

Scan and Update Rate The SMR4 must perform an entire scan of the Coverage Volume specified in Section 3.2.1 once per second nominal, within a tolerance of ±0.1 second.

The SMR4 must provide Target Reports for all Targets at a rate of once per second nominal, within a tolerance of ±0.1 second False Tracks Within the Runway Safety Area, the SMR4 Split Track rate must be less than or equal to five per 12-hour period.

Within the Runway Safety Area, the SMR4 False Track rate due to Static Clutter must be less than or equal to one per 12-hour period.

Within the Runway Safety Area, the SMR4 False Track rate due to Multiple Time Around Returns must be less than or equal to one per 12-hour period.

Within the Runway Safety Area, the SMR4 False Track rate due to Range Side Lobes must be less than or equal to one per 12-hour period.

Target Capacity The SMR4 target loading capacity must be greater than or equal to 200 Targets located anywhere within the Surface Surveillance Coverage Volume specified in Section 3.2.1, over a full 360-degree scan.

The SMR4 target loading capacity must be greater than or equal to 100 Targets concentrated within a 45-degree wedge of the Surface Surveillance Coverage Volume specified in Section 3.2.1.

The SMR4 must process new targets at a peak rate of 20 per second.

The SMR4 must utilize less than or equal to 50 percent of Central Processing Unit (CPU) resources under the maximum target loading capacity while performing all other…