03.07.2013 Views

View/Open - Naval Postgraduate School

View/Open - Naval Postgraduate School

View/Open - Naval Postgraduate School

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Contractors Supporting Military Operations<br />

Presenter: Richard L. Dunn is currently an independent consultant and Senior Fellow<br />

at the University of Maryland. He conducts research and provides advice on business strategies<br />

to effectively develop and employ technologies in the military and civil sectors. Mr. Dunn retired<br />

from Federal service where he served as the first General Counsel of the Defense Advanced<br />

Research Projects Agency and was awarded the Presidential Rank of Meritorious Executive. He<br />

also served at NASA Headquarters and was on active duty as a Judge Advocate in the USAF<br />

for ten years. At DARPA, Mr. Dunn pioneered contracting using “other transactions” to increase<br />

the effectiveness of R&D and prototyping efforts. He is a member of the editorial advisory board<br />

of the Government Contractor. He has written extensively both in the area of government<br />

contracts and military history. Mr. Dunn is a graduate of the University of New Hampshire (cum<br />

laude), and has law degrees from the University of Maryland and George Washington University<br />

(Highest Honors). Mr. Dunn and his wife, Karen, reside in Edgewater, Maryland.<br />

Richard L. Dunn<br />

444 Poplar Leaf Drive<br />

Edgewater MD 21037<br />

(410) 798-0332<br />

richardldunn@comcast.net<br />

OVERVIEW<br />

The author’s previous research surveyed issues and policies related to the trend toward<br />

increased reliance on contractors in combat and other contingency operations, documented<br />

relevant case studies, and, presented analyses and recommendations. 18 The current research<br />

presents a background summary and updates relevant policy developments since the earlier<br />

research. It then takes a distinctly different approach than the earlier study. Instead of trying to<br />

extract additional lessons from case studies of current events, this research attempts to gain<br />

historical perspective through case studies of earlier conflicts, primarily World War II. Rather<br />

than attempting to survey a catalog of issues, this research concentrates on a narrow set of<br />

issues.<br />

The issues reviewed in this paper relate to the extent contractors can and should be<br />

made an integral part of the “mission team” in combat and contingency operations. If contractors<br />

have become integral to the success of combat and contingency operations, shouldn’t they be<br />

responsive and responsible to the commander formally charged with mission success?<br />

Expressed another way, can and should the concept of “unity of command” be applied to<br />

contractors in a combat theater? Assuming that contractors should be integrated into joint task<br />

force operations in a way that creates the essence of unity of command, how can that be<br />

accomplished?<br />

The question of contractor control/unity of command can be relatively simply stated as<br />

suggested in the previous paragraph. This research found, however, that the path toward<br />

combatant commander control of contractors is complicated by divergent policies, conflicting<br />

18 Dunn, Contractors in the 21 st Century ‘Combat Zone’, presented at the <strong>Naval</strong> Post Graduate <strong>School</strong> 2 nd<br />

Annual Acquisition Research Conference (vide). Available from the Center for Public Policy and Private<br />

Enterprise, <strong>School</strong> of Public Policy, University of Maryland; and at the NPS website<br />

(www.nps.navy.mil/gsbpp/ACQN/publications).<br />

=<br />

=<br />

==================^Åèìáëáíáçå=oÉëÉ~êÅÜW=ÅêÉ~íáåÖ=ëóåÉêÖó=Ñçê=áåÑçêãÉÇ=ÅÜ~åÖÉ=======- 426 -<br />

=<br />

=

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!