FBI's Sentinel Project Hits Another Snag

Program Suspended Until Some Issues Are Worked Out

2 min read
FBI's Sentinel Project Hits Another Snag

US Federal Bureau of Investigation (FBI) Director Robert Mueller told the US House Appropriations Committee’s Subcommittee on Commerce, Justice, Science, and Related Agencies last week that the follow-on to the notoriously failed $170 million Virtual Case File program would once again slip its schedule and cost targets, the New York Timesreported.

Sentinel is the FBI's next-generation information management system.  According to the US Government Accountability Office (GAO),  Sentinel's key objectives are to: (1) successfully  implement a system that acts as a single point of entry for all  investigative case management and that provides paperless case  management and workflow capabilities, (2) facilitate a bureau-wide organizational change management program, and (3) provide intuitive interfaces that feature data relevant to individual users.

When the Sentinel contract was awarded in 2006 it was going to cost a total $425 million and take six years to be full complete and rolled out. It is now at $451 million and is expected to rise to at least $481 million and slip possibly several months if not longer.

The Times story says that Director Mueller decided to suspend work on Sentinel to correct some "minor" technical issues and make some design changes. These issues included, according to the Times, "slow response times, awkward display pages and screen print that was too small."

For these problems to be appearing now, given Sentinel's extremely high Congressional profile, the importance of Sentinel to the FBI, and the supposed tight oversight of the program after the VCF fiasco, indicates to me that there may be much more here than is being publicly disclosed. Even the Department of JusticeCIO rates the program as a 3.5 out of 5 in terms of overall program risk.

If I were Congress, I would ask the GAO to do an in-depth review of the program immediately. Things don't sound right.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}