Standard Terminal Automation Replacement System (STARS)

System Specification Document (SSD)

FAA-E-2904

Revision F

19th November, 2021

Focal Point Lisa Bercher

Organization: AJM-211

Federal Aviation Administration 800 Independence Avenue SW

Washington, DC 20591

STARS FAA-E-2904 Rev F

November 2021 Page ii

Revision Record Revision Letter

Description Date

Original Initial Issue 02/28/96 SCN-1 Changes requirements to implement interfaces between STARS and ESC-1 improvements (pFAST, PRM, SMA, NA, TCP-defined airspace, Free-form text, ASTERIX and the pFAST Functional Specification)

02/16/99

A Incorporates approved contractual and design requirements changes through January 31, 2000

12/13/01

B In accordance with FAA-STD-067 and direction from the JRC, this entire document has been changed and updated.

10/4/16

C Incorporates approved contractual and design requirements changes through January 31, 2017 in conjunction with the latest SSS Rev Y

7/26/17

D De-Clutter this document by scaling back on the detail and repetition of requirements.

10/01/18

E Incorporates requirement changes to support the software changes related to R8/R9/R10, and TSAS color changes. This revision also includes traceability to the STARS fPRD. Updated FAA Specification references (fPRD and ICDs)

7/31/20

F Incorporates requirement changes in support of the Dismounted TCW, software changes related to R1A, and the new TDM contrast ratio, brightness, and power switch location. Updated referenced standards.

11/19/21

November 2021 Page iii

SIGNATURE PAGE

SSD Approved by:

Lisa Bercher

TAMR Program Manager, AJM-2110 Signature Date

SSD Submitted by:

Lisa Cacciatore

TAMR Systems Engineering Program Manager, AJM-2113 Signature Date

November 2021 Page iv

TABLE OF CONTENTS

1 Introduction 1

1.1 BACKGROUND

1.2 SCOPE

1.3 PURPOSE

1.4 IDENTIFICATION

1.5 SPONSORSHIP

1.6 SYSTEM ARCHITECTURE

2 Reference Documents

2.1 FAA SPECIFICATIONS

2.2 FAA PUBLICATIONS

2.3 FAA ORDERS

2.4 MILITARY STANDARDS

2.5 FEDERAL STANDARDS

2.6 FEDERAL PUBLICATIONS

2.7 INDUSTRY STANDARDS

2.8 OTHER DOCUMENTS

3 STARS Requirements

3.1 STARS STATES, SERVICE LEVELS AND MODES

3.1.1 Operational Sites

3.1.1.1 States and Recovery

3.1.1.1.1 Resource States

3.1.1.1.2 Recovery

3.1.1.2 Service Levels

3.1.1.2.1 Concurrent Operation

3.1.1.2.2 Full Service Level (FSL)

3.1.1.2.3 Emergency Service Level (ESL)

3.1.1.2.4 Emergency Full Service Level (EFSL)

3.1.1.2.5 Site Support Service Level (SSSL)

3.1.1.2.6 Service Level Independence

3.1.1.2.7 Service Level Interdependence

3.1.1.3 Modes

3.1.1.3.1 Full Service (FS) Workstation Mode

3.1.1.3.2 Emergency Service (ES) Workstation Mode

3.1.1.3.3 FS Training Workstation Mode

3.1.1.3.4 ES Training Workstation Mode

3.1.1.3.5 FS Performance Verification Workstation Mode

3.1.1.3.6 ES Performance Verification Workstation Mode

3.1.1.3.7 MCP Workstation Mode

3.1.1.3.8 MCP Views

3.1.1.3.9 Service Level Modes

3.1.1.3.10 Direct Sensor Access (DSA) Mode

3.1.1.3.11 Direct Sensor Feed (DSF)

3.1.2 Support Sites (OSF, SCSC)

3.1.3 STARS LITE

3.2 STARS CAPABILITIES

3.2.1 Operational Sites

3.2.1.1 Full Service

3.2.1.1.1 ATC Surveillance

3.2.1.1.2 ATC Tracking

3.2.1.1.3 ATC Conflict Alert (CA) / Mode-C Intruder (MCI)

3.2.1.1.4 ATC Final Monitor Aid

3.2.1.1.5 ATC Minimum Safe Altitude Warning (MSAW)

3.2.1.1.6 ATC Converging Runway Display Aid (CRDA)

3.2.1.1.7 ATC Controller Automated Spacing Aid (CASA)

3.2.1.1.8 ATC Flight Data Processing

3.2.1.1.9 En Route and TFMS Interfaces

November 2021 Page v

3.2.1.1.10 TCP Data Entry

3.2.1.1.11 TCP Data Display

3.2.1.1.12 Status Monitoring

3.2.1.1.13 Performance Monitoring

3.2.1.1.14 System Control

3.2.1.1.15 FSL Verification

3.2.1.1.16 Data Recording

3.2.1.1.17 TCW/TDW Replay

3.2.1.1.18 Full Service Security

3.2.1.1.19 Independent Time Source

3.2.1.1.20 MCP Data Entry

3.2.1.1.21 MCP Data Display

3.2.1.1.22 Application Interface Gateway

3.2.1.1.23 FS Performance

3.2.1.2 Emergency Service

3.2.1.2.1 ATC Surveillance

3.2.1.2.2 TCP Data Entry

3.2.1.2.3 TCP Data Display

3.2.1.2.4 Status Monitoring

3.2.1.2.5 System Control

3.2.1.2.6 ESL Subsystem Verification

3.2.1.2.7 ESL Time Source

3.2.1.2.8 MCP Data Entry

3.2.1.2.9 MCP Data Display

3.2.1.2.10 ES Performance

3.2.1.2.11 Emergency Service Security

3.2.1.3 Operational Site Support Subsystem

3.2.1.3.1 Interfacility Test Function

3.2.1.3.2 Simulation

3.2.1.3.3 Data Reduction and Analysis (DR&A) Data Class Extraction

3.2.1.3.4 On-Site Maintenance

3.2.1.3.5 Independent Time Source

3.2.1.3.6 Operational Site Support Performance

3.2.2 SCSC & OSF Support Systems

3.2.2.1 SCSC & OSF Location

3.2.2.2 SCSC & OSF Maintenance Configurations

3.2.2.3 Software Storage

3.2.2.4 File Format

3.2.2.5 SCSC SDC

3.2.2.6 SCSC FSC

3.2.2.7 OSF SMC

3.2.2.8 OSF STC

3.2.2.13 SCSC and OSF System Security

3.2.2.16 SCSC and OSF System Performance

3.3 STARS EXTERNAL INTERFACES

3.3.1 External Interface Standards

3.3.2 Operational Site Interfaces

