DRAFT SIR CSS-FD Attachment J-1.pdf

Solicitation # Attachment J-1

Federal Aviation Administration

Common Support Services – Flight Data (CSS-FD)

CSS-FD Functional and Performance Specification

September 2023

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 Government Documents

1.3.3 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 SERVICE COMPONENTS

3.1.1 Data Validation

3.1.2 Data Mediation

3.1.3 Reserved

3.1.4 Flight Data Reconciliation

3.1.5 Flight Information Reconstitution

3.1.5.1 Flight Information Reconstitution Feeds

3.1.5.2 Generate Flight Information Reconstitution

3.1.5.3 Monitor Flight Information Reconstitution

3.1.6 Flight Object Management

3.1.6.1 Flight Identifier Management

3.1.7 Identity and Access Management

3.1.8 Flight Planning

3.1.8.1 FF-ICE Flight Plans

3.1.8.2 Filed Flight Plan Validation

3.1.8.3 Filed Flight Plan Response Messages

3.1.8.4 Update Flight Filing Feedback

3.1.8.5 Filed Flight Plan Dissemination

3.1.8.6 Reserved

3.1.8.7 Trial Request Processing

3.1.8.8 Feedback by Reference

3.1.8.9 Return ATC Preferences

3.2 BUSINESS RULES MANAGEMENT SYSTEM

3.3 PUBLICATION AND REPLY SERVICES

3.4 DATA STORAGE

3.4.1 Archival

3.4.2 Audit

3.5 SYSTEM MONITORING AND MANAGEMENT

3.6 SYSTEM LOGGING

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

5 INTERFACES

5.1 INTERFACES TO OTHER FAA ENTERPRISE ARCHITECTURE ELEMENTS

ii

5.2 DATA SOURCES

6 INFORMATION SYSTEMS SECURITY (ISS)

iii

TABLE OF TABLES

Table 1: Capabilities Mapping to J-1 Requirements Table 2: Constraints for Feedback by Reference Table 3: CSS-FD Input Data and Frequency Table 4: CSS-FD Output Data and Frequency Table 5: CSS-FD Services and Criticality Table 6: CSS-FD Data Source SWIM Services

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 (PFPLs), 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 will be cleared as filed, including those composed of detailed flight plans that result in fuel efficient trajectories such as constant power descent profiles to landing.

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 simplify global, national, and inter-agency data sharing and consolidate and, where differences exist, reconcile values for flight data. Flight data will be published in an expandable and 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 2.

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 are written from the point of view of the end user and 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 be a new service within the FAA, but it is replacing and enhancing existing NAS capabilities. The CSS-FD concepts include the following:

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

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

• CSS-FD will include the distribution of efficiency-critical flight data among NAS systems (e.g., En Route Automation Modernization (ERAM)).

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

Reference (NCR) and provide constraint reference information to the appropriate Enhanced AU (eAU).

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

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.

Authorized User (AU) An AU is a user who is authorized to file flight plans.

Business Rules Engine A management engine that evaluates data to determine appropriate application of business rules, and provides access control to and information exchange with the relevant Business Rules Microservice(s).

Term Definition Business Rules Management System

A Business Rules Management System (BRMS) is a comprehensive framework with three distinct components:

Development Environment, Repository, Business Rules Engine.

These will facilitate automation, management and applilcation of FAA business rules on flight data processing (e.g., flight plan acceptance, flight plan updates, ATC constraints, trial requests, etc.) within CSS-FD.

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

Results from applying a restriction to a particular flight and describes bounds (e.g., in altitude, speed, time, and route) that constrain free movement of the flight.

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.

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.

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 Matching and 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 Publication/Subscription Management

A service that manages the exchange of data between publishers and subscribers.

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 Tagging/Filtering Service

A service responsible for managing the message metadata elements to aid in message routing and filtering.

Data Validation Microservice

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 4DT that is requested and generated by the AU with knowledge of the ATM systems’ configuration and published restrictions.

Enhanced Authorized User (eAU)

An eAU is an AU that is capable of using FF-ICE services. A GUFI is not sent back to an AU because the AU cannot accept that information in the current system.

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 and other restrictions pertaining to a flight plan.

