After the September 11 attacks, one of the plainer institutional embarrassments to surface was this: the Federal Bureau of Investigation, the agency the country was asking to connect dots across cases and field offices, was still running its investigations largely on paper. Its digital case system, Automated Case Support (ACS), was a green-screen relic. Agents could not easily search across files, attach photographs or documents, or move a case electronically. The DOJ Inspector General identified the antiquated case-management system as a systemic weakness the FBI had to fix, and few people inside or outside the bureau disagreed. The mission need was real.
What followed over the next decade is a two-act story about how hard it is for a large government agency to buy and build software. In the first act, a program called Virtual Case File consumed roughly $170 million and produced nothing the FBI could deploy. In the second, its replacement, Sentinel, ran years late and hundreds of millions over its original budget, then, after a mid-course restructuring, actually shipped and became the FBI's operational case system. Both acts are documented in detail by the Department of Justice Office of the Inspector General (OIG), which is the authority this article leans on throughout. Neither act involves fraud or criminal convictions. This is a story about mismanagement, weak contracting, and eventual course-correction, not about anyone going to prison.
Act one: Trilogy and Virtual Case File
The umbrella program was called Trilogy. It had three parts. The first two were infrastructure: modern desktop computers for FBI personnel and the secure networks to connect them. The third was the software that would sit on top of that hardware and replace ACS: Virtual Case File, or VCF.
The infrastructure parts are important to the honest telling of this story, because they mostly worked. According to testimony by Inspector General Glenn A. Fine, the desktops-and-networks portion of Trilogy was largely completed, though it ran 22 months late and its cost rose from $238.6 million to $337 million. Congress had added roughly $78 million after 9/11 specifically to accelerate the effort. So the hardware and network backbone was delivered: late, over budget, but delivered. The catastrophe was concentrated in the software.
VCF's contractor was Science Applications International Corporation (SAIC). The bureau contracted for the case-management software without, in the OIG's assessment, defining its requirements, milestones, decision points, or contractor penalties up front, and it did so during a period of heavy turnover in its own IT management. The result, as IEEE Spectrum reported in its detailed post-mortem quoting the FBI, was roughly 700,000 lines of code that were so bug-ridden and off-target that the FBI scrapped the project. About $105 million of that code was deemed unusable. (One caveat on the numbers: the 700,000-lines and $105-million-unusable specifics trace to IEEE Spectrum quoting the FBI rather than to the OIG testimony directly, and some outlets such as CNN framed the loss as about $104 million rather than $105 million of unusable code. Both figures circulate; the order of magnitude is not in dispute.)
In February 2005, OIG Audit Report 05-07 concluded that the FBI could not deploy VCF and that the software would require substantial additional work or would need to be scrapped and replaced. In April 2005 the FBI scrapped it. After more than three years and about $170 million budgeted, the software heart of Trilogy had produced no deployable system.
That is the single hardest fact in the record: roughly $170 million spent, zero usable case-management software delivered.
Act two: Sentinel
The need did not go away when VCF died. Agents still could not do their work on a modern system. So the FBI tried again, this time under the name Sentinel.
In March 2006 the FBI awarded the Sentinel prime contract to Lockheed Martin. Public reporting put the overall program at roughly $425 million, structured around a contract valued at about $305 million, to be delivered in phases. This was a larger and, on paper, more disciplined effort than VCF, built to avoid the earlier mistakes.
It did not avoid them cleanly. By 2007 to 2008 the estimated cost had been rebaselined upward to about $451 million. (The exact date of that revision is soft in the record: some press accounts put it in October 2007, while the OIG's own later report refers to the $451 million projection in 2008, so it is fairer to describe it as a 2007-to-2008 rebaseline than to pin a single month.) By 2010 the OIG was warning that Sentinel was running roughly $100 million over and about two years behind schedule. Sentinel was, in other words, tracking toward its own version of the VCF story: a big case-management build slipping past its budget and its calendar.
What broke the pattern was a management intervention rather than a technical breakthrough. In October 2010 the FBI ran a TechStat review, a structured, data-driven program review of the kind the federal CIO's office was pushing across government at the time, and restructured Sentinel. It reduced Lockheed Martin's role as single prime integrator, brought program management in-house, and adopted an Agile software-development approach, building and shipping the system in short increments rather than one large delivery.
That pivot is the reason this is a two-act story and not a second total loss. Sentinel was made available to all FBI users on July 1, 2012. Unlike VCF, it shipped.
The money, kept distinct
The figures for these two programs get conflated constantly in casual retellings, and the fact base for this article warns repeatedly against doing so. They are two different projects with two different contractors and two different outcomes.
- Virtual Case File (VCF): the third, software component of Trilogy. Contractor SAIC. About $170 million budgeted over more than three years, with roughly $105 million of code deemed unusable (per IEEE Spectrum quoting the FBI). Scrapped in April 2005. Never deployed.
- Trilogy infrastructure (the first two components): desktops and networks. Delivered but 22 months late, with cost rising from $238.6 million to $337 million (per IG Fine's testimony). A partial success, not a loss.
- Sentinel: the VCF replacement. Prime contractor Lockheed Martin from March 2006, then FBI-led after October 2010. Originally about $425 million, rebaselined to about $451 million by 2007 to 2008. Delivered to all users July 1, 2012.
The Sentinel completion figure itself needs a note, because two numbers travel together and it is easy to mistake them for rivals. The Department's July 2012 report to Congress cited total project costs of about $441 million. But the OIG pointed out that this $441 million did not include roughly two years of post-deployment operations and maintenance that were within the original project scope. The fuller, all-in figure that included that O&M was about $451 million. So $441 million and $451 million are not competing claims about the "real" cost; $441 million is the implementation cost reported at go-live, and $451 million is the fuller projection including the operations and maintenance that the program had always been meant to cover. Any clean "Sentinel came in under budget" line is true only against the rebaselined $451 million ceiling, not against the original $425 million plan. Stated against the original plan, Sentinel ran over.
What the record actually establishes
It is worth being precise about what "delivered" means here, because the OIG was.
In September 2012, OIG Audit Report 12-38 examined the milestones the FBI said it had completed. The FBI claimed that 15 of 17 key milestones were complete by July 2012. When the OIG tested those claims independently, it found adequate support for 8 of them, partial support for 4, and no adequate evidence for 3. That is not the same as the OIG endorsing the FBI's own count, and it is not "8 of 17" either. It is a more careful finding: Sentinel had gone live, but at go-live the bureau's own completion claims outran what an auditor could verify.
There is also a usability caveat that belongs in an honest account. A 2014 OIG audit found that only about 42 percent of surveyed FBI employees often found the results they needed when searching in Sentinel. That is a meaningful limitation for a system whose entire purpose was to let agents find and connect information. It is not, however, evidence that Sentinel "failed too." A later OIG report in 2017 (report a1431) audited Sentinel's continued status and confirmed it remained the FBI's operational case-management system. The system was delivered, it endured, and it had real rough edges. All three of those things are true at once.
The timeline
- Pre-2001: FBI investigations run largely on the paper-era Automated Case Support (ACS) system.
- Post-9/11: Congress adds about $78 million to accelerate the Trilogy IT modernization program; the OIG endorses the modernization need.
- Through 2004: Trilogy infrastructure (desktops, networks) is built, ending 22 months late with cost rising from $238.6 million to $337 million. VCF software, built by SAIC, falls apart.
- February 2005: OIG Report 05-07 concludes VCF cannot be deployed and needs substantial rework or replacement.
- April 2005: FBI scraps VCF after about $170 million budgeted; about $105 million of code deemed unusable (per IEEE Spectrum).
- March 2006: FBI awards the Sentinel prime contract to Lockheed Martin; program about $425 million.
- 2007 to 2008: Sentinel estimate rebaselined to about $451 million.
- 2010: OIG warns of roughly $100 million in overruns and about two years of delay.
- October 2010: FBI runs a TechStat, reduces Lockheed Martin's role, brings management in-house, and adopts Agile.
- July 1, 2012: Sentinel available to all FBI users; about $441 million reported to Congress (excluding roughly two years of in-scope O&M, making the all-in figure about $451 million).
- September 2012: OIG Report 12-38 verifies 8 of the FBI's claimed-complete milestones fully, 4 partially, 3 not at all.
- 2014: OIG audit finds about 42 percent of surveyed employees often found needed search results.
- 2017: OIG report a1431 confirms Sentinel still in operational use.
The failure critique and the mission defense, side by side
The two verdicts on this decade can sit next to each other without either one cancelling the other out.
The efficiency and management critique is severe and it comes from the government's own auditors. The FBI spent on the order of $170 million on VCF and got nothing it could deploy, in part because, as the OIG found, it had contracted without defined requirements, milestones, decision points, or contractor penalties, during a stretch of heavy IT-management turnover. Having lived through that, it then repeated the pattern at larger scale with Sentinel: a program originally budgeted around $425 million whose estimate climbed to about $451 million while running roughly $100 million over and about two years late before a 2010 intervention pulled it back. A DOJ OIG series of critical audits, from 05-07 in 2005 through 12-38 in 2012, documents the whole arc of cost growth, delay, and weak oversight. The honest one-line indictment is that the FBI took most of a decade and roughly half a billion dollars of combined spend to accomplish what it set out to do after 9/11, and one entire project inside that span produced no usable system at all.
The public-good and mission defense is also real, and it is not just spin. The underlying need was legitimate and urgent: the FBI genuinely could not run modern investigations on ACS, and the OIG itself endorsed the modernization mandate. Trilogy was not a total loss; its infrastructure components were delivered, and only the VCF software failed outright. And Sentinel, unlike VCF, was ultimately finished. The October 2010 restructuring, moving to in-house management and Agile delivery, is frequently cited in government-IT case studies as a genuine, if belated and expensive, turnaround: proof that the capability could be achieved rather than abandoned. Sentinel went live for all users in July 2012 and, per the 2017 OIG audit, remained the bureau's operational case-management system years later. A country that needed its principal domestic investigative agency to work its cases digitally eventually got that, and the fix came from confronting the program's management problems head-on rather than throwing more money at the old structure.
Both readings are supported by the same record. The waste was large and the auditors named it plainly. The mission was legitimate and the second attempt, restructured, delivered. The lesson that survives is narrower and more useful than "government cannot build software": it is that requirements discipline, milestones with teeth, and a willingness to restructure a failing program in flight are what separated the project that shipped from the one that was thrown away.
Fact-check notes and sources
- The FBI's post-9/11 need to move off the paper-era Automated Case Support (ACS) system, and the OIG's endorsement of that modernization priority, are set out in Inspector General Glenn A. Fine's House testimony. DOJ Office of the Inspector General
- VCF as the third, software component of Trilogy, about $170 million budgeted over more than three years, and never deployed: DOJ Office of the Inspector General
- SAIC as VCF contractor, roughly 700,000 lines of code, the April 2005 scrapping, and about $105 million of code deemed unusable (specifics attributed to IEEE Spectrum quoting the FBI): IEEE Spectrum, "Who Killed the Virtual Case File?". CNN reporting framed the loss as about $104 million: CNN
- OIG Audit Report 05-07 (February 2005) concluding VCF could not be deployed and would need substantial rework or replacement, and that the FBI had contracted without defined requirements, milestones, decision points, or contractor penalties: DOJ OIG FBI report index; contemporaneous reporting: CNN
- Trilogy infrastructure completed 22 months late with cost rising from $238.6 million to $337 million, and the roughly $78 million congressional acceleration add: DOJ Office of the Inspector General
- Lockheed Martin awarded the Sentinel prime contract in March 2006; program about $425 million, contract value about $305 million: DOJ OIG Sentinel interim report (a1238)
- Sentinel estimate rebaselined to about $451 million (2007 to 2008), and the OIG's 2010 warning of roughly $100 million in overruns and about two years of delay: CNN; SiliconANGLE
- October 2010 TechStat, reduction of Lockheed Martin's prime-integrator role, in-house management, and the Agile pivot: DOJ OIG Report 12-38 (NCJRS abstract)
- Sentinel available to all FBI users July 1, 2012; about $441 million reported to Congress, excluding roughly two years of in-scope O&M that brings the all-in figure to about $451 million: DOJ OIG Report 12-38 (NCJRS abstract)
- OIG Report 12-38 (September 2012) milestone verification: of the FBI's 15-of-17 claimed-complete milestones, adequate support for 8, partial for 4, none for 3: DOJ OIG Report 12-38 (NCJRS abstract)
- Sentinel still the FBI's operational case-management system in a 2017 OIG audit: DOJ OIG Report a1431 (2017)
Related reading
- The VA's Oracle-Cerner electronic health record modernization, a sibling story of a large federal IT program running over budget and behind schedule.
- DEA cash seizures and civil forfeiture, another Department of Justice oversight story built on IG and primary records.
- The GAO High-Risk List and improper payments, the government's own framework for the kind of oversight this series applies.
- The full public-money programs index, the complete set of "where the public money goes" write-ups.
This post is informational and journalistic, not legal, financial, or investment advice. It describes public programs, documented events, and public records; mentions of third parties are nominative fair use and no affiliation is implied.