TFDM System Specification Document.pdf

ATTACHMENT J-6

System Specification Document (SSD)

Terminal Flight Data Manager (TFDM)

SYSTEM SPECIFICATION DOCUMENT (SSD)

FAA-E-41100

Document Number: SSD-PMO-02-TFDM-14-001 Rev. 16

March 16, 2026 Federal Aviation Administration

800 Independence Avenue SW Washington, DC 20591

C. Douglas Swol Date Program Manager (A) Terminal Flight Data Manager (TFDM), AJM-224 i

Revision Record

Revision Date Description Approval

- 03/06/2015 Screening for Information Request (SIR) Version 1.0

DCR-TFDM-009

Total Requirements Must Statement Count = 1196

1 05/28/2015 Updated based on Screening for Information Request (SIR) Questions

Count = 1198

2 04/08/2016 Updated based on Post SIR Review, EFSTS requirements

Count = 1210

3 04/05/2017 Updated based on SRR, EFSTS Subsumption, and ARMT Subsumption

DCR-TFDM-071

Count = 1224

4 06/05/2017 Updated based on VRTM changes and AJV-7

DCR-TFDM-081

Count = 1223

5 06/23/2017 Updated based on XL Tower configuration and M&C approach

DCR-TFDM-084

Count = 1221

6 09/25/2017 Updated based on CDR and Security Work Group

DCR-TFDM-106

7 12/08/2017 Updated based on Work Groups and Build 2 Meetings

DCR-TFDM-109

Count = 1214

8 07/09/2018 Updated based on Build 2 SRR and Work Group Meetings

DCR-TFDM-119

9 03/09/2020 Updated based on Working Group Meetings and Build 2 Development

DCR-TFDM-127

Count = 1232

10 07/13/2020 Updated based on multiple Change Requests

DCR-TFDM-129

Count = 1244

11 04/09/2021 Updated based on multiple Change Requests

DCR-TFDM-137

Count = 1246

12 10/17/2022 Updated based on multiple Change Requests

DCR-TFDM-141

Count = 1249

13 04/10/2023 Removed Appendix I VTRM and minor clarification to SSD10604

DCR-TFDM-142

Count = 1249

14 10/17/2023 Updated based on multiple Change Requests

DCR-TFDM-145

Count = 1253

15 03/06/2025 Updated based on multiple Change Requests associated with B2.3 and updates in TFDM fPRD Rev 2.

DCR-TFDM-146

Count = 1247

16 03/16/2026 Updated based on multiple Change Requests associated with B2.4, B2.5, B2.5T.

DCR-TFDM-147

Count = 1245 iv

This Page Intentionally Left Blank v

Table of Contents

1 SCOPE AND OPERATIONAL CONCEPT

1.1 PURPOSE & DOCUMENT SCOPE

1.2 OPERATIONAL CONCEPT

1.3 ASSUMPTIONS

2 APPLICABLE DOCUMENTS

2.1 COMPLIANCE DOCUMENTS

2.1.1 FAA Documents

2.1.2 FAA Orders and Standards

2.1.3 Other Documents

2.1.4 Government Compliance Documents

3 REQUIREMENTS

3.1 SYSTEM DESCRIPTION

3.1.1 System Overview

3.1.2 Services

3.1.3 TFDM Configurations

3.1.4 Implementation

3.1.5 Tower Size Categories

3.1.6 NAS Systems Replacement and TFDM Subsumptions

3.2 FUNCTIONAL CAPABILITIES

3.2.1 General Requirements

3.2.2 TFDM Processing

3.2.3 TFDM Displays

3.2.4 System Administration Support and Monitor & Control

3.2.5 Adaptation Requirements

3.3 INTEGRATION AND INTERFACE REQUIREMENTS

3.3.1 Functional Integration

3.3.2 Interfaces

3.4 PERFORMANCE REQUIREMENTS

3.4.1 Design Workload

3.4.2 Adaptation Limits

3.4.3 Response Times

3.4.4 Functional and Event Times

3.4.5 System Capacity

3.4.6 Reliability, Maintainability, and Availability (RMA) Requirements

3.5 DESIGN AND CONSTRUCTION AND ENVIRONMENTAL, OCCUPATIONAL SAFETY AND HEALTH (EOSH)

3.5.1 Design and Construction

3.5.2 Environmental, Occupational Safety and Health (EOSH)

3.6 SECURITY REQUIREMENTS

vi

3.6.1 System Integrity

3.6.2 Availability

3.6.3 Access Control

3.6.4 Identification and Authentication

3.6.5 Confidentiality

3.6.6 Non-Repudiation

3.6.7 Malicious Activity

3.6.8 Security Management

3.6.9 Security Audit

3.6.10 Reserved

3.7 SYSTEM SUPPORT

3.7.1 General Requirements

3.7.2 Support Tools

3.7.3 Second-Level Support

3.7.4 Depot Level Support

3.7.5 Quality Assurance Support

3.7.6 Training Support

3.8 TRANSITION REQUIREMENTS

3.8.1 General

4 VERIFICATION

4.1 VERIFICATION

4.1.1 Verification Phases

4.1.2 Verification Methods

APPENDIX A GLOSSARY TERMS

APPENDIX B ACRONYMS

APPENDIX C DATA SETS AND ADAPTATION TABLES

APPENDIX C.1 ELECTRONIC FLIGHT DATA FULL FLIGHT DATA SET

APPENDIX C.2 PARAMETERS TO BE ADAPTED IN TFDM PROCESSING

APPENDIX C.3 EFD ADAPTATION TABLE FOR PROPOSED FLIGHT TIME PRIOR TO FLIGHT PLAN TIME-OUT

APPENDIX C.4 CONFIGURABLE SETTINGS FOR C.3

