Agile Platform for Expeditionary C2 (APEX) RFI.pdf

Request for Information (RFI)

Airspace Mission Planning Division – APEX (Agile Platform for Expeditionary C2)

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. This notice is for informational and planning purposes only. In accordance with (IAW) the Revolutionary Far

Overhaul (RFO) Part 10 and the Revised - Defense Federal Acquisition Regulations (R-DFARS)

Part 210, the Government is conducting market research to determine the availability and adequacy of potential business sources that meet the Government’s requirement. This RFI does not constitute solicitation for bids or proposals, and in no way binds the Government to solicit or award a competitive contract. The Government will not be liable for any information not properly marked and clearly identified. The Government is not obligated to and will not reimburse respondents for any costs associated with preparing or submitting a response to this notice. All costs associated with responding to this RFI are solely at the responding parties' expense. All submissions become Government property and will not be returned to the sender.

This RFI is from the Air Force Life Cycle Management Center (AFLCMC) Airspace Mission

Planning Division (C3M) of the Command, Control, Communications and Battle Management

(C3BM) Portfolio Acquisition Executive (PAE) Operating Location 2 (OL-2) located at 859

Buchanan Street, Scott AFB, IL 62269. C3M is seeking unclassified information from interested

Contractors.

Any response submitted to this RFI constitutes consent for that submission to be reviewed by

Government personnel and Program Lifecycle Management Support Services (PLMSS), Advisory & Assistance Services (A&AS) contractors employed by ITSC Secure Solutions, Paragon, OBXtek, Kairos and MQP. Any objection to the release of this information to A&AS contractors shall be provided, in writing, via the cover letter accompanying the respondent’s submission.

1 INTRODUCTION

The Air Force Life Cycle Management Center (AFLCMC) Command, Control, Communications and Battle Management (C3BM) Operating Location 2 (OL-2) is executing Software

Development Lifecyle Management for Air Mobility Command’s (AMC) Rapid Global Mobility

Command and Control (RGM C2) Program, that leverages technical solutions and practices for all Air Force Transportation (AFTRANS) operations. AMC is the air component of United States

Transportation Command (USTRANSCOM), providing air refueling, cargo, and personnel delivery globally. AMC is also the Air Force Lead Command and Core Function Lead for RGM

C2. To effectively support the Joint Force, the MAF must globally command, control, and collaborate, navigate in degraded or operationally limited environments, conduct enroute logistics while under attack, and operate at the highest required tempo. This requires global situational awareness through collaboration, coordinated operations, and adherence to processes that accomplish Combatant Commander objectives.

2 SERVICE REQUIREMENTS DESCRIPTION

2.1 Overview

The scope of this effort includes the full software lifecycle support for National Security System level C2 applications. The government's goal is to partner with a contractor(s) who can deliver mission-focused capabilities to the warfighter at the speed of relevance by leveraging modern practices within a government-provided software factory and Platform as a Service (PaaS) environment.

2.2 Service Description

Please see the attached SOO.

2.3 Service Objective

Please see the attached SOO.

3 RESPONSES

3.1 Submission Information

Responses to this RFI shall be submitted no later than 5:00PM ET on 30 November 2026.

Respondents should provide submissions to Ms. Mikayla Sequeira at mikayla.sequeira@us.af.mil and Ms. Venezia Delgadillo at venezia.delgadillo@us.af.mil.

Questions pertaining to this RFI and submissions in response to this RFI should be sent to both points of contact (PoCs) provided above.

Any submission not adhering to the instructions provided will not be reviewed.

3.2 Contents

Responses shall address all of the questions below in section 3.5; responses shall be organized in the same order that the questions are posed in.

Submissions shall not include classified information, proprietary information, and/or trade secrets. The Government will not review any submittals with classified information, proprietary information, and/or trade secrets. All submittals must be unclassified.

3.3 Format

Submissions shall be provided as either Microsoft Word (.docx) or Adobe Acrobat (.pdf).

Responses shall use letter sized pages (8.5in by 11in) with a layout of at least 1in margins for the top, bottom, left, and right margins. Responses shall not exceed 5 single-sided pages (excluding the cover page). Responses shall not contain images, gifs, and/or other media.

