What’s Next For Deepwater?

02.05.07

Categorie: Industry, Naval |

What began as an ambitious but mostly overlooked scheme to modernize the Coast Guard’s entire fleet of ships and aircraft over a 20-year period has, just five years after conception, turned into one of the most troubled and criticized U.S. military programs.

The $24-billion Deepwater initiative was launched in 2002 with a contract naming Integrated Coast Guard Systems — a partnership between electronics maker Lockheed Martin and shipbuilder Northrop Grumman — the “lead systems integrator” for the program, meaning the firms, rather than the Coast Guard, would be responsible for selecting subcontractors to handle the aircraft, electronics and shipbuilding work.

Integrated Coast Guard Systems hailed the unusual arrangement as revolutionary — and the best way to leverage the firms’ shared expertise. But the service has terminated the lead-systems-integrator relationship, citing shoddy work on a $100-million effort to stretch and modernize eight 110-foot patrol boats — the first major shipbuilding portion of Deepwater. Those boats are being decommissioned due to hull buckling, leaving the Coast Guard with a 15-percent gap in its patrol boat force, Commandant Thad Allen said while announcing the decommissioning and the Deepwater changes on April 17. Earlier, Allen had cancelled the so-called Fast Response Cutter being designed from scratch by Integrated Coast Guard Systems to eventually fill that gap, instead expressing his intention to seek off-the-shelf boat designs.

The stretched boats also suffered from incomplete electronics integration and poor network security, according to Michael DeKort, a former Lockheed Martin engineer who worked on the boats but was fired, allegedly for challenging his bosses over the problems. Two weeks ago DeKort testified before a House committee investigating Deepwater. A Justice Department probe is also reportedly underway, following on the heels of several Coast Guard Inspector General reports that were critical of Deepwater.

The long-term consequences of the Deepwater shakeup are far from clear — and it’s possible that Lockheed Martin and Northrop Grumman will still do much of the work on the program, albeit strictly as contractors. According to Allen, all aspects of Deepwater that are already far advanced — including work on patrol planes, helicopters, short-range boats and several large cutters — will remain intact. But overall management of the program will pass from industry to the Coast Guard. That means the service will need more officers with acquisitions experience.

“I have already begun building my organic staff in the fiscal year 2008 budget request, and will combine that with other government assets as we transition to this new role,” Allen said.

But this might take years, so in the meantime, the Coast Guard will bring in experts from the American Bureau of Shipping and other third parties “to increase assurances that Deepwater assets are properly designed,” Allen said.

The Coast Guard’s renewal of its acquisitions forces comes hot on the heels of a similar initiative in the Navy, which has seen the price of its warships climb steeply, owing in part to poor contractor performance.

Cross-posted at Military.com

Related posts:

  1. Coast Guard Eyes New Cutter
  2. Warships International Fleet Review: U.S. Coast Guard’s Big Chill Demands New Tactics, Equipment
  3. Coast Guard Continues Support in Wake of Haiti Earthquake, Part One
  4. Navy Amphib Diverts for Haiti Relief
  5. Warships International Fleet Review: Unmanned Systems Could Help Fill “Fighter Gap”

6 Responses to “What’s Next For Deepwater?”

  1. DJ says:

    Why doesn’t the USCG partner up with the Navy in the LCS program for their new generation of patrol boat or cutter?

    Or does the Low Observable sides make operation harder for an unnecessary feature?

  2. Grandjester says:

    DJ

    LCS has some of the exact same problems, with the same damn contractors.

  3. [...] Related: What’s next for Coast Guard modernization? Coast Guard modernization not entirely screwed up Coast Guard launches new ship No Comments so far Leave a comment RSS feed for comments on this post. TrackBack URI Leave a comment Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong> [...]

  4. [...] In the wake of the withdrawal, the Coast Guard cancelled the shared Northrop-Lockheed Deepwater “lead systems integrator” management contract, citing poor performance. And this summer, the Coast Guard stood up the Acquisitions Directorate to fill the gap, a big step towards reasonable oversight for a service that long ago had surrendered leadership in its equipment programs to the very companies that stood to benefit financially from the programs. Subsequent correspondence between Coast Guard officials and industry revealed that DeKort had been right all along about the 123s: that their network gear, like their hulls, had failed to meet Coast Guard standards. [...]

  5. [...] For those closely following the ups, downs and more downs of the Coast Guard’s $25-billion Deepwater program launched in 2002, Shearington’s allegations come as no surprise. Deepwater aims to revamp the service’s entire inventory of ships, aircraft and electronics over the next 20 years. But it’s off to a poor start. [...]

  6. [...] Related: Coast Guard’s sunk costs Coast Guard’s billions Congress wants to take away CG’s buying power Coasties in Georgia Coasties to the rescue! Behind the Coast Guard’s rescue spin Coast Guard spins rescue Cutters got leaky networks Coast Guard slams contractors What’s next for Deepwater? Coast Guard sinking ever faster Deepwater: the good and the bad Lockheed’s bad boats No Comments so far Leave a comment RSS feed for comments on this post. TrackBack URI Leave a comment Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong> [...]

Leave a Reply