Attachment 6 FMDS FAD 250918.pdf

Flow Management Data and Services (FMDS)

Functional Analysis Document (FAD)

FINAL, Version 2.03

October 4, 2024

Flow Management Data and Services Functional Analysis Document ii

Table of Contents 1 Introduction

1.1 Summary of FMDS Concept of Operations

1.2 System Bounds

1.3 Timeframe

2 Operational Context

2.1 High-Level Context Diagram

2.2 High-Level Context Functions and Interactions

2.3 Boundary Systems

2.3.1 External TFM Automation (C.1)

2.3.2 Flight Operator Automation (C.3)

2.3.3 U.S. and International ATC Automation (C.4)

2.3.4 Weather Data (C.7)

2.3.5 Adaptation Data (C.8)

2.3.6 Schedule Data (C.9)

2.3.7 Space Data (C.12)

2.4 Boundary Stakeholders

2.4.1 Internal Users (C.2)

2.4.2 External Users (C.5)

2.4.3 General Public (C.6)

2.4.4 Post-Event Analysts (C.10)

2.4.5 Support Personnel (C.11)

2.5 Operational Environment

3 Functional Architecture

3.1 Functional Hierarchy

3.1.1 Perform TFM Functions (F.0)

3.2 Functional Behavior Model

3.2.1 Perform TFM Functions (F.0)

Appendix 1: Reference Documents

Appendix 2: Acronyms and Glossary Acronyms Glossary

Appendix 3: Data Dictionary ................................................................................................................................................. A iii

Document History

Version Date Changes

2.00 12/05/2022 Functional hierarchy updates and additions since IARD.

2.01 2/16/2023

2.02 10/2/2023 Updates based on updates and additions to fPRD.

2.03 10/4/2024 Updates to align the FAD with fPRD v1.0

1 Introduction 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 changing weather and system 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 National Airspace System (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]. 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 TFMS Program Office is pursuing many of these recommendations as part of the Flow Management Data and Services (FMDS) program.

This Functional Analysis Document (FAD) provides a comprehensive inventory of the functions to be implemented in FMDS, which will be deployed using modernized development and architecture practices.

1.1 Summary of FMDS Concept of Operations

FMDS, as documented in its Concept of Operations [4], will provide a robust and reliable automation system to support TFM functions in a modernized, service-based architecture using industry standards. Modernization will increase reliability and reduce response time for users, and a standards- and service-based architecture will provide flexibility to the Federal Aviation Administration (FAA) for implementing capabilities as well as extensibility to future enhancements.

As much as possible, functions needed by multiple applications will be implemented as services, keeping the business logic in each application as minimal as possible. This will avoid duplication of functions and data across services and applications, which will simplify development and maintenance. FMDS also will increase harmonization of the data and semantics used across services and applications.

TFM system functions will be implemented in a streamlined set of applications that will improve the user experience.

The consolidated application suite and improved performance will allow traffic managers to view all traffic, TMIs, and weather in one integrated situation awareness display, rather than having different TMIs modeled, coordinated, and represented in different applications/displays and maintaining a separate display for weather. This will improve demand predictions relative to constraints and allow traffic managers to develop, coordinate, and manage TMIs strategically and efficiently. Information that today is collected electronically but must be logged manually will be logged automatically, reducing traffic manager workload associated with entering duplicate data across applications.

Consolidation also will allow traffic managers to receive notifications associated with electronic coordination directly in the integrated situation awareness display and act on the notification all in one place.

Similarly, NAS users will access information about NAS operations, and participate in collaborative decision making, in new ways. The various web applications that today must be monitored separately will be streamlined and accessible via a single NAS Status Portal. NAS users will be able to subscribe to notifications of changes in TMIs, strategic plans, and other information accessible via the NAS Status Portal, relieving them from the need to poll or scrape1 several different websites. Collaborative Decision Making (CDM) members will transition away from the use of local instances of Flight Schedule Monitor (FSM). Rather, FMDS will expose Application Programming Interfaces (APIs) that will allow CDM members to access data and services they can use to model the impact of TMIs on their flights using the same algorithms that support the integrated situation awareness display used by traffic managers.

FMDS will create a robust archive of data presented to users, data exchanged among users/facilities, and data exchanged among the application support services that will drive the applications and displays. The streamlined application suite will make it easier to associate flights with TMIs, support post-event understanding of the series of events and their impacts on NAS operations, and replay them in the integrated situation awareness display.

1 Web scraping is an automated process for periodically downloading and extracting data from a web page.

The modernized architecture will improve responsiveness of TMI modeling capabilities, better meet users’ expectations for usability and performance, and will be scalable to future capabilities. FMDS will use accepted industry data formats when appropriate to minimize the number of different data structures utilized and ease data sharing and integration across NAS automation systems. Modernization also will improve the processes for providing system support, from reducing the need for synchronizing data on the backend to simplifying management of user accounts.

The service-based architecture will support a more rapid approach to development with a focus on frequently delivering small updates to the system capabilities. Each capability set will first be implemented in the form of a Minimum Viable Product (MVP) that may not include all the desired features but will allow early user evaluation, with feedback that can inform future iterations. This approach will allow new capabilities to be fielded faster than they are today, reducing the likelihood that operational needs will change while a capability is in development.

1.2 System Bounds

