Attachment 1-CSS-FD Initial Program Requirements Document.docx

Initial Program Requirements for CSS-FD

V0.5 (RFI) – 2/1/2021

Initial Program Requirements for Common Support Services – Flight Data

(CSS-FD)

Tailored for Request for Information

Version 0.5

February 1, 2020

Federal Aviation Administration 800 Independence Avenue SW Washington, DC 20591

THIS PAGE INTENTIONALLY LEFT BLANK

Table of Contents

Index of Figures Figure 1: CSS-FD Operational Concept Overview 8

Index of Tables

Initial Program Requirements for CSS-FD

V0.5 (RFI) – 2/1/2021

v

Introduction This document presents the Initial Program Requirements for the Federal Aviation Administration (FAA) Common Support Services – Flight Data (CSS-FD) program. These requirements identify essential capabilities, performance measures, and user interactions for the CSS-FD program capabilities. These requirements are written from the point of view of the end user and do not refer to any specific technologies or commit to a specific design.

Capability Description and Program Information Operational Concept CSS-FD includes eight capabilities divided into two investment packages. Capabilities are broken down in this way so that the foundational elements are implemented first in Package A.

Package A Capabilities Package A capabilities include:

Capability 1: Data Management and Security Framework Capability 2: Flight Plan Filing Capability 3: Evaluation of Constraints/Restrictions Capability 4: Flight Specific Feedback These capabilities are described in more detail in the following subsections.

Capability 1: Data Management and Security Framework The Data Management and Security Framework is the 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. One part of the Data Management and Security Framework capability is Globally Unique Flight Identifier (GUFI) management. A GUFI is 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, the system will create one for the Airspace User (AU) and enhanced airspace user (eAU)[footnoteRef:1] and return one to the Enhanced Airspace User (eAU). The system will generate, store, correlate, and validate GUFIs for each flight plan to support a consistent view of each flight. [1: 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.]

In addition to GUFI validation, validation rules will be applied to the received flight plan message to determine if flight data is acceptable for processing based on syntax, semantics, and data values. Additionally, there will be resiliency and reconstitution of flight data built into the system, so that NAS and non-NAS systems can efficiently obtain flight data upon start-up or system recovery. This includes the long-term storage of flight data for later analysis and recall for planning and investigation purposes.

Another large part of Data Management and Security Framework will be managing the identity and access privileges for interfacing systems and users. This will be done through managing data access rights to change current flight plan data, ensuring access rights to submit flight plans or access flight planning capabilities, validating access and change rights to data subscriptions and, lastly validating data access rights to change restrictions. Additionally, the Data Management and Security Framework will ensure data integrity, message authentication, and non-repudiation as required by FAA policy.

It is known that flight data will not always be provided from NAS users in a common format, so the CSS-FD Data Management and Security Framework will be able to convert the data into a CSS-FD usable format (e.g., International Civil Aviation Organization (ICAO) 2012 to FIXM). Conversely, the system will also be able to convert data to format extensions required by external systems (e.g., FIXM 4.1 to FIXM 3.0).

Not only can data be in different formats, but there can also be redundant or conflicting flight data from different systems. In these cases, CSS-FD will produce a single value for each flight data element using business rules to determine the authoritative source[footnoteRef:2] in each context. This eliminates the need for consumers to develop and maintain their own means to reconcile flight data, enables a consistent set of flight data values being provided to all consumers, and ensures all CSS-FD users share a single situational awareness derived from the most appropriate data source(s) for each circumstance. CSS-FD will receive flight data from various authoritative sources, aggregate the data, and then publish it to eAUs. Other than a Submission Response, which is acceptable for both AUs and eAUs, only eAUs will have the ability to receive the additional outbound messages from CSS-FD. Note that this figure is not meant to depict the actual interfacing systems; for example, Aeronautical Common Services (ACS) data will most likely be accessed through NAS Common Reference (NCR). [2: The authoritative source will vary depending on the data. CSS-FD is the aggregator of data from authoritative sources and may be the authoritative source for data which will be determined during system design.]

Capability 2: Flight Plan Filing The Flight Plan Filing capability will support the 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. CSS-FD will understand the flight plan in the legacy format (i.e., ICAO 2012) and in FF-ICE format (i.e., FIXM format).

While the Data Management and Security Framework capability will provide the ability to convert messages between formats, the Flight Plan Filing capability will enable those converted messages to be routed between CSS-FD and other systems through National Airspace Data Interchange Network (NADIN) Messaging Rehost (NMR) and other network connections. For all users, CSS-FD will send an outbound message with an acknowledgement confirming the inbound message was successfully received (i.e., submission response) and for eAUs a filing status will be sent with additional information. Furthermore, CSS-FD will have the ability to determine the ATC facility with which to file the received flight plan and the ability to forward said plan in the form needed based on the content included.

