Attachment 2_FMDS pPRD - Final.pdf

WARNING: This document contains information that is subject to the U.S. Export Administration Regulations (EAR, 15 C.F.R. Parts 730-774) and designated as EAR99. As a consequence, this information cannot be exported nor re-exported to country group E:1 or E:2 countries/persons (see Supp.1 to Part 740 of the EAR), nor can be made available to any national of such country. In addition, the information in this document cannot be exported nor re-exported to an end-user or for an end-use that is prohibited by Part 744 of the Export Administration Regulations (15 C.F.R. Part 744).

Preliminary Program Requirements for Flow Management Data and Services (FMDS) for Investment Analysis Readiness Decision (IARD) Version 1.23, April, 2022

Federal Aviation Administration 800 Independence Avenue

Washington, D.C. 20591

Flow Management Data and Services pPRD i Version 1.23, April 12th, 2022

Table of Contents

1 Introduction

1.1 Description

1.2 Scope

2 Capability Description and Program Information

2.1 Operational Concept

2.2 Quantities and Location

2.3 Constraints and Assumptions

2.3.1 Constraints

2.3.2 Assumptions

2.3.2.1 Operational and Technical Environment Assumptions

2.3.2.2 Baseline FMDS Capabilities

2.3.2.3 Additional FMDS Capabilities

3 Functional, Information and Performance Requirements

3.1 Functional Requirements

3.1.1 Manage Data

3.1.1.1 Ingest Data

3.1.1.2 Process Data

3.1.1.3 Derive Data

3.1.1.4 Provide Data

3.1.2 Assess NAS State

3.1.2.1 Define Ad Hoc Airspace

3.1.2.2 Specify Resource Capacity

3.1.2.3 Predict Resource Demand

3.1.2.4 Compare Demand and Capacity

3.1.2.5 Perform NAS State Analysis

3.1.3 Conduct Traffic Flow Management

3.1.3.1 Conduct NAS User Slot Reservations

3.1.3.2 Facilitate TMI Collaboration and Coordination

3.1.3.3 Manage Notifications

3.1.3.4 Conduct TMIs

3.1.3.5 Log NAS Event Data

3.1.4 Conduct Post-Event Analysis

ii Version 1.23, April 12th, 2022

3.1.4.1 Replay TFM Data

3.1.4.2 Extract Archived TFM Data

3.1.4.3 Create Performance Metrics

3.1.4.4 Generate Post-Event Reports

3.1.5 Provide TFM Display

3.1.5.1 Display Flight Data

3.1.5.2 Display Demand Data

3.1.5.3 Display Capacity Data

3.1.5.4 Display Adaptation Data

3.1.5.5 Display Weather Data

3.1.5.6 Display Notification Data

3.1.5.7 Display Route Availability Data

3.1.5.8 Display Operational Report Data

3.1.5.9 Display TMI Data

3.1.5.10 Display NAS Log Data

3.1.5.11 Display NAS Status Data

3.1.5.12 Display System Status Data

3.1.5.13 Display Reference Information

3.1.5.14 Display Space Data

3.1.5.15 Display NAS User Slot Reservations

3.1.5.16 Display TFM Replay Data

3.1.6 Maintain Operations

3.1.6.1 Record Data

3.1.6.2 Archive Data

3.1.6.3 Maintain Adaptation

3.1.6.4 Maintain Software

3.1.6.5 Perform Monitor and Control

3.1.6.6 Analyze System Performance

3.1.6.7 Maintain User Data

3.1.6.8 Simulate Scenarios

3.1.6.9 Support Testing

3.1.6.10 Support Training

3.2 Data and Information Requirements

iii Version 1.23, April 12th, 2022

3.2.1 FMDS Data and Information Sources

3.2.2 Data Formats

3.2.3 Data Retention

3.3 Performance Requirements

3.3.1 System Performance

3.3.1.1 Time Synchronization

3.3.1.2 System Response Times

3.4 Reliability, Maintainability, and Availability (RMA) and Resiliency Requirements

3.4.1 Reliability

3.4.2 Maintainability

3.4.2.1 Accessibility

3.4.3 Availability

4 Integration Requirements

4.1 Physical Integration

4.1.1 Environmental Requirements

4.1.2 Land and Facility

4.1.2.1 Grounding, Bonding, Shielding, Lightning Protection, Cables, Power and HVAC

4.1.2.2 Energy and Water Conservation

4.1.2.3 Hazardous Materials

4.1.3 Telecommunications

4.1.4 Special Considerations

4.2 Functional Integration

4.2.1 Interfaces to Other FAA Enterprise Architecture Elements

4.2.2 Interfaces

4.2.2.1 Adaptation

4.2.2.2 Operational

4.2.2.3 Weather

4.2.2.4 Post Operational

4.2.2.5 Maintenance

4.2.3 Spectrum Requirements

4.2.4 Software Integration

4.3 Human Factors

4.3.1 Human-Systems Engineering

iv Version 1.23, April 12th, 2022

4.3.2 Branding

4.4 Employee Safety and Health

5 Security and Safety Requirements

5.1 Facility Security

5.2 Personnel Security

5.3 Information Systems Security (ISS)

5.3.1 Security Management

5.3.2 Security Assessments

5.3.3 Security-Related System Support

5.3.4 System and Information Access

5.3.5 System and Information Monitoring

5.3.6 System and Information Protection

5.4 System Safety

5.4.1 Existing Controls

5.4.2 Safety Requirements

5.4.3 Programmatic Compliance

5.4.4 Programmatic Assessments & Documentation

5.4.5 System Software Safety

6 Quality and Configuration Management Requirements

6.1 Quality Assurance

6.1.1 Quality Assurance Program

6.1.2 Quality Assurance Control Procedures

6.1.3 Software Quality Measurement

6.2 Configuration Management

6.2.1 Configuration Management Program

6.2.2 Configuration Management Planning

6.2.3 Life-Cycle Configuration Management

6.2.4 Configuration Status Accounting System

6.2.5 System Documentation

