CSS-FD SIR J-1 Functional and Performance Spec_DRAFT_v2.0.pdf

Solicitation #

Attachment J-1

Federal Aviation Administration

Common Support Services – Flight Data (CSS-FD)

CSS-FD Functional and Performance Specification

November 2024

Federal Aviation Administration

800 Independence Avenue, SW

Washington, DC 20591 i

TABLE OF CONTENTS

1 INTRODUCTION

1.1 PURPOSE AND SCOPE

1.2 DEFINITION OF KEY TERMS

1.3 APPLICABLE DOCUMENTS

1.3.1 FAA Orders

1.3.2 Other FAA Documents

1.3.3 Other Government Documents

1.3.4 Non-Government Documents

2 CAPABILITY DESCRIPTION AND PROGRAM INFORMATION

2.1 OPERATIONAL CONCEPT

2.1.1 High-Level Concept Graphic

3 CSS-FD REQUIREMENTS

3.1 CORE SERVICES

3.1.1 Data Validation Service

3.1.1.1 Data Validation – FF-ICE

3.1.2 Data Transformation Service

3.1.3 Flight Data Reconciliation Service

3.1.4 Flight Object Management Service

3.1.5 Flight Identifier Management Service

3.1.5.1 Flight Identifier Management: GUFI Handling

3.1.5.2 Flight Identifier Management: CSS-FD UFI Handling

3.1.5.3 Flight Identifier Management: CSS-FD UFI Generation

3.1.6 Identity and Access Management Service

3.1.7 Constraint Service

3.1.8 Data Management Service

3.1.8.1 Archival

3.1.8.2 Audit

3.2 CSS-FD SWIM SERVICES

3.2.1 Flight Data Reconstitution Service

3.2.1.1 Flight Data Reconstitution Feeds

3.2.1.2 Generate Flight Data Reconstitution

3.2.1.3 Monitor Flight Data Reconstitution

3.2.2 Filing Service

3.2.2.1 Filed Flight Plan Response Messages

3.2.2.2 Return ATC Preferences

3.2.2.3 ATS Message Exchange

3.2.3 Data Publication Service

3.2.4 Flight Data Request Service

3.2.5 Trial Service

3.2.6 NAS Flight Coordination Service

3.2.7 International Data Provider Submission Service

3.3 ORCHESTRATION SERVICE

3.4 SYSTEM MONITORING AND MANAGEMENT

3.5 SYSTEM LOGGING

ii

4 PERFORMANCE REQUIREMENTS

4.1 FLIGHT PLAN HANDLING PERFORMANCE

4.2 SYSTEM LOAD

4.3 RELIABILITY, MAINTAINABILITY, AND AVAILABILITY (RMA) REQUIREMENTS

4.3.1 Reliability

4.3.2 Maintainability

4.3.3 Availability

4.3.4 Resiliency

5 FUNCTIONAL INTEGRATION

5.1 INTERFACES TO FAA ENTERPRISE ARCHITECTURE ELEMENTS

5.2 DATA INTERFACES

5.2.1 Non-SWIM Data Interfaces

5.2.2 SWIM Data Sources

5.2.3 CSS-FD SWIM Services (Business Services)

6 INFORMATION SYSTEMS SECURITY (ISS)

APPENDIX A: FDS AND FP&F REQUIREMENTS MAPPING

iii

TABLE OF TABLES

Table 1: Capabilities Mapping to J-1 Requirements Table 2: CSS-FD Core Services Table 3: Constraints for Feedback by Reference Table 4: CSS-FD SWIM Services Table 5: CSS-FD Input Data and Frequency Initial Capacity Requirements Table 6: CSS-FD Output Data and Frequency Initial Capacity Requirements Table 7: CSS-FD Capabilities and Criticality Table 8: FAA Enterprise Architecture Interfaces Table 9: CSS-FD Non-SWIM Interfaces Table 10: SWIM Data Sources

TABLE OF FIGURES

Figure 1: CSS-FD Operational Concept Overview (OV-1)

1 INTRODUCTION

The Federal Aviation Administration (FAA) Common Support Services – Flight Data (CSS-FD)1 will provide modernized, flexible, consistent, and robust services for the exchange of flight data among internal and external National Airspace System (NAS) users through a standard interface to enable a common view of flight information. CSS-FD will utilize Flight Information

Exchange Model (FIXM) international data exchange standards and facilitate the use of detailed flight information for Trajectory Based Operations (TBO) and better-informed Collaborative

Decision Making (CDM). The seven capabilities within CSS-FD accomplish modernized flight planning, flight plan filing, and flight data sharing.

Flight planning provides an international standards-based flight planning environment in which early intent or preliminary flight information relevant to a flight is shared between the Airspace

User (AU) and the FAA, supporting CDM based on consistent information. Flight planning also includes a pre-departure trajectory negotiation process using trial requests or Preliminary Flight

Plans (PFPs), which enables the AU to receive consistent, aggregated feedback on any Traffic

Flow Management (TFM) and Air Traffic Control (ATC) constraints applicable to the flight. By enabling the AUs to address constraints during the planning phase, the need to change the flight plan when the flight is airborne is reduced. This increases predictability while also reducing crew and controller workload.

Flight plan filing includes the actions of filing a flight plan in the NAS, as well as any subsequent updates to or cancellation of the filed flight plan. CSS-FD will facilitate coordination of needed changes once the flight plan is filed. CSS-FD enhancements will enable users and

FAA personnel to have a consistent view of a flight’s route or Four-Dimensional Trajectory

(4DT) and flight-specific applicable constraints. Users’ flight planning accuracy will be improved by CSS-FD-provided flight-specific feedback with applicable Traffic Management

Initiatives (TMIs), NAS automation-applied ATC Adapted Routes, and ATC Preferred Routes, which will increase the likelihood that flights, including those composed of detailed flight plans that result in fuel efficient trajectories such as constant power descent profiles to landing, will be cleared as filed.

