Skip to content
FederalRFIOpen Federal notice

Protected Anti-Jam Tactical SATCOM (PATS) Operations Center (PATSOC) Mission Operations Services Request for Information (RFI)

Department of the Air Force› FA8807 MIL COMM AND PNT SSC/CGK Colorado

Solicitation # FA8807-PATSOC-RFI-001Updated Nov 19, 2026Scored Nov 21, 2026

Responses due

Dec 21

Dec 21, 2026, 10:00 AM EST

Posted Nov 19Due Dec 21

Summary by RFP Detector

What this RFP is about

Department of the Air Force (FA8807 MIL COMM AND PNT SSC/CGK), part of the Department of Defense, posted a request for information titled “Protected Anti-Jam Tactical SATCOM (PATS) Operations Center (PATSOC) Mission Operations Services Request for Information (RFI)” under solicitation number FA8807-PATSOC-RFI-001. It was posted on Nov 19, 2026. Responses are due Dec 21, 2026, 10:00 AM EST. It is classified under NAICS 517810 (All Other Telecommunications). No set-aside is listed. The place of performance is Colorado. The listed point of contact is Scott Lucas.

Key facts

Sector
Federal
Notice type
RFI
As posted: Sources Sought
PSC
Not stated
Place of performance
Colorado
ZIP 80916
Value
Not statedTypical award in this market ≈ $102.2K
Solicitation #
FA8807-PATSOC-RFI-001
Listing
Official federal notice

RFP Detector Score

Score breakdown

Every RFP starts at 50. Each factor adds or subtracts points compared with a typical RFP; unknown data counts as neutral.

Starts at 50

  • Value−7.6estimated

    No value published. Typical award is about $102K: the median of 93 Air Force contracts over $25K awarded in NAICS 517810, FY24–FY26.

  • Competition & access−6.9measured

    Full and open competition. The largest recipient took 39% of these dollars in FY24–FY26.

  • Issuer & market−2.3measured

    Air Force obligated $329M on NAICS 517810 across 206 contracts in FY24–FY26. 3 other notices from this office in the past 12 months.

  • Time & stage+5.4measured

    Sources sought (market research, not a bid): 30 days to respond (due Dec 21, 2026, 10:00 AM EST).

  • Clarity & completeness+5.5estimated

    Documents not listed, 2 named contacts with email and phone, 4,001-word description.

  • Freshness+9.0measured

    Posted yesterday.

50 + contributions = 53 (C, Fair)

Informational, not advice to bid or not bid. Score version 1.0.0, evaluated Nov 21, 2026.

Requirements & submission

Eligibility · Full and open competition

Full and open competition means the notice states no set-aside: any responsible business can respond, subject to the requirements in the notice.

Not stated in a form we could extract. See the official solicitation for requirements, evaluation criteria and submission steps.

From the official notice

Description

4,001 words