In addition to today’s filed flight plans, eAUs will be able to submit Trial Requests (TRs) to evaluate route/4-dimensional trajectory (4DT) options for the desired route or alternatives for an existing filed flight plan. These TRs will have no effect on the flight plan’s current content and an eAU may submit multiple TRs to evaluate multiple route alternatives without a filed flight plan. TRs can also be used by Traffic Managers (TMs) to evaluate alternatives or other route options when assigning a Pre-Departure Re-Route (PDRR) to a flight. CSS-FD will not retain the TR for future evaluation but the eAU may use the results from the TR to update their route.

Capability 3: Evaluation of Constraints/Restrictions Evaluation of Constraints/Restrictions is the ability to provide information on airspace constraints or other restrictions for flight plans in the filing status or for TRs. The constraints and restrictions in Package A will include but are not limited to information from Traffic Flow Management System (TFMS) and Aeronautical Common Service (ACS) through the NAS Common Registry (NCR) or other means.

Capability 4: Flight Specific Feedback The Flight Specific Feedback capability within CSS-FD will provide a flight with applicable Traffic Management Initiatives (TMIs), NAS automation-applied Air Traffic Control (ATC) Adapted Routes, and static airspace constraints described in Standard Operating Procedures (SOPs) / Letters of Agreement (LOAs), in order to increase the likelihood that the flight will be cleared as filed.

The feedback to the eAU, via trial response, is expected to provide an indication of the constraint, which may include reference to the published restriction. When applicable, the feedback will also provide an indication of its impact, including altitude and speed restrictions and location of the constraint along the route or 4DT. The feedback on the ATC changes will highlight changes in the cleared route from the TR route in a one-time response. For TRs, the eAU is then expected to assess the feedback and determine their course of action.

For flight plan updates, the Flight Specific Feedback capability will also provide feedback on the new trajectory on which the flight will be cleared, with indicators on the elements that have changes from the previously filed flight plan. This feedback will include an evaluation of ATC amended filed flight plans against applicable constraint information received and provide an evaluation of Traffic Flow Management (TFM) and ATC constraints in a one-time response.

High Level Concept Graphic The CSS-FD operational concept is illustrated in the program-level Operational View (OV-1) presented in Figure 1.

The figure shows the integration of CSS-FD capabilities with existing air traffic services, systems, and displays, coupled with the underlying infrastructure supported by System Wide Information Management (SWIM) and Federal Cloud Services (FCS).

Figure 1: CSS-FD Operational Concept Overview

Functional, Information, and Performance Requirements Each requirement (“must” statement) in this document is provided a permanent identifying tag in the form of “PRD####” where the #### indicates a 4-digit value that is unique to the requirement and is 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 ID numbers and the ordering of the ID numbers does not have any implications as to the importance or precedence of a requirement.

Functional Requirements Capability 1: Data Management and Security Framework General Functional Requirements The CSS-FD system must [PRD1002] provide an enterprise service which can be used by multiple systems within the NAS.

The CSS-FD system must [PRD1006] operate in a mixed mode (legacy user and enhanced user) environment.

General Flight Data Sharing Requirements The CSS-FD system must [PRD1256] validate data acquired from external sources in accordance with each source’s respective interface documentation.

The CSS-FD system must [PRD1258] notify sources of invalid data received when such communication is supported by the data source.

The CSS-FD system must [PRD1260] publish only flight data that is valid with respect to its source’s respective interface documentation.

The CSS-FD system must [PRD1262] authenticate consumers upon receipt of subscription or reconstitution requests and prior to data publication.

The CSS-FD system must [PRD1264] store data required for:

System operations System maintenance and support System analysis recording.

Format Flight Data The CSS-FD system must [PRD1342] format subscribed flight data publications into the current FIXM format version in support of consumer transitions to FF-ICE/1 compliance.

The CSS-FD system must [PRD1343] format subscribed flight data publications into the pre-specified, older FIXM format versions in support of consumer transitions to FF-ICE/1 compliance.

Publish Flight Data The CSS-FD system must [PRD1344] send publication flight data to consumers in accordance with the connectivity information established when the request was approved.

The CSS-FD system must [PRD1346] send flight data for flights in the order in which it was updated by flight data source.

The CSS-FD system must [PRD1348] publish the date and time of each publication.

The CSS-FD system must [PRD1350] publish system generated metadata in addition to flight data to aid consumers in the identification of missing flight data transactions.

The CSS-FD system must [PRD2034] support flight-specific identification, intent, capabilities, or status information consumed outside of FF-ICE planning exchanges.

GUFI Management The CSS-FD system must [PRD1280] provide a function to manage the Globally Unique Flight Identifier (GUFI).

The CSS-FD system must [PRD1004] ensure each flight has a valid GUFI or LUFI.

The CSS-FD system must [PRD2002] validate a GUFI is Universally Unique Identifier (UUID) V4 format.

The CSS-FD system must [PRD2004] store the GUFI in Universally Unique Identifier (UUID) V4 format.

The CSS-FD system must [PRD2006] generate a GUFI upon request.

The CSS-FD system must [PRD2008] generate a GUFI when a flight information message is received that does not contain a GUFI.

