FAA Request for Information (RFI) Alaska Automation Capability (AAC) Challenge Based

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the Alaska Automation Capability (AAC) Ch-BA opportunity.

• SVC-B Messaging: The AAC automation system must provide SVC-B messaging in accordance with FAA JO 7110.10, which includes routing through NADIN and using Flight Service Station identifiers. FAA JO 7110.10 contains the relevant formatting and examples.
• Organizational Conflict of Interest (OCI): The Government will not identify specific companies with OCI at this stage. Vendors are responsible for assessing and disclosing any potential OCI.
• NAS-IR-23040001 Version: The updated document, dated 3/26/25, should be used for compliance.
• AAC Electronic Flight Strips (EFS) Input Device: The FAA will collaborate with the vendor on specifications for input devices (e.g., touch screens or tablets) and will provide these as Government Furnished Equipment (GFE).
• Integrated Printers: The requirement is updated to state that the FAA will provide two GFE printers at each Alaska HUB FSS and one GFE printer at each Alaska Satellite FSS.
• Font Size for Submissions: The 12-point Times New Roman font requirement applies to narrative text. Smaller, legible fonts are permissible for tables and graphics. Font size 8 is not acceptable; 10-font or above is preferred. This requirement does not apply to screenshots and images.
• Experience References: Experience references may be included as an appendix and are excluded from the Concept Paper page limitation.
• Past Performance: The RFI does not request formal contract past performance write-ups, but rather product history and relevant experience descriptions. Any discussion of prior experience or product history counts towards the Technical Solution page limit, except for up to three Prior Experience References.

This Q&A clarifies requirements, specifies document versions, and provides guidance on submission formatting and content, which may impact proposal preparation and strategy.

Form / Attachment / Pricing Sheet

This document, "Interface Requirements Document (IRD) Operational and Supportability Implementation System (OASIS) to External Users," outlines the technical requirements for the interface between the OASIS and external users. It details the functional requirements, data types, and protocols for various interfaces.

• Scope: Defines the purpose of the IRD, which is to provide requirements for the interface between OASIS and external users.
• Applicable Documents: Lists government and non-government documents relevant to the IRD, including FAA specifications, standards, orders, and ICAO/NIST publications.
• Interface Requirements: Details general requirements, security requirements (ISS, Internet, Web Service, Non-FAA Connections, Personnel Security), OASIS required external interfaces, and data types (accepted and transmitted).
• Functional Requirements: Describes the functional requirements of OASIS interfaces, including General Services Requirements, APs and Message Requirements, and Protocol Implementation (Application Layer, Transport Layer, Naming and Addressing).
• Physical Requirements: Outlines electrical power and electronic requirements, connectors, wire/cable, grounding, fasteners, and electromagnetic compatibility.
• Quality Assurance Provisions: Details verification and validation processes, including responsibility for verification, special verification requirements, verification levels, and methods.
• Appendices: Includes detailed message formats for various interfaces (e.g., NMR, QALQ, INREQ, ALNOT, ICAO messages) and abbreviations/acronyms.

This document is crucial for any bidder looking to integrate with or provide services to the OASIS system. It specifies the technical standards, message formats, and protocols that must be adhered to, providing a detailed technical blueprint for system interoperability. Understanding these requirements is essential for developing compliant solutions and ensuring successful integration with the FAA's operational systems.

Request for Information (RFI) / Announcement

This announcement is a Challenge Based Acquisition (ChBA) seeking information from potential respondents regarding solutions to modernize the Alaska Flight Service Automation System (AAC). The goal is to replace the legacy Operational and Supportability Implementation System (OASIS) with a modern, web-based cloud automation system that meets current and future needs for safety and efficiency in the National Airspace System (NAS).

This is not a solicitation for proposals but a request for information. Respondents are asked to provide information on their capabilities, system capabilities, processes, and pricing models. The FAA is seeking innovative solutions for safety, efficiency, and innovation.

This announcement is not a Screening Information Request (SIR) or Request for Offers (RFO). Responses will not be construed as a commitment to contract. The FAA may choose to conduct communications with respondents.

• Phase 1: Concept Paper, Demonstration/Oral Presentation, Rough Order of Magnitude (ROM) Estimate
  • Concept Papers are due by 2 PM Eastern on April 20, 2026.
  • Submissions must adhere to specific formatting requirements (Microsoft Word, Excel, or Adobe Acrobat; 8.5x11 paper; 12 pitch font; specific margins; single-sided; sequentially numbered pages).
  • Key components of the Concept Paper include:
    • Cover Page
    • Minimum Organizational Requirements Table
    • Technical Solution (demonstrating functionality, prior experience, contribution to Alaska Flight Service, dependencies, and capabilities)
    • Business Model (cost-effectiveness, scalability, team structure, security controls, best practices, risk mitigation)
