Attachment A - Draft E1 (ACS) System Specification Document (SSD).pdf

Aeronautical Information Management Modernization Enhancement 1 (AIMM E1)

Aeronautical Common Services (ACS) System Specification Document (SSD)

Version 0.1

June 15, 2021

Federal Aviation Administration 800 Independence Avenue SW

Washington, DC 20591

June 15, 2021 2

THIS PAGE INTENTIONALLY LEFT BLANK

AIMM E1 Aeronautical Common Services (ACS) System Specification Document (SSD)

October 5, 2021 iii

System Specification Document

Aeronautical Information Management Modernization Enhancement 1

(AIMM E1)

Aeronautical Common Services (ACS)

Revision History

Version Description Initials Date

0.1 Initial draft release KL 6/11/21

0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9

June 15, 2021 iv

TABLE OF CONTENTS

1 INTRODUCTION

1.1 SCOPE

1.2 BACKGROUND

1.3 OVERVIEW

1.3.1 ACS System Description

1.3.1.1 AIMM E1 ACS Enhancements

2 APPLICABLE DOCUMENTS

2.1 FAA DOCUMENTS

2.2 NON-FAA GOVERNMENT DOCUMENTS

2.3 OTHER DOCUMENTS

3 REQUIREMENTS

3.1 FUNCTIONAL REQUIREMENTS

3.1.1 Administer System

3.1.1.1 Manage System Access

3.1.1.2 Manage System Settings

3.1.1.3 Manage Business Processes

3.1.1.4 Manage Business Rules

3.1.1.5 System Administration Tools

3.1.2 Process Source Data

3.1.2.1 Collect Published Data

3.1.2.2 Integrate Aeronautical Information

3.1.2.3 Store Aeronautical Information

3.1.3 Format Aeronautical Information

3.1.3.1 Convert Integrated Aeronautical Information to Output Formats

3.1.3.2 Provide Aeronautical Information Baseline Filesets

3.1.4 Provide Services

3.1.4.1 Web Feature Service

3.1.4.2 Pre-Defined Aeronautical Information Queries

3.1.4.3 Aeronautical Information Subscriptions and Notifications

3.1.4.4 Aeronautical Information Web Mapping Services

3.1.4.5 Airspace Conflict Detection

3.1.4.6 Post-Operations Metrics

3.1.4.7 Geodetic Computations

3.2 DATA AND INFORMATION REQUIREMENTS

June 15, 2021 v

3.3 PERFORMANCE REQUIREMENTS

3.3.1 Process Source Data Performance

3.3.2 AI Formatting Performance

3.3.3 Service Performance

3.3.4 Business Process and Rules Performance

3.4 SECURITY

3.5 SYSTEM MONITORING AND CONTROL

3.6 RELIABILITY, MAINTAINABILITY, AND AVAILABILITY

3.7 HUMAN FACTORS

4 VERIFICATION

4.1 DEVELOPMENTAL TESTING

4.2 METHODS OF VERIFICATIONS

4.3 REQUIREMENTS FOR PERFORMANCE TESTING

4.3.1 Verification Levels

4.3.1.1 General

4.3.1.2 Software Subsystem Tests

4.3.1.3 System Tests

4.4 AUTOMATED TEST TOOL

APPENDIX A – ACRONYMS

APPENDIX B – GLOSSARY

APPENDIX C – INTERFACE DEFINITIONS

APPENDIX D – VERIFICATION REQUIREMENTS TRACEABILITY MATRIX (VRTM)

June 15, 2021 vi

LIST OF FIGURES

Figure 3-1. To-Be ACS Context Diagram

June 15, 2021 1

1 Introduction

Scope

This specification establishes the functional and system requirements for the Aeronautical Common Services (ACS) in the Aeronautical Information Management Modernization Enhancement 1 (AIMM E1) program. It includes requirements for system functions, external and internal interfaces, data and information, system performance, security, system monitoring and control, reliability, maintainability, availability, human factors, and verification.

Background

The Federal Aviation Administration (FAA) uses a wide variety of aeronautical data and Aeronautical Information (AI) products to enable safe, efficient, and cost-effective air transportation operations.

• Aeronautical data include airports, airspace and navigation aids information; Instrument Flight Procedures (IFP) and routes, Notices to Airmen (NOTAMs), and many other categories of National Airspace System (NAS) status and configuration information.

• AI products include NAS resource and status data contained in databases, navigation charts, maps and other data configurations.

Aeronautical data and AI products are exchanged between stakeholders such as Air Traffic Management (ATM) Service Providers, Mission and NAS Support Personnel, and NAS Users.

• ATM Service Providers are FAA operational staff who use ATM platforms such as En Route Automation Modernization (ERAM), Advanced Technologies and Oceanic Procedures (ATOP), Standard Terminal Automation Replacement System (STARS), and Information Display Systems (IDS) to provide air navigation services throughout the NAS.

• Mission and NAS Support Personnel are FAA staff who manage airspace, procedures, charts, and maps; provide Second Level Engineering (SLE) support; conduct operations analysis; and perform research and development (R&D).

• NAS Users plan, coordinate, and execute flight operations. Examples of users include flight planners, dispatchers, and flight crews from Government agencies, commercial airlines, and General Aviation (GA). The user community also includes third party Service Providers as well as international entities such as NAV CANADA, UK NATS, and Eurocontrol for flight planning and procedures development.

The FAA established the Aeronautical Information Management Modernization (AIMM) program to develop and enhance systems and services to address future air traffic requirements related to AI.

AIMM takes advantage of advancements in data processing, cloud storage, standardized information exchange models, and web-based services present opportunities to improve the quality, accuracy, and timeliness of aeronautical data and AI products. The AIMM program is essential to managing the integration of digital AI and improving data collection, management, and dissemination; delivering critical capabilities that support the vision to modernize the NAS through Next Generation Air Transportation System (NextGen) portfolio increments.