APPENDIX C.5 TRAFFIC FLOW DATA ADAPTATION TABLE

APPENDIX C.6 MAR ADAPTATION TABLE

APPENDIX C.7 MAR AIRPORT RESOURCE DATA

APPENDIX C.8 MAR AIRPORT CONFIGURATION DATA

APPENDIX C.9 PSS ADAPTATION TABLE

APPENDIX C.10 PSM ADAPTATION TABLE

APPENDIX C.11 MR&A ADAPTATION TABLE

APPENDIX C.12 SAS ADAPTATION TABLE

APPENDIX C.13 MULTIPLE SOURCE DATA HIERARCHY

vii

APPENDIX D CONFIGURATION B REQUIREMENTS

APPENDIX E RBS PRINCIPLES

APPENDIX F RESERVED

APPENDIX G RDR ACCURACY CALCULATION

APPENDIX H FLIGHT STATES AND TRANSITIONS

APPENDIX I RESERVED

viii

List of Figures

FIGURE 1-1: TFDM OV-1 “TO-BE”

FIGURE 3-1: TFDM OPERATIONAL AND SYSTEM VIEW

ix

List of Tables

TABLE 3-1: TFDM SERVICES BY CONFIGURATION

TABLE 3-2: NAS SYSTEMS REPLACEMENT AND TFDM SUBSUMPTIONS

TABLE 3-3: NOTIFICATIONS

TABLE 3-4: TFDM REMOTE INPUT MESSAGE RATES

TABLE 3-5: CONTROLLER COMMAND RATES

TABLE 3-6: SURFACE TRAFFIC MANAGEMENT COMMAND RATES

TABLE 3-7: SIGNIFICANT EVENT RATES

TABLE 3-8: MINIMUM DISPLAY ITEM SIMULTANEOUS COUNTS

TABLE 3-9: DATA ITEM ADAPTATION LIMITS

TABLE 3-10 COLD & WARM START

TABLE 3-11: TFDM SERVICE CRITICALITY

x

This Page Intentionally Left Blank

1 SCOPE AND OPERATIONAL CONCEPT

1.1 Purpose & Document Scope

This System Specification Document (SSD) establishes the functional and performance requirements for the TFDM System.

The TFDM System supports new services that provide automation support to current, manually intensive operations and replaces critical, antiquated components in Airport Traffic Control Towers (ATCTs) of selected airports in the National Airspace System (NAS). This document includes requirements for the following new services: Electronic Flight Data (EFD); Traffic Flow Data management (TFD); Airport Resources Management (ARM); Surface Scheduling (SS); Surface Metering (SM); Metrics, Reporting & Analysis (MRA); System Administration and Support (SAS); and Monitoring and Control (M&C). This document also includes external system interfaces support, human factors, security, design and construction, transition, and system performance requirements.

1.2 Operational Concept

TFDM provides selected ATCTs with an automation system and associated displays including the capability to electronically process and distribute flight and airport management data to different operational positions in the tower. In addition, TFDM contains advanced surface modeling and simulation tools that assist tower managers and controllers in performing surface management tasks and improving airport surface operations’ efficiency.

The TFDM OV-1 “To-Be” Operational View (Figure 1-1) identifies the operational systems, users, data flows and operations supported by TFDM. The OV-1 represents three (3) main aspects of operations:

flight operations (blue domain), air traffic operations (yellow domain), and TFDM operations (green domain). As different entities in the NAS communicate their data to the tower (blue and yellow arrows), TFDM integrates that data from multiple Air Traffic Control (ATC) domains to provide new services.

Figure 1-1: TFDM OV-1 “To-Be”

1.3 Assumptions

This section details the major assumptions about the NAS at the time TFDM becomes operational.

Operating Environment

• Data exchange between TFDM and external systems is defined by the interface and data exchange requirements based on System Wide Information Management (SWIM) or direct communications based on Transmission Control Protocol/Internet Protocol TCP/IP.

• TFDM will only have access to surface surveillance data from certified FAA systems: Airport Surface Detection Equipment – Model X (ASDE-X) and Airport Surface Surveillance Capability

(ASSC).

TFDM Architecture

• TFDM requirements can be met with different architectural solutions, i.e., fully distributed components, or a hybrid of distributed and centralized components. Whichever architectural solution is selected, it must meet the availability levels and availability design criteria contained within this SSD while minimizing program specific interfacility point-to-point communications.

For example, the EFD service is considered efficiency critical and can be achieved with high availability Wide Area Network (WAN) communications services. However, EFD has a requirement that the EFD service will continue to operate in the event of data communications failures at any local ATCT. Additionally, the surface management and scheduling service, if centralized, is considered efficiency critical—but the loss of that service at a single airport may not be efficiency critical, depending on the loss of that service at that specific airport and its impact on the NAS.

• The FAA is responsible for communication provisioning and costs within the FAA system boundary. Therefore, the FAA will require certain types of interfaces to minimize FAA communication costs.

TFDM ATCT Processing

• For each ATCT, TFDM processing components should have their own M&C and SAS capabilities.

TFDM ATCT Processing Assumptions

• For each ATCT, TFDM uses existing ATCT space and cooling.

TFDM Interface Guidelines

• Where available and when data is not local, SWIM interfaces are preferred.

• Use FTI telecommunication services.

2 APPLICABLE DOCUMENTS

The following specifications, handbooks, orders, standards, and drawings form a part of this document and are applicable to the extent specified herein Paragraph 2.1 Compliance Documents. The latest version of these documents applies. In the event of conflict between this document and any of the applicable documents cited below, the provisions of this System Specification Document apply.

a. Copies of Federal Aviation Administration (FAA) specifications and interface documents may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center APA-230, 800 Independence Avenue SW, Washington, DC 20591, 202-267-3484.

Requests should fully identify material desired and cite the solicitation or contract number.

