Skip to main content Accessibility help
×
Hostname: page-component-78c5997874-fbnjt Total loading time: 0 Render date: 2024-11-18T23:29:53.266Z Has data issue: false hasContentIssue false

7 - Management strategies for complex contracts

Published online by Cambridge University Press:  05 August 2013

Trevor L. Brown
Affiliation:
Ohio State University
Matthew Potoski
Affiliation:
University of California, Santa Barbara
David M. Van Slyke
Affiliation:
Syracuse University, New York
Get access

Summary

THE AFTERMATH

By the summer of 2007 the Deepwater program was on its last legs. After six months of exposés, investigations, lawsuits, and oversight hearings, the ICGS–Coast Guard relationship turned openly antagonistic. Coast Guard Commandant Allen announced that the Coast Guard would expand its acquisition workforce to take over the program’s LSI functions. On April 17, the Coast Guard announced it had reversed its decision to accept the first eight P-123s and two months later, on June 5, 2007, the Coast Guard filed suit in federal court to recover $96 million from ICGS (O’Rourke, 2010). Meanwhile Lockheed Martin’s and Northrop Grumman’s ICGS partnership began to dissolve. Lockheed quickly blamed Northrop Grumman for the P-123s, claiming that “it would not be financially affected by the government’s refund request because the faulty ships had structural, not equipment, problems,” meaning only Northrop was to blame since it had been responsible for the work on the P-123’s hull. Northrop passed the blame on to its subcontractor, Bollinger Shipyards, which also happened to be the original manufacturer of the 110 patrol boat (Associated Press, 2007). The Deepwater contract was still in effect, but the cooperative partnership the contract was intended to promote had crumbled.

Type
Chapter
Information
Complex Contracting
Government Purchasing in the Wake of the US Coast Guard's Deepwater Program
, pp. 203 - 235
Publisher: Cambridge University Press
Print publication year: 2013

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×