There were two previous segments for AIMM:

June 15, 2021 2

• AIMM Segment 1 (AIMM S1) improved the Central Altitude Reservation Function (CARF) for planning, coordinating, and approving Altitude Reservation (ALTRV) requests. It also modernized the collection, management, and dissemination of NOTAMs by establishing the Federal NOTAM System (FNS) as the modern authoritative source for digital NOTAMs.

• AIMM Segment 2 (AIMM S2) established the ACS to further streamline integration and dissemination of AI. The ACS is a trusted access point for distributing AI integrated from multiple authoritative sources. The ACS focuses on a data-centric environment by delivering web services using international standards such as the Aeronautical Information Exchange Model (AIXM) and the Open Geospatial Consortium (OGC) standards on the FAA’s System Wide Information Management (SWIM) infrastructure.

AIMM Enhancement 1 (AIMM E1) builds on the foundation established in AIMM S1 and AIMM S2 to meet the AIMM program’s goal of continuing to modernize the management of AI.

Overview

ACS System Description

The ACS is a system that was implemented in AIMM S2 to provide a consolidated access point for different types of AI that originate from various FAA authoritative sources. It does this through meeting two high-level capabilities:

AI Integration: The ACS collects AI feature updates published by their respective FAA authoritative sources. AI that the ACS collects falls into two main categories:

• Static AI: Baseline definitions for AI including airports, navigational aids (NAVAIDs), obstacles, and Special Activity Airspace (SAA).

• Dynamic AI: Notices and temporary changes to the baseline AI via NOTAMs and airspace schedules. For example, when a NOTAM reports a lighting outage on a runway or when a SAA is scheduled for use by the military for a specific time period.

The ACS then integrates the AI feature updates it collects with the AI stored by the ACS. Static AI updates are integrated with the ACS AI baseline by updating the respective AI feature, and resolving any AI feature references in the update to AI features within the ACS AI baseline. Dynamic AI updates are integrated with the AI features the updates affect (e.g., temporarily updating an airport and runway when a NOTAM of a runway closure is processed by the ACS).

AI Distribution via Services: The ACS uses this integrated AI to distribute AI via a set of web services over the FAA’s SWIM infrastructure. These services include:

• AI Queries: Services that provide users the ability to query for AI features stored in the ACS through a variety of filters.

• AI Subscriptions: Services to subscribe to and receive notifications of AI feature updates.

• AI Mapping: Services that provide geo-referenced map imagery based on AI features in the

ACS.

June 15, 2021 3

• Airspace Conflict Detection: A service to identify airspace conflicts with user-specified or user-defined airspaces.

• Post-Operation Metric Reports: A service to allow users to define and run custom reports based on AI in the ACS

• Geodetic Computations: A service to perform different geodetic computations on user request and do not rely on AI stored in the ACS.

1.3.1.1 AIMM E1 ACS Enhancements

AIMM E1 will build on the ACS implemented in AIMM S2 through the following improvements:

Data Source Ingestion: New AI authoritative sources will be integrated with the ACS.

• The Enterprise Airspace Tool (EAST) will provide a new authoritative source for airspace information. It will replace the ACS’s existing source for static SAA descriptions, and provide additional airspace types.

• Instrument Flight Procedures and Routes data will be provided to the ACS from a new authoritative source.

• Existing ACS AI integration will be updated for additional integration points from the expanded AI baseline and updates to existing authoritative sources (e.g., digital airspace NOTAMs).

Enhanced Web Services: A new ACS notification service as well as updating existing ACS services.

• A new ACS service implementing the Java Message Service (JMS) standard to provide filterable AI notifications over the FAA’s SWIM Cloud Distribution Service (SCDS).

• Updating existing AI services and operations to incorporate new AI types (e.g., new airspace types, IFP, and digital airspace NOTAMs) available in the ACS.

• Performance improvements to existing ACS service operations.

Business Process and Rules Integration: Integration of the ACS Business Process Engine and ACS Business Rules Engine with data source ingestion and AI integration. This will allow the ACS to quickly update business processes and rules to address any changes to the different data source system interfaces and improve the ability for the ACS to expand its AI scope in the future.

Additional Data Formats: ACS services to provide integrated AI in Aeronautical Information Exchange Model (AIXM) 5.2 format in addition to the existing AIXM 5.1 format.

The scope of the changes to the ACS in AIMM E1 are depicted in Figure 3-1.

June 15, 2021 4

Figure 3-1. To-Be ACS Context Diagram

June 15, 2021 5

2 Applicable Documents The following specifications, standards, instructions, orders, guidelines, and handbooks form a part of this document and are applicable to the extent specified herein. The latest version of these documents, as of the Preliminary Design Review milestone, must apply. In the event of a conflict between the referenced documents and the Draft System Specification Document (SSD), the specification in the SSD must apply.

FAA Documents

Document Number

Title Document Date Revision

FAA HF-STD-001B Human Factors Design Standard for the Acquisition of Commercial-Off-the-Shelf (COTS) subsystems, non-developmental items

December 2016

FAA JO 1370.96 ATO System Access Control April 2007

FAA JO 1370.99 ATO NAS Information System Security Patch Management April 2007

FAA JO 1370.101 ATO Information Security Incident Reporting and Response Policy

December 2007

FAA JO 1370.114 Implementation of FAA Telecommunications Infrastructure Services and IS Requirements in the NAS

January 2012

FAA JO 1900.47F Air Traffic Control Operational Contingency Plans March 2020

FAA Order 1200.22E

External Requests for National Airspace System (NAS) Data January 2012

FAA Order 1350.14B

Records Management December 2013

FAA Order 1370.121A

FAA Information Security and Privacy Program & Policy November 2020

FAA Order 1600.75

Protecting Sensitive Unclassified Information (SUI) February 2005

FAA Order 1370.46D

Automatic Data Processing Standard System Identification June 1982