Responses shall use a professional font (e.g., Times New Roman, Arial, Calibri, Aptos) with a font size no smaller than 11pts and line spacing no less than 1.0 (i.e. “single-spaced”).

Failure to follow formatting requirements may result in your proposal not being considered for award

3.4 Cover Letter

Responses shall include a cover page that provides the following information, at a minimum:

I. Company information

• Name

• Mailing address

• CAGE code

• UEI

mailto:mikayla.sequeira@us.af.mil mailto:venezia.delgadillo@us.af.mil

• North American Industry Classification System (NAICS) code(s) applicable to this RFI

• Phone number

• E-mail of designated point of contact (PoC)

II. Business type i.e., other than small business, small business, small business concern (specify program status as a historically underutilized business zone (HUBZone) small business concern, service-disabled veteran-owned small business (SDVOSB) concern, women-owned small business (WOSB), and/or 8(a) participant)

III. Interest in this effort as a Prime Contractor or Subcontractor

IV. Existing vehicle(s) your organization is party to with scope relevant to this RFI

V. If applicable, objection(s) to the release of your organization’s RFI response to A&AS contractors supporting the PLMSS contract.

3.5 RFI Questions

Management:

M1) Does your company possess in-depth knowledge and experience in project management of large-scale DoD or Air Force programs? If so, please provide demonstrated experience with National Security Systems, including the scale and complexity of these engagements.

M2) Beyond core development, what additional services do you offer, such as user training, documentation, or strategic consulting for mission-critical software?

M3) What is your experience supporting and troubleshooting complex applications built with modern technologies and architecture, even when you are not the primary developer?

Development:

D1) What is your experience developing and sustaining software for mission-critical systems, particularly those with requirements similar to Air Force Command and Control applications?

D2) What modern technologies, architectures, and programming languages does your team specialize in to build resilient, scalable, and secure applications?

D3) Can you describe your development process and methodologies for delivering solutions in a secure, mission-critical environment? How do you adapt your process for programs requiring high assurance and reliability?

D4) What is your experience in operational support of other developer solutions that must interact with a complex ecosystem of external government systems?

D5) Describe your organization's corporate structure and methodology for providing development, sustainment, and support to programs containing classified data. What typical labor categories, clearance levels, and core technical competencies does your organization utilize to execute these requirements? Please focus on organizational framework, recruitment pipeline, and security compliance protocols rather than specific individual personnel.

D6) What is your methodology for building security into National Security Systems from the ground up? How do you ensure compliance with relevant DoD standards and instructions throughout the system lifecycle?

D7) What quality assurance and testing methodologies do you follow to ensure mission-grade software reliability and scalability where system failure has significant consequences?

Sustainment:

S1) How is your operational support team structured? What roles, clearances, and expertise do your team members possess for executing sustainment and support of programs containing classified data?

S2) When a critical system incident occurs, what experience do you have correlating disparate data sources (e.g., alerts, logs, pipeline events) to identify the most probable root cause and accelerate troubleshooting?

S3) What experience does your company have with analyzing resource usage patterns to proactively recommend specific actions for improving performance and achieving cost efficiencies of resources in a secure cloud environment?

S4) Do you have experience deploying, accrediting, and sustaining software on classified networks?

S5) Describe your experience managing and operating National Security Systems in secure production environments, including government-focused cloud platforms and on-premises data centers.

S6) What experience does your team have maintaining operational excellence when you do not control the deployment pipeline?

S7) What specific metrics would you propose to measure and prove that your solutions are successfully reducing manual labor and increasing the efficiency and effectiveness of mission-critical operations?

S8) Describe your technical approach and experience in decomposing legacy monolithic apps into containerized, loosely couple microservices.

S9) Describe your organization's experience in executing graceful deprecation of legacy monolithic apps as new apps come online.

Acquisition Strategy:

A1) Under the current combined scope (simultaneous legacy sustainment of applications such as MAFPS, GDSS, CAMPS, and MEIS as well as N-Tier architecture development), what would be your organization’s anticipated bidding posture (Prime, Subcontractor/Teaming Partner, or No-Bid)? If the requirements were decoupled into two distinct contracts, how would your bidding posture change for each effort?

Any submission not adhering to the instructions provided above may not be reviewed.

Irrespective of any answers to the above questions, all interested vendors are encouraged to bid.