Receive new posts as email.
RSS 0.91 | RSS 2.0
RDF | Atom
Podcast only feed (RSS 2.0 format)
Get an RSS reader
Get a Podcast receiver
Sun | Mon | Tues | Wed | Thurs | Fri | Sat |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | |||
5 | 6 | 7 | 8 | 9 | 10 | 11 |
12 | 13 | 14 | 15 | 16 | 17 | 18 |
19 | 20 | 21 | 22 | 23 | 24 | 25 |
26 | 27 | 28 | 29 | 30 | 31 |
This site operates as an independent editorial operation. Advertising, sponsorships, and other non-editorial materials represent the opinions and messages of their respective origins, and not of the site operator or JiWire, Inc.
Entire site and all contents except otherwise noted © Copyright 2001-2006 by Glenn Fleishman. Some images ©2006 Jupiterimages Corporation. All rights reserved. Please contact us for reprint rights. Linking is, of course, free and encouraged.
Powered by
Movable Type
« Dallas Rolls Out Wireless Video Surveillance | Main | Motorola Adds Wireless Video Surveillance to Municipal Kit »
The Justice Department’s inspector general gives national law enforcement wireless network poor marks: $200m has been spent with little to show for it. The majority of the $772m allotted to the program was used to support the older, existing networks. The system’s overall cost will be $5b and take until 2021 to complete; 81,000 agents of the Justice, Homeland Security, and Treasury departments are to use the network. The Department of Homeland Security can’t wait for progress and is charting its own course.
Private analysts now peg the full cost at $30b, according to The Washington Post. The project is 15 months behind at present. In-fighting among departments, a long-standing problem in federal law enforcement, is one of the factors, the inspector general found.
A number of large-scale federal projects have been abandoned in recent years after hundreds of millions or even billions being spent, including an FBI project mentioned in this article, and the next-generation air-traffic control system. Software projects don’t scale, and integrated software/hardware projects are always orders of magnitude greater than expected.
For a great book on why projects like this fail, and how to avoid some of those problems, read Scott Rosenberg’s Dreaming in Code. He explains how software complexity has outstripped program management capability.
Posted by Glennf at March 27, 2007 1:48 PM
Categories: Radios
TrackBack URL for this entry:
https://db.isbn.nu/mt3/mt-tb.pl/4470