Printer Friendly

Feasibility of a joint engineering and logistics contract.


It is my great pleasure to present another of the Wright Flyer Papers series. In this series, Air Command and Staff College (ACSC) recognizes and publishes the "best of the best" student research projects from the prior academic year. The ACSC research program encourages our students to move beyond the school's core curriculum in their own professional development and in "advancing aerospace power." The series title reflects our desire to perpetuate the pioneering spirit embodied in earlier generations of airmen. Projects selected for publication combine solid research, innovative thought, and lucid presentation in exploring war at the operational level. With this broad perspective, the Wright Flyer Papers engage an eclectic range of doctrinal, technological, organizational, and operational questions. Some of these studies provide new solutions to familiar problems. Others encourage us to leave the familiar behind in pursuing new possibilities. By making these research studies available in the Wright Flyer Papers, ACSC hopes to encourage critical examination of the findings and to stimulate further research in these areas.

John W. Rosa, Brig Gen, USAF


Feasibility of a Joint Engineering and Logistics Contract

Background and Value of Civil Augmentation Service Contracts

The Army, Air Force, and Navy currently manage separate engineering and logistics contracts for employing civilian contractors as a force multiplier during military operations. These contracts are commonly referred to as "civil augmentation" contracts. Civil augmentation contracts afford flexibility when the services are limited by the availability of force structure during contingency scenarios. Active duty forces are often constrained by real world requirements or taskings that limit their use, such as having to maintain response capability for a major regional conflict. At the same time, activation of reserve and guard forces to fulfill manpower requirements, in certain scenarios, may be politically sensitive. There are also instances when the United States would like to stay engaged in nation-building or peacekeeping operations within a country, but needs to maintain a low military presence due to political considerations. Other factors, which lead to the use of an augmentation contract, are the lack of in-place host-nation support agreements in numerous underdeveloped countries and troop ceiling restrictions imposed by those host nations. (1) (See appendix A for further background information.)

Significance of Problem

A General Accounting Office (GAO) report, Contingency Operations: Opportunities to Improve the Logistics Civil Augmentation Program, however, questioned

the validity of each military service executing its own separate contract and stated that the services provided under the separate contracts were similar in nature. The report implied that it might be more "effective and efficient" if one service acted as the lead executive agent to eliminate duplication of services. The GAO report also noted that existing military doctrine was vague in addressing how to integrate contractor resources properly with the military force structure during contingency situations. (2)

Joint Publication (JP) 4-0, Doctrine for Logistic Support of Joint Operations, is the primary joint publication providing combatant commanders and military planners guidance on the conduct of logistics support during joint operations. This document outlines the responsibilities for logistics operations to include supply, maintenance, transportation, facilities engineering, health services, command and control, and several other areas. JP 4-0, however, does not address the fact that civilian contractors increasingly are being tasked to provide the aforementioned services for military operations.

When using civilian contractors, the deployed military commander must consider a whole new list of issues to include contractor security, status of forces agreement (SOFA) and clearance restrictions, and contractor and military force integration. Unfortunately, existing joint doctrine does not provide guidance as to when and how civil augmentation contracts should be used in support of military operations during wartime and small-scale contingencies.

Statement of Research Questions

This research paper addresses two of the important questions raised in the GAO report regarding the use of contractors in support of joint military operations. First, will a joint engineering and logistics service contract provide the combatant and service commanders any benefit over maintaining individual Navy, Army, and Air Force civil augmentation contracts? Second, does current joint doctrine adequately address the use of contractor services in support of contingency and wartime operations? If not, what information should be included in future joint doctrine?

Preview of Argument