3.3.2.1 Interface Diagram

3.3.2.2 Digital Surveillance Systems Interface

3.3.2.3 Number of Terminal/En Route Interfacility Interfaces

3.3.2.4 Terminal/En Route Interfacility Interface Characteristics

3.3.2.6 TFMS Interface Characteristics

3.3.2.7 Tower Interface

3.3.2.8 Remote Display Interface

3.3.2.10 External Applications Interfaces

3.4 STARS INTERNAL INTERFACES

3.5 ADAPTATION

3.6 SAFETY

3.6.1 Personnel Safety

3.6.2 Hazardous Materials

3.6.3 Physical Safety

November 2021 Page vi

3.6.4 Electrical Safety

3.6.5 Cabling and Connections

3.6.6 National Electrical Code Adherence

3.6.7 Fire Resistance

3.7 SECURITY AND PRIVACY

3.7.1 General Security Requirements

3.8 SYSTEM ENVIRONMENT

3.9 COMPUTER RESOURCES

3.10 SYSTEM QUALITY FACTORS

3.11 DESIGN AND CONSTRUCTION CONSTRAINTS

3.11.1 Architectural

3.11.2 Hardware

3.11.2.1 Connectivity and Characteristics

3.11.2.2 Keyboard Characteristics

3.11.2.3 Mouse/Trackball Characteristics

3.11.2.4 Special Tools

3.11.2.5 Terminal Controller Workstation (TCW)

3.11.2.6 TCW/TDW DCP Characteristics

3.11.2.7 TCW/TDW Characteristics

3.11.2.8 Monitor and Control Workstation (MCW)

3.11.2.9 Tower Display Workstation (TDW)

3.11.2.10 Tower Display Monitor (TDM) Characteristics

3.11.2.11 Supplemental Display

3.11.2.12 TDW Distance Limitations

3.11.2.13 Miscellaneous Hardware

3.11.3 Software

3.11.4 Firmware

3.11.5 Electrical

3.11.6 Mechanical

3.12 COMPUTER HUMAN INTERFACE (CHI)

3.12.1 General CHI

3.13 ADDITIONAL

3.13.1 Preplanned Product Improvement (P3I)

3.13.1.1 Interfaces

3.13.1.2 Specific P3I Capability Upgrades

3.13.1.2.1 Surveillance System Enhancements

3.13.1.2.2 Integrated Terminal Weather System (ITWS)

3.13.1.2.3 ASR-9 Wind Shear Processor

3.13.1.2.4 Terminal Doppler Weather Radar (TDWR)

3.13.1.2.5 Data Link Communications

3.13.1.2.6 CA and MCI Alert Enhancements

3.13.1.2.7 Traffic Management Enhancements

3.13.1.2.8 Supplemental Flight Data Processing (FDP)

3.13.1.2.9 TCP-Defined Airspace

3.13.1.2.10 FSL TCP Display Data Fields

4 Qualification Provisions

4.1 QUALITY ASSURANCE

4.1.1 ISO Standards

4.1.2 Completeness

4.1.3 Detection of Deficiencies

4.2 TEST PROGRAM

4.2.1 Test Strategy

4.2.2 Traceability

4.2.3 Test Conduct

4.2.3.1 Success Criteria

4.2.3.2 Pass/Fail

4.2.3.3 Pass/Fail Criteria

4.2.3.4 Test Completeness

4.2.3.5 Test Repeatability

November 2021 Page vii

4.2.3.6 Discrepancies

4.2.4 Test Methods

4.2.4.1 Applicability

4.2.4.2 Inspection

4.2.4.3 Analysis

4.2.4.4 Demonstration

4.2.4.5 Test

4.2.4.6 Review

4.2.5 Program Technical Reports (PTR)

4.2.5.1 PTR Objective

4.2.5.2 PTR Classifications

4.2.5.2.1 Type I

4.2.5.2.2 Type II

4.2.5.2.3 Type III

4.2.5.2.4 Type IV

4.3 TEST REQUIREMENTS

4.3.1 Applicability

4.3.2 Installation and Integration

4.3.2.1 Installation

4.3.2.2 Installation Tests

4.3.2.3 Integration Testing

4.3.3 Scenarios

4.3.3.1 Test Scenario

4.3.3.2 Background Scenario

4.3.3.2.1 Purpose

4.3.3.2.2 Characteristics

4.3.3.3 Maximum Stress Workload Scenario

4.3.3.3.1 Purpose

4.3.3.3.2 Workload Scenario Length

4.3.3.3.3 Concurrent Workload

4.3.3.3.4 Steady-State Period

4.3.3.3.5 TCW Workload

4.3.3.3.6 Distributed Load

4.3.3.3.7 System Configuration

4.3.4 Development Test and Evaluation (DT&E)

4.3.4.1 DT&E Components

4.3.4.2 FAA Technical Center Installation and Integration

4.3.4.3 Non-Operational Test

4.3.4.3.1 Purpose

4.3.4.3.2 Safety

4.3.4.3.3 System Environment

4.3.4.3.4 Reliability

4.3.4.3.5 Maintainability

4.3.4.3.6 Design and Construction

4.3.4.4 FAA Technical Center System Acceptance Test

4.3.4.4.1 General Test Conditions

4.3.4.4.2 Functional Tests

4.3.4.4.3 Site Adaptation

4.3.4.4.4 Computer Resource Utilization

4.3.4.4.5 System Enhancement

4.3.4.4.6 Scalability

4.3.4.4.7 Performance Tests

4.3.4.4.8 Interfaces

4.3.4.4.9 Confidence and Stability Tests

4.3.4.4.10 Support Tools

4.3.4.4.11 System Internal Interfaces

4.3.4.5 Key Site System Acceptance Test

4.3.4.5.1 Purpose

4.3.4.5.2 Installation and Integration

4.3.4.5.3 Test Conditions

4.3.4.5.4 Functional Tests

November 2021 Page viii

4.3.4.5.5 Key Site Adaptation

4.3.4.5.6 Workload

4.3.4.5.7 Confidence and Stability

4.3.4.5.8 Verification Tests

4.3.5 Contractor Acceptance Test and Evaluation (CAT&E)

4.3.5.1 Scope

4.3.5.2 Site Installation and Integration

4.3.5.3 Use of Adaptation Data

4.3.5.4 Site System Acceptance Tests

4.3.5.4.1 Scope

4.3.5.4.2 Functional Tests

4.3.5.4.3 Workload

4.3.5.4.4 Confidence and Stability

4.3.5.5 Performance Verification

4.4 REQUIREMENTS TRACEABILITY MATRIX

5 Requirements Traceability 6 Notes 312

6.1 ACRONYMS AND ABBREVIATIONS

