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
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Table of Contents
1 Introduction..........................................................................................................................................1
2 Capability Description and Program Information...........................................................................2
2.1 Operational Concept......................................................................................................................2
2.1.1 Package A Capabilities..........................................................................................................2
2.1.2 High Level Concept Graphic.................................................................................................4
3 Functional, Information, and Performance Requirements..............................................................6
3.1 Functional Requirements...............................................................................................................6
3.1.1 Capability 1: Data Management and Security Framework....................................................6
3.1.2 Capability 2: Flight Plan Filing...........................................................................................14
3.1.3 Capability 3: Evaluation of Constraints/Restrictions...........................................................19
3.1.4 Capability 4: Flight Specific Feedback................................................................................21
3.2 Data and Information Requirements............................................................................................21
3.2.1 Data Storage.........................................................................................................................21
3.2.2 Archival................................................................................................................................22
3.2.3 Audit....................................................................................................................................22
3.3 Performance Requirements..........................................................................................................23
3.3.1 General Design Requirements.............................................................................................23
3.3.2 General Performance Requirements....................................................................................23
3.3.3 Accuracy..............................................................................................................................24
3.3.4 Response Time.....................................................................................................................24
3.3.5 System Load.........................................................................................................................24
3.4 Reliability, Maintainability, and Availability Requirements.......................................................26
3.4.1 Reliability.............................................................................................................................26
3.4.2 Maintainability.....................................................................................................................27
3.4.3 Availability..........................................................................................................................27
4 Integration Requirements.................................................................................................................28
4.1 Physical Integration.....................................................................................................................28
4.1.1 Environmental Requirements...............................................................................................28
4.1.2 Land and Facility.................................................................................................................28
4.1.3 Telecommunications............................................................................................................28
4.1.4 Special Considerations.........................................................................................................28

iii
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

4.2 Functional Integration..................................................................................................................28

4.2.1 Interfaces to Other FAA Enterprise Architecture Elements................................................28
4.2.2 Interfaces..............................................................................................................................29
4.2.3 Spectrum Requirements.......................................................................................................32
5 Security and Safety Requirements...................................................................................................33
5.1 Facility Security...........................................................................................................................33
5.2 Personnel Security.......................................................................................................................33
5.3 Information Systems Security......................................................................................................33
5.3.1 Security Management..........................................................................................................35
5.3.2 Security Assessments...........................................................................................................35
5.3.3 Security-Related System Support........................................................................................35
5.3.4 System and Information Access...........................................................................................35
5.3.5 System and Information Monitoring....................................................................................35
5.3.6 System and Information Protection.....................................................................................35
5.3.7 Privacy Information Protection............................................................................................35
5.4 System Safety...............................................................................................................................35
5.4.1 Existing Controls.................................................................................................................35
5.4.2 Safety Requirements............................................................................................................36
6 Quality and Configuration Management Requirements...............................................................37
7 Test and Evaluation Requirements..................................................................................................38
8 Implementation and Transition........................................................................................................39
9 In-Service Support and Management..............................................................................................40
Appendix A Acronyms........................................................................................................................41
Appendix B Reference Documents....................................................................................................46
B.1 FAA Documents..........................................................................................................................46
B.1.1 Program Reference Documents...............................................................................................46
B.1.2 FAA Orders..............................................................................................................................46
B.1.3 FAA Standards.........................................................................................................................46
B.1.4 Other FAA Documents............................................................................................................46
B.2 Other Government Documents....................................................................................................47
B.3 Non-Government Documents......................................................................................................47

iv
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

Index of Tables
Table 1: Capabilities' Interdependencies.......................................................................................................6
Table 2: Constraints that can affect a flight’s 4DT......................................................................................21
Table 3: CSS-FD Planning and Filing Input Frequency..............................................................................28
Table 4: CSS-FD Planning and Filing Output Frequency...........................................................................29
Table 5: CSS-FD Interfaces.........................................................................................................................35
Table 6: CSS-FD Flight Data Source Systems............................................................................................36
Table 7: Critical Performance Requirements...............................................................................................59
Table 8: Acronyms and Abbreviations........................................................................................................60
Table 9: Terms and Definitions...................................................................................................................66
Table 10: Verification Requirements Traceability Matrix (VRTM)...........................................................77

v
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

