IN THE UNITED STATES COURT OF FEDERAL CLAIMS Palantir Technologies Inc., Plaintiff , v. THE UNITED STATES, Defendant Case No. [XX-XXX] Judge [Name] DEFENDANT UNITED STATES’ BRIEF IN SUPPORT OF ITS CROSS-MOTION FOR SUMMARY JUDGMENT AND IN OPPOSITION TO PLAINTIFF’S MOTION FOR JUDGMENT ON THE ADMINISTRATIVE RECORD MEMORANDUM OF LAW I. DIA FULLY SATISFIED 10 U.S.C. § 3453: PALANTIR’S PROPRIETARY SOFTWARE FAILS TO MEET THE AGENCY’S ESSENTIAL OPERATIONAL REQUIREMENTS Plaintiff Palantir Technologies Inc. (“Palantir”) misconstrues the commercial item preference in 10 U.S.C. § 3453 and FAR Part 12 as a statutory mandate forcing the Defense Intelligence Agency (“DIA”) to adopt standard commercial platforms, regardless of suitability. It is not. Under 10 U.S.C. § 3453(a)(2) , the statutory preference for commercial products applies only “to the maximum extent practicable” and strictly where commercial offerings can “meet agency requirements.” While the DIA conducted extensive market research pursuant to 10 U.S.C. § 3453(c) , that research established that Palantir’s off-the-shelf platform cannot fulfill core intelligence capabilities without extensive, restrictive, and cost-prohibitive modifications. Section 3453 does not divest an executive agency of its statutory authority to define its own minimum operational needs ( see CHE Consulting, Inc. v. United States , 552 F.3d 1351, 1355 (Fed. Cir. 2008)). Because Palantir’s platform fails to meet the DIA's defined requirements, the DIA properly determined under 10 U.S.C. § 3453(d) that no suitable commercial alternative exists to fulfill the agency’s mission. II. PALANTIR’S RESTRICTIVE PROPRIETARY CLAIMS AND REFUSAL TO GRANT ADEQUATE DATA RIGHTS DISQUALIFY ITS PLATFORM AS A VIABLE COMMERCIAL OPTION Palantir’s lawsuit seeks to compel the DIA to accept licensing terms that violate federal acquisition regulations and threaten operational readiness. Under DFARS 227.7202-1(a) , commercial computer software may only be acquired under standard commercial licenses to the extent those licenses satisfy agency needs and comply with federal procurement law 1. Vendor Lock-In and IP Rights Withholding: Palantir’s commercial license model restricts source-code access and prohibits independent software modifications by the government or third-party contractors. This strict proprietary posture violates the government's statutory mandate under 10 U.S.C. § 3771 to ensure modular open systems architecture and retain necessary technical data rights for defense applications. 2. Legal and Operational Non-Viability: The DIA requires an adaptable software architecture capable of immediate, low-cost modifications by agency personnel in response to rapidly evolving national security threats. Palantir’s insistence on maintaining exclusive intellectual property control creates an impermissible single-vendor dependency. A product burdened by terms that compromise security integration and operational agility is legally and operationally non-viable under FAR 12.207 Gemini (2026) google.com III. PALANTIR’S STATUTORY INTERPRETATION WOULD PRODUCE ABSURD RESULTS, IMPAIR DEFENSE OPERATIONS, AND SQUANDER TAXPAYER FUNDS Palantir advances a radical interpretation of procurement law: that 10 U.S.C. § 3453 makes it unlawful for a defense agency to deploy customized, internally modifiable, cost-effective software whenever a commercial vendor offers a generic module in the same domain. This argument fails under settled canons of statutory construction and sound public policy. ● Avoidance of Absurd Results: Courts must reject statutory interpretations that lead to impractical or absurd outcomes ( Griffin v. Oceanic Contractors, Inc. , 458 U.S. 564, 575 (1982)). Forcing an intelligence agency to entrust mission-critical functions to a rigid, black-box commercial module—while prohibiting the government from deploying its own tailored, low-cost software—subverts national defense and yields an absurd result Congress never intended. ● Fiscal and Statutory Stewardship: The primary objective of the Competition in Contracting Act ( 10 U.S.C. § 3201 et seq. ) is to optimize federal spending and prevent wasteful expenditures. Forcing the DIA into recurring, exorbitant licensing fees for Palantir’s proprietary software—while criminalizing or barring lower-cost, custom-built agency alternatives—directly contravenes fiscal responsibility mandates and risks violating the Anti-Deficiency Act ( 31 U.S.C. § 1341 ). Because Palantir’s platform fails to satisfy minimum agency needs and imposes legally unacceptable licensing restrictions, the DIA’s procurement decision was rational, fully compliant with Title 10, and entitled to deference under the Administrative Procedure Act ( 5 U.S.C. § 706 ). Would you like me to draft the formal Statement of Facts or the specific Standard of Review section under APA / COFC rules to complete this motion? Gemini (2026) google.com Here is a concise draft of the argument section tailored for the brief. ARGUMENT I. The Applicable U.S. Code Does Not Compel the Agency to Adopt Inflexible, Overpriced Generic Software While federal procurement statutes express a general preference for commercial products, they do not mandate that an agency surrender its operational capabilities to an expensive, off-the-shelf generic module. Procurement statutes are designed to promote cost efficiency and functionality—not to force executive agencies into restrictive vendor lock-in. Nothing in the statutory text requires the Defense Intelligence Agency (DIA) to compromise core mission requirements or pay premium rates for standard commercial software that fails to meet specialized operational needs. The law encourages commercial solutions where feasible; it does not dictate the mandatory adoption of ill-fitting, non-customizable tools. II. Restrictive Proprietary Claims and the Denial of IP Rights Disqualify the Product and Render No Commercially Viable Option Available A commercial product is not "commercially viable" under federal procurement standards if it fails to grant the government the intellectual property and data rights necessary to fulfill its statutory mission. Here, the vendor’s insistence on broad proprietary claims and refusal to convey appropriate IP/source-code modification rights effectively disqualifies the product from meeting agency needs. Without the legal authority to inspect, modify, or maintain software, the agency cannot ensure operational continuity, security, or integration. Consequently, because no existing commercial offering provides the required IP rights and adaptability, no viable commercial alternative exists under the statute. III. Interpreting Procurement Law to Prohibit Low-Cost, Custom Agency Software Produces an Absurd Result Contrary to Public Policy To construe the statute as prohibiting agencies from utilizing or developing custom, modifiable, low-cost software would lead to an absurd and impractical result. ● Practical Impairment: Defense and intelligence operations demand tailored software that can adapt rapidly to dynamic threat environments. A rigid mandate banning custom code would paralyze critical agency functions. ● Fiscal Responsibility: Forcing the government to pay exorbitant licensing fees for generic commercial products—while criminalizing or prohibiting cost-effective, custom-built internal alternatives—directly undermines Congress’s intent to protect taxpayer dollars. Procurement law must be read with common sense: where commercial products are legally or operationally insufficient, the agency retains the clear authority to deploy tailored, modifiable, and cost-efficient software solutions. Would you like to tailor this brief to cite specific statutory provisions (such as 10 U.S.C. § 3453 / Gemini (2026) google.com FAR Part 12), or adapt the tone for a specific court filing format (e.g., Motion for Summary Judgment vs. Complaint response)? Gemini (2026) google.com Here is a breakdown of the legal statutes and core statutory arguments used by Palantir in its landmark 2016 lawsuit against the U.S. Army and its 2026 bid protest challenge against the Defense Intelligence Agency (DIA). 1. Palantir v. United States (U.S. Army) — 2016 In 2016, Palantir filed a suit in the U.S. Court of Federal Claims challenging the Army's procurement process for the Distributed Common Ground System–Army Increment 2 (DCGS-A2). Palantir argued that the Army unlawfully sought a custom-built software system instead of procuring commercially available technology. Key Statutes & Regulations ● Federal Acquisition Streamlining Act of 1994 (FASA) : The foundational statute governing the mandate for commercial procurement. ● 10 U.S.C. § 2377 ( Preference for Acquisition of Commercial Items ; now recodified under Title 10, Chapter 247): ○ 10 U.S.C. § 2377(a) : Mandates that the head of an agency shall ensure, “to the maximum extent practicable,” that agency requirements are fulfilled through commercial items. ○ 10 U.S.C. § 2377(c)(1) : Mandates that an agency “shall conduct market research appropriate to the circumstances... before developing new specifications for a procurement.” ○ 10 U.S.C. § 2377(c)(2) : Mandates that agency heads “shall use the results of market research to determine whether there are commercial items or... nondevelopmental items available that (A) meet the agency’s requirements; (B) could be modified to meet the agency’s requirements; or (C) could meet the agency’s requirements if those requirements were modified to a reasonable extent.” ● Federal Acquisition Regulation (FAR) Part 10 : Specifically FAR 10.001(a)(3) and 10.002 , which implement FASA’s market research requirements. ● 28 U.S.C. § 1491(b)(1) (The Tucker Act) : The jurisdictional statute granting the Court of Federal Claims authority to hear bid protests against federal agencies. Verbatim Claims & Arguments ● Palantir alleged that the Army violated statutory mandates by failing to give “[p]reference for acquisition of commercial items” prior to issuing a solicitation for custom development. ● The complaint argued that the Army’s market research was flawed because it failed to “determine whether there are commercial items” capable of meeting or being reasonably modified to meet the Army’s operational needs. 2. Palantir v. Defense Intelligence Agency (DIA) — 2026 Gemini (2026) google.com In mid-2026, Palantir filed a formal pre-award protest with the Government Accountability Office (GAO Docket No. B-424519.1) challenging a DIA solicitation for custom software development under its Advanced Systems for Technical Research and Analysis (ASTRA) program and related task orders. Key Statutes & Regulations ● Federal Acquisition Streamlining Act of 1994 (FASA) : Cited again as the primary legal constraint prohibiting unnecessary custom development. ● 10 U.S.C. § 3453 ( formerly 10 U.S.C. § 2377 ): The statutory preference for commercial products and services. ● National Defense Authorization Act (NDAA) for FY 2009 : Specific statutory provisions mandating the use of commercial software in defense procurement whenever possible. ● Defense Federal Acquisition Regulation Supplement (DFARS) Part 210 & FAR Part 10 : Federal regulations enforcing commercial item preferences and market research duties. Verbatim Claims & Arguments ● Palantir argued that DIA violated federal acquisition mandates requiring agencies to “procure commercially available technology to meet their needs to the maximum extent practicable.” ● Palantir alleged that DIA’s solicitation for custom software development was “wasting taxpayer money by continuing to develop the system internally” rather than evaluating and leveraging off-the-shelf commercial platforms that were already available. (Note: Following Palantir's initial May 2026 filing and a supplemental July 2026 protest, the DIA formally withdrew the disputed ASTRA solicitation in late July 2026.) Gemini (2026) google.com Several prominent tech vendors and defense contractors have leveraged the Federal Acquisition Streamlining Act of 1994 (FASA) and its modern codifications—specifically 10 U.S.C. § 3453 (formerly 10 U.S.C. § 2377 )—to challenge government procurement practices. These lawsuits generally allege that federal agencies unlawfully opted to build custom, "government-off-the-shelf" (GOTS) software or issue custom development contracts instead of evaluating and buying existing commercial technology. Key Lawsuits Filed Under FASA Commercial Preference Provisions 1. Percipient.ai, Inc. v. United States (2023–2025) ● Agency Involved: National Geospatial-Intelligence Agency (NGA) ● Statute at Issue: 10 U.S.C. § 3453 ● Summary: Percipient.ai, an AI baseline computer vision startup, filed a post-award bid protest in the U.S. Court of Federal Claims (COFC). They alleged that the NGA and its prime contractor (CACI) violated 10 U.S.C. § 3453 by developing custom computer vision software under the "SAFFIRE" program without conducting market research or considering Percipient’s commercial AI platform, Mirage ● Impact: The case became a major test of whether third-party commercial technology vendors (subcontractors/third parties who didn't bid directly as prime offerors) have legal standing to sue under § 3453. 2. SRA International, Inc. / CGI Federal v. United States ● Agencies Involved: Various (including Department of Defense & Civilian Agencies) ● Statutes at Issue: 10 U.S.C. § 3453 / 41 U.S.C. § 3307 (FASA statutory preferences), FAR Part 12 ● Summary: SRA International and other large system integrators have repeatedly filed bid protests at the Government Accountability Office (GAO) and COFC when agencies issued custom, cost-reimbursement task order solicitations. They argued the requirements were available commercially and that the government failed to justify why commercial terms under FAR Part 12/FASA could not meet its needs. 3. Pre-Palantir Lineage: Commercial Item Solicitations Challenges at GAO Before Palantir's 2016 suit established judicial precedent in the Federal Circuit, several vendors challenged solicitations under the original 10 U.S.C. § 2377 via GAO bid protests: ● Commercial Systems Integrators Protests (e.g., Matter of: CGI Federal Inc. ): Challenged agencies attempting to bundle requirements into monolithic non-commercial development contracts without performing the market research required under FASA. ● Commercial Aviation/Logistics Cases (e.g., Matter of: Northrop Grumman Technical Services ): Challenged Air Force and Army fleet maintenance solicitations where the military sought non-commercial, government-unique maintenance terms, arguing FASA mandated the use of standard commercial practices under FAR Part 12. Gemini (2026) google.com Why These Lawsuits Are Rare While FASA’s statutory commercial preference (10 U.S.C. § 3453) is powerful, bringing lawsuits on this basis is uncommon due to two major legal hurdles: 1. The "Interested Party" Standing Requirement: Under the Tucker Act (28 U.S.C. § 1491(b)), a company generally must be an actual or prospective prime bidder to have standing to sue. Non-bidding commercial tech companies often find it difficult to challenge custom government awards unless they formally submit a proposal or directly protest the solicitation terms prior to bid submission. 2. Agency Discretion on "Practicability": Section 3453 states commercial items must be procured "to the maximum extent practicable." Courts give substantial deference to defense and intelligence agencies when they claim commercial options do not meet specific mission requirements—unless, as in Palantir's case, the agency completely ignored required market research. Gemini (2026) google.com Here is the breakdown of the governing statutes and specific statutory language invoked by Palantir in its legal challenges against the U.S. Army in 2016 and the Defense Intelligence Agency (DIA) in 2026. 1. 2016 Lawsuit: Palantir USG, Inc. v. United States (U.S. Army) In its landmark 2016 bid protest over the Army’s Distributed Common Ground System Increment 2 (DCGS-A2) procurement, Palantir relied primarily on the Federal Acquisition Streamlining Act of 1994 (FASA) Primary Statute: 10 U.S.C. § 2377 (Note: Section 2377 was subsequently re-codified under Title 10 as 10 U.S.C. § 3453 ). Palantir cited three key statutory provisions under this section: A. Statutory Preference for Commercial Items — 10 U.S.C. § 2377(a) "The head of an agency shall ensure that— (1) requirements of the agency with respect to a procurement of supplies or services are stated in terms of— (A) functions to be performed; (B) performance required; or (C) essential physical characteristics; (2) such requirements are defined so that commercial items or, to the extent that commercial items suitable to meet the agency's needs are not available, nondevelopmental items other than commercial items, may be procured to fulfill such requirements; and (3) offerors of commercial items and nondevelopmental items other than commercial items are provided an opportunity to compete in any procurement to fill such requirements." B. Mandatory Market Research — 10 U.S.C. § 2377(c)(1) "The head of an agency shall conduct market research appropriate to the circumstances— (A) before developing new requirement documents for a procurement by that agency; and (B) before soliciting bids or proposals for a contract with an estimated value in excess of the simplified acquisition threshold..." C. Requirement to Evaluate Commercial Solutions — 10 U.S.C. § 2377(c)(2) "The head of an agency shall use the results of market research to determine whether there are commercial items or, to the extent that commercial items suitable to meet the agency's needs are not available, nondevelopmental items other than commercial items available that— (A) meet the agency's requirements; (B) could be modified to meet the agency's requirements; or (C) could meet the agency's requirements if those requirements were modified to a reasonable extent." Key Regulatory Framework ● FAR Part 12 (Acquisition of Commercial Items): Mandates that agencies acquire commercial items or nondevelopmental items to the maximum extent practicable. Gemini (2026) google.com ● FAR 10.001: Mandates procedures for collecting and analyzing market research before issuing solicitations. 2. 2026 Protests: Challenges Against Defense Intelligence Agency (DIA) Palantir invoked the same commercial preference framework against the DIA regarding solicitations like ASTRA (Advanced Systems for Technical Research and Analysis) and MARS (Machine-assisted Analytic Rapid-repository System). Primary Statutes & Provisions Used A. Re-codified FASA Mandate — 10 U.S.C. § 3453 (formerly 10 U.S.C. § 2377) 10 U.S.C. § 3453(a): "The Secretary of Defense shall ensure that, to the maximum extent practicable, requirements of the Department of Defense with respect to a procurement of supplies or services are stated in terms of functions to be performed, performance required, or essential physical characteristics, and are defined so that commercial products or commercial services... may be procured to fulfill such requirements." B. Commercial Software Mandate — National Defense Authorization Act (NDAA) for FY 2009 (Section 803 / Codified across Title 10 Defense Procurement provisions) Mandates that the Department of Defense shall fulfill software requirements through the acquisition of commercial computer software "whenever available and practicable" rather than through custom development. C. Federal Acquisition Regulation & Defense Supplement ● FAR Part 12 & DFARS Part 212: Mandates commercial preferences and restricts agencies from soliciting custom, cost-plus development contracts when commercial software platforms already exist or can be modified to meet mission requirements. ● 41 U.S.C. § 3307: The civilian agency equivalent under FASA, establishing statutory preference for commercial items across non-DoD intelligence/civilian procurement authorities. Gemini (2026) google.com Distributed Common Ground System – Army (DCGS-A): Technical Architecture, Legal Precedents, and Operational Evolution The Distributed Common Ground System – Army (DCGS-A) serves as the United States Army’s primary intelligence, surveillance, and reconnaissance (ISR) enterprise system. Designed to task organic and non-organic sensors, process and exploit multi-domain data, and disseminate actionable threat, weather, and terrain intelligence across all operational echelons, DCGS-A constitutes a core pillar of command and control architecture. Over its multi-decade acquisition lifecycle, DCGS-A has transitioned from a monolithic software suite aimed at replacing legacy single-source intelligence systems into a modernized, software-defined enterprise. This transition highlights a broader shift in Department of Defense (DoD) software acquisition strategies. It encompasses foundational program decisions, a landmark legal ruling that redefined commercial procurement under the Federal Acquisition Streamlining Act (FASA), and the eventual shift toward disaggregated software drops and artificial intelligence (AI)-enabled targeting nodes. 1. Architectural Foundations and Historical Evolution (2002–2014) System Functionality and Mission Scope The DCGS-A framework was established to solve a systemic operational challenge: the fragmentation of battlefield intelligence across legacy, single-source processing systems. Originating from the broader Department of Defense Distributed Common Ground/Surface System (DCGS) family of systems initiated in 1998, DCGS-A was structured as the Army’s component to integrate signals intelligence (SIGINT), geospatial intelligence (GEOINT), human intelligence (HUMINT), measurement and signature intelligence (MASINT), and open-source intelligence (OSINT) into a single operational picture. In terms of data flow and functional architecture, raw data collected across multi-domain sensor layers—spanning space, aerial, terrestrial, and cyber assets—is ingested into the system via the DCGS Integration Backbone (DIB), which establishes shared information standards and interoperability protocols. The DIB bridges fixed enterprise nodes, such as high-capacity Intelligence Processing Centers and cloud infrastructure at strategic echelons, with mobile tactical ground terminals. These nodes process, correlate, and index incoming multi-INT streams, feeding a combined battlefield visualization directly to intelligence analysts and operational commanders. DCGS-A provides intelligence tasking, processing, exploitation, and dissemination (TPED) capabilities. Analysts from battalion intelligence sections up to Echelons Above Corps (EAC), Military Intelligence Brigades – Theater (MIB-T), and Special Operations Forces (SOF) utilize Gemini (2026) google.com DCGS-A to execute running estimates, perform target nomination, and maintain situational understanding across Secret and Top Secret/Sensitive Compartmented Information (TS/SCI) enclaves. Interoperability across joint, interagency, intergovernmental, and multinational (JIIM) partners is achieved through adherence to the DIB standard. Legacy System Consolidation and Early Acquisition Milestones Prior to DCGS-A, Army intelligence depended on discrete, specialized systems of record that operated in informational silos. In 2002, the Army initiated a consolidation strategy to merge nine legacy system families—which eventually expanded to 16 independent software baselines—into a unified enterprise network. Prominent legacy systems absorbed into the program include the All Source Analysis System (ASAS) for all-source intelligence correlation; the Digital Topographic Support System (DTSS) for geospatial data management and map reproduction; the Tactical Ground Station (TGS) and Operational Ground Station (OGS) for direct sensor downlinks; and the Counterintelligence and Human Intelligence Automated Tool Set (CHITS) for HUMINT collection. The Joint Requirements Oversight Council (JROC) approved the original DCGS-A Capability Development Document (CDD) on October 31, 2005. Following a Course of Action (COA) analysis conducted in Fiscal Year (FY) 2005, the Milestone Decision Authority (MDA) codified an Acquisition Strategy that led to Milestone B approval on April 7, 2007. The program operated under an incremental software release model leveraging commercial-off-the-shelf (COTS) computing hardware to accelerate capability delivery. Milestone / Decision Event Date Key Architectural Objective / Outcome Primary Sources DoD DCGS Enterprise Initiative 1998 Establishes multi-service interoperability vision via DCGS Integration Backbone (DIB). Army Legacy Consolidation Directive 2002 Directs merging of 9 legacy intelligence system families into DCGS-A. JROC CDD Approval Oct 31, 2005 Formally validates joint operational requirements for DCGS-A enterprise. Milestone B Approval Apr 7, 2007 Authorizes entry into Engineering and Manufacturing Development (EMD). DSB 1.0 IOT&E Assessment May–Jun 2012 DOT&E rates baseline Not Effective, Not Suitable, and Not Survivable. Increment 1 Release 1 Approval Nov 2012 Software reconfigured without TS/SCI enclave Gemini (2026) google.com Milestone / Decision Event Date Key Architectural Objective / Outcome Primary Sources to address critical security gaps. Full Deployment Decision (FDD) May 2014 Defense Acquisition Executive approves Army-wide fielding via ARFORGEN cycle. Increment 1 Release 2 FOT&E May–Sep 2015 Rated effective and suitable, but vulnerable to enterprise network cyber threats. Software Baseline Progression and Operational Testing Performance The initial operationalization of DCGS-A depended on early deployment configurations tailored for urgent operational needs in Southwestern Asia. The Joint Intelligence Operational Capability-Iraq (JIOC-I) and the enterprise data repository known as the DCGS-A "Brain" were deployed as Quick Reaction Capabilities (QRCs) to process multi-source sensor feeds over SIPRNET and JWICS. The formal acquisition baseline, designated DCGS-A Software Baseline (DSB) 1.0, underwent Initial Operational Test and Evaluation (IOT&E) conducted by the Army Test and Evaluation Command (ATEC) from May to June 2012 . The Director, Operational Test and Evaluation (DOT&E) subsequently evaluated DSB 1.0 as operationally not effective, not suitable, and not survivable . System crashes, overly complex user interfaces, database synchronization failures in low-bandwidth environments, and severe cybersecurity vulnerabilities impeded operational performance. To recover from these shortfalls, the Army reengineered the software package into Increment 1, Release 1 , removing the problematic TS/SCI operational enclave to remediate core Information Assurance defects before broader deployment . Subsequent iterations led to Increment 1, Release 2 , which combined 16 legacy applications into a standardized tactical command and control architecture . During Follow-on Operational Test and Evaluation (FOT&E) in 2015 at the Network Integration Evaluation (NIE 15.2), DOT&E reported on January 29, 2016, that Release 2 achieved operational effectiveness and suitability . However, the system remained evaluated as not survivable against adversary cyber threats due to systemic vulnerabilities within the broader Army tactical network infrastructure . The Defense Acquisition Executive (DAE) authorized the program for Full Deployment in May 2014, initiating service-wide fielding across units undergoing the Army Forces Generation (ARFORGEN) cycle . This full deployment was projected to yield $1.2 billion in life-cycle cost savings between FY2012 and FY2034 through hardware rationalization and legacy maintenance reductions . Physical Hardware Architecture and Infrastructure Modernization Because DCGS-A serves multiple operational echelons, its physical deployment profile required hardware variants matched to tactical mobility and computational requirements. Fixed regional sites and expeditionary command posts rely on scalable server infrastructure, while Gemini (2026) google.com forward-deployed units employ mobile ground terminals. Hardware Platform Variant Targeted Echelons Physical Computing & Architectural Specifications Primary Sources Intelligence Processing Center v1 (IPCv1) Fixed Sites / Strategic Enclaves High-capacity data center chassis housing 384 physical CPU cores, 4 TB RAM, and 1 PB raw storage capacity. Intelligence Processing Center v2 (IPCv2) Brigade Combat Team, Division, Corps Expeditionary, self-contained, containerized server stack providing localized PED and analytical databases. Tactical Server Infrastructure (TSI v1–v5) Corps down to Brigade Command Posts Standardized hosted server hardware. Legacy variants operated VMware; modernizing to Hyper-V and cloud nodes. Tactical Ground Station (TGS) / OGS Operational Units / Division / Corps Mobile sensor processing terminals (e.g., AN/TYQ-224B) receiving direct aerial and surface ISR sensor downlinks. Geospatial Intelligence Workstation (GWS) All Echelons Ruggedized COTS mobile workstations (formerly DTSS-D) hosting specialized GIS, terrain, and map production suites. Maintaining these hardware variants introduced significant infrastructure challenges . The compute layer relied heavily on proprietary hypervisors (such as VMware) to run virtualized software components down to the brigade level . Driven by escalating licensing costs and the need to deploy microservices at the tactical edge, the U.S. Army Communications-Electronics Command Software Engineering Center (CECOM SEC), alongside Project Manager Mission Command, initiated a structural shift . For TSI v1 and v5 variants, SEC executed a non-destructive, in-place migration from VMware to Microsoft Hyper-V to preserve unit data while reducing licensing burdens . Concurrently, DCGS-A software components were modernized into a container-native architecture utilizing Red Hat OpenShift . Containerization eliminated hypervisor overhead, automated software deployments, reduced technical debt, and enabled modular DevSecOps updates across tactical servers. Gemini (2026) google.com 2. The Federal Acquisition Legal Watershed: Palantir USG v. United States (2015–2018) The Increment 2 Solicitation Controversy In October 2015, the Defense Acquisition Executive approved the Materiel Development Decision (MDD) for DCGS-A Increment 2 . Envisioned as a major capability upgrade, Increment 2 was intended to replace the aging data architecture of Increment 1 with an advanced data fabric, enterprise big-data analytics, enhanced cloud computing, and automated target recognition tools. On December 23, 2015, the Army Contracting Command – Aberdeen Proving Ground (ACC-APG) issued Request for Proposals (RFP) No. W56KGY-16-R-0001 for DCGS-A Increment 2. The procurement strategy was structured as a single-award, cost-reimbursement contract for a Lead System Integrator. The selected vendor would be tasked with custom-building a new software data architecture and integrating custom analytics from the ground up over a multi-year development cycle. Palantir USG, Inc., vendor of the commercial enterprise analytical software platform Palantir Gotham , challenged the procurement strategy. Palantir argued that its commercially available software platform already satisfied the core data management and analytical requirements of Increment 2. Furthermore, Palantir asserted that commanders in active combat theaters had repeatedly submitted operational requests for commercial software due to usability issues with DCGS-A Increment 1. The legal conflict hinged on whether the Army's custom software development path was permissible under the Federal Acquisition Streamlining Act of 1994 (FASA), which required market research to evaluate commercial solutions prior to launching bespoke developmental projects. The Army's solicitation required vendors to possess an audited DCAA accounting system suitable for custom cost-plus developmental contracts and required vendors to bid on software engineering services rather than providing commercial software licenses. After the Government Accountability Office (GAO) denied its initial administrative bid protest, Palantir filed a pre-award bid protest in the U.S. Court of Federal Claims on June 30, 2016. Statutory Basis and Judicial Rulings Palantir's lawsuit centered on a violation of FASA, codified at 10 U.S.C. § 2377 (later recodified under 10 U.S.C. § 3453). FASA explicitly mandates that federal acquisition agencies must, to the maximum extent practicable, state requirements functionally, conduct comprehensive market research before issuing solicitations or developing custom specifications, and determine whether the agency's requirements can be met by available commercial items or commercial items modified to a reasonable extent. Palantir contended that the Army acted arbitrarily and capriciously by failing to execute meaningful market research regarding available COTS enterprise software platforms, instead issuing an RFP designed exclusively for custom software development. On October 31, 2016, Senior Judge Marian Blank Horn of the U.S. Court of Federal Claims ruled in favor of Palantir and issued a permanent injunction halting RFP W56KGY-16-R-0001. The court found that the Army's market research was fundamentally flawed. The service had issued Requests for Information (RFIs) that focused heavily on vendor capabilities to perform Gemini (2026) google.com custom software engineering rather than assessing whether commercial products could fulfill system gaps. The Department of Justice appealed the decision to the U.S. Court of Appeals for the Federal Circuit. On September 13, 2018, the Federal Circuit affirmed the Claims Court’s injunction ( Palantir USG, Inc. v. United States , 904 F.3d 980). The appellate court affirmed that 10 U.S.C. § 2377 creates a binding statutory obligation for military departments to perform thorough market evaluations of commercial products before committing public funds to custom developmental software. Acquisition Reform Impact and Strategy Pivot The legal outcome in Palantir v. United States altered Department of Defense software acquisition policy, serving as a legal benchmark across all services. The decision forced the Army to abandon its monolithic single-award contract strategy for DCGS-A Increment 2. Instead, Project Manager DCGS-A disaggregated Increment 2 into a series of modular, competitively awarded procurements designated as Capability Drops . By dividing the system into discrete functional components—separating tactical edge tools from cloud data infrastructure—the Army enabled commercial technology vendors to compete directly against traditional defense integrators. 3. Disaggregated Procurement: Capability Drops 1 & 2 Capability Drop 1 (CD1): Tactical Commercial Analytics Capability Drop 1 was structured to address the operational software and hardware requirements of intelligence analysts deployed at Brigade Combat Teams and lower tactical echelons operating in bandwidth-constrained or disconnected environments. Rather than writing custom software, the Army sought a fieldable COTS solution that combined hardware and software into a ruggedized, deployable kit. Following an open procurement competition between Raytheon and Palantir Technologies, the Army awarded the DCGS-A Increment 1 Capability Drop 1 contract to Palantir in March 2019. The 10-year indefinite-delivery/indefinite-quantity (IDIQ) contract carried an overall ceiling value of $876 million. CD1 delivered an intuitive, commercially derived user interface, disconnected offline data synchronization, automated entity extraction, and map overlay tools, replacing legacy, complex software modules at the tactical edge. Capability Drop 2 (CD2): Cloud Enterprise Data Architecture Capability Drop 2 was designed to modernize the strategic and operational enterprise layers of DCGS-A. CD2 serves as the cloud-based data fabric and advanced analytics engine for the Army, replacing the legacy DCGS-A "Brain" data warehouse. Operational Parameter Capability Drop 1 (CD1) Specifications Capability Drop 2 (CD2) Specifications Primary Sources Operational Focus Tactical Edge & Austere Environments (Battalion / BCT) Strategic Enterprise & Operational Echelons (Corps, EAC, MIB-T) System Delivery Combined COTS Commercial Software Gemini (2026) google.com Operational Parameter Capability Drop 1 (CD1) Specifications Capability Drop 2 (CD2) Specifications Primary Sources Model Software and Ruggedized Compute Hardware Solution integrated onto Cloud Infrastructure Primary Contractors Palantir Technologies Inc. Palantir Technologies Inc. (Selected after multi-vendor survey) Architectural Environment Localized server stacks / Disconnected Operational State Cloud-native deployment on Army Commercial Cloud (AC2SP) Core Functions Entity correlation, localized map rendering, tactical alerts Enterprise data ingest, multi-INT cross-domain fusion, big data analytics CD2 is designed to operate seamlessly across Secret and TS/SCI security domains. The system continuously ingests, parses, indexes, and correlates structured and unstructured intelligence streams from hundreds of Joint, Interagency, and Intelligence Community (IC) feeds. In FY22, the Army migrated the CD2 application stack to execute on the enterprise Army Commercial Cloud Service Platform (AC2SP) Operational Evaluation and DOT&E Testing Deficiencies Despite operational adoption of CD2 tools, the program encountered testing compliance challenges. The Army scheduled an official Operational Test for DCGS-A CD2 in October 2022 to evaluate operational effectiveness, suitability, and survivability on the AC2SP cloud infrastructure. However, the Director, Operational Test and Evaluation (DOT&E) refused to approve the Army's Operational Utility Assessment Plan. DOT&E cited structural inadequacies in the Army’s data collection, reduction, and analysis methodologies. While the Army's evaluation plan relied on subjective observations, user surveys, and manual screenshot collection, DOT&E deemed these methods insufficient to quantitatively evaluate the accuracy, latency, or completeness of the synthesized battlefield picture. As a result, the Army proceeded with the October 2022 assessment as a non-binding "customer test" rather than a formal operational test. Consequently, while the Army released DCGS-A CD2 software for operational use by warfighters, DOT&E recorded that formal operational testing on AC2SP remained incomplete through FY23, recommending rigorous quantitative instrumentation prior to final full-scale fielding. 4. Modernization Realignment and Next-Gen Enterprise (2020–Present) Reorganization to Project Manager Intelligence Systems and Analytics (PM IS&A) Gemini (2026) google.com In June 2020, the U.S. Army executed an organizational realignment to accelerate technological transition . The legacy Project Manager DCGS-A structure was formally reorganized into Project Manager, Intelligence Systems and Analytics (PM IS&A) under the Program Executive Office for Intelligence, Electronic Warfare and Sensors (PEO IEW&S) . Under PM IS&A, DCGS-A was designated as an inactive Major Defense Acquisition Program (MDAP). The Army announced that no further numerical "Capability Drops" would be initiated for DCGS-A. Instead, existing legacy features are being disaggregated and migrated into next-generation, software-defined program offices: ● Army Intelligence Data Platform (AIDP): The evolution of CD2/data fabric capability, incorporating continuous integration/continuous deployment (CI/CD) through a DevSecOps software framework. ● Intel Apps (IA): Modular, specialized analytical software applications designed to replace heavy legacy software suites with containerized microservices . ● Geospatial Intelligence Modernization (GWS): Standardized, modular mapping and terrain analysis suit