• Respondents who successfully complete Phase 1 will be invited to participate in Demonstrations/Oral Presentations within three weeks of notification.
• Phase 2: Prototype
  • Respondents invited to Phase 2 must demonstrate a prototype within four weeks of notification, covering functions such as Weather Products, Flight Planning, Data Recording, Search and Rescue, Maintenance, and FAA Order compliance.
• Phase 3: Follow-On Production Vehicle
  • Achieves Initial Operating Capability (IOC) no later than September 2027.

Not applicable for this RFI stage.

• Attachments contain Sensitive Security Information (SSI) and require agreement to terms and conditions for release by April 10, 2026, including signing an NDA, providing a Consolidated Employee Screening List, and a Business Declaration Form.
• The FAA is not responsible for any costs incurred in preparing or submitting a response.
• All submissions become Government property and will not be returned.
• The Contracting Officer (CO) is Helaina.K.Germosen@faa.gov.

Request for Information (RFI) / Announcement

This announcement is a Challenge Based Acquisition (ChBA) to seek information and innovative solutions for the Alaska Automation Capability (AAC). The AAC aims to modernize the Alaska Flight Service management system, replacing the legacy Operational and Supportability Implementation System (OASIS) with a modern, web-based cloud automation system. The focus is on solutions that enhance safety, efficiency, and innovation.

This is not a solicitation for offers, but an RFI to gather information on capabilities. Respondents are asked to provide:

• Offeror capabilities and system capabilities
• Processes
• Charging structures/pricing models for other customers

This announcement is not a commitment to contract. The FAA is not seeking or accepting unsolicited proposals. Costs incurred by respondents are at their own expense.

This is a phased acquisition. Phase 1 involves submitting a Concept Paper, followed by a Demonstration/Oral Presentation, and a Rough Order of Magnitude (ROM) estimate. Key deadlines:

• Concept Papers due: April 17, 2026
• Oral Presentations/ROM (if invited): within 3 weeks of notification
• Prototype Demonstration (Phase 2, if invited): within 4 weeks of notification
• Initial Operating Capability (IOC) target: September 2027

Not applicable for this RFI stage.

• The document references several attachments that provide detailed requirements, objectives, and policies, including a Statement of Objectives (SOO) and AAC Automation Requirements Document.
• Access to Sensitive Security Information (SSI) documents requires agreement to terms and conditions and submission of specific forms by April 10, 2026.
• Responses must be submitted via email to Helaina.K.Germosen@faa.gov by 2 PM Eastern on April 20, 2026.

Form / Attachment / Pricing Sheet

This document is a Non-Disclosure Agreement (NDA) and Non-Use Agreement required for potential bidders responding to the Federal Aviation Administration (FAA) Challenge Based Acquisition (ChBA) Announcement Number AAC-2026-ChBA, specifically for the procurement of the Alaska Automation Capability (AAC). It governs the use of export-controlled technical data provided by the FAA.

• Recipient Obligations: Bidders must agree to use the provided technical data solely for the purpose of responding to the AAC announcement.
• Pre-Approval: Recipients, subcontractors, and vendors must undergo a name check against the Department of Commerce's Consolidated Screening List to ensure they are not prohibited end users.
• Subcontractor/Vendor Requirements: Any subcontractors or vendors receiving the data must also execute a similar NDA/NUA and a Business Declaration Form.
• Export Control: Adherence to EAR99 marking is required, prohibiting export or re-export to specific countries or prohibited end-users without appropriate licenses.
• Data Destruction: Upon fulfillment of the agreement's purpose, the recipient must destroy all technical data received and certify destruction in writing to the FAA.
• Indemnification: The recipient agrees to indemnify the U.S. Government against liability arising from misuse or unauthorized disclosure of the data.
• Confidentiality Exceptions: Specific exceptions to confidentiality are outlined, including data already in the public domain or legally possessed by the recipient prior to receipt.

This NDA/NUA is a mandatory requirement for any bidder who will receive export-controlled technical data related to the AAC opportunity. Bidders must electronically sign and return this agreement, along with ensuring their subcontractors and vendors comply, before accessing such data. Failure to comply will prevent access to critical technical information necessary for proposal preparation.

Statement of Objectives (SOO)

This Statement of Objectives (SOO) defines the requirements for a web-based cloud solution for the Alaska Automation Capability (AAC) project, supporting Alaska flight services as part of the Department of Transportation's Brand New Air Traffic Control System (BNATCS).

The AAC project aims to modernize the existing Alaska Flight Service automation system into a web-based, cloud solution. This will provide upgraded technology enhancements for FAA Flight Service support to the Alaska general aviation community. The effort is part of a Challenge-Based Acquisition (ChBA) focused on speed, safety, efficiency, and innovation. The system will replace the legacy client automation application (OASIS) and provide:

• Consistent weather briefing and flight planning for Alaska general aviation pilots.
• Coordination for Search and Rescue (SAR) initiation and aircraft emergency activities.
• Aeronautical information services to Alaska pilots and air traffic controllers.
• Issuance of Notice to Airmen (NOTAMs). The project seeks to leverage new and emerging technologies.

The schedule outlines FAA goals for the ChBA, with anticipated milestones:

• 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 Work is anticipated at government and remote sites.

The overall objective is to design, develop, test, implement, and support a reliable web-based cloud automation system for FAA-specific AAC functions. Key objectives include:

• AAC Automation System Replacement

• AAC Automation System Deployment and OASIS Retirement

• Additional Baselined System Capabilities

• Respondents must consider specifications in Attachment 2 (AAC Automation Requirements Document) and Attachment 3 (FAA Orders and Policies).

• Solutions must align with FAA cybersecurity policies, including Zero Trust architecture.

• Performance will be measured by Service Availability, Service Continuity, Usability, and Schedule.

The Government will provide computers, monitors, and peripherals necessary to access the AAC web-based cloud solution.

Form / Attachment / Pricing Sheet

This document, "Alaska Automation Capability (AAC) Automation Requirements Document Version 1.2," outlines the functional and performance requirements for a new automation system intended to support flight services in Alaska. It serves as a baseline for understanding the government's capability needs for this acquisition.

• Functional Requirements: Details specific capabilities required for preflight services, inflight services, flight data/operational services (including Search and Rescue), and self-assisted services.
• Performance Requirements: Specifies system performance metrics, including acquisition rates for various data products, site peak loading, and concurrent transaction rates.
• Data and Information Requirements: Outlines needs for maintaining static data, prestored flight plans, pilot/aircraft information, and local knowledge.
• Integration Requirements: Addresses how the new system will integrate with existing FAA systems and external interfaces.
• Security and Safety Requirements: Details compliance with NIST standards and FAA orders for information systems security and system safety.
• Quality Management Requirements: Outlines quality assurance and configuration management standards.
• Test and Evaluation Requirements: Describes the necessary testing phases, including Development Testing, Site Acceptance Testing, and Operational Testing.
• In-Service Support and Management: Covers logistics, maintenance, training, and technical data requirements.

This document is crucial for potential bidders as it defines the comprehensive technical and performance specifications for the Alaska Automation Capability (AAC) system. Bidders must understand these requirements to propose a solution that meets the FAA's needs for modernizing flight services in Alaska. It details the scope of work, functional capabilities, performance expectations, and various compliance and operational standards that the proposed solution must adhere to.

Form / Attachment / Pricing Sheet

This document, "Attachment 4 - AAC Sites List," provides a comprehensive list of Federal Aviation Administration (FAA) facilities and Flight Service Stations (FSS) within Alaska (AAC). It details the locations, operational hours, contact information, and workstation counts for various FAA sites.

• FAA Facilities: Lists major FAA hubs with site type, location ID, hours of operation, contact person, phone number, and total workstation count.
• Satellite Flight Service Stations (FSS): Details individual FSS locations, including site type, hub connection, location ID, hours of operation, supervisor contact, phone number, and workstation count. This section covers numerous locations across Alaska such as Barrow, Cold Bay, Deadhorse, Dillingham, Homer, Kenai, Ketchikan, Kotzebue, McGrath, Nome, Northway, Palmer, Sitka, Talkeetna, and Iliamna.
• Other Alaska Locations: Includes a regional office in Anchorage.
• Additional FAA Locations: Lists facilities at William J. Hughes Technical Center in Atlantic City, NJ, and FAA Headquarters in Washington, D.C., with their respective contact information and workstation counts.

This list is crucial for bidders to understand the geographical distribution and operational presence of FAA facilities relevant to the opportunity. It may inform logistical planning, site visit requirements, or personnel deployment strategies. The detailed contact information and workstation counts can provide insights into the scale and operational capacity at each listed site.

Form / Attachment / Pricing Sheet

This document is an Excel spreadsheet containing a "Name Check" sheet for the Alaska Automation Capability (AAC) Challenge Based Acquisition (AAC-2026-ChBA). It is intended for use by prospective prime contractors and subcontractors to list company information and personnel for screening purposes.

• Company Name: Field for the prospective prime contractor or subcontractor's name.
• Company Point of Contact and Phone Number: Fields to provide contact information.
• Name: Column for the last name, first name of individuals to be screened.
• Organization: Column to specify the organization (Prospective Prime Contractor/Subcontractor).
• Country or Countries of Citizenship: Column to list the citizenship of the individual.
• United States Citizen?: Column to indicate 'YES' or 'NO' regarding US citizenship.
• For FAA Use Only: A designated section for Federal Aviation Administration use.