The CSS-FD system must [PRD1206] determine the flight’s GUFI from received filed flight plans when automation does not provide a GUFI.

The CSS-FD system must [PRD2010] provide a GUFI when GUFI is not provided upon receipt of flight plan.

The CSS-FD system must [PRD2012] reject a message if the GUFI is associated with flight data marked as Cancelled in the persistent flight data structure.

The CSS-FD system must [PRD2014] reject a message with a GUFI already associated with another flight data element from the persistent flight data structure.

The CSS-FD system must [PRD2016] ensure uniqueness of a GUFI for at least ten years.

The CSS-FD system must [PRD2018] reject changes to a GUFI once associated with a flight data element from the persistent flight data structure.

The CSS-FD system must [PRD2020] evaluate business rules to determine operations for correlating GUFI to a flight data element.

The CSS-FD system must [PRD2022] evaluate business rules to determine operations for validating GUFI to a flight data element from the persistent flight data structure.

The CSS-FD system must [PRD1282] verify that GUFI-flight combinations are unique.

The CSS-FD system must [PRD1284] provide GUFI-flight uniqueness verification errors.

The CSS-FD system must [PRD1286] verify that LUFI-flight combinations are unique.

The CSS-FD system must [PRD1288] remediate LUFI-flight uniqueness verification errors.

The CSS-FD system must [PRD1290] associate the previously received GUFI to matched flights received without a GUFI or LUFI, where applicable.

The CSS-FD system must [PRD1292] associate the previously assigned LUFI to matched flights received without a GUFI or LUFI, where applicable.

The CSS-FD system must [PRD1294] generate a LUFI for unmatched (new) flights that are received without a GUFI from upstream systems.

Flight Data Conversion The CSS-FD system must [PRD2024] convert flight information messages to Flight Information Exchange Model (FIXM) format.

The CSS-FD system must [PRD2026] convert messages in FIXM 3.0 format to FIXM 4.1 format.

The CSS-FD system must [PRD2028] convert messages in FIXM 4.0 format to FIXM 4.1 format.

The CSS-FD system must [PRD2030] convert Traffic Flow Management (TFM) Version 3.0 Expect Departure Clearance Time (EDCT) messages to FIXM 4.1 format.

The CSS-FD system must [PRD2032] translate ATS formatted messages to FIXM 4.1 format.

The CSS-FD system must [PRD1276] enhance flight data.

Disseminate Flight Plan Filing Information The CSS-FD system must [PRD1222] provide evaluated flight planning information (including evaluation results) to the TFM automation in the form needed with the appropriate content.

The CSS-FD system must [PRD1223] provide flight plan filing information to TFM automation in accordance with TBD IRD.

The CSS-FD system must [PRD1224] provide received and evaluated flight planning information, including evaluation results, to the Flight Data Publication service functions in the form needed with the appropriate content.

The CSS-FD system must [PRD1225] provide flight plan filing information for publication in accordance with TBD IRD.

The CSS-FD system must [PRD1266] acquire live flight data generated by external, FAA approved sources.

The CSS-FD system must [PRD1268] monitor the status of flight data source connections.

The CSS-FD system must [PRD1270] provide a notification to consumers of changes in the status of flight data source connections.

The CSS-FD system must [PRD1278] perform flight data matching to determine if flight data received from source producers pertains to flights for which the system has previously received flight data.

The CSS-FD system must [PRD1328] generate flight data for publication.

Produce Subscribed Flight Data The CSS-FD system must [PRD1330] produce subscribed flight data transactions based on the data that has been requested and the consumer’s data access rights.

The CSS-FD system must [PRD1332] produce flight data transactions whenever new source flight data is received that results in a change to previously published data.

The CSS-FD system must [PRD1334] eliminate redundant data from produced flight data transactions.

The CSS-FD system must [PRD1336] include the validated and matched GUFI and/or LUFI for each flight in its associated flight data transaction.

The CSS-FD system must [PRD1338] produce flight data transactions containing only reconciled values when inconsistent data elements are identified.

The CSS-FD system must [PRD1340] produce flight data transactions that retain context specific data (i.e., unique data).

SWIM Subscription Management The CSS-FD system must [PRD1302] manage subscriptions.

The CSS-FD system must [PRD2222] provide status information to SWIM Enterprise Service Monitoring (ESM) for each of its business services.

The CSS-FD system must [PRD1305] provide a function to communicate with FAA SWIM.

The CSS-FD system must [PRD1307] provide a function to publish Flight Object data to FAA SWIM.

The CSS-FD system must [PRD1309] provide a function to subscribe to flight information from FAA SWIM.

The CSS-FD system must [PRD1311] provide metadata headers for Flight Object publication in accordance with FAA SWIM content-based routing specifications.

Determine Subscriber Access Rights The CSS-FD system must [PRD1304] determine subscriber access rights in accordance with the FAA data access policy and the consumer’s on-ramping credentials.