b. Requests for copies of documents not covered in the preceding paragraph should be addressed to the Contracting Officer (CO). Requests should fully identify material desired and cite the solicitation or contract number.

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

d. Copies of American National Standard Institute (ANSI)/American Society of Quality Control (ASQC) ANSI/ASQC-Q9001-2008 and International Standards Organization (ISO) 9000- 3:2004 can be obtained from the following source: American Society for Quality Control P.O. Box 3005, Milwaukee, WI 53201-3005 or 600 North Plankinton Avenue, Milwaukee, WI 53203 Phones: 414-272-8575 or 800-984-4323. The Fax is: 414-272-1734.

2.1 Compliance Documents

2.1.1 FAA Documents

Document Name Document Title (Cover Page)

FTI Time Source Service NTP/PTP User Guide

STDDS JMSDD Publication Service

(TAIS)

SWIM Terminal Data Distribution System (STDDS) JAVA Messaging Service Data Dictionary (JMSDD) for Terminal Automation Information Service (TAIS)

SWIM Governance Policies System Wide Information Management (SWIM) Governance Policies

TBFM JMSDD Publication Service

(MIS)

Time Based Flow Management (TBFM) JAVA Messaging Service Description Document Metering Information Service

(MIS)

TFDM ASDE-X IRD Terminal Flight Data Manager (TFDM) and Airport Surface Detection Equipment – Model X (ASDE-X) Interface Requirements Document (IRD)

Document Name Document Title (Cover Page)

TFDM ASSC IRD Terminal Flight Data Manager (TFDM) and Airport Surface Surveillance Capability (ASSC) Interface Requirements Document (IRD)

TFDM FDIO IRD Terminal Flight Data Manager (TFDM) and Flight Data Input Output (FDIO) Interface Requirements Document (IRD)

TFDM RMLS WSRD (TRP) Terminal Flight Data Manager (TFDM) Remote Monitoring and Logging System (RMLS) Publication (TRP) Web Service Requirements Document (WSRD)

TFDM STARS IRD Terminal Flight Data Manager (TFDM) and Standard Terminal Automation Replacement System (STARS) Interface Requirements Document (IRD)

TFDM TBFM WSRD Request Response Service (RTCS)

Time Based Flow Management (TBFM) Web Service Requirements Document (WSRD) Release Time Coordination Service (RTCS)

TFDM TDLS IRD Terminal Flight Data Manager (TFDM) and Tower Data Link Services (TDLS) Interface Requirements Document (IRD)

TFDM Terminal Publication (TTP)

WSRD

TFDM Terminal Publication (TTP) WSRD

TFDM Small UPS Specification TFDM Small Uninterruptible Power Supply (UPS) Specification

TFDM TEMP TFDM Test and Evaluation Master Plan

TFMS WSDD Publication Service (TFMData)

Traffic Flow Management System Web Service Description Document (WSDD) Traffic Flow Management Data (TFMData)

TFMS WSDD Publication Service (TFMData)

Traffic Flow Management System Web Service Description Document (WSDD) Traffic Flow Management Data (TFMData)

2.1.2 FAA Orders and Standards

Document Title

DOT/FAA/CT-03/05 HF-STD-001 Human Factors Design Standard for Acquisition of Commercial Off-The-Shelf

DOT FAA Specification FAA-G- 2100H

Electronic Equipment, and General Requirements

FAA Order 1050.10C Prevention, Control, and Abatement of Environmental Pollution at FAA Facilities

FAA Order 1050.20A Airway Facilities Asbestos Control Program

FAA Order 1370.121 FAA Information Security and Privacy Program & Policy

Document Title

FAA Order 3900.19 Occupational Safety and Health Program

FAA Order 6000.5 Facility, Service and Equipment Profile (FSEP)

FAA Order 6950.2 Electrical Power Policy Implementation at National Airspace System Facilities

FAA Order 6950.27 Short Circuit Analysis and Protective Device Coordination Study

FAA Order 6980.25 Maintenance of Batteries for Standby Power

FAA Order JO 7210.55 Operational Data Reporting Requirements

FAA Order JO 7110.65 Air Traffic Control

FAA-STD-019E Lightning and Surge Protection, Grounding, Bonding, and Shielding Requirements for Facilities and Equipment

2.1.3 Other Documents

Document Title

AIXM Aeronautical Information Exchange Model (AIXM) Release 5.1, EUROCONTROL/FAA, February 1, 2010.

FIXM Flight Information Exchange Model (FIXM) Version 2.0, EUROCONTROL/FAA, August 22, 2013.

iWXXM ICAO Meteorological Information Exchange Model (iWXXM) Version 1.0, September 2013.

2.1.4 Government Compliance Documents

Document Title

9 CFR 1926 Safety and Health Regulations for Construction

29 CFR 1910 Occupational Safety and Health Standards

29 CFR 1926 Safety and Health Regulations for Construction

40 CFR 761 Polychlorinated Biphenyls (PCBs) Manufacturing, Processing, Distribution in Commerce, AND Use Prohibitions

47 CFR Part 15 Federal Communications Commission (FCC) Class A, (47 CFR Part 15)

Executive Order (EO) 13423 Strengthening Federal Environmental, Energy and Transportation Management

Executive Order (EO) 13514 Federal Leadership in Environmental, Energy, and Economic Performance

3 REQUIREMENTS

3.1 System Description

3.1.1 System Overview

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 is deployed 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, data exchange with stakeholders and 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.

3.1.2 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 the 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.

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 Surface Metering Program (SMP) parameters by the airport's designated Traffic Management Coordinator (TMC), Operational Supervisor (OS), or Controller in Charge (CIC) to optimize performance for any given operational environment. With these SMP parameters, PSM detects when a demand/capacity imbalance is predicted to occur.

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 TFDM representation in Figure 3-1.Figure 3-1