NAS RD-2013 National Airspace System Requirements Document August 2014

AeroNav Products Aeronautical Chart User's Guide November 2020

FAA COMPSYS 21 Geodetic Computations User Documentation

March 2010, Version 3

June 15, 2021 6

Number

Title Document Date Revision

NAS Enterprise Messaging Service (NEMS) Asynchronous Messaging ICD

NAS OS Configuration Baseline Standards

NEMS Interface Control Document

SWIM Governance Policies February 2020, Version 3.1

SWIM Identity and Access Management (IAM) Requirements for Screening Information Requests and Requests for Proposals

SWIM Interface Requirements Document

SWIM NAS Service Registry/Repository Overview

SWIM Service Compliance Requirements

Non-FAA Government Documents

Number

Title Document Date Revision

DOT Order 1351.37

Departmental Cybersecurity Policy June 2011

FIPS 199 Categorization of Federal Information and Information Systems

February 2004

FIPS 200 Minimum Security Requirements for Federal Information and Information Systems

March 2006

SP 800-53 National Institute of Standards and Technology (NIST) Security and Privacy Controls for Information Systems and Organizations

September 2020 Revision 5

National Oceanic and Atmospheric Administration's (NOAA) National Geodetic Survey (NGS) Geodetic Tool Kit

Other Documents

June 15, 2021 7

Number Title

Document Date Revision

Annex 15 International Civil Aviation Organization (ICAO) Annex 15, Aeronautical Information Services

July 2018, 16th Edition

OGC 04-094

OGC Web Feature Service (WFS) Implementation Specification October 2016

OGC 06-042 OpenGIS Web Map Service Implementation Specification March 2006, Version 1.3

OGC 07-057r7 OpenGIS Web Map Tile Service Implementation Standard April 2010, Version 1

OGC 08-038r7 OGC Axis Order Policy Guidance June 2017

OGC 12-027r3 OGC Web Feature Service Temporality Extension (WFS-TE) July 2014, Version 1

AIXM Specification Version 5.1

AIXM 5.1 Business Rules

February 2019, Version 0.8

AIXM 5 Feature Identification and Reference April 2011, Version 1

AIXM 5 Temporality Concept

February 2019, Version 1.1

June 15, 2021 8

3 Requirements

This section describes the functional, data and information, performance, security, system monitoring and control, human factors, and reliability, maintainability, and availability (RMA) requirements.

The following set of requirements includes both legacy requirements from AIMM S2 and new AIMM E1 requirements. In some cases, AIMM S2 legacy requirements needed to be modified to address the needs of AIMM E1. All AIMM S2 legacy and modified requirements will be applicable for AIMM E1.

Functional Requirements

Administer System

This section and subsections capture functional requirements related to the administration of the ACS.

3.1.1.1 Manage System Access

SSD-A-001 The ACS web services must comply with System Wide Information Management

(SWIM) Governance Policies, Version 3.1, February 2020.

SSD-A-002 The ACS web service interfaces must be available through the FAA SWIM infrastructure.

SSD-A-003 The ACS must provide JMS AI update notifications through the FAA's SWIM Cloud

Distribution Service (SCDS).

3.1.1.2 Manage System Settings

SSD-A-004 The ACS must have secure connections to authoritative sources be configurable by system administrators without requiring a redeployment of the system.

3.1.1.3 Manage Business Processes

This section captures functional requirements for the ACS Business Process Engine to manage and execute business processes used by the ACS in its AI processing.

SSD-A-005 The ACS must manage business processes in a business process engine (ACS

Business Process Engine).

SSD-A-006 The ACS must restrict access to business process management to users with system administrator privileges.

SSD-A-007 The ACS business processes must be defined in industry standard language.

Note: For example, Business Process Execution Language (BPEL).

SSD-A-008 The ACS must add business rules from the ACS Business Rules Engine to steps in business process definitions as specified by the user.

June 15, 2021 9

SSD-A-009 The ACS must create a business process on user request.

SSD-A-010 The ACS must update a business process on user request.

SSD-A-011 The ACS must delete a business process on user request.

SSD-A-012 The ACS must store business process definitions.

SSD-A-013 The ACS must apply business process updates in production on system administrator request without requiring a redeployment of the system.

SSD-A-014 The ACS must execute a stored business process upon request of the system.

SSD-A-015 When executing business processes, the ACS must enforce business rules applicable to each business process.

SSD-A-016 The ACS must return an error message upon failure of any business process.

SSD-A-017 The ACS must provide status, including current process step, of business process instances to track progress.

SSD-A-018 The ACS must provide a mechanism for authorized users to attach files to a business process instance during execution as supporting documentation.

3.1.1.4 Manage Business Rules

This section captures functional requirements for the ACS Business Rules Engine to manage execute business rules used by the ACS in its AI processing.

SSD-A-019 The ACS must manage business rules in a business rules engine (ACS Business

Rules Engine).

SSD-A-020 The ACS must restrict access to business rules management to users with system administrator privileges.

SSD-A-021 The ACS business rules must be defined in industry standard language.

Note: For example, Semantics of Business Vocabulary and Business Rules (SBVR).

SSD-A-022 The ACS must create a business rule on user request.

SSD-A-023 The ACS must update a business rule on user request.

SSD-A-024 The ACS must delete a business rule on user request.

SSD-A-025 The ACS must store business rule definitions.

SSD-A-026 The ACS must validate that business rules are formatted in industry standard language.

SSD-A-027 The ACS must manage at least 3 different versions of business rules (i.e., provide rule versioning).

SSD-A-028 The ACS must apply business rule updates in production on system administrator request without requiring a redeployment of the system.

SSD-A-029 The ACS must execute stored business rules when triggered by a business process.

SSD-A-030 The ACS must generate an error message that states the cause of the error upon failure during execution of a business rule.

June 15, 2021 10

3.1.1.5 System Administration Tools