1
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

2 Capability Description and Program Information

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

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

2.1.1.1 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)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.
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

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.

2
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

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.

3
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

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

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

2.1.2 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).

4
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Figure 1: CSS-FD Operational Concept Overview

5
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

3.1 Functional Requirements

3.1.1 Capability 1: Data Management and Security Framework

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

3.1.1.2 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:
a. System operations
b. System maintenance and support
c. System analysis recording.

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

6
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

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

7
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

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

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

8
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

3.1.1.8 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).

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

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

9
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

3.1.1.10 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:
a. Hardware
b. Software
c. Network
d. Interfaces (e.g., flight data sources)
The CSS-FD system must [PRD1362] display the system status and performance of its:

10
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

a. Hardware
b. Software
c. Network
d. 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:
a. Automatically
b. 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.

11
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

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

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

12
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

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

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

13
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

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

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

14
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

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

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

15
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

16
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

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

17
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

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

18
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

3.1.3 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 1).

19
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

Category Constraint
Airspace Constraints

Restricted Airspace Temporary Flight Restriction (TFR)

Active Special Use Airspace (SUA)/ATC Assigned Airspace
(ATCAA) (includes scheduled to be active when flight will be in
airspace)
Prohibited Area
Closed route
TFM required Controlled Departure Time
trajectory elements  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])
Delays/Reroutes with Flow Evaluation Area (FEA) or Flow Constrained Area (FCA)
no required trajectory TFM Advisory: Route Advisory— Recommended
elements 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

ATC required ATC assigned route (automated or manual)— ERAM auto-route or

trajectory elements ATC Preferred Route)
Altitude or speed crossing restriction from ATC SOP/LOA
NAS Resource Constraints

20
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Category Constraint
Outages Navigation Aid (NAVAID)
Radar
Closed Runway
Closed Taxiway
Instrument Landing System (ILS)
Global Positioning System (GPS)
Resource Constraints due to Meteorological Conditions – applied near time of departure

Airport/Route Runway configuration at origin/destination

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

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

3.2 Data and Information Requirements

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

3.2.1 Data Storage

3.2.1.1 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).

21
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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.

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

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

22
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

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

3.3 Performance Requirements

3.3.1 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 artifacts must [PRD2186] be in accordance with the Artifacts
Versioning for SWIM-enabled Services, Software Specification, Version 1.0.0 (December 18,
2015).

23
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

The CSS-FD system must [PRD2190] be in accordance with FAA-STD-060, Data Standard for
the NAS.

3.3.2 General Performance Requirements

The CSS-FD system must [PRD2192] validate proposed flight plans and amendments with a
mean of less than or equal to 4 seconds.
The CSS-FD system must [PRD2194] validate proposed flight plans and amendments with a
mean of less than or equal to 4 seconds.
The CSS-FD system must [PRD2196] validate proposed flight plans and amendments within 6
seconds (99th percentile).
The CSS-FD system must [PRD2198] validate proposed flight plans and amendments with a
maximum of 12 seconds.
The CSS-FD system must [PRD2200] establish independent emergency data communication
within a maximum time of 60 seconds of an emergency being declared.
The CSS-FD system must [PRD2202] assure the data integrity of ground-to-ground data
communications within CSS-FD.

3.3.3 Accuracy
The CSS-FD system’s ATC constraint applicability determination for a flight must [PRD1476]
be consistent with determination using the trajectory that ERAM would generate for the case
when no trajectory is submitted by the user.
The CSS-FD system’s TFM constraint applicability determination for a flight must [PRD1478]
be consistent with determination using the trajectory that TFMS would generate for the case
when no trajectory is submitted by the user.
The CSS-FD system must [PRD2204] utilize the NAS Network Time Protocol (NTP) servers to
maintain a system time within 10 milliseconds.

3.3.4 Response Time

The CSS-FD system must [PRD1480] respond to a user-submitted flight plan and flight plan
update with feedback on all applicable constraints within 3.0 seconds (mean) and 5.0 seconds
(99th percentile) under the system load.
The CSS-FD system must [PRD1482] respond to a constraint update with feedback on all plans
output within 15 seconds (mean) and 45 seconds (99th percentile) under the system load.
The CSS-FD system must [PRD2309] transfer operations between inter-facility data
communication systems within a maximum time of 6 seconds.