The development of a joint civil augmentation program (JCAP) contract will prevent individual program redundancies, while eliminating possible competition among the services and providing efficiencies in the areas of personnel resources and program costs. As stated in the GAO report, unnecessary duplication of effort and functions may have occurred as a result of employing individual Army, Air Force, and Navy contracts to provide engineering and logistics support in combined forces scenarios. (3) However, while some duplication may exist among individual service contracts, the Army's Logistics Civil Augmentation Program (LOGCAP) contract and the Air Force's Contractor Augmentation Program (AFCAP) contract provide numerous benefits to their individual service components. The intent of JCAP is to build upon this foundation with a shift in focus to the ultimate customer, the war-fighting commander in chief (CINC).

This paper will also show that current joint doctrine inadequately addresses the numerous issues regarding employment of contractors in the battlefield. This research effort will provide the issues and doctrinal guidance to be addressed in JP 4-0 and the Joint Task Force (JTF) Commander's Handbook for Peace Operations. Such issues as contractor security, host-nation restrictions, and deployment issues have to be provided to the CINC planners and deployed commanders for effective employment of contractor operations during military operations.

Because of its limited scope, the Navy's Construction Capabilities Contract (CONCAP) will not be analyzed in depth. The Navy contract is for emergency construction and engineering services only and does not include additional support in areas such as services and logistics. The majority of service-related and contract-specific issues will be sufficiently addressed in this paper through the analysis of the AFCAP and LOGCAP contracts.

Analysis of Logistics Civil Augmentation Program

LOGCAP was developed based on the Army's experience during the Vietnam War. During Vietnam, the Army was forced to rely on civilian contractors because its Reserve and Guard forces were never activated. In 1992 the Army awarded its first centrally managed LOGCAP contract through the US Army Corps of Engineers (USACE) to Brown and Root Services Corporation. The cost-plus award-fee (CPAF) contract was awarded for one basic and four option years. Under this contract, the Army has supported six contingency operations beginning with Operation Restore Hope in Somalia and is currently supporting Operation Joint Endeavor in Bosnia. Total estimated contract value to date is $1 billion. (4) The Army Materiel Command (AMC) in 1997 awarded the LOGCAP follow-on contract to DynCorp Aerospace Technology. This contract is also a CPAF contract with one basic and four option years, but it contains fixed-price line items for planning efforts.

A team consisting of a program manager and approximately 15 other people manages the program. The team is comprised of two directorates responsible for planning and business management. The planning directorate works with each Army major command (MACOM) and has incorporated the use of LOGCAP into various operations plans (OPLAN) and concept plans (CONPLAN). Communications and Electronics Command (CECOM) at Fort Monmouth, New Jersey, provides contracting support for LOGCAP. Defense Contract Management District-International (DCMD-I) provides contract administration services during contractor operations.

Services Provided

Per the statement of work (SOW), "The objective of LOGCAP is to preplan for the use of commercial contractors to prepare plans and execute approved plans to provide logistics services and construction/engineering support with reasonable assurance of success and within reasonable cost." (5) Under the planning effort, the contractor maintains three types of permanent management plans: a worldwide management and staffing plan (WMSP), a generic undeveloped and developed country management plan, and regional management plans (RMP). (See appendix B.) Additionally, the LOGCAP contract requires DynCorp to develop, at the request of the procuring contracting officer (PCO), CINC/MACOM specific requirements support plans. These plans are based upon specific CINC/MACOM requirements, which are generated in support of specific OPLANs, CONPLANs, and functional plans. In conducting this effort, the contractor works with the staffs of the supported Army MACOM to develop, maintain, and refine LOGCAP planning documents. (6) Cost for the management staff, which includes the worldwide plan, is $865,000 per year. Yearly cost to maintain the regional plans is $30,000. (7)

Support provided by the LOGCAP contractor during wartime or contingency operations can be broken down into five areas: supply operations, field services, engineering and construction, maintenance, and transportation. (See appendix C for a detailed list of services provided.)

Requesting LOGCAP

