CCMDs2DoDNet_SSN 27AUG26.pdf

SOURCES SOUGHT NOTICE

Tracking Number 6XX2026

The Defense Information Systems Agency, (DISA) J6, DoDNet Program Management Office (PMO) is seeking sources for Combatant Command (CCMD) Migration to the Department of Defense Network (DoDNet)

CONTRACTING OFFICE ADDRESS:

DISA

Defense Information Technology Contracting Organization (DITCO) - National Capital Region 6910 Cooper Avenue Fort Meade, MD 20755

INTRODUCTION:

This is a SOURCES SOUGHT NOTICE to determine the availability and technical capability of small businesses and large businesses to provide the required services.

DISA is seeking information from potential sources to migrate the Department of War’s (DoW) Combatant Commands’ (CCMD) common-use Information Technology (IT) Non- Classified Internet Protocol Router Network (NIPRNet) and Secret Internet Protocol Router Network (SIPRNet) requirements onto the DISA-managed DoDNet. This acquisition is being planned in response to a memo published from the DoW Chief Information Officer (CIO) on 22 May 2026 titled “Combatant Command Network Optimization Execution Guidance.” The memorandum states that “DISA will execute migrations for all unclassified (NIPR) and classified (SIPR) Common Use IT” for the CCMDs by the end of Fiscal Year (FY) 2028. The memorandum is attached to this notice for reference.

The eleven (11) CCMDs currently operate independent NIPRNet and SIPRNet environments. Each CCMD performs a unique mission and operates globally across both Continental United States (CONUS) and Other than Continental United States (OCONUS) locations. There are approximately 231,000 users and approximately 200 sites across the 11 CCMDs. Site locations are withheld from public release due to classified Combatant Command (CCMD) requirements.

DISA is seeking contractor support to migrate the common-use CCMD network and user requirements into the single DISA-managed environment, the DoDNet. This effort will include tasks for endpoint and network discovery, design, planning, and migration execution in order to transition to operations, and sustainment to the Government. The key objectives are to:

• Migrate 11 CCMDs (231,000 users, 200 global sites) common-use IT NIPRNet and SIPRNet environments to DoDNet by the end of the FY 2028.

• Provide a single contract with capability for all migration activities from customer contact, discovery effort, migration of networks and endpoints, and to transition to operations.

• Utilize best practice tools, techniques, processes, and procedures to provide the highest level of quality customer service.

• Generate innovative service delivery techniques that will allow for complete discovery and migrations by the end of the FY 2028, which is the timeframe mandated by the DoW CIO memo.

The anticipated Period of Performance is 01 October 2026 to 30 September 2028.

The anticipated Place of Performance is across approximately 200 Global sites.

DISCLAIMER:

THIS SOURCES SOUGHT NOTICE IS FOR INFORMATIONAL PURPOSES ONLY.

THIS IS NOT A REQUEST FOR PROPOSAL. IT DOES NOT CONSTITUTE A

SOLICITATION AND SHALL NOT BE CONSTRUED AS A COMMITMENT BY THE

GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS AND THE

GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT AS A

RESULT OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR

PREPARATION OF RESPONSES TO THIS ANNOUNCEMENT. ANY INFORMATION

SUBMITTED BY RESPONDENTS TO THIS TECHNICAL DESCRIPTION IS

STRICTLY VOLUNTARY.

CONTRACT/PROGRAM BACKGROUND:

The migration of the CCMD customers to the DoDNet Single Service Provider environment is a new requirement. A similar and related migration of the Defense Agencies and Field Activities (DAFA) to the DoDNet Single Service Provider environment is already underway.

This requirement must be executed in parallel, and without disturbing ongoing DAFA migrations.

REQUIRED CAPABILITIES:

Demonstrated knowledge and expertise in the following foundational technical capabilities is required.

Technical Capability Description Why this is a critical capability A primary pillar to achieve Details the Identity Zero Trust Architecture (ZTA) Management, Active requirements, provide access