3.3.5 System Load

The CSS-FD system must [PRD1500] be able to retain 12,000 total flight plans (Preliminary and
Filed Plans) for evaluation when a constraint update occurs.

24
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

The CSS-FD system must [PRD1501] maintain a reserve communication bandwidth capacity
equivalent to 50% of the maximum bandwidth workload usage.
The CSS-FD system must [PRD1503] maintain a reserve capacity to support a 50% increase in
the number of users beyond the initial capacity allocated at delivery.
The CSS-FD system must [PRD1505] maintain a reserve capacity to support a 50% increase in
the number of flights beyond the initial capacity allocated at delivery.
The CSS-FD system must [PRD1507] maintain a reserve capacity to support a 50% increase in
the processing capacity beyond the initial capacity allocated at delivery.
The CSS-FD system must [PRD2486] be capable of processing all inputs at associated
frequencies defined in Table 2.
The CSS-FD system must [PRD2488] be capable of producing all outputs at associated
frequencies defined in Table 3.
Table 2: CSS-FD Planning and Filing Input Frequency
Frequency (per Notes
Data
minute)
User Inputs
Preliminary Flight Plans 148
TOS 37
Trial Plans 1480
Filed Plan 148
Plan update/amendment (includes ICAO CHG
74
and DLA messages)
Plan cancellation (includes ICAO CNL message) 0
Other flight plan related messages for pass-
through to ERAM (includes RCF, SPL and RQS 0
messages)
Slot substitution messages -
Inputs from ATC Automation
Filed Plan Amendment 48
Response to a Filed Plan 148
Departure Information 148
Constraints

25
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Frequency (per Notes

Data
minute)
Speed/altitude restrictions for boundary crossing
0
– status update
Auto-routes (ADR, ADAR, AAR status updates) 59
SAA Status update 22
This is the aggregate value
TMI – Reroute Advisory 10 for all TMIs except
MIT/MINIT restrictions.
TMI – MIT/MINIT Restrictions 12
Metering restriction 1
TMI – GDP Included in Reroute
TMI – GS Advisory value.
TMI – AFP
TMI - CTOP
ATC Preferred Routes 0
Controlled Departure Time 141
Atmospheric Data
Wind and temperature aloft, barometric pressure
0.02
data
Constraints
Result of CTOP processing of TOS Plan by
37
TFMS
Table 3: CSS-FD Planning and Filing Output Frequency
Data Frequency (per minute)
Constraint feedback 3080
CSS-FD generated trajectory 3080
TFM/ATC amendment to plan 48
Plans for filing 148
Preliminary plans 148
TOS plans 37

26
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Data Frequency (per minute)

Response to a filed plan 148

3.4 Reliability, Maintainability, and Availability Requirements

3.4.1 Reliability
The CSS-FD system must [PRD1512] restore efficiency-critical services within 6 seconds of
failure.
The CSS-FD system must [PRD1506] have no single point of failure.

3.4.2 Maintainability
The CSS-FD system must [PRD1516] have a Mean Time Between Failure (MTBF) for
efficiency-critical service threads be equal to or greater than 50,000 hours.
The design of the CSS-FD system must [PRD0396] allow maintenance of each hardware
component.
The design of the CSS-FD system must [PRD2396] allow maintenance of each hardware
subsystem.
The design of the CSS-FD system must [PRD2398] allow maintenance of each lowest
replaceable unit (LRU).
Where redundant hardware or software is used to satisfy reliability requirements, the CSS-FD
system must [PRD2506] automatically switchover from a failed element to the redundant
element.
Where redundant hardware or software is used to satisfy reliability requirements, the CSS-FD
system must [PRD1365] monitor the health of all redundant elements.
Failed resources must [PRD2206] be isolatable from the CSS-FD for performance of
maintenance operations.

3.4.3 Availability
The CSS-FD system must [PRD2508] have an inherent availability (A i) to support efficiency
critical services (0.9999).
The CSS-FD system must [PRD1502] process flight plans at efficiency critical level of
availability.
The CSS-FD system must [PRD1509] acquire flight information for flight planning at efficiency
critical level of availability.

27
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

4 Integration Requirements
4.1 Physical Integration

4.1.1 Environmental Requirements

Not applicable.

4.1.2 Land and Facility