Create and Maintain Subscription The CSS-FD system must [PRD1306] create subscriptions.

The CSS-FD system must [PRD1308] maintain subscriptions.

The CSS-FD system must [PRD1310] accept subscription requests for flight data from consumers.

The CSS-FD system must [PRD1312] accept requests to terminate subscriptions for flight data from consumers.

The CSS-FD system must [PRD1314] accept requests for subscription data filtering from consumers.

The CSS-FD system must [PRD1316] allow consumers to specify a request for flight data in a specific FIXM format version.

The CSS-FD system must [PRD1318] determine the set of requested flight data authorized to be published based on the consumer’s data access rights.

The CSS-FD system must [PRD1320] provide a notification to the consumer of the successful initiation of a subscription request for authorized flight data.

The CSS-FD system must [PRD1322] provide a notification to the consumer when the subscription request for flight data has been terminated.

The CSS-FD system must [PRD1324] update subscriptions when a change occurs in any of the following: a. a consumer’s data access rights b. the FAA data access policy.

The CSS-FD system must [PRD1326] provide a notification to the consumer of any changes to their active subscriptions.

SWIM Publication Management The CSS-FD system must [PRD1352] monitor and control its publication service.

The CSS-FD system must [PRD1354] maintain publication service configuration data to support the maintenance of data access rights and subscription descriptions.

The CSS-FD system must [PRD1356] maintain source configuration data to support the maintenance of publication and reconstitution services.

The CSS-FD system must [PRD1358] manage publication service operations.

The CSS-FD system must [PRD1360] monitor the system status and performance of its:

1. Hardware Software Network Interfaces (e.g., flight data sources) The CSS-FD system must [PRD1362] display the system status and performance of its:

1. Hardware Software Network Interfaces (e.g., flight data sources).

The CSS-FD system must [PRD1364] detect component failure events.

The CSS-FD system must [PRD1366] detect interface failure events.

The CSS-FD system must [PRD1368] detect service failure events.

The CSS-FD system must [PRD1370] provide alerts when a component failure event is detected.

The CSS-FD system must [PRD1372] provide alerts when an interface failure event is detected.

The CSS-FD system must [PRD1374] provide alerts when a service failure event is detected.

The CSS-FD system must [PRD1376] record (archive) failure events for post- operation analysis.

The CSS-FD system must [PRD1378] allow authorized operators to manage connections to external interfaces.

The CSS-FD system must [PRD1380] archive system data for a minimum of 45 days for system support and maintenance activities.

The CSS-FD system must [PRD1382] provide a tool for s authorized system support personnel to perform analysis and generate reports from archived data.

The CSS-FD system must [PRD1384] provide a tool for authorized system support personnel to manually log maintenance actions and system events.

The CSS-FD system must [PRD1386] allow authorized operators to display the system log.

The CSS-FD system must [PRD1388] allow authorized operators to specify the rate for publishing updates from each data source:

1. Automatically At a specified update rate.

The CSS-FD system must [PRD1390] allow authorized operators to manage the system and its components.

The CSS-FD system must [PRD1392] allow authorized operators to restart the system and its components.

The CSS-FD system must [PRD1394] allow authorized operators to update the system and its components.

The CSS-FD system must [PRD1396] allow authorized operators to switch the system and its components to a backup.

The CSS-FD system must [PRD1398] provide a tool for authorized system support personnel to access online diagnostics from system components (e.g., to monitor system health, certification).

The CSS-FD system must [PRD1400] allow authorized operators to display maintenance manuals.

Flight Data Management The CSS-FD system must [PRD2036] provide a data structure to store persistent flight data.

The CSS-FD system must [PRD2038] create persistent entries in the flight data structure according to appropriate business rules.

The CSS-FD system must [PRD2040] provide access to flight data to authorized users.

The CSS-FD system must [PRD2042] be capable of retrieving flight data entries from the persistent flight data structure.

The CSS-FD system must [PRD2044] evaluate business rules to determine data read operations for a entries in the flight data structure.

The CSS-FD system must [PRD2046] provide a function to update flight data within the flight data structure.

The CSS-FD system must [PRD2048] evaluate business rules to determine data update operations for entries in the flight data structure.

The CSS-FD system must [PRD2050] not allow updates to cancelled entries in the persistent flight data structure.

The CSS-FD system must [PRD2052] provide a function to designate flight data as deleted within the flight data structure.

The CSS-FD system must [PRD2054] evaluate business rules to determine data delete operations for flight data.

The CSS-FD system must [PRD2062] provide a function to correlate new flight information to the persistent flight data structure.

Flight Data Validation The CSS-FD system must [PRD2056] provide a function to validate messages.

The CSS-FD system must [PRD2058] validate messages based on schemas associated with the message received.

The CSS-FD system must [PRD2060] validate messages based on semantic business validation rules.

The CSS-FD system must [PRD2064] evaluate business rules to determine operations for correlating flight data.

Flight Data Reconciliation The CSS-FD system must [PRD2066] reconcile new flight information with the corresponding entries in the persistent flight data structure.