6.2 DEFINITIONS

6.3 TRACEABILITY MATRIX

November 2021 Page ix

LIST OF FIGURES

1-1 3-1

3-2

3.2.1.1.4-1 3.3.2.6-1 3.11.2.2-1 3.11.2.2-2 3.11.2.2-3 3.11.2.5-1 3.11.2.6-1 3.11.2.6-2 3.11.2.6-3 3.12.7-1

STARS System Architecture STARS Operational Site Service Levels and Modes of Operation – dual FSL System Configuration STARS Operational Site Service Levels and Modes of Operation – G1 or G2 System Configuration AMZ with Three Parallel Runways Operational Site External Interfaces Keyboard Menu Key Labels Color of Key Caps and Marking QWERTY Keyboard Layout

STARS TCW

TCW Display Control Panels Backlit Panel TDW DCP Configuration Options Target Symbol Illustration

November 2021 Page x

LIST OF TABLES

3-1 Summary of Required Operational Site Modes 15 3.2.1.1.7-1 3.2.1.1.7-2 3.2.1.1.9-1 3.2.1.1.9-2 3.2.1.1.10-1 3.2.1.1.23-1 3.2.1.1.23-2 3.2.1.1.23-3 3.2.1.1.23-3A 3.2.1.1.23-4 3.2.1.1.23-5 3.2.1.1.23-6 3.2.1.1.23-7 3.2.1.1.23-7A 3.2.1.1.23-8 3.2.1.1.23-8A 3.2.1.1.23-9 3.2.1.1.23-10 3.2.1.1.23-11 3.2.1.1.23-11A 3.2.1.1.23-11B 3.2.1.1.23-12 3.2.1.1.23-13 3.2.1.1.23-14 3.2.1.1.23-15 3.2.1.1.23-16 3.2.1.1.23-17 3.2.1.1.23-18 3.2.1.1.23-19 3.2.1.1.23-20 3.2.1.1.23-21 3.2.1.1.23-22 3.2.1.1.23-23

Weight Class (from light to heavy) IFR Separation Categories An In-Out-In Series May Consist of:

Amendment Message Processing Example with 1N as the sending position and 1F as the receiving TCP FS System Workload, Sources and Destinations of Data FS System Workload, Airspace Definition FS System Workload, System Data Capacity STARS LITE System Workload, System Data Capacity FS System Workload, Input Message Rates FS System Workload, Output Message Rates FS System Workload, Single Sensor Peak Target Rates FS Individual Data Display Workload STARS LITE Individual Data Display Workload FS Simultaneous Data Display Workload STARS LITE Simultaneous Data Display Workload Long and Short Range Surveillance Sensor Characteristics Aircraft Motion Characteristics Track Loss Probability, Short Range Radar Inputs Track Loss Probability, Multilateration Inputs Target Acceleration, Multilateration Inputs Track Swap Probability, Short Range Radar Inputs Steady State Position Accuracy, Short Range Radar Inputs Steady State Position Accuracy, Long Range Radar Inputs Steady State Speed Stability, Short Range Radar Inputs Transient Speed Stability, Short Range Radar Inputs Steady State Speed Accuracy, Short and Long Range Radar Inputs Steady State Heading Accuracy, Short and Long Range Radar Inputs Transient Track Position, Speed and Heading Accuracy, Short Range Radar Inputs Time to Establish Steady-State Tracking, Short Range Radar Inputs Altitude Tracker Conflict Alert Rate of Detection Requirements Minimum Safe Altitude Warning Rate of Detection Requirements

3.2.1.2.10-1 3.2.1.2.10-2 3.2.1.2.10-3 3.2.1.2.10-4 3.2.1.2.10-5 3.2.1.2.10-6 3.2.1.2.10-7 3.2.1.2.10-8 3.2.1.3.3-1 3.3.2.2.7-1 3.3.2.2.7-2 3.3.2.2.7-3 3.3.2.2.7-4 3.3.2.2.7-5 3.3.2.2.7-6 3.3.2.2.7-7 3.3.2.2.7-8 3.3.2.2.7-9 3.3.2.2.7-10

ES System Workload, Sources and Destinations of Data ES System Workload, Airspace Definition ES System Workload, Input Message Rates ES System Workload, Additional Input Message Rates ES System Workload, Output Message Rates ES System Workload, Single Sensor Peak Target Rates ES Individual Data Display Workload ES Simultaneous Data Display Workload Plot File Interface Characteristics Departure Flight Plan (Format 1) Departure Flight Plan (Format 2) Arrival Flight Plan (Format 1) Arrival Flight Plan (Format 2) Overflight Flight Plan (Format 1) Overflight Flight Plan (Format 2) Delete Flight Plan Modify Aircraft ID in Flight Plan Modify Time in Flight Plan

November 2021 Page xi

3.3.2.2.7-11 3.3.2.2.7-12 3.3.2.2.7-13 3.3.2.2.7-14 3.3.2.2.7-15 3.3.2.2.7-16 3.3.2.2.7-17 3.3.2.2.7-18 3.12.6-1 3.12.6-2 3.12.6-3 3.12.7-1 3.12.7-2 3.12.7-3 3.12.7-4 3.12.7-5 3.12.7-6 3.12.7-7

Modify Aircraft Type in Flight Plan Modify Beacon Code in Flight Plan Generic Flight Plan Update Processing Logic for Supplementary Data in FDIO Message Flight Plan Aircraft ID Field Supplementary Modification Flight Plan Time Field Supplementary Modification Flight Plan Aircraft Type Field Supplementary Modification Flight Plan Beacon Code Field Supplementary Modification Range Increments FS Brightness Ranges ES Brightness Ranges Target Extent Symbol Adaptation Parameters Processing Logic for Computation of Track Positional Uncertainty Value Default Slant Range Values – Maximum Standard (Terminal) Separation Default Eligibility/Loss-of-Eligibility Intervals Processing Logic for Fused-Track Symbol Display Colors Color Coordinates

1 Introduction

1.1 Background

The terminal automation system forms the critical backbone of the Air Traffic Control (ATC) information network for the airports in the NAS. Terminal Air Traffic (AT) approach control and automation is achieved primarily through the use of STARS. The STARS hardware and software platform is adaptable to a wide range of traffic sizes within terminal domains, and via the TAMR Program Office, replaced the older automation platforms at facilities that previously utilized either Common Automated Radar Terminal Systems (CARTS) IIIE, Automated Radar Terminal Systems (ARTS) IIE or ARTS IE technology.

1.2 Scope