Not applicable.

4.1.3 Telecommunications
The CSS-FD program must [PRD0550] comply with FAA Order 1830.10, Managing New
Telecommunications Requirements.
The CSS-FD program must [PRD0551] comply with FAA-STD-049, Fiber Optic
Telecommunication System and Equipment.

4.1.4 Special Considerations

N/A

4.2 Functional Integration

The CSS-FD system must [PRD0475] prohibit the use, connection to, or exchange of data with
nongovernmental systems or publicly available systems except through the approved NAS
boundary gateways as outlined in FAA Order 1370.121, FAA Information Security and Privacy
Program and Policy.

4.2.1 Interfaces to Other FAA Enterprise Architecture Elements

Service interface requirements for CSS-FD services must [PRD2208] be identified and
documented in accordance with FAA-STD-074, Preparation of Service Requirements Document.
Web Service Description Documents (WSDDs) for CSS-FD services must [PRD2210] be
developed in accordance with FAA-STD-065 Rev. B, Preparation of Web Service Description
Documents.
Java Message Service Description Documents (JMSDDs) for CSS-FD Services must [PRD2212]
be developed in accordance with FAA-STD-073A, Preparation of Java Messaging Service
Description Documents (December 9, 2019).
The CSS-FD program must [PRD2216] comply with onboarding requirements from SWIM
program office for producer functions.
The CSS-FD program must [PRD2218] comply with onboarding requirements from SWIM
program office for consumer functions.
The CSS-FD system must [PRD1303] support SWIM request/response communications.

28
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

The CSS-FD system must [PRD2220] provide a function to communicate with NADIN Message
Rehost (NMR).
The CSS-FD program must [PRD0554] prepare interface documentation in accordance with
FAA-STD-025F, Preparation of Interface Documentation.
The CSS-FD program must [PRD0555] implement remote maintenance monitoring interfaces in
accordance with FAA Order JO 6000.53D, Remote Maintenance Monitoring Interface
Development and Implementation.

4.2.2 Interfaces
Interfaces between CSS-FD and other systems must [PRD2224] be designed to support
continuous operations in the event of system failures.

4.2.2.1 Interfaces to External Users/Systems

The CSS-FD system must [PRD1486] support the interfaces listed in Table 4.
Table 4: CSS-FD Interfaces
Interface Purpose Notes

Messages are defined in

the ICAO Manual on FF-
ICE Implementation
Guidance and ICAO
The interface is used for submittal of FF-ICE and Procedures for Air
Users of the Navigation Services- Air
legacy messages to the system and receipt of
system for Traffic Management.
responses including feedback on applicable
Planning and
constraints. The messages received include inputs Note-- NAS Data
Filing
destined for ATC automation systems and TFMS. Interchange Network
(NADIN) and NEMS are
used for legacy message
exchange and NEMS for
FF-ICE messages.

TFMS The interface provides TFM constraints to the JAVA MESSAGING

system. Also, the interface is used by the system SERVICE DESCRIPTION
to send Preliminary Plans and Collaborative DOCUMENT Traffic Flow
Decision Making (CDM) messages to TFMS. Management Data Service
And the interface is used by the system to send (TFMData)
amendments from users received during the
lockout to TFMS.

29
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Interface Purpose Notes

There will also be an off-line interface used by
Note--current definition
the system to receive TFMS adaptation data such
will need to be enhanced to
as aircraft performance used for trajectory
address system needs.
modeling
The interface is used by the system to submit
filed plans to ERAM and ATOP and receive
responses. Also, the interface is used by the
ERAM/National Airspace
system to receive updates to constraint status for
Data Interchange Network
SAAs, adapted routes, and altitude and speed
restrictions. And it is also used to receive ATOP
dynamic routes.
There will also be an off-line interface used by
the system to receive ERAM and ATOP
(NADIN) (Service-B
ERAM and adaptation data such as airspace definition and
Users) and
ATOP aircraft performance used for plan validation and
trajectory modeling
ERAM/ User Systems via
ATM IPOP Interface
Control Document.
Note--will need to be
enhanced or supplemented
to address additional data
exchange needs for the
system,
Aeronautical The interface is used by the system to receive Note--Aeronautical
Common constraint data not available from TFMS or ATC Common Services are
Services automation, such as NOTAMs. currently being defined.
The interface is used by the system to receive (WSDD WINS WEB
CSS-WX
winds and temperature aloft data to model COVERAGE SERVICE
Services
trajectories. (WCS))
The interface is used to obtain constraint
NCR
information and enterprise-level NAS status.