The capabilities that support flight data sharing make flight data available to systems that use that data to perform operational and analytical functions throughout the entire lifecycle of a flight

(i.e., from pre-departure to arrival). This will be done through a modern, standards-based flight data exchange mechanism that will consolidate and, where differences exist, reconcile values for flight data, simplifying global, national, and inter-agency data sharing. Flight data will be published in a machine-readable format that has been filtered according to data access policies established by the FAA and criteria specified by the CSS-FD consumer.

1 The description in this section is intended to provide an overview of CSS-FD concepts as a whole and may include discussion of both Phase 1 and Phase 2 capabilities. Delineation and separation of Phase 1 and Phase 2 capabilities for the purposes of the current acquisition phase is addressed in Section Error! Reference source not found..

1.1 PURPOSE AND SCOPE

This document presents the functional and performance specifications for CSS-FD Phase 1.

These requirements identify essential capabilities, performance measures, and user interactions for the CSS-FD capabilities. These requirements do not refer to any specific technologies or commit future developers to a specific design.

The scope of this document focuses on the specification of functional requirements to implement the identified CSS-FD capabilities in support of CSS-FD Phase 1. CSS-FD will augment and enhance existing NAS capabilities. The CSS-FD Phase 1 concepts include the following:

• CSS-FD will address the exchange of flight data during the pre-departure phase of flight.

• CSS-FD will include the exchange of flight data at an efficiency-critical level with NAS systems (e.g., En Route Automation Modernization (ERAM)).

• CSS-FD will share flight data with consumers during the pre-departure, departure, en route, and arrival phases of flight.

• CSS-FD will leverage operational constraint information available from NAS Common

Reference (NCR) and provide constraint reference information to the appropriate enhanced AU (eAU). The term ‘eAU’ is used to indicate an Airspace User/Operator that is FF-ICE capable/FF-ICE enabled.

• CSS-FD will provide support for Continental United States (CONUS) domestic, Alaska domestic, offshore (including Hawaii), and United States controlled oceanic airspace.

• CSS-FD will implement the International Data Providers (IDP) inbound interface, currently provided by Traffic Flow Management Data (TFMData), which allows foreign

Air Navigation Service Providers (ANSP) to share flight plans and flight information with the NAS, prior to the receipt of such information by NAS ATC systems.

1.2 DEFINITION OF KEY TERMS

The following terms are used throughout this document to describe the FAA’s requirements. The terms are defined here to ensure a common understanding of the requirements.

Term Definition

Four-Dimensional

Trajectory (4DT)

A four-dimensional (x, y, z, and time) trajectory of an aircraft from gate-to-gate, at the level of fidelity required for attaining the agreed ATM system performance levels.

Agreed 4DT The 4DT generated by the Enhanced ATM Service Provider

(eASP) that is agreed between the operator and the eASP after collaboration, or imposition of pre-collaborated rules.

Archive To retain information so that it is available for historical look-up by authorized administrative users.

Airspace User (AU) An AU is a user who is authorized to file NAS format or ICAO

2012 flight plans.

Business Rules Business Rules define relationships between CSS-FD objects, logic applied, and translation into various conditional statements.

Business Rules provide a clear understanding of how the FAA expects CSS-FD to operate within the National Airspace System

(NAS).

Capability The ability to achieve a desired effect under specified performance standards and conditions through combinations of ways and means activities and resources to perform a set of activities Department of Defense Architecture Framework

(DODAF).

Constraint or Flight

Constraint

A description of the restriction on the flight’s route, generally applicable to the route/trajectory of flight or specific to a trajectory point on the route along with its impact (e.g., in altitude, speed, time, and route)..

Context Specific Data Context Specific Data retains information about originator of the data the allows for data tailoring based on the consumer needs.

Note: One example of context specific data is a case where both

STARS (STDDS) and ERAM (SFDPS) publish aircraft position information. The context specific information in this case would be the source system of the position report.

Convert/Conversion To change the presentation of data available in one form or structure to another presentation method or structure without changing the fundamental data values.

Coordinate/Coordination To bring together different elements into a relationship that enables them to work together to provide a given service or end product.

Correlate To connect or relate two or more data objects.

CSS-FD User A user who utilizes CSS-FD exposed services. Includes eAU, Flight Data consumer, ANSPs, and NAS systems.

Data Conversion Service A service that converts data from one format/format extension to a different formats/format extensions (e.g., from Air Traffic

System (ATS) to FIXM) as required for communication of data between systems.

Data Management and

Security Framework

CSS-FD foundational capability that enables flight planning, flight plan filing, and flight data sharing. This foundation includes global flight data management functions including standardization, translation, reconciliation, and validation along with reconstitution, as well as security elements required for identity and access management.

Data Reconciliation

Service

A service responsible for receiving data from multiple sources, correlating new data to existing data, and reconciling any discrepancies between the data to maintain a single common reference for each data element of the flight object when multiple values that are either redundant or inconsistent are provided by two or more systems.

Data Reconstitution

Service

A service that provides flight data upon request in order to support data reconstitution by the end user.

Data Store A repository for persistent storage of data, such as a database, a file system, or a directory.

Data Management Service A service enables access and management of information in a data store.

Data Tagging/Filtering A capability responsible for managing the message metadata elements to aid in message routing and filtering.

Data Validation Service A service responsible for validating data and applying rules to the received messages to determine if the data is acceptable for processing (based on syntax, semantics, and data values) or if it should be rejected (e.g., due to missing fields or other reasons).

Desired 4DT The preferred route of flight submitted by the eAU.

NAS Flight Coordination

Service

The NAS Flight Coordination Service provides access to CSS-FD

Flight Plan management in advance of proposed departure times for systems like FMDS and other approved NAS systems. The

FMDS Collaborative Decision Making (CDM) use case is different from that of eAUs, which are expected to file less than

