FA8807 Mil Comm and Pnt Ssc/Cgk of Department of the Air Force posted this Sources Sought on Nov 19, 2026. Responses are due Dec 21, 2026. NAICS 517810 (All Other Telecommunications). Place of performance: Colorado 80916. Solicitation number FA8807-PATSOC-RFI-001.
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.
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.
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.
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
2. Mission Planning and Operations and SATCOM Service Delivery
3. Test, Evaluation, Discrepancy Resolution, and Transition to Operations
4. Technical Manuals, Training, TTPs, Dashboards, and Knowledge Management
5. External Coordination, Cybersecurity, and Community of Interest Support
6. Continuity of Operations
7. Geographic Support
8. Compliance, Independence, and Management Controls
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:
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:
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:
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.
The operating system for your proposal team - for federal and state contractors. Submit a polished proposal with minimal effort.
Plans from $129 a month, or $99 a month billed yearly.