4.2.2.2 Flight Data Source Systems

The CSS-FD system must [PRD1488] obtain its source flight data from the NAS systems
specified in Table 5.

30
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Table 5: CSS-FD Flight Data Source Systems

Source Primary Function Generated Flight Data
ASDE-X and Monitor surface traffic Flight tracking updates
ASSC (one-second update rate)
EFSTS and Track and manage tower flight strips, deliver pre- Clearance delivery times,
TDLS departure clearances actual event times
(departure and surface)
STARS Monitor and control flights in TRACON airspace VFR flight data, departure
(TRACON) event times, coordination
information, flight track
updates (five-second
update rate)
ERAM (En Monitor and control flights in CONUS en route ERAM ARTCC-specific
Route airspace flight plan identifier, flight
Automation plan information, P-times
System) (usually the gate pushback
time), arrival event times,
coordination information,
flight track updates (12-
second update rate)
TFMS Monitor and manage traffic demand TFMS NAS-wide flight
ID, flight planning data,
flight plan information
(reroutes, assigned routes,
and extended routes), event
times (departure, arrival,
and surface), controlled
times, flight status, flow
information
Oceanic (i.e., Monitor and control flights in oceanic, Flight plan information,
ATOP), international, and offshore airspaces departure and arrival event
International, times, coordination
and Offshore information, flight track
Sources (e.g., updates (at varied update
OASIS) rates)
STDDS Publishes tower and TRACON data STDDS airport-wide flight
(SMES) identifier (SMES only),
actual event times
(departure, arrival, and
surface)

31
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Source Primary Function Generated Flight Data

TBFM Provides arrival and en route metering TBFM ARTCC-specific
flight identifier, route
estimated times, meter
times, Meter Reference
Element (MRE)
information
TFDM Monitor and manage surface operations TFDM flight identifier,
event times (departure,
arrival, and surface),
surface hold/queue
information, departure
readiness status,
departure/arrival runway
assignments, flight status

4.2.3 Spectrum Requirements

N/A

32
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

5 Security and Safety Requirements

Note: The CSS-FD is a “Moderate” impact system under Federal Information Processing
Standards (FIPS) FIPS 199, Standards for Security Categorization of Federal Information and
Information Systems and will implement the Moderate ATO-tailored National Institute of
Standards and Technology (NIST) SP800-53 security control requirements. The CSS-FD is
responsible to implement the “System” type controls found in the ATO-tailored matrix, while the
“Common” type controls are provided by enterprise services and organizations (ex. FTI, NAS
Enterprise Security Gateway [NESG], Net-Centric Operations (NCO), Security and Hazardous
Materials Safety (ASH), ATO ISS Program). Further analysis will be conducted at the Initial
Investment Decision (IID) to further tailor the ATO requirements to the needs of the CSS-FD.

5.1 Facility Security

N/A

5.2 Personnel Security

N/A

5.3 Information Systems Security

The CSS-FD system must [PRD2240] be compliant with FIPS-200, Federal Information
Processing Standard Publication 200, Minimum Security Requirements for Federal Information
and Information Systems.
The CSS-FD system must [PRD2242] comply with WS-Federation 1.2 for federation of different
security realms.
The CSS-FD system must [PRD1475] be built in accordance with FAA Order FAA Order
1370.121, FAA Information Security and Privacy Program and Policy.
The CSS-FD system must [PRD2244] maintain and record all system access attempts in a
security audit log, in accordance with FAA Order 1370.121, FAA Information Security and
Privacy Program and Policy, Appendix 4, Audit and Accountability, Section 2.2 on auditable
events, and Appendix 11, Section 4.2 on audit logging of access attempts.
The CSS-FD system must [PRD1477] validate the credentials of each requestor to access
information in accordance with the FAA Order 1370.121.
The CSS-FD system must [PRD1479] authenticate human users in accordance with the FAA
Order 1370.121.
The CSS-FD system must [PRD1481] authenticate systems in accordance with the FAA Order
1370.121.
The CSS-FD system must [PRD1483] complete authentication transaction queries across a
federated network to 500 milliseconds (excluding any additional time introduced by external
systems or infrastructure) in accordance with the FAA Order 1370.121.

