To download as a PDF click here - US Army Center Of Military History
To download as a PDF click here - US Army Center Of Military History
To download as a PDF click here - US Army Center Of Military History
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
94 so u R c e s o f we a p o n sy s T e m s In n o v a T Io n In T h e depaR TmenT o f defense<br />
military preparedness. They also had a major impact on the Air Force, especially<br />
given the service’s expanding role in the development, production, and deployment<br />
of intercontinental and intermediate-range ballistic missiles. Much of the<br />
propulsion and materials technology built into the missile force complemented<br />
the hardware requirements of the new space program. Consequently, the Air<br />
Research and Development Command’s in-house facilities broadened their<br />
programming functions to include space-b<strong>as</strong>ed R&D for military applications.<br />
Organizational changes followed. In April 1959, Bernard Schriever, now a major<br />
general, <strong>as</strong>sumed command of ARDC. Guided by the success of the ballistic<br />
missile program managed by the Western Development Division, Schriever<br />
separated weapons production and procurement from the Air Materiel<br />
Command and merged both functions into ARDC, resulting in the formation of<br />
the Air Force Systems Command in 1961. The remaining functions of AMC—<br />
supply and maintenance—were consolidated into the new Air Force Logistics<br />
Command.<br />
The driving force behind the formation of the Air Force Systems Command<br />
w<strong>as</strong> the ongoing struggle between ARDC and AMC to work out a mutually<br />
agreeable division of labor at the often-disputed point in the procurement process<br />
w<strong>here</strong> weapons development ce<strong>as</strong>ed and production commenced. The adoption<br />
of ide<strong>as</strong> about concurrency—the process of overlapping R&D and production<br />
stages to accelerate the development of weapon systems—had only exacerbated<br />
this conflict. New institutional mechanisms, such <strong>as</strong> the Weapon System Project<br />
<strong>Of</strong>fice, provided a temporary solution to this problem by managing all ph<strong>as</strong>es<br />
of R&D and procurement through on-site collaboration of ARDC and AMC<br />
personnel. Still, even in c<strong>as</strong>es w<strong>here</strong> this solution w<strong>as</strong> effective—at the Western<br />
Development Division, for example—a tenuous relationship continued to exist<br />
between the commands. Typically, the Air Staff had to intervene to resolve<br />
disputes on a c<strong>as</strong>e-by-c<strong>as</strong>e b<strong>as</strong>is. 79<br />
Other organizational problems persisted, which prompted Air Force Chief<br />
of Staff Gen. Thom<strong>as</strong> White to request, shortly after the launch of Sputnik,<br />
that the Scientific Advisory Board form a special committee to review ARDC<br />
policies, functions, and procedures. Submitted in the summer of 1958, the<br />
Stever Committee Report (named after the committee’s chairman, MIT physicist<br />
H. Guyford Stever) recommended sweeping changes to ARDC’s highly<br />
centralized management structure. Day-to-day oversight and micromanagement<br />
of programs, the committee concluded, should not be the function of the<br />
headquarters staff. Rather, headquarters should focus on program coordination<br />
and long-term policymaking. The committee advised General White to<br />
decentralize ARDC’s command structure and grant full control of program<br />
functions and resource allocation to the weapon system project offices operating<br />
in the field. <strong>To</strong> facilitate this transition and improve operating efficiencies<br />
at the program level, the committee urged the Air Staff to reorganize ARDC<br />
79 Johnson, The United States Air Force and the Culture of Innovation, 52–54; Gorn, Vulcan’s Forge,<br />
63–66.