Section I: PTES Description & Background Protected Anti-Jam Tactical SATCOM (PATS) provides worldwide, beyond line of sight (BLOS), Anti-Jam, Low Probability of Intercept (LPI) communications to tactical warfighters in both benign and contested environments. PATS uses the Protected Tactical Waveform (PTW) to enable forward-deployed users and coalition/international partners to fill capability gaps for protected communications. PATS employs a military web-based planning and operations architecture and communications hubs to enable existing or new terminals with a PTW-capable modem. The PTW can be used on any PTW processed or non-processed wideband satellite communications platform, providing mission critical communications with varying levels of protection depending on the SATCOM environment, satellite system, and available resources. PTW supports high throughput in benign conditions and adapts automatically to reduced capacity in favor of increased robustness for contested environments such as jamming, terminal movement, and weather degradation. PTW also provides logical and cryptographic separation of user groups to maintain operational security. PATS will be implemented in phases aligned with Protected Tactical Enterprise Service (PTES) ground capabilities. PTES is the enabling ground component of PATS, providing operational planning, mission and network management, and hubs for PTW networks using Wideband Global SATCOM (WGS) and commercial transponded SATCOM systems. WGS PATS Phase capability provides PTW over WGS, and Commercial Satellite Communications (COMSATCOM) Phase increases flexibility and resiliency by supporting PTW over COMSATCOM. Protected Tactical Satellite (PTS) Phase adds PTW over PTS satellites for near-peer jamming protection. Section II: RFI Objective The purpose of this RFI is to understand industry capabilities, risks, staffing approaches, recommended contract structure, transition considerations, and relevant experience associated with delivering mission planning and mission operations described in this request. This Request for Information (RFI) is issued to identify and gather information from sources capable of providing full-spectrum staffing for the Protected Anti-Jam Tactical SATCOM (PATS) Operations Center (PATSOC). The Government seeks information regarding industry capability to establish, staff, train, manage, and sustain a cleared operational workforce supporting planning, provisioning, monitoring, management, cybersecurity coordination, operational reporting, and execution of PTW networks. Government anticipates utilizing contractor personnel to fulfill designated onsite operator positions for each phase of performance, as discussed in Section III, Table 1, below. The anticipated NAICS for this acquisition is 517810 and the size standard is $40,000,000.00. Small businesses and Government entities with existing contract vehicles are encouraged to respond to this request. Section III: RFI Scope The contractor shall be responsible for management oversight and for providing qualified and cleared personnel. The contractor shall conduct proficiency and recurring training, maintaining situational awareness of COI processes and procedures regarding mission planning and mission operations, updating training, technical manuals, TTPs, continuity planning, and any relevant material required to perform mission planning and mission operations accordingly. The contractor shall staff the PATSOC and conduct mission planning and mission operations using Government-provided MMS, NMS, KMS, PATS PVT, and associated applications, while interfacing with additional tools required to perform and support mission planning and mission operations. PATSOC personnel are expected to manage account administration, registrar functions, role-based access control enabling mission planning and mission operations. These functions will extend to the COI enabling the concept of operations. The contractor may support phases of the operational lifecycle, including pre-operational test preparation, IT&E/MOT&E support, discrepancy report and problem report resolution, regression testing, transition to CFC Trial Period operations, sustained operational execution, situational awareness reporting, Continuity of Operations preparation and execution, and transition to a future operations and maintenance construct. The Government anticipates that the phases of support described herein may be revised, restructured, or further subdivided based on industry responses to this RFI. Phase 1 PATSOC Pre-Mission Operations Establish PATSOC mission operations after PATSOC Site Acceptance and prior to the start of Integrated Test & Evaluation (IT&E). Provide M-F 8hr staffing to include but not limited to: planning and operations manager, mission planner, network controller, help desk, system and network administrator, registrar, cryptographic operator, database administrator, and training manager. Pre-Mission Operations positions may be reduced by the Government to a subset of position roles defined in the PTES System Concept and listed above. Pre-Mission Operations shall conduct initial preparation and support execution of IT&E, Multi-service Operational Test & Evaluation (MOT&E) and all other events related to test and evaluation of the PTES system. Pre-Mission Operations shall prepare for mission objectives defined in the PATS Concept of Operations (CONOPS), and the PTES Capability Development Document (CDD). The following summary is provided to clarify the focus of the anticipated Pre-Operations Mission Support phase. It is intended to help industry understand the type and scope of staffing the Government may require prior to the start of the IT&E evaluation of the PTES system. Beginning after PATSOC Site Acceptance and approximately 90 days prior to the IT&E dry-run event and continuing until the start of the CFC Trial Period. Provide sufficient staffing to support Monday – Friday 8 hours a day for IT&E and MOT&E test events, including dry runs, test community coordination, workspace familiarization, access readiness, and operational readiness preparation. Develop and submit a PATSOC Staffing Plan identifying proposed roles, responsibilities, and staffing quantities for the Pre-Operations Mission Support period. Operate, evaluate, and use the Mission Management System (MMS), PATS Planning Verification Tool (PVT), Network Management System (NMS), Key Management System (KMS) and associated applications for network/mission planning, product generation, monitoring, management, trouble ticket response, network management, account management, registrar functions, and COI situational awareness. Develop, maintain, and provide updates to the PATSOC training program, update technical manuals, develop and update Tactics, Techniques, and Procedures (TTPs), maintain shift logs, create and update shift changeover briefings, create and customize dashboards, and prepare trending data for official reports and for the COI. Perform registrar functions and PTES account management. Identify and document discrepancies, perform root cause analysis, support Discrepancy Review Board (DRB) prioritization and resolution, conduct regression testing, and support Government disposition planning. Support Government preparation and execution of transition to the CFC Trial Period and sustained operations. Phase 2 Interim Contract Support (ICS) PATSOC Mission Operations Provide sustained PATSOC mission operations staff starting two weeks prior to start of Combat Forces Command (CFC) Trial Period and continuing through Full Operational Capability (FOC) declaration or until terminated by the Government. Provide 24/7 operations floor staff to include but not limited to: planning and operations manager, mission planner, network controller, help desk, system and network administrator and registrar. Provide M-F 8hr support staff enabling both the PATSOC operations floor and the broad PATS Community of Interest (COI). Support staffing shall include but is not limited to: system and network administrator, registrar, cryptographic operator, help desk, database administrator, and training manager. Both 24/7 and M-F 8hr positions support the full spectrum of position roles and responsibilities as defined in the PTES System Concept, while employing mission objectives defined in the PATS CONOPS, and the PTES CDD. Roles and responsibilities will evolve as the PATS architecture evolves and is expanded over time. The PTES System Concept shall not be interpreted as a finite list of roles and responsibilities but shall be tailorable and modified as needed to ensure PATSOC mission success. The following summary is provided to clarify the focus of the anticipated Mission Operations phase. It is intended to help industry understand the type and scope of staffing the Government may require beginning two weeks prior to the start of the CFC Trial Period. Beginning two weeks prior to the start of the CFC Trial Period continuing through to OA, Initial Operational Capability (IOC) declaration, and leading up to FOC declaration. Update and submit a PATSOC Staffing Plan identifying updated staffing roles and quantities to support the Mission Operations period. Evaluate user requirements, conduct satellite resource coordination, perform post-allocation planning, assign cryptographic key material, package and distribute configuration files, support service activation. These activities will be referred to as mission planning in the remainder of this RFI. Monitor and troubleshoot PTES network elements remotely and direct Joint Hub site maintenance personnel to perform level 1 maintenance as needed to resolve issues with Joint Hubs. Coordinate and schedule depot level maintenance when level 1 maintenance can’t correct the issue. Contact the Boeing help desk (or Tobyhanna help desk after Depot activation) to resolve issues with PTES system/sub-systems. Maintain and track network elements status and metrics. Provide Help Desk support and trouble ticket response to users reporting issues with PATS networks to include planning, activating, maintaining, and communicating over the PATS Family of System architecture referred to as mission operations in the remainder of this RFI. Provide 24/7 operations floor staffing for roles necessary to support users as part of mission planning and mission operations. Provide 8/5 staffing as support staff for the operations floor and PATS COI. Staffing composition and quantity may fluctuate during this phase based on industry responses. Respondents should identify their ability to support staffing composition and quantity and describe any assumption, limitations, or dependencies that may affect onsite operations. Coordinating with the PATS COI as part of mission planning and mission operations to include but not limited to: Regional SATCOM Support Centers (RSSCs), Wideband Satellite Communications Operations Centers (WSOCs), DISA, Joint Hub sites, Key Loading and Initialization Facility, depot organizations, terminal managers, and operators to determine satellite operational state, sufficient beam coverages, status of networks, Defense Information Systems Agency (DISA) Department of Defense Information Network (DODIN) operational circuits, Joint Hub operations, sufficiency/accuracy of configuration files, and general terminal troubleshooting. Report on Operational Capability Assessment (OPSCAP) and System Capability Assessment (SYSCAP). Identify and document discrepancies, perform root cause analysis, support Discrepancy Review Board (DRB) prioritization and resolution, conduct regression testing, and support Government disposition planning. Develop and implement a Continuity of Operations (COOP) plan capable of supporting operations at a Government-designated CONUS location, including planning assumptions for up to 15 days of warm COOP activities per year. Test COOP capability by deploying to the Government-designated CONUS location annually for a period of time determined by the Government. Continuous training evolution, technical manual updates, TTP updates, dashboard customization, regression testing, problem report/discrepancy tracking, operational reporting, process improvement, and transition support to a future post-ICS operations and maintenance contract. Phase 3 Contractor Logistics Support (CLS) PATSOC Transition Mission Operations Provide sustained PATSOC mission operations post-FOC and until terminated by the Government or until the PATSOC transitions to an organic Government staffed operation. Provide 24/7 operations floor staff to include but not limited to: planning and operations manager, mission planner, network controller, help desk, system and network administrator and registrar. Provide M-F 8hr support staff enabling both the PATSOC operations floor and the broad PATS COI. Back-office staffing shall include but is not limited to: system and network administrator, registrar, cryptographic operator, help desk, database administrator, and training manager. Both 24/7 and M-F 8hr positions support the full spectrum of position roles and responsibilities as defined in the PTES System Concept, while employing mission objectives defined in the PATS CONOPS, and the PTES CDD. Roles and responsibilities will evolve as the PATS architecture evolves and is refined over time. The PTES System Concept shall not be interpreted as a finite list of roles and responsibilities but shall be tailorable and modified to ensure PATSOC mission success. The following summary is provided to clarify the focus of the anticipated Transition of Mission Operations phase. It is intended to help industry understand the type and scope of support the Government may require following FOC declaration and transition to organic Government operations of the PATSOC. Beginning following FOC declaration. Update and submit a PATSOC Staffing Plan identifying updated staffing roles and quantities to support the Mission Operations period. Describe your approach to knowledge transfer, workforce transition, documentation turnover, and reduced contractor staffing during Government assumption of mission operations responsibilities. All desired intent from phase 2 remains in effect beyond the time specification, staffing plan uniqueness, and transition responsibilities. Section IV: RFI Questions and Prompts Please provide a response that addresses your company’s ability to meet the areas of interest listed below. Where possible, cite relevant past performance, corporate experience, contract vehicles, labor categories, workforce assumptions, and anticipated risks. Responses should be specific to PATSOC mission operations and should avoid generic corporate capability statements. 1. Personnel, Staffing, and Workforce Readiness Describe your approach to recruiting, clearing, training, retaining, and replacing personnel who possess and can maintain a TS/SCI clearance and have the necessary skill sets to perform PATSOC mission planning and mission operations. Detail your experience providing personnel for roles specified in Table 1. Provide a representative staffing composition and quantity model for Pre-Operations Mission Support, including labor categories, quantities, role descriptions, assumptions, escalation paths, and ability to flex between 6:00 AM and 6:00 PM Mountain Time in alignment with test and other events. Assume no more than 4 operators are needed at any given time. Provide a representative staffing composition and quantity model for PATSOC Mission Operations, including 24-hour operations floor coverage, Monday through Friday support staff coverage, on-call support assumptions, response time recommendations. Assume no more than 40 operators are needed at any given time. Describe how your organization maintains personnel proficiency, certification records, shift continuity, and knowledge management in a classified mission operations environment. 2. Mission Planning and Operations and SATCOM Service Delivery Describe your experience operating or supporting military SATCOM systems, network operations centers, mission operations centers, satellite access authorization processes, tactical communications services, or equivalent operational service delivery functions. Describe your approach to receiving user requirements, planning required resources, requesting resources from a SATCOM provider, processing allocated resource notifications, conducting post-allocation planning, assigning key material, and packaging/distributing configuration files to hubs and terminal modems. Describe your approach to assisting users through the satellite resource request lifecycle, including the initial requests, resource authorization, quality control of mission configuration files, and mission adjudication actions. Describe your experience supporting cryptographic key management, registrar functions, account management, role-based access control, token and PIN management, and user onboarding for operational communities. Describe your approach to monitoring PATS networks, opening and responding to trouble tickets, distributing situational awareness information, and coordinating with external network operations or help desk organizations. Describe your experience integrating operational help desk ticketing systems with external DoW and contractor maintenance repositories to maintain end-to-end incident traceability and asset status. 3. Test, Evaluation, Discrepancy Resolution, and Transition to Operations Describe your experience supporting developmental testing, operational testing, dry-run events, formal test events, OA, and transition to operations. Explain your process for identifying, documenting, prioritizing, tracking, resolving, and reporting Discrepancy Reports (DRs) and other system or operational issues discovered during testing or operations. Describe your experience supporting root cause analysis, corrective action development, regression testing, and coordination with Government and contractor engineering teams. Describe how you would support the Government in preparing for and executing transition to the CFC Trial Period and sustained operations. Identify information, access, training, or Government-furnished resources needed to support transition readiness. 4. Technical Manuals, Training, TTPs, Dashboards, and Knowledge Management Describe your methodology for developing, maintaining, documenting, and implementing a PATSOC training program for operations floor and support staff personnel. The government will conduct initial training at the kickoff of this effort, after which the awardee will assume full responsibility for training management. Describe how you would evaluate technical manuals and training materials during test and operational use and provide recommended updates to maintain personnel proficiency. Describe your approach to developing, updating, controlling, delivering and maintaining TTPs for mission operations. Describe experience customizing operational dashboards , to maximize situational awareness, trouble ticket generation, anomalous behavior analysis, and reporting for the PATS COI. Describe your approach to maintaining shift logs, shift changeover briefings, operational metrics, and issue/status reporting. 5. External Coordination, Cybersecurity, and Community of Interest Support Describe your experience coordinating operations, operational reporting, cybersecurity operations, and incident response with external Government and mission partner organizations. Describe how your organization would coordinate with organizations such as DISA, gateway sites, depot support organizations, WSOCs, RSSCs, cybersecurity organizations, Government support agencies, terminal managers, terminal users, and other PATS COI stakeholders. Describe your experience collecting, reviewing, forwarding, and responding to system/security logs as part of overall security and cybersecurity operations. Describe how you would respond to a report of a compromised modem or modem authorization issues such as Key Loading and Initialization Facility (KLIF) anomalies. 6. Continuity of Operations Describe your experience developing, exercising, and executing COOP plans for 24-hour operations centers or equivalent mission-critical environments. Describe how personnel, mission execution, management functions, operational reporting, and support functions would continue at a Government-designated alternate Continental United States (CONUS) location. Describe cost estimating assumptions for COOP activities, including Joint Travel Regulation-based travel assumptions, per diem, duration, personnel coverage, and sustainment of up to 15 days of COOP activities per year and to support annual training of the COOP capability. 7. Geographic Support Confirm your ability to support work at a Government identified facility within 25 miles of Peterson Space Force Base, Colorado Springs, Colorado, and identify any workforce, facility, or commuting constraints. Confirm your ability to support work at a Government identified COOP location within CONUS for up to 15 contiguous or non-contiguous calendar days plus any annual training requirement of the COOP capability. 8. Compliance, Independence, and Management Controls Confirm your ability to comply with applicable federal, state, and local statutes, regulations, Presidential Executive Orders, and Environment, Safety & Occupational Health (ESOH) code applicable to PTES operations. Explain safeguards you would implement to ensure impartiality of PATSOC personnel involved in testing, including preventing transfer to contractor development roles or involvement in development activities, consistent with Title 10, United States Code, Section 4171. Describe your program management approach, including staffing plan development, schedule management, risk management, quality control, training records, status reporting, and Government interface management. Describe your approach to common support duties associated with working on a military installation and in a Sensitive Compartmented Information Facility (SCIF), including required training, escort duties, anti-terrorism/force protection responsibilities, and shared workspace responsibilities. Describe efficiencies, process improvements, automation opportunities, or contract structure recommendations that could reduce cost or improve mission support effectiveness. Describe your ability to adhere to all access, control, escort and other duties identified by Department of War (DoW) regulation, policy or instruction and any local facility responsibilities and duties associated with operations within the PATSOC facility. 9. Government-Furnished Resources, Documentation, and Information Gaps Government has identified manuals, documents, data, technical information, and other resources that are anticipated to be available to potential awardee(s). The Government seeks industry feedback regarding the adequacy of the anticipated documentation and information available to support successful performance. Respondents are requested to review the Government’s preliminary identification of available documentation and provide input on the following: Identify any additional documents, manuals, technical data, system information, procedures, or other resources necessary to successfully perform phases of support as outlined in section III. Describe any anticipated challenges, risks, assumptions, or limitations associated with documentation or information as identified as unavailable. Recommend alternative approaches or resources to mitigate the impact of unavailable documentation. Identify additional Government-furnished information, access, property, or support necessary to effectively perform phases of support as outlined in section III. Identify risk areas, assumptions, constraints, Government-furnished information needs, specified skill or certification required to fulfill identified positions, and recommend transition considerations to include in a Request for Proposal (RFP). Documents Available with Potential RFP (Not Provided for RFI Response): PATS Concept of Operations PTES System Concept PTES Capability Development Document PATS Manpower Estimate Report PTES MMS and PVT Mission Planning CONOPS PATSOC Training Manual PATSOC Technical Manual Section V: Requested Response Content In addition to responding to the questions in Section IV, respondents are requested to provide the following information to assist the Government in shaping a potential acquisition strategy and future RFP: Company name, address, UEI/CAGE code, business size, point of contact, and relevant contract vehicles. Summary of directly relevant past performance, including customer, contract number if releasable, period of performance, scope, staffing level, clearance level, and operational environment. Recommended labor categories, staffing quantities, skill qualifications, shift model, and assumptions for both Pre-Operations and Operations Mission Support. Recommended Government and contractor responsibility allocation, including Government-furnished information, access, facilities, systems, training inputs, and operational authorities. Key risks, dependencies, assumptions, long-lead staffing considerations, and recommended RFP clarifications. Any recommended alternate approaches, phasing strategies, contract type considerations, performance metrics, service-level agreements, or transition milestones. Identify any potential or actual Organizational Conflict of Interest (OCI) that would arise as a result of your organization’s response to this request. Provide recommendations on how to structure OCI mitigation plans and firewall strategies. Section VI: Industry Day, Response Format, Submittal Instructions, and Questions The Government may host an industry day at a future date. One-on-one meetings may be offered during an industry day event for the purpose of allowing interested vendors to clarify scope, identify risks, and discuss alternative approaches that may better support the Government’s mission need. One-on-one meetings may or may not be conducted outside of an industry day engagement, at the sole discretion of the Government. Response Format Responses shall be submitted as a white paper in PDF or Microsoft Word for Office 2007 or later compatible format, supplemented with Microsoft Word, Excel, PowerPoint, PDF, or JPG attachments, as necessary. Responses shall be prepared so that when printed, they meet the following requirements: 8.5 x 11 inch paper, single-spaced typed lines, 1-inch margins, and 12-point Times New Roman font. Tables may use 10-point font. Pictures, Illustrations such as tables, flowcharts, organizational charts, process charts, or other similar informational charts may be used. Respondents are responsible for ensuring the legibility of all tables, charts, etc., and should assume that printed or copied responses will be produced in black and white. The Government will not accept company literature or marketing materials in response to this notice. Responses that do not materially address the content of this RFI, including responses that only make inquiries or provide generic capability statements, will be disregarded. Responses shall not exceed fifteen (15) pages describing how their company’s products, technical expertise, or operational approach can produce and deliver the capabilities specified in this RFI. Response Classification All material provided in response to this notice shall be UNCLASSIFIED, non-confidential, and non-proprietary to the maximum extent practicable. Firms providing confidential or proprietary information shall separately and clearly identify and mark all confidential or proprietary information. The Government will take all necessary steps to protect and safeguard confidential or proprietary information that is clearly marked. Submittal POCs Responses shall be submitted electronically. Unclassified responses shall be submitted electronically to the points of contact listed below: Scott Lucas, Contracting Officer, at scott.lucas.1@spaceforce.mil Heather Ayres, Contract Specialist, at heather.ayres@spaceforce.mil William Chan, Contract Specialist, at william.chan.5@spaceforce.mil Submittal Due Date Responses are due by 10:00 AM Pacific Time on 21 December 2026. Questions and Communications All questions and communications associated with this RFI shall be submitted in writing to Scott Lucas, Contracting Officer, at scott.lucas.1@spaceforce.mil. Section VII: Disclaimers THIS IS A REQUEST FOR INFORMATION ONLY. This notice is issued solely for information and planning purposes. It does not constitute a solicitation, Request for Proposal, Request for Quotation, or promise to issue a solicitation in the future. This notice does not commit the Government to contract for any supply or service whatsoever. Furthermore, the Government is not, at this time, seeking proposals. Respondents are advised that the Government will not pay for any information or administrative costs incurred in response to this notice. The Government will not assume liability for costs incurred by any attendee for travel expenses or marketing efforts. All costs associated with responding to this notice will be solely at the responding party’s expense. Proprietary information, if any, should be kept to a minimum and shall be clearly marked. All submissions become Government property and will not be returned. To review RFI responses, proprietary information may be provided to Federally Funded Research and Development Center (FFRDC) and/or Advisory and Assistance Services (A&AS) contractors working for the Government. Non-Government support contractors and their subcontractors may be involved in the review of any responses submitted. Respondents should advise the listed Government points of contact in advance of response submission if they do not wish for their submission to be reviewed by non-Government support contractors and their subcontractors.