Feedback by Reference The ability to provide information on airspace constraints or other restrictions 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 Data Publication Services

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

Flight Information Flight information include, but are not necessarily limited to, flight plan submission, flight plan amendments, trial requests, etc.

Flight Object (Data) A collection of common information elements 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.

Flight Plan Filing A service responsible for ingestion and routing of appropriate responses to submitted filing of a flight plan by AUs and eAUs via both the legacy method and the FF-ICE method, respectively.

Flight Planning Service

(CSS-FD)

Flight planning service provides feedback on flight plans or flight intent in the planning stage, validating and evaluating flight planning requests, updating feedback as constraints change, and distributing flight planning information as appropriate.

Flight Planning/Trial Request

A service provided to users and traffic managers to submit a “what-if” type of 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 An activity that is specified in context of the resource (human or machine) that performs it [Ministry of Defense Architecture Framework (MODAF)].

Activity: Work, not specific to a single organization, weapon system or individual that transforms inputs (Resources) into outputs (Resources) or changes their state [DODAF].

GUFI A single reference for Flight and Flow Information for a Collaborative Environment (FF-ICE) information pertinent to a flight that is unique globally. If a GUFI is present in the flight plan, this capability will validate it. If a GUFI is not present, e.g., due to a legacy user, the system will create and assign a Unique Flight Identifier.

Flight Information Management

The management of a single globally unique reference identification for FF-ICE information pertinent to a flight.

Legacy Interface Management

The processes that support the interface between CSS-FD functionality and the legacy systems, e.g., NADIN/NMR.

Lockout Time The time prior to the proposed departure time at which the flight plan filer can no longer amend 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 the flight plan that has been filed for the flight.

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.

Mediate/Mediation The transformation of data (structure and/or content) to establish semantic equivalence of different representations.

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

Planning Service (FF-

ICE)

Planning service permits eAU to submit information concerning the intention to operate a flight (a PFPL) for evaluation. Feedback is provided regarding restrictions and associated constraints that will be applicable to the flight, and it allows for a collaborative, iterative planning process to optimize the plan and reduce any surprises once a filed flight plan is submitted.

Preliminary Flight Plan

(PFPL)

The flight plan submitted by an operator or a designated representative to conduct collaborative planning of a flight, prior to filing a flight plan for use by ATS units.

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 ERAM) or by 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 type of delivered functionality, specified independently of the resources that provide it [MODAF].

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 [DODAF].

Service Function Describes the abstract behavior of service operations, regardless of the actual implementation [Unified Profile for DODAF and

MODAF (UPDM)].

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.

Trajectory Modeling A service 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.

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 1370.129

TBD

Information Security Requirements for Federal Aviation Administration (FAA) Telecommunications Services in the Mission Critical and Mission Essential Operating Environments

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

1.3.2 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.3 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), 2012

ICAO Document 4444 ICAO Procedures for Air Navigation Services — Air Traffic Management (PANS-ATM) (Doc. 4444) 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 seven 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.

Table 1: Capabilities Mapping to J-1 Requirements

Capability Capability Description J-1 Requirement Sections 1 Data Management and Security

Framework (for flight planning and flight plan filing)

3.1.1 - 3.1.7;

3.2 - 3.6

2 Flight Planning and Flight Plan Filing 3.1.8.1 - 3.1.8.7 3 Feedback by Reference 3.1.8.8 4 Return ATC Preferences 3.1.8.9

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

NOTE: All "CSS-FD####-BR" formatted requirements will be extracted from the Final System Specification and incorporated into a Section J Attachment J-X, Common Support Services Flight Data Business Rules for the Final SIR in order to encompass initial Business Rules and any additional business rules guidance.

3.1 SERVICE COMPONENTS

CSS-FD services provide the foundation of CSS-FD capabilities and allow future NAS systems to reuse that functionality as a shared service without modification to other CSS-FD functional elements. Services include:

• Data Validation - Validates data and applies 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 Mediation - The transformation of data (structure and/or content) to establish semantic equivalence of different representations.

• Data Reconciliation - A service responsible for flight data matching, producing and maintaining 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 - Provides flight object data upon request in order to support data reconstitution by the data end user.

• Flight Object Management - The management of a single globally unique reference idenitificaton for FF-ICE information pertinent to a flight.

• Identity and Access Management – Management of AU and eAU permissions and access to CSS-FD flight information and data per FAA Governance.

• Flight Planning - Flight Planning will support the ingestion and routing of appropriate responses to flight plan submissions by both AUs and eAUs via the legacy method and FF-ICE method, respectively.

3.1.1 Data Validation

CSS-FD2057 The CSS-FD system must validate each received data message from all interfaces defined in Section 5.2.

CSS-FD2058 The CSS-FD system must verify the syntax of each received data message.

CSS-FD2059 The CSS-FD system must verify the semantic consistency of each received data message.

CSS-FD2060 The CSS-FD system must ensure each received data message complies with defined business rules.

CSS-FD1255 The CSS-FD system must validate data values in each received data message.

CSS-FD1256 The CSS-FD system must validate each data element acquired from data sources defined in Section 5.2 complies with the respective interface and/or data documentation of the source.

CSS-FD1257 The CSS-FD system must respond with a rejection message for each request data message that fails the validation checks.

CSS-FD1258 The CSS-FD system must reject each data message that fails the validation checks.

3.1.2 Data Mediation

Data mediation is the ability to accept and translate between FIXM versions (e.g., FIXM 4.2 to

FIXM 3.0).

CSS-FD2025 The CSS-FD system must perform data mediation from data sources defined in Section 5.2.

CSS-FD2026 The CSS-FD system must mediate flight information messages in all

FIXM versions between FIXM 3.0 through 4.3 with the respective approved NAS extension(s).

CSS-FD2032 The CSS-FD system must mediate ATS format messages received over NADIN/NMR to FIXM 4.3.

CSS-FD2096 The CSS-FD system must mediate from FIXM 4.3 to ATS format messages.

3.1.3 Reserved

3.1.4 Flight Data Reconciliation

CSS-FD1297 The CSS-FD system must perform flight data reconciliation to an authoritative Flight Object.

CSS-FD2062 The CSS-FD system must correlate each piece of new flight information with an authoritative Flight Object.

CSS-FD2066 The CSS-FD system must match each applicable data element in a flight information message with its corresponding field in the authoritative Flight Object.

CSS-FD1298 The CSS-FD system must identify any logical, semantic, and syntactical inconsistencies for data element(s) in the flight information message.

CSS-FD1296 The CSS-FD system must reconcile all flight information messages received from all flight data sources specified in Section 5.2.

CSS-FD2062-1 The CSS-FD system must store the updated flight information in the authoritative Flight Object upon completion of reconciliation.

CSS-FD2070-BR The CSS-FD system must reconcile each flight data element that contains conflicting input data for a specific data element based on configured business rules.

CSS-FD2138-BR The CSS-FD system must reject each piece of flight information according to the configured business rules.

3.1.5 Flight Information Reconstitution

CSS-FD2069 The CSS-FD system must provide flight information reconstitution.

CSS-FD2069-1 The CSS-FD system must utilize the identity and access management service to validate access to flight information reconstitution.

CSS-FD2069-2 The CSS-FD system must provide the capability for authorized requesters to request flight information reconstitution.

CSS-FD2071 The CSS-FD system must provide flight information reconstitution from the Flight Object data store based on criteria specified in the request.

3.1.5.1 Flight Information Reconstitution Feeds

CSS-FD1402 The CSS-FD system must manage the configuration of each reconstitution feed.

CSS-FD1406 The CSS-FD system must create reconstitution feeds.

CSS-FD1416 The CSS-FD system must accept each request for reconstitution of current flight data.

CSS-FD1417 The CSS-FD system must accept each request for flight data pertaining to a specified time period not to exceed 45 days prior to the request.

CSS-FD1411 The CSS-FD system must permit each requester to cancel their subscription to the flight data reconstitution feed.

CSS-FD1263 The CSS-FD system must authenticate each consumer upon receipt of a reconstitution request.

CSS-FD1414 The CSS-FD system must permit each requester to specify the reconstitution feed be provided in the FIXM version between FIXM 3.0 through 4.3 with the respective approved NAS extension(s).

CSS-FD1420 The CSS-FD system must notify each requester upon successful initiation of their reconstitution request for flight information.

CSS-FD1422 The CSS-FD system must notify each requester when their reconstitution request for flight information has been terminated.

CSS-FD1424 The CSS-FD system must update each reconstitution feed when consumer permissions change.

CSS-FD1426 The CSS-FD system must notify each requester of changes to their active reconstitution feeds.

3.1.5.2 Generate Flight Information Reconstitution

CSS-FD2071-4 The CSS-FD system must enforce permissions for each reconstitution feed.

CSS-FD1432 The CSS-FD system must eliminate redundant data from each reconstitution flight information transaction.

CSS-FD1444 The CSS-FD system must send reconstitution flight information for each flight object that was updated in the order in which it was updated.

CSS-FD1446 The CSS-FD system must include the date and time in each reconstitution publication.

CSS-FD1448 The CSS-FD system must include system-generated metadata in each reconstitution publication.

3.1.5.3 Monitor Flight Information Reconstitution

CSS-FD1450 The CSS-FD system must detect any changes to each active reconstitution service feed.

CSS-FD1452 The CSS-FD system must maintain configuration data for the reconstitution service.

3.1.6 Flight Object Management

CSS-FD2036 The CSS-FD system must store an authoritative Flight Object for each received flight.

CSS-FD2139 The CSS-FD system must maintain an authoritative Flight Object for each flight.

CSS-FD2140 The CSS-FD system must store metadata for each authoritative Flight

Object.

CSS-FD2042 The CSS-FD system must retrieve each authoritative Flight Object from the data store.

CSS-FD2046 The CSS-FD system must update the flight information for each authoritative Flight Object in the data store.

CSS-FD2050 The CSS-FD system must prevent updates to each cancelled Flight

Object.

CSS-FD2052 When a user deletes a Flight Object, the CSS-FD system must archive and not permanently delete the Flight Object in the data store.

3.1.6.1 Flight Identifier Management

CSS-FD1290 The CSS-FD system must associate the previously received GUFI to matched flight data received without a GUFI.

CSS-FD1292 The CSS-FD system must associate the previously assigned Unique Flight

Identifier to matched flights received without a GUFI.

CSS-FD1004 The CSS-FD system must ensure each FF-ICE filed flight plan is assigned a valid GUFI.

CSS-FD2010 The CSS-FD system must generate a Unique Flight Identifier for each received flight plan without a GUFI.

CSS-FD2008 The CSS-FD system must generate a Unique Flight Identifier for a flight when the first flight information message received for that flight does not already contain a Unique Flight Identifier or a GUFI.

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

CSS-FD2002 The CSS-FD system must validate a GUFI complies with UUID V4 format.

CSS-FD2004 The CSS-FD system must store the GUFI in UUID V4 format.

CSS-FD1284 The CSS-FD system must provide verification errors for any flight plan submitted with a non-unique GUFI.

CSS-FD1288 The CSS-FD system must resolve Unique Flight Identifier-flight uniqueness verification errors.

CSS-FD2016 The CSS-FD system must maintain GUFI uniqueness for a minimum period of 10 years.

CSS-FD2520 The CSS-FD system must maintain UFI uniqueness for a minimum period of 10 years.

CSS-FD2018 The CSS-FD system must reject changes to a GUFI once the GUFI is associated with an authoritative Flight Object.

CSS-FD1278 The CSS-FD system must correlate received flight data to flights for which the system has previously received flight information.

CSS-FD1282-BR The CSS-FD system must apply business rules to confirm the uniqueness of each GUFI and flight combination.

CSS-FD1286-BR The CSS-FD system must apply relevant business rules to confirm the uniqueness of each Unique Flight Identifier and flight combination.

3.1.7 Identity and Access Management

CSS-FD1304 The CSS-FD system must authorize user access in accordance with the

