TFDM Market Survey Industry Capability for Maintenance Sustainment Development 9.18.26 final.docx

Acquisition Sensitive--This document may contain information considered sensitive unclassified information (SUI) and would merit protection from unauthorized disclosure under 5 U.S.C, Section 552(b)(4). No information shall be released except as authorized by the Contracting Officer.

MARKET SURVEY ANNOUNCEMENT FOR TERMINAL FLIGHT DATA MANAGER (TFDM) FOLLOW-ON CONTRACT

1. Introduction The Federal Aviation Administration (FAA) is conducting this Market Survey in accordance with the FAA Acquisition Management System (AMS) Section 3.2.1.2.A.1. Its purpose is to identify capable vendors to provide Second Level Engineering (SLE), Sustainment, Development, and Implementation services for the Terminal Flight Data Manager (TFDM) system.

This is a request for information (RFI) ONLY and does NOT constitute a Request for Proposal nor a Request for Quotation. The FAA will not pay for any information received nor costs incurred in preparing the response to this Market Survey; is solely at the interested vendor’s expense; providing a response to this Market Survey neither qualify respondents nor excludes respondents from responding to the resulting Screening Information Request, if any; and - at its sole discretion, the FAA may contact any respondents to this Market Survey and request additional information.

2. Objectives

a) Identify contractors with experience and capabilities to provide future support for the operational TFDM systems and the next set of objectives for the program, including site system and software maintenance support, sustainment, cloud migration, and possible development of future enhancements and additional sites receiving TFDM services.

b) Assess the technical expertise and capacity to perform Second Level Engineering (SLE) support activities for TFDM.

3. Background The Terminal Flight Data Manager (TFDM) program delivers to tower Air Traffic Controllers (ATC) and FAA traffic managers, NAS modernization decision support capabilities that integrate flight, surface surveillance, and traffic management information. TFDM provides the tools for the collection, distribution, and update of flight data information in the terminal area to improve access to information for the safe and efficient control of air traffic.

Operational Scope: TFDM is part of Brand New Air Traffic Control System (BNATCS) with a current plan to deploy the system to 89 operational sites by the end of CY2028. The TFDM production system has been developed and operationally deployed under the existing TFDM contract and the current vendor. As of August 1, 2026, 19 TFDM site systems are operational and TFDM site implementation activities for new sites are ongoing under the current contract.

A new TFDM contract is needed to support the TFDM site and support systems and future TFDM program objectives after the operational deployment of the 89 sites. Services envisioned to be provided under the new contract include Second Level Engineering, Sustainment, Maintenance/Logistics Support, Software Maintenance, Software Development, and Site Implementation. An additional site (site 90), the ATC Tower in Anchorage, Alaska is planned to receive TFDM services pending delivery of a new automation system at the Anchorage Air Route Traffic Control Center (ZAN). It is envisioned that the deployed TFDM systems will continue NAS operations for an additional 12 or more years. Beyond the current plan to deliver TFDM systems to 89 sites and one future site (Anchorage), the FAA seeks opportunities to migrate the operational TFDM services provided by site-based systems to the Cloud, which may or may not be an FAA provided Cloud solution.

The FAA plans to have a contractual resolution for the sustainment of the TFDM system prior to the completion of the 89-site waterfall implementation schedule.

a) Key TFDM Functionality:

i. Electronic Flight Data (EFD): Electronically processes, updates, and distributes flight data to different control positions in the tower through electronic flight strips.

ii. Surface Scheduling: A Surface Management Display (SMD) assists Controllers by providing a departure scheduler with live data offering departure metering capability, runway balancing, and other surface management tools.

iii. Systems Consolidation: Combines legacy tower systems to mitigate limited cab space and equipment obsolescence.

iv. Stakeholder Collaboration: Enhances collaborative decision making and supports data publishing/ subscribing in real time with NAS stakeholders through data integration.

b) Major TFDM Benefits:

i. Improve Situational Awareness. EFD/EFS allow tower controllers to maintain an integrated view of the air traffic environment, improving their situational awareness of airport operations.

ii. Enhance Data Exchange. Enhanced traffic flow management data integration with Time Based Flow Management (TBFM) and Traffic Flow Management System (TFMS) enables airlines, controllers, and airports to share and exchange real-time data. This results in improved surface traffic management as well as improving the products produced by TFMS and TBFM.

iii. Improve Surface Management Efficiency. TFDM decision support capabilities promote safe and efficient airport operations while managing airport surface traffic sequencing and scheduling.