In this document, TFMS is considered to comprise several applications, the most prominent of which are as follows:

• TFMS Core is the computational engine and database at the core of the TFMS system. This includes computation of flight trajectories, deterministic demand, and TMI impacts for Reroute TMIs and Collaborative Trajectory Options Programs (CTOPs). The TFMS Core consists of a primary site – the TFM Production Center (TPC) hosted at William J. Hughes Technical Center (WJHTC) – and a backup site – the Disaster Recovery (DRC) System Node.

• Traffic Situation Display (TSD) is the user interface for all TFMS functions except those provided by FSM and NTML. This includes the “thin-client” TSD-C that provides selected functions to flight operators and other users external to the NAS.

• FSM is an application used by traffic managers and flight operators to create and maintain Ground Delay Programs (GDPs), Ground Stops (GSs), and Airspace Flow Programs (AFPs), as well as monitor demand and capacity of NAS resources (e.g., airports, sectors).

• National Traffic Management Log (NTML) is the application used by traffic managers to enter and coordinate restrictions and log other significant events and actions affecting the NAS.

• Enhanced Status Information System (ESIS) is the system used to communicate TFM-related NAS status information within a facility. It is integrated with the NTML such that restrictions entered via NTML can be automatically posted to the ESIS display.

• TRS is software that runs at each TFMS user site and performs background communications and data processing for TSD and FSM. This includes sites that are outside the FAA operational network, such as sites in Canada, referred to as External Traffic Flow Management Remote Sites (ETRSs).

• TFMS Web Applications is a suite of web applications hosted at the TPC to provide various TFM functions to both the FAA and NAS users. Some applications are available publicly while others are only accessible via the FAA intranet.

Any function currently performed by these applications is considered an existing TFMS function and will remain a required function for FMDS. For some functions, this document may include notes indicating which applications are currently performing which functions, but it is generally not the purpose of a functional analysis to allocate system functions to system components or applications.

Additionally, all items that were baselined as part of TFMS Enhancement 4 and/or requirements levied on TFMS by Terminal Flight Data Manager (TFDM) [1] are assumed to be part of FMDS. This includes the following functionality:

• Enhancements to Surface Viewer

• Additional data exchanges between TFMS and TFDM

• Requirements allocated to TFMS for a Departure Spacing Program (DSP) replacement that:

o Shows status of airport/runway line-ups at all airports feeding shared Metroplex departure fixes.

o Allows towers and Air Route Traffic Control Center (ARTCC)/Terminal Radar Approach Control

(TRACON) traffic managers to tactically coordinate departures to manage departure flows more efficiently.

o Extends DSP capabilities beyond New York Metroplex.

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

• Improved Demand Prediction (IDP), which produces more accurate demand predictions by using new data sources, considering implemented TMIs, adjusting TFMS demand prediction algorithms, and smoothing deterministic demand [5].

• Integrated TMI Modeling (ITM), which supports modeling multiple TMIs together and assessing their impact on baseline operations to develop the Operations Plan. ITM also simplifies the use of existing TMI tools, improves coordination of TMIs, and enhances the modeling and implementation of MIT [5].

• Integrated Departure Route Planning (IDRP) for selected major metroplexes, which supports:

o Identification of route options for departures on a flight list, including eligible routes for user-selected flights; and future demand for specific departure fixes.

o Quick access to a simplified Route Amendment Dialog (RAD) for departures to be re-routed.

o Improved departure trajectory predictions based on requirements from the IDP baseline.

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

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

• Integration with Common Support Services – Weather (CSS-Wx) and Common Support Services – Flight Data

(CSS-FD).

A more detailed description of the external systems and their interfaces with FMDS is found in Section Error! Reference source not found. Error! Reference source not found..

1.3 Timeframe

FMDS is currently traversing the Acquisition Management System (AMS) process and has the following milestones:

• Investment Analysis Readiness Decision (IARD) – Q1 CY2023

• Final Investment Decision (FID) – Q1 CY2025

If this schedule is maintained, FMDS will reach Contract Award by January 2025 and Initial Operating Capability (IOC) by September 2029.

At the same time, the S3 program will also be going through the AMS process and has two scheduled milestones:

• IARD – Q1 CY2022

• FID – Q2 CY2023

The objective of S3 is to sustain the TFMS system until FMDS is operational. Critical core hardware will be refreshed and the aging auxiliary subsystem, which hosts the web applications, will be retired. Those web applications will be rehosted on a new platform, accelerating the realization of some of the FMDS benefits associated with the hardware or hosting platform.

Since this FAD represents the end state of FMDS and encompasses S3 functionality, those functions that have been allocated to the S3 program are included.

2 Operational Context

2.1 High-Level Context Diagram

The figure below depicts FMDS and its interfaces with external systems and human operators. The highest-level function, F.0 Perform TFM Functions, and its top-level sub-functions (labeled F.1 though F.6), are represented in the center blue block within the FMDS system bounds. For a full description of context functions and their interaction with TFMS refer to Section Error! Reference source not found. Error! Reference source not found..

Figure 2: Context and Boundary Diagram

2.2 High-Level Context Functions and Interactions

Twelve high-level context functions (C.1 through C.12) exchange data with FMDS. Their roles as providers and/or consumers of information are described in this section. Error! Reference source not found. below shows the data items exchanged between FMDS and the context functions.