6.2.6 Configuration Audits

6.2.7 Configuration Change Control

6.2.8 Change Proposals and Notices

6.2.9 Configuration Control Board

v Version 1.23, April 12th, 2022

7 Test and Evaluation Requirements

7.1 Planning and Test Design Requirements

7.2 Development Test Requirements

7.3 Operational Test Requirements

7.4 Site Test Reuqirements

7.5 Reporting Requirements

7.6 Test Support Requirements

7.7 Critical Operational Issues

7.8 Independent Operational Assessment

8 Implementation and Transition Requirements

9 In-Service Support and Management Requirements

9.1 Integrated Logistics Support

9.2 Maintenance Planning

9.2.1 Field Maintenance Support

9.2.1.1 Service and System Certification Criteria

9.2.1.2 Remote Maintenance Monitoring

9.2.2 Second Level Engineering, Maintenance, and Technical Support

9.2.3 Depot Level Support

9.3 Supply Support

9.3.1 Site Sparing

9.3.2 Life Cycle Provisioning/Depot Spares

9.3.3 Screening

9.3.4 Warranty

9.3.5 Asset Management

9.4 Packaging, Handling, Storage, and Transportation

9.4.1 Depot Spares

9.4.2 Barcoding

9.5 Support Equipment Maintenance

9.5.1 Tools and Test Equipment

9.6 Direct-Work Maintenance Staffing

9.7 Maintenance Support Facilities

9.8 Training, Training Support, and Personnel Skills

9.8.1 FAA Academy Training System

vi Version 1.23, April 12th, 2022

9.9 Technical Data

9.9.1 Manuals and Instructions

9.9.2 Drawings and Specifications

9.9.3 Escrow Package

9.9.4 Computer Resources Support

10 Appendix 1. Critical Performance Requirements

11 Appendix 2. Acronyms and Glossary Terms

11.1 Acronyms

11.2 Glossary

12 Appendix 3. Reference Documents

13 Appendix 4. Program Requirements Traceability and Verification

14 Appendix 5

Version 1.23, April 12th, 2022

1 Introduction While the National Airspace System (NAS) is the safest in the world, there is a high degree of uncertainty due to changing weather and system constraints, along with variability in traffic demand, including space operations. The fundamental goal of Traffic Flow Management (TFM) is to strategically manage the flow of air traffic to minimize delays and congestion in response to such constraints. TFM promotes a safe, orderly, and expeditious flow of traffic that minimizes delays through analysis, coordination, and dynamic utilization of Traffic Management Initiatives (TMIs). Today, the Traffic Flow Management System (TFMS) provides tools to support balancing NAS capacity and (growing) flight demand within a dynamic environment. However, those tools have reached end of life and are exhibiting reliability, maintainability, and availability (RMA) and other performance shortfalls.

In recent years, TFMS user expectations for RMA and performance have increased to a point that exceeds the current system capability. A recent technical refresh at the TFMS Remote Sites (TRSs) was unable to address all the performance issues, and the obsolescence of the current software may preclude another technical refresh [1]1. The TFMS Program Office investigated the root causes of TFMS outages, identified system shortfalls, and developed recommendations, with the goal of improving RMA and performance [2, 3]. The Federal Aviation Administration (FAA) is pursuing some of these recommendations as part of the Flow Management Data and Services (FMDS) program.

This preliminary Program Requirements Document (pPRD) describes the high-level requirements for FMDS to provide a basis for determining alternative solutions and estimating costs for the FMDS program. This pPRD was developed in accordance with the Federal Aviation Administration's (FAA's) Program Requirements Document Template [4] with use of the FAA’s Target NAS Requirements Document (TNRD) [5].

1.1 Description

FMDS will replace TFMS, which has evolved over several decades, moving from the original Enhanced Traffic Management System (ETMS) automation to the current architecture and functionality seen in FAA air traffic facilities today. As a result, the capabilities were developed in a piecemeal fashion and deployed onto an aging infrastructure making modifications challenging. The requirements put forth in this pPRD account for all current TFMS functions and planned functions through TFMS R16 and provide an initial foundation for solutions to the following shortfall areas identified in the FMDS Shortfall Analysis Report (SAR) [1]:

• Unacceptable performance and a lack of expandability and scalability prevents TFMS from meeting evolving needs.

• Lack of a comprehensive failover strategy prevents continuity of operations.

• Lack of integrated capabilities prevents consistent operational system-wide views, operational decision making, and usability of the system. FMDS is accounted for in the FAA NAS Enterprise Architecture (EA) Airport and Automation Roadmaps as shown in Figure 1 and Figure 2.