Bidders, particularly prime contractors, will need to complete this form by providing the requested information for their company and any subcontractors. This is a mandatory step for personnel screening as part of the acquisition process.

Form / Attachment / Pricing Sheet

This document is a "Business Declaration" form. It is used to collect information about a firm's ownership, business type, size, and demographic status for contracting purposes.

• Firm identification (Name, Address, Telephone, Tax ID)
• Contact person details
• Ownership and control information (including minority, female, and veteran status)
• Business type and years in operation
• Gross receipts for the past three years
• Small business, service-disabled veteran-owned small business, and socially/economically disadvantaged small business status
• Declaration of truthfulness and awareness of criminal prosecution for false statements.

Bidders will likely need to complete and submit this form as part of their proposal or registration. The information provided helps the government determine the firm's eligibility for certain contract set-asides and track small business participation.

Form / Attachment / Pricing Sheet

This document outlines the "Method of Evaluation" for the Phase 1 Challenge 1 of the announcement. It details how respondents' Concept Papers will be assessed and the criteria for advancing to Phase 1 Challenge 2.

• Evaluation Basis: Respondents' Concept Papers will be evaluated against three (3) criteria using a "Meets/Does Not Meet" rating.
• Phase 1 Eligibility: Respondents must "Meet" all three criteria to be eligible for Phase 1 Challenge 2. Failure to meet any criterion results in elimination.
• Criteria 1: Minimum Organizational Requirements Table: Respondents must answer "Yes" to all questions in this table, indicating existing capabilities or demonstrable delivery within the project timeline without material developmental risk. Unsupported assertions are insufficient.
• Criteria 2: Technical Solution: Evaluates the technical feasibility, operational viability, and commercial maturity of the proposed solution. This includes describing functionality, contribution to Alaska Flight Service, estimated AAC functions met, dependencies, additional capabilities, and current/envisioned cloud architecture.
• Criteria 3: Business Model: Assesses the proposed business model for cost-effectiveness, scalability, sustainability, and best value. It also covers team structure, personnel expertise, security control adherence, best practices, and risk mitigation.

This document is critical for bidders as it defines the specific requirements and evaluation standards for the initial phase of the acquisition. Understanding these criteria is essential for preparing a compliant and competitive Concept Paper. Failure to meet any of the outlined criteria will lead to disqualification from further stages of the competition.

Form / Attachment / Pricing Sheet

This document is a template for the Cover Page of a Concept Paper submission for the Alaska Automation Capability (AAC) opportunity. It provides a standardized format for bidders to submit essential information about their proposed project and organization.

• Notice ID: TBD

• Proposed Project Title: Placeholder for the respondent's title.

• Submittal Date: Placeholder for the submission date and time.

• Submitted By: Name of the prime entity.

• Team Members: Names of any subcontractor entities.

• SAM Unique Entity ID (UEI) & CAGE Code: For the prime entity.

• Proposed North American Industry Classification System (NAICS) Code: With a note to also provide this in Section L.2, AMS Provision 3.6.1-17.

• Prime Point of Contact (POC): Primary and Secondary contact details (Name, Position, Address, Phone, Email) for the prime respondent only.

• Signed: Field for digital signature.

• Bidders must format the table as needed (add/resize rows/columns).

• All italicized instructions highlighted in gray must be deleted and replaced with required content.

• The signed Cover Page is not included in the total page limit. No other cover page is permitted.

This template is crucial for bidders to correctly format and submit their initial concept paper. It ensures all required identifying and contact information is provided in a standardized manner, adhering to the government's specified format. Failure to use this template correctly may impact the submission.

Form / Attachment / Pricing Sheet

This document, "Attachment L.2 - Minimum Organizational Requirements Table," is a form designed to collect information from potential respondents regarding their organizational capabilities and experience relevant to the opportunity.

The table outlines several requirements and asks respondents to indicate "YES" or "NO" for each:

• Experience in specific aviation-related areas (e.g., cloud-based weather systems, flight plan filing, safety-critical operations, 24/7 time-sensitive alerts, commercial platform customization).
• Ability to provide 24/7 Help Desk support for Alaska Flight Service.
• Demonstrable understanding of Flight Service operations within the National Airspace System (NAS), including FAA policies and procedures.
• Readiness to meet with the Government within one month of Concept Paper submission for a capabilities presentation.
• Ability to meet AAC Automation Requirements and be operationally ready by September 2027 (Initial Operating Capability - IOC).

It also includes a certification statement and fields for the respondent's authorized representative to sign, name, title, and date.

This attachment is crucial for bidders to assess their eligibility and capability to meet the minimum organizational requirements set forth by the Government. Bidders must accurately complete this table to demonstrate their qualifications and commitment to the opportunity's operational timelines and technical demands.