SSD-A-031 The ACS must have a graphical user interface (GUI) to manage business processes used by the ACS.

SSD-A-032 The ACS must provide a graphical representation of business processes defined in the system.

SSD-A-033 The ACS must provide a graphical user interface to system administrators that monitors business processes being executed.

SSD-A-034 The ACS must have a graphical user interface (GUI) to manage business rules used by the ACS

Process Source Data

This section and subsections capture functional requirements related to the collection, integration, and storage of AI in the ACS.

3.1.2.1 Collect Published Data

SSD-A-035 The ACS must collect each AI feature update published by the authoritative sources.

SSD-A-036 The ACS must collect published AI feature updates from authoritative sources via

SWIM Infrastructure.

SSD-A-037 The ACS must collect metadata provided by authoritative sources.

SSD-A-038 The ACS must perform checks to ensure data collected from authoritative sources was not corrupted in transit.

3.1.2.2 Integrate Aeronautical Information

SSD-A-039 The ACS must maintain a level of data integrity as defined by International Civil

Aviation Organization (ICAO) Annex 15 for essential data.

Note: This is in section 3.2.3 of ICAO Annex 15, of the Sixteenth Edition, July 2018:

"assure corruption does not occur at any stage of the entire process and include additional processes as needed to address potential risks in the overall system architecture to further assure data integrity at this level."

SSD-A-040 The ACS must resolve associations with referenced AI features to AI features stored in the ACS when ingesting AI feature updates.

SSD-A-041 The ACS must maintain associations with referenced AI features when ingesting AI feature updates.

Note: For example: that a Runway is at a specific Airport; that a Notice to Airmen (NOTAM) applies to a specific NAVAID; or an Airspace is defined using an Airport as a center point of a circle.

June 15, 2021 11

SSD-A-042 The ACS must maintain associations between AI features stored in the ACS using the Universally Unique Identifiers (UUIDs) of the AI features.

SSD-A-043 The ACS must uniquely identify AI features using UUIDs in accordance with the AIXM 5 Feature Identification and Reference document.

SSD-A-044 The ACS must maintain the UUID for each AI feature throughout the AI feature’s entire lifecycle.

SSD-A-045 The ACS must assign a UUID for each AI feature ingested that does not already contain a UUID.

SSD-A-046 The ACS must maintain the existing UUID for each AI feature ingested that has a

UUID.

SSD-A-047 The ACS must persist the effective dates of the AI changes received from authoritative sources.

SSD-A-048 The ACS must update AI features consistent with the AIXM Temporality Model documented in AIXM 5 Temporality Concept.

SSD-A-049 The ACS must capture metadata on the source for each AI feature update ingested.

SSD-A-050 The ACS must update SUA features that are baselined in the ACS to incorporate SUA schedules received from an authoritative source.

SSD-A-051 The ACS must update ATCAA features that are baselined in the ACS to incorporate

ATCAA schedules received from an authoritative source.

SSD-A-052 The ACS must update MTR features that are baselined in the ACS to incorporate

MTR schedules received from an authoritative source.

SSD-A-053 The ACS must update AI features that are baselined in the ACS to incorporate changes to that feature from a digital NOTAM received from an authoritative source.

Note: For example, if a NOTAM is received that a runway is closed, the affected runway is updated in the ACS.

SSD-A-054 If no latitude/longitude values are present for a NOTAM being processed by the ACS, the ACS must set the NOTAM's latitude/longitude position based on the NOTAM's associated features or location field.

Note: For example, if the NOTAM is at a given Airport, the latitude/longitude position of the NOTAM is to be populated with the Airport's Airport Reference Point.

SSD-A-055 The ACS must process initial data loads from the authoritative sources to create an initial AI baseline in the ACS.

SSD-A-056 The ACS must retain existing ACS AI feature UUIDs in the event the ACS processes additional initial data loads from an authoritative source.

SSD-A-057 The ACS must define AI integration business processes using the ACS Business Process Engine.

SSD-A-058 The ACS must use the ACS Business Process Engine to perform business processes related to AI integration.

SSD-A-059 The ACS must use business processes defined in the business process manager for processing AI feature updates from AI authoritative sources.

SSD-A-060 The ACS must define AI integration business rules using the ACS Business Rules Engine.

SSD-A-061 The ACS must use the ACS Business Rules Engine to perform business rules related to AI integration.

June 15, 2021 12

3.1.2.3 Store Aeronautical Information

SSD-A-062 The ACS must store AI feature updates collected from the authoritative sources.

SSD-A-063 The ACS must store initial data loads from the authoritative sources.

SSD-A-064 The ACS must store metadata on AI features.

SSD-A-065 The ACS must store metadata on AI feature updates.

Format Aeronautical Information

This section and subsections capture functional requirements related to the formatting of AI provided by the ACS.

3.1.3.1 Convert Integrated Aeronautical Information to Output Formats

SSD-A-066 The ACS must convert stored AI feature information to AIXM 5.1 specification format for distribution.

SSD-A-067 ACS messages in AIXM 5.1 format must be valid against the AIXM 5.1 and approved

AIXM extension schemas.

SSD-A-068 The ACS must adhere to AIXM Temporality Usage Rules documented in AIXM 5

Temporality Concept 1.1 when generating AIXM 5.1 messages.

SSD-A-069 The ACS must adhere to AIXM business rules documented in AIXM 5.1 Business

Rules that are applicable to the ACS data set when generating AIXM 5.1 messages.

SSD-A-070 The ACS must adhere to AIXM Temporality Data Coding Rules documented in AIXM

5 Temporality Concept 1.1 when generating AIXM 5.1 messages.

SSD-A-071 The ACS must convert stored AI feature information to AIXM 5.2 specification format for distribution.

SSD-A-072 ACS messages in AIXM 5.2 format must be valid against the AIXM 5.2 and approved

AIXM extension schemas.

SSD-A-073 The ACS must adhere to AIXM Temporality Usage Rules documented in AIXM 5

Temporality Concept when generating AIXM 5.2 messages.

SSD-A-074 The ACS must adhere to AIXM business rules documented in AIXM 5.2 Business

Rules that are applicable to the ACS data set when generating AIXM 5.2 messages.

SSD-A-075 The ACS must adhere to AIXM Temporality Data Coding Rules documented in AIXM

5 Temporality Concept when generating AIXM 5.2 messages.

SSD-A-076 The ACS must define format conversion business processes using the ACS Business

Process Engine.

SSD-A-077 The ACS must use the ACS Business Process Engine to perform business processes related to converting AI to output formats.

June 15, 2021 13

3.1.3.2 Provide Aeronautical Information Baseline Filesets

SSD-A-078 The ACS must create AI baseline filesets that contain all AI features in the ACS that are effective within a specified period of time to support initial load for ACS subscribers.

SSD-A-079 The ACS must create separate AI baseline files to support different AI feature types.

SSD-A-080 The ACS must create separate AI baseline filesets to support all different formats ACS notifications are provided in.

SSD-A-081 The ACS must provide automated AI baseline fileset creation based on a configurable recurring schedule.

SSD-A-082 The ACS must provide AI baseline fileset creation on request of system administrators for system administrator specified effective date, AI feature types, and data formats.

SSD-A-083 The ACS must automatically upload AI baseline file sets to configurable locations to support distribution for ACS user initial loads.

Note: Configurable locations may include cloud distribution.

Provide Services

This section and subsections capture functional requirements related to the services provided to ACS users.

3.1.4.1 Web Feature Service

This section captures functional requirements for the ACS’s Web Feature Service (WFS), which implements the OGC’s WFS standard to provide users the ability to query for any AI feature stored in the ACS.

SSD-A-084 The ACS must provide a Web Feature Service (WFS) service in accordance with the

Open Geospatial Consortium (OGC) Web Feature Service (WFS) Implementation Specification.

SSD-A-085 The ACS WFS must provide descriptions of operations and parameters related to ACS WFS upon request.

SSD-A-086 The ACS WFS must return AI features based on combinations of spatial, temporal, attribute, and feature relationship constraints in a user-defined query.

SSD-A-087 The ACS WFS must provide geo-referenced AI features.

SSD-A-088 The ACS WFS must follow the OGC axis ordering guidelines when a spatial reference system (SRS) is not specified. [OGC Axis Order Policy Guidance, June 2017].

SSD-A-089 The ACS WFS must create response messages to user-defined AI queries based on AI features stored by the ACS.

SSD-A-090 The ACS WFS must return only AI feature information that applies to the user-submitted query time parameters.

June 15, 2021 14

SSD-A-091 The ACS WFS must process the AIXM time slices for temporal filters on user-defined AI queries adhering to the OGC Web Feature Service Temporality Extension (WFS-

TE).

SSD-A-092 The ACS WFS must return associated AI features when a user-defined query requests AI features based on associations with other AI features (e.g., provide all Runways at a given Airport, or provide all Route Segments that are part of a given Route).

SSD-A-093 The ACS WFS must return AI features based queries on feature metadata.

SSD-A-094 The ACS must perform altitude data conversions between Mean Sea Level (MSL), Above Ground Level (AGL), and Flight Level (FL) when processing user-defined queries on AI feature altitude.

SSD-A-095 The ACS WFS must return human-readable error messages to the user in response to failed user-defined query requests.

SSD-A-096 The ACS must provide user-defined query results in the user specified data format.

SSD-A-097 The ACS must provide user-defined query results in AIXM 5.1 data format.

SSD-A-098 The ACS must provide user-defined query results in AIXM 5.2 data format.

SSD-A-099 The ACS must provide a web service for users to create customized stored queries.

SSD-A-100 The ACS must provide a web service for users to read customized stored queries.

SSD-A-101 The ACS must provide a web service for users to delete customized stored queries.

SSD-A-102 The ACS must restrict reading stored queries to users who are the stored query creator or system administrators.

SSD-A-103 The ACS must restrict updating stored queries to users who are the stored query creator or system administrators.

SSD-A-104 The ACS must restrict deleting stored queries to users who are the stored query creator or system administrators.

SSD-A-105 The ACS must store user customized stored queries.

SSD-A-106 The ACS must process user-specified stored queries on user request.

SSD-A-107 The ACS must process user-specified stored queries on user-specified parameters.

SSD-A-108 The ACS must restrict stored query processing to users who are the stored query creator or system administrators.

3.1.4.2 Pre-Defined Aeronautical Information Queries

This section captures functional requirements for ACS operations to query AI features in ways that are not supported by the OGC WFS standard.

SSD-A-109 The ACS must provide descriptions of pre-defined queries and parameters upon request.

SSD-A-110 The ACS pre-defined queries must follow the OGC axis ordering guidelines when a spatial reference system (SRS) is not specified. [OGC Axis Order Policy and Recommendations, June 2017].

SSD-A-111 The ACS must create response messages to pre-defined AI queries-based AI features stored by the ACS.

June 15, 2021 15

SSD-A-112 The ACS must return only AI feature information that applies to the user-submitted query time parameters for pre-defined queries.

SSD-A-113 The ACS must perform altitude data conversions between MSL, AGL, and FL when processing pre-defined queries on AI feature altitude.

SSD-A-114 The ACS must return error messages that state the cause of the error to the user in response to failed pre-defined query requests.

SSD-A-115 The ACS must provide pre-defined query results in the user specified data format.

SSD-A-116 The ACS must provide pre-defined query results in AIXM 5.1 data format.

SSD-A-117 The ACS must provide pre-defined query results in AIXM 5.2 data format.

SSD-A-118 The ACS must provide a query operation that returns AI features within a user specified flight path, feature type, altitude range, and time period.

Note: A flight path is a linear geometry formed by a series of routes, NAVAIDs, airports, and/or fixes with a buffer.

SSD-A-119 The ACS must provide a query operation that returns NOTAMs within a user specified flight path, feature type, altitude range, and time period.

Note: A flight path is a linear geometry formed by a series of routes, NAVAIDs, airports, and/or fixes with a buffer.

SSD-A-120 The ACS must provide a query operation that returns AI features within a user specified radius, center point, feature type, altitude range, and time period.

SSD-A-121 The ACS must provide a query operation that returns NOTAMs within a user specified radius, center point, feature type, altitude range, and time period.

SSD-A-122 The ACS must provide a query operation that returns an AI feature for a user specified AI feature UUID, type with values effective for a user specified time period.

SSD-A-123 The ACS must provide a query operation that returns a NOTAM and all AI features in the ACS affected by that NOTAM matching a user specified NOTAM.

SSD-A-124 The ACS must provide a query operation that returns an Airspace and all related AI features that make up the legal description of the user-specified Airspace and time range.

SSD-A-125 The ACS must provide a query operation that returns an Airport and all related AI features describing the airport (e.g., services, runway directions, lighting systems) matching a user-specified Airport and time range.

3.1.4.3 Aeronautical Information Subscriptions and Notifications

This section captures functional requirements for ACS services to subscribe to and receive notifications of AI feature updates.

SSD-A-126 The ACS must provide the ability for a user to subscribe to AI updates.

SSD-A-127 The ACS subscription service must provide details on the capabilities of the service on user request.

SSD-A-128 The ACS must provide a Java Message Service (JMS) to distribute AI update notifications to subscribers.

June 15, 2021 16

SSD-A-129 The ACS subscription service must provide subscriptions based on AI domains available in the ACS.

Note: An AI domain refers to a group of AI feature updates pertaining to a specific set of AI. For example, a user subscribing to update for airports could want updates not just to airports, but related features such as runways, runway direction, lighting systems. A subscriber to NAVAIDs would expect to get updates for associated NAVAID equipment (e.g., Very High Frequency (VHF) Omnidirectional Range (VORs), Tactical Air Navigation System (TACANs), and glidepaths).

SSD-A-130 The ACS subscription service must create a new subscription to AI updates on user request.

SSD-A-131 The ACS subscription service must update a user's subscription to AI updates on user request.

SSD-A-132 The ACS subscription service must cancel a user's subscription to AI updates on user request.

SSD-A-133 The ACS must create notification messages containing the changes to AI features when AI feature changes are ingested by the ACS.

SSD-A-134 The ACS must deliver subscription notification messages to users subscribed to the AI features changed in the message.

SSD-A-135 The ACS JMS must provide a way for subscribers to filter notifications using multiple filter criteria without processing the whole notification message.

Note: This could be a subset of important elements (e.g., Air Route Traffic Control Center (ARTCC), State, Designator, Type, Dynamic vs Static update (i.e., time slice interpretation)) for each feature type in the header message. Some of these elements might be derived from that feature's relationships to other features (e.g., the state (e.g., Virginia) that a Runway is in is captured by the Airport the Runway is located).

SSD-A-136 The ACS must identify the sequence of subscription notification messages provided to subscribers.

SSD-A-137 The ACS must identify AI updates provided to subscribers that are corrections to previous AI updates.

Note: An example of this is an AI update setting the end time for an existing AIXM feature time slice.

SSD-A-138 The ACS must ensure that subscription notification messages are delivered at least once to subscribers.

SSD-A-139 The ACS subscription service must provide different subscriptions for the different output formats available.

SSD-A-140 The ACS must provide subscription notification messages in AIXM 5.1.

SSD-A-141 The ACS must provide subscription notification messages in AIXM 5.2.

3.1.4.4 Aeronautical Information Web Mapping Services

This section captures functional requirements for two different ACS mapping services that provide AI map imagery.

• The ACS Web Map Service (WMS) is an implementation of the OGC’s Web Map Service standard in order to provide map imagery of AI features stored by the ACS, retrievable from user requests including a user-specified filter and map layer.

June 15, 2021 17

• The ACS Web Tile Map Service (WMTS) is an implementation of the OGC’s Web Map Tile Service standard in order to provide map imagery as tiles of AI features stored by the ACS, retrievable from users requesting specific tiles from available ACS WMTS tile matrices and map layers.

SSD-A-142 The ACS must provide a service (ACS Web Map Service (WMS)) that provides geo-referenced map layer images representing AI features in the ACS.

SSD-A-143 The ACS WMS must comply with the OGC Web Map Service Implementation

Specification.

SSD-A-144 The ACS WMS must execute the mandatory functionality of the OpenGIS Web Map

Service Implementation Specification.

SSD-A-145 The ACS WMS must use FAA standard symbology when representing AI features in map imagery.

Note: Refer to AeroNav Products Aeronautical Chart User's Guide.

SSD-A-146 The ACS WMS must provide AI map imagery implementing the World Geodetic System 84 (WGS84) spatial reference system (SRS).

SSD-A-147 The ACS WMS must provide AI map imagery implementing the North American Datum of 1983 (NAD 83) SRS.

SSD-A-148 The ACS WMS must advertise AI map layers available from the services.

SSD-A-149 The ACS WMS must advertise supported coordinate reference systems for the mapping services.

SSD-A-150 The ACS WMS must provide different map layers for different AI feature domains.

Note: For example, different layers for Airports, NAVAIDs, SAA, Sector Airspace.

SSD-A-151 The ACS WMS must filter AI features for map layer images by one or more layer names.

SSD-A-152 The ACS WMS must filter AI features for map layer images by bounding box parameters.

SSD-A-153 The ACS WMS must filter AI features for map layer images by parameters for effective times.

SSD-A-154 The ACS WMS must filter AI features for map layer images by data above a user-specified parameter value.

SSD-A-155 The ACS WMS must filter AI features for map layer images by data below a user-specified parameter value.