iv. Collaborative Decision Making for the Surface (CDM): EFD facilitates enhanced flight data exchange between controllers within the tower, those in other ATC facilities, and those overseeing TFMS. This also facilitates data exchange with aviation partners such as the airlines' flight operations centers and airport operators to support CDM.

This Market Survey will support market research and may be used for planning purposes. The FAA will review all responses submitted as input to the acquisition strategy. This Market Survey is open to all interested parties.

4. Contract Activities

The following activities are within the planned scope of the TFDM Support and Sustainment efforts:

· 24/7 TFDM system second level engineering technical support (advanced troubleshooting, root cause analysis, and engineering support) for TFDM System Help Desk and site identified TFDM issues

· Software Maintenance

· Design/develop/integrate/test software changes to resolve software maintenance issues (~10,000 SLOC per year) and interface updates with other FAA systems

· Design/develop/integrate/test Software Problem Report (PR) fixes for identified latent defects (150-200 PRs per year)

· Sustainment Engineering

· Identify system components reaching end-of-life or end-of-service dates

· Identify and quantify projected shortfalls in system component availability or service life

· Identify and quantify the projected need for system components and replacement equipment required to sustain current systems

· Identify technology opportunities and cost-effective implementation approaches to migrate operational TFDM services from site-based systems to the Cloud

· Support TFDM System Adaptation updates

· Specialty Engineering Support (security, safety, system performance, and Reliability/Maintainability/Availability (RMA)) analysis and process activities for each software release and all tech refresh efforts

· Quality Assurance and Configuration Management processes and activities to support the TFDM sustainment and development activities

· Contractor Depot Logistics Support (CDLS) for the TFDM system

· Support the existing TFDM lab hardware, software, and system administration support (WJHTC and contractor facilities) to support TFDM maintenance and development activities

· Technical support for the operational usage of the TFDM System Development Environment Tool Sets

· Regression testing program to identify any software code breakage or regression during development

· Updates to all TFDM system documentation (technical and training) impacted by software maintenance and sustainment activities

· General engineering and technical services for TFDM, as requested by the Government Contracting Officer

· Design, develop, integrate, and test a prototype for migrating TFDM Services from site-based system to the Cloud

· Program Management support of all contract activities

The following activities are within the planned scope for Software Development and Implementation support for new Functionality, Tech Refresh, Site Implementation, and Cloud Migration Needs:

· Design/develop/integrate/test software and any hardware changes to implement new Sustainment Functionality (RHEL 10 uplevel, IPv6 uplevel, new security requirements/features, etc.)

· Engineering, development, test, and deployment of Tech Refresh solutions for hardware, Commercially Available Software (CAS) products, Government approved technology opportunities, new System Enhancements, and new/modified TFDM software supporting the continuation of TFDM services to the operational sites

· Design, develop, integrate, and test a prototype for migrating TFDM Services from site-based system to the Cloud

· Specialty Engineering Support (security, safety, performance, and Reliability/Maintainability/Availability (RMA)) for each software release

· Regression testing activities to identify any software code breakage or regression

· Quality Assurance and Configuration Management processes and activities to support the TFDM sustainment activities

· Site Implementation/Deployment of new Tech Refresh hardware or TFDM services to new sites and the conversion of existing sites to Cloud solution

· Updates to all TFDM system documentation (technical and training) impacted by sustainment functionality and enhancement development activities as well as changes due to Cloud Migration

· Program Management support of the TFDM Support, Sustainment, Development, Implementation and Cloud Migration efforts

The new contract may also include Option CLINs for the development/integration/test of new TFDM system enhancements if future funding is identified and provided for TFDM enhancements. Additionally, the new contract may include Option CLINs for providing TFDM services to new sites if future requirements and funding are identified.

5. Contracting

Potential acquisition strategy for the TFDM Follow-on contract assumes a contract award in GFY2027. The estimated Period of Performance is a 5-year base period with selected concurrent one-year option CLINs and an additional 5-year option period for a total possible period of performance of ten years.

The current TFDM contractor is Leidos, Inc. of Gaithersburg, MD.

The following additional TFDM information is provided as attachments: 1) TFDM System Specification Document, 2) TFDM System Overview presentation, and 3) TFDM Sustainment Efforts/Timeline.

This Market Survey requests interested parties provide input on the information listed in Section 6.

6. Questions and Requests for Market Survey Below is a series of information requests related to the TFDM requirement. Interested vendors are requested to submit the following documentation and responses to the listed information before the deadline stated:

a) Company Information

i. Company name, address, point of contact, phone, and email.

ii. Unique Entity Identifier number and applicable NAICS code(s).

