Commercial augmentation for intelligence operations: lessons learned from the Global War on Terrorism.
Since the beginning of the Global War on Terrorism (GWOT), the Department of Defense (DoD) has witnessed an unprecedented expansion of private sector support to military operations, a market now valued at over $200 billion a year and accounting for nearly half of the DoD's total annual expenditures (Apgar & Keane, 2004, p. 45). Equally significant has been the dramatic increase in service-based contracting. During the mid-1980s, approximately two-thirds of the Pentagon's acquisition budget went towards the purchase of goods and infrastructure projects while today over half of all DoD contracting dollars are used to acquire services, representing a 90% increase since 1993 (Makinson, 2004).
For many decades, DoD employed contract labor primarily for logistical and military support functions. Today, the private contractor workforce is used extensively for sensitive security- and intelligence-related tasks as well. Among several of the intelligence organizations created in the wake of 9/11, such as the National Counterterrorism Center (NCTC) and DoD's Counterintelligence Field Activity (CIFA), more than half of all staff analysts are private contractors (Pincus, 2006). This trend applies as well for many of DoD's deployed operational organizations with over 60 firms currently providing security and intelligence-related services in Iraq and 20 in Afghanistan (Cooper, 2004, p. 570). This figure includes over 6,000 private contract linguists supporting various military operations around the world at a total annual cost exceeding $250 million (Alexander, 2004). According to some estimates, nearly half of the entire U.S. intelligence budget in 2004 was spent on such procurements of commercial systems and operational support services (Shorrock, 2005), reflecting DoD's "unprecedented reliance on the contracting community for analytical staffing, workforce management, and training," according to one intelligence community expert (Pincus, 2006).
While these commercial augmentation programs have proven essential for conducting critical wartime intelligence operations, several recent government investigations have revealed deficiencies in contract administration procedures such as repeated violations of the Federal Acquisition Regulation (FAR), misuse of the Federal Supply Schedule, significant performance of out-of-scope activities by contractors, improper use of personal services contracts, and inadequate oversight of contract delivery and performance. A 2004 DoD Inspector General (IG) report reviewing contract awards for the Iraq Coalition Provisional Authority, including several vendors providing intelligence support services, found "significant weaknesses" in management procedures for 22 of the 24 contracts reviewed (DoD, Office of the IG, Report No. D-2004-057, March 18, 2004, p. 28). Likewise, one Government Accountability Office (GAO) report on intelligence support services in Iraq revealed "a lack of effective management controls" in 10 of 11 task orders worth a total of $66 million (U.S. GAO Study, GAO-05-201, April, 2005, p. 7). These reports, among others, reveal inadequate contract administration recordkeeping for intelligence support services used during recent contingency operations. While DoD intelligence organizations have aggressively exploited a wide range of commercial augmentation to satisfy expanded operational requirements, they have not dedicated sufficient resources and training to ensure the effective management and oversight of these contracts.
THE CONTRACT AWARD PROCESS
The most critical element of any successful program of commercial augmentation is the application of effective administration procedures beginning with the contract award. This process includes the tasks of identifying requirements, circulating requests for proposal, soliciting bids, conducting market research, and developing contract language. Shortfalls in any step of the development process can make effective management and surveillance of contract performance difficult, if not impossible, to achieve.
The enormous operational demands since 9/11 have placed many DoD intelligence organizations under significant pressure to rapidly expand their collection and analytical capabilities, in some cases resulting in inappropriate modification of contract award procedures. One of the problems cited in recent investigations was repeated misuse of Blanket Purchase Agreements (BPA) under the General Services Administration (GSA) Federal Supply Schedule to expedite contract awards and bypass open bidding. These violations of Federal Acquisition Regulation (FAR) were later cited by investigators as contributing factors in problems with contractor support in Iraq and at the detention facility at Guantanamo Bay for operations involving human intelligence teams, document exploitation support, strategic debriefing, linguistic services, and interrogation functions (Department of Interior IG Report, 2004).
Generally speaking, such BPAs offer the government a simplified contracting vehicle whereby an agency may use an indefinite delivery order for a broad class of goods or services where the precise quantity and delivery requirements are not known in advance. These contract vehicles are particularly useful for repeated procurements of individual services over a given period of time, particularly from habitual service providers offering a known price advantage with an established record of performance. When properly applied, this system can greatly expedite the process of solicitation and market research, yet problems with several intelligence-related contracts arose when contracting officials misused GSA schedule labor categories to acquire out-of-scope services for certain intelligence support activities. Specifically, GSA schedules used to procure strategic debriefers, interrogators, counterintelligence agents, and intelligence analysts for work in Iraq were classified as "engineering" and "information technology services." A later GAO review of these contract awards found that "the labor category descriptions in the GSA contracts were, in most cases, significantly different from the descriptions on DoD's Statements of Work and do not accurately represent the work the contractor performed" (U.S. GAO Study, GAO-05-201, 2005, p. 8).
A drawback of using such BPA awards for sensitive intelligence functions arises partly because with the GSA system the government loses a significant degree of oversight into how a vendor may fulfill an individual task order. This situation can also limit the government's discretion over the screening, vetting, and assignment of contractor personnel. Additionally, GSA procedures provide limited visibility into how a prime contractor may subcontract out various parts of the required services. For routine commercial services, this arrangement is generally satisfactory, yet is problematic as contracting officers attempt to provide appropriately suited individuals for highly technical intelligence tasks or sensitive operational requirements. The Army investigation into abuse incidents at Abu Ghraib specifically cited the potential danger of using the GSA Federal Supply Schedule for sensitive intelligence activities, noting that such "contracts should be carefully scrutinized given the complexity and sensitivity connected to interrogation operations" (DoD, Office of the IG, AR 15-6 Investigation, Abu Ghraib, 2004, p. 50).
In addition to misapplication of GSA schedules, several contracts for intelligence-related services in Iraq and Guantanamo Bay lacked sufficient market research and utilized improper solicitation procedures. Expedited awards for several support contracts with the Coalition Provisional Authority in Iraq included problems with vague requirements language, improper use of personal services contracts, and lack of price reasonableness determinations prior to award (DoD, Office of the IG, Report No. D-2004-057, March 18, 2004, p. 18). Other procedural irregularities surfaced during reviews of interrogation support contracts for the Abu Ghraib detention facility including evidence that vendors assisted in the drafting of the requirements language and preparation of Statements of Work (SOW) prior to the contract award. While there are some legal allowances for such collaboration, the subsequent contract award to the same vendor potentially presented a conflict of interest in violation of FAR guidelines (DoD, Office of the IG, AR 15-6, Abu Ghraib, 2004, p. 49).
Many of the cited discrepancies in the contract award process were attributable in part to enormous unforeseen operational demands of the GWOT. This operation placed significant strain on a limited number of contracting officials, some without adequate knowledge of the unique mission requirements or specific tasks that the vendors would perform. The Army in particular was unprepared for the surge in demand of intelligence support requirements for GWOT operations. During the initial phases of Operation Enduring Freedom (OEF), numerous intelligence organizations reported critical shortfalls of key personnel, particularly for high-demand skills sets such as linguistic support and interrogation operations. A U.S. Central Command after-action review of OEF operations reported that "the Army could not provide, and did not have an effective system in place to identify and contract for this support" (U.S. Army Central Command, Operation Enduring Freedom: CAAT Initial Impressions Report, p. 54).
DEVELOPING CONTRACT LANGUAGE
Another significant shortfall affecting some intelligence service contracting has been the lack of standardized contract language and explicit SOWs describing the nature of required support. A recent GAO report on DoD contract management procedures noted that there has been "no standardization of necessary contract language for deployment of contractors" (U.S. GAO Study, GAO-03-695, June 2003, p. 3). Such problems have led to some contract personnel arriving at duty locations with insufficient training, equipment, or professional qualifications for their assigned tasks--a problem compounded by task orders inaccurately describing the nature of services to be performed and conditions of the work environment. One contracting official involved with Operation Iraqi Freedom (OIF) noted, "the demands that we asked of our contractors were not always written in the contracts that they were supporting" (Tiron, 2003, p. 32).
The mismatch between SOW language and required contractor skill sets was cited as a compounding factor in difficulties with management of interrogators supporting OIF. The initial SOW for contract interrogation services described similar skill sets as military occupational specialty 97E, Human Intelligence Collector, yet many of the contractor personnel were later determined to lack equivalent professional training as their uniformed counterparts. Several of the contractors in question possessed experience in law enforcement or related civilian functions but lacked specific knowledge of military interrogation techniques, the Law of Land Warfare, the Geneva Conventions, and applicable DoD intelligence oversight policy (DoD, Detainee Operations Inspection, 2004, p. 88). Similar problems were identified during operations in Afghanistan where several contract interrogators supporting operations at Bagram Air Base had received no military intelligence training prior to deployment.
Another implication of poorly defined SOW language is that narrowly articulated duty descriptions can significantly limit the range of labor that a contractor may perform as mission requirements change over time. A Contracting Officer's Representative (COR) is legally unable to revise SOW language based on changing mission needs without an explicit revision to the original contract. In some cases, this situation results in undue pressure on contractors to perform out-of-scope activities for which they are not properly trained. In the case of Abu Ghraib, several of the contractors performing interrogation and analytical functions were originally employed only for translation services. The Army investigation recommended that for future operational support contracts, the "requiring activities must carefully develop the applicable SOW to include technical requirements and requisite personnel qualifications, experience, and training" (DoD, Office of the IG, AR 15-6 Investigation, Abu Ghraib, 2004, p. 49).
Another issue of concern arising from narrowly crafted contract language is that when task orders do not reflect the actual nature of work to be performed, pressure often arises from the vendor's local manager to "grow the contract" outside of the scope of the original proposal. This situation may result in operational inefficiencies for the receiving unit as well as potentially unforeseen costs to the government, as contracts must be modified after the fact to reflect the actual conditions of work performance.
Difficulties in developing precise SOW language often arise from a lack of communication between the contracting authority and the end user of the commercial service. In the case of the OIF interrogation contracts, the original SOW did not specify the need for prior training in military interrogation procedures, detainee handling policy, or applicable military intelligence doctrine. In some cases the contracting authority did not possess familiarity with the specific mission needs of the receiving unit or the manner in which contractors would be employed, resulting in the deployment of contractors not properly screened or qualified for their required duties.
For sensitive functions such as intelligence collection and analysis, it is imperative that language in the contract proposal explicitly define all performance standards and technical qualifications. This requires that contracting officers without operational intelligence experience must have close interaction with technical experts from the requiring unit and frequent interface with designated CORs located at the site of work; yet, in many cases this level of collaboration does not occur. The GAO report on management procedures in Iraq found that contracting officers "had little to no communication with the CORs in Iraq and did not follow up to obtain monthly reports from them on the contractor's performance ... [and] never verified that the Army personnel serving as CORs had appropriate training" (U.S. GAO Study, GAO-05-201, 2005, p. 12).
Communication between the contracting officer, the requiring unit, and the designated CORs must begin at the earliest stages of the Request for Proposal process to facilitate effective market research, identify the most suitable vendors, and ensure that appropriate contract language is developed that reflects actual mission requirements. Without input from the requiring unit, it is nearly impossible for contracting officers to communicate clear performance expectations to potential vendors during the solicitation process. As a review of intelligence operations during OIF concluded, the "continued use of contractors will be required, but contracts must clearly specify the technical requirements and personnel qualifications, experience, and training needed (Independent Panel to Review DoD Detention Operations, Final Report, 2004, p. 69).
CONTRACTOR TRAINING AND INTEGRATION
Detailed SOW language is also a necessary prerequisite for ensuring proper vetting, pre-deployment preparation, and integration of contracted support. The Army's Abu Ghraib investigation noted that 35 percent of the contract interrogators originally employed at Abu Ghraib lacked experience as interrogators, and none had received training on Geneva Conventions or rules of engagement for treatment of detainees (DoD, Office of the IG, AR 15-6 Investigation, Abu Ghraib, 2004, p. 51). The lack of pre-deployment training placed contract personnel "at a higher risk of violating Army policies and doctrine, and decreasing intelligence yield" to the support units (DoD, Detainee Operations Inspection, 2004, p. 87). Furthermore, military supervisors in receiving units generally had little or no control over the vetting and pre-deployment process for arriving contractors and "knew little of their [contractors'] individual backgrounds or experience and relied on higher headquarters to screen them before arrival. Such screening was not occurring" (DoD, Office of the IG, AR 15-6 Investigation, Abu Ghraib, 2004, p. 40). The Army determined that the subsequent integration of these contractors without proper training and certification "created ineffective interrogation teams and the potential for non-compliance with doctrine and applicable laws" (DoD, Office of the IG, AR 15-6 Investigation, Abu Ghraib, 2004, p. 18).
Similar pre-screening problems were also cited in the review of the initial operations at the detention facility in Guantanamo Bay. Many of the contract linguists supporting the intelligence operations had no experience with military interrogation techniques or intelligence methodologies. Although contract linguists were vetted for basic language proficiency, some of their skills sets were not appropriately matched against required duties for interrogators as the operational demands became more specific and mission requirements evolved.
Recent policy changes outlining a revised selection process, training, and certification have addressed some of these early problems with contractor integration. Currently, all DoD contract interrogators must have previously received some training on military interrogation techniques or possess equivalent educational or professional experience. Furthermore, all contract interrogators must now receive training on approved interrogation procedures, Geneva-Hague Convention, and Law of Land Warfare, and are subject to extraterritorial jurisdiction for any violations of procedures occurring in the performance of their duties (Kimmons, 2006).
In addition to pre-deployment training, contract personnel involved with intelligence support services must also be pre-screened to determine eligibility for necessary security clearances. During recent operations, some deployed contractors holding only interim clearances were unable to serve in assigned duty functions while awaiting final clearance adjudication, a situation resulting in wasted government resources and work backlogs for the supported unit. This problem was partly attributable to unmonitored vendors who did not adequately pre-screen their employees, resulting in deployed personnel unable to pass the required background checks. During the initial phases of operations in Afghanistan and Iraq approximately 30-40 percent of linguist candidates provided by DoD vendors never received final clearances for work on intelligence-related missions (Voelz, 2006, p. 76). Recent rules changes to the DFARS now stipulate that "all required security and background checks be complete and acceptable" prior to deployment, but given the enormous backlog of background investigations this requirement still presents an enormous challenge for contracting officers as they try to project support estimates for rapidly changing mission requirements (DFARS, 48 C.F.R. Pt. 252.225-7040 (h), 2004).
To effectively utilize such commercial augmentation, contracting authorities must have a clear understanding of the operational environment, mission objectives, special skills, clearance requirements, and the pre-deployment training expectations of the supported unit. These details must be clearly outlined in the initial Request for Proposal and explicitly articulated in the SOW language so vendors are able to prescreen personnel best suited for the mission requirements. Finally, contract language must clearly provide the government with a mechanism to remove and replace any contractor that does not meet the performance expectations established in the SOW.
MANAGING CONTRACTOR PERSONNEL
One of the major challenges of utilizing commercial augmentation for intelligence operations arises from the generally poor understanding of contract management procedures among military commanders. A GAO review of Army contract management procedures during recent operations noted generally "inadequate training for staff responsible for overseeing contractors and limited awareness by many field commanders of all contractor activities taking place in their area of operations" (U.S. GAO Study, GAO-03-695, 2003, Executive Summary). A separate report on management procedures for intelligence support in Iraq found that "the Army officials responsible for overseeing the contractor, for the most part, lacked knowledge of contracting issues and were not aware of their basic duties and responsibilities" (U.S. GAO Study, GAO-05-201, 2005, p. 1).
Part of the challenge in preparing military leaders for contract management responsibilities is exemplified by guidelines provided in the Army's own doctrinal manual, noting that "there is no specifically identified force structure nor detailed policy on how to establish contractor management oversight within an AOR [area of responsibility]. Consolidated contractor management is the goal, but reality is that it has been, and continues to be, accomplished through a rather convoluted system" (U.S. Army Field Manual (FM) 3-100, 2003). Existing doctrinal guidelines for managing deployed contractors were described by one recent GAO report as "inconsistent and sometimes incomplete" (U.S. GAO Study, GAO-03-695, 2003, p. 1). An independent investigation of OIF interrogation operations reinforced this finding, noting that "oversight of contractor personnel and activities was not sufficient to ensure intelligence operations fell within the law and the authorized chain of command" (Independent Panel to Review DoD Detention Operations, Final Report, 2004, p. 69).
While ample doctrinal literature exists on general contract management procedures, there is virtually no guidance that specifically deals with the unique oversight challenges of managing commercial intelligence services. The Abu Ghraib investigations noted that "no doctrine exists to guide interrogators and their intelligence leaders in the contract management or command and control of contractors in a wartime environment" (DoD, Office of the IG, AR 15-6 Investigation, Abu Ghraib, 2004, p. 49). The report also pointed out that during recent operations the "interrogators, analysts, and leaders were unprepared for the arrival of contract interrogators and had no training to fall back on in the management, control, and discipline of these personnel" (Abu Ghraib, 2004, p. 49).
In addition to a lack of clear doctrinal standards there is also significant confusion among some military supervisors concerning their responsibilities and legal authorities over contract personnel. Recent investigations revealed that intelligence "leaders faced numerous issues involving contract management ... with respect to contractors; roles, relationships, and responsibilities of contract linguists and contract interrogators with military personnel; and the methods of disciplining contractor personnel" (Abu Ghraib, 2004, p. 18). In many cases leaders unfamiliar with their management obligations will defer these responsibilities to a vendor's onsite manager for matters such as performance evaluation, discipline, and oversight requirements--a situation that essentially amounts to vendors providing their own management and evaluation.
CONTRACTING OFFICER'S REPRESENTATIVE TRAINING
Perhaps the most important tool for achieving effective oversight of commercial services is the Contracting Officer's Representative (COR), providing on-site surveillance of the contractor's work. Yet, critical shortages of DoD intelligence personnel have resulted in the lack of formal training in contract administration procedures for many organizational CORs, who in some cases do not serve in close proximity to the site of work performance. Given the habitual shortfalls in training resources, these CORs are often required to learn their skills through "on the job training"; but as the Abu Ghraib investigation noted, "if functions such as these [intelligence] are being contracted, MI [military intelligence] personnel need to have at least a basic level of contract training so they can protect the Army's interests" (Abu Ghraib, 2004, p. 51).
A sampling of several ongoing operational support missions suggests a wide variance in procedures and training standards for CORs managing intelligence support contracts. This is due in part to the fact that the specific training requirements for CORs are only vaguely defined by the Defense Federal Acquisition Regulation Supplement (DFARS), and typically established internally by individual government department or agency. For example, during the first 18 months of operations at the joint detention facility in Guantanamo Bay, no assigned on-site government COR was monitoring contract performance for the linguist and interrogation support personnel (Voelz, 2006, p. 78). The Army investigation of Abu Ghraib revealed similar problems with CORs operating at different locations from the contractor's work, noting that "it is very difficult, if not impossible, to effectively administer a contract when the COR is not on site" (DoD, Office of the IG, AR 15-6 Investigation, Abu Ghraib, 2004, p. 52). A separate investigation into DoD's contract management procedures also determined that "personnel acting as CORs did not, for the most part, have the requisite training and were unaware of the scope of their duties and responsibilities" (U.S. GAO Study, GAO-05-201, 2005, p. 18).
Few deployed DoD intelligence organizations have the dedicated resources for long-term oversight by a single individual. Instead, COR responsibilities are often assigned to intelligence specialists as "additional duty" to be performed adjunct to their primary leadership, analytical, or collection management tasks. Frequent rotations of intelligence personnel only exacerbate the challenge of providing continuity of surveillance. Frequently, when a new COR arrives on site, there remains only limited documentary evidence of the vendor's previous work that can provide a useful basis for comparative analysis. Commonly, the vendor's site manager will be the only individual with lengthy operational experience at a given location. All of these factors make it extremely difficult for intelligence specialists without specific contract management experience to effectively fulfill their responsibilities as CORs.
Another challenge for inexperienced CORs is defining clear performance measures and effective surveillance methodologies to evaluate a vendor's work. For many major DoD contracts, dedicated personnel from the Defense Contract Management Agency (DCMA) will oversee a vendor's performance, but these personnel are in critically short supply. Over the past decade, DoD has reduced acquisition management personnel by nearly half while simultaneously more than doubling services contracting (Barr, 2005). As a result, most contracts for operational intelligence support services will be monitored by organizational CORs, in many cases with only limited training in contract surveillance techniques.
Compounding this challenge for inexperienced CORs, few service contracts offer detailed metrics for evaluation of a contractor's performance. SOWs for intelligence and linguistic services will often contain initial qualification criteria, but typically not provide any instruction for skills maintenance programs, developmental training, or periodic reevaluation. Most of the criteria for work evaluation are informal at best with little consideration given to developmental counseling or periodic performance review. These tasks are generally left to the vendor's on-site contract manager, but often occur without sufficient government surveillance.
The difficulty of defining effective evaluation metrics has become even more challenging as the government moves toward greater use of Performance-Based Service Acquisition (PBSA). This contracting methodology focuses less on specific process description and more on results-based evaluation where the requiring activity defines specific performance goals, known as a Statement of Objectives, then provides vendors with significant latitude in developing work plans to satisfy the government's needs. The benefit of this approach is that vendors are not bound by a specific SOW description and are free to devise optimal solutions for satisfying the government's needs. DoD has established a goal to award 50% of all acquisition dollars utilizing PBSA methodology by FY 2005 (Bolton, 2004).
While most current operational support contracts for intelligence-related activities still employ traditional SOW methodology in which specific labor functions are clear, still somewhat uncertain is how PBSA may be applied for future intelligence support contracts. Although PBSA has clear advantages of leveraging vendor expertise to develop creative solutions to satisfy government needs, this system also places a much greater burden on contracting officers to clearly define mission objectives, conduct careful market research for appropriate vendors, closely manage performance, and evaluate standards of work against the achievement of broad mission objectives. PBSA only increases the necessity of well-trained intelligence professionals closely monitoring and evaluating the contractor's contribution to the overall mission goals. Present deficiencies in contract surveillance practices leave considerable doubt as to the government's ability to adequately utilize these management concepts for sensitive intelligence-related functions, particularly given current shortages of government contracting officers familiar with PBSA methodology (Phillips, 2004). Certainly, even fewer intelligence specialists possess the necessary experience and training to employ these complex management methodologies.
Given that few intelligence specialists possess extensive contract management experience, arming them with general "rules of thumb" is critical in assisting them to make appropriate determinations on the uses of commercial augmentation within their organizations. Due to the sensitive nature of many intelligence support functions, careful consideration must be given to the suitability of private sector augmentation so that public interest is adequately protected. These criteria are not intended as definitive guidelines for validating the applicability of all commercial augmentation programs, but rather serve to highlight some fundamental considerations for effective integration and management of commercial services. These "rules of thumb" offer evaluative criteria in three critical areas: acceptability of private sector involvement, suitability of vendor services, and accountability of contract management procedures.
The enormous intelligence demands of the Global War on Terrorism will require continued reliance on commercial augmentation to satisfy operational requirements. Specialized vendors continue to provide critical skills and services that are not sufficiently resourced within the Intelligence Community and cannot be acquired through traditional government hiring practices. Yet, contract management functions are still not viewed as a core competency among intelligence professionals and frequently misunderstood or neglected by community leaders.
As demonstrated in the preceding discussion, shortcomings in any aspect of the contract management process may lead to poor integration of commercial services, ineffective oversight, and compromise of government interest. For private sector resources to be effectively leveraged by the Intelligence Community, leaders and acquisition specialists must cooperate to improve management practices and provide adequate training and resources to ensure effective oversight of these highly sensitive commercial services.
The views expressed in the article are the author's and do not reflect the official policy or position of the Department of Defense or the U.S. Government.
LEADER "RULES OF THUMB" FOR DETERMINING THE APPLICABILITY OF COMMERCIAL AUGMENTATION FOR INTELLIGENCE SUPPORT SERVICES
Acceptability of Private Sector Involvement
* Contract service does not perform inherently governmental functions.
* Contract administration adheres to proper solicitation and award procedures.
* Use of commercial services does not present operational or intelligence security risks.
* Vendor offers a best value alternative (including price and performance standards).
Suitability of Vendor Services
* Vendor offers unique services or products unavailable in the public sector.
* Vendor offers scalability, of service and flexible output to meet mission requirements.
* Contract is negotiated in a mature market environment with in-sector competition.
* Bidder possesses established performance record and known reliability.
Accountability of Contract Management Procedures
* Contract language provides appropriate legal oversight and accountability measures.
* Contract has detailed Statement of Work (SOW) and qualification requirements.
* Contract provides effective contractor integration and training plan.
* Contract offers clear performance measures and evaluation methodology.
* Government possesses appropriately trained on-site contract management personnel.
Alexander, K. B. (2004, April 7). Statement before the Committee on Armed Services Subcommittee on Strategic Forces, 108th Cong., 2nd session. Retrieved May 2, 2005, from http://armed-services.senate.gov/statemnt/2004/April/Alexander.pdf
Apgar, M. & J. Keane. (2004, September). New business with the new military. Harvard Business Review 82(9), 45-56.
Barr, S. (2005, May 30). Defense bills push for stricter contract procedures. Washington Post.com. Retrieved June 4, 2005, from http://www.washingtonpost. com/wpdyn/content/article/2005/05/29/AR2005052900991.html
Bolton, C. M. (2004, March 10). Performance based service acquisition. (Memorandum). Washington, DC: Department of the Army.
Cooper, M. H. (2004, June 25). Privatizing the military. CQ Researcher 14(24), 568-587.
Defense Federal Acquisition Regulation Supplement. (1998). Retrieved from http://www.acq.osd.mil/dpap/dars/dfarspgi/current/index.html
Department of Defense. (2004). Office of the Inspector General. AR 15-6 Investigation of Abu Ghraib Prison and the 205th Military Intelligence Brigade. Retrieved August 25, 2004, from http://www.globalsecurity.org/intell/library/reports/2004/800-mp-bde.htm
Department of Defense. (2004, March 18). Office of the Inspector General. Contracts awarded for the Coalition Provisional Authority by the Defense Contracting Command--Washington, Report No. D-2004-057 (PDF). Retrieved September 30, 2004, from http://www.globalsecurity.org/military/library/report/2004/ 04057sum.htm
Department of Defense. (2004, July 21). Detainee operations inspection. Retrieved August 16, 2004, from http://www4.army.mil/ocpa/reports/ ArmyIGDetaineeAbuse
Department of Interior. (2004, July 16). Office of the Inspector General. Review of 12 procurements placed under General Services Administration Federal Supply Schedules 70 and 871 by the National Business Center. Washington, DC: DOI Publication.
Independent Panel to Review DoD Detention Operations. (2004, August). Final report of the independent panel to review DoD detention operations. Retrieved August 24, 2004, from http://www.defenselink.mil/news/Aug2004/d20040824finalreport.pdf
Kimmons, J. E (2006, March 7). Contract interrogator selection, training, and certification requirements. (Memorandum). Washington, DC: U.S. Department of the Army.
Makinson, L. (2004, September). Outsourcing the Pentagon. The Center for Public Integrity. Retrieved September 30, 2004, from http://www.publicintegrity.org/pns/report.aspx?aid=386
Phillips, Zack. (2004, November 17). Performance-based contracts gaining popularity--but is the government ready to use them? Retrieved March 17, 2005, from CQ Homeland Security digital archive, a subscription, fee-based service at http://www.cqhls.com/
Pincus, W. (2006, May 7). Lawmakers want more data on contracting out intelligence. Washington Post.com. Retrieved May 7, 2006, from http://www. washingtonpost.com/wpdyn/content/article/2006/05/06/AR2006050601088.html
Shorrock, T. (2005, January-February). The spy who billed me. Mother Jones. Retrieved March 8, 2005, from http://www.motherjones.com/news/ outfront/2005/01/12_400.html
Tiron, R. (2003, September). Army not equipped to manage contractors on the battlefield. National Defense 88(598), 32.
U.S. Army Central Command. (2002, September). Operation Enduring Freedom: Afghanistan, Army Central Command Combined Armed Assessment Team (CAAT) Initial Impressions Report 2002, Leavenworth: Center for Army Lessons Learned. Chapter 3: Intelligence Operations, pp. 43-67. Available through the Center for Army Lessons Learned digital archive at http://call.army.mil/. Documents stored in this archive are unclassified but can not be publicly accessed without DoD user identification.
U.S. Army. (2003, January). Contractors on the battlefield. Field Manual (FM 3-100). Washington, DC: U.S. Department of the Army.
U.S. Government Accountability Office Study. (2005, April). Interagency contracting: Problems with DoD's and Interior's orders to support military operations (GAO-05-201). Retrieved May 11, 2005, from http://www.gao.gov/highlights/ d05201high.pdf
U.S. Government Accountability Office Study. (2003, June). Military operations: Contractors provide vital services to deployed forces but are not adequately addressed in DoD plans (GAO-03-695). Retrieved October 13, 2004, from http://www.gao.gov/highlights/d03695high.pdf
Voelz, Glenn J. (2006). Managing the private spies: The use of commercial augmentation for intelligence operations. (Discussion Paper No. 14). Washington, DC: Center for Strategic Intelligence Research.
MAJ Glenn James Voelz, USA is an Army intelligence officer currently serving as the executive assistant to the director for intelligence, Joint Chiefs of Staff. Previously, he served as the joint intelligence advisor to Saudi Arabian Ministry of Defense and Aviation, responsible for industrial security oversight of U.S. Security Assistance Programs, intelligence training, and doctrinal development for the Saudi Arabian Armed Forces. MAJ Voelz is a graduate of the United States Military Academy at West Point and holds master's degrees from the University of Virginia and the National Defense Intelligence College.
(E-mail address: email@example.com)
|Printer friendly Cite/link Email Feedback|
|Author:||Voelz, Glenn James|
|Publication:||Defense A R Journal|
|Date:||Dec 1, 2007|
|Previous Article:||Test and evaluation lessons learned from the field.|
|Next Article:||Beyond Lean and Six Sigma.|