1 The [#] notation indicates a reference document identified in Appendix 3.

Version 1.23, April 12th, 2022

Figure 1. NAS EA Airport Roadmap

Figure 2. NAS EA Automation Roadmap

Version 1.23, April 12th, 2022

FMDS aligns to the Business and Technology Improvement (BTI) identified in Table 1.

Table 1. FMDS Alignment

BTI Number BTI Description

508120 Improved Automation Infrastructure

FMDS aligns to the NextGen Operational Improvement (OI) Increments summarized in Table 2, as described in the FMDS Concept of Operations (ConOps) v1.31 [6].

Table 2. FMDS Alignment to OI Increments

ID Number OI Increment Description

1 105210-01 Improve Demand Predictions

2 105210-02 Integrate TMI Modeling

3 105210-03 Improved Integration of Traffic Flow Management Operations

4 105210-04 Aircraft Equipage Eligibility During TMIs

5 105211-01 Integrate Departure Route Planning

6 105303-24 Enhanced Post Operations

FMDS is a solution-level concept, as illustrated in Table 3.

Table 3. FMDS Concept Alignment

Level Layer Concept

0 Global ICAO Doc 9971: Manual on Collaborative Air Traffic Flow Management

1 Enterprise Charting Aviation’s Future – Operating in an Info-Centric NAS

Enterprise Information Management

2 Service Performance Based Flow Management (PBFM)

FFM: The Corporate Plan for Future TFM

Collaborative Air Traffic Management

System Wide Information Management (SWIM)

3 Sub-Service N/A

4 Solution Flow Management Data and Services (FMDS)

1.2 Scope

TFMS users’ operational needs for availability, accuracy, and system response times have increased to a point that exceeds the current system capability. A recent technical refresh at the TRSs was unable to address all the performance issues, and obsolescence of the current software may preclude another technical refresh. The TFMS Program Office investigated the root causes of TFMS outages, identified system shortfalls, and developed recommendations for improving RMA and performance.

The FMDS ConOps describes a replacement system to provide a streamlined experience to support the full array of users within and external to the FAA. FMDS plans to not only include all of the functionality

Version 1.23, April 12th, 2022 of the current TFMS system, but also provide a foundation for efforts to achieve future FAA goals such as:

• Quickly identify lessons learned to better support continuous TFM planning processes

• Gate-to-gate integration of flight and flow data

• Standardize operational metrics across TMIs and planning timeframes

• Integrate new entrants into the NAS

• Improve response of NAS operations to uncertainty

• Improve underlying TFM algorithms to better support predicting and managing demand and capacity

Figure 3 summarizes the core FMDS functions.

Figure 3. Core FMDS Functions

TMIs are defined in FAA Order 7210.3 as techniques used to manage demand with capacity in the NAS.

TMIs include altitude restrictions (e.g., tunneling, capping), miles-in-trail, minutes-in-trail, fix balancing, airborne holding, departure sequencing, ground delay programs, airspace flow programs, CTOPs, reroutes, and ground stops. FMDS provides automation support for facilitating, modeling, implementing, monitoring, and analyzing TMIs and TMI impact on the NAS.

Version 1.23, April 12th, 2022

2 Capability Description and Program Information

2.1 Operational Concept

Figure 4 provides an overview of the FMDS concept as described in the FMDS ConOps v1.31 [6]. FMDS users internal to the FAA will access most of the information needed to perform the key TFM collaboration and decision-making functions through an integrated situation awareness display. FMDS users external to the FAA (e.g., NAS users) will access the TFM information through a streamlined suite of FMDS applications and data. Access to these applications will be configurable based on individual users and their role(s).

Figure 4. FMDS To-Be High-Level Concept Overview

FMDS system users include internal FAA users and users external to the FAA, as shown in Table 4.

Table 4. FMDS Users

Internal FAA Users External Users

Traffic managers at different facilities, including ATCSCC, ARTCCs, TRACONs, and ATCTs

Air traffic control personnel, including:

Operations Supervisors

Operations Managers

Air traffic controllers

Quality control (QC) personnel

System analysts

Training personnel

System administration and support:

System specialists

System administrators

Software engineering support

NAS users:

Domestic and international air carriers

Commercial operators

General aviation

Flight Plan Service Providers2

Military

Flying public

International ATC organizations

External users of TFM automation system data

Space Operators

The FMDS will impact stakeholders in different ways as summarized below:

• Traffic managers will experience increased productivity in conducting their TFM activities. FMDS will relieve traffic managers from manual entry of data from one application into another by automating these processes. Traffic managers will access TFM information and capabilities from a single integrated situation awareness display rather than having to switch back and forth between applications.

• NAS users will have access to improved situation awareness of NAS status and operations through the centralized portal for NAS status information. NAS users will be able to exchange data with FMDS using the same capabilities they use today except for Collaborative Decision Making (CDM) members who use Flight Schedule Monitor (FSM) and the web-based Traffic Situation Display (TSD). The capabilities from FSM and the TSD Thin client will still be available via FMDS, but the specifically named applications (FSM, TSD) will not be part of the FMDS baseline.

• System support personnel will be able to deliver improved RMA with a reduced hardware and logistics footprint. The modernization envisioned by FMDS will change the technologies employed and the skills needed for system support.

• Analysts supporting the post-event, quality control, and quality assurance processes will have improved access to the data they need to build an understanding of NAS operations.

• System developers will have an improved ability to develop and deploy new capabilities in a timely and efficient manner.

• FMDS Program Office will benefit from improved return on investments in system development and maintenance. The modernized FMDS architecture and envisioned development and

2 Flight plan service providers access TFM data on behalf of their customers to support flight planning and re-planning.

Version 1.23, April 12th, 2022 deployment strategy may require new approaches for contract management and configuration management.

FMDS will deliver needed updates to today’s TFM environment that will benefit all stakeholders and will facilitate future enhancements in TFM decision support that are not accommodated with today’s infrastructure.

FMDS will improve operational availability and system reliability, system response times, and remote site equipment maintenance and support by implementing failover strategies that maintain a full suite of FMDS services during system upgrades and provide better management of outages, component failures, and major disaster failures. The FMDS applications will exchange data with an underlying suite of common services using APIs designed according to approved industry standards.

System enhancements will be provided through applications and services developed and deployed using a set of practices that automates processes between development, security, and operations teams to build, test, and release incremental software improvements rapidly and reliably. This process is envisioned to be one of continuous exploration of enhancements that, once tested, are deployed via automated processes that ensure continuous synchronization between operational and test environments. FMDS will release new features into the operational environment on-demand instead of as part of large, periodic system updates. FMDS will streamline and standardize the data exchange interfaces within the TFM automation system as well as the external interfaces between the TFM automation system and other NAS automation systems.

2.2 Quantities and Location

FMDS processing capabilities will be hosted in geographically dispersed locations that support a primary and contingency operational capability. FMDS will provide end user hardware and networking capabilities for the following FAA facilities:

1. The Air Traffic Control System Command Center (ATCSCC)

2. Twenty-one U.S. Air Route Traffic Control Center (ARTCC) facilities

3. Three Combined En Route/Radar Approach Control (CERAP) facilities

4. Five Regional offices

5. Thirty-five U.S. Terminal Radar Approach Control (TRACON) facilities

6. Seventeen Airport Traffic Control Tower (ATCT) facilities

7. Other FAA facilities, including the Emergency Operations Center (EOC), FAA Headquarters, FAA Academy, and William J. Hughes Technical Center (WJHTC)

At this time, the FAA has not determined if FMDS will provide hardware and networking capabilities for the non-FAA locations currently supported by TFMS. These facilities may be responsible for providing the hardware and networking necessary to access FMDS data and services. The locations currently receiving FAA support for TFMS are as follows:

1. Military and other non-FAA government sites, including:

a. North American Aerospace Defense Command (NORAD)

b. Air and Marine Interdiction Coordination Center (AMICC)

2. International Air Traffic Control (ATC) sites:

Version 1.23, April 12th, 2022

a. UK (London)

b. Eurocontrol

c. Mexico

d. Chile

e. Central American Corporation for Air Navigation Services (COCESNA)

f. Colombia

g. Canada

3. Other undisclosed US Government locations as designated by the FMDS program

4. Approximately thirty CDM airline sites and six contractor sites

2.3 Constraints and Assumptions

2.3.1 Constraints

The following constraints impact the technical and operational environment for the FMDS concept:

• Implementing FMDS will not impose changes on other NAS systems that are not specified in baselined requirements documents.

• FMDS will be designed and implemented in a manner consistent with existing agreements with the CDM community. This includes data and functionality provided to CDM members.

• Deployment of FMDS should be coordinated with deployment or maintenance of other critical NAS systems to avoid interference.

• Implementation of FMDS should not complicate traffic managers’ working environment or require additional floor space in the field facilities than TFMS.

• FMDS user interfaces will be designed with an emphasis on maximizing usability and transferability of TFMS users’ knowledge to the new system.

• FMDS requirements based on criticality of the system to the NAS may constrain the options for FMDS architecture and hosting.

• FMDS options for data exchange standards may be constrained if FMDS needs to maintain legacy interfaces between NAS automation systems.

• A detailed timeline is not currently available; however, the projected Initial Operating Capability (IOC) date is Q4 CY2025 [7], and the projected Full Operational Capability (FOC) date is Q3

CY2027 [7].

2.3.2 Assumptions

This document includes assumptions about the FMDS operational and technical environments and the baseline FMDS capabilities. Baseline FMDS capabilities are not stating new functionality for FMDS;

baseline FMDS is current TFMS plus implemented functions from R15 and R16 as stated in 2.3.2.3.

2.3.2.1 Operational and Technical Environment Assumptions

• FMDS will be implemented in an environment in which bandwidth is not necessarily a primary constraint on the system architecture.

Version 1.23, April 12th, 2022

• FMDS will be deployed in a NAS automation environment that is evolving to embrace new processes and technologies such as enterprise services; Cloud computing; continuous testing and continuous integration practices; and Agile acquisition, software development, and deployment processes [8, 9].

• FMDS will be implemented in an operational environment characterized by the increased use of Time-Based Metering (TBM) and other flow management improvements deployed by NAS-wide initiatives such as Trajectory Based Operations (TBO) and the FAA Metroplex Program.

• FMDS will leverage new and existing SWIM services for receiving relevant data as appropriate.

• FMDS components will be certified if needed according to FAA Order 6000.15.

• NAS users will continue to be active participants in TFM by providing the necessary data to FMDS in a timely and effective manner and participating in planning webinars as they do today.

• NAS users will transition away from legacy data exchange interfaces (ARINC, AOCNet), to use SWIM data exchange interfaces (TFMData Request/Reply). Note that advisories and Estimated Departure Clearance Times (EDCTs) will continue to be disseminated via teletype in addition to modern data exchange methods to support a broad range of NAS users.

• FMDS will utilize, or be integrated with, services developed by other FAA programs as appropriate based on related functionality and deployment schedule, including Common Support Services-Weather (CSS-Wx) and Common Support Services-Flight Data (CSS-FD). While the schedule and integration with CSS-Wx and CSS-FD are not known at this time, FMDS will not create a dependency on either of these programs that negatively impacts the FMDS deployment schedule.

2.3.2.2 Baseline FMDS Capabilities

FMDS will provide all capabilities currently provided by TFMS, with the following exceptions:

• Capabilities currently provided by TFMS that other programs will provide in the future. For example, CSS-Wx and CSS-FD will perform some of the weather and flight data processing functions performed by TFMS today.

• Capabilities currently provided by TFMS that are unused in the current environment and no longer necessary. Stakeholder feedback throughout the requirements development process identified capabilities no longer required.

2.3.2.3 Additional FMDS Capabilities

FMDS will provide all capabilities that were baselined as part of TFMS Enhancement 4 and/or requirements levied on TFMS by the Terminal Flight Data Manager (TFDM) Program [10]. The capabilities related to Enhancement 4 and TFDM that are not available in TFMS at the time of writing but will be deployed with FMDS are summarized below.

2.3.2.3.1 Traffic Management Visibility into Surface Operations

• Ability for traffic managers to view status of airport/runway line-ups at all airports feeding shared Metroplex departure fixes (existing Departure Spacing Program [DSP] capability) for selected Metroplexes.

• Capability for ATCT and ARTCC/TRACON traffic managers to tactically coordinate departures to manage departure flows more efficiently (existing DSP capability).

Version 1.23, April 12th, 2022

• Airport Resource Management Tool (ARMT) departure efficiency analysis and reporting to replace the standalone ARMT tool currently deployed at 30+ Air Traffic Control (ATC) facilities.

2.3.2.3.2 TMI Modeling and Performance

• Integrated TMI Modeling (ITM) capability to model multiple TMIs together and assess their impact on baseline operations.

• Simplified use of existing TMI tools, improved coordination of TMIs, and enhanced modeling and implementation of MIT consistent with the ITM.

• Integrated Departure Route Planning (IDRP) (OI Increment 105211-01) for selected major metroplexes, which supports:

○ Traffic manager identification of route options for departures on a flight list, including eligible routes for user-selected flights and future demand for specific departure fixes.

○ Quick access to a simplified Route Amendment Dialog (RAD) for departures to be rerouted.

○ Improved departure trajectory predictions based on requirements from the Improved Demand Prediction (IDP) baseline.

○ IDRP departure fix combine/de-combine and open/closure status will automatically be logged in National Traffic Management Log (NTML).

• International Civil Aviation Organization (ICAO) Equipment Code Processing that allows checking of route eligibility based on Area Navigation (RNAV) equipage for aircraft being rerouted via TFMS and identification of flights eligible for selected Automatic Dependent Surveillance- Broadcast (ADS-B)-dependent spacing procedures (OI Increment 105210-04).

• Improving Demand Prediction (IDP), which produces more accurate demand predictions by using new data sources, considering implemented TMIs, adjusting TFMS demand prediction algorithms, and smoothing aggregate demand [11] (OI Increment 105210-01).

2.3.2.3.3 Data Exchange

• Data exchanges between TFMS and TFDM.

• Addition to TFMData to publish airport arrival and departure delay to support cloud migration of the web applications.

Version 1.23, April 12th, 2022

3 Functional, Information and Performance Requirements

3.1 Functional Requirements

3.1.1 Manage Data

Ingests and processes external data sources including flight, resource, aeronautical, weather, CDM Member, and space data to create a common model of NAS operations based on available data and supporting algorithms. This includes the derivation of additional data (e.g., modeled trajectories, weather analysis) and the provision of data for use by FMDS and by authorized users.

3.1.1.1 Ingest Data

Acquires data messages provided by external systems and human operators that are needed by FMDS functions.

3.1.1.1.1 Ingest NAS Flight Data

FMDS_pPRD_100. The FMDS system must acquire individual flight data messages from NAS systems including flight plans, flight events (e.g., departure and arrival), flight attributes (e.g., departure runway, arrival runway), and en route and surface surveillance data from the following systems:

ERAM

FS21

STARS

ATOP

OFDPS

FDPS

MEARTS

ASDE-X

ASSC

TFDM

TBFM

3.1.1.1.2 Ingest International Flight Data

FMDS_pPRD_101. The FMDS system must acquire individual flight data messages from ANSPs and their international ATC systems including flight plans, flight events (e.g., departure and arrival), and en route surveillance data for flights that originate in or are destined for an international airport that will traverse the NAS from the following ANSPs:

UK

Chile

Mexico

Colombia

Brazil

COCESNA

Canada

EUROCONTROL

Trinidad and Tobago

Version 1.23, April 12th, 2022

3.1.1.1.3 Ingest Schedule Data

FMDS_pPRD_104. The FMDS system must acquire schedule data, currently provided by OAG, consisting of planned schedules of flights arriving at, departing from, or flying over the United States as well as Canada and parts of Mexico, the Caribbean, and Europe.

3.1.1.1.4 Ingest Weather Data

FMDS_pPRD_102. The FMDS system must acquire textual and gridded weather data messages for the following types of weather data:

METAR

TAF

VAA

NOWRAD

Lightning strikes

RVR

TCF

CIWS

Forecast wind

Echo tops

3.1.1.1.5 Ingest Adaptation Data

FMDS_pPRD_103. The FMDS system must acquire geographic boundaries, aeronautical features (e.g., Navigational Aids (NAVAIDs), fixes, routes, sectors), and system data from the following sources:

NASR/NFDC

NACO

ERAM

International ANSPs including UK, Chile, Mexico, Colombia, Brazil, COCESNA, Canada, EUROCONTROL, Trinidad and Tobago, and Dominican Republic

OAG supporting data

ATCSCC FMDS adaptation

RAPT

Weather location reporting

Flight service station

World geographic boundaries

TFDM surface adaptation

3.1.1.1.6 Ingest CDM Member Data

FMDS_pPRD_105. The FMDS system must acquire CDM Member Data consisting of flight data (e.g., identification, origin, destination, intent [e.g., gate and runway time estimates, TOS messages], actual events [e.g., OOOI]), and actions (e.g., create, modify, cancel, substitution).

CDM Members are a subset of NAS Users that meet the FAA requirements for CDM Member status and access.

Version 1.23, April 12th, 2022

3.1.1.1.7 Ingest Reference Information

FMDS_pPRD_106. The FMDS system must acquire reference information data that can be used by either the general public to improve their knowledge of the NAS or FAA personnel to assist them in the conduct of their roles and responsibilities.

3.1.1.1.8 Ingest Space Data

FMDS_pPRD_662. The FMDS system must acquire data messages that provide space operation information.

3.1.1.1.9 Ingest Sector Configuration Data

FMDS_pPRD_663. The FMDS system must acquire sector configuration data from NAS automation.

3.1.1.1.10 Ingest Departure Sequencing Data

FMDS_pPRD_664. The FMDS system must acquire departure sequencing data from NAS automation.

3.1.1.2 Process Data

Processes the data ingested by the Ingest Data function.

3.1.1.2.1 Process Flight Data

Processes the flight data ingested by the Ingest NAS Flight Data, Ingest International Flight Data, Ingest Schedule Data, and Ingest CDM Member data functions. This function performs flight data validation, flight data parsing, flight data matching, and flight data saving from these sources.

3.1.1.2.1.1 Validate Flight Data

Ensures the validity of the ingested flight data by performing format, syntax, range, and logic checking specific to the type of flight data: NAS, International, Schedule, and CDM Member.

3.1.1.2.1.1.1 Validate NAS Flight Data

FMDS_pPRD_107. The FMDS system must validate ingested NAS flight data.

3.1.1.2.1.1.2 Validate International Flight Data

FMDS_pPRD_108. The FMDS system must validate ingested International flight data.

3.1.1.2.1.1.3 Validate Schedule Data

FMDS_pPRD_109. The FMDS system must validate ingested Schedule data.

3.1.1.2.1.1.4 Validate CDM Member Flight Data

FMDS_pPRD_110. The FMDS system must validate ingested CDM Member flight data.

3.1.1.2.1.2 Parse Flight Data

Separates a flight data message into fundamental data elements specific to the type of flight data: NAS, International, Schedule, and CDM Member.

3.1.1.2.1.2.1 Parse NAS Flight Data

FMDS_pPRD_111. The FMDS system must separate validated NAS flight data into fundamental data elements from NAS or ICAO formatted flight data.

Version 1.23, April 12th, 2022

3.1.1.2.1.2.2 Parse International Flight Data

FMDS_pPRD_112. The FMDS system must separate validated ingested International flight data into fundamental data elements from ICAO formatted flight data.

3.1.1.2.1.2.3 Parse Schedule Data

FMDS_pPRD_113. The FMDS system must separate validated ingested Schedule data into fundamental data elements.

3.1.1.2.1.2.4 Parse CDM Member Flight Data

FMDS_pPRD_114. The FMDS system must separate validated ingested CDM Member flight data into fundamental data elements.

3.1.1.2.1.3 Match Flight Data

FMDS_pPRD_115. The FMDS system must determine if the ingested, validated, and parsed flight data message matches an existing flight based on fundamental data elements.

3.1.1.2.1.4 Save Flight Data

Updates flight data for matched flights or creates a new flight if no match is identified.

3.1.1.2.1.4.1 Update Existing Flight

FMDS_pPRD_117. The FMDS system must update the matched flight data with the new information from the processed flight data.

3.1.1.2.1.4.2 Create New Flight

FMDS_pPRD_597. The FMDS system must create a new flight with the information from the processed flight data.

3.1.1.2.2 Process Weather Data

Processes the weather data ingested by the Ingest Weather Data function to validate the ingested data.

3.1.1.2.2.1 Validate Weather Data

FMDS_pPRD_118. The FMDS system must ensure the validity of the ingested weather data by performing format, syntax, range, and logic checking specific to the type of weather data.

3.1.1.2.3 Process Adaptation Data

Processes the adaptation data ingested by the Ingest Adaptation Data function. The applicable functions include validating adaptation data, filtering adaptation data, merging and aliasing adaptation data, and reconciling adaptation data.

3.1.1.2.3.1 Validate Adaptation Data

FMDS_pPRD_121. The FMDS system must ensure the validity of the ingested adaptation data by performing format, syntax, range, and logic checking specific to the type of adaptation data.

3.1.1.2.3.2 Filter Adaptation Data

FMDS_pPRD_122. The FMDS system must filter out unnecessary adaptation data items or fields from the following sources:

NASR/NFDC

Version 1.23, April 12th, 2022

NACO

ERAM

International ANSPs, including Chile, Mexico, Colombia, Dominican Republic, Caribbean, Europe, and COCESNA

OAG

3.1.1.2.3.3 Merge Adapted Elements

FMDS_pPRD_123. The FMDS system must merge airport, fix, or airway definitions when two or more adapted elements are geographic duplicates.

3.1.1.2.3.4 Alias Adapted Elements

FMDS_pPRD_124. The FMDS system must alias airport, fix, or airway definitions when two or more adapted elements are semantic duplicates. Aliasing allows multiple references from external sources to be treated as a single element within FMDS (e.g., KLAX, LAX).

3.1.1.2.3.5 Reconcile Adapted Elements

FMDS_pPRD_125. The FMDS system must reconcile the adapted elements to define a single adapted element when an adapted element is defined in more than one adaptation source.

3.1.1.2.4 Process CDM Member Data

Processes the data ingested by the Ingest CDM Member Data function. The applicable functions include processing substitution packets and TOS messages. Feedback to CDM Members is provided based on the processing of the data including for flights impacted by a bridging action from a slot credit substitution.

3.1.1.2.4.1 Process Substitution Data

Processes a substitution message packet received from a CDM Member. The applicable functions include substitution packet validation, substitution packet parsing, flight matching, and substitution response generation.

3.1.1.2.4.1.1 Validate Substitution Data

FMDS_pPRD_593. The FMDS system must ensure the validity of the ingested substitution data by performing format, syntax, range, and logic checking specific to the type of substitution data.

3.1.1.2.4.1.2 Parse Substitution Data

FMDS_pPRD_126. The FMDS system must separate a substitution data message into fundamental data elements specific to the type of substitution data.

3.1.1.2.4.1.3 Match Substitution Data

FMDS_pPRD_665. The FMDS system must determine if the ingested, validated, and parsed substitution data matches existing flights based on fundamental data elements.

3.1.1.2.4.1.4 Generate Substitution Response

FMDS_pPRD_594. The FMDS system must generate the response to the substitution request to indicate if one or more flight changes can accommodate the substitution request.

3.1.1.2.4.2 Process TOS Message

Processes a TOS message received from a CDM Member. The applicable functions include TOS message validation, TOS route validation, flight matching, and TOS response generation.

Version 1.23, April 12th, 2022

3.1.1.2.4.2.1 Validate TOS Message Data

FMDS_pPRD_127. The FMDS system must ensure the validity of the ingested TOS message data by performing format, syntax, range, and logic checking including route validation.

3.1.1.2.4.2.2 Parse TOS Message Data

FMDS_pPRD_666. The FMDS system must separate a TOS message into fundamental data elements.

3.1.1.2.4.2.3 Match TOS Flight Data

FMDS_pPRD_667. The FMDS system must determine if the ingested, validated, and parsed TOS data matches an existing flight based on fundamental data elements.

3.1.1.2.4.2.4 Generate TOS Message Response

FMDS_pPRD_596. The FMDS system must generate the response to the TOS message.

3.1.1.2.5 Process Space Data

FMDS_pPRD_668. The FMDS system must process the space data ingested by the Ingest Space Data function.

3.1.1.2.6 Process Sector Configuration Data

FMDS_pPRD_669. The FMDS system must process the sector configuration data ingested by the Ingest Sector Configuration Data function.

3.1.1.2.7 Process Departure Sequencing Data

FMDS_pPRD_670. The FMDS system must process departure sequencing data including flight matching, Route Approval Status and Route Database Logic Checking.

3.1.1.3 Derive Data

Derives data for use by FMDS that is based on the external interface data (e.g., single flight information, weather).

3.1.1.3.1 Derive Modeled Trajectories

Creates and evaluates modeled trajectories for each flight operating or planning to operate in the NAS.

3.1.1.3.1.1 Create Modeled Trajectories

Creates a modeled trajectory for a flight by generating profiles (i.e., lateral, vertical, speed), computing trajectory times, and generating a flight event list.

3.1.1.3.1.1.1 Generate Lateral Profile

FMDS_pPRD_151. The FMDS system must create a projection of the flight's trajectory on the surface of the Earth. A flight's lateral profile consists of a sequential list of adapted fixes (or waypoints) that includes the departure and arrival airports along with fixes associated with airways. This function uses various types of issued route assignments and historical flight routes to ascertain which route to utilize when creating a modeled trajectory for a flight. This function also uses the conformance assessment and added ATC maneuvers from the Evaluate Modeled Trajectories function to modify a flight's lateral profile when the flight trajectory is determined to have changed.

Version 1.23, April 12th, 2022

3.1.1.3.1.1.2 Generate Vertical Profile

FMDS_pPRD_152. The FMDS system must create a projection of a flight's altitude for each phase of flight: climb, cruise, and descent. Vertical profiles provide an altitude value for each location in a flight's lateral profile generated by the Generate Lateral Profile function. This function also uses the conformance assessment and added ATC maneuvers from the Evaluate Modeled Trajectories function to update a flight's vertical profile after conformance checking.

3.1.1.3.1.1.3 Generate Speed Profile

FMDS_pPRD_153. The FMDS system must create a projection of a flight's speed for each point in the lateral profile. A speed profile consists of segments of constant speed or constant acceleration for each phase of flight. Additionally, this function generates a separate speed profile that accounts for the most recent wind velocity forecasts. This function utilizes the profiles generated by the Generate Lateral Profile and Generate Vertical Profile functions. This function also uses the conformance assessment and added ATC maneuvers from the Evaluate Modeled Trajectories function to update a flight's speed profile, if necessary.

3.1.1.3.1.1.4 Compute Trajectory Times

FMDS_pPRD_154. The FMDS system must calculate the times associated with specific points of interest along a flight's trajectory. This includes ground times (e.g., wheels-up time given a gate pushback time), relative and absolute time profiles, and delay time adjustments provided by assigned metering time and EDCTs. This function uses the profiles generated by the Generate Lateral Profile, Generate Vertical Profile, and Generate Speed Profile functions.

3.1.1.3.1.1.5 Generate Event List

FMDS_pPRD_155. The FMDS system must create the list of flight events a flight will encounter during the operation. The event list is used for flight matching and demand predictions and includes the following events:

Departure Event - the absolute time and location at which a flight is projected to takeoff from the departure airport.

Top-of-Climb Event - the absolute time and location at which a flight's climb profile is projected to reach the cruising altitude.

Fix Crossing Event - the absolute time and location at which a flight is projected to cross a named fix.

Airway Traversal Event - the absolute times and locations when a flight is projected to enter and exit a defined airway.

Airspace Intersection Events - the absolute time and location at which a flight is projected to intersect the boundary of a defined airspace (e.g., ARTCCs, sectors, Fixed Airspace Volumes (FAVs), FxAs, SUAs).

Inflection Point Events - the absolute times and locations a flight is projected to change its cruising speed (speed inflection), change its heading (lateral inflection), or change its altitude (vertical inflection).

Top-of-Descent Event - the absolute time and location at which the descent profile reaches the flight's cruising altitude.

Arrival Event - the absolute time and location at which a flight is projected to land at its arrival airport.

Version 1.23, April 12th, 2022

3.1.1.3.1.2 Evaluate Modeled Trajectories

Evaluates that modeled trajectories remain consistent with the flight's reported position, track data history, and event list. Determines if the modeled trajectory should be recomputed including the identification of ATC maneuvers that the flight is performing.

3.1.1.3.1.2.1 Evaluate Conformance

FMDS_pPRD_156. The FMDS system must compare a flight's current position and track history to the modeled trajectory to evaluate conformance across four dimensions: lateral, vertical, longitudinal, and speed (which accounts for time). If a flight is not conformant with the modeled trajectory, a new modeled trajectory is created from the Create Modeled Trajectories function.

3.1.1.3.1.2.2 Identify ATC Maneuver

FMDS_pPRD_157. The FMDS system must use a flight's current position, track data history, event list, and conformance assessment to determine which ATC maneuver a flight is currently performing. The ATC maneuvers identified are:

Hold Maneuver - occurs when consecutive position reports for a flight indicate that the flight is in the exact same position and the track history data indicates that the flight is not progressing toward the destination.

Coast Maneuver - occurs when consecutive position reports for a flight indicate that the flight is in the exact same position. Identification of a Coast Maneuver ends re-conformance checking.

Vector Maneuver - occurs when a flight's deviation from the modeled trajectory would result in a delay less than or equal to an adapted maximum vector delay time.-

Ascend Maneuver - occurs when a flight's track data history indicates a consistent altitude increase in the cruise phase of flight other than those expected in the flight plan.

Descend Maneuver - occurs when a flight's track data history indicates a consistent altitude decrease in the cruise phase of flight other than those expected in the flight plan.

Fly-At-New-Cruise Maneuver - occurs when the recent position reports for a flight in the cruise phase indicates that a flight has changed altitude and has leveled off.

Direct-To-Fix Maneuver - occurs when a flight's current heading would take the flight over any of the downstream fixes in the flight's modeled trajectory other than those expected in the flight plan.

Wander Maneuver - occurs when a flight is non-conformant, but maneuver type cannot be determined.

3.1.1.3.1.2.3 Add ATC Maneuver

FMDS_pPRD_158. The FMDS system must add an ATC maneuver to the modeled trajectory when detected by the Identify ATC Maneuver function. These maneuvers include holding, vectoring, new cruise altitude, new cruise speed, and direct route. Maneuvers detected by the Identify ATC Maneuver function that are not added to the modeled trajectory simply retain an indication of the maneuver.

3.1.1.3.2 Derive Weather Data

Derives gridded, textual, and WAF weather products based on ingested and processed weather data.

Version 1.23, April 12th, 2022

3.1.1.3.2.1 Derive Gridded Weather Products

FMDS_pPRD_119. The FMDS system must convert the ingested weather data from native format to a format for user interface display or trajectory modeling. Gridded weather data refers to weather information that is overlaid on a two-dimensional grid.

3.1.1.3.2.2 Derive Textual Weather Products

FMDS_pPRD_120. The FMDS system must format and filters out extraneous data for user interface display from the ingested non-gridded weather data received in a text-based format.

3.1.1.3.2.3 Derive WAF Grid

FMDS_pPRD_165. The FMDS system must create the WAF grid from the CIWS Vertically Integrated Liquid (VIL) and echo tops data provided by the Process Weather Data function. The WAF is a two-dimensional (1 km grid) field of values that estimate the probability of pilot deviation at each grid point due to that location's weather conditions.

Note, when implemented, the generation of the WAF grid will be performed by NWP and made available to FMDS via CSS-Wx. Therefore, if implemented prior to FMDS, this function will change to functions that ingest, process, and provide the WAF Grid.

3.1.1.4 Provide Data

Makes FMDS data available to authorized users. This includes FMDS functions and other automation systems.

3.1.1.4.1 Provide Flight Data

FMDS_pPRD_128. The FMDS system must provide ANSP (e.g., NAS, International) flight data, Schedule flight data, TMI-specific flight data (e.g., departure control times, route assignments), and CDM Member flight data to authorized users.

3.1.1.4.2 Provide Demand Data

FMDS_pPRD_130. The FMDS system must provide NAS resource demand data to authorized users.

3.1.1.4.3 Provide Capacity Data

FMDS_pPRD_131. The FMDS system must provide NAS resource capacity data to authorized users.

3.1.1.4.4 Provide Adaptation Data

FMDS_pPRD_132. The FMDS system must provide FMDS adaptation data to authorized users.

3.1.1.4.5 Provide Weather Data

FMDS_pPRD_133. The FMDS system must provide gridded and textual weather data to authorized users.

3.1.1.4.6 Provide Notification Data

Provides notification data (e.g., numbered advisories, restrictions, general messages) to authorized users.

Version 1.23, April 12th, 2022

3.1.1.4.6.1 Provide Advisory

FMDS_pPRD_147. The FMDS system must provide numbered advisory data to authorized users.

3.1.1.4.6.2 Provide Demand Capacity Imbalance Notification

FMDS_pPRD_134. The FMDS system must provide demand capacity imbalance notification data to authorized users.

3.1.1.4.6.3 Provide General Notification

FMDS_pPRD_135. The FMDS system must provide general notification data to authorized users.

3.1.1.4.6.4 Provide Restriction Notification

FMDS_pPRD_927. The FMDS system must provide restriction notification data to authorized users.

3.1.1.4.6.5 Provide NAS Event Notification

FMDS_pPRD_928. The FMDS system must provide NAS event notification data to authorized users.

3.1.1.4.6.6 Provide Slot Modification Control Notification

FMDS_pPRD_929. The FMDS system must provide slot modification control notification data to authorized users.

3.1.1.4.6.7 Provide TMI Parameters Notification

FMDS_pPRD_930. The FMDS system must provide TMI parameters notification data to authorized users.

3.1.1.4.7 Provide Route Availability Data

FMDS_pPRD_136. The FMDS system must provide route availability data (e.g., timelines, trend data, and blockage scores) to authorized users.

3.1.1.4.8 Provide TMI Data

FMDS_pPRD_139. The FMDS system must provide TMI data (e.g., program type, time, scope, capacity, impacts) for proposed and implemented TMIs to authorized users.

3.1.1.4.9 Provide CDM Member Data

FMDS_pPRD_148. The FMDS system must provide CDM Member data (e.g., flight intent, operational updates, substitutions, TOSs) to authorized users.

3.1.1.4.10 Provide NAS Log Data

FMDS_pPRD_141. The FMDS system must provide NAS Log data to authorized users.

3.1.1.4.11 Provide NAS Status Data

FMDS_pPRD_143. The FMDS system must provide NAS Status data (e.g., airport, NAS, international operations) to authorized users.

3.1.1.4.12 Provide System Status Data

FMDS_pPRD_144. The FMDS system must provide system status data (e.g., monitor and control events, outages, and scheduled maintenance for the FMDS system or FMDS components) and

Version 1.23, April 12th, 2022 system administration data (e.g., system performance, network performance, hardware performance) to authorized users.

3.1.1.4.13 Provide Reference Information

FMDS_pPRD_145. The FMDS system must provide Reference information to authorized users.

This function will be implemented by the S3 program.

3.1.1.4.14 Provide Space Data

FMDS_pPRD_671. The FMDS system must provide Space data to authorized users.

3.1.1.4.15 Provide Analytics Data

Provides analytics data to authorized users for real-time and post-event analysis.

3.1.1.4.15.1 Provide Real-time Analytics Data

FMDS_pPRD_137. The FMDS system must provide analytics data to authorized users for real-time analysis.

3.1.1.4.15.2 Provide Post-event Analytics Data

FMDS_pPRD_672. The FMDS system must provide analytics data to authorized users for post-event analysis.

3.1.2 Assess NAS State

Uses ingested, processed, and derived data to evaluate the current and projected state of the NAS and enables authorized users to identify near- and long-term problems to determine whether mitigating actions are needed.

3.1.2.1 Define Ad Hoc Airspace

The FMDS system must provide authorized users the ability to define airspaces of interest to support traffic management, including crossing line(s), circles, and polygons and attributes (e.g., altitudes, aircraft types). Ad hoc airspaces are represented by FxAs in the current system.

3.1.2.2 Specify Resource Capacity

Specifies resource capacity as the number of operations that can safely use a NAS resource over a specified period of time (e.g., aircraft arrivals per hour) or the expected usage of departure…