The STARS product line consists of several variants that, while operating the same baseline software and having the same system functionality, supports multiple hardware platforms. These variants include the baseline STARS system, referred to as Full STARS and STARS ELITE (Enhanced Local Integrated Tower Equipment). Full STARS consists of a redundant suite of hardware referred to as FSL (Full Service Level) along with an identical redundant suite for back-up purposes referred to as E-FSL (Emergency- Full Service Level). STARS ELITE consists of a redundant suite of hardware similar to Full STARS with a reduced footprint for smaller facilities.

This document establishes the performance and design requirements for the STARS system.

Though there are several STARS system variants, the functional characteristics are unified across all variants. In this light, the requirements refer simply to “the system” and imply all of the STARS variants. This document includes the requirements for terminal surveillance data processing, flight data processing, internal and external interfaces, system monitoring and control, system support, human factors, security, design and construction, transition, and system performance characteristics and capabilities.

1.3 Purpose

This document provides the technical, performance, operational, and support characteristics for the STARS system. This includes the requirements for surveillance data processing, target tracking, flight data processing, computer human interfaces, safety alerts, external system interfaces, monitor and control, system security, system support, design and construction, and system performance characteristics and capabilities.

1.4 Identification

STARS provides to the controller appropriately scaled information about the location, identification and tracking of aircraft within terminal airspace. It supports Terminal Radar Approach Control (TRACON) controllers responsible for managing aircraft within terminal airspace and Air Traffic Control Tower (ATCT) controllers responsible for managing aircraft arriving and departing an airport. It supports system maintenance personnel in the detection, isolation and repair of hardware and software failures. It supports on-site training for both TRACON and ATCT controllers.

November 2021 Page 2

1.5 Sponsorship

The STARS procurement activity is administered by the FAA. The STARS procurement activity is sponsored jointly by the FAA and the DoD. The automation system resulting from the procurement activity is intended for use by FAA-authorized and DoD-authorized organizations and personnel. FAA-authorized and DoD-authorized users will include personnel engaged in civil, commercial and military air traffic control operations, air traffic management, system maintenance and monitoring, user training, and system test and upgrade.

1.6 System Architecture

Figure 1-1 depicts a top-level view of the system architecture used as a model to develop the requirements contained in this specification. This architecture portrays all major subsystems and external interfaces supporting national deployment.

In the context of this document, the terms local and co-located refer to equipment that is connected to the Local Area Network (LAN) of a TAMR facility, while the term remote refers to equipment that is connected via FAA Telecommunications Infrastructure (FTI) to a TAMR facility.

STARS implements two fundamental user displays – Monitor and Control Position (MCP) and Terminal Control Position (TCP). The MCP is the display that provides maintenance personnel the functionality to monitor and control the system. All system status, health, and error messages are displayed at the MCP. The TCP is the display that enables air traffic controllers to provide service to aircraft in the terminal environment. The primary function of the TCP is to display situational awareness information that has been collected by surveillance sensors and tracked by the system.

The STARS system supports a two way interface with a single NAS En Route Automation System to transmit and receive flight and control data. It supports a receive only interface with Digital Altimeter Setting Indicator (DASI), Airport Surveillance Radars (ASR), Air Route Surveillance Radars (ARSR), as well as, Automatic Dependent Surveillance Broadcast (ADS-B) and Multilateration (MLAT) surveillance sources.

STARS interfaces to a standard time source system to obtain a time reference that is consistent and accurate. The standard time data is used to ensure synchronization of data within and between nationally deployed systems and to “time-stamp” all recorded data.

The STARS system provides interfaces to various external NAS clients such as, Airport Surface Detection Equipment Model X (ASDE-X) and Precision Runway Monitor (PRM) for the purpose of providing flight and tracking data.

The STARS system provides a backup sensor capability through either Direct Sensor Feed (DSF) or Direct Sensor Access (DSA) connections. DSF connections are applicable to remote ATCT facilities, while DSA connections are appropriate for TRACONS and local ATCT facilities under the STARS ELITE configuration.

The STARS Central Support Complex (SCSC) manages and provides the ability to update software, adaptation, and system documentation. The SCSC will be capable of compiling, maintaining and performing Configuration Management of system software. The SCSC will be

November 2021 Page 3 capable of developing, verifying and performing Configuration Management of the site adaptation for each Operation Support Facility (OSF) and to support various testing efforts.

The OSF subsystems are logically part of the SCSC, but are located at sites physically removed from the SCSC. The OSF subsystems will be used to perform site adaptation and site support.

November 2021 Page 4

2 Reference Documents If a requirement within this document conflicts with a requirement in a referenced document, this document’s requirement shall have precedence.

2.1 FAA Specifications

NAS-IC-82150001-01 Digital Altimeter Setting Indicator (DASI) to Terminal Automation Systems ICD, November 30 2012.

FAA Final Program Requirements for Terminal Automation Modernization and Replacement (TAMR), January 2017.

FAA-E-2312A Console, TRACON/RAPCON, January 15, 1976.

FAA-G-2100F Electronic Equipment, General Requirements, November 15, 1993.

NAS-IC-21052414 Standard Terminal Automation Replacement System (STARS) / Traffic Flow Management System (TFMS), April 24, 2012.

NAS-IC-21058100 Standard Terminal Automation Replacement System (STARS) to Air Route Traffic Control Center (ARTCC) for Interfacility Data Transfer (IFDT) ICD, Rev F, August 5, 2019.

NAS-IC-34032105 Airport Surveillance Radar Model 9 (ASR-9) / Standard Terminal Automation Replacement System (STARS) ICD, June 14, 2001.

NAS-IC-34132105 En Route Surveillance Radar / Standard Terminal Automation Replacement System (STARS) ICD, June 22, 2001.

NAS-MD-314 Computer Program Functional Specification – Local Outputs, September 30, 2003.

NAS-MD-315 Computer Program Functional Specification – Remote Outputs, October 4, 2003.

NAS-MD-581 FDIO Software ICD, April 2005.

NAS-IC-34112105 Airport Surveillance Radar Model 11 (ASR-11) to Standard Terminal Automation Replacement System (STARS), Rev K, June 19, 2006.

NAS-IC-21050001-01 Standard Terminal Automation Replacement System (STARS) General NAS User Services (GeNUS) ICD, Rev H, May 13, 2019.

H372347 Standard Terminal Automation Replacement System (STARS) to Automated Protocol Exchanger (APEX) for Interfacility Data Transfer (IFDT) Outside the United States ICD, August 7, 2008.

NAS-IC-34180001-01 Airport Surface Detection Equipment – Model X (ASDE-X) Multilateration Surveillance Data to Air Traffic Control (ATC) User Subsystem, March 9, 2009.

November 2021 Page 5

PRM-A System Requirements, Ver 1.3, August 30, 2006.

G710561 Interface Control Document between the ASR-11 Radar and the Data Translation Equipment, Rev P, November 19. 2010.

SE-002-02-20100812 Surveillance and Broadcast Services Integration into ATC Automation Processing Requirements Document (RD), February, 10, 2011.

FAA-E-3020 Surveillance and Broadcast Services Visual System Specification (SSD), December 14, 2010.

NAS-IC-82530001-01 Surveillance and Broadcast Services (SBS) Service Delivery Point (SDP) to ATC Automation and Service Monitoring User Subsystem ICD, August 23, 2016.

Microprocessor En Route Automated Radar Tracking System (Micro-EARTS) Computer Program Functional Specification (CPFS) NAS-MD-674 Conflict Alert (CA) and Altitude Reporting Mode of Secondary Radar (Mode C) Intruder (MCI), September 2008.

NAS-MD-322 Computer Program Functional Specification – Real Time Quality Control of Radar Data.

National Airspace System (NAS) Secure Operating System Configuration Baseline Standard for LINUX/UNIX, Version 2.2, November 27, 2013

NAS-IC-21058257 Standard Terminal Automation Replacement System (STARS) To and From Time Based Flow Management (TBFM) ICD, August 14, 2018.

2.2 FAA Publications

Operational Concept Document for the Standard Terminal Automation Replacement System (STARS): Airway Facilities, November 1995.

FAA Operational Requirements Document for Standard Terminal Automation Replacement System (STARS), June 1995.

STARS Interchange Format Agreement (SIFA), August 1999.

FAA Digital Aeronautical Information (DAI), Digital Obstacle File (DOF), Version 1.0, April 2001.

2.3 FAA Orders

FAA Order 6000.15 General Maintenance Handbook for Airways Facilities, August 1991.

FAA Order 6000.27 Transmittal of Maintenance Philosophy Steering Group Report, June 1979.

November 2021 Page 6

FAA Order 6480.7C Airport Traffic Control Tower and Terminal Radar Approach Control Facility Design Guidelines, April 28,1995.

FAA Order 7110.65N Air Traffic Control, February 21, 2002.

FAA Order 7210.3K Facility Operation and Administration, September 16, 1993.

FAA Order 1370.114 Implementation of Federal Aviation Administration (FAA) Telecommunications Infrastructure (FTI) Services and Information Security Requirements in the National Airspace System (NAS), January 4, 2012.

FAA Order 1370.117 National Airspace System (NAS) Internet Protocol (IP) Addressing Policy, April 25, 2016.

FAA Order 1370.121 FAA Information Security and Privacy Program & Policy, December 23, 2016.

FAA Notice 1370.46 NAS Information Security Incident Detection, Reporting, and Response, September 30, 2015.

FAA Notice 6100.23 TDM-to-IP Transition Requirements for NAS Systems, October 16, 2015.

2.4 Military Standards

MIL-STD-1472G, Department of Defense Design Criteria Standard (Human engineering), 11 January 2012.

MIL-STD-454N Standard General Requirements for Electronic Equipment, June 30, 1992.

MIL-STD-498 Software Development and Documentation, December 5, 1994.

MIL-HDBK-1280, Department of Defense Handbook for Keyboard Arrangements, 20 February 1998.

2.5 Federal Standards

Federal Information Processing Standards (FIPS) 119-ADA Ada Language Processors, March 13, 1995.

Federal Information Processing Standards (FIPS) 127-2 Database Language Structured Query Language (SQL), October 4, 1993.

Federal Information Processing Standards (FIPS) 146-2 Profiles for Open Systems Internetworking Technologies, June 20, 1995.

Federal Information Processing Standards (FIPS) 151-2 Portable Operating System Interface (POSIX) – System Application Program Interface (C Language), May 12, 1993.

November 2021 Page 7

Federal Information Processing Standards (FIPS) 156 Information Resource Dictionary System, August 3, 1992.

Federal Information Processing Standards (FIPS) 160-C C Language Processors, August 24, 1992.

Federal Information Processing Standards Publication (FIPS PUB) 140-2, Security Requirements for Cryptographic Modules, May 25, 2001.

Federal Information Processing Standards Publication (FIPS PUB) 199, Standards for Security Categorization of Federal Information and Information Systems, February 2004.

National Institute of Standards and Technology Special Publication (NIST SP) 800-53 revision 4, Security and Privacy Controls for Federal Information Systems and Organizations, April 2013.

2.6 Federal Publications

FCC 47CFR Part 15 Federal Communications Commission Code Federal Regulations, October 1, 1993.

Federal Emergency Management Agency (FEMA) document FEMA 74, Reducing the Risks of Nonstructural Earthquake Damage, September 1994.

2.7 Industry Standards

AS9100D, Quality Management Systems – Requirements for Aviation, Space, and Defense Organizations

Electronic Industries Association (EIA)-449 General Purpose 37-Position and 9-Position Interface for Data Terminal Equipment and Data Circuit Terminating Equipment Employing Serial Binary Data Interchange, February 1990.

EIA-530A High Speed 25-Position Interface for Data Terminal Equipment and Data Circuit- Terminating Equipment, March 1987.

EIA/Telecommunications Industry Association (TIA)-232E Interface Between Data Terminal Equipment and Data Circuit-Terminating Equipment Employing Serial Binary Data Interchange, July 1991.

National Fire Protection Association (NFPA) 70 National Electrical Code, 1996.

Postscript Manual, January 1992; Updates to Postscript Manual, 2nd Edition, 7 July 1995.

Underwriters Laboratory (UL)60950 Safety of Information Technology Equipment, Issue 3, December 11, 2000.

UL60950-1 Information Technology Equipment – Safety – Part 1: General Requirements, December 19, 2011.

November 2021 Page 8

AA-K759B-TK Ethernet Version 2.0 The Ethernet Local Area Network data Link Layer and Physical Layer Specifications, Version 2.0, November 1982

ISO/IEC 8802-3: 1996 Information Processing Systems Local Area Networks Carrier Sense Multiple Access with Collision Detect (CSMA/CD) and Institute of Electrical and Electronic Engineers (IEEE) 802.3

Institute of Electrical and Electronic Engineers (IEEE) 802.3, Standard for Ethernet, September 2015.

Institute of Electrical and Electronic Engineers (IEEE) 1003.1-2008/Cor 2-2016 - Portable Operating System Interface (POSIX(R)) - Base Specifications, September 30, 2016.

Internet Engineering Task Force (IETF) Request for Comment (RFC) 791, Internet Protocol Specification, September 1981.

Internet Engineering Task Force (IETF) Request for Comment (RFC) 2460, Internet Protocol, Version 6 (IPv6) Specification, December 1998.

International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 9945:2009 Information technology — Portable Operating System Interface (POSIX®) Base Specifications, Issue 7, August 15, 2013.

International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) 23360-1:2006, Linux Standard Base (LSB) core specification 3.1 -- Part 1: Generic specification, December 15, 2006.

ANSI/HFES 100, Human Factors Engineering of Computer Workstations, 2007

Center for Internet Security (CIS) Red Hat Enterprise Linux 7 Benchmark, v2.1.1, January 31,

2.8 Other Documents

EUROCONTROL Radar Data Exchange (ASTERIX) standard:

Part 1, All-purpose structured EUROCONTOL Radar Data Exchange, Reference 005-1- 93.

Part 2, Transmission of Monoradar Data, Reference 005-2-93.

Part 3, Transmission of Monoradar Weather Information, Reference 005-3-93.

MTR 95W0000071 Development Methodology for the Standard Terminal Automation Replacement System (STARS) Functional Performance Requirements, August 1995.

JDS:99:01 Raytheon memorandum “Anomalous Flights in MITRE Test Scenarios”, March 2, 1999.

November 2021 Page 9

LMTSS4 ERAM Tracking Accuracy and Stability Requirements, Version 3, August 28, 2004.

FY17 ATO Requirements - MODERATE v1.0 (Tailored NIST SP 800-53 Rev4) - (Updated 10/6/2016).

November 2021 Page 10

3 STARS Requirements

3.1 STARS States, Service Levels and Modes

The STARS States, Service Levels, and Modes of Operation are defined for each of the site types: Operational and Support.

3.1.1 Operational Sites

Operational Sites consist of the Automation Subsystem (TAS, Local Towers, Remote TRACONs and Remote Towers) and the Operational Site Support Subsystem. Resources within the Operational Sites may be in the On-Line, Off-Line, or in some cases, the Standby resource state.

The Automation Subsystem supports ATC Operational and System Operational Functionality.

Multiple service levels are supported concurrently as illustrated in Figure 3-1 and 3-2. Included are the Full Service Level and Emergency Full Service Level (FSL and EFSL - each may be further divided into partitions A and B for test and cutover) and the Emergency Service Level (ESL). The site configuration may consist of FSL and ESL systems, or FSL and EFSL (dual FSL) systems. The air traffic controller at a TCP can interact with any one service level by selecting the corresponding mode for that TCW or TDW. Other TCW/TDW modes include training and Performance Verification (PV) variants of FS or ES. Operators at an MCW can select multiple views, including PRTA, PRTB or ES MCPs. Within FSL, MCP input defines whether each workstation in the FSL should interact with PRTA or PRTB. Similarly, within EFSL, MCP input defines whether each workstation in the EFSL should interact with PRTA or

PRTB.

The Operational Site Support Subsystem provides CAS software maintenance support for the FSL, EFSL and ESL service levels and includes the Site Support Service Level (SSSL) functionality.

The Support Subsystem site type, operating as a standard UNIX workstation using CAS, provide System Support Functionality for FSL, EFSL and ESL service levels. Support Subsystems have an operational and a test mode.

3.1.1.1 States and Recovery

3.1.1.1.1 Resource States

A resource state is an attribute of the resource that characterizes its condition (On-Line, Off- Line, or Standby) with respect to use in the system. When a resource is off-line, it is available for comprehensive diagnostic testing for resource verification or software testing. The Off-line resource state of FSL, with EFSL, is utilized within the Service Level Test Modes.

Except for non-concurrent redundant elements, major automation equipment (workstations, data processors, gateways, etc.) and individual service levels within each operational site shall[STARS-SSD-00001] be switchable to the On-Line or Off-Line resource state.

Any Automation Subsystem element (equipment and corresponding software) that is redundant to improve availability but cannot operate concurrently with the corresponding On-Line element

November 2021 Page 11 shall[STARS-SSD-00002] be switchable to either the On-Line, Off-Line, or Standby resource state.

November 2021 Page 12

3.1.1.1.2 Recovery

3.1.1.1.2.1 Recovery from Power Failure

Recovery from a power failure shall[STARS-SSD-00003] be automatic once power is restored.

3.1.1.1.2.2 Recovery from System Resource Failure

Reconfiguration of a resource from Standby to On-line shall[STARS-SSD-00004] be automatic upon failure of the corresponding On-line resource.

3.1.1.2 Service Levels

A service level is an indication of the functional and performance capability provided by STARS. Service levels operate concurrently and independently in STARS.

3.1.1.2.1 Concurrent Operation

Among the FSL, EFSL or ESL service levels (specified below); for each service level that is in its On-Line resource state, the Automation Subsystem shall[STARS-SSD-00005] concurrently provide the ATC Operational and System Operational functionality and performance (FSL, EFSL and ESL) required while maintaining the resource reserves described in Computer Resources (3.10).

The Operational Site Support Subsystem and Automation Subsystem shall[STARS-SSD-00006] operate concurrently.

3.1.1.2.2 Full Service Level (FSL)

The FSL includes the ATC Operational and System Operational Functionality capabilities and performance specified in sections 3.2.1.1 with reserves specified in section 3.10. FSL is divided into two variable-extent partitions, PRTA and PRTB, to support test and cutover between two versions of FSL software and/or hardware.

Each FSL partition in the Automation Subsystem shall[STARS-SSD-00007] accommodate FSL functionality while using live and simulated (from SSSL below) system inputs when in the On- Line resource state and simulated (from SSSL) system inputs when in the Off-Line resource state.

The Automation Subsystem shall[STARS-SSD-00008] accommodate separate instances of FSL software in two partitions: PRTA and PRTB.

The Automation Subsystem shall[STARS-SSD-00009] provide initiation of separate instances of STARS FSL automation subsystem software in PRTA and PRTB.

The Automation Subsystem shall[STARS-SSD-00010] accommodate FSL resources ranging from the minimum to all, within partition PRTA, with the remaining FSL resources allocated to

PRTB.

MCP input shall[STARS-SSD-00011] select those FSL resources to be assigned to PRTA, with a default of “all”.

November 2021 Page 13

3.1.1.2.3 Emergency Service Level (ESL)

The ESL includes the ATC Operational and System Operational capabilities and performance specified in section 3.2.1.2 with reserves specified in section 3.10.

The Automation Subsystem shall[STARS-SSD-00012] accommodate ESL functionality, using live and simulated (from SSSL below) system inputs, when ESL is in the On-Line resource state.

The Automation Subsystem shall[STARS-SSD-00013] accommodate ESL functionality using simulated (from SSSL) system inputs when ESL is in the Off-Line resource state.

3.1.1.2.4 Emergency Full Service Level (EFSL)