Documents

No documents are listed for this notice.

Contacts

2 contacts

Points of contact as published on the notice.

Timeline & history

  1. Sources Sought posted

  2. Responses dueNext · in 29 days

  3. Archive date on the official notice

Federal award history

Market context

Department of the Air Force · NAICS 517810 · FY24–FY26

Typical award (over $25K)
$102.2K
Contracts awarded
206
Total obligated
$328.7M
Award size, Department of the Air Force · NAICS 517810 contracts, FY24–FY26 (log scale)
P25 $6.3KMedian $18.5KP75 $90.8KP90 $318.9K

Largest recipients in this market

  • FIVE RIVERS ANALYTICS, LLC$126.8M39%
  • INDYNE, INC.$54.6M17%
  • SIERRA NEVADA COMPANY, LLC$33.7M10%

Recipients of past awards in this market, not the incumbent of this RFP.

View as table
Fiscal yearObligated ($)
FY20220
FY202312,875,953.08
FY202462,336,173.86
FY2025124,754,103.88
FY2026141,567,319.84

Federal contract award records, award types A–D, FY24–FY26. Updated Nov 15, 2026.

Similar open RFPs

Same NAICS group or Telecommunications & Networks, nearby first, ranked by score.

Excellent

FS Bldg T112 8 Sipr Drop Installation

