TOPICS
TOPICS
Army to create central acquisition organization
Under pressure to bring more engineering expertise back in-house after years of ceding such capability to contractors, the Army has begun standing up a centralized staff of systems engineers with the skill and judgment to broadly examine and improve the service's acquisition programs.
The awkwardly named System-of-Systems Systems Engineering organization -- SoS SE in Army parlance -- is intended to bring a level of engineering oversight to Army weapons programs now lacking.
"We realized there was nobody [with systems engineering expertise] looking across all of our programs," said Ross Guckert, assistant deputy for acquisition and systems integration at the Office of the Assistant Secretary of the Army for Acquisition, Logistics and Technology.
That deficiency was made clear last summer when the Army discovered it had 16 different battle command systems on record, plus a number of others that had crept into use on the battlefield outside of the conventional acquisition process. Battle command systems are the technology troops use to communicate on the battlefield.
Implementing a unified battle command system will be the new organization's first pilot program. It will be a "painful" process for those units that have to adapt to a new system, Guckert conceded, but will benefit the Army as a whole.
Eventually, all 303 of the Army's brigades in active and reserve units will be able to share critical information across formations on the battlefield. And the unified battle command will eliminate redundant investments and streamline training, Guckert said.
Army procurement is organized into 12 program executive offices focused on related programs, such as ground combat systems or aviation. While there are several hundred systems engineers in those offices, they are not looking at the integration of programs across the service. As such, the SoS SE, with a staff of 17, will be organized to integrate brigade formations.
The systems engineers hired for the new organization will serve at the GS-15 level, Guckert said.
COMMENTS
- DODI 5000.02, IEEE 1220 and relevant DAU courses (e.g., CLE-0003) can help Army SEs understand what is missing from their Programs. There needs to be more emphasis on 1) early System Requirements Reviews, 2) how to tailor the above guides for Quick Reaction Capability programs and 3) lessons learned in development of System-of-Systems. Rushing to PDR because of existing COTS could undermine Army IT transformation. wpgradbill Posted May 31, 2009 9:31 PM
- We not only need systems engineers at the 15 level but we need some hands on engineers that can write contractually effective specifications, and test engineers and System Engineering WIPT Chairs. We need people that understand the technology and mission that are not affraid to speak up to influence programs positively instead of "Group-Think." We need smart competitive strategies with well balanced system engineering input. People should be encouraged to use their talents which result in positive outcomes. We need to train and mentor each generation of engineers, acquisition analysts,logisticians, business managers and KOs. westj Posted May 26, 2009 11:53 AM
- Why has it taken so long ?? Mary Farr Posted May 26, 2009 9:53 AM
PROMO RIGHT: GBC
Advancing the business of government through analysis, insight and the sharing of best practices.
SPONSORED RESEARCH
Achieving a Greener Federal Government IBM
Federal Cybersecurity: Securing the Nation's Information IBM
American Recovery and Reinvestment Act: New Requirements for Tracking and Reporting Federal Workforce Data Kronos
Managing the Stimulus: A Candid Survey of Federal Program Managers Accenture and Microsoft
Improving Collaboration and Productivity in 21st Century Government: The Role of Communication for Government Executives Cisco
