Former Defense leaders call for simpler acquisition system

The Pentagon could achieve better contracting outcomes if Congress removed burdensome layers of bureaucracy, former top Defense Department officials told a House panel on Wednesday.

On the heels of the passage of one of the largest weapons procurement reform measures in two decades, the House Armed Services Committee's Defense Acquisition Reform Panel went back to work examining the lack of integration between the Defense agencies that develop program requirements, establish budgets and implement contracts.

Panel Chairman Rep. Robert Andrews, D-N.J., said poor coordination is responsible for a growing gap between what the government pays for and what it receives in Defense acquisitions. But, retired Air Force Lt. Gen. Ronald Kadish said the problem did not pop up overnight and there is no simple solution. Past efforts to improve the acquisition system, he said, have added unnecessary rules and processes and created unmanageable expectations.

"In an effort to improve the system, we have made it almost unintelligibly complex," said Kadish, who now serves as a vice president of the consulting firm Booz Allen Hamilton. "And, this complexity is an albatross around our neck."

Kadish warned the panel that any legislative fix that "adds to the rule book without taking something away does not help the process."

Panel members seemed to get the message. Rep. Jim Cooper, D-Tenn., invited Kadish to "strike sections of the rule book with a red pen." Kadish seemed intrigued by the offer and said he would accept the challenge "if he had the time."

Former Deputy Secretary of Defense Gordon England noted a need to synchronize the Pentagon's overarching purchasing needs, but said doing so would require providing agency managers with increased flexibility and industry stakeholders with greater budgetary stability for their contracts.

The No. 2 official at the Pentagon during President George W. Bush's second term, England recommended making greater use of multiyear contracts for programs with mature technologies that are unlikely to experience significant requirement changes. Ret. Navy Adm. Edmund Giambastiani pointed to contracts for the F-18 Super Hornet aircraft, Navy destroyers and Virginia-class submarines as examples of multiyear agreements that fit such criteria.

Giambastiani, chairman of the board of directors at Alenia North America, an aerospace firm, said if the government is "ruthless" in its risk assessment early on, then upgrades will be easier to implement later in the process.

Other reforms England suggested include allowing Defense to build a budgetary reserve that could be used when contract requirements and costs change and altering the hiring system to recruit more experienced acquisition professionals.

Implementing these "incremental changes" would "immediately help operations and have a meaningful effect," England said.

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 Brocade

    Best of 2016 Federal Forum eBook

    Earlier this summer, Federal and tech industry leaders convened to talk security, machine learning, network modernization, DevOps, and much more at the 2016 Federal Forum. This eBook includes a useful summary highlighting the best content shared at the 2016 Federal Forum to help agencies modernize their network infrastructure.

  • Sponsored by CDW-G

    GBC Flash Poll Series: Merger & Acquisitions

    Download this GBC Flash Poll to learn more about federal perspectives on the impact of industry consolidation.

  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

  • Sponsored by Aquilent

    A DevOps Roadmap for the Federal Government

    This GBC Report discusses how DevOps is steadily gaining traction among some of government's leading IT developers and agencies.

  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.

  • Sponsored by CDW-G

    Joint Enterprise Licensing Agreements

    Read this eBook to learn how defense agencies can achieve savings and efficiencies with an Enterprise Software Agreement.

  • Sponsored by Cloudera

    Government Forum Content Library

    Get all the essential resources needed for effective technology strategies in the federal landscape.


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