The CSS-FD system must [PRD2068] evaluate business rules to determine operations for reconciling flight data.

The CSS-FD system must [PRD1296] reconcile flight data from multiple sources.

The CSS-FD system must [PRD2070] reconcile flight data containing conflicting input data for a specific flight data element.

The CSS-FD system must [PRD1298] identify inconsistent flight data elements (i.e., contains different values for the same data element that are logically or physically inconsistent).

The CSS-FD system must [PRD1300] reconcile values for inconsistent flight data elements using configured business rules.

Flight Data Reconstitution The CSS-FD system must [PRD2071] provide a function to reconstitute flight data entries from the persistent flight data structure.

The CSS-FD system must [PRD2072] evaluate business rules to determine operations for reconstituting flight data.

Flight Data Reconstitution Feeds The CSS-FD system must [PRD1402] manage reconstitution feeds.

The CSS-FD system must [PRD1404] determine requester access rights in accordance with the FAA data access policy and the requester’s on-ramping credentials.

The CSS-FD system must [PRD1406] create reconstitution feeds.

The CSS-FD system must [PRD1408] maintain reconstitution feeds.

The CSS-FD system must [PRD1410] accept reconstitution requests for flight data from requesters.

The CSS-FD system must [PRD1412] accept requests for reconstitution data filtering from requesters.

The CSS-FD system must [PRD1414] allow requesters to specify a request for reconstituted flight data in a specific FIXM format version.

The CSS-FD system must [PRD1416] accept reconstitution requests to restore the current state of flight data or to republish flight data from a specified time period.

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

The CSS-FD system must [PRD1420] provide a notification to the requester of the successful initiation of an authorized reconstitution request for flight data.

The CSS-FD system must [PRD1422] provide a notification to the requester when the reconstitution request for flight data has been terminated.

The CSS-FD system must [PRD1424] update reconstitution feeds when a change occurs in any of the following: a. a requester’s data access rights b. the FAA data access policy.

The CSS-FD system must [PRD1426] provide a notification to the requester of any changes to their active reconstitution feeds.

Generate Flight Data Reconstitution The CSS-FD system must [PRD1428] generate reconstitution flight data.

The CSS-FD system must [PRD1430] produce reconstitution flight data transactions based on the data that has been requested and the requester’s data access rights.

The CSS-FD system must [PRD1432] eliminate redundant data from produced reconstitution flight data transactions.

The CSS-FD system must [PRD1434] include the validated and matched GUFI and/or LUFI for each flight in its associated reconstitution flight data transaction.

The CSS-FD system must [PRD1436] produce reconstitution flight data transactions containing only reconciled values when inconsistent data elements are identified.

The CSS-FD system must [PRD1438] produce reconstitution flight data transactions that retain context specific data (i.e., unique data).

The CSS-FD system must [PRD1440] format reconstitution flight data publications into the current FIXM format version and in pre- specified, older FIXM format versions in support of consumer transitions to FF-ICE/1 compliance.

The CSS-FD system must [PRD1442] send reconstitution flight data to the requester in accordance with the connectivity information established when the request was approved.

The CSS-FD system must [PRD1444] send reconstitution flight data for a flight in the order in which it was updated by the flight data source.

The CSS-FD system must [PRD1446] publish the date and time of each reconstitution publication.

The CSS-FD system must [PRD1448] publish system generated metadata in addition to reconstitution flight data to aid requesters in the identification of missing flight data transactions.

Monitor Flight Data Reconstitution The CSS-FD system must [PRD1450] monitor and control its reconstitution service.

The CSS-FD system must [PRD1452] maintain reconstitution service configuration data to support the maintenance of data access rights and reconstitution descriptions.

The CSS-FD system must [PRD1453] maintain reconstitution service operations.

Capability 2: Flight Plan Filing The CSS-FD system must [PRD1101] accept and check each flight planning related message.

Note: For messages that do not pass these validation checks, the issues are reported to the submitter. Messages passing these checks are sent to the appropriate functions for further processing.

The CSS-FD system must [PRD1108] accept FF-ICE Filed Flight Plan messages.

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

The CSS-FD system must [PRD1112] accept FF-ICE Trial Request messages for Filed Flight Plans.

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

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

The CSS-FD system must [PRD1117] subscribe to SFDPS for messages related to FF-ICE filed flight plan and act on those messages based on business rules.

Filed Flight Plan Validation The CSS-FD system must [PRD1120] validate FF-ICE Filed Flight Plan messages.

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

The CSS-FD system must [PRD1124] validate FF-ICE Trial Request messages for Filed Flight Plans.

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

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

The CSS-FD system must [PRD1129] receive validated Request Flight Plan Information messages for flights with Filed Flight Plans and will provide the requested information.

The CSS-FD system must [PRD1148] store validated FF-ICE Filed Flight Plans.

Filed Flight Plan Response Messages The CSS-FD system must [PRD2080] send a Submission Response message to the submitter of a Flight Plan Update for a Filed Flight Plan.