The Army uses a decision matrix to decide whether to use LOGCAP to support wartime or contingency operations. (See appendix D for decision criteria.) After the decision is made to use the LOGCAP contract, the theater Army service component commander forwards the request to the Department of the Army for a final decision. If approved, the request is then passed on to the LOGCAP project manager at AMC. The LOGCAP management staff will generate a SOW for the contractor in conjunction with the theater staff. The PCO generates a delivery order for the services once funding is received from the theater command. The PCO also delegates contract administration to DCMD-I and USACE. The LOGCAP management staff deploys to the area of responsibility (AOR) to assist in planning and managing the contract. The LOGCAP management team consists of a program manager, a CECOM/PCO, contractor representatives, a USACE representative for technical advice, DCMD-I personnel to perform contract administration and quality assurance evaluation (QAE) duties, a LOGCAP support unit, and a logistics support element. The team falls under the operational and administrative control of the theater logistics support element commander. (8) To assist potential users of LOGCAP services, the LOGCAP Program Management Office has developed the LOGCAP Battlebook and AMC Pamphlet 70030 as user's guides to assist customers in understanding the capabilities of LOGCAP.

Benefits: Force Multiplier

LOGCAP is a force multiplier and provides the Army numerous benefits. First, preplanning of contractor efforts, as with deliberate planning directed by the Joint Strategic Capabilities Plan (JSCP), lays the groundwork for quick and smooth execution during military operations. As in Vietnam, much of the Army's combat support (CS) and combat service support (CSS), especially its construction capability, is maintained in its Reserve component. Deployment of Reserve forces, however, requires presidential activation, time to mobilize, and military strategic lift. LOGCAP can fill this force structure gap by mobilizing immediately upon PCO notification. In accordance with the contract, DynCorp has to be ready to deploy in 72 hours, with initial support by C+15 and full capability at C+30. The LOGCAP contractor also provides its own strategic and in-theater lift capability. LOGCAP is not dependent on the Department of Defense (DOD) logistics system; therefore, it can source materials independently and lessen the Army's burden on the logistics system. It also provides the CINC with a suitable workaround when military force caps are in place. Contractor augmentation lessens the military "tooth-to-tail" ratio and enables available troops to concentrate on mission critical tasks.

Benefit: Cost Control

The LOGCAP contract's award fee ranges from 0 to 5 percent for above average performance with no base fee. Contractor performance is rewarded in the areas of delivery, quality of performance, and cost. Learning from Bosnia, the LOGCAP management staff (Army program managers and contractor personnel) has also improved its cost reporting procedures and benefited from the oversight provided by the DCMD-I Contingency Contracting Administration Services (CCAS) teams who perform contract monitoring. Another potential benefit of LOGCAP is that according to one recent report by the Logistics Management Institute, "when compared with the costs of using an equivalent military force, the use of LOGCAP contractors is economical." (9) The report stated that the LOGCAP contractor employed 24 percent fewer personnel than an equivalent military force package for operations conducted in Bosnia. Using the equivalent military force package, the report also compared marginal costs and found the contractor to be 28 percent less expensive. (10) Since the Army MACOMs do not budget for funding LOGCAP, there is an initial "sticker shock" felt by both the MACOMs and the deploying commanders as they try to control costs from their operation and maintenance funds. Overall, LOGCAP provides the Army an effective and efficient capability to augment deployed military forces.

Other Benefits

In addition to its capability-related benefits, the LOGCAP contract provides some side benefits within the host country. The LOGCAP contractor benefits the local economy since the contractor hires personnel from the local workforce and subcontracts to local vendors. In Operation Joint Endeavor in Bosnia, 80 percent of the contractor's workforce was local foreign nationals. (11) Use of the LOGCAP contractor also allows for a reduced US military presence in the country of operations and minimizes the local reaction to these forces. The trade-off, however, is in force protection, which will be discussed next.

Considerations: Security in a Hostile Environment

