J6A_TFDM_TFMS_SSD_Amend-1.pdf

TFM-2 SIR DTFAWA-16-R-00010 Amendment 1

Attachment J-6.A

Terminal Flight Data Manager (TFDM)

TFMS Functional Allocation

System Specification Document

TFDM-TFMS Functional Allocation SSD August 19, 2016

Terminal Flight Data Manager (TFDM)

Requirements Allocated to

Traffic Flow Management System (TFMS)

FUNCTIONAL ALLOCATION –

SYSTEM SPECIFICATION DOCUMENT (FA-SSD)

August 19, 2016

Federal Aviation

Administration

800 Independence Avenue

SW Washington, DC

20591

Revision Record

Revision Description Date

A

Updated Introduction to include latest description of

TFDM capabilities and services.

Added requirement IDs after each requirement.

Added additional requirements in 3.1.1.1 Data

Exchange Inputs section.

Moved requirements in 3.1.1.2 User Inputs to Display

Outputs section.

Added "pre-canned" to glossary.

Deleted, 3.1.4.4.2.46 Departure Demand Aggregates as some requirements were duplicative of other requirements in the document. Moved fix requirements to Departure Fix Demand section.

Added 3.1.4.4.3 Arrived/Landed, 3.1.4.4.4 Departed

Flight List, and 3.1.4.7 Departure Delay List sections.

Added 3.1.4.10 Arrival Efficiency Analysis Section.

Moved requirements from the Departure Demand

Flight List section related to general flight list manipulation to new section 3.1.4.4.1 Flight List

Manipulation

Updated 3.1.4.15 Performance Requirements section.

The Departure Delay List section has been moved to after the Restrictions List section.

The Arrival Flight List section has been renamed the

“Arrived” Flight List section.

3.1.4.3.2. has been moved to the departure flight list section.

Removed note regarding pending departures. Added requirement FA-SSD843.

Removed requirements referencing parking location status.

12/05/14

B Added Departure Efficiency Analysis and Arrival Demand requirements

Deleted Arrival Efficiency Analysis requirements

03/19/2015

C Added Appendix A for Build 3 requirements.

Misc. formatting edits 06/10/2015

D Misc. formatting edits 07/29/2015

E Misc. formatting edits

Specified rerouting display requirements are based on user input

(FA-SSD525, 526, 527 and 528)

Added ‘Not Read’ as a differentiable route approval status (FA-

SSD444)

Removed predicted taxi start time requirement (FA-SSD596)

Added notes for clarification

09/18/2015

F Added:

1. Differentiation of aircraft by airline three letter designator

(FA-SSD1005)

2. Differentiation by A/C type (FA-SSD1006)

3. Filtering of aircraft by airline three letter designator (FA-

SSD1007)

4. Filtering by A/C type (FA-SSD1008)

5. Data tag auto offset (FA-SSD1010)

6. Data tag manual offset (FA-SSD1009)

02/10/2016

G Revised requirement tracking numbers for 3.1.4.4.4 through

3.1.4.4.8 to eliminate duplicate use of FA-SSD542.

08/19/2016

Table of Contents

1 INTRODUCTION

1.1 Scope & Background

1.1.1 TFDM System Description

1.2 Allocated Functionality Overview

1.2.1 TFMS

2 APPLICABLE DOCUMENTS

2.1 Government Documents

2.1.1 Specifications

2.1.2 Standards

2.1.3 Other Government Documents

2.2 Non-Government Documents

3 FUNCTIONAL ALLOCATIONS

3.1 TFMS Requirements

3.1.1 TFMS Inputs

3.1.2 TFMS Processing

3.1.3 TFMS Outputs

3.1.4 TFMS Display Outputs

APPENDIX A BUILD 3 REQUIREMENTS

APPENDIX B GLOSSARY

APPENDIX C ACRONYMS AND ABBREVIATIONS

TABLE OF FIGURES

Figure 1-1 TFDM Operational and System View

Table of Tables

Table 1-1 TFDM Services by Configuration Table 1-2 TFDM Subsumption

1 Introduction

1.1 Scope & Background

This specification establishes the functional and performance requirements for the Traffic Flow

Management System (TFMS) as a result of the Terminal Flight Data Manager (TFDM) program investment.

TFDM is an ATCT system focused on improving the flow of flight and other tower data between

ATCT and other ATC domain users. It also provides data exchanges between users and stakeholders, and facilitates user management of airport surface resources by providing a set of decision support capabilities to improve surface traffic flow.

The TFDM System deployment is to a subset of NAS ATCTs. These ATCTs receive the TFDM capabilities based on their operational needs and their installation and deployment impacts on the

NAS. Towers with fewer operational needs may receive only EFD and improved data exchange as one of two primary system configurations.

Other towers may require improved traffic management, require data exchange with stakeholders and provide decision support capabilities in addition to EFD. These airports, that frequently experience demand/capacity imbalances and delays, may receive EFD, traffic management tools, and decision support capabilities, such as SM, to support collaborative management of surface congestion.

The full range of capabilities required for the TFDM program are allocated between the TFDM

System and other existing and future processing platforms within the NAS. Allocations to other major systems and platforms include the Flight Data Input/Output system (FDIO), Airport

Surface Detection Equipment, Model X (ASDE-X), Airport Surface Surveillance Capability

(ASSC), Standard Terminal Automation Replacement System (STARS), Traffic Flow

Management System (TFMS), and Time-Based Flow Management (TBFM).

1.1.1 TFDM System Description

1.1.1.1 Services

TFDM electronically receives, processes, and displays flight data to operational positions in the

ATCT. In addition, TFDM makes that information available to other automation systems. By integrating flight data from multiple NAS and non-NAS systems and stakeholders, TFDM provides an electronic means of coordination between tower, Terminal Radar Approach Control

(TRACON), other FAA operational domains and external stakeholders. This allows for improved situational awareness for the ATCT and all other stakeholders.

TFDM provides air traffic controllers with a view of available surface and terminal area surveillance information when integrated with electronic flight data information. The CHI requirements are detailed in the CHI specification document.