• C.1 Perform External TFM Automation Functions – Provides automated functions for performing TFM different from those provided by FMDS. Specifically, Time Based Flow Management (TBFM) provides functions for time-based metering, and TFDM will provide functions for surface traffic management.

• C.2 Perform Traffic Management Functions – Encompasses the functions of traffic management personnel located at FAA facilities.

• C.3 Perform Flight Operator Automation Functions – Obtains information from FMDS, including flight data and FMDS TMI data, in order to effectively manage the flights under the control of a flight operator. This function also provides FMDS with flight data from flight operator automation.

• C.4 Perform Air Traffic Control Automation Functions – Provides automation for ensuring separation and safety among aircraft operating within controlled airspaces. It provides FMDS with runway configurations and flight data for active and proposed aircraft operating within ground, terminal, and en route-controlled NAS domains. To different degrees, equivalent flight data is also provided for flights operating in oceanic and some international domains with varying surveillance capabilities, data-exchange solutions, and data-sharing agreements. This context function relies on FMDS to provide it with information on Expect Departure Control Times (EDCTs) and FMDS route assignments.

• C.5 Perform External Stakeholder Functions – Provides NAS stakeholders, which are external to FMDS, access to FMDS data and functions. Currently, this is done through TFMData via System Wide Information Management (SWIM) and the use of the “thin-client” TSD-C and other dedicated web applications.

• C.6 Obtain Public FMDS Data – Provides adaptation and TMI data to the general public.

• C.7 Provide Weather Data – Provides weather data from multiple sources to FMDS.

• C.8 Provide Adaptation Data – Provides adaptation data, including geographic and aeronautical, to FMDS.

• C.9 Provide Schedule Data – Provides scheduled flight data from Official Airline Guide (OAG) to FMDS.

• C.10 Perform Post-Event Analysis Functions – Provides archived data to authorized personnel or automation systems to analyze historical operational data from FMDS.

• C.11 Perform System Maintenance Functions – Encompasses the functions used by adaptation managers and system administrators to maintain FMDS.

• C.12 Provide Space Data – Provides space operation (e.g., launch and reentry) data to FMDS.

Table 2-1. Context Function Data Flows

Context Function Context Function Description Data Item Name Data Item Description Notes

C.01 Perform External TFM Automation Functions

Provides automated functions for performing TFM different from those provided by FMDS. Specifically, TBFM provides functions for time-based metering, and TFDM will provide functions for surface traffic management.

To FMDS

Flight Data Messages Data messages to be ingested and processed by FMDS that provide NAS and International flight data, including flight plans, surveillance data, and surface events.

For C.01, only includes:

• TFDM Data Messages

• TBFM Data Messages

Sector Configuration Data Messages

Messages defining sector configurations, specifically Sector and/or TRACON identifiers with their associated Facility Adapted Airspace data.

Departure Sequencing Data Messages

Messages defining the departure sequence.

C.02 Perform Traffic Management Functions

Encompasses the functions of traffic management personnel located at FAA facilities.

To FMDS

User IAM Request Request from a FMDS user when logging into their display for authorization and authentication purposes.

Traffic Manager Parameters

Information entered by traffic managers through FMDS user interfaces that governs the performance of FMDS functions.

Includes data defining TMIs, parameters for trajectory revision calculations, collaboration input for proposed trajectory revisions, and selection of trajectory revisions for execution.

Requests

Requests made by traffic managers through FMDS user interfaces for specific data, through a flight list, display requests, or initiate a TMI or trajectory revision.

From FMDS

User IAM Response Data that validates or invalidates the authorization and authentication information for a FMDS user.

Data Displays Data displayed to FMDS users that provides the current or historic state and performance of the NAS. The data displayed includes flight, adaptation, weather, demand and capacity, route availability, notification, real-time and post-event

For C.02, only includes:

• Flight Data Display

• Demand Data Display

• Capacity Data Display

• Adaptation Data Display reports, TMI, NAS Event Log, NAS status, reference, and replay data.

• Weather Data Display

• Route Availability Data Display

• Real-time Reports Display

• Numbered Advisories Display

• DCI Notifications Display

• NAS Event Notifications Display

• General Messages Display

• Slot Modification Control Notifications Display

• TMI Parameters Notifications Display

• FxA Display

• TMI Data Display

• NAS Event Log Data Display

• NAS Status Data Display

• Space Data Display

C.03 Perform Flight Operator Automation Functions

Obtains information from FMDS, including flight data and FMDS TMI data, in order to effectively manage the flights under the control of a flight operator. This function also provides FMDS with flight data from flight operator automation.

To FMDS

CDM Data Messages Data messages from an authorized NAS user to be ingested and processed by FMDS consisting of flight data, substitution packets, and TOS messages.

Provided TMI Data FMDS TMI data (e.g., program type, time, scope, capacity, impacts) that has been made available to authorized users (including FMDS functions and other automation systems).

Provides TMI route assignments and EDCTs to CDM Members.

Provided CDM Member Data

FMDS CDM Member data (e.g., flight intent, operational updates, substitutions, TOSs) and associated response messages that have been made available to authorized users (including FMDS functions and other automation systems).

Provides CDM Member Response Messages external to FMDS.

C.04 Perform Air Traffic Control Automation Functions

Provides automation for ensuring separation and safety among aircraft operating within controlled airspaces. It provides FMDS with runway configurations and flight data for active and proposed aircraft operating within ground, terminal, and en route-controlled NAS domains. To different degrees, equivalent flight data is also provided for flights operating in oceanic and some international domains with varying surveillance capabilities, data-exchange solutions, and data-sharing agreements. This context function relies on FMDS to provide it with information on EDCTs and FMDS route assignments.

Flight Data Messages Data messages to be ingested and processed by FMDS that provide NAS and International flight data, including flight plans, surveillance data, and surface events.

Provided TMI Data FMDS TMI data (e.g., program type, time, scope, capacity, impacts) that has been made available to authorized users (including FMDS functions and other automation systems).

For C.04, only includes Tactical Reroute requests/responses to/from

ERAM.

C.05 Perform External Stakeholder Functions

Provides NAS stakeholders, which are external to FMDS, access to FMDS data and functions. Currently, this is done through TFMData via SWIM and the use of the “thin-client” TSD-C and other dedicated web applications.

To FMDS

User IAM Requests Request from a FMDS user when logging into their display for

Data Displays Data displayed to FMDS users that provides the current or historic state and performance of the NAS. The data displayed includes flight, adaptation, weather, demand and capacity, route availability, notification, real-time and post-event reports, TMI, NAS Event Log, NAS status, reference, and replay data.

For C.05, only includes:

• Flight Data Display

• Demand Data Display

• Capacity Data Display

• Adaptation Data Display

• Weather Data Display

• Route Availability Data Display

• Real-time Reports Display

• Numbered Advisories Display

• DCI Notifications Display

• NAS Event Notifications Display

• General Messages Display

• FxA Display

• TMI Data Display

• NAS Event Log Data Display

• NAS Status Data Display

C.06 Obtain Public FMDS Data

Provides adaptation and TMI data to the general public.

Numbered Advisories Display

Display that allows authorized users to view active numbered advisories.

General Messages

Display that allows authorized users to view general notifications.

TMI Data Display Display that allows authorized users to view data for proposed, issued and historical TMIs. This includes reroute, CTOP, FxA, GDP, GS, AFP, MIT, MINIT, STOP, APREQ, time-based management, DSP, TXT, and coversheet data displays.

For C.06, only includes public restriction data.

NAS Status Data Display

Display that allows authorized users to view NAS status information. This includes airport status and NAS status data.

C.07 Provide External Weather Data

Provides weather data from multiple sources to FMDS.

To FMDS

Weather Data Messages

Messages to be ingested and processed by FMDS that consist of observed and forecast weather information.

C.08 Provide External Adaptation Data

Provides adaptation data, including geographic and aeronautical, to FMDS.

To FMDS

Adaptation Data Messages

Adaptation data messages to be ingested and processed by FMDS that define geographic boundaries and aeronautical features; for example, NAVAIDs, fixes, routes, and sectors.

C.09 Provide Schedule Data

Provides scheduled flight data from OAG, the ARTCCs, the ATCSCC, and Canadian Sites to FMDS.

To FMDS

Schedule Data Messages

Messages to be ingested and processed by FMDS that provide flight schedule data from the OAG for the next 90 days, or batched flight plan schedule data (FPSD) command files retrieved from the ARTCCs, the ATCSCC, and Canadian sites.

C.10 Perform Post-Event Analysis Functions

User IAM Request Request from a FMDS user when logging into their display for

Provides archived data to authorized personnel or automation systems to analyze historical operational data from FMDS.

Traffic Manager Parameters

Information entered by traffic managers through FMDS user interfaces that governs the performance of FMDS functions.

Includes data defining TMIs, parameters for trajectory revision calculations, collaboration input for proposed trajectory revisions, and selection of trajectory revisions for execution.

Requests made by traffic managers through FMDS user interfaces for specific data, through a flight list, display requests, or initiate a TMI or trajectory revision.

Provided Post-Event Analytics Data

FMDS post-event analytics data that has been made available to authorized users (including FMDS functions and other automation systems).

Data provided externally to post-event analysis systems (e.g., VADER, PDARS, OPSNET)

TFM Replay Data Display

Display that allows authorized users to view TFM replay data.

Archived Data Reports Display

Display that allows authorized users to view archived report data.

C.11 Perform System Maintenance Functions

Encompasses the functions used by adaptation managers and system administrators to maintain FMDS.

To FMDS

User IAM Requests Request from a FMDS user when logging into their display for

System Administrator

Parameters set by system administrators to monitor the performance of FMDS.

System Administrator

Requests entered by system administrators to retrieve system status information or compile system performance reports.

Adaptation Specialist

Parameters entered by Adaptation Specialists during the adaptation data management process.

Adaptation Specialist

Requests entered by Adaptation Specialists to access adaptation data.

ATCSCC Parameters Data entered by ATCSCC personnel to assist them in the conduct of their roles and responsibilities.

System Status Data

Display that allows authorized users to view system status (e.g., monitor and control events, outages, and scheduled maintenance for the FMDS system or FMDS components).

Open/Closed Loop Test Results

Results of testing accomplished with/without aircraft flight events (e.g., departure, trajectory, arrival) being impacted by FMDS system decisions.

C.12 Provide Space Data

Provides space operation (e.g., launch and reentry) data to FMDS.

To FMDS

Space Data Messages Data messages to be ingested and processed by FMDS that provide information regarding space operations.

2.3 Boundary Systems

2.3.1 External TFM Automation (C.1)

TBFM

TBFM performs time-based metering for pre-departure and airborne aircraft that are subject to a common constraint, for example, due to a limited airport arrival capacity. TBFM provides Scheduled Times of Departure (STD) and Scheduled Times of Arrival (STA) to FMDS for flights for which TBFM metering is in effect. Data from TBFM are available via the TBFM – Metering Information Service (MIS) from SWIM (current TFMS design).

TFDM

TFDM is a surface management solution that will seek to optimize terminal and surface operations, utilizing the exchange of information between the surface operation stakeholders. TFDM will provide FMDS with airline, tower, and terminal data concerning surface operations. Data from TFDM are available via the TFDM Terminal Publication (TTP) service from SWIM (current TFMS design).

Note, at the time of writing, details for how FMDS will ingest this TBFM and TFDM data are undecided. FMDS may ingest via CSS-FD or via the programs' SWIM connections (i.e., TBFM MIS, TTP Service).

2.3.2 Flight Operator Automation (C.3)

Flight operators (airline, air carrier, air freight, military, or general aviation/business aviation operators) utilize different automation systems that interact with FMDS. While each user may have different systems, there are several typical roles for these systems. One role is maintaining and managing data about planned operations. These systems can get data from FMDS that affect those operations; for example, assigned routes and EDCTs. For a CDM participant, these systems also send flight data updates, including updated times and statuses, to FMDS.

2.3.3 U.S. and International ATC Automation (C.4)

En Route Automation Modernization (ERAM)

ERAM is responsible for monitoring and controlling flights in the Contiguous United States (CONUS) en route airspace.

TFM reroute assignments are exchanged with ERAM over the Airborne Reroute/Pre-departure Reroute (ABRR/PDRR) interface. To ERAM, FMDS sends route amendment requests for flights as well as flow control information (e.g., EDCT).

From ERAM, FMDS receives an indication when a route amendment is applied. Additionally, FMDS receives sector configuration data from ERAM via the SWIM Flight Data Publication Service - En Route Airspace Data Publication (SFDPS-ERADP) service.

Common Support Services - Flight Data (CSS-FD)

CSS-FD is an emergent system in the NAS that will ingest flight data from numerous source systems, merge and consolidate the data while reconciling redundant items to establish an authoritative source and provide to users such as FMDS. Via CSS-FD, FMDS will receive consolidated and reconciled flight data from the following source systems:

• Standard Terminal Automation Replacement System (STARS) - ATC system that monitors and controls flights in terminal area airspace.

• Airport Surface Detection Equipment, Model X / Airport Surface Surveillance Capability (ASDE-X/ASSC) -surveillance systems that detect and track the movement of aircraft and other vehicles on the surface of an airport.

• Flight Service 21 (FS21) - provides flight plan messages (including cancels) from Flight Service Stations (FSSs).

• Advanced Technologies and Oceanic Procedures (ATOP) – provides flight data for active aircraft to FMDS from the oceanic air traffic control facilities at New York, Anchorage, and Oakland.

• Offshore Flight Data Processing System (OFDPS) – provides flight plan information and flow control messages to FMDS from the Combined Center Radar Approach Control (CERAP) facilities in Honolulu and Guam.

• Flight Data Processing System (FDPS) – provides flight plan, departure, and arrival messages to FMDS from the Anchorage ARTCC (ZAN).

• Micro En Route Automated Radar Tracking System (MEARTS) – provides track data messages to FMDS from Anchorage, San Juan, Guam, and Honolulu. In addition, flight plans from San Juan and flow messages to San Juan are handled by the Miami ERAM using a special patch.

• International ATC Systems - monitor and control flights in the en route airspace of international Air Navigation Service Providers (ANSPs). ICAO arrival, departure, flight plan, and track messages provided from the following ANSPs:

o Europe: EUROCONTROL o Canada: CANADATA o United Kingdom (UK): National Air Traffic Services (NATS) UK o Chile: Dirección General de Aeronáutica Civil Chile (DGAC Chile) o Mexico: Servicios a la Navegación en el Espacio Aéreo Mexicano (SENEAM) o Colombia: Unidad Administrativa Especial de Aeronáutica Civil (UAEAC) o Brazil: Departamento de Controle do Espaço Aéreo (DECEA) o Belize, Costa Rica, El Salvador, Guatemala, Honduras, and Nicaragua: Corporación Centroamericana de Servicios de Navegación (COCESNA)

2.3.4 Weather Data (C.7)

Weather data serves two distinct purposes within FMDS: it helps traffic managers obtain common situation awareness and it provides a critical input to FMDS’ trajectory modeling algorithms. FMDS will acquire textual and gridded weather data products from CSS-Wx. Textual products (also referred to as non-gridded products) provide observations or computed results for singular or sparsely distributed sets of geospatial locations such as points, curves, or contours.

Gridded products are expressed as arrays with element values representing uniformly spaced observations or computed results mapped to the earth's surface. These products include, but are not limited to:

• Textual Weather Products o Meteorological Aerodrome Reports (METARs) o Terminal Aerodrome Forecasts (TAFs) o Volcanic Ash Advisories (VAAs) o TFM Convective Forecast (TCF) o Growth/Decay Trends o Echo Tops Contours o Forecast Accuracies

• Gridded Weather Products o Pressure Products (e.g., Surface, Hybrid Level) o Wind Products (e.g., Hybrid Level, Height Above Ground Level, Isobaric Level) o Temperature Products (e.g., Surface, Hybrid Level, Isobaric Level) o RAPT Convective Weather Avoidance Field (CWAF) o Precipitation (VIL) Products (e.g., Mosaic, Mosaic Flags, Forecast) o Echo Tops Products (e.g., Mosaic, Mosaic Flags, Forecast) o Satellite Mosaic

2.3.5 Adaptation Data (C.8)

Adaptation data is static information used by FMDS for display to the end user and for numerous internal flight data processes. FMDS obtains adaptation data from the following sources:

• National Airspace System Resources (NASR) from the National Flight Data Center (NFDC) – provides adaptation data for the NAS, including airports/landing facilities, ARTCC boundaries, airways, fixes, navigational aids (NAVAIDs), Special Activity Airspace (SAA), Standard Terminal Arrival Routes (STAR), and Departure Procedures

(DP).

• ERAM – provides aircraft characteristic data, airborne equipment data, airports, fixes, nodes, sectors, and Fix Posting Areas (FPAs).

• ARTCCs – provide sector definition files from each CONUS ARTCC; oceanic sector boundary files from Houston ARTCC (ZHU), Jacksonville ARTCC (ZJX), Miami ARTCC (ZMA), New York ARTCC (ZNY), and Oakland ARTCC (ZOA); and sector boundary files from Anchorage ARTCC (ZAN).

• Canada – provides adaptation data for the Canadian airspace and traffic management operations from NAVCANADA, including airports, Canadian STAR, NAVAID, fixes, airways, restricted and alert areas, Terminal Control Areas, Canadian sector boundaries, and Canadian sector definitions.

• United Kingdom – provides adaptation data for the United Kingdom airspace, including fixes, NAVAID, sector boundaries, and sector definitions.

• Europe – provides adaptation data for the European airspace needed to process flight data received from

EUROCONTROL.

• Caribbean – provides adaptation data for Caribbean airspace.

• COCESNA – provides adaptation data for Belizean, Costa Rican, Salvadoran, Guatemalan, Honduran, and

Nicaraguan airspaces.

• Chile – provides adaptation data for Chilean airspace.

• Colombia – provides adaptation data for Colombian airspace.

• Dominican Republic – provides adaptation data for the Dominican airspace.

• Mexico – provides adaptation data for Mexican airspace.

• Brazil – provides adaptation data for Brazilian airspace.

Additionally, a manual interface is used to maintain several miscellaneous data types, including aircraft performance data, OAG supporting data, monitored element capacity data, and Route Availability Planning Tool (RAPT) adaptation data.

2.3.6 Schedule Data (C.9)

Schedule data provides FMDS with flight schedule information. On a weekly basis, FMDS retrieves basic flight data from OAG for flights scheduled to arrive, depart, or fly over the United States, Canada, or England.

2.3.7 Space Data (C.12)

Space data provides FMDS with real-time information about the operation of space vehicles in the NAS, particularly during launch and reentry.

Note, at the time of writing, the specific details surrounding the space data that will be available to FMDS are currently being determined by the NAS Space Integration Capability (NSIC) program.

2.4 Boundary Stakeholders

FMDS users include:

• NAS Users – Flying public, including private pilots and small operators.

• CDM Members – Representatives from government, general aviation, airlines, and private industry that collaborate to support TFM decision making.

• Traffic Managers – ATCSCC and Traffic Management Unit (TMU) personnel that use FMDS to monitor demand and capacity and, as needed, to model, implement, and maintain TMIs. Includes AJR and AJT personnel at various facilities.

• ATC Personnel – Personnel at ATC facilities that use FMDS to maintain situation awareness of TFM activities, including Operations Supervisors, Operations Managers, and Air Traffic Controllers. Includes international ATC organizations.

• Military – Military users of FMDS.

• Flight Plan Service Providers – Provide TFM data on behalf of their customers to support flight planning and re-planning.

• Post-Event Analysts – Any user conducting analyses after real-time operations.

• Adaptation Specialists – Personnel that maintain the set of adaptation data used by FMDS.

• Maintenance Specialists – System maintenance personnel that monitor the status of system hardware, software, and network components and interfaces, perform diagnostics checks, and execute system-level actions (e.g., set operation mode, shut down/restart processors, enable/disable external interfaces, select software version).

• System Administrators – Administration personnel that maintain user roles, assignments, and authorizations.

• System Testers – QC personnel that use FMDS’ scenario capability to test system function.

• Training Instructors – Personnel overseeing training activities. Responsible for scripting and reviewing student run-throughs.

• Trainees – Users being trained on FMDS capabilities.

2.4.1 Internal Users (C.2)

Internal FMDS users primarily include TFM personnel at FAA facilities (C.2). This comprises traffic managers at the Air Traffic Control System Command Center (ATCSCC), ARTCCs, TRACONs, and Air Traffic Control Towers (ATCT) as well as other FAA personnel who perform traffic management duties in addition to their primary roles.

2.4.2 External Users (C.5)

External FMDS users include:

• Flight operator personnel, using flight operator automation, potentially including flight operations center personnel (e.g., flight dispatchers) and pilots (depending on the type of operator, the type of problems identified, and the communication mechanisms available).

• ATC personnel at FAA facilities, using ATC automation, primarily en route ARTCC sector controllers for trajectory revisions affecting airborne flights as well as tower controllers for trajectory revisions affecting pre-departure flights.

In addition to Flight Operator Automation and ATC Automation, external FMDS users can also use a web browser to access both dedicated FMDS web applications and, currently, thin client displays of the TSD, FSM, and NTML. These tools allow authorized users to obtain a complete view of NAS operations as well as tools to collaborate with internal stakeholders.

The following additional positions have an indirect stake in the performance of the functions described in this document and can also obtain TFM information via web applications and/or thin client displays (if authorized):

• Operational Supervisors at ARTCCs and TRACONs

• International FMDS Users

• FMDS Service Developers

• SWIM Data Users

2.4.3 General Public (C.6)

Through dedicated web interfaces, the general public can view and access TMI and adaptation data from FMDS.

Currently, this is provided via the Operational Information System (OIS) webpage, the ATCSCC Advisory Database, and Web Route Management Tool (RMT).

2.4.4 Post-Event Analysts (C.10)

TFM system analysts and quality control (QC) personnel extract archived data from FMDS to examine historical NAS performance for a specific time in the past. To support this, FMDS provides post-event analysts with the ability to retrieve reports of archived data. Replay capabilities are also available to allow analysts to view the historical data in its native application, and when necessary, interact with it to obtain a complete understanding of the scenario.

Furthermore, User Interface (UI) activity recordings allow analysts to assess how a user interacted with their workstation at a specific time in the past.

2.4.5 Support Personnel (C.11)

Adaptation Specialists

Adaptation specialists are responsible for ensuring that the operational adaptation data utilized by FMDS is accurate and complete. This is conducted through a multi-step process whereby an adaptation specialist accesses, validates, tests, and deploys the latest set of adaptation updates. Depending on the adaptation data type, this process is conducted every 7 (e.g., airline data) or 56 days (e.g., sector boundary data from ERAM). In addition to adaptation changes that occur on regular intervals, some adaptation data changes on irregular intervals (e.g., sub-carrier relationships). In this case, when new adaptation data is received, the adaptation updates are processed and deployed.

Maintenance Specialists

Maintenance Specialists continually monitor and maintain the FMDS system. To do this, maintenance specialists rely on a constant stream of system monitoring information from FMDS to assess its health and stability. Specific responsibilities include:

• Monitor, diagnose, and resolve system problems.

• Obtain assistance and maintenance for the system.

• Properly start, stop, and selectively reboot servers.

• Select and control system data recording levels.

System Administrators

System administrators grant access privileges to users and maintain user roles and assignments.

System Testers

System testers test the FMDS system using the testing and training capability.

2.5 Operational Environment

The relevant operational environment identifies the operational characteristics, operational connections, and technological connections where FMDS will provide the greatest benefit. In 2024, based on the Enterprise Architecture (EA) Infrastructure Roadmaps from February 2020 [6], the operational environment is envisioned to include the following key characteristics:

• All scheduled TFMS releases have been implemented and are in use.

• TBFM Sustainment 1 and Enhancement 1 will be deployed and operational.

• The implementation of TFDM will be complete and will subsume the following existing capabilities: Surface

Movement Advisor (SMA), Advanced Electronic Flight Strips (AEFS), DSP, and ARMT.

• The following ATC automation system updates will be operational:

o ERAM Enhancement 2 o STARS Sustainment 2 and Enhancement 2 o ATOP Sustainment 2

• Information exchange via SWIM is widely available, with many necessary services available to FMDS, such as CSS-Wx and CSS-FD.

• The FAA Cloud Services (FCS) in operations and mission support are both operational and available to host FMDS services.

• Internal FAA communication will be conducted through the FAA Enterprise Network Services (FENS).

3 Functional Architecture This section presents detail on the functional hierarchy and the functional behavior models for FMDS. The functional hierarchy in Section Error! Reference source not found. shows the high-level functions and their decomposition, with descriptions of each function. The functional behavior model in Section Error! Reference source not found. shows how the functions interact, in terms of functional flow and data interactions.

3.1 Functional Hierarchy

The functional hierarchy presented here includes all functions relevant to FMDS; that is, it includes all existing functions provided today via TFMS, along with new functions that will be introduced via FMDS.

3.1.1 Perform TFM Functions (F.0)

Ingests and processes external data to assess the NAS state, conduct TFM, and display TFM data. Additionally, this function provides TFM data to external consumers, enables post-event analysis through the archiving of TFM data, and maintains operation of the system.

Figure 3-1. Hierarchy Diagram for F.0 Perform TFM Functions

• F.0 Perform TFM Functions - Ingests and processes external data to assess the NAS state, conduct TFM, and display TFM data. Additionally, this function provides TFM data to external consumers, enables post-event analysis through the archiving TFM data, and maintains operation of the system.

• F.1 Manage Data - Ingests and processes external data sources including flight, weather, aeronautical, CDM, 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 services and external automation and users.

• F.2 Assess NAS State - Evaluates the current and projected state of the NAS and enables Traffic Managers to identify near- and long-term problems to determine whether mitigating actions are needed.

