The Pentagon’s War Data Platform: what it buys is the integration
7 min read
On 28 July, trade press headlines a $821 million contract for the Pentagon’s AI data platform. In the federal record, the same award appears as a delivery order signed on 25 June, with $102,250 obligated. Neither figure is false. But the word that explains what was actually bought is not a number: it sits in the official description, and it is “CORE INTEGRATION”.
What the record says
The public record — which we queried through the USAspending API, the interface that exposes FPDS data — is precise and bare. Contract identifier (PIID): 47QFCA26F0023, type DELIVERY ORDER, signed on 25 June 2026. The description, verbatim and all in capitals as it appears in the register: “THIS AWARD IS IN SUPPORT OF THE CHIEF DATA ARTIFICIAL INTELLIGENCE OFFICE CDAO WAR DATA PLATFORM WDP CORE INTEGRATION CI”. The obligated amount is $102,250; the fields that would carry the value including options are not populated.
The awarding body is the General Services Administration, through the Federal Acquisition Service and the GSA FAS AAS FEDSIM office. The funding body is the Department of Defense, through the Immediate Office of the Secretary of Defense and an office that in the register is named, verbatim, “OFFICE, CHIEF DIGITAL & AI OFFICER”. This detail is worth pausing on: the data platform does not belong to a single military service — it belongs to the top of the Department.
The awardee is Accenture Federal Services LLC (UEI C47BNA8GM833), based in Arlington, Virginia. The solicitation — 47QFCA26R0014, an MAFO (multiple award fair opportunity) procedure — received five offers. Place of performance: Falls Church, Virginia, and at award-search level the period runs from 28 July 2026 to 27 July 2027.
Who buys on whose behalf
The funder and the awarding body are not the same entity. Defense provides the funds; the buyer, technically, is the General Services Administration, through the FEDSIM office — a contracting vehicle built to let other federal agencies route purchases through it. Buying this way means inheriting a competition already set up: the field of competitors — five offerors here — and the qualification procedures have already been managed by whoever runs that vehicle, not by whoever will use the outcome. The price is one extra hop between whoever uses the system — the CDAO — and whoever holds the contract on paper.
This is not an anomaly: it buys speed in exchange for a layer of intermediation. In Italy the equivalent question is which central purchasing body lands the contract, and how much that choice shapes timelines, requirements and which bidders are admitted.
The two figures
A five-year ceiling is not money spent, and an amount obligated on one delivery order is not the value of a programme. The two figures do not contradict each other — they measure different things. Federal News Network, on 28 July, headlined a contract worth “up to $821 million over five years” — a ceiling, not spending — attributing the figure to HigherGov, a private service tracking federal procurement, not a government announcement. At the time of our query, the USAspending fields carrying the value including options are not populated: that ceiling, on the register, cannot be read.
The word that matters: integration
The word that matters in the official description is not “platform”: it is CORE INTEGRATION. The Department is not buying a new product to install. It is buying the work of holding together data flows that already exist and belong to different systems — pipelines, schemas, matching between identifiers, quality rules, continuity of service. Federal News Network describes the War Data Platform as a collection point for battlefield information linking hundreds of military data feeds processed by AI applications, to assist troops and speed up decisions, with the goal — as reported by the outlet — of integrating over 1,500 data sources, commercial and military. The same article quotes, on the required performance: “Support critical WDP data operations, the integration of infrastructure and platform tools, robust cybersecurity measures, and comprehensive service desk capabilities”, to ensure “seamless interoperability”.
This is the layer nobody sees and everything else rests on. For a European reader — large enterprise, defence, public administration, healthcare — the lesson is not about the front-end software, which can be swapped out: it is about who holds the map of where the data runs once the integrator walks away. It is the same question we raised reading about who builds Mercury Systems’ ontology: the value — and the risk — sit in the middle layer, not the end application.
How we check it
When a client brings us news about a supplier, the first thing we do is look up the award in the public register of the agency that made it, not in the article reporting it. We read the official description rather than the headline: that is where you see whether you are buying a product or a body of integration work. We separate the obligated amount from the contractual ceiling, because conflating them produces wrong estimates a budget later gets built on. And we always note who awards and who funds, because — as here — they are rarely the same party, and they answer to different rules.
See the service · Talk to an engineer
One line in the register worth a question
Among the categories the federal register attaches to the recipient is, alongside others, the entry “Foreign Owned”; in the register’s recipient hierarchy, the parent company listed for Accenture Federal Services is Novetta Solutions, LLC. These are classifications from the federal information system, not judgements, and we treat them with the same precision as a contract number. The point of interest for a European reader is not an insinuation about Accenture: it is that a state entrusts the integration of its own defence data platform to a commercial operator whose ownership is registered and publicly searchable, and nobody treats this as an anomaly — because the security perimeter is defined by contract, not by the shareholder’s nationality. The question worth turning on ourselves is different: in our own contracts, is that information — who actually owns the supplier we hand our data integration to — just as readable?
What a European organisation can take from this
- Look up the award in the register of the agency that made it, not in the news article reporting it.
- Distinguish the contractual ceiling, the base value and the obligated amount, and ask which of the three figures is the one written into the contract that actually concerns you.
- Read the official description of the work being performed: that is where you find out whether you are buying a product or the work of keeping it integrated with everything else.
- Ask, in writing, who owns the pipelines, schemas and identifier mappings at contract end — not just who owns the software.
- Always check who awards and who funds: they are often two different agencies, with different rules on transparency and accountability.
The two axes, applied
Complying: verifying an award — official description, obligated amount checked against the stated ceiling, awarding agency versus funding agency, the supplier’s ownership structure — becomes a check that runs against the client’s own contracts and documents, with a dated supplier register ready for an inspection or a board.
Deciding: here the case speaks for itself. What the Department of Defense is buying is exactly what we build at organisational scale: plants, archives, management systems, sensors and scattered documents held together in a single operating model — the organisation’s data lake becoming one thing — on which AI agents execute decisions with a human operator in command, for large enterprises, defence, public administration and healthcare. The difference we claim sits in ownership of the integration layer: ontology, pipelines and identifier mappings stay with the client, because that is the layer that cannot be repurchased once the integrator changes.
Always in two modes: on-premise, on autonomous machines that do not require deep integration into the client’s network, or dedicated cloud with a data centre in Italy — always with shared management: you should not need to already have someone in-house administering AI systems.
Want to know whether the contract you are about to sign buys a product or the integration — and who will own it afterwards? Let’s talk it through, at no cost for the first session.