EFSL shall[STARS-SSD-00014] operate independently of FSL but function exactly like FSL unless specifically noted.

3.1.1.2.5 Site Support Service Level (SSSL)

The SSSL includes the System Support Functionality capabilities and performance specified in section 3.2.1.3.

The Operational Site Support Subsystem shall[STARS-SSD-00015] support SSSL, creating simulated system inputs from scenario generation tools for performance verification, test or training use by FSL or ESL in the Automation Subsystem.

3.1.1.2.6 Service Level Independence

ESL, FSL, and EFSL shall[STARS-SSD-00016] be implemented independently such that the software or adaptation of one service level can be switched without affecting operation of the alternate service level.

3.1.1.2.7 Service Level Interdependence

3.1.1.2.7.1 FSL/ESL

The requirements in this section apply only to a system that comprises FSL and legacy ESL. The requirements for a system that comprises FSL and EFSL are stated in section 3.1.1.2.7.2. FSL settings data will be periodically communicated to ESL so that upon switching from FSL to ESL a controller will find ESL settings to be correct and current. Where FSL settings do not apply exactly to ESL, ESL will apply the FSL settings to the extent reasonable.

Settings shall[STARS-SSD-00017] be transferred from FSL to ESL no less frequently than each 20 seconds.

Transferred settings shall[STARS-SSD-00018] be applied to ESL at the TCW/TDW if all the following conditions are met:

a. TCW/TDW is displaying FSL

b. TCW/TDW is not in Performance Verification Mode.

c. FSL and ESL are in the same service level mode.

November 2021 Page 14

Display Control Settings shall[STARS-SSD-00019] be preserved and used when switching from FSL to ESL.

A list containing up to 80 pairs of Aircraft Identification (ACID) and assigned discrete beacon code for active tracks (associated and disassociated) and pending flight plans owned at that TCW/TDW shall[STARS-SSD-00020] be transferred from FSL to ESL.

The ACID/beacon code list shall[STARS-SSD-00021] be transferred from FSL to ESL no less frequently than every 20 seconds.

The transferred ACID/beacon code list shall[STARS-SSD-00022] be applied to ESL at the TCW/TDW if the same conditions as shall[STARS-SSD-00018] above are met.

The Current System Altimeter setting shall[STARS-SSD-00023] be the latest valid setting from the altimeter reporting station adapted as the system altimeter for the TCP.

3.1.1.2.7.2 FSL/EFSL

FSL display settings data will be periodically communicated to EFSL. Where FSL settings do not apply exactly to EFSL due to differences in software or adaptation versions, EFSL will apply the FSL settings to the extent reasonable.

Display settings and the ACID/Beacon Code list shall[STARS-SSD-00024] be transferred from FSL to EFSL no less frequently than each 10 seconds.

Transferred display settings and ACID/Beacon Code data shall[STARS-SSD-00025] be applied to EFSL when eligible.

Display Control Settings shall[STARS-SSD-00026] be preserved and used when switching from FSL to EFSL.

A list containing up to 160 pairs of ACID and assigned discrete beacon code for active tracks and pending flight plans owned at that TCP shall[STARS-SSD-00027] be transferred from FSL to EFSL.

The Current System Altimeter setting shall[STARS-SSD-00028] be the latest valid setting from the altimeter reporting station adapted as the system altimeter for the TCP.

Upon switchover at a TCP from FSL to EFSL, owned flight plans at that position from FSL shall[STARS-SSD-00029]be created on EFSL as follows:

a. As local flight plans, with flight data from the last transfer interval

b. As unsupported or frozen data blocks if not updated by surveillance source

c. As frozen data blocks if beacon codes are non-discrete or primary only

d. As frozen data blocks if in some state of coast and with an alert condition

e. TSAS data for individual flights will not be synchronized between FSL and EFSL.

3.1.1.3 Modes

A mode is the manner, method, or way that a given resource behaves.

November 2021 Page 15

For each mode specified below, its scope (the resource to which it applies) is also specified. The following table summarizes the required modes for all Operational Site resources that require modes. Requirements regarding FS Workstation Mode also apply to EFSL Workstation Mode, unless otherwise stated.

Table 3-1 Summary of Required Operational Site Modes Scope Workstation Modes

Subsystem Resource Normal and Test Training Performance Verification

MCP

FS2 ES DSA3 DSF4 FS2 ES DSA

DSF FS2 ES

Automation TCW X1 X X3 X4 X1 X X1 X X Automation TDW X X X3 X4 X X X X X Service Level Modes Normal Test Automation TCW X X Automation TDW X X

1 FMA mode available 2 FS workstation includes both FS and EFS modes which apply to both FSL and EFSL respectively, in the dual FSL configuration 3 For STARS ELITE only, DSA mode is only available for selection at TCWs and LTDWs.

4 For Full STARS only, DSF is only available at TCWs/TDWs in a Remote Location.

3.1.1.3.1 Full Service (FS) Workstation Mode

A TCW in FS Workstation Mode shall[STARS-SSD-00030] independently allow selection of FMA mode in which the specified FMA functions are available.

Each TCP shall[STARS-SSD-00031] independently allow selection of a FS mode in which the workstation functions in concert with PRTA or PRTB functions throughout the remainder of the Automation Subsystem and with SSSL functions in the Operational Site Support Subsystem.

The requirements regarding FS workstation mode also apply to EFS workstation mode throughout the SSD, unless otherwise noted.

3.1.1.3.2 Emergency Service (ES) Workstation Mode

Each TCP shall[STARS-SSD-00032] independently allow selection of a ES mode in which the workstation functions in concert with ESL functions throughout the remainder of the Automation Subsystem and with SSSL functions in the Operational Site Support Subsystem.

3.1.1.3.3 FS Training Workstation Mode

Each TCP shall[STARS-SSD-00033] independently allow selection of a FS Training mode in which the workstation functions in concert with FSL functions handling training data throughout

November 2021 Page 16 the remainder of the Automation Subsystem and with SSSL functions in the Operational Site Support Subsystem.

A TCW in FS Training Workstation Mode shall[STARS-SSD-00034] independently allow selection of an FMA mode in which the specified FMA functions handling training data are available.

A TCP in FS Training Workstation Mode shall[STARS-SSD-00035] independently allow TCP-specific ATPA commands to be entered.

3.1.1.3.4 ES Training Workstation Mode

Each TCP shall[STARS-SSD-00036] independently allow selection of a ES Training mode in which the workstation functions in concert with ESL functions handling training data throughout the remainder of the Automation Subsystem and with SSSL functions in the Operational Site Support Subsystem.

3.1.1.3.5 FS Performance Verification Workstation Mode

The FS MCP shall[STARS-SSD-00037] display the results of PV testing.

