Should DISA reopen competition for the Combatant Command migration?

Should DISA reopen competition for the Combatant Command migration effort, or is expanding an existing vehicle the fastest path to mission success?

Argument FOR DISA’s Review:

  • The migration affects approximately 231,000 users across 200 locations worldwide, making it one of the most consequential DoD network modernization efforts underway.
  • Conducting market research after the protest creates an opportunity to validate assumptions, assess alternative capabilities, and strengthen acquisition integrity.
  • Competition can often uncover innovative approaches, reduce risk, and improve long-term value for taxpayers.

Argument AGAINST Delaying Execution:

  • DoD has directed DISA to migrate combatant commands to the DoDNet environment, and the agency has a target of completing the effort by 30 September 2028.
  • Delays in acquisition strategy decisions can impact mission timelines and increase uncertainty for stakeholders.
  • The challenge is not just procurement. It is executing a highly complex migration while maintaining operational continuity.

From my perspective, the real question is not whether DISA should move fast or compete fairly. It must do both. In mission-critical IT modernization, speed without scrutiny creates risk, while scrutiny without execution creates delay. The winning strategy is a transparent acquisition approach that accelerates delivery without sacrificing competition.

What do you think? Should DISA pursue a new competitive path, or was leveraging the existing DES contract the right move from the start?

Source: Federal News Network Article [federalnew…etwork.com]

1 Like

It doesn’t have to be an all-or-nothing choice between a 2-year delay or a sole-source expansion. DISA could utilize a hybrid approach: leverage existing enterprise frameworks for baseline DoDNet onboarding, while competitively soliciting specialized task orders or sub-tier requirements—like Thunderdome Zero Trust integration, ICAM, and theater-specific operational edge capabilities. This maintains execution momentum on common commodity IT while opening up mission-critical specialized work to competitive market capabilities.

1 Like