FAA data access policy.

CSS-FD2040 The CSS-FD system must provide access to flight data to each authenticated and authorized user.

CSS-FD1304-1 The CSS-FD system must maintain read and write permissions for each field of the Flight Object.

3.1.8 Flight Planning

3.1.8.1 FF-ICE Flight Plans

CSS-FD1108 The CSS-FD system must implement FF-ICE Application 1.1.0 as defined in Attachment J-12, FIXM User Manual.

CSS-FD1110 The CSS-FD system must accept FF-ICE Flight Plan Update messages for FF-ICE Filed Flight Plans.

CSS-FD1114 The CSS-FD system must accept FF-ICE Flight Plan Cancellation messages for FF-ICE Filed Flight Plans.

CSS-FD1116 The CSS-FD system must accept FF-ICE Request Flight Plan Information messages for FF-ICE Filed Flight Plans.

3.1.8.2 Filed Flight Plan Validation

CSS-FD1120 The CSS-FD system must validate FF-ICE Filed Flight Plan messages.

Note: FF-ICE message definitions and validation requirements are in ICAO Procedures for Air Navigation Services — Air Traffic Management (PANS-ATM) (Doc. 4444) and Appendix A to WP XX Manual on FF- ICE Implementation Guidance.

CSS-FD1122 The CSS-FD system must validate FF-ICE Flight Plan Update messages for FF-ICE Filed Flight Plans.

CSS-FD1126 The CSS-FD system must validate FF-ICE Flight Plan Cancellation messages for FF-ICE Filed Flight Plans.

CSS-FD1128 The CSS-FD system must validate FF-ICE Request Flight Plan Information messages for FF-ICE Filed Flight Plans.

3.1.8.3 Filed Flight Plan Response Messages

CSS-FD2079 The CSS-FD system must send a Submission Response message to the submitter of an FF-ICE Filed Flight Plan.

CSS-FD2080 The CSS-FD system must send a Submission Response message to the submitter of an FF-ICE Flight Plan Update for an FF-ICE Filed Flight Plan.

CSS-FD2082 The CSS-FD system must send a Submission Response message to the submitter of an FF-ICE Flight Plan Cancellation request.

CSS-FD2084 The CSS-FD system must include error codes identified by the system in the FF-ICE Filing Status message.

CSS-FD2086 The CSS-FD system must include error codes identified by the system in the FF-ICE Submission Response message.

CSS-FD1162 The CSS-FD system must send an FF-ICE Filing Status message to the submitter of an FF-ICE Filed Flight Plan message.

CSS-FD1164 The CSS-FD system must send an FF-ICE Filing Status message to the submitter of an FF-ICE Flight Plan Update for an FF-ICE Filed Flight Plan.

CSS-FD1132 The CSS-FD system must provide a submission response of “ACK” to the submitter of an FF-ICE flight plan filing message when all validation checks are passed.

CSS-FD1134 The CSS-FD system must provide a submission response of “REJ” to the submitter of an FF-ICE flight plan filing message with the reason for the rejection when a validation check fails.

CSS-FD1170 The CSS-FD system must return a response of “NOT ACCEPTABLE” to the submitter when the flight plan or flight plan update is operationally inconsistent with ATM configuration and/or with restrictions applicable to the flight.

CSS-FD1136 The CSS-FD system must respond with a "REJ" to the submitter of an FF- ICE Filed Flight Plan message if it represents a change to an existing FF- ICE Filed Flight Plan after the lockout time, even if all validation checks are passed.

CSS-FD1138 The CSS-FD system must respond with a "REJ" to the submitter of an FF- ICE Flight Plan Update message if it represents a change to an existing FF-ICE Filed Flight Plan after the lockout time, even if all validation checks are passed.

CSS-FD1140 The CSS-FD system must respond with a "REJ" to the submitter of an FF- ICE Flight Plan Cancellation message if it represents a change to an existing FF-ICE Filed Flight Plan after the lockout time, even if all validation checks are passed.