The Traffic Flow Management (TFM) Data function integrates surface data with data from the

NAS traffic management systems by exchanging and processing data from Time-Based Flow

Management (TBFM) and Traffic Flow Management System (TFMS). TFDM also includes support for the automated release time requests, subsumes Airport Resource Management Tool

(ARMT) capabilities and the integration of surface scheduling functions and data.

TFDM contains capabilities that assist air traffic controllers in performing their tasks more efficiently while reducing their workload. TFDM manages airport resources through airport configuration management, including the ability to create, store and implement airport configurations and make airport resource information available to stakeholders. Included in the manage airport resources capability is the ability to perform runway load balancing and to model, schedule and implement load balancing solutions.

This integrated automated ATCT environment improves surface traffic flow efficiency, reduces taxi delays, reduces carbon emissions by reducing fuel burn, and further enhances collaborative decision making capabilities contained in SS and SM services which are described in the

Perform Surface Scheduling (PSS) and Perform Surface Metering (PSM) sections. Surface scheduling calculates predicted schedules using adapted rules and data from external systems at runways (including assignments), de-ice pads and holding areas within the active movement area, hand-off spots, and parking gates. PSM includes the setting of Departure Metering Program

(DMP) parameters by the airport's designated Departure Reservoir Coordinator (DRC) to optimize performance for any given operational environment. With these DMP parameters, PSM detects when a demand/capacity imbalance is predicted to occur and then recommends a DMP to minimize time waiting in a queue along with maximizing a resource's throughput.

The MRA component provides ATCT users and other stakeholders with key metrics needed to evaluate the effectiveness of TFDM’s scheduling and metering functions. Furthermore, MRA provides key operational data such as traffic counts and taxi delays which ATCTs are required to report. MRA allows users to filter the metric data into operational reports that can be tailored by request.

SAS and M&C include data recording, data archiving, data playback and system monitoring.

TFDM services as described in earlier sections are presented graphically in the notional TFDM representation in Figure 1-1 below.

Figure 1-1 TFDM Operational and System View

1.1.1.2 TFDM Configurations

TFDM provides two software configurations that consist of different levels of TFDM capabilities. Both configurations provide SAS and M&C capabilities.

TFDM Configuration A provides the entire suite of TFDM capabilities

TFDM Configuration B provides Electronic Flight Data with some limited traffic flow data, limited airport resource management capability, and limited data exchange with

Flight Operator System (FOS).

Table 3-1 below highlights the key services provided in each configuration. It should be noted, however, that during TFDM deployment, the specific needs of any individual ATCT may require a combination of TFDM capabilities that do not map precisely into one of the two primary

TFDM configurations. These facilities will be identified during the site-survey when each tower’s existing capabilities such as ASDE-X/ASSC, TDLS, Departure Spacing Program (DSP), Surface Movement Advisor (SMA), ARMT, Electronic Flight Strip Transfer System (EFSTS) or other capabilities are confirmed.

TFDM Services Configuration A Configuration B

EFD

Electronic Flight Data (EFD) Full Full

EFD Integration w/Surveillance

Data Full

Full, if surface surveillance is available

SS Surface Scheduling Full

SM Surface Metering Full

ARM Airport Resource Management Full Selected

TFD Traffic Flow Data Management Full Selected

MRA Metrics, Reporting & Analysis Full Selected

M&C Monitor and Control Full Full

SAS

System Administration and

Support Full Full

Table 1-1 TFDM Services by Configuration

1.1.1.3 Implementation

The amount and type of TFDM resources that are deployed to each tower is based on two attributes. The first attribute is the general tower size category; which implies the number of existing/legacy systems and operational positions that the tower contains. The second attribute is an ATCT’s designated TFDM Configuration; which is determined based on the ATCT’s positive cost/benefit analysis with those services deployed.

1.1.1.3.1 Tower Size Categories

Tower size categories range from Large to Small. For purposes of this SSD, there are three sizes

(large, medium, and small). In the large tower category, a tower has multiple staffed Local

Control (LC) and Ground Control (GC) positions, a Flight Data and Clearance Delivery (FD/CD) position, a Front Line Manager (FLM) position, and a Traffic Management Unit (TMU) that contains TFMS and/or TBFM displays. At some large towers, a gate metering/gate hold

(GM/GH) position may also be present. Additionally, large towers have, at minimum, the following systems: ASDE-X /ASSC, Tower Data Link Services (TDLS), and EFSTS. Some large towers also have DSP (at New York area airports) or SMA (at Atlanta Airport). Medium towers generally do not have a TMU or ASDE-X/ASSC.

The permutations of tower size and equipage vary extensively. Small towers generally only have one LC, one GC, one FLM, and a combined FD/CD position. Additionally, Small towers do not generally have a TDLS system, as well as no ASDE-X/ASSC, DSP, or SMA systems.

1.1.1.3.2 NAS System Replacement and TFDM Subsumptions

Table 3‑ 2 below is an overview of the subsumption by TFDM of some NAS automation and manual systems. These systems’ functions are either subsumed by TFDM or re-allocated to one or multiple FAA systems (e.g., TFDM/TBFM/TFMS). The TFDM SSD details the requirements for the legacy systems’ functions which the TFDM System is implementing.

System Subsumed Components Subsumed by TFDM

Paper Strip Bays All

Drop Tubes All

Cameras All

EFSTS (Electronic Flight Strip Transfer System) All (allocated between TFDM/FDIO)

ARMT (Airport Resource Management Tool) All (allocated between TBFM/TFMS/TFDM)

AEFS (Advanced Electronic Flight Strip) All

DSP (Departure Spacing Program) All (allocated between TBFM/TFMS/TFDM)

SMA (Surface Movement Advisor) All (allocated between TBFM/TFMS/TFDM)

Table 1-2 TFDM Subsumption

1.2 Allocated Functionality Overview

1.2.1 TFMS

Through several analysis efforts, it was determined that TFMS was the most appropriate system to develop and deploy certain aspects of functionality of the TFDM concept [1-5]. Rationale for these allocations range from who the expected user will be to the types of data and operations anticipated and how they have traditionally been supported by automation. The functionality allocated to TFMS covers four (4) primary areas:

Provision of data exchange between the TFMS and TFDM systems to enable operations and traffic management.

Subsumption of components of the Departure Spacing Program (DSP), an operational capability for the New York Metroplex facilities

Subsumption of components of the Airport Resource Management Tool (ARMT), an operational capability used at various locations throughout the NAS

Provision of a Surface Situational Awareness (SSA) capability for Air Traffic

Control Tower (ATCT), Terminal Radar Approach Control (TRACON), Air

Route Traffic Control Center (ARTCC) and Air Traffic Control System

Command Center (ATCSCC) facilities

These four areas significantly overlap in functionality. The requirements provided have been traced for source need to ensure that any duplication is removed, while still achieving all required functionality for each of the four areas. The requirements developed to support these functions are organized into sections for Inputs, Processing, Outputs, and Display Outputs within the requirements section. These functional areas are further described in the sections below.

1.2.1.1 TFMS-TDFM Data Exchange

In 2012, a cross-domain, cross-program integration working group was initiated to support the

TFDM acquisition. This TBFM-TFMS-TFDM Integration working group engaged in efforts and topics to integrate the three programs’ operational concepts, system development, requirements generation, and data needs to ensure the critical envisioned Next Generation Air Transportation

System goals and milestones are met. Representatives (FAA and contract support personnel) for the TFDM, TBFM, and Collaborative Air Traffic Management Technologies (CATM-T) programs were in attendance, and met bi-weekly to discuss integration-related items such as data exchange, use cases, and functional allocation.

The requirements provided in this document represent the functions identified by this working group and allocated to TFMS. The requirements, in general, cover necessary bi-directional interface(s) with TFMS for specific data needs.

1.2.1.2 DSP Subsumption Functionality

Under the vision for the Next Generation Air Transportation System (NextGen), the Federal

Aviation Administration (FAA) is working to modernize the systems used for air traffic control and management in the NAS. As part of this effort, the FAA is focused on ensuring a seamless transition from the systems used for current day operations to this future state. In the effort to modernize, TFDM is working to subsume the DSP operational capability, allowing for its decommissioning and removal from NAS operations.

The New York area departure operations are unique within the NAS, yet involve some of the most complex operations. The New York area is the only NAS user of DSP, a NAS operational capability first prototyped in 1994 to 1995 in the Los Angeles basin then implemented only in the Greater New York area starting in 1998. DSP serves as a critical capability for New York operations supporting traffic flow management, tower functions the coordination required between facilities to ensure that New York’s complex departure operations can be carried out efficiently. It must be specifically considered to ensure that the functions that comprise DSP are present in the systems being implemented in the mid-term timeframe (2017-2020). The importance of the New York area in the operational success of air traffic control and many airlines ensures that the subsumption of this one system in particular is thoroughly addressed, without hampering the efforts in the rest of the NAS.

DSP was designed to assist traffic managers at the New York Air Route Traffic Control Center

(ZNY ARTCC) and New York Terminal Radar Approach Control (N90 TRACON) to sequence and minimize departure delays for aircraft departing from multiple airports over the same departure fix. While the DSP system was originally intended to support this function, its current day use can be broken down into three key areas of use:

1. Tower use for departures

2. Traffic Flow Management (TFM) use for departures

3. Departure traffic metering

The requirements provided in this document focus primarily on the traffic flow management aspects of DSP and support for electronic coordination allowing for the reduction of phone calls.

The requirements, in general, cover:

Update and display of real-time flight plan status, supporting coordination between ZNY and N90

Awareness of flight surface progress through flight state data exchange

Awareness of the dynamic (real-time) flight line-up at each airport, allowing for coordination between N90 and tower Local Controllers (LC)

Coordination regarding airport configuration and associated parameters

The remaining elements of DSP functionality are either already planned to be developed through the CATM-T Work Package 4 (WP4) program investment or are allocated to other NAS automation systems, such as TFDM or TBFM.

1.2.1.3 ARMT Subsumption Functionality

Similar to the DSP subsumption, TFDM is also working to ensure full subsumption of the

ARMT capability allowing for its decommissioning and removal from NAS operations.

ARMT development began in 1990 as a joint effort between the Atlanta ATCT and Delta

Airlines. The resulting capability was provided local/regional airport demand and traffic management information to support Traffic Management Supervisors, Specialists, and Officers within the Atlanta Terminal complex. Its current day use can be broken down into three key areas of use:

1. Airport resource management

2. Traffic management decisions

3. Collection of airport operational data

ARMT is now deployed at over 40 facilities and has evolved to include functionality for:

Supporting administrative tasks such as traffic counts and delay report statistics, Integrating data through external interfaces, Analyzing and displaying traffic data for arrival and departure demand and delays, Analyzing and displaying airport configuration management data for improved runway landing rates, reduced taxi times, elimination of lost or timed-out flight plans, and other efficiencies, and

Generating and displaying efficiency analyses and reports.

The requirements provided in this document replicate the traffic flow management displays of

ARMT and the required processing to generate those displays. The requirements, in general, cover:

Display of flight lists, filterable by attributes (e.g., departed, taxi, gate hold, etc.)

Display of aggregate demand information

Display of traffic counts and delay information

Generation, display, and reporting of post-operations analysis for departures and arrivals

The remaining elements of ARMT functionality are allocated to other NAS automation systems, such as TFDM.

1.2.1.4 SSA Capability Functionality

Beyond the aforementioned subsumptions, the TFDM Program is planning to deploy a surface situation capability that will equip ATCTs, TRACONs, ARTCCs, and the Air Traffic Control

System Command Center (ATCSCC) with shared SSA. Shared SSA is an outcome achieved when traffic managers have an understanding of airport surface information such as departure queue length, elapsed and predicted taxi times, route status information, etc.

To a limited extent, SSA is accomplished today through verbal conversations and the use of automation available at some facilities. However, identifying an SSA-related problem, assembling all of the needed information by the appropriate traffic manager or traffic mangers, and developing a resolution to solve the problem requires many time-consuming actions often by many different individuals. The result is reactive decision making and delay. Shared SSA can be more effectively achieved by providing the same view of the airport surface and associated airport and flight data to all of the appropriate traffic management stakeholders. SSA enables earlier problem identification, fewer actions need to resolve the problem, earlier problem resolution, and ultimately less delay.

Through this capability, the TFDM Program will enhance effective decision making regarding surface operations amongst stakeholders. The requirements provided in this document focus on three primary areas with respect to the airport surface:

Surface Traffic Data, including surface surveillance tracks for aircraft and vehicles on airport layout maps

Airport and Airspace Resource Data, including airport and airspace resource data for the surface traffic, with filtering and differentiating the display of aircraft as icons on the airport layout map and in flight lists based on user input.

2 Applicable Documents

2.1 Government Documents

See other contract documents

2.1.1 Specifications

2.1.2 Standards

2.1.3 Other Government Documents

See other contract documents.

2.2 Non-Government Documents

See other contract documents.

3 Functional Allocations

3.1 TFMS Requirements

NOTE: Unless otherwise indicated, the requirements herein support TFDM Build 1. No Build 2 requirements have been allocated to TFMS. Build 3 requirements herein supporting DSP subsumption have grey shading.

3.1.1 TFMS Inputs

This section describes the new inputs required to support the functions outlined within this document. Existing inputs are not explicitly detailed but are assumed to be present in order to support this integration effort (i.e. ERAM).

3.1.1.1 Data Exchange Inputs

This section describes the data exchange inputs required to support the functionality outlined within this document. Data exchange outputs are detailed in a subsequent section.

3.1.1.1.1 TFMS must receive TFDM Airport and Flight Information Service (AFIS) data. [FA-SSD302]

3.1.1.1.2 TFMS must receive TFDM General Information Service (GIS) data. [FA-

SSD837]

3.1.1.1.3 TFMS must receive Departure Queue Acknowledgement Service (DQAS) requests. [FA-SSD838]

Note: TFMS is expected to develop and support a dynamic subscription service to allow for the request and update of the departure queue acknowledgement status. This is necessary for DSP subsumption.

3.1.1.1.4 TFMS must receive STARS Application Interface Gateway (AIG) data.

[FA-SSD303]

3.1.1.1.5 TFMS must receive surveillance surface data from ASDE-X equipped airports. [FA-SSD304]

3.1.1.1.6 TFMS must receive surveillance surface data from ASSC equipped airports. [FA-SSD305]

3.1.1.1.7 TFMS must receive free-text messages based on user input. [FA-SSD317]

Note: This is an internal data exchange to support messaging capabilities between facilities.

3.1.1.1.8 TFMS must receive pre-canned messages based on user input. [FA-

SSD318]

Note: This is an internal data exchange to support messaging capabilities between facilities.

3.1.1.1.9 TFMS must accept user input to specify the analysis time period for the departure efficiency analysis. [FA-SSD313]

Note: The Departure Efficiency Analysis provides a consolidated view of various data points that allow users to evaluate past operational performance. This tool is further described in the display section for

Departure Efficiency Analysis requirements.

3.1.1.2 User-Configurable Time Parameters

3.1.1.2.1 TFMS must accept user input to set the predicted total taxi time threshold parameter. [FA-SSD322]

3.1.1.2.2 TFMS must accept user input to set an ETD threshold time parameter.

[FA-SSD323]

3.1.1.2.3 TFMS must accept user input to set the elapsed taxi time threshold time parameter. [FA-SSD324]

3.1.1.2.4 TFMS must accept user input to set the predicted delay time increments.

[FA-SSD325]

3.1.1.2.5 TFMS must accept user input to set the current delay time increments.

[FA-SSD326]

3.1.1.2.6 TFMS must accept user input to set a parameter to define the predicted delay time threshold. [FA-SSD327]

3.1.1.2.7 TFMS must accept user input to set a parameter to define the current delay time threshold. [FA-SSD328]

3.1.1.2.8 TFMS must accept user input to set the fix departure resource rate. [FA-

SSD329]

Note: Requirement is expected to be part of CATM-T WP4.

3.1.1.2.9 TFMS must accept user input to set the fix demand time increment within the departure fix demand list. [FA-SSD330]

3.1.1.2.10 TFMS must accept user input to set the Estimated Departure Control Time

(EDCT) time increments. [FA-SSD331]

3.1.1.2.11 TFMS must accept user input to set the Call For Release (CFR) time increments. [FA-SSD332]

3.1.2 TFMS Processing

This section describes the new processing required to support the functions outlined within this document.

3.1.2.1 General Processing

3.1.2.1.1 TFMS must update the flight-specific departure route approval status upon receiving user input route approval status. [FA-SSD334]

Note: This replaces DSP functionality that enables the manual update of a flight’s route approval status.

3.1.2.1.2 TFMS must change the flight-specific departure route approval status upon receipt of a flight plan amendment. [FA-SSD335]

Note: This replaces DSP functionality which allows for the automatic setting of a flight’s route approval status to revised (REV) when a reroute has been entered into the KVDT emulator.

3.1.2.1.3 TFMS must change flight-specific departure route approval status upon receipt of a flight plan that matches adapted low-altitude routes. [FA-

SSD336]

Note: This replaces DSP functionality which allows for the automatic setting of a flight’s route approval status to Terminal Enroute Control

(TEC) status.

3.1.2.1.4 TFMS must generate aggregate fix delay metrics. [FA-SSD337]

3.1.2.1.5 TFMS must calculate the flight-specific elapsed departure taxi duration.

[FA-SSD338]

Note: TFMS will receive the taxi start time from TFDM in order to calculate the elapsed duration. TFDM will also send data to notify TFMS that the flight is no longer in taxi status.

3.1.2.1.6 TFMS must calculate the flight-specific elapsed departure delay. [FA-

SSD339]

3.1.2.2 Replay Capability

3.1.2.2.1 TFMS must provide a replay capability within the Airport Layout View based on a user-selectable time period. [FA-SSD349]

Note: The replay capability does not need to operate simultaneously with viewing the current airport layout map.

3.1.2.2.2 TFMS must accept a user request to review operational information in replay. [FA-SSD309]

3.1.2.2.3 The replay capability must depict all airport layout view data presented to the user at the time of the recording [FA-SSD839]

3.1.2.2.4 TFMS must provide the user the ability to set a start time for the replay capability. [FA-SSD350]

3.1.2.2.5 TFMS must provide the user the ability to set an end time for the replay capability. [FA-SSD351]

3.1.2.2.6 TFMS must store all data necessary to provide the replay capability in accordance with existing TFMS data archiving requirements and policy.

[FA-SSD352]

3.1.2.2.7 TFMS must provide the user the ability to rewind within the replay capability. [FA-SSD353]

3.1.2.2.8 TFMS must provide the user the ability to fast forward within the replay capability. [FA-SSD354]

3.1.2.2.9 TFMS must provide the user the ability to pause within the replay capability. [FA-SSD355]

3.1.2.2.10 TFMS must provide the user the ability to search a specific time for replay within the replay capability. [FA-SSD356]

3.1.2.3 Messaging

3.1.2.3.1 TFMS must create pre-canned messages based on user input. [FA-

SSD315]

3.1.2.3.2 TFMS must create free-text messages based on user input. [FA-SSD316]

3.1.2.3.3 TFMS must acknowledge the pre-canned messages based on user input.

[FA-SSD319]

3.1.2.3.4 TFMS must acknowledge free-text messages based on user input. [FA-

SSD320]

3.1.2.3.5 TFMS must record pre-canned messages. [FA-SSD357]

3.1.2.3.6 TFMS must record free-text messages. [FA-SSD358]

3.1.2.4 User Preferences

3.1.2.4.1 TFMS must provide user preferences for the airport layout view, aircraft icons, aircraft icon filtering, aircraft icon differentiation, data tag elements, user-configurable parameters, flight lists, and demand views. [FA-

SSD360]

3.1.2.4.2 TFMS must provide user preference capabilities in accordance with existing TFMS requirements. [FA-SSD361]

Note: User preference capabilities include the ability to create, save, modify, and recall user preferences.

3.1.3 TFMS Outputs

This section describes the new data exchange outputs required to support the functions outlined within this document. Existing or planned outputs are not all explicitly detailed but are assumed to be present in order to support this integration effort.

3.1.3.1.1 TFMS must send flight-specific departure route approval status to the

TFDM system. [FA-SSD363]

3.1.3.1.2 TFMS must send Departure Queue Acknowledgement Service (DQAS) responses. [FA-SSD364]

Note: TFMS is expected to develop and support a dynamic subscription service to allow for the request and update of the departure queue acknowledgement status. This is necessary for DSP subsumption.

3.1.3.1.3 TFMS must send aggregate fix delay metrics to the TFDM system. [FA-

SSD365]

3.1.3.1.4 TFMS must send aggregate fix delay metrics to the TBFM system. [FA-

SSD366]

3.1.3.1.5 TFMS must send the airport departure rate to the TFDM system. [FA-

SSD367]

Note: This functionality is existing.

3.1.3.1.6 TFMS must send pre-canned messages based on user input. [FA-SSD369]

3.1.3.1.7 TFMS must send free-text messages based on user input. [FA-SSD370]

3.1.4 TFMS Display Outputs

This section describes the display outputs required to support the functions outlined within this document. In this section it is noted where requirements are expected as a part of existing or planned functionality.

3.1.4.1 Airport Layout View

3.1.4.1.1 TFMS must display airport layout map elements in the airport layout view in accordance with the FAA Design Standard FAA-E-2493, National

Airspace System (NAS) Visual Specification for Airport Surface

Applications (VSASA), Sections 3.1.1.1 and 3.1.2. [FA-SSD373]

3.1.4.1.2 TFMS must search for aircraft by ACID within the Airport Layout View based on user input. [FA-SSD308]

3.1.4.1.3 TFMS must identify an aircraft icon on the airport layout upon user search input of the ACID. [FA-SSD374]

3.1.4.1.4 TFMS must identify an aircraft on the flight list upon user search input of the ACID. [FA-SSD375]

3.1.4.1.5 TFMS must display all airport aircraft stands. [FA-SSD376]

3.1.4.1.6 TFMS must display all runways. [FA-SSD377]

3.1.4.1.7 TFMS must display all taxiways. [FA-SSD378]

3.1.4.1.8 TFMS must display all ramp areas, to include ramp entry and exit points.

[FA-SSD379]

3.1.4.1.9 TFMS must display all building and structures on the airport surface. [FA-

SSD380]

3.1.4.1.10 TFMS must display all de-icing pads. [FA-SSD381]

3.1.4.1.11 TFMS must display airport aircraft stand identification (including gate numbers) based on user input. [FA-SSD382]

3.1.4.1.12 TFMS must display runway identification on the airport layout view based on user input. [FA-SSD383]

3.1.4.1.13 TFMS must display taxiway identification on the airport layout view based on user input. [FA-SSD384]

3.1.4.1.14 TFMS must display ramp identification on the airport layout view based on user input. [FA-SSD385]

3.1.4.1.15 TFMS must display building and structure identification on the airport layout view based on user input. [FA-SSD386]

3.1.4.1.16 TFMS must display ramp entry and exit point identification on the airport layout view based on user input. [FA-SSD387]

3.1.4.1.17 TFMS must display de-icing pad identification on the airport layout view based on user input. [FA-SSD388]

3.1.4.1.18 TFMS must display adapted airport layout views based on user input.

[FA-SSD389]

3.1.4.1.19 TFMS must depict the airport layout configuration in the Airport Layout

View. [FA-SSD390]

Note: Airport Layout Configuration includes a textual description of the current airport configuration, including AARs and ADRs, if applicable.

3.1.4.1.20 TFMS must acknowledge a displayed notification based on user input.

[FA-SSD391]

3.1.4.1.21 Current Airport Resource Information

The Current Airport Resource Information originates from TFDM, and the following set of requirements allows the user to toggle individual display attributes.

3.1.4.1.21.1 TFMS must distinguish between current runways used for arrival and departures on the airport layout view based on user input. [FA-SSD394]

3.1.4.1.21.2 TFMS must indicate the current runway open/closed status on the airport layout view based on user input. [FA-SSD395]

3.1.4.1.21.3 TFMS must indicate current taxiway segments open/closed status on the airport layout view based on user input. [FA-SSD396]

3.1.4.1.21.4 TFMS must indicate current ramp open/closed status on the airport layout view based on user input. [FA-SSD397]

3.1.4.1.21.5 TFMS must indicate current ramp entry and exit point(s) open/closed status on the airport layout view based on user input. [FA-SSD398]

3.1.4.1.21.6 TFMS must indicate partial runway closure status on the airport layout view based on user input. [FA-SSD400]

3.1.4.1.22 Scheduled Airport Resource Information

The Scheduled Airport Resource Information originates from TFDM, and the following set of requirements allows the user to toggle individual display attributes.

3.1.4.1.22.1 TFMS must display scheduled runway arrival and departure usage based on user input. [FA-SSD404]

3.1.4.1.22.2 TFMS must display the scheduled runway open/closed status based on user input. [FA-SSD405]

3.1.4.1.22.3 TFMS must display scheduled taxiway open/closed status based on user input. [FA-SSD406]

3.1.4.1.22.4 TFMS must display scheduled ramp open/closed status based on user input. [FA-SSD407]

3.1.4.1.22.5 TFMS must display scheduled ramp entry and exit point(s) open/closed status based on user input. [FA-SSD408]

3.1.4.1.22.6 TFMS must indicate scheduled partial runway closure status on the airport layout view based on user input. [FA-SSD401]

3.1.4.1.23 Airport –Related Notifications

Data used to generate Airport-Related Notifications originates from TFDM, and the following set of requirements allows the user to toggle individual display attributes.

3.1.4.1.23.1 TFMS must display a notification in the event of a change in airport configuration. [FA-SSD411]

3.1.4.1.23.2 TFMS must display a notification based on user input in the event of a change in runway open/closed status. [FA-SSD413]

3.1.4.1.23.3 TFMS must display a notification based on user input in the event of a change in taxiway open/closed status. [FA-SSD414]

3.1.4.1.23.4 TFMS must display a notification based on user input in the event of a change in ramp open/closed status. [FA-SSD415]

3.1.4.1.23.5 TFMS must display a notification based on user input in the event of a change in ramp entry and exit point open/closed status. [FA-SSD416]

3.1.4.1.24 Surface Surveillance Track Data

TFMS system requirements and performance parameters specified herein requiring surface surveillance data must be achieved using only that data from the surface surveillance data coverage volume. [FA-SSD419]

Note: Surface Surveillance Coverage Volume: The area in which surface surveillance is certified to meet its performance parameters, including accuracy, update rate, and false target rates. Typically includes the airport movement area, the airspace 300 feet above the airport movement area, and the arrival corridors out to five miles from the end of the threshold, including non-standard approach corridors, as well as locally adapted areas used by Air Traffic personnel.

3.1.4.1.24.1 TFMS must display aircraft positions from the ASDE-X/ASSC surface surveillance system in accordance with the FAA Design Standard FAA-E-

2493, National Airspace System (NAS) Visual Specification for Airport

Surface Applications (VSASA), Section 3.1.6.1.1. [FA-SSD420]

3.1.4.1.24.2 TFMS must display vehicle positions from the ASDE-X/ASSC surface surveillance system in accordance with the FAA Design Standard FAA-E-

2493, National Airspace System (NAS) Visual Specification for Airport

Surface Applications (VSASA), Section 3.1.6.1.1. [FA-SSD421]

3.1.4.1.24.3 TFMS must provide a notification when an aircraft track under ASDE-

X/ASSC surface surveillance is dropped, suspended, or detection is lost.

[FA-SSD422]

Note: Indication of an ASDE-X/ASSC surface surveillance track which has been dropped, suspended, or lost is provided in the data received from the ASDE-X/ASSC system for the individual track.

3.1.4.1.24.4 TFMS must allow the user to enable/disable the notification of all ASDE-

X/ASSC surface surveillance track drops, suspends, or lost detections in the airport layout view. [FA-SSD423]

3.1.4.1.24.5 TFMS must geographically filter the display of aircraft positions on the airport layout view based on adaptation. [FA-SSD424]

Note: This allows the display masking of aircraft positions for specified areas on the airport surface in the Airport Layout View.

3.1.4.1.24.6 TFMS must filter by altitude the display of aircraft positions on the airport layout view based on adaptation. [FA-SSD425]

Note: This allows the display masking of aircraft positions over/below a specified altitude in the Airport Layout View.

3.1.4.1.24.7 TFMS must geographically filter the display of vehicle positions on the airport layout view based on adaptation. [FA-SSD426]

3.1.4.1.25 Display of Surface Surveillance Icons

3.1.4.1.25.1 Aircraft Icons

3.1.4.1.25.1.1 Aircraft Icon Differentiation

3.1.4.1.25.1.1.1 TFMS must differentiate the display of aircraft icons by whether the flight is an arrival or a departure based on user input. [FA-SSD430]

Note: Requirement represents existing TFMS functionality.

3.1.4.1.25.1.1.2 TFMS must differentiate the display of aircraft icons by departure runway assignment based on user input. [FA-SSD431]

3.1.4.1.25.1.1.3 TFMS must differentiate the display of aircraft icons by arrival runway assignment based on user input. [FA-SSD432]

3.1.4.1.25.1.1.4 TFMS must differentiate the display of aircraft icons by aircraft wake category based on user input. [FA-SSD433]

3.1.4.1.25.1.1.5 TFMS must differentiate the display of aircraft icons by the following departure constraints: Miles in Trail (MIT), Minutes in Trail (MINIT), Departure Stop (DS), Collaborative Trajectory Options Program (CTOP), Ground Delay Program (GDP), Airspace Flow Program (AFP), Reroute, Ground Stop (GS), Time-Based Metering, and Departure Metering

Program (DMP). [FA-SSD434]

Note: It is expected for TFMS to receive Departure Stop, Time-Based

Metering, and Departure Metering information.

3.1.4.1.25.1.1.6 TFMS must differentiate the display of aircraft icons by departure fix based on user input. [FA-SSD435]

3.1.4.1.25.1.1.7 TFMS must differentiate the display of aircraft icons by destination airport based on user input. [FA-SSD961]

3.1.4.1.25.1.1.8 TFMS must differentiate the display of aircraft icons by flights predicted to traverse each departure fix during user selectable increments based on user input. [FA-SSD436]

Note: User selectable time increment is expected to be 5 to 60 minutes.

3.1.4.1.25.1.1.9 TFMS must differentiate the display of aircraft icons by flights departing over a fix where the departure fix demand exceeds a user defined threshold for a user selectable increment (5 min to 30 min) for 1 hour into the future based on user input. [FA-SSD437]

3.1.4.1.25.1.1.10 TFMS must differentiate the display of aircraft icons for aircraft with an

Estimated Departure Control Time (EDCT) within user defined time increments based on user input. [FA-SSD438]

3.1.4.1.25.1.1.11 TFMS must differentiate the display of aircraft icons for aircraft with a

Call for Release (CFR) within user defined time increments based on user input. [FA-SSD439]

3.1.4.1.25.1.1.12 TFMS must differentiate the display of aircraft icons by aircraft with a predicted total taxi time (departure OUT to OFF) that exceeds a user defined threshold time parameter based on user input. [FA-SSD440]

3.1.4.1.25.1.1.13 TFMS must differentiate the display of aircraft icons by aircraft with a predicted total taxi time (arrival ON to IN) that exceeds a user defined threshold time parameter based on user input. [FA-SSD441]

3.1.4.1.25.1.1.14 TFMS must differentiate the display of aircraft icons by aircraft with an

ETD that exceeds a user selected time parameter based on user input. [FA-

SSD442]

3.1.4.1.25.1.1.15 TFMS must differentiate the display of aircraft icons with an elapsed taxi time that exceeds a user selected time parameter based on user input. [FA-

SSD443]

3.1.4.1.25.1.1.16 TFMS must differentiate the display of aircraft icons by current delay time for user defined time increments based on user input. [FA-SSD444]

3.1.4.1.25.1.1.17 TFMS must differentiate the display of aircraft icons by aircraft with a predicted delay time that exceeds a user defined threshold time parameter based on user input. [FA-SSD445]

3.1.4.1.25.1.1.18 TFMS must differentiate departure aircraft icons for flights with routes that do not comply with required reroute advisories based on user input.

[FA-SSD446]

3.1.4.1.25.1.1.19 TFMS must differentiate the display of aircraft icons by the following route approval status if available: Cleared as Filed (CAF), No Route

Available (NRA), Terminal En Route Control (TEC), Revision (REV), Not Read (NR) based on user input. [FA-SSD447]

3.1.4.1.25.1.1.20 TFMS must differentiate the display of aircraft icons for aircraft with predicted aircraft stand conflicts based on user input. [FA-SSD449]

3.1.4.1.25.1.1.21 TFMS must differentiate the display of aircraft icons for aircraft with missed EDCTs based on user input. [FA-SSD451]

3.1.4.1.25.1.1.22 TFMS must differentiate the display of aircraft icons for aircraft with changed EDCTs based on user input. [FA-SSD452]

3.1.4.1.25.1.1.23 TFMS must differentiate the display of aircraft icons for aircraft with missed CFR times based on user input. [FA-SSD453]

3.1.4.1.25.1.1.24 TFMS must differentiate the display of aircraft icons for aircraft with changed CFR times based on user input. [FA-SSD454]

3.1.4.1.25.1.1.25 TFMS must differentiate the display of aircraft icons by airline three letter designator based on user input. [FA-SSD1005]

3.1.4.1.25.1.1.26 TFMS must differentiate the display of aircraft icons by aircraft type based on user input. [FA-SSD1006]

3.1.4.1.25.1.2 Aircraft Icon Filtering

3.1.4.1.25.1.2.1 TFMS must filter the display of aircraft icons by whether a flight is an arrival or a departure based on user input. [FA-SSD457]

3.1.4.1.25.1.2.2 TFMS must filter the display of aircraft icons by departure runway assignment based on user input. [FA-SSD458]

3.1.4.1.25.1.2.3 TFMS must filter the display of aircraft icons by arrival runway assignment based on user input. [FA-SSD459]

3.1.4.1.25.1.2.4 TFMS must filter the display of aircraft icons by aircraft wake category or weight class based on user input. [FA-SSD460]

3.1.4.1.25.1.2.5 TFMS must filter the display of aircraft icons by the following departure constraints: MIT, MINIT, DS, CTOP, GDP, AFP, Reroute, GS, DMP, Time Based Metering (TBM) based on user input. [FA-SSD461]

3.1.4.1.25.1.2.6 TFMS must filter the display of aircraft icons by departure fix based on user input. [FA-SSD462]

3.1.4.1.25.1.2.7 TFMS must filter the display of aircraft icons by flights predicted to traverse each departure fix during user selectable increments (5 min to 30 min) based on user input. [FA-SSD463]

3.1.4.1.25.1.2.8 TFMS must filter the display of aircraft icons by flights departing over a fix where the departure fix demand exceeds a user defined threshold for a user selectable increment (5 min to 30 min) for 1 hour into the future based on user input. [FA-SSD464]

3.1.4.1.25.1.2.9 TFMS must filter the display of aircraft icons for aircraft with an EDCT within user defined time increments based on user input. [FA-SSD465]

3.1.4.1.25.1.2.10 TFMS must filter the display of aircraft icons by aircraft with a CFR within user defined time increments based on user input. [FA-SSD466]

3.1.4.1.25.1.2.11 TFMS must filter the display of aircraft icons by aircraft with a predicted total taxi time (departure OUT to OFF) that exceeds a user defined threshold time parameter based on user input. [FA-SSD467]

3.1.4.1.25.1.2.12 TFMS must filter the display of aircraft icons by aircraft with a predicted total taxi time (arrival ON to IN) that exceeds a user defined threshold time parameter based on user input. [FA-SSD840]

