Pentagon signs nearly $7B Oracle deal to unify defense software and cut $441M in costs ⁠84%

By Aamir Khollam⁠44%

7/23/2026, 4:36:12 PM

BS Summary: This article contains 19 faulty reasoning types, including Appeal to Authority, Biased Writer Voice, and Ambiguity (Equivocation), with Optimism Bias as the most egregious example at 51.9% saturation with 298 hits. Analysis detected 1,044 faulty-reasoning hits from 574 analyzed words, generating a BS Score of 75.1% and a BS Rank of ⁠84% (3,653 of 21,887 articles). This article is worse (more manipulative) than 83.30% of the article peer group.

The Department of War (DoW) has signed a nearly $7 billion enterprise software agreement with Oracle, marking its first direct, department-wide contract for on-premises Oracle software. 
Officials expect the deal to reduce fragmented software purchasing, improve oversight of enterprise technology spending, and save American taxpayers at least $441 million over the agreement’s lifetime. 
The Department of the Navy negotiated the contract on behalf of the broader department. 
It covers the entire DoW, along with the U.S. 
Coast Guard and the Intelligence Community. 
Officials say the agreement replaces years of separate licensing purchases with a single procurement framework that offers better visibility into software use across agencies. 
Replacing fragmented purchases 
Defense agencies have traditionally bought Oracle software through separate contracts, creating overlapping licenses and inconsistent spending patterns. 
The new enterprise agreement shifts those purchases under one contract, giving technology leaders a clearer picture of how software is deployed and where costs can be reduced. 
Officials believe the approach will also simplify license management and help eliminate duplicate purchases across military organizations. 
Better oversight could free up funding for other modernization efforts without reducing access to essential software. 
Officials also expect the centralized licensing model to simplify future software planning across the defense enterprise. 
Instead of managing separate agreements with different renewal dates and pricing structures, technology teams will work under a common framework. 
That approach can make budgeting more predictable and help agencies identify unused or underutilized licenses before committing to additional purchases. 
Greater visibility into software inventories could also support faster procurement decisions as operational requirements evolve. 
The agreement runs for an initial five-year period and includes an option to extend it for another five years, bringing the total potential duration to a decade. 
Supporting military modernization 
DoW Chief Information Officer Kirsten A. 
Davies said the agreement improves both procurement efficiency and operational readiness. 
“Improving how we acquire Oracle software will generate at least $441 million in taxpayer savings,” Davies said . 
She added that the agreement will strengthen the department’s digital infrastructure and support military missions with secure, scalable technology capable of meeting current and future operational demands. 
Officials view the contract as part of a broader effort to modernize defense information technology while controlling long-term operating costs. 
Centralizing procurement also gives the department more consistent data on software usage, making future technology planning easier. 
A unified licensing structure could also reduce administrative overhead and help technology teams respond faster as mission requirements and software demands change across defense organizations. 
Focus on security and interoperability 
Navy officials say the agreement extends beyond financial savings. 
Standardizing Oracle software across organizations could improve compatibility between systems and reduce cybersecurity risks linked to inconsistent deployments. 
Barry Tanner, performing the duties of the Department of the Navy’s Chief Information Officer, said the agreement will speed the delivery of secure software from shore-based networks to operational forces. 
“Reducing fragmented procurement and advancing enterprise standardization will strengthen interoperability, reduce cybersecurity risk, and help us focus resources on resilient capabilities that can scale, integrate, and endure in contested conditions,” Tanner said. 
The enterprise agreement represents one of the largest software procurement efforts undertaken by the Department of War. 
Officials expect it to serve as a long-term foundation for managing Oracle software across the U.S. defense enterprise while reducing unnecessary spending, improving technology oversight, and creating a more consistent approach to software acquisition across military organizations. 
Article reasoning-pattern comparisonThis article: 7.8%Aamir Khollam: 2.9%Interesting Engineering: 3.9%Confirmation Bias7.8%This article: 5.7%Aamir Khollam: 1.5%Interesting Engineering: 1.2%Anchoring Bias5.7%This article: 0.0%Aamir Khollam: 1.7%Interesting Engineering: 2.4%Availability Heuristic0.0%This article: 3.1%Aamir Khollam: 1.3%Interesting Engineering: 1.2%Representativeness Heuristic3.1%This article: 0.0%Aamir Khollam: 0.4%Interesting Engineering: 0.3%Hindsight Bias0.0%This article: 0.0%Aamir Khollam: 2.6%Interesting Engineering: 5.2%Overconfidence Bias0.0%This article: 10.1%Aamir Khollam: 7.2%Interesting Engineering: 6.4%Framing Effect10.1%This article: 0.0%Aamir Khollam: 0.4%Interesting Engineering: 0.2%Loss Aversion0.0%This article: 3.0%Aamir Khollam: 0.9%Interesting Engineering: 0.6%Status Quo Bias3.0%This article: 0.0%Aamir Khollam: 0.5%Interesting Engineering: 0.5%Sunk Cost Effect0.0%This article: 51.9%Aamir Khollam: 22.9%Interesting Engineering: 16.9%Optimism Bias51.9%This article: 0.0%Aamir Khollam: 0.1%Interesting Engineering: 0.6%Pessimism Bias0.0%This article: 0.0%Aamir Khollam: 0.4%Interesting Engineering: 0.9%Negativity Bias0.0%This article: 0.0%Aamir Khollam: 4.9%Interesting Engineering: 4.6%Self-Serving Bias0.0%This article: 3.5%Aamir Khollam: 0.1%Interesting Engineering: 0.2%Fundamental Attribution Error3.5%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Actor-Observer Bias0.0%This article: 0.0%Aamir Khollam: 0.3%Interesting Engineering: 0.9%In-Group Bias0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.1%Out-Group Homogeneity Bias0.0%This article: 5.6%Aamir Khollam: 4.2%Interesting Engineering: 5.2%Halo Effect5.6%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Horn Effect0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Dunning-Kruger Effect0.0%This article: 0.0%Aamir Khollam: 1.0%Interesting Engineering: 1.1%Recency Bias0.0%This article: 0.0%Aamir Khollam: 0.3%Interesting Engineering: 0.2%Primacy Effect0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Blind-Spot Bias0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Ad Hominem0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Straw Man0.0%This article: 19.7%Aamir Khollam: 7.8%Interesting Engineering: 8.6%Appeal to Authority19.7%This article: 0.0%Aamir Khollam: 1.2%Interesting Engineering: 1.5%False Dilemma0.0%This article: 0.0%Aamir Khollam: 0.4%Interesting Engineering: 0.3%Slippery Slope0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.1%Circular Reasoning0.0%This article: 4.2%Aamir Khollam: 4.4%Interesting Engineering: 5.1%Hasty Generalization4.2%This article: 0.0%Aamir Khollam: 0.1%Interesting Engineering: 0.1%Red Herring0.0%This article: 3.0%Aamir Khollam: 0.4%Interesting Engineering: 0.8%Bandwagon3.0%This article: 5.6%Aamir Khollam: 1.8%Interesting Engineering: 2.3%Appeal to Emotion5.6%This article: 4.7%Aamir Khollam: 0.6%Interesting Engineering: 1.2%Begging the Question4.7%This article: 8.7%Aamir Khollam: 2.1%Interesting Engineering: 2.2%Post Hoc (False Cause)8.7%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Tu Quoque0.0%This article: 6.4%Aamir Khollam: 0.5%Interesting Engineering: 0.6%Burden of Proof6.4%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.2%Appeal to Nature0.0%This article: 0.0%Aamir Khollam: 0.5%Interesting Engineering: 0.3%Composition/Division0.0%This article: 0.0%Aamir Khollam: 0.7%Interesting Engineering: 0.7%Anecdotal0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.1%No True Scotsman0.0%This article: 10.3%Aamir Khollam: 1.6%Interesting Engineering: 2.6%Ambiguity (Equivocation)10.3%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Gambler’s Fallacy0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.1%Middle Ground0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Personal Incredulity0.0%This article: 0.0%Aamir Khollam: 0.1%Interesting Engineering: 0.1%Special Pleading0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Genetic Fallacy0.0%This article: 6.6%Aamir Khollam: 1.1%Interesting Engineering: 1.7%Unattributed Quote6.6%This article: 8.7%Aamir Khollam: 0.8%Interesting Engineering: 0.7%Quote-first Misdirection8.7%This article: 13.2%Aamir Khollam: 3.2%Interesting Engineering: 3.9%Biased Writer Voice13.2%This article: 0.0%Aamir Khollam: 0.1%Interesting Engineering: 0.7%Indoctrination0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.0%Politically Left Leaning Bias0.0%This article: 0.0%Aamir Khollam: 0.0%Interesting Engineering: 0.1%Politically Right Leaning Bias0.0%This article: 0.0%Aamir Khollam: 8.9%Interesting Engineering: 10.7%Attempt to Sell a Product or S…0.0%