The LOGCAP contractor is self-sufficient in its operations to support US forces, however, the CINC employing LOGCAP support has an obligation to provide security for the contractor. The level of security depends on the degree of hostility in the area of operations, regardless of whether the operation is during wartime or a small-scale contingency. Security precautions may include providing military escorts for line-haul operations, requiring the contractor and its nonlocal employees to live on and conduct operations from military compounds, and providing contractor employees with small arms. The importance of providing contractor force protection was illustrated during Operation Desert Storm. After receiving chemical attack warnings, contractor personnel providing food service at several Air Force installations walked off the job. The personnel returned to the installations only after receiving appropriate protective equipment. (12) In addition to providing for contractor security, deployed commanders must weigh the risks associated with providing nonmilitary personnel access to military installations. Contract personnel, especially host-nation personnel, are potential security risks as they may be sympathizers with the enemy. (13)

Considerations: Status of Forces and Omnibus Agreements

The gaining CINC must also ensure that SOFA and omnibus agreements include provisions concerning the LOGCAP contractor and its employees. For instance in Operation Joint Endeavor, Hungary would not allow the contractor to bring its employees in-country since it was not part of the omnibus agreement. The Hungarian government, however, was eventually persuaded to allow these employees access after it received assurances that a large portion of Brown and Root's workforce would be Hungarian. (14) The Hungary Ministry of Finance also imposed a value added tax on Brown and Root and an income tax on its employees. The US government ended up reimbursing Brown and Root for the $18 million in costs since the LOGCAP contract is a cost reimbursable contract. (15) The US government was later able to amend the omnibus agreement with Hungary and recoup the money. (16)

Considerations: Cultural Issues

The LOGCAP contractor's hiring of foreign nationals can create communication and cultural challenges. For instance, Saudi truck drivers providing line-haul services after Desert Storm routinely cooked meals on small propane stoves near their vehicles. This practice was alarming to Army ordnance personnel, especially when the cargo being hauled was high explosive ordnance. (17)

Significant Lessons Learned

Operation Joint Endeavor in Bosnia pointed out some key lessons. First, this operation showed that LOGCAP "is not always an initial entry capability" because the contractor requires time to set up its operations. However, Joint Endeavor illustrated that the LOGCAP contractor "is well suited to take over base camp maintenance and operations after initial base camp construction." (18) In Bosnia, a unique challenge was created for the team consisting of Air Force Rapid Engineer Deployable Heavy Operational Repair Squadron Engineer (RED HORSE) troops, Navy SeaBees, and Brown and Root workers because of the large number of troops already deployed in-theater, the harsh Balkan winter, and the decision to build more and smaller camps. However, their joint effort created a synergy that contributed to a greater success than any one service's engineers could accomplish and allowed the team to meet the challenge. (19)

Although the contractor has its own strategic lift capability, the contractor may be subject to the same logistical constraints as the military. Several factors can result in degradation of the contractor's ability to bring equipment and supplies into theater. These include crowded lines of communications (LOC), an austere operating environment, and a theater with damaged infrastructure or limited economy. For example in Bosnia, Brown and Root rail and truck shipping competed against the needs of the very troops the contractor was there to support. Contractor aircraft also competed with military aircraft for available ramp space. (20)

Doctrine for Logistic Support of Joint Operations provides guidance to the geographic combatant commander and re commends the establishment of a joint civil-military engineering board (JCMEB), joint facilities utilization board (JFUB), and CINC logistic procurement board (CLPSB). (21) These boards are to be used to establish theater policy, procedures, direction, and priorities and to provide coordination for construction and engineering, facilities, and contracting activities. The development of a joint acquisition review board (JARB) and joint contracting committees in Operation Joint Endeavor and their resulting success p roved the merit of the JP 4-0 guidance. Their establishment was critical for elimination of competition among the different contracting activities for local resources, consolidation of requirements, and overall control and management of the acquisition system. A JARB located in Hungary, Croatia, and Bosnia reviewed requirements and established priorities. The requirements, after being funded, were then passed to the joint contracting committee, which determined whether host-nation support, local purchase through central region or joint contracting centers, or LOGCAP would be used to fulfill the requirement. (22)