Identity, Directory (AD) forest trusts, controls, permissions, and end Credential, and domain consolidation plans, user lifecycle management from Access and specialized Global migration through ongoing Management Directory configurations that sustainment. Requirement is to (ICAM) have been engineered to immediately leverage purpose-connect legacy DAFA built scripts and integrations networks to DoDNet. with service providers have been developed for efficiency.

Technical Capability Description Why this is a critical capability

Zero Trust Architecture

(ZTA) &

Security Boundaries

Specific as-built network topologies, firewall rule sets, rapid onboarding methodology, and service availability tools developed to monitor the DoDNet Single Service Provider (SSP) boundary.

Foundation of the secure by design and ZTA enabled DoDNet environment. Required planning, design, and integration steps have been developed and operationalized over the past 4 years. Required to ensure common operating environment and scalability.

Infrastructure as Code (IaC) & Automation Scripts

Purpose built automation scripts, API connections, provisioning tools, and communications, used to rapidly migrate users, devices, data from legacy environments into the DES cloud/on-premises infrastructure.

Purpose built, automation tools using Bash, PowerShell, and Python that are hardened with PKI certificates and secure key exchanges. Required to learn, incorporate, and improve these for immediate use and continuity.

Migration Methodologies & Runbooks

The streamlined governance processes within the DoDNet System Engineering Framework (DSEF), Standard Operating Procedures (SOP), physical and virtual site survey data, and lessons-learned artifacts compiled while migrating the initial 22 DAFAs.

Required for immediate success and continuity of overall DoDNet processes. Immediate integration of all procedures to meet migration goals over the next two fiscal years. The overall strategies were previously developed over 6-12 months to gain migration efficiencies.

1. Unmanaged Environments & Parallel Baselines:

o Provide one or two concrete examples of projects similar in Department of

War (DOW) scope and magnitude (approx. 20 locations / 12,000 users) where you successfully executed network and endpoint discovery, migration planning, and execution for an environment you did not currently manage.

Specifically, detail your experience migrating to a new baseline in parallel with a physical lifecycle hardware replacement.

2. Modernization Execution & Velocity:

o Provide one or two examples of successfully performing automated migrations from legacy endpoint tools (e.g., MECM/SCCM, Jamf) to modernized device management solutions (e.g., Microsoft Intune) within a

Department of War (DOW) environment. For each example, specify the exact deployment timeframe and the total endpoint count migrated.

3. Training and Adoption:

o Please detail your training and adoption strategy to deploy an accelerated ramp up in geographically disperse locations. Specifically, what tools, platforms, or methodologies have you employed in similar efforts to minimize the learning curve and ensure uninterrupted mission readiness for users transitioning to a new integrated endpoint and network service provider.

SPECIAL REQUIREMENTS:

The contractor must possess a minimum SECRET level facility security clearance. Please provide your current Facility Clearance level.

SUBMISSION DETAILS:

Responses should include:

1) Business name and address;

2) Name of company representative and their business title;

3) Small Business socio-economic status (if small);

4) CAGE Code;

5) Prime contract vehicles for which this requirement may be within scope and ceiling;

6) In order to make a determination for a small business set-aside, two or more qualified and capable small businesses must submit responses that demonstrate their qualifications and experience to perform similar services for requirements similar to size and scope of the CCMD migrations. Responses must demonstrate the company’s ability to perform in accordance with the Limitations on Subcontracting clause (FAR 52.219-14).

Businesses who wish to respond must send a response via email no later than August 28, 2026 3:00 PM Eastern Daylight Time to Jonathan Chattler (jonathan.r.chattler.civ@mail.mil), Darrin Meyer (darrin.r.meyer.civ@mail.mil). In no more than five (5) pages, interested businesses should submit a capabilities statement package, with responses to the required capability inquires stated above, demonstrating their ability to perform the services listed.

Proprietary information and trade secrets, if there are any, must be clearly marked on all materials. All information received that is marked Proprietary will be handled accordingly.

All submissions become Government property and will not be returned. All government and contractor personnel reviewing submitted responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.

mailto:(jonathan.r.chattler.civ@mail.mil mailto:(darrin.r.meyer.civ@mail.mil