iii. Business size and socioeconomic classification (e.g., small, 8(a), SDVOSB, etc.).

b) Challenges

The FAA is aware of several challenges associated with sustaining the TFDM system and fulfilling the next set of TFDM program objectives. Interested parties should respond with their approach for mitigating the following challenges.

These challenges include but are not limited to:

i. TFDM System Availability Requirements. The TFDM system supports Efficiency-Critical and Essential services. An Efficiency-Critical service provided by the TFDM System must have a service availability of greater than or equal to 0.99998. An Essential service provided by the TFDM System must have a service availability of greater than or equal to 0.9998. Any TFDM outage has a significant impact to the site ATC operations and likely results in significant delays and monetary impacts to the aviation industry and passengers. As such, the objective is to provide continuous service for all operational TFDM systems and expeditiously respond to and resolve TFDM site issues impacting service availability. As a result, the award of the new TFDM contract must not result in increased risk to satisfying the TFDM Service Availability Requirements (0.999998) and overall NAS capability and availability.

ii. Limited Overlap with TFDM Incumbent. The Government plans for a limited overlap of the existing contract with the award of any new contract. This anticipated duration is constrained by budget and Government resources limitations.

iii. Comprehensive System and Software Design Knowledge of TFDM Software Code for Maintenance Support and Potential Future Enhancements. The new contract vendor must be capable of providing full coverage of all operational software to respond to possible system software issues impacting system availability. For latent software defects impacting service, the vendor must have comprehensive system engineering knowledge of the TFDM system to be capable of determining the problem and developing the necessary software fixes so that the impact to the operational systems can be remedied as soon as possible. Comprehensive software design knowledge of TFDM software code is also needed for the new contract vendor to be capable of successfully developing and integrating future TFDM enhancements into the production system if future funding is provided for system enhancements. The new contractor must have the ability to design/develop/integrate/test Software Problem Report (PR) fixes for identified latent defects (150-200 PRs per year) and design/develop/integrate/test software changes to resolve software maintenance issues (~10,000 SLOC per year) and interface updates with other FAA systems.

iv. Programming Languages used in the TFDM system. The table below identifies the various programming languages used in the TFDM system. The new contract vendor must be able to provide staff personnel capable of maintaining sole responsibility for sustaining the TFDM software once the overlap period with the existing contract incumbent is over.

v. TFDM Development Environment Tool Sets. The TFDM Development Environment contains the tool sets needed to deliver the TFDM system software, documentation, and support tools for each TFDM system software build. The current TFDM Development Environment tool set products include but are not limited to: Atlassian products (Bamboo, BitBucket, Confluence, Crucible, Fisheye, JIRA), IBM products (Clearcase, DOORS, Rhapsody), JIDE, Sonatype Nexus, Sonar Qube, OC Systems RootCause, and Microsoft Visual Studio Professional. The TFDM development team for the new contract vendor must be proficient with and have the ability to use the existing TFDM development environment tool sets for software development or obtain Government approval and fully implement similar development environment tool set products/services before the end of the contract overlap period with the incumbent.

vi. Comprehensive Engineering Knowledge of the TFDM System to Support TFDM System Service Restoral. The new contract vendor must provide a group of system engineers, system architects and software architects that have a detailed knowledge of all aspects of the TFDM system design, including the detailed software functionality and relationships within the design, and its external interfaces. The contractor will be responsible for 24/7 TFDM second-level engineering support in case of the loss of service or a significant problem at any TFDM site. This group must support 24/7 availability and be capable of quickly assessing the problem, identifying solutions, coordinating with the site to restore operational service as quickly as possible to minimize the impact to the NAS and ATC services.

vii. Tech Refresh of TFDM. The new contract vendor must be capable of efficiently completing any in-progress or future Tech Refresh efforts to ensure that the TFDM service availability requirements can continue to be satisfied. As a minimum, operational sites 1-34 will likely need selected hardware refresh and TFDM system software changes to support the new hardware. It is anticipated that the Tech Refresh at sites 1-34 will be needed prior to the availability of TFDM Cloud-based services.

viii. TFDM Adaptation. Adaptation data controls TFDM system behavior without requiring code modifications or software recompilation. Read during system initialization, this data dictates component-level behavior and ranges in complexity from single parameters to entire airport surface maps. TFDM Adaptation Management encompasses data import, modification, parameter file generation, and packaging. The packaging process integrates the National Adaptation with the core software to create the National Release, which is then combined with Site Adaptation data to produce the final System Release. Because TFDM utilizes over 1,500 adaptation parameters, managing system complexity presents significant development and maintenance challenges. New contract vendor must:

a. Maintain detailed records of all adaptation changes, including technical rationale and stakeholder approvals, in accordance with FAA change management policies.

b. Provide dedicated on-site or remote support during system transitions to ensure real-time resolution of any adaptation-related anomalies.

c. Monitor the performance of deployed systems and propose refinements to enhance long-term operational effectiveness and surface safety.

The new contract vendor must possess the capability to perform all facets of Adaptation Management. This includes the ability to periodically author, modify, or update system adaptation parameters across all operational and support sites.

ix. TFDM Interfaces. The new contract vendor must be capable of modifying associated system software to support changes to external interface requirements. The new contract vendor must have detailed knowledge of and be capable of efficiently and effectively addressing problem reports for all TFDM’s interfaces with the following NAS systems:

· System Wide Information Management (SWIM)

· Time Based Flow Management (TBFM) system

· Traffic Flow Management System (TFMS)

· Flow Management Data and Services (FMDS) (after replacing TFMS)

· Flight Data Input Output (FDIO) system

· Airport Surface Detection Equipment – Model X (ASDE-X) and Airport Surface Surveillance Capability (ASSC) system

· Standard Terminal Automation Replacement System (STARS)

· Tower Data Link System (TDLS)

· Remote Monitoring and Logging System (RMLS)

· SWIM Terminal Data Distribution System (STDDS)

x. Cloud Migration Knowledge/Experience. The new contract vendor must be capable of designing, developing, and implementing a cost-effective approach for migrating the operational TFDM services provided by the site installed TFDM system to a Cloud based solution to meet 0.9999 Reliability/Maintainability/Availability, FAA Security Requirements, applicable NIST SP 800-171 security requirements, and Cloud bandwidth efficiency constraints. The Cloud implementation may be a FAA-provided system or a commercially available system depending on the timing and outcome of FAA efforts to acquire an FAA-only Cloud based solution. During the migration, the goal is to prevent the loss of TFDM services at the operational sites.

xi. TFDM Services at Anchorage. The new contract vendor must be capable of providing TFDM services at the ATC Tower in Anchorage, Alaska. This may be a site installed system or via a Cloud based solution, with the solution type and installation date dependent on the availability on a new automation system and Cloud opportunities at Anchorage. The Anchorage TFDM services would also require continued site support as with the other 89 operational sites.

c) Relevant Past Performance. Describe any past efforts in which your company has assumed responsibility for an existing operational system (with system size, complexity and sustainment requirements similar to TFDM) that was developed by another company but transitioned to your company for follow-on sustainment support after completion of initial development and deployment. Describe your level of success with these efforts and provide sufficient information so that the FAA may contact others to obtain additional feedback regarding your efforts.

d) Additional Comments. Provide any additional information or feedback relevant to the FAA’s TFDM support, sustainment, development, implementation, and Cloud migration needs.

7. Instructions Interested companies must submit their responses to this Market Survey electronically to Evon.M.Pollack@faa.gov and Christopher.D.Swol@faa.gov later than October 16, 2026 at 5:00 pm ET. The subject line of the email responses should read “TFDM Support, Sustainment, Development and Implementation Market Survey.”

The information received may be used as input for the development of an acquisition strategy. Telephone calls or paper submissions will not be accepted.

Responses should be submitted electronically in Microsoft Office format. A Microsoft version of the response must also be provided if submissions are provided in portable document file (PDF) format. A 40-page limit applies for responses. Please provide a capability statement addressing Sections a), b), c), and d) listed in Section 6 of this Market Survey.

Responses must include company point(s) of contact, title(s), telephone number(s), e-mail address(s), and mailing address.

Responses will not be returned. Any proprietary or confidential information in the Market Survey submissions must be appropriately marked.

After reviewing Market Survey responses, the FAA may elect to schedule one-on-one discussions with individual vendors to clarify understanding of the vendor’s response. Per the FAA Acquisition Management System (AMS), the FAA may conduct one-on-one meetings with all, some, or none of the respondents, at the FAA’s discretion.

If this announcement is viewed from other than the SAM.GOV website, some information or attachments may not be transferred correctly. Please check the FAA’s Contracting Opportunities website http://SAM.gov frequently for any updates and amendments to this announcement.

Attachments:

1. TFDM System Specification Document

2. TFDM System Overview Presentation

3. TFDM Sustainment Efforts/Timeline

(End of Announcement) TFDM Follow-on Market Survey image1.png image2.emf

ATT J-06_SSD Rev16_20260316_Final Signed.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

TFMS WSDD Publication Service

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

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

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

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

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

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…