AMC A6 AOI_Final_Amendment 02.pdf

Area of Interest 1: Air Mobility Command (AMC) A6 – Base Information Technology Modernization – Please note that responses will only be accepted from Service-Disabled Veteran Owned Small Businesses (SDVOSBs) – Amendment 02

*All amendment changes noted in red font.

Due to the questions received during the Q&A period, this CSO and AOI are currently on pause as the acquisition strategy is further examined and determined. Please continue to monitor SAM.gov postings for future updates.

Introduction & Mission Objective

Air Mobility Command (AMC) seeks innovative partners to lead a comprehensive transformation of its Information Technology (IT) infrastructure. The current legacy environment is outdated, inefficient, and hinders the "Global Reach" mission by compromising operational speed, data sharing, and overall warfighter effectiveness.

The objective is to overhaul this system by assessing existing architecture, developing a forward-looking roadmap, and integrating modern technologies across core, cloud, and edge environments. The goal is to field a secure, scalable, and purpose-built IT infrastructure that enables data-driven, globally maneuverable airpower for modern joint warfare.

The Challenge: Critical Infrastructure Vulnerabilities

The IT infrastructure currently supporting AMC bases suffers from several critical vulnerabilities that directly impact mission readiness:

• Operational Inefficiency: Aging hardware and antiquated software result in slow performance, frequent outages, and an unsustainable maintenance burden, diverting critical resources from mission-focused activities.

• Limited Data Sharing: The lack of secure, accredited cross-domain solutions prevents the seamless flow of critical data between NIPRNET, SIPRNET, and other partner networks, hindering joint operational planning and execution.

• Poor Scalability and Resilience: The rigid, on-premises infrastructure cannot scale to meet new mission demands, surge capacity, or ensure rapid recovery from disruptions.

• Degraded Warfighter Effectiveness: These combined limitations create a slow and siloed system, directly impeding the rapid, data-driven decision-making essential for projecting modern airpower.

Detailed Scope of Work & Technical Requirements

Step One: White Paper Submission

Technical Approach:

I. Title Page, which must include:

o Company Name o Title of the Submission o Point of Contact (Name, Title, Date, E-Mail, Phone, Address) o A list of any subcontractors or additional team members o An abstract providing a concise description of the approach

II. Technical Approach Narrative, which must:

o Describe the background, objectives, technical methodology, and resources needed for the solution proposed in the White Paper.

o Include the nature and extent of the anticipated results.

o Detail any potential ancillary issues such as certifications, algorithms, or specific engineering/software development methodologies to be used.

o Provide a Statement of Work (SOW) and a detailed project schedule. You may refer to the White Paper but should not duplicate its content.

III. Government Support Required:

Identify the type of support, if any, requested from the Government, such as facilities, equipment, data, or other materials.

Submission & Evaluation Process

The selection process will occur in two steps. Offerors are responsible for monitoring SAM.gov for any amendments to this solicitation.

Step One: White Paper Submission

• Questions Due Date: No later than 10 April 2026, at 14:00 CST.

o Q&A Matrix will be posted on the 10th following the question deadline with answers to outstanding questions.

Q&A Matrix will be posted once the Acquisition Strategy is determined (due to potential changes resulting from questions received during Q&A period).

• White Paper Due Date: On or before 24 April 2026, at 14:00 CST.

• Submission POC:

https://www.google.com/url?q=https%3A%2F%2Fsam.gov%2Fcontent%2Fhome o Contracting/Agreements Officer: Lisa Pendragon (lisa.pendragon@us.af.mil) o Contract/Agreements Specialist: Elijah Dodd (elijah.dodd@us.af.mil)

White Paper Content:

• Section A: Company Information:

o Project Title, Company Name, Business Size, CAGE number, UEI number, and POCs for contracting and technical matters.

• Section B: Technical Solution:

o A description of how your concept uniquely and innovatively meets the requirements detailed in “Detailed Scope of Work & Technical Requirements” section.

• Section C: Total Project Price:

o Propose a total price and provide supporting data (e.g., commercial price catalogs) to help the Government determine a fair and reasonable price.

(White Papers shall not exceed 10 pages OR 15 slides excluding title page/slide and table of contents. Font shall be 12 pt Times New Roman.)

White Paper Evaluation:

White Papers will be evaluated and categorized as either Selectable (recommended to advance) or Not Selectable.

Step Two: Detailed Approach (By Invitation Only)

Companies whose White Papers are deemed “Selectable” will be invited to submit a fully written Detailed Approach. Companies are encouraged to discuss ideas and details with the Government during the writing process. The Government will provide information on equipment and software needed to complete step two as applicable.

Step Two – Detailed Approach:

After White Paper evaluation(s), selected offerors will be invited to design and implement a solution for AMC’s IT challenges for step two. Air Force subject matter experts (SMEs) will be available for consultation. The proposed solution must provide a detailed technical approach that meets or exceeds the following requirements:

Travel Assumption:

https://www.google.com/url?q=mailto%3Alisa.pendragon%40us.af.mil https://www.google.com/url?q=mailto%3Aelijah.dodd%40us.af.mil o For evaluation purposes only, assume one person travelling to two of the locations listed in Section 5 and indicate which two were selected in your proposal. Price each trip at 2 weeks, including Air Fare, Lodging, etc.

A. Assessment & Analysis Methodology:

• Describe the technical approach for conducting a comprehensive assessment of the existing IT infrastructure at two representative AMC installations.

• This must include a detailed methodology for evaluating legacy systems to identify specific operational inefficiencies, performance bottlenecks, and security vulnerabilities.

• Proposals must specify the tools, diagnostic techniques, and personnel expertise that will be used to map the current “as-is” architecture and operational workflows.

• Explain how findings will be analyzed and documented to establish a clear performance and security baseline for the transition roadmap.

B. Proposed Future State Architecture:

• Present a high-level concept for the target “to-be” architecture that is secure, scalable, and resilient. This design must encompass core data centers, edge computing environments, and cloud components (hybrid and/or multi-cloud).

• Specifically address the approach for implementing a secure and accredited Cross- Domain Solution (CDS) to enable seamless data exchange between NIPRNET, SIPRNET, and other required domains.

• Describe the strategy for migrating legacy applications and on-premises data to the proposed modernized environment while ensuring mission continuity and adhering to strict cybersecurity requirements.

C. Transition & Implementation Roadmap:

• Provide a notional, phased transition roadmap that logically sequences key activities, including pilot programs, testing, and phased installation across AMC sites to minimize operational disruption.

• The roadmap must identify major proposed milestones, critical dependencies between tasks, and key go/no-go decision points for each step.

• Define the key performance indicators (KPIs) and metrics that will be used to measure the success and effectiveness of the modernization effort at each stage.

• Include a detailed Statement of Work (SOW) identifying all work to be performed, key deliverables, and a project schedule outlining all phases of work.

D. Core Technical Capabilities & Approach:

• Detail corporate experience and the proposed approach for executing key technical functions, including:

o System Integration: Integrating diverse, multi-vendor hardware, software, and cloud services into a cohesive, manageable system.

o Network Design: Designing and implementing modern, resilient network architectures based on principles such as Zero Trust and Software-Defined Networking (SDN).

o Multi-Solution Testing: Establishing a test and evaluation environment to validate integrated solutions and de-risk large-scale deployments.

o Large-Scale Installation: The project management and logistical approach for deploying the approved solution across multiple geographically dispersed CONUS and OCONUS installations.

E. Cybersecurity & Compliance Framework:

• Demonstrate a robust understanding of DoD cybersecurity requirements by describing the approach to:

o Risk Management Framework (RMF): The methodology for developing and delivering the necessary documentation to support the Assessment and Authorization (A&A) process and achieve an Interim Authority to Test (IATT).

o Cybersecurity Supply Chain Risk Management (C-SCRM): The processes used to ensure full traceability of all hardware and software components and to verify compliance with the Trade Agreements Act (TAA).

o Classified Operations: The technical and procedural controls that will secure the infrastructure and manage data at the NIPRNET and SIPRNET classification levels.

Detailed Approach Evaluation:

Proposals will be evaluated on Technical Merit, Importance to Agency, and Price. All factors are of equal importance. They will be categorized as Acceptable (recommended for funding) or Not Acceptable.

Contract Administration & General Information

• Funding: The Government will review responses and seek funding for the most innovative and affordable solutions. All awards are subject to the availability of funds.

• Pricing Strategy: Any resulting award will be a firm-fixed-price contract subject to RFO FAR 12.205 Solicitation provisions and contract clauses.

• Security Requirements: Offerors will require access to classified information up to the SECRET level. All personnel must have a minimum of a Tier 3 Security Investigation with “SECRET” eligibility and be enrolled in Continuous Vetting within 30 days of award. A “SECRET” facilities clearance is required for this effort.

• Location of Work: Work will primarily be performed at government-furnished facilities at AMC installations. Contract management will be conducted at the offeror’s facility.

Travel may be required to the following locations:

o Joint Base McGuire-Dix-Lakehurst, NJ o Joint Base Charleston, SC o Pope Army Airfield, NC o Travis AFB, CA o Scott AFB, IL o Joint Base Pearl Harbor-Hickam, HI o Ramstein AB, Germany o Little Rock AFB, AR o Joint Base Lewis-McChord, WA o Joint Base Andrews, MD o Dyess AFB, TX o Dover AFB, DE o MacDill AFB, FL o McConnell AFB, KS o Fairchild AFB, WA

Attachments:

Attachment 1 - Q&A Matrix