# DIMHRS: the billion-dollar military HR and pay system that was never fielded GAO tracked about $766 million spent on DIMHRS by March 2008 and roughly $1 billion through FY2009 for a joint military pay system cancelled in 2010. Author: J.A. Watte Published: July 16, 2026 Source: https://jwatte.com/blog/dimhrs-military-hr-payroll-failure/ --- A soldier in the National Guard moves from a weekend drill status to active-duty orders, deploys overseas, comes home, and shifts back again. At each of those transitions, the pay and the personnel record have to move with the person. For years, that handoff ran through a tangle of separate service systems that did not talk to one another cleanly, and troops paid the price in late checks, wrong amounts, and records that did not follow them. The Defense Integrated Military Human Resources System, known by the acronym DIMHRS, was the Pentagon's attempt to fix that with one joint personnel-and-pay system for the entire uniformed force. It was initiated in 1998, absorbed roughly $766 million by early 2008 and about $1 billion counting projected spend through fiscal 2009, and it was never fielded department-wide before the joint program was cancelled in 2010. This post follows the money and the record. The failure is real and documented by the Pentagon's own leaders. The mission behind it was also legitimate and genuinely hard, and part of the work was salvaged. Both of those things are true, and the sources let them sit side by side. ## What DIMHRS was supposed to be In February 1998, the Department of Defense initiated a program to design and implement what the Government Accountability Office described as a "joint, integrated, standardized personnel and pay system for all military components (including active and reserve components)." That is the ambition in one sentence: take the Army, Navy, Air Force, and Marine Corps, active and reserve, and put their human-resources and payroll functions on one common platform. The scale of what it was replacing is part of why the goal mattered. According to DoD program descriptions and press accounts, DIMHRS was meant to subsume more than 90 legacy military personnel and pay systems. GAO's own reporting refers to "numerous military component-unique personnel and pay systems" without printing an exact count, so the "more than 90" figure is best attributed to DoD descriptions and trade press rather than to GAO. Either way, the problem was real: aging, stovepiped systems that struggled most at exactly the moments when troops moved between statuses. It is worth being precise about the timeline from the start. The 1998 date is when the program was initiated. Full-scale contract development ramped up later. The Navy, acting as the department's contracting authority for the joint effort, awarded Northrop Grumman a development contract of about $281 million in September 2003. So while the program's life spans roughly a decade or more, the heavy build did not begin in 1998. ## Who built it DIMHRS was not a single-vendor project, and getting that right matters for an honest account. Northrop Grumman's information technology arm was the systems integrator and developer. The underlying commercial-off-the-shelf software was PeopleSoft, the human-resources platform that Oracle acquired in 2005. The contractor team also drew in other firms, including Accenture and CACI and smaller businesses. It is often described as one of the largest ERP and PeopleSoft human-resources implementations ever attempted. One attribution note is worth flagging, because it is easy to get wrong. GAO's 2008 report on the program names no vendor. It refers only to software "referred to as a commercial-off-the-shelf product." The Northrop Grumman and PeopleSoft attribution rests on Northrop Grumman's own press release and on trade-press reporting, not on the GAO document. The management side has its own anchor: DIMHRS was acquired by the Department's Business Transformation Agency in October 2005, which oversaw it through the troubled middle years. ## What the record establishes The clearest primary account of both the spend and the schedule is GAO report GAO-08-927R, issued in September 2008. Two findings from it carry most of the weight of this story. The first is money. GAO stated that DoD had expended approximately $766 million on DIMHRS as of March 31, 2008, with an estimated additional $286 million projected through fiscal year 2009. Added together, that is the source of the widely repeated "roughly $1 billion" figure. It is important to read that total correctly: it is spent-plus-projected through 2009, not a lump sum that had all been outlaid at the moment the program ended. The second is schedule. GAO listed a sequence of planned Army deployment dates that kept slipping: April 2006, April 2008, July 2008, and October 2008 were all postponed, with deployment then rescheduled to March 2009. Four announced fielding dates came and went. The joint system was never deployed across the department. A separate and commonly cited accounting puts the figure at about $850 million spent over roughly eleven years, counted from 1998 to the 2010 cancellation. That number and GAO's roughly $1 billion "through fiscal 2009" figure are not a contradiction. They are two different accountings: one is money actually spent measured at cancellation, the other is spent-plus-projected measured through 2009. The most defensible way to state it is the one this post uses: about $766 million spent as of March 2008, roughly $1 billion counting projected spend through fiscal 2009 per GAO, and commonly cited in the $850 million to $1 billion range at cancellation. ## The timeline, dated - **February 1998:** DoD initiates DIMHRS to build a single joint personnel-and-pay system for all military components (GAO-08-927R). - **September 2003:** The Navy, as contracting authority, awards Northrop Grumman a development contract of about $281 million (Northrop Grumman press release). - **October 2005:** The Business Transformation Agency takes over management of the program. - **2006 through 2008:** Planned Army deployment dates of April 2006, April 2008, July 2008, and October 2008 are all postponed (GAO-08-927R). - **January 16, 2009:** A Deputy Secretary of Defense memorandum directs a restructuring, transitioning the program's "core" toward the individual military departments. - **March 2009:** The then-current rescheduled deployment target (GAO-08-927R). - **February 2010:** Secretary of Defense Robert Gates and Joint Chiefs Chairman Admiral Mike Mullen announce the cancellation of the joint department-wide program in Senate Armed Services Committee testimony. Two words in that timeline deserve care. The January 2009 action was a restructuring, directed by memo, that pointed the work toward the individual services. The February 2010 action was the public cancellation of the joint department-wide program. The effort was scaled back and redirected to service-specific systems rather than simply erased. Some earlier accounts attached the January 2009 restructuring date to an older GAO report from 2005; that source predates the event and cannot document it. The restructuring is anchored by the January 16, 2009 DoD memorandum. ## What the Pentagon's own leaders said The bluntest verdicts on DIMHRS came from inside the building. Testifying before the Senate Armed Services Committee, Admiral Mullen said flatly, "This program has been a disaster." Secretary Gates offered the line that has followed the program ever since: "what we've gotten for a half billion dollars is an unpronounceable acronym." Gates's phrasing carries one trap worth defusing. His "half billion dollars" understated the actual spend. GAO tracked roughly double that figure, about $1 billion through 2009, and later accounting notes that his cost estimate was short by about half. So the Gates quote is useful for the human and political weight of the moment, not as an accurate total. Both quotes come from congressional testimony reported by Stars and Stripes; a direct hearing transcript would harden them further, but the sourcing is solid. ## What happened to the money and the work After the joint program was cancelled, the services fell back on their own personnel and pay systems. The Marine Corps, for example, continued with its existing Total Force system. That is the plain waste side of the ledger: roughly a decade of effort and on the order of $850 million to $1 billion, with no fielded joint system to show for it at the point of cancellation. But the technical work was not thrown away entirely. The Army carried the DIMHRS core forward into a successor program, the Integrated Personnel and Pay System-Army, known as IPPS-A. IPPS-A reused the PeopleSoft-based technical solution and the hard lessons from DIMHRS, and it is important not to blur the two. IPPS-A is a distinct, Army-only successor. It reached full deployment years later, in the 2022 to 2023 window. Calling IPPS-A a continuation of DIMHRS, as if they were the same program, gets both the accounting and the history wrong. DIMHRS was cancelled; IPPS-A is what part of it became for one service. ## The honest failure critique By the measures the Pentagon itself used, DIMHRS is a textbook federal ERP failure. It ran for roughly a decade, consumed on the order of $850 million to $1 billion, and was never fielded across the department. Deployment slipped through at least four announced dates before the joint program was restructured and then cancelled. Its own senior leaders described it as a disaster and as money spent for an acronym. It sits in the same cautionary category as other large commercial-off-the-shelf modernization efforts that collapsed under scope, requirements churn, and the difficulty of integrating across service and agency silos. The Air Force's Expeditionary Combat Support System, another PeopleSoft-based ERP effort, is a close companion in the federal record, though it is a separate program with its own figures that should not be merged with DIMHRS. The pattern in both is familiar: an ambitious joint or enterprise-wide system, a heavy reliance on customising commercial software, and a schedule that kept moving right until the money and the patience ran out. ## The honest mission defense The other half of the ledger is just as real. The problem DIMHRS was built to solve was legitimate and genuinely hard. The Department was running dozens of aging, stovepiped personnel and pay systems, and the people most hurt by that fragmentation were Guard and Reserve troops who moved between duty statuses and suffered chronic pay and record errors as a result. Unifying human resources and pay across four services, active and reserve, into one standardized joint system is one of the largest and most complex ERP problems anyone has attempted, in or out of government. Part of the failure reflects that inherent difficulty, not only mismanagement. And the effort was not a total loss. The Army's IPPS-A inherited the DIMHRS technical solution and lessons and, years later, delivered a modern integrated personnel-and-pay system for the Army. The waste critique and the mission's real value coexist. Roughly a billion dollars bought no joint system in 2010, and the underlying need was real enough that the government kept solving it, at the service level, with tools DIMHRS helped build. One frame to keep clean at the close: DIMHRS is a spent-and-wasted story, not a missing-money story. The record does not allege that funds vanished or were unaccounted for. It documents money spent, over years, on a joint system that was never fielded before the department pulled the plug and salvaged what it could for one service. That distinction is the difference between a program that failed and a program that was corrupt, and the sources here support only the former. ## Fact-check notes and sources - DoD initiated DIMHRS in February 1998 to build a "joint, integrated, standardized personnel and pay system for all military components (including active and reserve components)": [U.S. GAO, GAO-08-927R (September 2008)](https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-08-927R/html/GAOREPORTS-GAO-08-927R.htm). 1998 is program initiation; heavy contract development ramped later. - DoD had expended approximately $766 million as of March 31, 2008, with an estimated additional $286 million projected through fiscal year 2009 (roughly $1 billion spent-plus-projected): [GAO-08-927R](https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-08-927R/html/GAOREPORTS-GAO-08-927R.htm). - Planned deployment dates of April 2006, April 2008, July 2008, and October 2008 were postponed, with deployment rescheduled to March 2009: [GAO-08-927R](https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-08-927R/html/GAOREPORTS-GAO-08-927R.htm). - Program goal language, three-phase scope, and management deficiencies: [U.S. GAO, GAO-05-189 (February 2005)](https://www.gao.gov/products/gao-05-189). Note: this 2005 report does not and cannot document the January 2009 restructuring. - Northrop Grumman as integrator with a Navy-awarded development contract of about $281 million in September 2003, with PeopleSoft as the commercial-off-the-shelf platform: [Northrop Grumman press release](https://investor.northropgrumman.com/news-releases/news-release-details/us-navy-awards-northrop-grumman-281-million-contract-defense). GAO-08-927R itself names no vendor. - Admiral Mullen's "This program has been a disaster" and Secretary Gates's "what we've gotten for a half billion dollars is an unpronounceable acronym," from Senate Armed Services Committee testimony; Gates's "half billion" understated the actual spend, which GAO tracked at roughly double: [Stars and Stripes](https://www.stripes.com/opinion/military-update-dimhrs-program-dumped-as-a-disaster-1.99558). - More than 90 legacy systems (per DoD program descriptions and press, not an exact GAO count); PeopleSoft/Oracle COTS software; the January 16, 2009 restructuring memo and February 2010 cancellation by Gates and Mullen; the roughly $850 million "at cancellation" figure over about eleven years; and IPPS-A as the Army-only successor that reused the DIMHRS technical solution and reached full deployment in 2022 to 2023: [Wikipedia: Defense Integrated Military Human Resources System](https://en.wikipedia.org/wiki/Defense_Integrated_Military_Human_Resources_System). ## Related reading - [Air Force ECSS: the ERP that cost a billion and shipped nothing](/blog/air-force-ecss-erp-failure/): the closest companion in the federal ERP-failure record, another PeopleSoft-based effort that collapsed. - [The FAA Advanced Automation System](/blog/faa-advanced-automation-system/): a decades-long modernization program that ran over budget and was heavily restructured. - [The VA and the Oracle Cerner electronic health record modernization](/blog/va-oracle-cerner-ehr-modernization/): a more recent large-scale federal system rollout with its own cost and schedule troubles. - [The GAO High-Risk List and improper payments](/blog/gao-high-risk-list-improper-payments/): the oversight lens for how the government tracks large-dollar failure risk. - [The public-money programs index](/blog/public-money-programs-index/): the full set of "where the public money goes" oversight write-ups. *This post is informational and journalistic, not legal or financial advice. It describes public programs and documented events; mentions of third parties are nominative fair use and no affiliation is implied.* --- Canonical HTML: https://jwatte.com/blog/dimhrs-military-hr-payroll-failure/ RSS: https://jwatte.com/feed.xml JSON Feed: https://jwatte.com/feed.json Hero image: https://jwatte.com/images/dimhrs-military-hr-payroll-failure.webp