The CSS-FD system must [PRD2082] send a Submission Response message to a submitter of a Flight Plan Cancellation request.

The CSS-FD system must [PRD2084] include in the Filing Status message error codes identified by the system.

The CSS-FD system must [PRD2086] include in the Submission Response message error codes identified by the system.

The CSS-FD system must [PRD1162] send a Filing Status message to the submitter of a Filed Flight Plan message.

The CSS-FD system must [PRD1164] send a Filing Status message to the submitter of a Flight Plan Update for a Filed Flight Plan.

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

The CSS-FD system must [PRD1134] provide a 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.

The CSS-FD system must [PRD1136] provide a response of MAN to the submitter of an FF-ICE Filed Flight Plan message when validation checks were passed, but the message represents a change to an existing FF-ICE Filed Flight Plan and it is past the lockout time for the flight.

The CSS-FD system must [PRD1138] provide a response of MAN to the submitter of an FF-ICE Flight Plan Update message when validation checks were passed, but the message represents a change to an existing FF-ICE Filed Flight Plan and it is past the lockout time for the flight.

The CSS-FD system must [PRD1140] provide a response of MAN to the submitter of an FF-ICE Flight Plan Cancellation message when validation checks were passed, but the message represents a change to an existing FF-ICE Filed Flight Plan and it is past the lockout time for the flight.

The CSS-FD system must [PRD1144] send a Request Flight Plan Information to the submitter to request a full FF-ICE Filed Flight Plan to resynchronize the versions when an FF-ICE Flight Plan Update message has a version number that is more than one higher than the current version.

The CSS-FD system must [PRD1168] send a Filing Status of ACCEPTABLE to the submitter when the trajectory for a Filed Flight Plan reflects the trajectory that the ATC Service Provider anticipates the flight will fly.

Note: this applies to both a submitted Filed Flight Plan and the update to that Filed Flight Plan resulting from an Update Plan message.

The CSS-FD system must [PRD1170] return a response of UNACCEPTABLE to the submitter when the flight operator needs to address an identified problem before the flight plan can be cleared.

Note: this applies to both a submitted Filed Flight Plan and the update to that Filed Flight Plan resulting from an Update Plan message.

Update Flight Filing Feedback The CSS-FD system must [PRD1166] send a Trial Response to the submitter of a valid Trial Request for a flight with a Filed Flight Plan.

Note: A flight plan need not be Filed for a Trial to be submitted.

The CSS-FD system must [PRD1190] determine the updated Filing Status for each re-evaluated Filed Flight Plan.

Note: Feedback is provided only when there is a change from the original Filing Status.

The CSS-FD system must [PRD1192] send an updated Filing Status, including any errors, to the submitter when the Filing Status changes for a Filed Flight Plan.

The CSS-FD system must [PRD1188] keep track of constraints applicable to a Filed Flight Plan.

The CSS-FD system must [PRD1198] determine the appropriate change in a flight status for a flight identified by a GUFI, given events such as Flight Cancellation of a Filed Flight Plan or departure of a flight with a Filed Flight Plan.

The CSS-FD system must [PRD1196] update the filed flight plan status for a GUFI.

The CSS-FD system must [PRD1199] determine changes in the status of a flight identified by a GUFI when updated information about a flight with that GUFI is received, including flight cancellation or departure of the flight.

The CSS-FD system must [PRD1212] determine the updated Filing Status for the evaluated ATC-amended Filed Flight Plans. Feedback includes the new trajectory on which the flight will be cleared, with indicators on the elements that have changed from the previous flight plan.

The CSS-FD system must [PRD1208] determine the filing status for amended Filed Flight Plans.

The CSS-FD system must [PRD1210] determine the updated Filing Status for ATC-amended Filed Flight Plans.

The CSS-FD system must [PRD1211] provide an updated Filing Status to the submitter of the Filed Flight Plan when an ATC amendment changes the Filed Flight Plan.

The CSS-FD system must [PRD1216] determine the ATC facility with which to file the received flight plan and will provide flight filing information to that facility's ATC automation in the form needed with the appropriate content.

Note: The Filing Status includes the new route/trajectory to which the flight will be cleared, with indicators on the elements that have changed from the previous flight plan.

Filed Flight Plan Dissemination The CSS-FD system must [PRD1214] provide flight filing information to ATC.

The CSS-FD system must [PRD1217] determine the ATC facility or facilities to which flight filing information is to be sent.

The CSS-FD system must [PRD1218] allow modification of which ATC facility/facilities will receive a filed flight plan.

The CSS-FD system must [PRD1220] provide flight plan filing information to the ATC automation system at the determined ATC facility in accordance with TBD IRD.

The CSS-FD system must [PRD1131] receive validated Request Flight Plan Information messages for flights with Filed Flight Plans and will provide the requested information.

The CSS-FD system must [PRD1231] respond to the submitter with an error message when the system cannot provide the requested information.