Operation Joint Endeavor showed the need for LOGCAP program management representation on the CINC planning and management staffs as well as the staffs of the deployed commanders in Bosnia, Croatia, and Hungary to provide an understanding of the scope and capabilities of the contract. Establishment of the JARB eventually helped eliminate misconceptions about the performance of Brown and Root. (23) Appointing base camp "mayors" as focal points for the contractor also improved the relationship between the contractor and customer. Communication between the two parties improved and the contractor gained a clearer understanding of what it deemed constantly changing requirements. (24)

Analysis of Air Force Contractor Augmentation Program

AFCAP is a contingency support contract the Air Force developed to relieve or augment military operations in small-scale contingencies. Primary areas of support include logistics, services, engineering, and operations and maintenance. The contract supports all phases of military operations to include planning, mobilization, construction, sustainment, reconstitution, and restoration. In supporting small-scale contingencies, the AFCAP contract can also provide relief support for natural disasters worldwide. Since the AFCAP contract was awarded in 1997, it has only been used for two large-scale taskings--typhoon relief at Anderson Air Force Base (AFB) in Guam and Hurricane Georges relief at Keesler AFB, Mississippi.

The AFCAP contract was awarded to Readiness Management Support (RMS) as a joint venture between Johnson Controls and Lockheed Martin for a period of one base year with four option years. The contract is CPAF with a fixed-price line item for worldwide manpower backfill at military bases. AFCAP has the capacity to handle up to $452.6 million in task orders over the life of the contract. (25) The basic annual contract costs cover contractor program management, development and maintenance of a worldwide management plan (WMP), and two annual validation exercises. These basic contract costs are funded by the Air Force Civil Engineer. Individual task orders are funded by the requesting Air Force major command (MAJCOM) or using agency. (26)

The contract is managed by a dedicated management team comprised of two full-time program managers assigned to Headquarters Air Force Civil Engineer Support Agency (AFCESA) and two full-time contracting officers assigned to the 325th Contracting Squadron, both located at Tyndall AFB, Florida. In addition, either the MAJCOM or DCMD-I provides on-site surveillance. (27) The Air Force has also developed an AFCAP user's guide outlining the responsibilities of AFCESA, contracting, DCMD-I, and the user.

Sustainment versus Beddown

The genesis of AFCAP was a request from Brig Gen John Allen, the Air Combat Command Civil Engineer, at the 1994 Air Force Civil Engineer Worldwide Conference. General Allen saw a clear need for a worldwide sustainment contract to relieve military troops from performing nontraining-related repetitive tasks. (28) Although the AFCAP contract can accomplish beddown taskings, its focus is sustainment activities. Beddown taskings provide excellent training for such military forces as Prime Base Engineer Emergency Force (Prime BEEF) and RED HORSE, which provide the Air Force organic beddown capabilities. Examples of beddown taskings include tent setup and utilities installation. As illustrated by the successful support Air Force organic forces provided US forces in Bosnia, the Air Force needs to maintain a responsive in-house beddown capability. AFCAP is primarily a relief or augmentation tool for prolonged sustainment activities.


The AFCAP contractor's notional timeline for deployment is not tied to the initiation of conflict. Since the Air Force employs Prime BEEF and RED HORSE for initial beddown activities, Air Force MAJCOM leaders determine the appropriate time to transition to the AFCAP contractor workforce to relieve these military forces. Although the contract typically requires RMS to respond within 30 days, the contractor responded immediately during its first two deployments.

Worldwide Management Plan