SSD-A-156 The ACS WMS must filter AI features for map layer images by data equal to a user-specified parameter value.

SSD-A-157 The ACS WMS must filter AI features for map layer images by data between two user-specified parameter values.

SSD-A-158 The ACS WMS must filter AI features for map layer images by altitude parameters.

SSD-A-159 The ACS WMS must provide AI feature information for features present at a specific map position upon request.

SSD-A-160 The ACS WMS must provide base map reference layers.

SSD-A-161 The ACS WMS must provide state boundary map layers.

SSD-A-162 ACS WMS layers must be configured using the OGC Styled Layer Descriptor (SLD) format, as defined in the OGC Styled Layer Descriptor Implementation Specification.

June 15, 2021 18

SSD-A-163 The ACS WMS must provide styling of layers and features using stored styling definitions.

SSD-A-164 The ACS WMS must provide a map legend on user request.

SSD-A-165 The ACS WMS must apply user-specified styles to AI feature imagery upon request.

SSD-A-166 The ACS WMS must advertise styling options for AI map imagery.

SSD-A-167 The ACS WMS must provide AI map layer imagery in the user-specified resolution requested.

SSD-A-168 The ACS WMS must use "nearest neighbor" as the default method of spatial interpolation. [see OpenGIS Web Map Service Implementation Specification, version 1.3.0, Annex C.4.3]

SSD-A-169 The ACS WMS must convert the positions of data from NAD83 coordinates to spherical earth models/datum coordinates as needed.

[see OpenGIS Web Map Service Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]

SSD-A-170 The ACS WMS must convert the positions of data from NAD83 coordinates to WGS84 earth models/datum coordinates as needed.

see [OpenGIS Web Map Service Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]

SSD-A-171 The ACS WMS must re-project the positions of data from parameterized Lambert Conformal coordinates to parameterized Cartesian coordinates upon request.

SSD-A-172 The ACS WMS must re-project the positions of data from parameterized Lambert Conformal coordinates to parameterized Latitude/Longitude map projection coordinates upon request.

SSD-A-173 The ACS WMS must re-project the positions of data from parameterized Lambert Conformal coordinates to parameterized Mercator map projection coordinates upon request.

SSD-A-174 The ACS WMS must re-project the positions of data from parameterized Lambert Conformal map projection coordinates to parameterized Lambert Azimuthal Equal- Area map projection coordinates upon request.

SSD-A-175 The ACS WMS must re-project the positions of data from parameterized Latitude/Longitude coordinates to parameterized Cartesian coordinates upon request.

SSD-A-176 The ACS WMS must use defined coordinate reference systems for re-projection transformations. [see OpenGIS Web Map Service Implementation Specification, version 1.3.0, Sections 7.3.3.5, 7.3.3.6, 7.3.5]

SSD-A-177 The ACS WMS must re-project a different parameterization of the Lambert Conformal map projection upon request. [see WCS Implementation Standard, version 1.1.2, Section 10.3.4]

SSD-A-178 The ACS WMS must re-project a different parameterization of the Cartesian Tile Matrix up request in accordance to [see OpenGIS Web Map Tile Service Implementation Specification, version 1.0.0, Sections 6.1, 7.1.1.1.2]

SSD-A-179 The ACS WMS must re-project a different parameterization of the Latitude/Longitude Tile Matrix up request in accordance to [see OpenGIS Web Map Tile Service Implementation Specification, version 1.0.0, Sections 6.1, 7.1.1.1.2]

June 15, 2021 19

SSD-A-180 The ACS must provide a service (ACS Web Map Tile Service (WMTS)) providing geo-referenced AI imagery on map tile images in accordance to the OGC Web Map Tile Service standard.

SSD-A-181 The ACS Web Map Tile Service must provide different map layers for different AI feature domains.

Note: For example, different layers for Airports, NAVAIDs, SAA, Sector Airspace.

SSD-A-182 The ACS WMTS must provide map tiles as a collection of tile matrices in accordance with WMTS [see OpenGIS Web Map Tile Service Implementation Specification, version 1.0.0, Sections 6.1, 7.1.1.1.2]

SSD-A-183 The ACS WMTS must provide map layer tiles with AI imagery filtered by user-specified layer name, TileMatrixSet, TileMatrix, and tile position [see OpenGIS Web Map Tile Service Implementation Standard version 1.0.0, Sections 7.2.2, 8.2]

SSD-A-184 The ACS WMTS must provide styling of layers and features on map tiles using stored styling definitions.

SSD-A-185 The ACS WMTS must advertise available tile matrix sets.

SSD-A-186 The ACS WMTS must maintain a cache of recently requested map tiles.

SSD-A-187 The ACS WMTS must use FAA standard symbology when representing AI features in map imagery.

Note: Refer to AeroNav Products Aeronautical Chart User's Guide.

SSD-A-188 The ACS WMTS must provide AI map imagery implementing the WGS84 SRS.

SSD-A-189 The ACS WMTS must provide AI map imagery implementing the NAD 83 SRS.

SSD-A-190 The ACS WMTS must advertise AI map layers available from the services.

SSD-A-191 The ACS mapping services must advertise supported coordinate reference systems for the mapping services.

SSD-A-192 The ACS WMTS must provide different map layers for different AI feature domains.

Note: For example, different layers for Airports, NAVAIDs, SAA, Sector Airspace.

SSD-A-193 The ACS WMTS must filter AI features for map layer images by one or more layer names.

SSD-A-194 The ACS WMTS must provide AI feature information for features present at a specific map position upon request.

SSD-A-195 The ACS WMTS must provide base map reference layers.

SSD-A-196 The ACS WMTS must provide state boundary map layers.

SSD-A-197 The ACS WMTS layers must be configured using the OGC SLD format, as defined in the OGC Styled Layer Descriptor Implementation Specification.

SSD-A-198 The ACS WMTS must provide styling of layers and features using stored styling definitions.

