Contracts · C2
Air Force asks vendors about splitting mobility C2 software work
The APEX request asks whether separating legacy sustainment from new development would change vendors’ bidding plans. Responses are due Nov. 30.
The Air Force is asking contractors how splitting software development and legacy sustainment into separate contracts would change their interest in work for Air Mobility Command’s command and control applications.2
If the requirements were decoupled into two distinct contracts
Air Force Life Cycle Management Center
RFI question A1 asks bidding posture under the current combined scope of legacy sustainment and N-Tier architecture development
how bidding posture would change if the requirements were decoupled into two distinct contracts
The RFI is for market research and does not constitute a solicitation or bind the government to award
Source: Air Force APEX request for information, SAM.gov
Sources
The current scope combines legacy application sustainment with N-tier architecture development. Vendors are asked whether they would participate as a prime contractor, subcontractor or teaming partner, or decline to bid, and how those choices would change under two distinct contracts. The split is posed as a market-research question; the request is not a solicitation and does not commit the government to an award.2
Posted Oct. 28, 2026, the request for information is titled Agile Platform for Expeditionary C2, or APEX.1 It comes from the Air Force Life Cycle Management Center’s Airspace Mission Planning Division and concerns Air Mobility Command’s Rapid Global Mobility Command and Control program.2
The proposed work covers full software lifecycle support for National Security System level command and control applications, with access to a government-provided accredited software factory.2–3 Legacy applications covered include MAFPS, GDSS, CAMPS and MEIS. The statement of objectives lists delivery of a minimum viable capability release within six months of newly defined user needs as an example performance measure.3
Responses are due Nov. 30, 2026.2 The cutoff is 5 p.m. Eastern.2
Vendors’ answers would give the service evidence about contractor interest under each structure, without establishing which structure it will choose.2