CSS-FD1144 The CSS-FD system must respond with a "REJ" to the submitter of an FF- ICE Flight Plan Update message if an FF-ICE Flight Plan Update message has a version number that exceeds the current version by more than one.

CSS-FD1168 The CSS-FD system must send a Filing Status labeled "ACCEPTABLE" to the submitter when the CSS-FD-generated FPL (based on the FF-ICE Filed Flight Plan) is accepted by ATC automation.

CSS-FD1168-1 The CSS-FD system must send a Filing Status labeled "ACCEPTABLE" to the submitter when the CSS-FD-generated FPL (based on the FF-ICE Updated Flight Plan) is accepted by ATC automation.

CSS-FD2149 Upon receiving a cancellation acknowledgement from ATC automation, the CSS-FD system must set the status to "Cancelled" for the authoritative Flight Object.

3.1.8.4 Update Flight Filing Feedback

CSS-FD1190 The CSS-FD system must determine the updated filing status for each re-evaluated filed flight plan.

CSS-FD1198 The CSS-FD system must determine the appropriate change in a filing status for a flight identified by a GUFI.

CSS-FD1210 The CSS-FD system must determine the updated filing status for ATC-amended filed flight plans .

CSS-FD1192 The CSS-FD system must send an updated filing status, inclusive of any errors, to the submitter whenever the Filing Status for a filed flight plan changes.

CSS-FD1211 The CSS-FD system must send the updated filing status to the flight plan submitter when an ATC amendment alters the filed flight plan.

CSS-FD2148 Upon validation of an FF-ICE Flight Plan Cancellation message, the CSS- FD system must set the status to "Cancellation Requested" for the authoritative Flight Object.

3.1.8.5 Filed Flight Plan Dissemination

CSS-FD1225 The CSS-FD system must provide FF-ICE functionality in accordance with the CSS-FD Interface Requirements Document (IRD) (TBS).

CSS-FD2088 The CSS-FD system must send ATS formatted messages via

NADIN/NMR.

CSS-FD1220 The CSS-FD system must send flight plan information to ATC facilities in accordance with Appendix B of the Interface Control Document En Route Automation Modernization (ERAM)/National Airspace Data Interchange Network (NADIN) (Service-B Users). (NEED J Attachment)

CSS-FD1217-BR The CSS-FD system must apply relevant business rules to identify the ATC facility(ies) to send flight filing information.

3.1.8.6 Reserved

3.1.8.7 Trial Request Processing

CSS-FD1112 The CSS-FD system must accept FF-ICE Trial Request messages, as defined in J-12, FIXM User Manual.

CSS-FD1124 The CSS-FD system must validate FF-ICE Trial Request messages.

CSS-FD1166 The CSS-FD system must send a Trial Response to the submitter of an

FF-ICE Trial Request.

3.1.8.8 Feedback by Reference

The functionality associated with Capability 3 is only applicable to flight plans submitted by an eAU.

Table 2: Constraints for Feedback by Reference

Category Constraint Airspace Constraints • Special Activity Airspace (SAA), Special Use Airspace (SUA), ATC Assigned Airspace (ATCA)

• Closed/Impacted Routes

• Prohibited Areas

• Altitude Reservation (ALTRV)

Traffic Management Constraints

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

• Airspace Flow Program (AFP)

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

• Ground Delay Program (GDP)

• Ground Stop (GS)

• Stop Restrictions

• Collaborative Trajectory Option Program (CTOP)

• Metering Restrictions

• Departure Spacing Program

• REROUTE (TFM Advisory Required)

Resources Constraints Due to Weather

• Deicing

Runway Constraints • Closed Runway

• Runway Configuration at Departure/Destination

Category Constraint NAS Resources Constraints

• Communication Constraints

• Navigation Aid (NAVAID) Status

• Radar

• Closed Taxiway

• Instrument Landing System (ILS)

• Ground Positioning System (GPS) status

• Outages

• Airport Closure

Others • Applicable Notice to Air Mission(s) (NOTAMs)

CSS-FD1152 The CSS-FD system must determine Constraints presented in Table 2, for the following:

a. FF-ICE Filed Flight Plans

b. FF-ICE Trial Requests