SSD-A-199 The ACS WMTS must provide a map legend on user request.

SSD-A-200 The ACS WMTS must apply user-specified styles to AI feature imagery upon request.

SSD-A-201 The ACS WMTS must advertise styling options for AI map imagery.

SSD-A-202 The ACS WMTS must provide AI map layer imagery in the user-specified resolution requested.

SSD-A-203 The ACS WMTS must use "nearest neighbor" as the default method of spatial interpolation. [see OpenGIS Web Map Service Implementation Specification, version 1.3.0, Annex C.4.3]

June 15, 2021 20

3.1.4.5 Airspace Conflict Detection

This section captures functional requirements for an ACS service to identify airspace conflicts with user-specified or user-defined airspaces.

SSD-A-204 The ACS must provide a service (Airspace Conflict Detection Service) that identifies airspace conflicts (i.e., overlaps between two features that are both spatial and temporal) between a user-specified airspace and other airspaces stored in the ACS.

SSD-A-205 The ACS Airspace Conflict Detection Service must identify airspace conflicts between a user-specified airspace in the ACS and other airspaces stored in the ACS.

SSD-A-206 The ACS Airspace Conflict Detection Service must identify airspace conflicts between a user-submitted airspace description and other airspaces stored in the ACS.

SSD-A-207 The ACS Airspace Conflict Detection Service must provide descriptions for the airspace conflicts that are identified.

SSD-A-208 The ACS Airspace Conflict Detection Service must limit airspace conflicts returned to the airspace stored in the ACS that match the user specified airspace type(s) filter.

Note: A user can submit an airspace to compare to the ACS airspaces, along with a filter limiting the response to only include specific types, such as SUAs, ATCAAs, or TFRs.

3.1.4.6 Post-Operations Metrics

This section captures functional requirements for an ACS service to allow users to define and run custom reports based on AI in the ACS.

SSD-A-209 The ACS must provide a web service for users to create AI metric report definitions.

SSD-A-210 The ACS must store user-created AI metric report definitions.

SSD-A-211 The ACS must provide a web service to query metric report definitions.

SSD-A-212 The ACS must provide a web service for users to update AI metric report definitions.

SSD-A-213 The ACS must restrict querying AI metric report definitions to users who are the AI metric report definition creator or system administrators.

SSD-A-214 The ACS must restrict updating AI metric report definitions to users who are the AI metric report definition creator or system administrators.

SSD-A-215 The ACS must provide a service that returns AI metric reports based on stored metric definitions and submitted user parameters on request.

SSD-A-216 The ACS must restrict processing AI metric reports to users who are the AI metric report definition creator or system administrators.

3.1.4.7 Geodetic Computations

This section captures functional requirements for an ACS service to perform different geodetic computations on user request.

June 15, 2021 21

SSD-A-217 The ACS must provide a service that computes one point of latitude and longitude from a user-specified starting point, forward azimuth, and distance.

Note: Known as Compute Forward in FAA COMPSYS 21 Geodetic Computations User Documentation v3.

SSD-A-218 The ACS must provide a service that computes the second rising or descending point of a segment from user-specified starting point, elevation, bearing, and distance.

Note: Known as Forwrd3D in the National Oceanic and Atmospheric Administration's (NOAA) National Geodetic Survey (NGS) Geodetic Tool Kit (https://geodesy.noaa.gov/TOOLS/index.shtml).

SSD-A-219 The ACS must provide a service that computes the true forward and backward azimuths and distance between two user-specified points on the surface of the earth.

Note: Known as Compute Inverse in FAA COMPSYS 21 Geodetic Computations User Documentation v3.

SSD-A-220 The ACS must provide a service that computes the forward and back azimuth and distance between two user-specified points and elevations.

Note: Known as Invers3D in the NOAA's National Geodetic Survey (NGS) Geodetic Tool Kit (https://geodesy.noaa.gov/TOOLS/index.shtml).

SSD-A-221 The ACS must provide a service that computes the intersecting point of two crossing segments.

Note: Known as Compute Bearing Bearing in FAA COMPSYS 21 Geodetic Computations User Documentation v3.

SSD-A-222 The ACS must provide a service that computes whether two segments intersect, plus the intersecting point if it exists.

Note: Known as Compute Segment Segment in FAA COMPSYS 21 Geodetic Computations User Documentation v3.

SSD-A-223 The ACS must provide a service that computes a point collinear with a user-specified segment at a user-specified distance from the first segment point in the direction of the second segment point, and whether the given distance is greater than the length of the segment.

Note: Known as Compute Segment Distance in FAA COMPSYS 21 Geodetic Computations User Documentation v3.

SSD-A-224 The ACS must provide a service that computes the shortest distance from a user-specified third point to a user-specified segment, and whether that shortest path is a) a segment perpendicular to the segment, b) a path to the first endpoint, or c) a path to the second endpoint Note: Known as Compute Point Segment in NASR.

SSD-A-225 The ACS must provide a service that provides the magnetic declination of a user-specified latitude, longitude, and date.

Note: Magnetic declination is the angle on the horizontal plane between the magnetic north and the true north at a particular location.

See similar functionality from NOAA's Magnetic Declination Calculator (https://www.ngdc.noaa.gov/geomag/calculators/magcalc.shtml).

Data and Information Requirements https://geodesy.noaa.gov/TOOLS/index.shtml https://geodesy.noaa.gov/TOOLS/index.shtml https://www.ngdc.noaa.gov/geomag/calculators/magcalc.shtml

June 15, 2021 22

This section captures requirements on the different types of data and AI the ACS receives and processes from other systems and authoritative sources.

SSD-A-226 The ACS must collect published NOTAM data from the authoritative source.

Note: Federal NOTAM System (FNS) is the authoritative source for NOTAM data.

SSD-A-227 The ACS must collect published Special Activity Airspace (SAA) NOTAM data from the authoritative…