222 hours prior to departure. The NAS Flight Coordination

Service request/reply functionality that FMDS uses to create and manage these early intent Flight Objects based on these early intent Flight Plans will only be accessible to approved NAS

2 Time to file varies between 22 hours, 59 minutes to 23 hours, 29 minutes depending on

ARTCC. See Table 2.1-1 in FAA En Route Automation Flight Planning Interface Guide

Version 3.0 October 1, 2022 systems, not eAUs. Internally, CSS-FD will manage these Flight

Objects using the Flight Object Management Service and update them with information received from the eAU (if/when flight plans are filed for these flights) and other source systems.

Enhanced Airspace User

(eAU)

An eAU is an AU that is capable of using FF-ICE services.

Evaluation of Constraints/

Restrictions The process by which constraints and restrictions are evaluated for a given flight, providing the ability to assess the effect of airspace constraints pertaining to a flight plan.

Feedback by Reference The ability to provide information on airspace constraints for flight plans as part of the filing status and trial request responses.

FF-ICE Filed Flight Plan A filed flight plan that is submitted in FIXM format and complies with FF-ICE/R1. It contains specified information provided to the

ATM service provider, relative to an intended flight or portion of a flight of an aircraft.

Filed Flight Plan The flight plan, including any associated updates as filed by an operator or a designated representative for use by ATS units. It is often referred to as an ATS flight plan.

Flight In the context of GUFI assignment, a flight refers to a single intended operation of an aircraft with a with specified aircraft identification that starts at a specified departure point at a specified date and time and finishes at an arrival point.

Flight Data Processor

System (FDPS)

FDPS is also referred to as Flight Data Processor 2000

(FDP2000). FDPS is the offshore en route automation system for flight data processing in Alaska.

Flight Information Flight Information is information about a flight that is contained in a Flight Object (e.g., its flight plan, ATC information relevant to the flight, such as which center is controlling it, metering programs relevant to the flight).

Flight Information

Exchange Model (FIXM) FIXM is the international data standard for flight information exchange. The FIXM data standard supports the exchange of flight information between NAS systems across multiple domains and international systems.

FIXM Core is supplemented by US FIXM extensions. Currently

US Extensions 4.3 is released with FIXM CORE 4.2. The FAA anticipates FIXM CORE 4.3 to release revised US Extensions

(4.4) to be compatible with FIXM CORE 4.3.

Throughout the J-1 document, when FAA refers to FIXM 4.3, it means FIXM CORE 4.3 and approved US Extensions version 4.4

(i.e., FAA NAS approved).

Flight Object (Data) The authoritative collection of common data elements, including metadata, describing an individual flight and available electronically for use by both the NAS users and the ATM service providers.

Flight Plan Specified information provided to the ATM service provider, relative to an intended flight or portion of a flight of an aircraft.

Filing Service A service responsible for ingestion and routing of appropriate responses to submitted filing of a flight plan by eAUs via the FF-

ICE method.

Trial Service A service provided to users to submit a Trial Request to ascertain the acceptability/validity and possible ATM impact of a potential flight plan or the effects of a change being considered, without creating an operational flight plan or changing the intended flight plan currently on file.

Function A system function is a characteristic action or activity that must be performed by an automated system in order to achieve a desired service objective (or stakeholder need).

Global Unique Flight

Identifier (GUFI)

A single reference for Flight and Flow Information for a

Collaborative Environment (FF-ICE) information pertinent to a flight that is unique globally. A GUFI is generated by the eAU and included in the eFPL when filed. If a GUFI is present in the flight plan, this capability will validate it. For flight plans filed via NADIN and received by CSS-FD from NADIN or from

SFDPS/ATOP, CSS-FD will create and assign a CSS-FD Unique

Flight Identifier (CSS-FD UFI).

Legacy User An AU that submits flight plans via the FP or FPL formats.

Lockout Time The time prior to the proposed departure time at which the flight plan filer can no longer amend or cancel the flight plan without manual coordination.

The lockout time is normally around 45 minutes before departure when the first flight strip is printed, and the NAS user can no longer amend or cancel the flight plan that has been filed for the flight.

Lockout time periods are specified in Table 2.1-1 of the FAA En

Route Automation Flight Planning Interface Guide Version 3.0, 10/01/2022.

Log To record or retain information regarding the system activities

(e.g., data entry, user actions, etc.)

Maintain To enable to continue, or to keep in a working condition.

Metadata Additional information about data published by a source (either

CSS-FD or one of its data sources), this may include original publication timestamps, source system information, and other context-specific data, etc.

Microservices Small, autonomous services that work together. Microservice applications are decentralized, independently deployable and maintainable, and organized around business capabilities.

Monitor/Control The continuous activity of evaluating and managing to track performance of an activity.

Offshore Flight Data

Processing System

(OFDPS)

OFDPS is the offshore en route automation system for flight data processing in Hawaii.

Orchestration A management function that coordinates the actions of, and communications between, various services/microservices in order to provide a given capability.

Point A point may be any aerodrome, airborne fix (including Latitude and Longitude), or user defined origin or destination as defined in

FF-ICE Manual 993 as a “Route Element Start point”.

Record To retain key system or operational data.

Required Trajectory

Element

Required Trajectory Elements include items that comprise a trajectory, including route, speed, altitude, time, and constraints that affect the trajectory.

Impacts requiring changes to Required Trajectory Elements may come from Adapted Departure Routes, Adapted Arrival Routes, Adapted Departure/Arrival Routes, ATC-imposed altitude and speed restrictions, ATC Preferred Routes, and TFM required routes.

Restrictions Documented rules that are aimed at managing the ATM system, which act on and reduce the freedom of a group of flights (i.e., flights with certain common characteristics). Restrictions result from ATM system limitations.

Return ATC Preferences Provides information and notification about a flight plan’s changes that are made either manually (i.e., ATC applies flight plan changes in ATC automation) or automatically by ATC automation to apply ATC preferences and/or local ARTCC adaptations.

Security Management The processes and methodologies which provide protection of information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability.

Service A mechanism to enable access to a set of one or more capabilities, where the access is provided using a prescribed interface and is exercised consistent with constraints and policies as specified by the service description. The mechanism is a

Performer. The “capabilities” accessed are Resources—

Information, Data, Materiel, Performers, and Geo-political

Extents.

Service Function Describes the abstract behavior of service operations, regardless of the actual implementation.

Service Oriented

Architecture (SOA)

An architectural model that involves loosely-coupled services

(possibly on heterogeneous platforms) accessible using an interface across a network and reusable among applications.

SWIM Flight Data

Publication Service

(SFDPS)

A service that publishes flight data and other flight related data.

Trajectory Modeling A function that computes and generates representative trajectory of an aircraft from given flight or flight plan information.

Translate To convert data from one format to another different format.

Unique Flight Identifier

(UFI)

A UFI is a unique flight plan identifier that is assigned by CSS-

FD, when received flight data does not contain a GUFI and cannot be matched to an existing flight that is identified by a

GUFI

1.3 APPLICABLE DOCUMENTS

The following specifications, handbooks, orders, and standards are applicable. Only the current approved version of these documents as of the contract date apply. In the event of a conflict between the Performance Work Statement (PWS) and any of the applicable documents cited below, the provisions of the PWS must apply.

1.3.1 FAA Orders

Document ID Number Title

FAA Order 1200.22E

Jan 20, 2012

External Requests for National Airspace System (NAS)

Data

FAA Order 1370.96

Apr 15, 2007

ATO System Access Control

FAA Order 1370.114

Jan 4, 2012

Implementation of FAA Telecommunications

Infrastructure Services and IS Requirements in the NAS

FAA Order 1370.117

Jan 21, 2014

National Airspace System (NAS) Internet Protocol (IP)

Addressing Policy

FAA Order 1370.121B

Apr 25, 2002

FAA Information Security and Privacy: Policy and

Supplemental Implementing Directives (Governance, FAA

Implementation of NIST Controls, FAA Supplemental

Security Controls, User Responsibilities and Obligations, Protection of Sensitive Unclassified Information (SUI) on

Federal and non-Federal Information Systems and

Services by External Entities)

FAA Order 1375.1F

Nov 4, 2021

Data and Information Management Policy

FAA Order 1375.8

May 26, 2020

Guidance for Implementing Standardized Maintenance and

Monitoring Data Exchanges

FAA Order 1600.69C

Aug 22, 2016

FAA Facility Security Management Program

FAA Order 1600.75

Feb 1, 2005

Protecting Sensitive Unclassified Information (SUI)

FAA Order 1800.66

Aug 10, 2022

Configuration Management Policy

FAA Order 4600.27D

Dec 29, 2021

Personal Property Asset Lifecycle Management

FAA Order JO 6000.53E

May 2, 2022

Remote Maintenance Monitoring and Control (RMMC)

Interface Development and Implementation

1.3.2 Other FAA Documents

Document ID/Date Title

FAA-HDBK-006D

Oct 8, 2020

FAA Handbook: System Reliability, Maintainability, and

Availability (RMA)

1.3.3 Other Government Documents

Copies of federal publications may be obtained from the U.S. Government Printing Office, 710

North Capitol Street, Washington DC, 20401, by calling (202) 512-0132, or through the web site http://bookstore.gpo.gov/.

DOT Order 1351.14 Media Protection

DOT Policy 2006-22

Sep 21, 2006

Implementation of DOT's Protection of Personally

Identifiable Information

FIPS-140-2

May 25, 2001

Security Requirements for Cryptographic Modules

FIPS-140-3

Mar 22, 2019

Security Requirements for Cryptographic Modules

NIST SP 800-53 Rev. 5

Sep 23, 2020

Security and Privacy Controls for Information Systems and

Organizations, Rev. 5

NIST 800-60

Aug 2008

Guide for Mapping Types of Information and Information

Systems to Security Categories

NIST SP 800-81-2

Sep 2013

Secure Domain Name System (DNS) Deployment Guide

NIST SP 800-84

Sep 2006

Guide to Test, Training, and Exercise Programs for IT

Plans and Capabilities

OMB Circular A-130, Jul 2016

Managing Information as a Strategic Resource

1.3.4 Non-Government Documents

Non-government documents may be requested from the organization responsible for the development and dissemination of the required document.

ICAO Document 9965 International Civil Aviation Organization (ICAO) Manual on Flight and Flow – Information for a Collaborative

Environment (FF-ICE), Volume II Implementation

Guidance, 2012

ICAO Document 4444 ICAO Procedures for Air Navigation Services — Air

Traffic Management (PANS-ATM) (Doc. 4444)

RFC 5424 Internet Engineering Task Force (IETF), Internet Standard

Request for Comments (RFC) 5424, the Syslog Protocol http://bookstore.gpo.gov/

2 CAPABILITY DESCRIPTION AND PROGRAM INFORMATION

2.1 OPERATIONAL CONCEPT

The FAA has investigated two concepts that relate to how a flight data consumer and an AU exchange flight data with the NAS. The first was Unified Flight Planning and Filing (UFPF), which addressed problems with how AUs submit planning and filing data to the NAS. The second was Flight Object Exchange Services (FOXS), which defined an enhanced approach to sharing NAS flight data with various data consumers. These two concepts have been unified under CSS-FD and are referred to as CSS-FD Flight Planning and Filing (FP&F) and CSS-FD

Flight Data Sharing (FDS), respectively.

The FP&F and FDS components have been further categorized into eight capabilities and divided into two phases. Capabilities are segmented in this way so that the foundational elements are implemented first in Phase 1. Additional capabilities can then be realized as part of Phase 1 or with implementation of Phase 2 capabilities. Table 1 contains a mapping of Phase 1 capabilities to J-1 Requirements sections. Appendix A contains a mapping of each Phase 1 requirement to either FDS or FP&F.

Table 1: Capabilities Mapping to J-1 Requirements

Capability Capability Description J-1 Requirement Sections

1 Data Management and Security

Framework

3.1.1 – 3.1.6, 3.1.8, 3.2.1,

3.3 – 3.5

2 Flight Planning and Flight Plan Filing 3.2.2, 3.2.2.1, 3.2.2.3,

3.2.3 – 3.2.5

3 Feedback by Reference 3.1.7

4 Return ATC Preferences 3.2.2.2

2.1.1 High-Level Concept Graphic

The CSS-FD operational concept is illustrated in the program-level Operational View (OV-1) presented in Figure 1 and is intended to provide a notional understanding of the goals of the

CSS-FD program. It is intended for a high-level understanding of the elements related to CSS-

FD and is not meant to be a comprehensive depiction of the NAS or NAS operations. Depiction of facilities, systems, and actors are intended to be conceptual abstractions.

Figure 1: CSS-FD Operational Concept Overview (OV-1)

3 CSS-FD REQUIREMENTS

Each requirement (“must” statement) in this document is provided a permanent identifying tag in the form of “CSS-FD####” or “CSS-FD####-#” where the #### or ####-# indicates a value that is unique to the requirement and persistent through the life of the requirement. This is used for configuration management and requirement life-cycle control. No specific meaning should be ascribed to requirement identification (ID) numbers, and the ordering of the ID numbers does not have any implications as to the importance or precedence of a requirement.

CSS-FD is expected to deploy multiple services that may be called or leveraged by CSS-FD as well as other NAS systems. These services are expected to accomplish the functions included in

Section 3, CSS-FD Requirements. In keeping with the Automation Evolution Strategy (AES) these services may be deployed as “services”, “microservices”, and/or “shared services”3;

however, all are denoted “services” in the following sections. These services may be individually exposed SWIM services offered by CSS-FD and others may be services internal to CSS-FD. The functionality in each requirement statement may shift to a more appropriate service during solution development.

3.1 CORE SERVICES

The internal CSS-FD Core Services are included below in Table 2.

Table 2: CSS-FD Core Services

Service Name Service Description

Data Validation

Service

Responsible for validating data and applying rules to the received messages to determine if the data is acceptable for processing (based on syntax, semantics, and data values) or if it should be rejected (e.g., due to missing fields or other reasons).

Data

Transformation

Service

A service that transforms data from one data format/format extension to a different data formats/format extensions as required for communication of data between systems (e.g., FIXM and ATS).

Flight Data

Reconciliation

Service

Responsible for reconciling any discrepancies between new and old data to maintain a single common reference for each data element of the flight object when multiple values that are either redundant or inconsistent are provided by two or more systems.

Flight Object

Management

Service

Responsible for storage and management of common information elements describing an individual flight.

3 The Automation Evolution Strategy (AES) defines these types of services at https://www.faa.gov/about/office_org/headquarters_offices/ang/icn/aes

Flight Identifier

Management

Service

Responsible for management of GUFI and UFI unique references for identification of information pertinent to a flight.

Identity and Access

Management

Service

Responsible for role-based access control for user access to information and data elements contained within CSS-FD.

Constraint Service Responsible for obtaining, identifying, and correlating flight constraints relevant to an FF-ICE flight plan.

Data Management

Service

Responsible for storage, logging, and management of non-Flight Object data required for the operation of the CSS-FD system's services (except for the Flight Object Management Service)

3.1.1 Data Validation Service

CSS-FD2057 The Data Validation Service must validate each received data message from each SWIM data source defined in Section 5.2.2 in accordance with each source’s respective schema(s) and/or rules specified in its interface documentation.

CSS-FD2060 The Data Validation Service must validate data acquired from the SWIM data sources defined in Section 5.2.2 based on business rules contained in

Attachment J-10, CSS-FD Business Rules.

CSS-FD2058 The Data Validation Service must verify the syntax of each received data message.

CSS-FD1256-1 The Data Validation Service must validate each data element acquired from non-SWIM data interfaces defined in Section 5.2.1.

CSS-FD1256 The Data Validation Service must validate each data element acquired from National Airspace Data Interchange Network (NADIN) data source defined in Section 5.2.1 in accordance with the Attachment J-3.M ERAS

Interface Reference Guide 5-9-24, FAA En Route Automation Flight

Planning Interface Guide Version 3.1, May 9, 2024.

CSS-FD1257 The Data Validation Service must respond with a rejection message for each request data message submitted to a CSS-FD request/reply service that fails validation checks.

CSS-FD1258 The Data Validation Service must reject each data message that fails the validation checks.

3.1.1.1 Data Validation – FF-ICE

CSS-FD1120 The Data Validation Service must validate FF-ICE Filed Flight Plan messages in accordance with: ICAO Doc 9965 Manual on FF-ICE, Volume II Implementation Guidance.

CSS-FD1122 The Data Validation Service must validate FF-ICE Flight Plan Update messages, in accordance with: ICAO Doc 9965 Manual on FF-ICE, Volume II Implementation Guidance.

CSS-FD1126 The Data Validation Service must validate FF-ICE Flight Cancellation messages, in accordance with: ICAO Doc 9965 Manual on FF-ICE, Volume II Implementation Guidance.

CSS-FD1128 The Data Validation Service must validate FF-ICE Flight Data Request messages, in accordance with: ICAO Doc 9965 Manual on FF-ICE, Volume II Implementation Guidance.

CSS-FD2523 The Data Validation Service must remove non-NAS FIXM extension data elements from FF-ICE messages before validating each message.

CSS-FD2002 The Data Validation Service must validate a GUFI is UUID V4 format.

CSS-FD1111-1 The Data Validation Service must apply the business rules contained in

Attachment J-10, CSS-FD Business Rules to validate the messages defined in the Attachment J-7, CSS-FD Service Requirements Document (SRD).

3.1.2 Data Transformation Service

CSS-FD2032 The Data Transformation Service must translate ATS message fields to

FIXM 4.3, in accordance with FIXM User Manual, Mapping of ATS

Fields to FIXM, https://docs.fixm.aero/#/ats-message-to-fixm-mapping/mapping-of-ats-fields-to-fixm and Attachment J-3.M ERAS

Interface Reference Guide 5-9-24, FAA En Route Automation Flight

Planning Interface Guide Version 3.0, May 9, 2024.

CSS-FD2096 The Data Transformation Service must translate FIXM 4.3 messages to

ATS messages in accordance with FIXM User Manual, Translating FF-

ICE FIXM Messages to ATS Messages, https://docs.fixm.aero/#/ats-message-to-fixm-mapping/translating-ffice-fixm-messages-to-ats-messages and Attachment J-3.M ERAS Interface Reference Guide 5-9-24, FAA En Route Automation Flight Planning Interface Guide Version 3.0, May 9, 2024.

CSS-FD1111-2 The Data Transformation Service must apply the business rules contained in Attachment J-10, CSS-FD Business Rules when translating messages defined in the Attachment J-7, CSS-FD Service Requirements Document

(SRD).

https://docs.fixm.aero/#/ats-message-to-fixm-mapping/mapping-of-ats-fields-to-fixm https://docs.fixm.aero/#/ats-message-to-fixm-mapping/mapping-of-ats-fields-to-fixm https://docs.fixm.aero/#/ats-message-to-fixm-mapping/translating-ffice-fixm-messages-to-ats-messages https://docs.fixm.aero/#/ats-message-to-fixm-mapping/translating-ffice-fixm-messages-to-ats-messages https://docs.fixm.aero/#/ats-message-to-fixm-mapping/translating-ffice-fixm-messages-to-ats-messages

3.1.3 Flight Data Reconciliation Service

CSS-FD1297 The Flight Data Reconciliation Service must perform flight data reconciliation to a Flight Object.

CSS-FD1298 The Flight Data Reconciliation Service must identify logical inconsistencies for flight data element(s) in the flight data message according to Attachment J-10, CSS-FD Business Rules and Attachment J-

12, Flight Object (FO) Workbook.

CSS-FD2589 The Flight Data Reconciliation Service must identify semantic inconsistencies for flight data element(s) in the flight data message according to Attachment J-10, CSS-FD Business Rules and Attachment J-

12, Flight Object (FO) Workbook.

CSS-FD2590 The Flight Data Reconciliation Service must identify syntactical inconsistencies between corresponding data fields in the Flight Object and flight data element(s) in the flight data message according to Attachment

J-10, CSS-FD Business Rules and Attachment J-12, Flight Object (FO)

Workbook.

CSS-FD1296 The Flight Data Reconciliation Service must reconcile elements in each flight information message received from the flight data sources specified in Section 5.2, with the applicable flight data element(s) contained in the corresponding Flight Object according to Attachment J-10, CSS-FD

Business Rules and Attachment J-12, Flight Object (FO) Workbook.

CSS-FD2070 The Flight Data Reconciliation Service must reconcile each flight data element that contains conflicting input data for a specific data element according to Attachment J-10, CSS-FD Business Rules.

CSS-FD2138 The Flight Data Reconciliation Service must reject each flight data element contained within flight data deemed to be incomplete, potentially erroneous, or inaccurate according to Attachment J-10, CSS-FD Business

Rules.

CSS-FD2062-1 The Flight Data Reconciliation Service must store the updated flight information, including metadata, in the Flight Object upon completion of reconciliation.

3.1.4 Flight Object Management Service

The term 'Flight Object’(FO) refers to the authoritative collection of common data elements, including metadata, describing an individual flight and available electronically for use by both

NAS users and ATM service providers. FO refers to the blueprint of current data and metadata maintained about a flight ('flight' as defined by CSS-FD). The ‘FO for a flight’ is one instance of the FO for a given flight. However, depending on context, the term 'Flight Object' could be used as a shorthand for an instance, that is, to mean 'the FO for a flight'. Since flight data changes over time (for example, the estimated time of arrival for a flight may change through the lifetime of the flight), FO history also needs to be maintained. When reconstituting data, users can request

FO history be returned for each FO.

CSS-FD2139 The Flight Object Management Service must maintain Flight Objects according to Attachment J-10, CSS-FD Business Rules.

CSS-FD2050-1 The Flight Object Management Service must perform create, read, update, delete controls according to Attachment J-10, CSS-FD Business Rules

CSS-FD2036 The Flight Object Management Service must store Flight Objects in the

Flight Object data store.

CSS-FD2120 The Flight Object Management Service must store data, including metadata, received from sources identified in Section 5.2 for 15 days.

CSS-FD2140 The Flight Object Management Service must store metadata associated with a Flight Object.

CSS-FD2544 The Flight Object Management Service must create a Flight Object for each flight.

CSS-FD2554 The Flight Object Management Service must store each Flight Object for

15 days.

CSS-FD2631 The Flight Object Management Service must create a Flight Object for each unmatched flight upon receipt of information from the sources listed in Section 5.2.

CSS-FD2010-2 The Flight Object Management Service must associate each generated

CSS-FD UFI with its associated Flight Object.

CSS-FD2554-1 The Flight Object Management Service must store the history associated with each Flight Object for 15 days.

CSS-FD2546 The Flight Object Management Service must archive each Flight Object.

CSS-FD2042 The Flight Object Management Service must be capable of retrieving each

Flight Object from the Flight Object data store.

CSS-FD2545 The Flight Object Management Service must update a Flight Object.

CSS-FD2046 The Flight Object Management Service must update flight information within the Flight Object data store.

CSS-FD1278 The Flight Object Management Service must match received flight data with previously received flight data contained within the Flight Object data store.

CSS-FD2062 The Flight Object Management Service must correlate each flight information message received from the flight data sources specified in

Section 5.2, with the applicable flight data entry in the Flight Object data store.

CSS-FD1346 The Flight Object Management Service must update the Flight Object using the most recent update published by each flight data source.

CSS-FD2052 The Flight Object Management Service must provide the capability to designate flight information as deleted within the Flight Object data store.

CSS-FD2050 The Flight Object Management Service must not allow updates to cancelled entries in the Flight Object data store.

CSS-FD2148 The Flight Object Management Service must update the status of a flight entry in the Flight Object to be “Cancellation Requested” upon validation of an FF-ICE Flight Cancellation message.

CSS-FD2149 The Flight Object Management Service must update the status of a flight entry in the Flight Object to be “Cancelled” upon receipt of cancellation acknowledgement from ATC automation.

CSS-FD2063 The Flight Object Management Service must store constraint references within a Flight Object.

CSS-FD1174 The Flight Object Management Service must update the constraint references associated with a Flight Object when the Constraint Service receives a constraint update, creation, or deletion message.

CSS-FD2124 The Flight Object Management Service must store data associated with a

Flight Object per the Attachment J-12, Flight Object (FO) Workbook.

CSS-FD2142 The Flight Object Management Service must store FF-ICE Filed Flight

Plan submission data associated with a Flight Object.

CSS-FD2144 The Flight Object Management Service must store FF-ICE Filing Status message data associated with a Flight Object.

CSS-FD2146 The Flight Object Management Service must store FF-ICE Flight Plan

Update message data associated with a Flight Object.

3.1.5 Flight Identifier Management Service

CSS-FD2008-1 The Flight Identifier Management Service must track each flight using a unique identifier.

CSS-FD2520 The Flight Identifier Management Service must ensure that the unique identifier assigned remains unique for at least 10 years.

3.1.5.1 Flight Identifier Management: GUFI Handling

The Flight Identifier Management Service provides GUFI validation to facilitate flight information correlation and FO updates from all flight data received with a GUFI. For FF-ICE filed flight plan data, FF-ICE requires all flight and flow information to contain a GUFI.

CSS-FD1282 The Flight Identifier Management Service must verify that GUFI-flight data combinations are unique by applying business rules according to

Attachment J-10, CSS-FD Business Rules.

CSS-FD1004 The Flight Identifier Management Service must ensure each FF-ICE filed flight plan has a valid GUFI.

CSS-FD2018-1 The Flight Identifier Management Service must set the GUFI to be immutable, once the GUFI is associated with a Flight Object from the

Flight Object data store by applying business rules according to

Attachment J-10, CSS-FD Business Rules.

3.1.5.2 Flight Identifier Management: CSS-FD UFI Handling

The Flight Identifier Management Service provides validation and matching of flight information for correlation and FO updates for all flight data received without a GUFI. For flight data without a GUFI, the Flight Identifier Management Service will match previously received data, and if no match is found, will generate a CSS-FD UFI used to update and uniquely identify the

Flight Object. See Section 3.1.5.3 for CSS-FD UFI generation requirement details.

CSS-FD1286 The Flight Identifier Management Service must verify that CSS-FD UFI-flight data combinations are unique by applying business rules according to Attachment J-10, CSS-FD Business Rules.

CSS-FD1206 The Flight Identifier Management Service must determine the flight’s

CSS-FD UFI when the flight data does not contain a GUFI or CSS-FD

UFI.

3.1.5.3 Flight Identifier Management: CSS-FD UFI Generation

CSS-FD2010-1 The Flight Identifier Management Service must generate a CSS-FD UFI when required as specified by business rules in Attachment J-10, CSS-FD

Business Rules.

CSS-FD2007 The Flight Identifier Management Service must generate a CSS-FD UFI in conformance with Universally Unique Identifier (UUID) V4.

CSS-FD2010 The Flight Identifier Management Service must generate a CSS-FD UFI upon receipt of a flight plan that cannot be matched to an existing Flight

Object.

CSS-FD2008 The Flight Identifier Management Service must generate a CSS-FD UFI upon receipt of a flight data message that cannot be matched to an existing Flight Object.

CSS-FD1288 The Flight Identifier Management Service must generate a new CSS-FD

UFI in the case of CSS-FD UFI-flight uniqueness verification errors.

3.1.6 Identity and Access Management Service

CSS-FD1304 The Identity and Access Management Service must authorize user access in accordance with the FAA data access policy and the consumer’s on-ramping credentials.

CSS-FD2040 The Identity and Access Management Service must provide access to flight data to authorized users.

CSS-FD1304-1 The Identity and Access Management Service must manage access to FF-

ICE Services through the ability to assign permissions to roles (Role

Based Access Control - RBAC).

CSS-FD1304-2 The Identity and Access Management Service must manage access to the

Flight Object data elements.

CSS-FD2617 The Identity and Access Management Service must restrict user access to

NAS Flight Coordination Service for creating and managing early intent

Flight Objects and/or Enhanced Flight Plans.

CSS-FD2527 The Identity and Access Management Service must provide the capability to apply permissions to CSS-FD users.

CSS-FD2528-1 The Identity and Access Management Service must provide the capability to assign, modify, and revoke CSS-FD permissions at runtime.

3.1.7 Constraint Service

The Constraint Service functionality is only applicable to flight plans submitted by an eAU.

Table 3: Constraints for Feedback by Reference

Category Constraint

Airspace Constraints • Special Use Airspace (SUA) o Special Activity Airspace (SAA) o Warning Areas o Restricted Areas o Prohibited Areas o Alert Areas o Military Operations Areas (MOA) o Aircraft Hazard Areas (AHA) o Air Traffic Control Assigned Airspace (ATCAAs) o Altitude Reservations (ALTRVs) o Temporary Flight Restrictions (TFRs) o Aerial Refueling Tracks/Anchors (AR)

