Acquisition workforce needs own category, analyst says

The new government series should include program management, contracting officers, and a new function named 'requirements management'

Federal officials should create a single employment series for government acquisition employees, matching the structure of the workforce to the nature of the work, a former procurement official has said.

The new government series should include program management, contracting officers and a new function called “requirements management,” which, in essence, would be “a professionalized super COTR,” or contracting officer’s technical representative, David Litman, a member of the board of directors at the Federal Acquisition Innovation and Reform Institute, wrote in a recent paper titled “A Call to Restructure the Acquisition Workforce.”

The series would build a team mentality, he wrote. Currently, contract specialists are in the 1102 series, and acquisition program managers have no dedicated series, although they have unique training and certifications.

Meanwhile, COTRs are often taken from the ranks of technical staff and their training on monitoring contracts helps little, wrote Litman, former senior procurement executive for the Transportation Department and former chairman of the Federal Chief Acquisition Officers Council’s Human Capital Working Group.

Stan Soloway, president of the Professional Services Council, said Litman's approach is on the right track. It emphasizes that acquisition includes more than just signing contracts, he said. It's also about defining requirements before issuing a solicitation, and about managing the contract after the award.

About the Author

Matthew Weigelt is a freelance journalist who writes about acquisition and procurement.

The Fed 100

Save the date for 28th annual Federal 100 Awards Gala.

Featured

  • computer network

    How Einstein changes the way government does business

    The Department of Commerce is revising its confidentiality agreement for statistical data survey respondents to reflect the fact that the Department of Homeland Security could see some of that data if it is captured by the Einstein system.

  • Defense Secretary Jim Mattis. Army photo by Monica King. Jan. 26, 2017.

    Mattis mulls consolidation in IT, cyber

    In a Feb. 17 memo, Defense Secretary Jim Mattis told senior leadership to establish teams to look for duplication across the armed services in business operations, including in IT and cybersecurity.

  • Image from Shutterstock.com

    DHS vague on rules for election aid, say states

    State election officials had more questions than answers after a Department of Homeland Security presentation on the designation of election systems as critical U.S. infrastructure.

  • Org Chart Stock Art - Shutterstock

    How the hiring freeze targets millennials

    The government desperately needs younger talent to replace an aging workforce, and experts say that a freeze on hiring doesn't help.

  • Shutterstock image: healthcare digital interface.

    VA moves ahead with homegrown scheduling IT

    The Department of Veterans Affairs will test an internally developed scheduling module at primary care sites nationwide to see if it's ready to service the entire agency.

  • Shutterstock images (honglouwawa & 0beron): Bitcoin image overlay replaced with a dollar sign on a hardware circuit.

    MGT Act poised for a comeback

    After missing in the last Congress, drafters of a bill to encourage cloud adoption are looking for a new plan.

Reader comments

Thu, Jul 30, 2009 mike.mcmanus wpafb, oh

A step in the right direction. The contracting officer merely places the requirement on contract. He does not define or establish it. Note that the term "COTR" refers to the "Contracting Officers TECHNICAL Representtive". It is critical that the CO have a representative who understands the technology underlying the contract. The contracting officer is required to understand the BUSINESS side of the contract, not the technical. I've often argued that the program manager should be the person who signs the contract. That way when the IG or GAO comes hunting for a head 5 or so years later the name and phone number of the program manager will be easy to locate (it would be on the front page of the contract he/she signed) for an explanation of why he signed the contract!

Wed, Jul 29, 2009

This suggestion kind of sounds like a another updated version of the DoD Acquisition Corps. So, how's that initiative working out these days? Oh, we still have all these pesky acquisition problems within DoD. Hmmmmmm. Draw your own conclusions.

Wed, Jul 29, 2009 Jaime Gracia Washington, DC

Starting out with poorly defined requirements will often lead to poor acquisition outcomes. It is a simple formula. The current process needs to be an interactive and collaborative one, where the use of social media tools and technology are the drivers for exchanging knowledge. Organizing the acquisition community into a fully integrated workforce will also help organize and manage data and drive an effective needs development process that includes all stakeholders and has a focus on quality, technological maturity, and feasibility for cost and schedule realism. This is opposed to the current process which is often declarative, and serves the end-user or the warfighter poorly.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group