Figure 3-1: TFDM Operational and System View

3.1.3 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 (EFD) with some selected surface scheduling, traffic flow data, airport resource management capability, and limited data exchange with Flight Operator System (FOS)

Table 3-1 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 (see Paragraph 3.1.6.

for NAS systems subsumption). For a complete listing of the Configuration B requirements see 0.

Table 3-1: TFDM Services by Configuration

TFDM Services Configuration A Configuration B

EFD Electronic Flight Data Full Full

SS Surface Scheduling Full Selected

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

3.1.4 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.

3.1.5 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 Ground 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.

3.1.6 NAS Systems Replacement and TFDM Subsumptions

Table 3-2 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 [to be replaced by FMDS]). The requirements that were allocated to TFMS are now part of the Flow Management Data & Services (FMDS) portfolio. The TFDM SSD details the requirements for the legacy systems’ functions which the TFDM System is implementing.

Table 3-2: NAS Systems Replacement and TFDM Subsumptions

System Subsumed Components Subsumed by TFDM

Strip Bays All

Drop Tubes All

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

ARMT (Airport Resource Management Tool) with SMA (Surface Movement Advisor)

All (allocated between TBFM, TFDM and TFMS to be replaced by FMDS)

AEFS (Advanced Electronic Flight Strip) All

DSP (Departure Spacing Program) All (allocated between TBFM, TFDM, and TFMS to be replaced by FMDS)

3.2 Functional Capabilities

3.2.1 General Requirements

3.2.1.1 The TFDM System must [SSD10864] enable all TFDM Services identified in Table 3-1 by default based on adaptation.

3.2.1.2 The TFDM System must [SSD12953] disable individual TFDM Services identified in Table 3-1 based on adaptation.

3.2.1.3 The TFDM System must [SSD10459] enable all TFDM Service(s) functionality based on adaptation.

3.2.1.4 The TFDM System must [SSD2990] select the data used in processing when the same data is received from multiple sources based on adapted hierarchical order.

3.2.2 TFDM Processing

3.2.2.1 Electronic Flight Data Service

Manage Flight Data

3.2.2.1.1.1 The TFDM System must [SSD10461] create a Full Flight Data Set for each flight containing the Flight Data Elements specified in Appendix C.1.

3.2.2.1.1.2 The TFDM System must [SSD10462] update Full Flight Data Set data elements as updates are generated or received.

3.2.2.1.1.3 The TFDM System must [SSD742] store the Full Flight Data Set as specified in Appendix C.1 as the Full Flight Data Set for every flight.

3.2.2.1.1.4 The TFDM System must [SSD2890] truncate EFD based on user input and adaptation.

3.2.2.1.1.5 The TFDM System must [SSD2891] expand EFD based on user input and adaptation.

3.2.2.1.1.6 Reserved.

3.2.2.1.1.7 The TFDM System must [SSD13201] visually mark departure and arrival flights meeting the criteria in an adaptable set of rules.

3.2.2.1.1.8 Provide Electronic Flight Strip (EFS) Capabilities

The TFDM System must [SSD747] automatically create EFS with data fields and data elements upon receipt of flight data as defined in adaptation.

The TFDM System must [SSD757] determine the departure queue sequence based on the order of the EFS when specified in adaptation.

The TFDM System must [SSD760] assign user-selected departure routes based on adaptation.

The TFDM System must [SSD10466] provide full route clearance to the user.

The TFDM System must [SSD10946] update the No Route Available (NRA) list based on:

a. User entry

b. Route Approval Status

The TFDM System must [SSD10951] detect when an aircraft with a Controlled Time of Departure (CTD) 1) changes its Earliest Off Block Time (EOBT) and 2) the aircraft’s recalculated Estimated Time of Departure (ETD) is greater than the end of the CTD release window.

The TFDM System must [SSD764] detect when there is more than one EFS with the same call sign and differing Computer IDs (CIDs).

The TFDM System must [SSD765] cache each EFS and its changes for 24 hours.

The TFDM System must [SSD767] update the proposed flight plan departure time prior to flight plan time-out based on user input as defined in adaptation.

When the user closes a runway on the ARM GUI, the TFDM System must [SSD13164] automatically place a sticky runway closure placard at the bottom of a designated EFS bay at each position with an active EFS role/roles based on adaptation.

When the closure of the designated runway is removed from the system on the ARM GUI, the TFDM System must [SSD13165] delete/remove the runway closure placard from all designated EFS bays.

The TFDM System must [SSD13166] create the following non ERAM EFSs from STARS data based on adaptation:

a. Arrival

b. Departure

c. Overflight

Note: The adaptation is to turn on/off this functionality at the facility level and locally adapt STARS scratchpad data.

The TFDM system must [SSD13175] automatically create EFS placards from messages from external systems as specified in adaptation.

Upon user request, the TFDM System must [SSD13401] set the site ATIS code(s).

3.2.2.1.1.9 Provide EFS Movement Capabilities

The TFDM System must [SSD819] assign EFSs to the appropriate operating position and EFS bay based on adaptation.

The TFDM System must [SSD10468] transfer EFSs based on adaptation.

The TFDM System must [SSD13066] transfer EFSs between ATCTs at an airport with multiple ATCTs based on adaptation.

The TFDM System must [SSD10469] send EFS updates, amendments, and notations to operational positions.

The TFDM System must [SSD820] transfer EFD to remote ATC facilities in accordance with the FDIO IRD.

The TFDM System must [SSD821] sequence EFSs at a receiving position in the same sequence that they were transferred.

The TFDM System must [SSD10912] update an EFS as follows:

a. A copied EFS with any changes made to the original EFS

b. The original EFS with any changes made to the copied EFS

The TFDM System must [SSD10943] transfer one or more copies of an EFS based on user input.

Reserved.

The TFDM System must [SSD10470] inhibit the movement of an EFS based on adaptable criteria including TMIs, No Route Available List and user input.

Note: Inhibit the movement means preventing the EFS from transitioning to another state (i.e., prevent EFS from moving to LUAW or CFTO from LUAW). The triggers for preventing the movement of an EFS would be based on flight specific criteria such as TMIs (e.g. Ground Stop, APREQ, Reroute, Disable), NRA and user entry.

The TFDM System must [SSD10471] inhibit the progression (Line Up and Wait (LUAW), Cleared for Take-Off (CFTO), Cleared to Land (CTL)) of EFSs that are assigned to a closed runway.

Note: The user needs to be able to “depart” (discard) an EFS for the runway if the runway closes after a flight is CFTO but not yet discarded.

The TFDM System must [SSD12397] transfer the EFS to an assigned local or remote location as defined by adaptation.

The TFDM System must [SSD13167] differentiate between the following placard types based on adaptation.

a. Sticky

b. Non-Sticky

3.2.2.1.1.10 Provide Printing Capability

The TFDM System must [SSD826] send EFS to FDIO for printing.

The TFDM System must [SSD12915] receive user input to send EFS to a designated FDIO printer.

The TFDM System must [SSD10924] send EFS to a designated FDIO printer.

Reserved.

Reserved.

3.2.2.1.1.11 Provide Message Capabilities

Reserved.

The TFDM system must [SSD10475] process non flight plan messages based on adaptation.

Determine Flight State and ATC Flight State Data

3.2.2.1.2.1 The TFDM System must [SSD10477] determine the flight state for each departure aircraft according to the following states:

a. Scheduled

b. Filed

c. At Stand

d. Stand Metering Hold

e. Ramp Taxi Out

f. At Spot Out

g. Airport Movement Area (AMA) Holding

h. AMA Taxi Out

i. In Departure Queue

j. Stand Return

k. Line Up and Wait (LUAW)

l. Take Off Roll

m. Take Off Roll Abort

n. Departed

3.2.2.1.2.2 The TFDM System must [SSD10478] determine the flight state for each arrival aircraft according to the following states:

a. En route

b. Arrival

c. On Final

d. Missed Approach

e. On Runway

f. AMA Taxi In

g. AMA Holding

h. Ramp Taxi In

i. At Stand

3.2.2.1.2.3 The TFDM System must [SSD10479] assign exactly one flight state for each aircraft at any time.

3.2.2.1.2.4 The TFDM System must [SSD13043] use surface surveillance and terminal area surveillance data, when available, to determine flight and ATC flight states.

3.2.2.1.2.5 The TFDM System must [SSD894] record the time when a flight state changes.

3.2.2.1.2.6 The TFDM System must [SSD10866] determine the ATC flight state for each departure aircraft according to the following states:

a. CD

b. CD Clearance

c. GC Pending

d. GC

e. Hold

f. LC

g. LUAW

h. Cleared for Take Off

i. Departed

j. Archive

3.2.2.1.2.7 The TFDM System must [SSD10867] determine the ATC flight state for each arrival aircraft according to the following states:

a. LC Pending

b. LC

c. Cleared to Land

d. GC

e. Hold

f. Archive

3.2.2.1.2.8 The TFDM System must [SSD10868] assign exactly one ATC flight state for each aircraft at any time.

Calculate Event Times

3.2.2.1.3.1 The TFDM System must [SSD10627] calculate the following times for each departure aircraft:

a. Actual Off Block Time (AOBT)

b. Spot Arrival Time

c. Actual Movement Area Entry Time (AMAT)

d. Actual AMA Holding Start Time

e. Actual AMA Holding End Time

f. Runway Queue Entry Time

g. Runway Queue Exit Time

h. Takeoff Roll

i. Actual Take Off Time (ATOT)

3.2.2.1.3.2 The TFDM System must [SSD10628] calculate the following times for each arrival aircraft:

a. Arrival Cleared to Land Time

b. Actual Runway Time of Arrival (ARTA)

c. Actual Runway Exit Time

d. Actual AMA Holding Start Time

e. Actual AMA Holding End Time

f. Actual Spot Crossing Time

g. Actual In Block Time (AIBT)

3.2.2.1.3.3 The TFDM System must [SSD10630] calculate the actual ramp taxi duration for each departure aircraft.

3.2.2.1.3.4 The TFDM System must [SSD10632] calculate the actual AMA holding duration for each departure aircraft.

3.2.2.1.3.5 The TFDM System must [SSD10633] calculate the actual spot to queue taxi duration for each departure aircraft.

3.2.2.1.3.6 The TFDM System must [SSD10634] calculate the actual runway queue duration for each departure aircraft.

3.2.2.1.3.7 The TFDM System must [SSD10635] calculate the actual runway occupancy duration for each departure aircraft.

3.2.2.1.3.8 The TFDM System must [SSD10636] calculate the actual runway occupancy duration for each arrival aircraft.

3.2.2.1.3.9 The TFDM System must [SSD10637] calculate the actual runway exit to spot taxi duration for each arrival aircraft.

3.2.2.1.3.10 The TFDM System must [SSD10638] calculate the actual AMA holding duration for each arrival aircraft.

3.2.2.1.3.11 The TFDM System must [SSD10639] calculate the actual arrival ramp taxi duration for each arrival aircraft.

3.2.2.1.3.12 The TFDM System must [SSD10642] calculate the actual position in the queue of each aircraft.

3.2.2.1.3.13 The TFDM System must [SSD10914] calculate the Flight Operator Delay time for an aircraft whose EFS has been placed in Flight Operator Delay status.

3.2.2.2 Traffic Flow Data Management Service

The TFDM System must [SSD12956] disable Traffic Flow Data Management functionality in accordance with Appendix D based on adaptation and site-specific operational configurations.

Reserved.

Enter Traffic Management Initiatives

3.2.2.2.3.1 The TFDM System must [SSD901] accept user-entered traffic management initiatives using inputs inclusive of the following:

a. Initiative Type

b. Start Date Time,

c. End Date Time,

d. Controlled Element (i.e. resource controlled by the TMI),

e. Value associated with Restriction Type [Miles-in-Trail (MIT), MINIT] (if applicable),

f. Expected update (if applicable),

g. Reason (if applicable),

h. Aircraft engine class/es,

i. Exclusions (if applicable).

j. Altitude (if applicable).

k. Airport (if applicable).

l. NAS Element (VIA) (if applicable)

m. Qualifier (if applicable)

n. Charge To

o. Aircraft Identification (if applicable)

p. MIT/MINIT As-One

3.2.2.2.3.2 The TFDM System must [SSD10945] determine the flights affected by a TMI.

3.2.2.2.3.3 The TFDM System must [SSD916] convert MIT restrictions into MINIT restrictions using a user-selected conversion parameter as defined in adaptation.

3.2.2.2.3.4 The TFDM System must [SSD13113] assign one or more selected flights to a TMI based on user input.

3.2.2.2.3.5 The TFDM System must [SSD13114] un-assign one or more selected flights from a TMI based on user input.

3.2.2.2.3.6 The TFDM System must [SSD13127] import TMI data from the TFMdata service.

Release Times

3.2.2.2.4.1 The TFDM System must [SSD918] enable one of the following modes per Call for Release (CFR) program of requesting release times for flights subject to a call for release based on user input:

a. Automatic Mode

b. Manual Mode

3.2.2.2.4.2 When in Automatic mode, the TFDM System must [SSD921] send a release time request:

a. For a flight that is within a user-entered lead time of a user-entered departure parameter as defined in adaptation or,

b. Based on EFS Movement as defined in adaptation or,

c. For an adapted change in flight state

3.2.2.2.4.3 For a Configuration A ATCT TFDM site, when in Automatic mode, the TFDM System must [SSD10497] calculate the release time request to be the:

a. Earliest Feasible Take Off Time (EFTT) plus the CTD buffer, if the flight is not subject to a TMI

b. The latter of the Expect Departure Clearance Time (EDCT) and EFTT, if the flight is subject to a TMI and has an EDCT

3.2.2.2.4.4 For a Configuration B ATCT TFDM site, when in Automatic mode, the TFDM System must [SSD13072] calculate the release time request based on inputs inclusive of EFS order.

3.2.2.2.4.5 The TFDM System must [SSD13044] enable release time requests based on adaptation.

3.2.2.2.4.6 The TFDM System must [SSD13045] disable release time requests based on adaptation.

3.2.2.2.4.7 When in Manual mode, the TFDM System must [SSD922] send a user-entered release time request.

3.2.2.2.4.8 When a flight’s release time is cancelled, the TFDM System must [SSD923] remove the release time from the EFS for that flight.

3.2.2.2.4.9 The TFDM System must [SSD13079] enable release time requests based on the APREQ mode from TBFM.

3.2.2.2.4.10 The TFDM System must [SSD13080] disable release time requests based on the APREQ mode from TBFM.

Calculate Delays

3.2.2.2.5.1 The TFDM System must [SSD926] calculate runway departure delay as the difference between the time at which a flight used the runway minus the time at which the flight would have used the runway if it were unimpeded in its taxi and it did not incur any departure metering or an adaptable taxi value.

3.2.2.2.5.2 The TFDM System must [SSD927] calculate flight specific accumulated departure delays.

3.2.2.2.5.3 The TFDM System must [SSD10956] calculate the flight specific metering hold as the time a flight is held at the stand due to a SMP.

3.2.2.3 Airport Resource Management Service

The TFDM System must [SSD12957] disable selected Airport Resource Management functionality in accordance with Appendix D based on adaptation and site-specific operational configurations.

Schedule Airport Configuration

3.2.2.3.2.1 The TFDM System must [SSD970] schedule a user-selected airport configuration.

3.2.2.3.2.2 The TFDM System must [SSD10498] set the start time for a user scheduled airport configuration to the user-entered start time.

3.2.2.3.2.3 The TFDM System must [SSD971] set data for an airport configuration in the airport configuration schedule based on:

a. User-entered Values

b. Values in the previous Airport Configuration in the Airport Configuration Schedule

c. Default Values in the Adaptation for the Airport Configuration

3.2.2.3.2.4 The TFDM System must [SSD10869] detect when it receives airport configuration data from TBFM that conflicts with the airport configuration schedule.

3.2.2.3.2.5 The TFDM System must [SSD976] set the airport operating conditions for an airport configuration in the Airport Configuration schedule based on the latest entered/selected data input to include:

a. User-Entered Airport Operating Conditions

b. Airport Operating Conditions in the previous Airport Configuration in the Airport

Configuration Schedule

c. Default Airport Operating Conditions in the Adaptation for the Airport Configuration

3.2.2.3.2.6 The TFDM System must [SSD979] set the Airport Acceptance Rate (AAR) schedule for an airport configuration in the airport configuration schedule based on the latest entered/selected data input to include:

a. User-entered AAR Schedule for the Airport Configuration

b. Sum of the Runway Arrival Rate (RARs) for all active runways in the Scheduled

Airport Configuration

c. Default AAR Value in the Adaptation for the Scheduled Airport Configuration

3.2.2.3.2.7 The TFDM System must [SSD10870] detect when it receives an AAR schedule from TBFM or TFMS that conflicts with the AAR schedule in the airport configuration schedule.

3.2.2.3.2.8 The TFDM System must [SSD984] set the Airport Departure Rate (ADR) schedule for an airport configuration in the airport configuration schedule based on the latest entered/selected data input to include:

a. User-entered ADR Schedule for the Airport Configuration

b. Sum of the Runway Departure Rate (RDRs) for All Departure Runways in the

Scheduled Airport Configuration

c. Default ADR Value in the Adaptation for the Scheduled Airport Configuration

3.2.2.3.2.9 The TFDM System must [SSD10871] detect when it receives an ADR schedule from TFMS that conflicts with the ADR schedule in the airport configuration schedule.

3.2.2.3.2.10 The TFDM System must [SSD988] set the RAR schedule for each arrival runway in an airport configuration in the airport configuration schedule based on the latest entered/selected data input to include:

a. User-entered RAR Schedule for the Airport Configuration

b. Default RAR Value in the Adaptation for the Airport Configuration

3.2.2.3.2.11 The TFDM System must [SSD10872] detect when it receives an RAR schedule from TBFM that conflicts with the RAR schedule in the airport configuration schedule.

3.2.2.3.2.12 The TFDM System must [SSD10499] set the RDR schedule for each departure runway for an airport configuration in the Airport Configuration schedule based on the latest entered/selected data input to include:

a. User-entered RDR schedule for the Airport Configuration

b. Default RDR Value in the Adaptation for the Airport Configuration

3.2.2.3.2.13 The TFDM System must [SSD10500] detect periods of time in the Airport Configuration schedule when the AAR is not equal to the sum of the RARs.

3.2.2.3.2.14 The TFDM System must [SSD10501] detect periods of time in the Airport Configuration schedule when the ADR is not equal to the sum of the RDRs.

3.2.2.3.2.15 The TFDM System must [SSD999] remove a scheduled airport configuration from the airport configuration schedule when the user cancels a scheduled airport configuration.

3.2.2.3.2.16 The TFDM System must [SSD1000] modify the start time of a scheduled airport configuration in the airport configuration schedule when the user edits the start time.

Implement Airport Configuration

3.2.2.3.3.1 The TFDM System must [SSD1003] set the Current Airport Configuration to the user-selected airport configuration when the user implements an airport configuration.

Runway Assignment Rules

3.2.2.3.4.1 The TFDM System must [SSD1021] set the Arrival Runway Assignment Rule schedule for an Airport Configuration in the Airport Configuration Schedule based on the following data input:

a. User-entered Arrival Runway Assignment Rule schedule for the Airport Configuration

b. The Default Arrival Runway Assignment Rule

3.2.2.3.4.2 The TFDM System must [SSD1024] set the Departure Runway Assignment Rule Schedule for an Airport Configuration in the Airport Configuration Schedule based on the following data input:

a. User-entered Departure Runway Assignment Rule schedule for the Airport

Configuration

b. The Default Departure Runway Assignment Rule

3.2.2.3.4.3 The TFDM System must [SSD1027] set the start time for each Arrival Runway Assignment Rule in the Airport Configuration Schedule to the user-entered start time.

3.2.2.3.4.4 The TFDM System must [SSD1029] set the start time for each Departure Runway Assignment in the Airport Configuration Schedule Rule to the user-entered start time.

3.2.2.3.4.5 The TFDM System must [SSD1031] implement a user-selected Arrival Runway Assignment Rule.

3.2.2.3.4.6 The TFDM System must [SSD1032] implement a user-selected Departure Runway Assignment Rule.

3.2.2.3.4.7 The TFDM System must [SSD10503] remove an Arrival Runway Assignment Rule from the Arrival Runway Assignment Rule Schedule when the user cancels a scheduled Arrival Runway Assignment Rule.

3.2.2.3.4.8 The TFDM System must [SSD10504] modify the start time of a scheduled Arrival Runway Assignment Rule when the user edits the start time.

3.2.2.3.4.9 The TFDM System must [SSD10505] remove a Departure Runway Assignment Rule from the Departure Runway Assignment Rule Schedule when the user cancels a scheduled Departure Runway Assignment Rule.

3.2.2.3.4.10 The TFDM System must [SSD10506] modify the start time of a scheduled Departure Runway Assignment Rule when the user edits the start time.

What-if Model Departure Runway Assignment Rules

3.2.2.3.5.1 The TFDM System must [SSD1034] schedule the lookahead window for What-if Model of Departure Runway Assignment Rules based on user input.

3.2.2.3.5.2 The TFDM System must [SSD1035] implement the results of a What-if Model of Departure Runway Assignment Rules based on user input.

3.2.2.3.5.3 The TFDM System must [SSD1036] calculate unimpeded number of departures using each Departure Runway for the user-entered lookahead window for each adapted Departure Runway Assignment Rule.

3.2.2.3.5.4 The TFDM System must [SSD1043] calculate the number of departures using each Departure Runway for the user-entered lookahead window for each adapted Departure Runway Assignment Rule accounting for separation based on aircraft wake category.

Runway Load Balancing

3.2.2.3.6.1 The TFDM System must [SSD1065] identify alternate runway(s) for departures that are eligible for runway load balancing based on:

a. Flights that are predicted to depart during the Runway Load Balancing Lookahead

Window

b. Flights that have alternate runway(s) based on the Runway Load Balancing Rule in effect at their predicted departure time

c. At least one of the alternate runways is acceptable to the flight operator

3.2.2.3.6.2 The TFDM System must [SSD1067] use the following criteria for identifying departures eligible for runway load balancing:

a. The flights are eligible for runway load balancing

b. Moving the flights to alternate runways would result in a lower aggregate airport delay

3.2.2.3.6.3 The TFDM System must [SSD10930] calculate for each flight recommended for load balancing, the following:

a. The change in ETD

b. The change in delay

c. The change in the runway schedule