In contrast to the numerous LOGCAP plans, the Air Force has required its AFCAP contractor to develop and maintain only one generic WMP, at a cost of approximately $300,000, which the Air Force believes can be tailored or adapted quickly to meet the specific needs of any crisis. The AFCAP plan is tested or validated twice each year during a tabletop exercise with the contractor. RMS is required to adapt its WMP to the specific scenario and provide an overall plan within 24 hours. According to AFCESA program management and contracting staff, the worldwide management plan is very flexible and affords the Air Force great versatility at a tremendous cost savings. Since the plan is not country, region, or type of contingency specific, it is less likely to become outdated than a detailed, site-specific plan. Due to the uncertainty as to where the next crisis will arise, AFCESA personnel believe a generic plan provides an adequate foundation from which to build a scenario-specific management plan.

Benefits: Tailored for Air Force Needs

The AFCAP contract was developed by AFCESA to support Air Force customer requirements worldwide. The contract was specifically tailored to meet on-going Air Force needs. As a result, the program managers have a functional understanding of Air Force operations, culture, procedures, and regulations. This high level of familiarity with customer needs translates into increased responsiveness and efficiency on the part of the AFCESA staff.

Benefit: Cost Control

The primary contractual incentive for superb contractor performance under the AFCAP contract is the award fee. "The award fee provides motivation for excellence in such areas as quality, timeliness, technical ingenuity, and cost effective management." (29) The AFCAP award fee is capped at 6 percent and is comprised of 40 percent for cost control, 35 percent for technical performance, and 25 percent for management. Award amounts are determined every six months by the Award Fee Board, and the approved award percentage is applied to all active task orders for that period.

Benefit: Force Multiplier

Used as a force multiplier, the AFCAP contract can alleviate several manpower, equipment, and training issues associated with sustained small-scale contingencies. There has been a substantial increase in the number of sustained contingency deployments Air Force personnel have supported over the last decade. As a result, home bases worldwide have endured prolonged losses of both manpower and equipment to support these operations. These losses have resulted in higher "ops-tempo" at most home bases and have affected the level of base support provided by many functions. Within civil engineering, for example, the loss of manpower can degrade a squadron's ability to sustain facility maintenance and repair on an installation. Although augmentation of home base manpower is not a primary role of the AFCAP contract, it has the ability to backfill manpower positions at home bases both within and outside the continental United States. The contract can also provide supplies and equipment to alleviate depletion of critical war reserve materiel (WRM) stockpile levels. RMS is generally expected to provide transportation of both personnel and equipment to the deployed location. The Air Force may choose to provide airlift for RMS to save cost; however, the Air Force maintains the flexibility of not having to provide those lift assets.

Limitation: Nonhostile Work Environment

The AFCAP contract cannot be employed in hostile environments. Under the Air Force's program, the contract can be used only in response to natural disaster crisis or small-scale contingencies that are considered nonhostile. If hostile activities should emerge, RMS and AFCESA would determine the appropriate time to disengage contractor forces. (30) Regardless of the situation, the US government is responsible for perimeter defense in both hostile and nonhostile environments. By restricting contractor forces from hostile environments, the Air Force limits its exposure to numerous safety, security, and legal issues.

Other Limitations

The AFCAP contract cannot be used for purchase of supplies. RMS is restricted to buying supplies in support of its own operations. Air Force deployed forces depend on contingency contracting officers to provide local purchase support of supplies and services. On-site military commanders often believe a loss of flexibility or responsiveness results when functions are contracted out. They have less control over contract employee actions and can not arbitrarily assign tasks as could be done with military forces. As discussed in the LOGCAP section, the AFCAP contractor may also be limited by SOFA and omnibus agreements and the problems associated with hiring foreign nationals.

Significant Lessons Learned

AFCAP was used in December 1997 in reaction to the typhoon that hit Anderson AFB and in the fall of 1998 in the aftermath of Hurricane Georges at Keesler AFB. As a result of those experiences, two key lessons learned were generated. First, funding streams need to be addressed. The MAJCOMs provide the funding for AFCAP use, yet they do not budget for this use. This leads to sticker shock when contingency costs are provided, even though AFCAP is often cheaper compared to life cycle cost with WRM assets. Second, commanders at deployed locations must be educated immediately about the capabilities and limitations of AFCAP. As a result of these natural disaster experiences, the AFCESA project manager now provides training immediately upon contract initiation to prevent unrealistic staff expectations and facilitate smooth contract execution. (31)