Department of the Army · Fort Shafter, HI

FederalCombined synopsisSmall business set-asideIT & Software+1
Posted Nov 18Due Dec 8, 2026, 11:59 PM HST (in 17 days)Federal notice
Excellent

Dual IF Limiter- B52H

Department of the Air Force · Warner Robins, GA

FederalSolicitationSmall business set-asideSupplies, Equipment & Furniture+1
Posted Nov 17Due Dec 17, 2026, 4:30 PM MST (in 25 days)Federal notice

RFP Detector Scores are informational.How we score →

More from Department of the Air Force

759 open RFPs from this issuer and its offices.

Poor

FD2020

Department of the Air Force

FederalSpecial noticeSupplies, Equipment & Furniture
Posted Nov 22Due Nov 22, 2026 (in 23 h)Federal notice
Poor

FD2020

Department of the Air Force

FederalSpecial noticeSupplies, Equipment & Furniture
Posted Nov 22Due Nov 22, 2026 (in 23 h)Federal notice
Poor

L-39 Albatross Historic Static Display

Department of the Air Force · Joint Base MDL, NJ

FederalSources soughtEvents, Travel & Hospitality
Posted Nov 18Due Nov 23, 2026, 9:00 AM EST (in 32 h)Federal notice
Not competed

Intent to Sole Source- Military Freefall Currency Training Support

Department of the Air Force · Eloy, AZ

FederalSpecial noticeEducation & Training
Posted Nov 19Due Nov 23, 2026, 8:30 AM MST (in 33 h)Federal notice
Limited

AFIT/ENG-Cleanroom DI-RO Type I Ultra-Pure Water System

Department of the Air Force · Wright Patterson AFB, OH

FederalSources soughtTransportation, Fleet & Logistics
Posted Nov 5Due Nov 23, 2026, 11:00 AM EST (in 34 h)Federal notice
Poor

Upgrade X-Ray Controller

Department of the Air Force · Oklahoma

FederalSolicitationSupplies, Equipment & Furniture
Posted Oct 29Due Nov 23, 2026, 10:00 AM CST (in 34 h)Federal notice

RFP Detector Scores are informational.How we score →

About this notice

Official federal notice. Updated Nov 19, 2026.

Official solicitation:Sign in free to open the official solicitation

RFP Detector is an independent service and is not affiliated with any government agency. Scores are informational.

RFP Detector is not affiliated with the organization that issued this RFP. Always rely on the official notice and confirm every date and requirement with the issuer.