The CSS-FD system must [PRD1226] respond to flight plan information requests for Filed Flight Plans.

The CSS-FD system must [PRD1228] provide the requested information to the submitter of a Flight Plan Information request.

Note: CSS-FD will determine the ATC facility with which to file the legacy flight plan received (in a non-FF-ICE/1-compliant format), then send the flight plan to the appropriate ATC automation system, in the format needed by that system. When the receiving system is able to ingest FF-ICE/1-compliant messages, that format conversion may need to include applying an appropriate LUFI, building a 4DT (Package B), and evaluating the 4DT. CSS-FD will also provide the legacy flight plan (as submitted) to the publication service (NMR).

The CSS-FD system must [PRD2518] provide flight filing information to ERAM.

The CSS-FD system must [PRD1519] provide flight plan filing information, including evaluation results, for publication in accordance with TBD IRD.

The CSS-FD system must [PRD2088] send FF-ICE FPL Messages in ATS format to ERAM via NMR.

The CSS-FD system must [PRD2090] send FF-ICE FPL Update Messages in ATS format to ERAM via NMR.

The CSS-FD system must [PRD2092] send FF-ICE Cancellation Messages in ATS format to NMR.

The CSS-FD system must [PRD2094] receive NMR messages in ATS format.

The CSS-FD system must [PRD2096] translate FIXM 4.1 format to ATS format all fields that contain equivalent data.

Legacy Flight Plans The CSS-FD system must [PRD1242] publish legacy flight plans to ATC automation.

The CSS-FD system must [PRD1244] determine the ATC facility with which to file received legacy flight plans.

The CSS-FD system must [PRD1246] provide legacy flight plans to the ATC automation at the determined ATC facility in accordance with TBD IRD.

The CSS-FD system must [PRD1248] provide legacy flight plans for publication in accordance with TBD IRD.

The CSS-FD system must [PRD1250] publish legacy ATC filing responses to NAS users.

Note: CSS-FD will receive the response from ATC automation when a legacy flight plan is filed and forward the response to the appropriate NAS user. When no response is received within the expected time, CSS-FD notifies the filer that the facility was unavailable and the flight plan filing was not completed.

The CSS-FD system must [PRD1252] forward the response to the appropriate NAS user when the system receives a response for a legacy filed flight plan from ATC automation.

The CSS-FD system must [PRD1254] notify the filer that the facility was unavailable and the flight plan filing was not completed when the flight plan could not be successfully transmitted to the relevant ATC automation.

Capability 3: Evaluation of Constraints/Restrictions The CSS-FD system must [PRD1156] determine constraints for filing requests.

The CSS-FD system must [PRD1152] determine constraints applicable to a flight based on the information contained in a Filed Flight Plan.

The CSS-FD system must [PRD1158] identify known ATC constraints that affect the flight’s Filed Flight Plan.

The CSS-FD system must [PRD1159] identify known TFM constraints that affect the flight’s Filed Flight Plan.

The CSS-FD system must [PRD1184] determine updated constraints applicable to a flight based on information contained in a Filed Flight Plan, when the status of a constraint changes.

The CSS-FD system must [PRD1200] evaluate ATC-amended Filed Flight Plans against applicable constraints.

Note: Much of this function is expected to use the same processes as in Flight Filing Request Evaluation. This function may have to suppress adding any required route elements, since the received amendment may be intended to override those normally applied by the ATC automation. When the ATC automation does not provide the flight's GUFI, this function may also need to determine the flight's GUFI. This function also retrieves other flight plan data for completing the response update to the appropriate NAS user.

The CSS-FD system must [PRD1202] update constraints based on information provided in a Filed Flight Plan when the plan is amended.

The CSS-FD system must [PRD1154] determine when there is an error in applying updated constraints to the Filed Flight Plan.

The CSS-FD system must [PRD1172] include in the Filing Status message each applicable constraint identified by the system, including the location where the flight will encounter the constraint.

The CSS-FD system must [PRD1204] assess the flight’s 4DT against current constraints for a Filed Flight Plan (see Table 2).

Table 2: Constraints that can affect a flight’s 4DT

Airspace Constraints

Active Special Use Airspace (SUA)/ATC Assigned Airspace (ATCAA) (includes scheduled to be active when flight will be in airspace) Prohibited Area Closed route

Ground Delay Program (GDP) Airspace Flow Program (AFP) TFM assigned route (Route Advisory— Required) TFM assigned route and departure time (Collaborative Trajectory Options Program[CTOP])

TFM Advisory: Route Advisory— Recommended TFM Advisory: Route Advisory—Planned TFM Advisory: Route Advisory—For Your Information (FYI) TMIs Ground Stop (GS) Miles-in-Trail (MIT) or Minutes-in-Trail (MINIT) Restrictions Fix Constraints Metering Restrictions Congestion in Oceanic Airspace

Air Traffic Constraints

Altitude or speed crossing restriction from ATC SOP/LOA

NAS Resource Constraints