Joint Contract Analysis

After reviewing both contracts, it is apparent that the LOGCAP and AFCAP contracts are similar in scope. The differences are due to (1) the Army's broader need for services because of its reliance on Guard and Reserve units to provide CS and CSS and (2) the Air Force's need for a sustainment force to relieve its troops and equipment from the high operations tempo that has been experienced since the end of the cold war. Since the scope of the two contracts is similar, it would seem possible to develop a joint civil augmentation program contract to meet the needs of both services. A joint contract should eliminate duplication of services provided and streamline management oversight.


The first step in developing a JCAP contract would be to establish the requirements of both services. Army requirements would obviously mirror the requirements in the LOGCAP SOW: (1) Preplanning to include maintenance and updates of the WMSP, generic underdeveloped and developed country management plans, and the nine RMPs and (2) CS and CSS augmentation capability broken down in the categories of supply operations, field services, engineering and construction, and maintenance and transportation. Air Force requirements would mirror requirements in the AFCAP SOW and would focus on the functions performed by Prime BEEF teams and Prime Readiness in Base Services (Prime RIBS) teams. The only Air Force unique requirements to be added to the Army requirements would be home base backfill shop support and airfield support, which includes airfield unique facilities, utilities, runways/ taxiways/parking ramps, aircraft arresting systems, lighting, markings, and emergency power. Construction standards, as is currently the case in both the AFCAP and LOG CAP SOWs, would be based on JP 4-0.

Contract Type

The JCAP contract would be a task order, indefinite-quantity contract. Per Federal Acquisition Regulation (FAR) 16.504(b) a task order, indefinite-quantity contract is appropriate for acquiring services "when the Government cannot pre determine, above a specified minimum, the precise quantities of services that will be required during the contract period, and it is inadvisable for the Government to commit itself for more than a minimum quantity." (32) Against this basic contract, task orders can be written specifying the services required from the SOW to meet the needs of the requestor. Task orders would be CPAF except for the preplanning requirements and the backfill shop requirements.

It is necessary for the government to shoulder the burden of risk of the contract due to the many unknowns that may occur in each contingency. The LOGCAP deployment to Bosnia is an excellent example of the government shouldering the burden of risk. Various campsites were built on soil requiring more preparation than anticipated because of the harsh and wet Bosnian winter. The contractor competed with the military for local sources of supply, especially for geo-textile and gravel, which drove material prices up and required the contractor to ship or airfreight material from the United States. Also, the shortage of available trucking and rail service into the theater further compounded the problem of bringing supplies to the AOR.

Contract type for the JCAP contract would remain cost-plus award-fee except for the firm fixed-price line items for planning efforts and backfill shop support. CPAF is appropriate per FAR 16.405-2(b) because "(1) It is neither feasible nor effective to devise predetermined objective incentive targets applicable to cost, technical performance or schedule; (2) the likelihood of meeting acquisition objectives will be enhanced by using a contract that effectively motivates the contractor toward exceptional performance and provides the Government with the flexibility to evaluate both actual performance and the conditions under which it was achieved; and (3) any additional administrative effort and cost required to monitor and evaluate performance are justified by the expected benefits." (33) Furthermore, the contract must be able to meet the principles of logistics from JP 4-0. The CPAF-type task order is especially supportive of two of the principles: responsiveness and economy. JP 4-0 defines responsiveness as "the right support in the right place at the right time. Among the logistic principles, it is the keystone; all else becomes irrelevant if the logistic system cannot support the concept of operations of the supported commander." JP 4-0 defines economy as "the provision of support at the least cost." (34) The selection of CPAF makes perfect sense to reward the contractor for achievement of these principles.

Guidelines for Use

