Labels and Tags

Accountability (34) ADR in procurement (2) Best interest of government (4) Best practices (14) Best value (3) Centralized procurement structure (9) Changes during bid process (5) Competence (5) Competition vs Efficiency (1) Compliance (12) Conflict of interest (10) Contract administration (7) Contract extension or modification (5) Contractor responsibility (8) Conviction (3) Cost and pricing (2) Debarment (2) Determining responsibility (14) Disclosure requirements (2) Disposal of surplus property (3) Effective enforcement requirement (12) Effective specifications (21) Emergency procurement (5) Evaluation of submissions (2) Fair and equitable treatment (9) Fair and reasonable value (8) Fiscal effect of procurement (3) Governmental functions (6) Guam (10) Guam procurement law (11) Improper influence (2) Incumbency (3) Interested party (3) Lore vs Law (1) Methods of source selection (7) Needs assessment (4) No harm no foul? (3) Other procurement links (8) Planning policy (10) Politics of procurement (14) Prequalification (1) Principle of competition (46) Private vs public contract (1) Procurement authority (2) Procurement controversies series (52) Procurement ethics (7) Procurement fraud (17) Procurement lifecycle (5) Procurement procedures (20) Procurement reform (28) Procurement theory (1) Procurment philosophy (3) Professionalism (7) Protest - timing (3) Protests - general (8) Purposes and policies of procurement (5) Recusal (1) Remedies (11) Requirement for new procurement (2) Responsiveness (5) Review procedures (2) Scope of contract (7) Settlement (1) Social preference provisions (37) Sole source (19) Staffing (3) Standards of review (1) Stays and injunctions (3) Substantiation (5) Surety (1) Suspension (3) The subject matter of procurement (15) Training (15) Transparency (22) Unsolicited proposals (1)

Tuesday, February 7, 2012

Acquisition malpractice

If we are to consider that procurement staff should be identified as a profession, and certificated as such, then we must accept the concept of "acquisition malpractice". Still, this article is the first I've seen that uses the term (not that I've been around long enough or experienced the field wide enough to have had a significant exposure to the field).

Procurement chief knocks early F-35 production
“Putting the F-35 into production years before the first test flight was acquisition malpractice,” said acting Pentagon procurement chief Frank Kendall, speaking at a Monday event hosted by the Center for Strategic and International Studies in Washington. “It should not have been done.”

Kendall said that the Pentagon had made “optimistic” predictions about the capabilities of design tools, simulations and modeling to build a fighter that would breeze through test flights without problems.

“We didn’t model everything as precisely as we thought,” Kendall said. “Now we’re paying the price for being wrong.”

Transitioning from development to production is traditionally been one of the most difficult challenges for any program.

Kendall said there is a tendency to start production too early, adding that the F-35 is an “extreme example.”

Barry Watts, an analyst at the Center for Strategic and Budgetary Assessments in Washington, D.C., agreed with Kendall’s assessment. But with then-Defense Secretary Robert Gates terminating the F-22 Raptor program, the Pentagon “has put all of its eggs in the JSF basket,” he said.

“My understanding is the amount of concurrency on this program is as great as or greater than any past program,” he said.

Watts, who has been to Lockheed’s Fort Worth, Texas, plant, described long lines of F-35s already being built. The F-35 is an extremely complicated engineering challenge with its many missions and three variants, Watts said.

“Most of those, if they’re going to be operational airplanes eventually, are going to have to go back and have a bunch of changes made to them,” he said. “That drives up cost and delays things.”

Watts said that the Pentagon should have insisted on more flight tests before starting low rate initial production.

0 comments: