Navy delays Littoral Combat Ship contract award

The Navy has extended its Dec. 14 deadline to announce a contract for the Littoral Combat Ship program by more than two weeks to give Congress more time to consider its plans to award 10 ships apiece to two contractors that had been vying for the program.

The sea service, which initially planned to award one contract for 10 ships to either Lockheed Martin or Austal USA, announced a revised procurement strategy on Nov. 3 that would give both companies orders to build a total of 20 shallow-water vessels. The firms' current proposals for the lucrative shipbuilding contract expire on Dec. 14 -- the date by which congressional approval of the new approach is required.

The continuing resolution passed by the House last week gives the Navy the authority it needs to alter its strategy for the Littoral Combat Ship program, but the fate of that legislation is unclear.

In a statement Monday, the Navy said it has asked for and received approval from Lockheed and Austal to extend the deadline to Dec. 30.

"The extension provides time to process the LCS contract award if Congress provides authorization for the dual-block buy or in the event that we proceed to a down-select to one company," the statement said. "This extension does not allow the Navy to continue to work for the dual-block buy authorization beyond December 30, 2010."

Some lawmakers, including Senate Armed Services Committee ranking member John McCain, R-Ariz., are skeptical of the Navy's plans to buy two different models of ships. But Adm. Gary Roughead, the chief of naval operations, has called it an "incredible, incredible opportunity with regard to locking in the prices on 20 ships."

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • Federal IT Applications: Assessing Government's Core Drivers

    In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security


When you download a report, your information may be shared with the underwriters of that document.