Radar Closed Runway Closed Taxiway Instrument Landing System (ILS) Global Positioning System (GPS)

Resource Constraints due to Meteorological Conditions – applied near time of departure

Runway Visual Range (RVR) Deicing operations Standard Instrument Departure (SID)/Standard Terminal Arrival Route (STAR) status

Capability 4: Flight Specific Feedback The CSS-FD system must [PRD1150] apply required trajectory elements to the Filed Flight Plan, accounting for aircraft performance characteristics, required equipage for Performance Based Navigation (PBN) routes, and required route elements from TFM and ATC.

The CSS-FD system must [PRD1151] apply required trajectory elements to filing requests.

Data and Information Requirements The CSS-FD system must [PRD2100] be in accordance with FAA order 1375.1, Data Management.

Data Storage Foundational Data Storage Requirements The CSS-FD system must [PRD2102] record operational system information.

The CSS-FD system must [PRD2104] log system activity data.

The CSS-FD system must [PRD2106] log all flight plan queries.

The CSS-FD system must [PRD2108] log flight plan subscription activity.

The CSS-FD system must [PRD2110] log all error messages.

The CSS-FD system must [PRD2112] log all flight plan storage activities (create, update, delete).

The CSS-FD system must [PRD2114] log all transactions for flight plan business processes/workflow.

The CSS-FD system must [PRD2116] record auditing information on database maintenance functions taken.

The CSS-FD system must [PRD2118] store system data in accordance with FAA JO 7210.3, Facility Operation and Administration.

The CSS-FD system must [PRD2120] store system-unique metadata elements.

The CSS-FD system must [PRD2122] provide system-unique metadata elements.

The CSS-FD system must [PRD2124] store system-derived data.

The CSS-FD system must [PRD2126] uniquely identify Aeronautical Information (AI) using the Universally Unique Identifier (UUID).

The UUID must [PRD2128] be used to track the AI throughout the entire lifecycle of the AI.

The CSS-FD system must [PRD2130] receive metadata from authorized external systems.

The CSS-FD system must [PRD2132] not replicate authoritative source data except where required to meet operational demand.

The CSS-FD system must [PRD2134] persist flight object data for a TBD designated period.

The CSS-FD system must [PRD2136] evaluate business rules to determine operations for storing Flight Object data.

The CSS-FD system must [PRD2138] reject information deemed to be incomplete, potentially erroneous, or inaccurate based on provided business rules.

The CSS-FD system must [PRD2140] store metadata associated with a Flight Object.

Flight Plan Filing Data Storage Requirements The CSS-FD system must [PRD2142] store data contained within an FF-ICE FFPL Submission.

The CSS-FD system must [PRD2144] store data contained within an FF-ICE Filing Status message.

The CSS-FD system must [PRD2146] store data contained within an FF-ICE FFPL Update message.

The CSS-FD system must [PRD2148] update the status of a flight entry in the persistent flight data structure to be “Cancelled” upon validation of an FF-ICE Flight Plan Cancellation message.

Archival The CSS-FD system must [PRD2150] archive log information for a minimum 3 years.

Audit The CSS-FD system must [PRD2152] perform logging of system logs in accordance with Appendix 4 (Audit and Accountability (AU)) of the FAA Order 1370.121, FAA Information Security and Privacy Program and Policy.

The CSS-FD system must [PRD2154] have security requirements that will stem from account management and parlay the SWIM requirements.

The CSS-FD system must [PRD2156] provide the capability to retrieve and sort archived log information by, at a minimum: time, date, UUID, and entry type.

The CSS-FD system must [PRD2158] provide a GUI for specified users to perform audits on all system activities.

The CSS-FD system must [PRD2160] provide a GUI for specified users to perform audits on all changes made to data.

The CSS-FD system must [PRD2162] time stamp events for use in audit record generation.

Performance Requirements General Design Requirements The CSS-FD system design must [PRD1496] be scalable.

The CSS-FD system must [PRD2164] be designed in accordance with FAA-STD-039, National Airspace System (NAS) Open System Architecture and Protocols.

The CSS-FD system must [PRD2166] be designed in accordance with FAA-STD-043, National Airspace System (NAS) Open System Interconnection (OSI).

The CSS-FD system must [PRD2168] be designed in accordance with FAA-STD-048, National Airspace System (NAS) Open System Interconnection (OSI) Interoperability Standard.

The CSS-FD software must [PRD2174] be developed in accordance with FAA-STD-026, Software Development for the NAS.

Software quality assurance must [PRD2176] comply with (RTCA) DO-278A, Guidance for Communications, Navigation, Surveillance and Air Traffic Management Systems Software Integrity assurance to level 3 or better.

The CSS-FD system must [PRD2180] comply with all SWIM standards and software for NAS programs.

The CSS-FD system must [PRD2182] comply with SWIM Governance Policies, as documented in SWIM Governance Policies Version 3.1.

The CSS-FD system must [PRD2184] comply with SWIM Service Lifecycle Management Process.

Versioning for CSS-FD services…