Any specified TCP shall[STARS-SSD-00038] support a FS PV mode in which the workstation provides data for evaluation of performance verification.

FS MCP input shall[STARS-SSD-00039] specify the TCP to be switched to FS PV mode.

A TCW in FS Performance Verification Workstation Mode shall[STARS-SSD-00040] independently allow selection of an FMA mode in which the specified FMA functions handling performance verification data are available.

A TCP in FS Performance Verification Workstation Mode shall[STARS-SSD-00041] independently allow TCP-specific ATPA commands to be entered.

3.1.1.3.6 ES Performance Verification Workstation Mode

Any specified TCW or TDW shall[STARS-SSD-00042] support an ES Performance Verification mode in which the workstation provides data for evaluation of performance verification.

ESL MCP input shall[STARS-SSD-00043] specify the TCW or TDW to be switched to ES Performance Verification mode.

The ESL MCP shall[STARS-SSD-00044] display the results of Performance Verification testing.

3.1.1.3.7 MCP Workstation Mode

Each TCP shall[STARS-SSD-00045] independently allow selection of a MCP mode in which the workstation provides MCP functionality.

When MCP input at a TCP in MCP mode switches it to a TCP mode, the associated TCP display shall[STARS-SSD-00046] automatically appear with no additional operator action.

November 2021 Page 17

3.1.1.3.8 MCP Views

Any workstation shall[STARS-SSD-00047] support multiple MCPs.

3.1.1.3.9 Service Level Modes

In the Normal mode, FSL and/or ESL shall[STARS-SSD-00048] receive live inputs and simulated inputs and be in the On-Line resource state.

In the Test mode, FSL and/or ESL shall[STARS-SSD-00049] receive only simulated inputs and be in the Off-line resource state.

The FSL and ESL MCP shall[STARS-SSD-00050] indicate when the corresponding service level is in test mode.

3.1.1.3.10 Direct Sensor Access (DSA) Mode

DSA mode will be available for selection in Normal mode and Test mode to provide targets for display to TCWs and LTDWs in the event that track data is not available from the RDP subsystem.

Capabilities such as tracking, flight data processing, MSAW, MCI, and CA processing, TSAS as well as TCP commands that would normally be processed by the RDP will not be available at a TCP in DSA mode. Weather processing, local TCP display control commands and the altimeter setting command will be available at TCPs in DSA mode.

DSA mode will only be available in a STARS ELITE system.

A TCP shall[STARS-SSD-00051] independently allow selection of DSA mode in which the functionality specific to DSA will be available.

Up to 160 pairs of ACID and assigned discrete beacon codes for active tracks (associated and disassociated) and pending flight plans owned at that TCW/LTDW shall[STARS-SSD-00052] be available for DSA mode.

3.1.1.3.10.1 Weather Data Processing

In DSA mode weather data shall[STARS-SSD-00053] be accepted simultaneously from multiple surveillance systems.

In DSA mode weather data shall[STARS-SSD-00054] be made available for display.

3.1.1.3.10.2 Source Data for Pressure Correction

In DSA mode input altimeter settings for each altimeter reporting station shall[STARS-SSD- 00055] be obtained from TCP input.

In DSA mode the current altimeter setting for each altimeter reporting station shall[STARS-SSD- 00056] be the most recent valid input altimeter setting.

November 2021 Page 18

3.1.1.3.11 Direct Sensor Feed (DSF)

The Direct Sensor Feed (DSF) capability will provide a display mode in which radar target data is displayed at TDWs in a Remote Tower Location as well as TCWs in a Remote TRACON Location in the event that track data is no longer available from the TAS. The DSF capability includes a dedicated direct Short Range Radar (SRR) feed to a set of NUNIOS located in the Remote Location (Tower or TRACON), monitoring of the direct sensor interface and NUNIOs, and the use of the Direct Sensor Access (DSA) CHI at the remote TCP to display target data from that direct sensor feed.

Capabilities such as tracking, flight data processing, MSAW, MCI, and CA processing, TSAS as well as TCP commands that would normally be processed by the RDP will not be available.

Weather processing, local TCP display control commands and the altimeter setting command will be available.

A remote TCP shall[STARS-SSD-00057] independently allow selection of DSF mode in which the functionality specific to the DSF capability (if adapted) will become available.

3.1.2 Support Sites (OSF, SCSC)

The support sites operate in a standard UNIX workstation and server mode of operation using CAS. The OSF and SCSC include equipment that replicates the Automation Subsystem and all of its modes of operation for testing purposes. Support Sites do not require modes. Testing of new versions of CAS or COTS at Support Sites is accomplished by use of the off line resource state.

3.1.3 STARS LITE

STARS LITE, is a Stand Alone Tower configuration of the STARS system. It provides Air Traffic Controllers (ATCSs) with improved surveillance capabilities within the airport traffic environment. Use of STARS LITE will aid ATCSs in more effectively handling air traffic workloads that are affected by airport congestion, a variety of aircraft performance characteristics, terrain, obstructions, complex runway configurations, and weather conditions. A certified STARS LITE system with CA, MSAW, MCI safety alert features extends an ATCS' ability to manage airspace through displayed weather and surveillance data rather than relying solely on visual contacts or pilot reports. The displayed data enables ATCSs in the tower cab to provide radar traffic advisories in accordance with FAAH 7110.65, FAA Air Traffic Control Handbook. STARS LITE, with the use of digital maps, enables ATCSs to see airspace boundaries as well as geographical features surrounding the airport. This mapping display facilitates locating and identifying arriving, departing, and over-flying aircraft.

STARS LITE, provides air traffic controllers with surveillance position information, aircraft beacon code, altitude, maps, range marks, and weather information. STARS LITE, provides maintenance personnel with capabilities to monitor the systems integrity.

The normal configuration of STARS LITE includes one TDW and a single FDIO input. There is no independent time source.

A standard COTS keyboard and trackball are used in place of the STARS DEC/keyboard/trackball hardware.

November 2021 Page 19

3.2 STARS Capabilities

This major section establishes requirements for the capabilities of STARS. A third-level section is dedicated to requirements for each of the site types: Operational and Support. ATC Operational, System Operational, and those System Support requirements relevant to Operational Sites are addressed in the Operational Sites section. System Support requirements appear in the OSF and SCSC sections.

3.2.1 Operational Sites

Operational Sites can operate autonomously to meet the immediate needs of the primary STARS mission which is to provide safe and efficient air traffic control. They rely on the support sites only for long-term support such as software upgrades and adaptation changes. They contain equipment and software to directly interface with the controllers and other operational personnel, providing the core STARS functionality. Their architecture is replicated for test and validation purposes in some of the support sites.