DISA seeks industry input on CommandNet migration following GAO protest 19%

By measley27%

8/4/2026, 7:53:10 AM

BS Summary: This article contains 17 faulty reasoning types, including Self-Serving Bias, Optimism Bias, and Begging the Question, with Unattributed Quote as the most egregious example at 14.3% saturation with 127 hits. Analysis detected 668 faulty-reasoning hits from 889 analyzed words, generating a BS Score of 25.8% and a BS Rank of 19% (25,942 of 31,900 articles). This article is better (less manipulative) than 81.30% of the article peer group.

The Defense Information Systems Agency is conducting market research on its planned CommandNet migration weeks after General Dynamics Information Technology protested the agency’s decision to award the work without holding a competition. 
A sources-sought notice posted to Sam.gov on July 27 is requesting industry feedback on the CommandNet effort  which aims to move users across all 11 combatant commands to a single, DISA-managed IT architecture known as DODNet by fiscal 2028. 
Interested companies are being asked to submit their technical approach, transition plans, cost estimates and relevant past performance. 
DISA first announced CommandNet last year as an effort to consolidate disparate, geographically-isolated networks into an agency-managed enterprise architecture. 
A May memorandum from Pentagon Chief Information Officer Kirsten Davies directed the agency to migrate all CoCom common-use unclassified and classified services to DODNet by the end of FY28  expanding the agency’s ongoing enterprise IT modernization across the Pentagon. 
Each combatant command currently runs and operates its own unique IT infrastructure that segregates users by geographic location and makes collaboration across CoComs inefficient. 
DISA’s call to industry estimates that at the 11 combatant commands, approximately 231,000 users at 200 sites located around the world will need to be moved to CommandNet. 
The work is expected to be completed by September 2028, according to the sources-sought notice. 
Vendors are required to provide a solution featuring identity and access management (ICAM), zero-trust cybersecurity, infrastructure as code and migration methodologies. 
“The government estimates a competitive procurement cycle of approximately 220 days from solicitation release to contract award,” DISA stated. 
“Responses must detail a realistic, risk-mitigated milestone schedule that fits within this condensed timeline to guarantee full compliance with the September 30, 2028 deadline.” 
Industry’s responses to the sources-sought notice are due Aug. 
4. 
The decision to conduct market research is a notable shift from the agency’s earlier acquisition strategy. 
In June, DISA announced that it would give a sole-source task order for CommandNet migration to Leidos under the $11.5 billion Defense Enclave Services (DES) contract, which was awarded to the company in 2022 to migrate the Pentagon’s “Fourth Estate” agencies to DODNet. 
The DES expansion award was challenged by GDIT in a bid protest filed with the Government Accountability Office on July 10. 
The protest has since been dismissed following DISA’s new call for market research, and the agency is now asking industry to demonstrate they can overcome the exact reasons DISA previously cited for avoiding competition. 
According to DISA’s original justification to sole-source , the existing DES contract was the only viable option for CommandNet because the 2028 deadline left insufficient time to conduct a new competition and transition work to another contractor. 
Awarding the work under an open competition would “result in substantial duplication of administrative and technical cost, which is not expected to be recovered through competition,” the agency stated. 
DISA had also asserted that bringing on a new contractor would require significant time to develop expertise in the DODNet environment, increasing the risk of schedule delays and operational disruption. 
But GDIT’s protest disputed these claims, arguing that DISA’s failure to conduct market research led the agency to incorrectly conclude only Leidos could perform the CommandNet migration. 
Other acquisition strategies and contracting vehicles could support the agency’s requirements and deadline, according to a source familiar with the matter. 
“A rushed approach to consolidating combatant command IT needs into the Defense Enclave Service contract really failed to consider faster, cheaper and more effective alternatives to achieve the CIO’s goal,” the source told DefenseScoop. 
“There was an opportunity to really think about what is the best contracting vehicle given the specific nature of what’s trying to be achieved here.” 
In addition, the company’s protest contended that migrating CoCom users to DODNet presents different technical and operational challenges than the Fourth Estate organizations currently transitioning under DES. 
Defense agencies and field activities primarily rely on enterprise IT services, while combatant commands support operational missions across multiple environments, security classifications and alliance structures. 
“These IT systems are what enable commanders to communicate with warfighters and weapon systems. 
It’s fundamentally different than the back-office IT  which is very important  that the Defense Enclave Services contract has traditionally been focused on,” the source said. 
GDIT further argued that DISA overstated Leidos’ performance on the DES contract. 
In its justification document, the agency cites the company’s migration of around 40,000 users in the last four years as proof it is the only vendor qualified for the work. 
However, DISA’s solicitation for the DES contract required the prime contractor to migrate at least 370,000 Fourth Estate users to DODNet. 
In a statement, Leidos said it is focused on continuing its work to migrate Fourth Estate users to DODNet. 
“We have migrated more than 40,000 users to the DoDNet environment since 2022 and believe our in-depth experience with the architecture, migration processes and technical baseline will allow us to transition combatant commands effectively and rapidly,” a spokesperson told DefenseScoop. 
“We will continue working alongside DISA to support the agency’s operations and enhance mission readiness.” 
GDIT declined to comment on its protest with GAO and the newly posted sources-sought notice. 
DISA did not respond to DefenseScoop’s multiple requests for comment. 
The post DISA seeks industry input on CommandNet migration following GAO protest appeared first on DefenseScoop . 
Article reasoning-pattern comparisonThis article: 1.8%measley: 1.0%DefenseScoop: 1.8%Confirmation Bias1.8%This article: 0.0%measley: 0.2%DefenseScoop: 0.7%Anchoring Bias0.0%This article: 2.4%measley: 1.0%DefenseScoop: 1.8%Availability Heuristic2.4%This article: 2.7%measley: 0.6%DefenseScoop: 0.4%Representativeness Heuristic2.7%This article: 0.0%measley: 0.0%DefenseScoop: 0.1%Hindsight Bias0.0%This article: 0.0%measley: 1.1%DefenseScoop: 2.2%Overconfidence Bias0.0%This article: 0.0%measley: 3.5%DefenseScoop: 4.3%Framing Effect0.0%This article: 0.0%measley: 0.1%DefenseScoop: 0.3%Loss Aversion0.0%This article: 0.0%measley: 0.8%DefenseScoop: 0.6%Status Quo Bias0.0%This article: 0.0%measley: 0.3%DefenseScoop: 0.5%Sunk Cost Effect0.0%This article: 7.9%measley: 9.5%DefenseScoop: 8.5%Optimism Bias7.9%This article: 0.0%measley: 0.4%DefenseScoop: 1.4%Pessimism Bias0.0%This article: 3.8%measley: 1.7%DefenseScoop: 2.8%Negativity Bias3.8%This article: 11.2%measley: 1.7%DefenseScoop: 2.1%Self-Serving Bias11.2%This article: 0.0%measley: 0.2%DefenseScoop: 0.1%Fundamental Attribution Error0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Actor-Observer Bias0.0%This article: 2.8%measley: 0.1%DefenseScoop: 0.6%In-Group Bias2.8%This article: 0.0%measley: 0.0%DefenseScoop: 0.1%Out-Group Homogeneity Bias0.0%This article: 3.4%measley: 2.0%DefenseScoop: 2.7%Halo Effect3.4%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Horn Effect0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Dunning-Kruger Effect0.0%This article: 0.0%measley: 0.7%DefenseScoop: 0.8%Recency Bias0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Primacy Effect0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Blind-Spot Bias0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.1%Ad Hominem0.0%This article: 0.0%measley: 0.1%DefenseScoop: 0.2%Straw Man0.0%This article: 0.0%measley: 2.3%DefenseScoop: 3.2%Appeal to Authority0.0%This article: 0.0%measley: 1.0%DefenseScoop: 0.8%False Dilemma0.0%This article: 0.0%measley: 0.2%DefenseScoop: 0.3%Slippery Slope0.0%This article: 0.0%measley: 0.2%DefenseScoop: 0.3%Circular Reasoning0.0%This article: 3.4%measley: 1.7%DefenseScoop: 2.7%Hasty Generalization3.4%This article: 0.0%measley: 0.0%DefenseScoop: 0.1%Red Herring0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.2%Bandwagon0.0%This article: 1.6%measley: 1.2%DefenseScoop: 1.5%Appeal to Emotion1.6%This article: 7.2%measley: 0.5%DefenseScoop: 0.6%Begging the Question7.2%This article: 3.6%measley: 1.0%DefenseScoop: 1.4%Post Hoc (False Cause)3.6%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Tu Quoque0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.3%Burden of Proof0.0%This article: 0.0%measley: 0.1%DefenseScoop: 0.1%Appeal to Nature0.0%This article: 2.8%measley: 0.2%DefenseScoop: 0.2%Composition/Division2.8%This article: 2.4%measley: 1.1%DefenseScoop: 1.2%Anecdotal2.4%This article: 0.0%measley: 0.0%DefenseScoop: 0.1%No True Scotsman0.0%This article: 3.8%measley: 1.3%DefenseScoop: 1.2%Ambiguity (Equivocation)3.8%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Gambler’s Fallacy0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.1%Middle Ground0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Personal Incredulity0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Special Pleading0.0%This article: 0.0%measley: 0.0%DefenseScoop: 0.0%Genetic Fallacy0.0%This article: 14.3%measley: 1.4%DefenseScoop: 1.9%Unattributed Quote14.3%This article: 0.0%measley: 1.0%DefenseScoop: 1.2%Quote-first Misdirection0.0%This article: 0.1%measley: 0.8%DefenseScoop: 1.8%Biased Writer Voice0.1%This article: 0.0%measley: 0.8%DefenseScoop: 0.9%Indoctrination0.0%This article: 0.0%measley: 0.1%DefenseScoop: 0.0%Politically Left Leaning Bias0.0%This article: 0.0%measley: 0.1%DefenseScoop: 0.0%Politically Right Leaning Bias0.0%This article: 0.0%measley: 1.0%DefenseScoop: 4.4%Attempt to Sell a Product or S…0.0%

889 words analyzed.

Speakers

3speakers19%attributed speech722writer words
Selected voice

Leidos

100%flagged-word coverage
74 attributed words44% of attributed speech41% writer coverage
0%37.5%75.0%Unattributed Quote+74.3 ptsWriter: 0.0%Leidos: 74.3%74.3%Biased Writer Voice-0.1 ptsWriter: 0.1%Leidos: 0.0%0.0%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.