• Closed/Impacted Routes

Traffic Management

Constraints

• TFM Advisories

• Flow Evaluation Area (FEA)/Flow Constrained Area (FCA)

• Airspace Flow Program (AFP)

Category Constraint

• Miles in Trail (MIT)/Minute in Trail (MINIT)

• Ground Delay Program (GDP)

• Ground Stop (GS)

• Departure Stop

• Collaborative Trajectory Option Program (CTOP)

• Metering Restrictions

• Departure Spacing Program (DSP)

• Reroute (TFM Advisory Required)

• Approval Request (APREQ)/Call for Release (CFR)

• Time-Based Metering (TBM)

Airport Constraints • Airport Closure

• Closed Runway

• Closed Taxiway

• Airport Configuration at Departure/Destination

• Deicing

NAS Resources

Constraints

• Communication Constraints

• Navigation Aid (NAVAID) Status

• Radar

• Instrument Landing System (ILS)

• Global Positioning System (GPS) status

• Outages

Others • Notice to Air Missions (NOTAMs) applicable to the flight’s trajectory as provided by NCR

CSS-FD2539 CSS-FD must generate a 4DT for flight plans using Government

Furnished Information (GFI) trajectory-modeling software.

CSS-FD1156 The Constraint Service must use the CSS-FD generated 4DT to retrieve relevant constraints for:

a. FF-ICE Filed Flight Plans

b. FF-ICE Flight Plan Updates

c. FF-ICE Trial Requests

d. ATC-Amended Flight Plans

CSS-FD2605 The Constraint Service must refine constraints by applying business rules according to Attachment J-10, CSS-FD Business Rules to ensure relevance to:

a. FF-ICE Flight Plans,

b. FF-ICE Trial Requests,

c. FF-ICE Flight Plan Updates, and

d. ATC-Amended Flight Plans

CSS-FD1175 The Constraint Service must maintain NCR subscription(s) to receive updates for new Constraints or changes to Constraints for the following:

a. FF-ICE Filed Flight Plans

b. FF-ICE Flight Plan Updates

c. ATC-Amended Flight Plan

CSS-FD2106 The Constraint Service must log constraint data retrieval and subscriptions.

CSS-FD2633 The Constraint Service must cancel NCR subscription(s) upon flight departure or receipt of a cancellation message.

CSS-FD1519 The Constraint Service must provide FF-ICE flight plan constraints using the flight plan’s CSS-FD modeled 4DT.

CSS-FD1182 The Constraint Service must evaluate constraints associated with an FF-

ICE flight plan by applying business rules according to Attachment J-10, CSS-FD Business Rules.

3.1.8 Data Management Service

The data storage requirements define the capability to retain and access data associated with

CSS-FD.

CSS-FD1264 The Data Management Service must provide caching and persistent storage capabilities.

CSS-FD2130 The Data Management Service must be capable of storing both data and metadata.

CSS-FD1264-1 The Data Management Service must be capable of tagging data for traceability to actions performed with the data.

CSS-FD1264-2 The Data Management Service must maintain changes made to data so audits for traceability can be performed.

CSS-FD1264-3 The Data Management Service must provide a GUI for authorized users to have command and control of storage, archival, retrieval and audit functions.

CSS-FD2112 The Data Management Service must log each create, read, update, delete data storage activity.

3.1.8.1 Archival

CSS-FD2150 The Data Management Service must have an archival capability that is customizable for durations up to 3 years.

CSS-FD2156/7 The Data Management Service must have an archive retrieval capability that can be customized to retrieve and sort the returned data based on time, date, UUID, and free text entry/search.

3.1.8.2 Audit

CSS-FD2162 The Data Management Service must time stamp events for use in audit record generation.

CSS-FD2158 CSS-FD must provide the capability for authorized users to perform audits on all system activities.

CSS-FD2160 CSS-FD must provide the capability for authorized users to perform audits on all changes made to data.

3.2 CSS-FD SWIM SERVICES

The CSS-FD SWIM services are exposed to eAUs and/or NAS Systems and are included below in Error! Reference source not found..

Table 4: CSS-FD SWIM Services

Flight Data

Reconstitution

Service

Responsible for accepting requests for data and sending data to CSS-FD users to reconstitute data up to 15 days in the past.

Exchange pattern: Request/Reply, responses may be via message publication

Filing Service Responsible for accepting filed FF-ICE flight plans from eAUs, communicating flight plan data with FAA automation, sending FF-ICE submission responses, and sending FF-ICE filing status and updates.

Exchange pattern: Request/Reply

Data Publication

Service

Responsible for publishing flight data and other related data to subscribers.

Exchange pattern: Publish/Subscribe

Flight Data Request

Service

Responsible for accepting for FF-ICE Request Flight Plan Information request messages and sending data to requestors.

Exchange pattern: Request/Reply

Trial Service Responsible for accepting FF-ICE Trial Requests from eAUs, sending

FF-ICE trial responses, and sending FF-ICE submission responses.

Exchange pattern: Request/Reply

NAS Flight

Coordination

Service

Responsible for receiving CDM and Official Airline Guide (OAG) data from FMDS for creation of Flight Objects before flights are filed by eAUs and AUs. NAS Flight Coordination Service is only expected to be used by FMDS in CSS-FD Phase 1.

Exchange pattern: Request/Reply

International Data

Provider (IDP)

Submission Service

Responsible for receiving flight data from IDP according to the

TFMData schema. International Data Provider Submission Service is only to be used by IDP users.

Exchange pattern: Fire and forget

All FF-ICE messages are specified in the ICAO Doc 9965 FF-ICE Manual Volume II –

Implementation Guidance in Appendix C – FF-ICE Messages. The tables in ICAO Doc 9965

Volume II, Appendix C include additional information in the “Guidance" column pertaining to specific…