Contingency need, as opposed to contractor capability, should be the deciding factor for contract employment. The Air Force intends to use its organic forces for initial response to any contingency and then use civil augmentation as a replacement for these forces. The Air Force allows the MAJCOM responsible for providing support to decide whether or not to use the AFCAP contract. If the MAJCOM decides to use AFCAP, the contractor typically has 30 days to respond. The Army has established decision criteria to determine when to use LOGCAP, based on LOGCAP being used as a last resort. Therefore, if military capability and host-nation support are bypassed, the Army needs the contract to provide the in-scope support requested. "Army practice has been to make the force self-sustaining for the first 30 days in a contingency theater with the troops living under field conditions." (35) These troops depend on contingency contracting officers for initial entry support. For JCAP employment, the standard for full-up response should be 30 days from deployment of the first forces. The contractor should be notified of any required work at the onset of a military deployment. Until joint doctrine is developed, the services should retain decision authority on whether or not to use the contract. The Air Force, however, needs to follow the Army's lead and develop decision criteria for when to use a civil augmentation contract.

The JCAP contract must be employable in hostile environments to meet Army needs. Restricting contractor operations to military operations other than war (MOOTW) runs the risk of restricting contract use only to humanitarian and disaster relief operations. LOGCAP operations in Bosnia, Somalia, and Haiti have proven MOOTW can be as dangerous as war for the contractor. Instead of limiting contractor operations to nonhostile environments, the contractor and its employees must be provided a secure working environment. This can be accomplished by carefully locating contractor operations to minimize risk and by using military forces to protect the contractor. Army Regulation 700-137, Logistics Civil Augmentation Program (LOGCAP), specifies that each contract should set operational boundaries for contractor personnel. "Normally, contractor personnel will not be used forward of the brigade support area." (36) Thus, deliberate planning should task military forces to provide contractor security in a hostile environment. Security provided by military forces should be a special provision in the contract. Contractor personnel should be deployed during wartime contingencies only after the area in which they will be working has been secured.

When the decision is made to use JCAP, it is essential that a team familiar with the contract deploy. The team is necessary to provide the JTF staff and base commanders an understanding of JCAP's capabilities and how best to integrate JCAP into the force structure. This team should consist of a program manager, contracting officer, engineering technical representative, and a contract administration representative from DCMD-I. The interface and training provided by this team would augment the peacetime coordination that occurs on a regular basis with the CINC's logistics staff. The team should also insist on the creation of a JCMEB, JFUB, and CLPSB, as explained in JP 4-0, to prevent duplication of effort and requirements.


Proper training of personnel is essential for JCAP success. Engineering technical re p resentatives, administrative contracting officers, and quality assurance evaluators need to be trained before deployment since their first experience with the contract will likely be during an actual deployment. Defense Contract Management Command (DCMC), in support of its CCAS deployment teams, has developed an excellent three-phase program to pre p a re its members for deployment. The training provides CCAS teams, composed of military and DOD civilian members, essential skills for general mission readiness, specific mission information, and identified AOR training. Just prior to deployment, DCMC provides the team with the most current mission-specific information and conducts a final deployment review. (37) Additionally, it also would be beneficial if the requesting customers in the AOR were also trained before contract initiation. For such prolonged operations as Bosnia, rotating personnel should receive the training prior to deployment.
COPYRIGHT 1999 Air Force Research Institute
No portion of this article can be reproduced without the express written permission from the copyright holder.
Copyright 1999 Gale, Cengage Learning. All rights reserved.

Article Details
Printer friendly Cite/link Email Feedback
Title Annotation:p. i-19
Author:Dowling, Maria J.; Feck, Vincent J.
Publication:Wright Papers
Article Type:Report
Geographic Code:1USA
Date:Sep 1, 1999
Next Article:Feasibility of a joint engineering and logistics contract.

Terms of use | Privacy policy | Copyright © 2018 Farlex, Inc. | Feedback | For webmasters