SAOC SPARR Request for Information (RFI).docx
DOCX document 56 KB Posted
- Solicitation number
- FA283426Q0003
About this file
This is a Request for Information (RFI) issued by the United States Air Force, Air Force Life Cycle Management Center (AFLCMC/WVSM) for the Survivable Airborne Operations Center (SAOC) Program Accelerated Risk Reduction initiative. The Air Force seeks information from interested contractors capable of supporting risk reduction activities in the Mission Systems branch of SAOC across three focus areas: Mission System Communications (radios, antennas), Mission System Infrastructure (networking, servers, audio/visual capabilities, encryption), and Mission System Software Development (applications, software pipelines, development and deployment environments). The RFI explicitly states this is for information and planning purposes only and does not constitute a commitment to issue an RFP, award a contract, or reimburse respondents for costs incurred. All submissions become Government property and will not be returned.
Interested parties must submit white papers by December 18, 2026 at 4:00 PM via email to the Contracting Officer, Capt. Landon Smith (landon.smith.13@us.af.mil). White papers must include Section 1 with administrative information (company contact details, recommended contracting strategy, business type, and facility security clearance) and Section 2 limited to 8 pages addressing experience in mission system infrastructure, communications, software development, system integration labs/operations, general engineering, and acquisitions. The Government requests specific examples of relevant experience, particularly in areas such as network design, DevSecOps practices, software deployment environments, radio integration, cloud-based development environments, NC3 systems compliance, and TS/SCI level work. Proprietary information must be clearly marked and minimized. Questions regarding the RFI must be submitted in writing by December 4, 2026 to the Contracting Officer and will be answered via www.sam.gov; verbal questions will not be accepted.
View the file
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
REQUEST FOR INFORMATION
Survivable Airborne Operations Center (SAOC) Program Accelerated Risk Reduction Nov 17th, 2026
1.0 Description
1.1 The United States Air Force, Air Force Life Cycle Management Center, AFLCMC/WVSM is seeking information from interested companies with the capability to support an effort to reduce risk in the Mission Systems branch of SAOC. The Program Management Office is looking to execute experimental activities, prototyping, analysis of alternatives, dual path solutions, and other innovative strategies to propel the current state of SAOC’s Mission Systems Engineering, Manufacturing, and Development (EMD) phase. These activities will cover three main focus areas: Mission System Communications (radios, antennas, etc), Mission System Infrastructure (networking, servers, audio/visual capabilities, encryption, etc), and Mission System Software Development (developing software applications, creating and utilizing software pipelines, creating and utilizing software development and deployment environments, etc.)
1.2 THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This Request For Information (RFI) is issued solely for information and planning purposes; it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. Further, the Air Force is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. If a solicitation is released, it will be synopsized on the www.sam.gov website. It is the responsibility of the potential offerors to monitor these sites for additional information pertaining to this requirement.
2.0 Background
The United States Air Force is seeking interested Contractors to help supplement on-going efforts to design, modify, and build the Mission System that will be on the SAOC Aircraft. The Mission System contains multiple types of radios ranging across various frequencies, antennas, servers, networking, workstations, multiple software applications, software pipelines, software delivery systems, Nuclear Command and Control (NC3) systems, encryption devices, modems, and more. This activity will be considered risk reduction to better posture the SAOC Program Management Office (PMO) for delivery of operational capabilities. These efforts will span across multiple classification levels, going up to Top Secret /Sensitive Compartmented Information (TS/SCI).
3.0 Work Description
3.1 The Contractor shall support analysis of the current state of SAOC Mission Systems and work with the PMO to identify potential acceleration solutions.
3.2 The Contractor shall perform risk reduction and prototyping activities for potential future implementation onto the SAOC Aircraft.
3.3 The Contractor shall support procurement and integration of hardware components, to include but not limited to: Radios, Antennas, Modems, Workstations, Network Infrastructure, Servers, Racks, Cross Domain Solutions, Audio and Visual Devices, Monitors, Power Controls, Encryptors.
3.4 The Contractor shall support software development, integration, and testing of Mission Systems applications, to include: Message Processing, Health and Status Monitoring, Radio Control Interfaces, Radio Performance Monitoring, Mission Planning Loading/Support, Timing Controls, System Controls, Wall Clock Controls, and Crypto Controls.
3.5 The Contractor shall support Software Development, Security, and Operations (DevSecOps) practices, to include: Building a software development pipeline, maintain and configuring a software development pipeline, assessing software code scans, managing artifact repos, setting software security standards, support Authority to Operate (ATO) and Certificate to Field (CtF) practices.
3.6 The Contractor shall support creating a software deployment environment for both staging and operational needs, to include: creating a software environment framework, establishing a platform for deployment (i.e. Kubernetes), maintain database structure and standards, standards for packaging completed software, identity and access management, observability implementation, and logging.
3.7 The Contractor shall support creating a software delivery pathway that can bring completed applications to the aircraft. This includes understanding the process from development labs, to test environment (System Integration Labs, etc.), to “staging” areas, and to the production destination (the Aircraft). This is commonly referred to as a Path to Production which includes the full lifecycle of requirements review, derivation, coding, test, integration, configuration management, and operational support on the fleet of aircraft.
3.8 The Contractor shall assess the SAOC requirements documents and suggest opportunities to meet the requirements as is with developed solutions or suggest alternative options to meet the requirements with Commercial Off the Shelf (COTS) or Modified COTS. The Contractor shall also suggest requirements changes to the Government as necessary if modifications would enable more options for solutions.
4.0 Requested Information
Interested parties are requested to respond to this RFI with a white paper addressing the following questions. If the question asks about related experience you possess, please provide specific examples. If the Contractor has recommendations for their approach to solving a certain question, please include that in your response.
4.1 Mission System Infrastructure
· Do you have experience producing network, compute and storage rack designs to host Mission System services and applications while producing backup and archival data management?
· Do you have experience working alongside Security Control Assessors (SCA) and Authorizing Officials (AO) to meet Risk Management Framework compliance for systems and networks?
· Do you have Cross Domain System (CDS) experience or experience working with the National Security Agency (NSA) /Air Force Cross-Domain Support Element (CDSE)?
· Do you have experience working with Nuclear Command, Control, and Communications (NC3) systems and NC3 compliance?
· Do you have experience with distributing network access and network access switching at localized Network Access Panels (NAPs)?
· Do you have experience with multiple networks and security domains accessing a single port, certifiable via Type-1 encryption, separation or other logical or physical separation solutions?
· Do you have experience building operational workstations?
· Do you have experience working alongside operational units to iterate on Human System Integration (HSI) designs and documenting workflows?
· Do you have experience working with Common Audio Access Devices (CAAD) that allow multiple independent levels of security?
· Do you have experience integrating multiple security domains and circuits onto a single end-user device?
· Describe your experience with Presidential National Voice Conference (PNVC).
· Describe your experience regarding the Chairman of the Joint Chief of Staff Instruction (CJCSI) Emergency Action Procedure (EAP) Vol VI conferencing and strategic conferencing.
· Does your company have experience with commercial Boeing 747-8 aircraft, to include existing wiring, power and cooling systems?
· Do you have experience with power management systems on airborne platforms?
· Do you have experience developing a strategy for aircraft power, mission system power and uninterruptable power supply (UPS) for a platform of flight and mission critical systems?
· Do you have experience with system, rack and Line Replaceable Unit temperature monitoring with services to manage and maintain temperature control?
· Do you have experience working with Classified Data at Rest (CDAR) or inline media encryption solutions?
· Do you have experience with both using or integrating Nuclear systems such as Defense Injection/Reception Emergency Action Message Command and Control Terminal (DIRECT LITE), Processing and Display Subsystem – Migration (PDS-M), Command & Control Battle Management Communications (C2BMC), or Nuclear Planning & Execution System (NPES)?
4.2. Communications
· Do you have experience procuring and integration complex radio systems into an aircraft platform?
· What experience do you have with the integrating with radios from Very Low Frequency (VLF) up to Extremely High Frequency? If so, please list the different radios and bands in which you have that experience.
· What experience do you have with Tier 2 Open Mission Systems (OMS) compliance for Radio Frequency (RF) systems?
· Do you have any experience with resilient comms and building multi-path data and voice connections?
· What experience do you have with commercial satellite communications (SATCOM) services use by the military?
· Do you have experience performing cosite analysis?
· Do you have experience in RF filtering?
· Describe your understanding of CM2 compliance, and highlight any work you have done in this area.
· Describe your experience with radio and encryption integration efforts.
· Do you have experience in comms management, route selection, and providing logical GUI integration?
· Do you have experience with assured comms and telephony services?
· Do you have experience with antenna system design, and testing?
· Do you have experience in centralizing crypto key filling?
4.3 Mission Systems Software
· Do you have experience developing software in an agile fashion alongside a Government Program Office?
· Has your company successfully deployed software to an operational environment? If so, please give specifics details to include how you achieved an Authority to Operate (ATO) or Certification to Field (CTF).
· Do you have experience working with OMS compliant Universal Command and Control Interface (UC) messages?
· Do you have experience interfacing software with an abstract service bus?
· Do you have experience developing federated applications that need to share data with one another?
· Do you have experience developing software that must be integrated with, and be able to control, hardware components?
· Do you have experience developing certifiable software that can be approved with and delivered to a weapon system?
· Do you have experience developing software that requires connecting multiple radio messages into one centralized software application?
· Do you have experience developing software that requires monitoring performance and health activities of aircraft systems?
· Do you have experience development map-related functionality that can show information such as aircraft position and route?
· Do you have experience developing and/or integrating chat functionality?
· What coding languages have you worked with before?
· Do you have experience creating software development environments?
· Do you have experience creating coding standards to apply throughout the lifecycle of a software project?
· Do you have experience architecting a full system solution starting with decomposition of a System Requirement Document (SRD)?
· Do you have experience with virtual machines that can be used to run multiple software applications?
· Do you have experience with virtualizing software applications?
· Do you have experience with creating logging systems that track application activities and security issues?
· Do you have experience developing and integrating Video Teleconferencing (VTC) software?
· What experience do you have with both creating and utilizing a DevSecOps Pipeline?
· Please list all the DevSecOps Pipeline tools you have worked with in the past and explain how you used them in various projects
· What experience do you have with assessing code scans and other reporting from a DSO Pipeline?
· What experience do you have with setting coding metrics and standards that get incorporated into a DSO Pipeline?
· Do you have experience building in IL5, IL6 and TS Cloud environments?
4.4 System Integration Labs / Operations
· Do you have development labs for integration testing?
· Do you have the ability to build a System Integration Lab, purposed both for Test & Evaluation (T&E) and sustainment / configuration management?
· Can you conduct Hardware-in-the-Loop (HIL), Software-in-the-Loop (SIL) testing for a variety of mission scenarios.
· Do you have experience building a training system to replicate an aircraft that can be used to train operators?
· Do you have experience building mission training systems that interoperate with government training systems?
· What training capabilities have you used to satisfy operational training?
· Do you have experience creating operational software deployment environments?
· Do you have experience supporting operations of deployed software?
· Do you have experience driving configuration management throughout the testing and deployment phases of programs?
4.6 General Engineering
· What experience do you have in building and managing cloud based IDE?
· Do you have experience managing requirements and with what tools?
· Do you have experience with Cameo, Jira, Jama, or other engineering tools?
· Do you have experience linking engineering tools to create a Digital Thread?
· Do you have experience creating engineering products that can be produced and/or integrated by a prime contractor? If so, please provide examples of working with a prime to support full production.
· Do you have experience working directly with USG PMOs to rapidly prototype engineering solutions with the goal to field?
· Do you have integration experience with large scale mission systems on commercial derivative aircraft?
· Do you have access to staffing that can support up to TS/SCI engineering activities?
· Do you have facility space at both the SECRET and TOP SECRET/SCI Level that could be leveraged immediately to support this effort?
4.7 Acquisitions
· Is your company currently in any easily accessible GSA IDIQs? If so, please list them
· What is your company’s North American Industry Classification System (NAICS) code?
· How many employees does your company have? Do you qualify as a small business?
· What is the largest acquisition that your company has handled?
· Does your company have a successful history of Department of War (DoW) work based on previous Contractor Performance Assessment Reports (CPARs)?
· What experience do you have with Acquisition Category (ACAT) I programs?
5.0 Responses
5.1 Interested parties are requested to respond to this RFI with a white paper.
5.2 White papers in Microsoft Word compatible format are due no later than December 18th, 2026 at 4:00 PM and shall be submitted via e-mail only to the Contracting Officer; Capt. Landon Smith, landon.smith.13@us.af.mil.
5.3 Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned. Results will be reviewed and retained by the government and Government support contractors. Solicitation does not obligate the government to issue an RFP or award a contract. Responses must be at responders expense.
5.4 Section 1 of the white paper shall provide administrative information, and shall include the following as a minimum:
5.4.1 Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, and e-mail of designated point of contact.
5.4.2 Recommended contracting strategy.
5.4.3 Business type (large business, small business, small-disadvantaged business, 8(a)- certified small-disadvantaged business, HUBZone small business, woman-owned small business, very small business, veteran-owned small business, service-disabled veteran-owned small business) based upon North American Industry Classification System (NAICS). “Small business concern” means a concern, including its affiliates, which is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria and size standards in 13 CFR part 121.
Please refer to Federal Acquisition Regulation RFO 19 for detailed information on Small Business Size Standards. The RFO is available at https://www.acquisition.gov/far-overhaul/far-part-deviation-guide
5.4.4 The facility security clearance of the offeror.
5.5 The number of pages in Section 1 of the white paper shall not be included in the 8-page limitation, which applies only to Section 2 of the white paper.
5.6 Section 2 of the white paper shall answer the issues addressed in Sections 3 and 4 of this RFI and shall be limited to 8 pages of text (excluding pictures and graphs).
6.0 Questions
Questions regarding this announcement shall be submitted in writing by e-mail to the Contracting Officer, Capt. Landon Smith, landon.smith.13@us.af.mil. Verbal questions will NOT be accepted. Questions will be answered by posting answers to the www.sam.gov website; accordingly, questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions received after 4 December 2026 will be answered. To access the website, go to www.sam.gov. Interested parties are invited to subscribe to the website to ensure they receive any important information updates connected with this RFI.
7.0 Summary
THIS IS A REQUEST FOR INFORMATION (RFI) ONLY to identify sources that can provide the capability to deliver an IDE and DSO Pipeline. The information provided in the RFI is subject to change and is not binding on the Government. The Air Force has not made a commitment to procure any services discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.
File details come from the government source that posted it. Updated .