33
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

The CSS-FD system must [PRD1485] comply with the Information Security standards as
specified in the NAS TV-1 and FAA Order 1370.121, FAA Information Security Program and
Policy.
The CSS-FD system must [PRD1487] use Attribute Based Access Control (ABAC) based on
standards described in the NIST SP 800-162, Guide to Attribute Based Access Control (ABAC)
Definition and Considerations, January 2014.
Note: most data is publicly available and only needs system or user access control. However,
certain system functions and data (e.g.: business rules) may require ABAC.
The CSS-FD system must [PRD1489] protect passwords from unauthorized disclosure when
stored and transmitted in accordance with the FAA Order 1370.121.
The CSS-FD system must [PRD1491] prohibit passwords from being displayed in accordance
with the FAA Order 1370.121.
The CSS-FD system must [PRD1493] enforce password minimum and maximum lifetime
restrictions in accordance with the FAA Order 1370.121.
The CSS-FD system must [PRD1495] prohibit password reuse for a specified number of
generations in accordance with the FAA Order 1370.121.
The CSS-FD system must [PRD1497] perform password and PIN Management in accordance
with the FAA Order 1370.121.
The CSS-FD system must [PRD1499] authenticate NAS and non-NAS systems before
establishing a connection in accordance with the FAA Order 1370.121.
The CSS-FD system must [PRD2501] detect and report attempts to use expired, revoked,
suspended, or otherwise improper or unauthorized identity credentials in accordance with the
FAA Order 1370.121.
The CSS-FD system must [PRD2248] detect malicious activity, in accordance with NAS-SR-
1000, section 3.10.3.7.
The CSS-FD system must [PRD2250] ensure that all data entered/transferred into the system is
guaranteed free from malware such as Trojans and viruses.
The CSS-FD system must [PRD2252] incorporate anti-virus and malware detection software to
protect its database and application from being infected by computer viruses and Trojans.
The CSS-FD system must [PRD2254] reject and or quarantine all data/files that have been
infected by malware and notify the administrator of the threat/action.
The system boundary protection must [PRD2256] implement intrusion detection technology.
The CSS-FD system must [PRD2258] have boundary protection to prevent unauthorized access
and the insertion of malicious code.
The CSS-FD system must [PRD2503] prevent malicious and unintentional disruption of service
to the FAA networks.

34
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

The CSS-FD system must [PRD2505] provide security service capabilities in accordance with
FAA Order 1370.121, FAA Information Security and Privacy Program and Policy.
The CSS-FD system must [PRD1521] protect access to assets during all operational states, in
accordance with NAS-SR-1000, section 3.10.3.8.
The CSS-FD system services must [PRD2509] be compliant with the requirements defined in the
SWIM Interoperability Basic Security Profile.
The CSS-FD system must [PRD1511] be compliant with Appendix 2, Access Control, of FAA
Order 1370.121. The CSS-FD system must [PRD1513] comply with 44 United States Code
(USC) Federal Information Security Management Act (FISMA).
The CSS-FD system must [PRD1515] record and log security relevant events, and forward such
events for FAA event correlation, incident analysis and potential investigation.
The CSS-FD system must [PRD1517] restrict write access to data through ABAC.
The CSS-FD system must [PRD1523] restrict the release of NAS data to authorized users and
implement confidentiality/access clearance in accordance with NAS-SR-1000, section 3.10.3.4.

5.3.1 Security Management

N/A

5.3.2 Security Assessments

N/A

5.3.3 Security-Related System Support

The CSS-FD system must [PRD0313] support contingency operations in accordance with
Appendix 7, Contingency Planning in FAA Order 1370.121, Information Security and Privacy
Program and Policy.

5.3.4 System and Information Access

N/A

5.3.5 System and Information Monitoring

The CSS-FD system must [PRD0060] implement non-repudiation mechanisms.

5.3.6 System and Information Protection

The CSS-FD system must [PRD0050] connect to non-NAS networks and non-NAS information
systems via the FTI NAS Enterprise Security Gateway (NESG) in accordance with FAA Order
JO 1370.114, Implementation of FAA Telecommunications Infrastructure Services and
Information Security Requirements in the NAS.

5.3.7 Privacy Information Protection

N/A

35
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

5.4 System Safety

5.4.1 Existing Controls

TBD

5.4.2 Safety Requirements

5.4.2.1 Programmatic Compliance

N/A

5.4.2.2 Programmatic Assessments & Documentation

N/A

5.4.2.3 System Safety

The CSS-FD system must [PRD0160] comply with Radio Technical Commission for
Aeronautics (RTCA) DO-278A, Software Integrity Assurance Considerations for
Communication, Navigation, Surveillance and Air Traffic Management (CNS/ATM) Systems.

36
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

6 Quality and Configuration Management Requirements

N/A

37
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

7 Test and Evaluation Requirements

N/A

38
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

8 Implementation and Transition

N/A

39
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

9 In-Service Support and Management

N/A

40
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Appendix A Acronyms
A list of acronyms used throughout this document is provided in Table 6.
Table 6: Acronyms
Acronym Definition
4DT 4-Dimensional Trajectory
AAR Airport Arrival Rate
ABAC Attribute-Based Access Control
ACK “Acknowledge” message
ACS Aeronautical Common Services
ADAR Airport Departure & Arrival Rate
ADIZ Air Defense Identification Zone
ADR Airport Departure Rate
AFP Airspace Flow Program
ANG FAA NextGen Program
ANSI American National Standards Institute
ARTCC Air Route Traffic Control Center
ASDE Airport Surface Detection Equipment
ASH Security and Hazardous Materials Safety
ASSC Airport Surface Surveillance Capability
ATC Air Traffic Control
ATCAA ATC Assigned Airspace
ATM Air Traffic Management
ATO Air Traffic Organization
ATOP Advanced Technologies and Oceanic Procedures
ATS Air Traffic Service
CDM Collaborative Decision Making
CHG “Modification” Message
CNL “Cancellation” Message
CNS Communication, Navigation, and Surveillance
CONUS Continental United States

41
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Acronym Definition
CSS Common Support Services
CTOP Collaborative Trajectory Options Program
DLA “Delay” Message
EDCT Expect Departure Clearance Time
EFSTS Electronic Flight Strip Transfer System
ERAM En Route Automation Modernization
ESM Enterprise Service Monitoring
FAA Federal Aviation Administration
FCA Flow Constrained Area
FCS FAA Cloud Services
FEA Flow Evaluation Area
FF-ICE Flight and Flow – Information for a Collaborative Environment
FFPL Filed Flight Plan
FIPS Federal Information Processing Standard
FISMA Federal Information Security Management Act
FIXM Flight Information Exchange Model
FPL Flight Plan
FTI FAA Telecommunications Infrastructure
FYI For Your Information
GDP Ground Delay Program
GPS Global Positioning System
GUFI Globally Unique Flight Identifier
GUI Graphical User Interface
ICAO International Civil Aviation Organization
ICD Interface Control Document
IFR Instrument Flight Rule
IID Initial Investment Decision
ILS Instrument Landing System
IP Internet Protocol

42
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Acronym Definition
IPOP Intermediate Point of Presence
IRD Interface Requirements Document
ISS Information Systems Security
IT Information Technology
IVR Interactive Voice Response
JMSDD Java Message Service Description Documents
LOA Letter of Agreement
LRU Lowest Replaceable Unit
LUFI Locally Unique Flight Identifier
MAN “Manual” Message
MINIT Minutes in Trail
MIT Miles in Trail
MRE Meter Reference Element
MTBF Mean Time Between Failure
N/A Not Applicable
NADIN National Airspace Data Interchange Network
NAS National Airspace System
NAVAID NAS Boundary Protection System
NCO Net-Centric Operations
NCR NAS Common Registry
NEMS NAS Enterprise Messaging Service
NESG NAS Enterprise Security Gateway
NIST National Institute of Standards and Technology
NMR NADIN Message Rehost
NTP Network Time Protocol
OASIS Operational and Supportability Implementation System
OSI Open System Interconnection
PANS Procedure for Air Navigation Services
PBN Performance Based Navigation