3.1.4.1.25.1.2.13 TFMS must filter the display of aircraft icons by aircraft with a predicted

Take-Off time that exceeds a user defined threshold time parameter based on user input. [FA-SSD468]

3.1.4.1.25.1.2.14 TFMS must filter the display of aircraft icons by aircraft with an elapsed taxi time that exceeds a user defined threshold time parameter based on user input. [FA-SSD469]

3.1.4.1.25.1.2.15 TFMS must filter the display of aircraft icons by current delay time for user defined time increments based on user input. [FA-SSD470]

3.1.4.1.25.1.2.16 TFMS must filter the display of aircraft icons by predicted delay time for user defined time increments based on user input. [FA-SSD471]

3.1.4.1.25.1.2.17 TFMS must filter the display of aircraft icons by aircraft with a current delay time that exceeds a user defined threshold time parameter based on user input. [FA-SSD472]

3.1.4.1.25.1.2.18 TFMS must filter the display of aircraft icons by aircraft with a predicted delay time that exceeds a user defined threshold time parameter based on user input. [FA-SSD473]

3.1.4.1.25.1.2.19 TFMS must filter the display of departure aircraft icons for flights with routes that do not comply with required reroute advisories based on user input. [FA-SSD474]

3.1.4.1.25.1.2.20 TFMS must filter the display of aircraft icons by the following route approval status if available: CAF, NRA, TEC, REV based on user input.

[FA-SSD475]

3.1.4.1.25.1.2.21 TFMS must filter the display of aircraft icons by aircraft with predicted stand conflicts based on user input. [FA-SSD477]

3.1.4.1.25.1.2.22 TFMS must filter the display of aircraft icons by aircraft with missed

EDCTs based on user input. [FA-SSD479]

3.1.4.1.25.1.2.23 TFMS must filter the display of aircraft icons by aircraft with changed

EDCTs based on user input. [FA-SSD480]

3.1.4.1.25.1.2.24 TFMS must filter the display of aircraft icons by aircraft with missed CFR times based on user input. [FA-SSD481]

3.1.4.1.25.1.2.25 TFMS must filter the display of aircraft icons for aircraft with changed

CFR times based on user input. [FA-SSD482]

3.1.4.1.25.1.2.26 TFMS must filter the display of aircraft icons by destination airport based on user input. [FA-SSD960]

3.1.4.1.25.1.2.27 TFMS must filter the display of aircraft icons by airline three letter designator based on user input. [FA-SSD1007]

3.1.4.1.25.1.2.28 TFMS must filter the display of aircraft icons by aircraft type based on user input. [FA-SSD1008]

3.1.4.1.26 Aircraft Icon Data Tag

3.1.4.1.26.1 Display of Aircraft Icon Data Tag

3.1.4.1.26.1.1 TFMS must display a data tag containing the Aircraft ID (ACID) for each displayed aircraft icon. [FA-SSD489]

3.1.4.1.26.1.2 TFMS must display the aircraft type (Piston, Turboprop, Jet) within the aircraft data tag based on user input. [FA-SSD492]

3.1.4.1.26.1.3 TFMS must display aircraft wake turbulence category (e.g. RECAT, Heavy, 757) within the aircraft data tag based on user input. [FA-SSD493]

3.1.4.1.26.1.4 TFMS must display the flight’s assigned stand in the aircraft data tag based on user input. [FA-SSD496]

3.1.4.1.26.1.5 The Aircraft Icon Data Tag elements must be updated dynamically upon receipt of updated information. [FA-SSD497]

3.1.4.1.26.1.6 TFMS must display free-text messages in the aircraft data tag based on user input. [FA-SSD498]

3.1.4.1.26.1.7 TFMS must permit the user to enter free-text messages in the aircraft data tag. [FA-SSD499]

3.1.4.1.26.1.8 TFMS must display scratchpad data from STARS (scratchpad 1 and scratchpad 2, if available) in the aircraft data tag based on user input. [FA-

SSD501]

3.1.4.1.26.1.9 TFMS must manually offset a single data tag based on user input. [FA-

SSD1009]

3.1.4.1.26.1.10 TFMS must automatically offset all data tags based on user input. [FA-

SSD1010]

3.1.4.1.26.2 Departure Aircraft Icon Data Tag

3.1.4.1.26.2.1 TFMS must display the predicted total departure delay time for a flight within the aircraft data tag based on user input. [FA-SSD490]

3.1.4.1.26.2.2 TFMS must display the current departure delay time for a flight within the aircraft data tag based on user input. [FA-SSD491]

3.1.4.1.26.2.3 TFMS must display elapsed taxi time within the aircraft data tag based on user input. [FA-SSD494]

3.1.4.1.26.2.4 TFMS must display the predicted total taxi time (departure OUT to OFF) for the flight in the aircraft data tag based on user input. [FA-SSD841]

3.1.4.1.26.2.5 TFMS must display the predicted total taxi time (arrival ON to IN) for the flight in the aircraft data tag based on user input. [FA-SSD495]

3.1.4.1.26.2.6 TFMS must display the flight’s departure runway assignment in the aircraft data tag for departures based on user input. [FA-SSD503]

3.1.4.1.26.2.7 TFMS must display the flight’s number in the departure sequence in the aircraft data tag for departures based on user input. [FA-SSD504]

3.1.4.1.26.2.8 TFMS must display the flight’s planned departure fix in the aircraft data tag for departures based on user input. [FA-SSD505]

3.1.4.1.26.2.9 TFMS must display the flight’s planned destination in the aircraft data tag for departures based on user input. [FA-SSD506]

3.1.4.1.26.2.10 TFMS must accept user input to change flight-specific departure route approval status. [FA-SSD306]

Note: This is necessary for DSP subsumption.

3.1.4.1.26.2.11 TFMS must display the route approval status if available (e.g., CAF, NRA, TEC, REV) in the aircraft data tag for departures based on user input. [FA-SSD507]

3.1.4.1.26.2.12 TFMS must display the reroute revision number (e.g., R1, R2, etc.) in the aircraft…