c. FF-ICE Flight Plan Updates

d. ATC-Amended Flight Plan

CSS-FD2063 The CSS-FD system must update the authoritative Flight Object with Constraints.

CSS-FD1175 The CSS-FD system must identify any new Constraints or changes to Constraints for the following:

a. FF-ICE Filed Flight Plans

b. FF-ICE Trial Requests

c. FF-ICE Flight Plan Updates

d. ATC-Amended Flight Plan

CSS-FD1172 The CSS-FD system must include references to all identified applicable Constraints in FF-ICE Filing Status messages.

CSS-FD2061-BR The CSS-FD system must apply relevant business rules to correlate Constraints associated with an FF-ICE Flight Plan.

CSS-FD1174-BR The CSS-FD system must apply relevant business rules to examine changes in incoming Constraint data against previous data to identify any effects on applicable flights.

3.1.8.9 Return ATC Preferences

The functionality associated with Capability 4 is only applicable to eAU-submitted flight plans.

CSS-FD1158-BR The CSS-FD system must apply relevant business rules to identify ATC

Constraints for Flight Plan filing and updates.

CSS-FD1149-BR The CSS-FD system must accept applied Required Trajectory Elements for a filed flight plan from ATC Automation.

CSS-FD1151-BR The CSS-FD system must apply Required Trajectory Elements to the appropriate FF-ICE Filed Flight Plan.

CSS-FD1155-BR The CSS-FD system must accept applied Required Trajectory Elements for a flight plan update from ATC Automation.

CSS-FD1153-BR The CSS-FD system must apply Required Trajectory Elements to the appropriate FF-ICE Flight Plan Update.

CSS-FD1182-BR The CSS-FD system must re-evaluate affected FF-ICE Filed Flight Plans when a required route element has changed.

3.2 BUSINESS RULES MANAGEMENT SYSTEM

A Business Rules Management System (BRMS) is a comprehensive framework encompassing three interconnected yet discrete components, each fulfilling distinct roles:

Development Environment: Within this integral BRMS aspect, a sophisticated platform enables crafting and methodical definition of intricate business rules, creating a structured approach to formulation.

Repository: The repository centrally stores and manages intricate business rules, serving as an organized hub for cataloging, safe maintenance, and secure accessibility.

Business Rules Engine: The core of the BRMS houses a dynamic business rules engine that executes designed rules, acting as the powerhouse to translate abstracted rules into tangible actions, harmonizing business logic and real-world processes.

The CSS-FD BRMS will automate, manage and apply FAA business rules on flight data processing (e.g., flight plan acceptance, flight plan updates, ATC constraints, trial requests, etc.)

within CSS-FD. It enables the definition, management, and execution of business rules and logic without requiring manual coding changes in the applications. The engine operates based on a set of predefined rules and conditions, allowing for dynamic adjustments and optimizations to business processes.

CSS-FD1111-1 The CSS-FD system must be able to define, store, and manage business rules with specific permissions.

CSS-FD1111-2 The CSS-FD system must provide an interface for system support personnel to create, read, update, and delete (CRUD) business rules.

CSS-FD1111-3 The CSS-FD system must allow system support personnel to assign and modify permissions associated with each business rule.

CSS-FD1111-4 The CSS-FD system must allow system support personnel to disable or delete business rules, with the effect being immediate on the operations and transactions.

CSS-FD1111-5 The CSS-FD system must maintain an activity history of all changes made to business rules, including creation, updates, and deletion.

CSS-FD1111-6 The CSS-FD system must provide a mechanism to handle exceptions and errors when a business rule fails to execute or when an operation or transaction violates a business rule.

CSS-FD1111-7 The CSS-FD system must provide notifications to system support personnel on any errors encountered during the execution of business rules.

CSS-FD1111-8 The CSS-FD system must allow the import and export of business rules for backup or transfer purposes.

CSS-FD1115-BR The CSS-FD system must apply relevant business rules to each FF-ICE filed flight plan message.

CSS-FD2020-BR The CSS-FD system must apply relevant business rules to correlate a GUFI to each flight data element.