43
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Acronym Definition
PDRR Pre-Departure Re-Route
PIN Personal Identification Number
PRD Program Requirements Document
RCF “Radio Communications Failure” Message
REJ “Reject” Message
RQS “Request Supplementary Flight Plan” Message
RTCA Radio Technical Commission for Aeronautics
RVR Runway Visual Range
SAA Special Activity Airspace
SFDPS SWIM Flight Data Publication Service
SID Standard Instrument Departure
SMES Surface Movement Event Service
SOP Standard Operating Procedure
SPL “Supplementary Flight Plan” Message
STAR Standard Terminal Arrival Route
STARS Standard Terminal Automation Replacement System
STD Standard
STDDS SWIM Terminal Data Distribution System
SUA Special Use Airspace
SWIM System Wide Information Management
TBD To Be Determined
TBFM Time Based Flow Management
TDLS Tower Data Link System
TFDM Terminal Flight Data Manager
TFM Traffic Flow Management
TFMS Traffic Flow Management System
TFR Temporary Flight Restriction
TMI Traffic Management Initiative
TOS Trajectory Option Set

44
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Acronym Definition
TR Trial Request
TRACON Terminal Radar Approach Control
USC United States Code
UUID Universally Unique Identifier
VFR Visual Flight Rules
WCS Web Coverage Service
WINS Weather Information Network Server
WSDD Web Service Description Document

45
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

Appendix B Reference Documents

The references cited within this document are listed below.
The specifications, standards, and handbooks form a part of this document to the extent specified
herein. Unless specifically identified, the issue of a document that is cited in this document is the
one (including all change pages, amendments, inserts, supplemental reports) that is current at the
time of contract award.
B.1 FAA Documents
B.1.1 Program Reference Documents
N/A
B.1.2 FAA Orders
 FAA Order 1376.1, Data Management
 FAA Order JO 1370.98, ATO IT Infrastructure Requirements for Non-FAA connectivity
 FAA Order JO 1370.99ATO NAS Information System Security Patch Management
 FAA Order 1370.121, FAA Information Security and Privacy Program & Policy.
 FAA Order JO 7210.3, Facility Operation and Administration
B.1.3 FAA Standards
 FAA-STD-026, Software Development for the NAS
 FAA-STD-043, National Airspace System (NAS) Open System Interconnection (OSI)
 FAA-STD-047, National Airspace System (NAS) Open System Interconnection (OSI)
Conformance Testing
 FAA-STD-048, National Airspace System (NAS) Open System Interconnection (OSI)
Interoperability Standard
 FAA-STD-060, Data Standard for the NAS
 FAA-STD-065 Rev. B, Preparation of Web Service Description Documents
 FAA-STD-073A, Preparation of Java Messaging Service Description Documents
(December 9, 2019)
 FAA-STD-074, Preparation of Service Requirements Document
B.1.4 Other FAA Documents
 Artifacts Versioning for SWIM-enabled Services, Software Specification, Version 1.0.0
(December 18, 2015)
 FAA AMS Lifecycle Verification and Validation Operations Guide
 FAA ATO NAS Modernization System Safety Management Program (SSMP)
 FAA ATO Safety Risk Management Guide for System Acquisition (SRMGSA)
 FAA NAS TV-1
 FAA NAS-SR-1000
 FAA Security Authorization Handbook
 FAA SWIM Interoperability Basic Security Profile

46
 Initial Program Requirements for CSS-FD
V0.5 (RFI) – 2/1/2021

B.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/.
 29 CFR 1910.1001, Asbestos
 29 CFR 1910.145, Specifications for Accident Prevention Signs
 29 CFR 1910.95, Occupational Noise Exposure
 44 USC FISMA
 FIPS-199, Standards for Security Categorization of Federal Information and Information
Systems
 NIST SP 800-162, Guide to Attribute Based Access Control (ABAC) Definition and
Considerations
B.3 Non-Government Documents
Non-government documents may be requested from the organization responsible for the
development and dissemination of the required document.
 ANSI Z535.4, Product Safety Signs and Labels
 NFPA 13, Standard for the Installation of Sprinkler Systems
 NFPA 101, Life Safety Code
 NFPA 70, National Electrical Code
 NFPA 70E, Standard for Electrical Safety in the Workplace
 RTCA DO-278A, Guidance for Communications, Navigation, Surveillance and Air
Traffic Management Systems Software Integrity
 WS-Federation 1.2

47