3.2.2.3.6.4 The TFDM System must [SSD1077] set the Runway Load Balancing rule lookahead window to the user-entered Runway Load Balancing Rule lookahead window.

3.2.2.3.6.5 The TFDM System must [SSD10507] set the Runway Load Balancing rule for an Airport Configuration in the Airport Configuration Schedule to the user-entered Runway Load Balancing rule.

3.2.2.3.6.6 The TFDM System must [SSD10508] stop calculations for a user cancelled Runway Load Balancing rule for an airport configuration in the Airport Configuration Schedule.

3.2.2.3.6.7 The TFDM System must [SSD1083] implement a user selected Runway Load Balancing Solution.

3.2.2.3.6.8 The TFDM System must [SSD1084] implement a user selected subset of a Runway Load Balancing Solution.

Airport Resource Status

3.2.2.3.7.1 The TFDM System must [SSD1088] schedule the open/close status of the Airport Resources based on the following input:

a. User entry

b. Default Airport Resource Data in the Adaptation

3.2.2.3.7.2 The TFDM System must [SSD10509] implement user-entered Airport Resource Open/Close Status changes.

The TFDM System must [SSD13051] cache Manage Airport Resources (MAR) operational data to include Airport Configuration, Open/Close Status for Airport Resource, and Traffic Count for 48 hours.

3.2.2.4 Surface Scheduling Service

Calculate Predicted Resource Assignments

3.2.2.4.1.1 Calculate Predicted Departure Runway Assignments

The TFDM System must [SSD1115] calculate the predicted runway assignment for every departure that is in the AMA and has not yet Taken Off.

For use in EFS, the TFDM System must [SSD1120] calculate predicted departure runway assignments for every departure using inputs inclusive of the following:

a. User entry

b. Adapted Departure Runway Assignment Rules

c. Runway balancing rules

d. Flight-Operator Provided List of Flight-Specific Acceptable/Unacceptable Runways

e. Current Airport Configuration

f. Current Airport Resource Status

For use in modeling, the TFDM System must [SSD1124] calculate predicted departure runway assignments for every departure using inputs inclusive of the following:

a. User entry

b. Adapted Departure Runway Assignment Rules

c. Runway balancing rules

d. Flight-Operator provided List of Flight-specific Acceptable/Unacceptable Runways

e. Schedule of Planned Airport Configurations

f. Schedule of Planned Airport Resource Status

When the user has not manually changed the departure runway assignment, the TFDM System must [SSD10915] detect when the departure runway assignment displayed on the electronic flight strip differs from the default that would be assigned by TFDM for the current runway configuration.

The TFDM System must [SSD13115] calculate the predicted runway assignment for every departure that has Blocked Out but is still in a Non-Movement Area (NMA).

The TFDM System must [SSD13116] calculate the predicted runway assignment for every departure that has not Blocked Out but has a Scheduled Time (e.g., P-time, L-time, (Earliest Off Block Time [EOBT]), etc.) within the TFDM Prediction Horizon.

3.2.2.4.1.2 Calculate Predicted Arrival Runway Assignments

The TFDM System must [SSD1129] calculate the predicted runway assignment for every arrival that has not yet landed and is predicted to land within the TFDM Prediction Horizon.

For use in EFS, the TFDM System must [SSD1131] calculate predicted arrival runway assignments using inputs inclusive of the following:

a. User entry

b. Arrival Runway Assignments received from STARS

c. Adapted Arrival Runway Assignment Rules

d. Current Airport Configuration

e. Current Airport Resource Status

Reserved.

For use in modeling, the TFDM System must [SSD13117] calculate predicted arrival runway assignments using inputs inclusive of the following:

a. User entry

b. Arrival Runway Assignments received from STARS

c. Adapted Arrival Runway Assignment Rules

d. Schedule of Planned Airport Configurations

e. Schedule of Planned Airport Resource Status

3.2.2.4.1.3 Calculate Predicted Spot Assignments

The TFDM System must [SSD1146] calculate the predicted spot assignment for:

a. Every Arrival that has not yet landed and is predicted to land within the TFDM

Prediction Horizon

b. Every Arrival that has landed but has not yet exited the AMA

c. Every Departure with a scheduled time (e.g., P-time, L-time, EOBT, etc.) within the

TFDM Prediction Horizon that has not yet entered the AMA

The TFDM System must [SSD1150] calculate predicted spot assignments based on the following data:

a. Assigned Stand

b. Predicted or Actual Runway

c. Adapted Spot Assignment Rules

d. Flight Operator Provided Spot Assignment

Calculate Predicted Arrival Times

3.2.2.4.2.1 The TFDM System must [SSD1157] calculate the predicted landing time for every arrival that has yet to land and is predicted to land within the TFDM Prediction Horizon.

3.2.2.4.2.2 The TFDM System must [SSD1159] calculate predicted arrival landing times based on arrival time estimates from external automation systems (e.g. ERAM/FDIO, TBFM, TFMS).

3.2.2.4.2.3 The TFDM System must [SSD1163] calculate predicted arrival landing times such that each pair of successive times is separated by the greater of the separation specified by RAR and the wake vortex separation.

Calculate Predicted Runway Schedules

3.2.2.4.3.1 Demand Adjustments

The TFDM System must [SSD1173] exclude the following departure flights for scheduling calculations for the duration of the event considered from the following:

a. Flights affected by Ramp Closure

b. Flights on the No Route Available List

The TFDM System must [SSD1177] remove non-cancelled departure flight from scheduling calculations when all of the following conditions are met:

a. The flight has not yet blocked out

b. The flight's EOBT is in the past, and

c. The current time is equal to or later than the flight's Target Movement Area entry

Time (TMAT) plus the Upper Bound of the TMAT Compliance Window parameter plus the Flight Suspension Warning…