Q and A MGEO RFI_2.xlsx
XLSX spreadsheet 16 KB Posted
- Attached to
- Maneuverable Geosynchronous Orbit (MGEO) Commercial Satellite-Based Services Request for Information (RFI) /Sources Sought Federal contract opportunity
- Solicitation number
- FA2541-25-015
- Issued by
- Department of the Air Force
About this file
This document is a Questions and Answers (Q&A) file for the Maneuverable Geosynchronous Orbit (MGEO) Commercial Satellite-Based Services Request for Information (RFI) issued by the Department of the Air Force. The RFI seeks to establish a contract vehicle for worldwide commercial satellite communication (COMSATCOM) services utilizing geosynchronous (GEO) orbit satellites with unique resilience capabilities, including maneuverability and dispersed satellite configurations.
Key details include a targeted early January 2026 release date for the official Request for Proposal (RFP), with no current timeline for subsequent task order competitions. The government is considering a teaming day or providing a list of RFI respondents to facilitate industry engagement. The Q&A addresses technical nuances such as satellite repositioning, transmission paths, security requirements, and operational capabilities. Respondents raised questions about corporate experience substitution, response page limits, and the scope of tasks across functional areas. The contract aims to provide flexible, resilient satellite communication services supporting U.S. military and partner communication needs worldwide, with a focus on GEO orbital domain and unconventional service resilience.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Q and A MGEO RFI_2 (09 Oct 25 Update).xlsx | XLSX spreadsheet | |
| Q and A MGEO RFI_2 (09 Oct 25 Update).pdf | ||
| Q and A MGEO RFI_2.pdf | ||
| RFI Comment Matrix.xlsx | XLSX spreadsheet | |
| MGEO_PWS_20250822.docx | DOCX document | |
| FA1 Eval Factor_20250825.docx | DOCX document | |
| FA2 Eval Factor_20250825.docx | DOCX document | |
| MGEO_RFI2_Letter_Signed.pdf | ||
| FA3 Eval Factor_20250825.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Q&A
| Question # | Document Title | Document Ref | Question | Answer | ||
| 1 | N/A | N/A | The Response Guidelines stipulate a maximum of 10 page response. Are the CRM included in the 10 pages? | The CRM does not count towards the 10 page response limit, however the CRM should not be utilized to provide multiple paragraph responses. Each referenced point in the CRM should be limited to a few sentences at most. | ||
| 2 | PWS | 1.3 | Will the government expand the section in the PWS (beyond what’s in section 1.3 Scope) on the Government requesting access to traditional sized satellites that are reaching end-of-life or are inclined but could be repositioned and leased by the Government. | The Government does not intend to expand this section. The scope of the MA/IDIQ will provide a path for actions that allow access to EOL and inclined satellites. The Government currently believes that taking advantage of those capabilities are already covered in the stated tasks. If Quantum disagrees, we welcome additional info to consider on this topic. | ||
| 3 | FA1 | Functional Area 1, Subfactor 1 | Can Corporate Experience be substituted with Team Experience? | The Government would need additional information on what Team Experience would include and how it would demonstrate the ability to meet the needs of the functional area. Please provide additional information so that the Government can consider this option. | ||
| 4 | FA2 | Functional Area 2, Subfactor 1 | Can Corporate Experience be substituted with Team Experience? | The Government would need additional information on what Team Experience would include and how it would demonstrate the ability to meet the needs of the functional area. Please provide additional information so that the Government can consider this option. | ||
| 5 | FA3 | Functional Area 3, Subfactor 3 | Can Relevant Experience be substituted for Past and/or Planned Activities? | The Government will take this recommendation under advisory and discuss internally how to best allow for relevant experience in response to an official RFP. The Government acknowledges that benefit of this possibility. | ||
| 6 | N/A | N/A | Please identify the related Program Element numbers associated with the anticipated IDIQ. | No PE numbers are available at this time. PE numbers will be established when funded task orders are generated with mission partners. | ||
| 7 | N/A | N/A | Will there be a Briefing to Industry prior to release of the final solicitation? | While this is undetermined, the Government does not currently have a briefing to industry planned. If you believe a briefing to industry would be beneficial to industry respondents, please elaborate in your response. | ||
| 8 | N/A | N/A | In order to plan our proposal and staffing resources, please provide a notional timeline for the initial IDIQ solicitation, as well as the planning for the associated TO/DO competitions and awards. | At this time, the Government is targetting an early January 2026 release date for this official RFP. There is no timeline available for any TO/DO competitions. | ||
| 9 | N/A | N/A | Will there be a listing of other interested companies involved, so as to facilitate teaming/partnering discussions? | The Government has considered hosting a teaming day, however if this is unable to be met in the time avaialble, the Government will consider providing a listing of all MGEO RFI respondents to facilitate inter-industry engagement. | ||
| 10 | N/A | N/A | Who is the SSA/MDA for this initiative? | The Government does not share this infomration. | ||
| 11 | PWS | Entirety /Also see RFI Questions Context/Background/Observations | Can the Government more clearly delineate or categorize which specific tasks discussed in the PWS the Government views as being executed across all subsequent Task Orders awarded to the various firms on the basic IDIQ? Additionally, which specific tasks will the government execute on an individual task order basis? | The Government will take the suggestion to restructure the PWS to align each specific PWS task with its respective functional area, but does not not guarnatee a restrucutre. Specific tasks for individual task orders will be based on the requirement of the funding mission partner and their end goal. | ||
| 12 | PWS | Entirety / Also see RFI Questions Context/Background/Observations | In order to “maneuver communications” or “maneuver networks,” a great many tasks and coordination activities are required, either a priori or concurrent with the maneuver itself. In almost all cases, as with maneuvering, the various requisite tasks can require days to months to complete. The PWS addresses the aspect of repositioning spacecraft but is not as clear regarding associated tasks. Such associated tasks include obtaining ITU approval to radiate in a geosynchronous orbital slot; coordination with adjacent satellites and their operators; obtaining appropriate host nation approval and landing rights; establishing supporting ground infrastructure (e.g., appropriate TT&C facilities and communications/networking ground entry points, a.k.a., “teleports”), validating security (e.g., physical and cyber) and establishing secured terrestrial connectivity to a Point of Presence connected to terrestrial portions of the DoD Information Network (DoDIN). Shouldn’t the full range of tasks and capabilities required to enable resilient satellite communications support to U.S. warfighter and the networks which support them be addressed within the scope of the draft RFP? | See tab "Q2". The Government will add explicit language surround ITU, repositioning, host nation, ground, infastucture, TT&C etc. at the task order level. | ||
| 13 | PWS | SECTION I, Sect 1.3, Scope, 2nd para; Sect 1.3, sole para; Sect 2.1 (Task 1) sole para; Sect 2.2 (Task 2) sole para; Sect 2.5 (Task 5), paras 2.5.1 and 2.5.1.1; Sect 2.7 (Task 7) first para / Also see RFI Questions Context/Background/Observations | Will the capability to move services between fixed satellites in different orbital slots (a.k.a., “maneuverable networks," “spectrum maneuverability,” or “portability") also considered maneuver? | This has been considered by the Government, however a final determination has not been made on inclusion. The Government fails to see how this is different from porting requirements for capacity and services as required in standard COMSATCOM contracts. The Government is open to additional information should you wish to provide more detail in your response. | ||
| 14 | PWS | SECTION I, Sect 1.3, 3rd para | This paragraph includes the statement that, “The scope of this contract is limited by the intended orbital domain (GEO) and goal of resiliency through maneuverability and use of multiple transmission paths.” What is the difference between maneuverability and multiple transmission paths? | Maneuverability is the physical aspect of moving a spacecraft from one location to another in the GEO plane, whereas multiple transmission paths include the use of satellite and terrestrial paths to get a signal to the necessary end point. | ||
| 15 | PWS | SECTION II, Sect 2.7.3 (Subtask 7.3) sole para; Sect 2.71 (Subtask 7.1) first para / Also see RFI Questions Context/Background/Observations | This combination of maneuverability using decentralized, spatially dispersed small and medium satellites increases the resilience of both the service overall…”. Can “small and medium” be removed from the above language and retain the same desired effect to provide resilient SATCOM services? | The Government will take this under advisement, but will not commit to the removal of this language and may specify SV size based on government requirements. | ||
| 16 | PWS | SECTION VI – 6.0 Security Requirements / Also see RFI Questions Context/Background/Observations | The third and fourth paragraphs of this section currently include the following provisions—but in separate paragraphs: a. | Third Paragraph: “The contractor’s NOC shall be manned by cleared SECRET U.S. Citizen and English-speaking technicians available 24 hours a day 7 days a week as the focal point for any problems encountered with the leased services.” b. | Fourth Paragraph: “. . . The reliance of the contractor on a business partner with appropriate clearances and security devices to supply this capability or use of appropriate commercial standard encryption devices and NATO or allied cleared personnel is acceptable.” Questions: Can the above language be replaced with the following language which is a provision included in the EUCOM BPA? “The contractor shall have English speaking technicians available 24 hours a day, 7 days a week as the focal point for any problems encountered with the leased services. The technicians shall be able to troubleshoot or escalate to the next tier any problems encountered on the leased services. The contractor shall support U.S. SECRET voice capability and personnel with U.S. SECRET security clearances to discuss sensitive information. The reliance of the contractor on a business partner with appropriate clearances and security devices to supply this capability or use of appropriate commercial standard encryption devices and NATO or allied cleared personnel is acceptable.” | The Governmnet acknowledges the request and PWS Section 6 may be updated in the final draft to clarity the security clearance requirements. |
| 17 | FA2 | Section L, Functional Area 2, Subfactor 2, para a. / Also see RFI Questions Context/Background/Observations | The capability to support operational managed and/or leased-resource services via GEO commercial satellites globally”. Given that many vendors provide services on a regional basis and task orders may be regional in nature, can "globally" be removed from above language? | No. Global support is required, and as the solutions are not being priced at the IDIQ level, regional support will be identified and priced at the task order level. |
Q2
| Question Element | Government Response (Specific PWS References) | Explicit in PWS? | Clarification Action |
| Coordination before/during maneuver | Addressed in Section 2.9.5 (Communications and Escalation Plan) and Section 2.2.1 (Task 1 – Spacecraft Operations), which require coordination and regulatory activities associated with spacecraft operations and maneuvers. | Implicit | The Government will consider adding explicit reference to pre- and concurrent coordination activities, including timeline expectations. |
| Spacecraft repositioning | Addressed in Sections 2.1 and 2.2.1 (Task 1 – Spacecraft Operations), which require on-orbit operations including maneuverable spacecraft and repositioning. | Explicit | The Government will cross-reference Tasks 2 and 6 to ensure supporting activities are clearly tied to repositioning requirements. |
| ITU approval | Covered in Section 2.9.8 (Frequency Clearances and Approvals), which requires contractors to obtain all necessary national and international approvals to operate. | Implicit | The Government will consider explicitly including “ITU filings for geosynchronous slot operations.” |
| Coordination with adjacent satellites | Addressed in Section 2.2.1 (Task 1 – Spacecraft Operations) under “any required regulatory or coordination activities.” | Implicit | The Government will consider adding explicit mention of coordination with adjacent satellite operators. |
| Host nation approval / landing rights | Covered in Section 2.9.8 (Frequency Clearances and Approvals), which requires host nation approvals (HNAs) as applicable. | Implicit | The Government will consider explicitly including “host nation approvals and landing rights.” |
| Ground infrastructure / teleports | Addressed in Section 2.2.2 (Task 2 – Ground Infrastructure), which requires the contractor to establish and operate TT&C facilities and network entry points, including gateways and teleports. | Explicit | None. Clarification will occur at the task level. |
| Security validation (physical/cyber) | Explicitly covered in Sections 6.4 (Information Security), 6.6 (NIST SP 800-171 Compliance), and 6.7 (Cyber Incident Response). | Explicit | None. Clarification will occur at the task level. |
| Secured DoDIN connectivity | Addressed in Section 2.2.2 (Task 2 – Ground Infrastructure), which requires network entry points to support service delivery, and Section 6.4 (Information Security), which requires information assurance and encryption. | Implicit | The Government will consider adding explicit requirement for “secured connectivity to authorized DoDIN Points of Presence.” |
| Comprehensive task scope | Addressed across Section 2.1 (Purpose), Tasks 1, 2, 4, and 6, and Section 2.9 (Service Continuity/Management). | Partially | The Government will consider adding an overarching statement defining “maneuver communications” as encompassing all operational, regulatory, and infrastructure activities required to ensure resilient SATCOM support to the warfighter. |
File details come from the government source that posted it. Updated .