• F.3 Conduct Traffic Flow Management - Provides tools to Traffic Managers to maintain the flow of air traffic in the NAS by defining FxAs, conducting TMIs for balancing demand and capacity, and logging NAS events.

• F.4 Conduct Post-Event Analysis - Employs historical data in improving trajectory and demand algorithms, enabling the replay capability, and the generation of reports of past data.

• F.5 Manage Display - Manages the user interface display and configuration settings of the display, as well as allows users to capture their workstation screen activity for post-event analysis and training purposes.

• F.6 Maintain Operations - Records and archives operational data, maintains FMDS adaptation, monitors and controls the operational system, analyzes system performance, maintains user access and identities, and supports test and training.

3.1.1.1 Manage Data (F.1)

Ingests and processes external data sources including flight, weather, aeronautical, CDM, 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 services and external automation and users.

«activity» F.0 Perform TFM

Functions

«activity» F.1 Manage Data

«activity» F.2 Assess NAS State

«activity» F.3 Conduct Traffic Flow Management

«activity» F.4 Conduct Post-

Event Analysis

«activity» F.5 Manage Display

«activity» F.6 Maintain Operations

Figure 3-2. Hierarchy Diagram for F.1 Manage Data

• F.1.1 Ingest Data - Acquires data messages provided by external systems and human operators that are needed by FMDS functions.

• F.1.2 Process Data - Processes the data ingested by FMDS.

• F.1.3 Derive Data - Derives data for use by FMDS that is based on the external interface data (e.g., single flight information, weather).

• F.1.4 Provide Data - Makes FMDS data available for use by FMDS services and external automation systems and users.

3.1.1.1.1 Ingest Data (F.1.1)

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

Figure 3-3. Hierarchy Diagram for F.1.1 Ingest Data

• F.1.1.1 Ingest Flight Data - Acquires flight data.

Note, this includes NAS and international flight data consisting of flight plans, surveillance data, and surface events.

• F.1.1.2 Ingest Schedule Data - Acquires schedule data.

Note, schedule data originates from OAG and batched flight plan schedule data (FPSD) command files retrieved from the ARTCCs, the ATCSCC, and Canadian sites.

• F.1.1.3 Ingest Weather Data - Acquires textual and gridded weather data messages from CSS-Wx for the following types of weather data:

o METARs o TAFs

«activity» F.1 Manage Data

«activity» F.1.1 Ingest Data

«activity» F.1.2 Process Data

«activity» F.1.3 Derive Data

«activity» F.1.4 Provide Data

«activity» F.1.1 Ingest Data

«activity» F.1.1.1 Ingest Flight

Data

«activity» F.1.1.2 Ingest Schedule

Data

«activity» F.1.1.3 Ingest Weather

Data

«activity» F.1.1.4 Ingest

Adaptation Data

«activity» F.1.1.5 Ingest CDM

Data

«activity» F.1.1.6 Ingest Space

Data

«activity» F.1.1.7 Ingest Sector Configuration Data

«activity» F.1.1.8 Ingest

Departure Sequencing Data o VAAs o Radar o Satellite o Lightning o TCFs o Corridor Integrated Weather System (CIWS) o Forecast Wind Echo Tops

• F.1.1.4 Ingest Adaptation Data - Acquires geographic boundaries, aeronautical features (e.g., NAVAIDs, fixes, routes, sectors), and system data from the following sources:

o NASR/NFDC o ERAM o International ANSPs including UK, Chile, Mexico, Colombia, Brazil, COCESNA, Canada, EUROCONTROL, Trinidad and Tobago, and Dominican Republic o OAG Supporting Data o ATCSCC FMDS Adaptation (e.g., Airport Arrival Rates/Airport Departure Rates [AARs/ADRs], flight number ranges, code share information) o RAPT Adaptation o Weather Location Reporting o FSS o World Geographic Boundaries o TFDM Surface Viewer Adaptation o TBFM airport configuration data

Note, ingesting airport configuration data from TBFM is part of the IDP requirements.

• F.1.1.5 Ingest CDM Data - Acquires CDM data from CDM Members.

Note, CDM data consists of CDM flight Data (e.g., identification, origin, destination, gate and runway estimates, and actual events [e.g., OOOI (Gate Off, Wheels Off, Wheels On, Gate In)]), and CDM action data (e.g., Trajectory Options Set [TOS], substitution).

• F.1.1.6 Ingest Space Data - Acquires data messages that provide space operation information.

• F.1.1.7 Ingest Sector Configuration Data - Acquires sector configuration data from SFDPS-ERADP.

• F.1.1.8 Ingest Departure Sequencing Data - Acquires departure sequencing data from TFDM.

3.1.1.1.2 Process Data (F.1.2)

Processes the data ingested by FMDS.

Figure 3-4. Hierarchy Diagram for F.1.2 Process Data

• F.1.2.1 Process Flight Data - Processes the flight data ingested by FMDS. Flight data processing includes validation, parsing, flight matching, and saving flight data.

• F.1.2.2 Process Schedule Data - Processes the schedule data ingested by FMDS. Schedule data processing includes validation and parsing.

• F.1.2.3 Process Weather Data - Processes the weather data ingested by FMDS. Weather data processing includes validation.

• F.1.2.4 Process Adaptation Data - Processes the adaptation data ingested by FMDS. Adaptation data processing includes validation, filtering, merging, aliasing, and prioritizing adaptation data.

•…