574 words analyzed.

Speakers

4speakers29%attributed speech410writer words
Voice mapSelect a segment to jump to its words
Writer's voice • 15 words • 100.0% coverageDepartment of War • 26 words • 0.0% coverageWriter's voice • 27 words • 100.0% coverageDepartment of the Navy • 14 words • 0.0% coverageWriter's voice • 9 words • 0.0% coverageWriter's voice • 6 words • 0.0% coverageWriter's voice • 24 words • 100.0% coverageWriter's voice • 3 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 27 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 16 words • 0.0% coverageWriter's voice • 16 words • 0.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 15 words • 0.0% coverageWriter's voice • 27 words • 0.0% coverageWriter's voice • 3 words • 0.0% coverageKirsten A. Davies • 6 words • 0.0% coverageKirsten A. Davies • 11 words • 100.0% coverageKirsten A. Davies • 18 words • 100.0% coverageKirsten A. Davies • 27 words • 0.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 25 words • 0.0% coverageWriter's voice • 5 words • 0.0% coverageWriter's voice • 9 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageBarry Tanner • 30 words • 0.0% coverageBarry Tanner • 32 words • 100.0% coverageWriter's voice • 17 words • 0.0% coverageWriter's voice • 37 words • 100.0% coverage
Selected voice

Barry Tanner

100%flagged-word coverage
62 attributed words38% of attributed speech83% writer coverage
0%27.5%55.0%Quote-first Misdirection+51.6 ptsWriter: 0.0%Barry Tanner: 51.6%51.6%Biased Writer Voice-18.5 ptsWriter: 18.5%Barry Tanner: 0.0%0.0%Unattributed Quote-6.6 ptsWriter: 6.6%Barry Tanner: 0.0%0.0%

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

Loading…
Loading…
Loading…

Analysis

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