Attachment 1 - AAC Statement of Objectives.pdf
PDF 228 KB Posted
- Solicitation number
- 693KA7-26-RFI_AACCB
About this file
This is a Statement of Objectives (SOO) for the Alaska Automation Capability (AAC) project issued by the Federal Aviation Administration (FAA), dated March 16, 2026, Version 1.0. The document outlines the FAA's requirements for modernizing Alaska Flight Service operations through a Challenge-Based Acquisition (ChBA) approach. The primary objective is to replace the legacy Operational and Supportability Implementation System (OASIS) with a modern, web-based cloud solution that will serve all Alaska Flight Service Stations (FSSs). The solution must support core flight service functions including pilot briefings, flight plan management, inflight advisory services, search and rescue initiation, aircraft emergency response, and Notice to Airmen (NOTAM) issuance.
The project is structured in multiple phases with anticipated milestones spanning Q3 FY26 through Q4 FY27, including concept papers, demonstrations, prototype development, and initial operating capability. Three core objectives guide the effort: AAC Automation System Replacement, AAC Automation System Deployment (including OASIS retirement), and development of Additional Baselined System Capabilities. The solution must meet fourteen technical objectives encompassing software development processes, system design and deployment, interface integration, user training and support, cutover planning, and leveraging emerging technologies. The contractor must comply with FAA cybersecurity policies including Zero Trust architecture principles, align with FAA Enterprise Architecture, and meet performance measures for service availability, service continuity, usability, and schedule. Work will be performed at both government sites and remote locations to be finalized upon production award, with the government furnishing required computers, monitors, and peripherals for system access.
View the file
Other files
Show all 13
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
United States Department of Transportation
Federal Aviation Administration
Alaska Automation Capability (AAC)
Statement of Objectives (SOO)
Version 1.0
Date: March 16, 2026
Revision History for AAC Statement of Objectives (SOO)
Revision # Description Document Date
1 Draft Statement of Objectives - AAC 3/16/2026
1.0 INTRODUCTION
This Statement of Objectives (SOO) defines the Respondent requirements to provide a web-based cloud solution for the Alaska Automation Capability (AAC) project in support of Alaska flight services as part of the Department of Transportation (DOT) Brand New Air Traffic Control System
(BNATCS).
1.1 Background
The Federal Aviation Administration (FAA) Flight Service primary role is to provide weather data, aeronautical information, and flight planning services to pilots. The FAA provides flight services to pilots through:
a. Direct contact, by phone or radio, with a Certified Professional Controller (hereafter referred to as CPC) who translates weather and aeronautical data into critical and comprehensible information tailored for a particular flight.
b. Online web portal providing Pilots access to weather and aeronautical data and the ability to file, activate, and close flight plans without speaking to a CPC.
Flight Service also supports disaster relief, medical evacuations, weather and traffic reporting, and business and personal travel to thousands of airports and landing areas. Military, law enforcement, commercial, corporate, Customs and Border Protection, and air taxi operators also benefit from services provided by Flight Service. Most users of un-controlled airspace are customers of Flight
Service.
1.2 Purpose
The SOO details the FAA's goals and expectations for the modernization of the AAC automation system. The AAC effort will provide the means to modernize the existing or legacy
Alaska Flight Service automation system to a web-based, cloud solution that provides upgraded technology enhancements to how FAA Flight Service provides support to the Alaska general aviation community. This SOO is issued as part of a Challenge-Based Acquisition (ChBA) focused on evaluating solutions for speed, safety, efficiency, and innovation.
The FAA faces a rapidly growing, complex, and demanding aviation sector, with commercial air travel returning to pre-COVID levels. In addition, there are new entrants in the National
Airspace System (NAS), including drones, advanced air mobility, and commercial space. The air traffic control system is based on outdated technologies that are unable to meet these demands. The system is showing its age, which leads to delays and inefficiencies.
This ChBA for AAC seeks to transform Alaska Flight Service from its legacy client automation application system (referred to herein as the Operational and Supportability Implementation
System-OASIS) to a modern, web-based system capable of meeting the demands of today and the future. The FAA plans to implement a new state-of-the-art automation system that will enhance the safety and efficiency of the Alaska airspace supported by FAA Flight Service.
1.3 Scope
AAC will address legacy Alaska Flight Service automation shortfalls while leveraging best practices and new technology to provide the Agency with a level of flexibility through a modernized web-based cloud system that is not currently available in the existing legacy system. Additionally, stakeholder-desired features and functionalities that are costly and time consuming to develop in the legacy system will be realized through this approach and allow for future growth and technological advances. The ultimate goal is to fully replace the legacy
AAC automation solution as part of the BNATCS effort.
AAC will provide a foundation for efforts to achieve Flight Service goals such as:
a. Provide consistent weather briefing and flight planning for Alaska general aviation pilots.
b. Coordinate Search and Rescue (SAR) initiation and aircraft emergency activities.
c. Provide aeronautical information services to Alaska pilots and air traffic controllers.
d. Issue Notice to Airmen (NOTAM) providing essential information relating to the abnormal status of a component of the NAS.
Additionally, AAC seeks to leverage new and emerging technologies, where applicable, to meet the FAA’s requirements.
2.0 PERIOD OF PERFORMANCE
The schedule below represents the FAA goals for this ChBA with resulting production award.
Through this process, an integrated schedule that demonstrates deliveries in support of the
Agency’s goals will be developed.
Identified opportunities and risks associated with accelerating the AAC automation system deployment prior to the respective project completion dates are preferred by the FAA.
Milestone Activity1 Anticipated
Schedule
Phase 1 Challenge 1 - Concept Papers Q3 FY26
Phase 1 Challenge 2 - Demonstration/Oral Presentations Q3 FY26
Phase 2 - Challenge - Prototype Q3 FY26
Phase 3 - Follow-on Production Vehicle Q4 FY26
Initial Operating Capability (IOC) Q4 FY27
The FAA anticipates work to be performed at both government-site and remote locations; to be finalized upon production award. See Attachment 4, AAC Sites List.
1 All milestones are target objectives with preference for acceleration supported by realistic risk mitigation.
3.0 PERFORMANCE OBJECTIVES
The overall performance objective of this SOO is to design, develop, test, implement, and support a solution that provides a reliable web-based cloud automation system to sustain FAA- specific
AAC functions. Through Phases 2 and 3 the FAA will engage with participant(s) on the terms and conditions of a production award. The FAA is not restricting flexibility in all elements of business approaches or methods of delivery and deliverables if the conditions comply with applicable laws and regulations and the product best satisfies the FAA’s performance requirements and goals.
3.1 Core Objectives
The solution will leverage new technologies and approaches to software development and deployment to further enhance and accelerate the delivery of modern AAC automation capabilities. AAC will employ a new web-based cloud platform that will align with Agency goals and evolutions in the FAA Enterprise Architecture and infrastructure. The new architecture and infrastructure will allow Flight Service activities to scale to projected Alaska air traffic growth.
With an architecture designed for flexibility and extensibility, AAC will provide a foundation for future Alaska Flight Service capabilities that will leverage new technologies and operate in a more modernized, interconnected operational and technical environment. In achieving this, AAC will address shortfalls in legacy Flight Service systems related to the current inability of its architecture and hardware to support long-desired, advanced technological features and functions. The new system will execute, at a minimum, the recommendations and enhancements as identified by the
Flight Service Program Office (PO).
The three (3) core objectives to meet AAC requirements include:
a. AAC Automation System Replacement
b. AAC Automation System Deployment/OASIS Retirement
c. Additional Baselined System Capabilities
3.1.1 Core Objective 1 – AAC Automation System Replacement
For AAC, the web-based cloud solution will be deployed and will replace the legacy Alaska Flight Service application across all Alaska Flight Service Stations
(FSSs). The automation system will be accessible via the internet on the NAS network requiring an integration and deployment plan across all FSSs. The FAA's priority during this step is schedule acceleration.
3.1.2 Core Objective 2 – AAC Automation System Deployment (OASIS Retirement)
For AAC, the web-based cloud solution will be deployed and assume all Alaska flight service functions, including pilot briefings, flight plans, inflight advisory services, search and rescue initiation, aircraft emergencies and NOTAM. The legacy OASIS application will be retired across all Alaska FSSs.
3.1.3 Core Objective 3 – Additional Baselined System Capabilities This third objective, subject to change based on advances in technology, will usher in the development and implementation of enhanced capabilities across Flight Service functional areas. AAC seeks to integrate new and emerging technologies, where applicable, to meet the Agency's requirements and standardize the services provided in
Alaska, leveraging technological advancements to improve air traffic services for general aviation pilots. Additional capabilities will be prioritized based on operational value, enterprise alignment, and technical feasibility.
3.2 Technical Objectives
To meet the overall requirements of this SOO, the Respondent's solution must execute the technical objectives identified in the table below:
Core
Objective#
Technical
Objective
Technical Objective Description
1 Define software development and testing processes that conform to modern industry standards and FAA guidance.
2 Design, develop, test, and support Flight Service and cloud supporting services via a new automation platform.
3 Design, develop, test, and support AAC interfaces.
4 Deploy automation system across all Alaska Flight Service
Stations, with access to AAC services through a web-based, cloud architecture, based on operational requirements.
5 Describe testing and training environment for AAC Users.
6 Develop and conduct training for AAC Users.
7 Describe customer and site support for AAC Users.
8 Describe cutover process from OASIS to AAC.
10 Describe cutover process from OASIS to AAC.
11 Deploy automation system across all Alaska Flight Service
Stations, with access to AAC services through a web-based, cloud architecture, based on operational requirements.
12 Update training and customer support documentation to address
AAC capabilities.
13 Update and maintain modernized automation web solution.
14 Leverage new and emerging technologies to meet the FAA requirements.
C o re
O b je ct iv e
A A
C u to m at io n S y st em
R ep la ce m en t
C o re O b je ct iv e
A
C u to m at io n S y st em
D ep lo y m en t (O
A S
IS
R et ir em en t)
4.0 CONSTRAINTS AND REQUIREMENTS
4.1 Operating Constraints
Operating constraints will be determined upon production award.
4.2 Technical Requirements Documents
When working on its solution, the Respondent must take into consideration the specifications identified in the following documents found in the Attachments:
a. Attachment 2, AAC Automation Requirements Document*
b. Attachment 3, FAA Orders and Policies*
Those documents identified with an * contain system, service, or policy requirements.
4.3 Security Constraints
The Respondent’s solution must demonstrate alignment with FAA cybersecurity policies, including Zero Trust architecture principles and applicable cloud authorization requirements.
The Respondent must comply with all applicable security regulations, directives, and requirements throughout the entire performance of the production award. Additionally, the
Respondent must perform the requirements of the production award in a manner that aligns with evolving security industry best practices.
5.0 PERFORMANCE MEASURES
The following performance measures will inform the determination of whether the identified objectives are met successfully:
a. Service Availability
b. Service Continuity
c. Usability
d. Schedule
Additional performance measures may be developed and included prior to production award.
Previously approved performance measures may be adjusted during the period of performance.
6.0 GOVERNMENT-FURNISHED ITEMS (GFI)
The Government will furnish required computers, monitors, and peripherals necessary to access the
AAC web-based cloud solution.
7.0 ACRONYMS
Acronym Definition
AAC Alaska Automation Capability
BNATCS Brand New Air Traffic Control System
ChBA Challenge-Based Acquisition
CPC Certified Professional Controller
DOT Department of Transportation
FAA Federal Aviation Administration
FSS Flight Service Station
GFI Government Furnished Items
NAS National Airspace System
NOTAM Notice to Airmen
OASIS Operational and Supportability Implementation System
PO Program Office
SAR Search and Rescue
SOO Statement of Objectives
File details come from the government source that posted it. Updated .