CSS-FD2022-BR The CSS-FD system must apply relevant business rules to correlate a GUFI to each flight data element from the authoritative Flight Object.

CSS-FD2038-BR The CSS-FD system must apply relevant business rules to populate each field in the authoritative Flight Object.

CSS-FD2048-BR The CSS-FD system must apply relevant business rules to update each applicable field in the authoritative Flight Object.

CSS-FD2054-BR The CSS-FD system must apply relevant business rules to delete each applicable authoritative Flight Object.

CSS-FD2064-BR The CSS-FD system must apply relevant business rules to correlate flight information.

CSS-FD2068-BR The CSS-FD system must apply relevant business rules to reconcile flight information.

CSS-FD2072-BR The CSS-FD system must apply relevant business rules to reconstitute flight information.

CSS-FD2136-BR The CSS-FD system must apply relevant business rules to store flight information.

CSS-FD2302-BR The CSS-FD system must apply relevant business rules for flight plan filing.

CSS-FD2306-BR The CSS-FD system must apply relevant business rules for flight information requests.

CSS-FD2308-BR The CSS-FD system must apply relevant business rules for flight data sharing.

CSS-FD2310-BR The CSS-FD system must apply relevant business rules for flight data reconstitution.

CSS-FD2312-BR The CSS-FD system must apply relevant business rules for constraint identification.

CSS-FD2314-BR The CSS-FD system must apply relevant business rules for constraint notification.

CSS-FD2304-BR The CSS-FD system must apply relevant business rules for trial requests.

3.3 PUBLICATION AND REPLY SERVICES

Publication and Reply services make flight data available to systems that perform operational and analytical functions throughout the entire lifecycle of a flight (i.e., from pre-departure to arrival). Flight data will be made available in FIXM and non-FIXM formats in accordance with data access policies established by the FAA and criteria specified by the CSS-FD consumer.

CSS-FD1342 The CSS-FD system must publish flight information in FIXM 4.3 format.

CSS-FD1343 The CSS-FD system must publish flight information in into the user-selected, FIXM versions between FIXM 3.0 through 4.3.

CSS-FD1270 The CSS-FD system must provide a message to consumers of flight data source connections status changes.

CSS-FD1328 The CSS-FD system must publish flight information to SWIM.

CSS-FD1346 The CSS-FD system must send flight information in the order in which it was updated by the source.

CSS-FD1418 The CSS-FD system must determine the set of requested flight data authorized to be provided based on the requester’s data access rights.

CSS-FD1260 The CSS-FD system must publish only valid flight information.

CSS-FD1348 The CSS-FD system must include the date and time in each published message.

CSS-FD1359 The CSS-FD system must support message filtering through the use of

Java Message Service (JMS) properties.

CSS-FDS011 The CSS-FD system must send status change notification messages to users of the flight data sharing services.

CSS-FDS021 The CSS-FD system must send status change notification messages to users of the flight plan filing service.

3.4 DATA STORAGE

The data storage requirements define the capability to retain and access Flight Object data and all flight information associated with CSS-FD.

CSS-FD2134 The CSS-FD system must retain data for each Flight Object for a minimum of 48 hours from its initial submission.

CSS-FD1148 The CSS-FD system must store validated FF-ICE Filed Flight Plans.

CSS-FD2100 The CSS-FD system must store data in accordance with FAA Order

1375.1F, Data and Information Management Policy.

CSS-FD2120 The CSS-FD system must store metadata elements that are unique to the system.

CSS-FD2122 The CSS-FD system must provide system-unique metadata elements when requested by an authorized user.

CSS-FD2124 The CSS-FD system must store system-derived data.

CSS-FD2130 The CSS-FD system must store metadata received from authorized external systems.

CSS-FD2142 The CSS-FD system must store data contained within an FF-ICE Filed

Flight Plan submission.

CSS-FD2144 The CSS-FD system must store data contained within an FF-ICE Filing

Status message.

CSS-FD2146 The CSS-FD system must store data contained within an FF-ICE Flight

Plan Update message.

3.4.1 Archival

CSS-FD2150 The CSS-FD system must…