News

 

CONTRACT AIRCRAFT REPAIR

LEAN LOGISTICS

A HANDBOOK FOR SYSTEM PROGRAM OFFICES

IN CONTRACTING

PROGRAMMED DEPOT MAINTENANCE

Shifting Roles and Responsibilities between the Government and Industry

 

 

 

 

Prepared for Warner Robins Air Logistics Center

Robins Air Force Base Georgia

 

 

 

 

 

October 1996

Contract Aircraft Repair (CAR) Lean Logistics Study:

A Handbook

 

Table Of Contents

Executive Summary 4

Chapter 1. Background 12

CAR Focus 14

Project Purpose/Goal 16

CAR Lean Logistics Team 17

Methodology (Overview) 17

The Process Stakeholders and Their Objectives 19

Chapter 2. Initiatives 21

Workloading 22

Scheduling 29

Material Support 36

Over & Above Process 42

Engineering Support 50

Organizing for Success 55

Incentives for Contractors 61

Metrics 64

Chapter 3 Lessons Learned from C-130 PDM Contract 68

Chapter 4. Project Summary 72

Summary 73

Cost Benefit Analysis 75

 

Appendix A—Depot Level Maintenance 77

A-1. Policy Extract of Depot Level Maintenance and Repair 77

A-2. Description of PDM 79

A-3. Depot Maintenance Business Area (DMBA) 81

A-4. Unscheduled Depot Level Maintenance (UDLM) 85

A-5. C-130 Aircraft Outyear Projected PDM Requirements 87

Appendix B--Study Methodology 88

Appendix C--IDEF0 Model 91

Appendix D--IDEF3 Processes Model 95

Appendix E--Contractor Perspective 104

E-1. Contractor Symposium 104

E-2. Site Visit 111

Appendix F--ALC Perspective 113

Appendix G--Customer Perspective -- Customer Symposium 118

Appendix H--Commercial Comparison -- FedEx Site Visit 121

Appendix I—Shop Service Center 125

Appendix J—C-130 PDM Contract Lessons Learned Comments 127

J-1. Statement of Objectives 127

J-2. Section L 129

J-3. Section M 142

J-4. Minimum Mandatory Requirements 149

J-5. Baseline Requirements 153

J-6. Section F and H Clauses 155

J-7. Section B Clauses 163

J-8. Pricing Proposal Format 169

J-9. Appendix B 182

Appendix K--CAR Core Team Biographies 194

Appendix L—References 197

Appendix M—Acronyms 198

Appendix N—Distribution 203

EXECUTIVE SUMMARY

 

In late 1995, the Warner Robins Air Logistics Center (WR-ALC) Commander established 6 center level Lean Logistics teams to develop plans for product directorates use in changing the way key products and services are provided to customers. One of the teams was tasked to focus on the contract aircraft repair (CAR) process. Simply put, the CAR team was challenged to develop initiatives and ideas that WR-ALC aircraft "companies" and support agencies could use in preparing, administering and supporting aircraft repair contracts that could result in reducing throughput (flow days) by 50%, reducing cost by 30% and improving customer satisfaction by 20%.

A cross-functional team was formed with representatives from the major ALC aircraft System Program Offices (SPOs) and support agencies, the Defense Logistics Agency, the Defense Contract Management Command, contractors and customers. Two contractors (Intergraph Corporation and Modern Technologies Corporation) assisted with the study. This document is a result of the team's research and effort and provides recommended initiatives/actions SPO program managers should consider when contracting, administering and supporting contract aircraft repair. If implemented and institutionalized, the CAR team has high confidence all three goals will be met--and in some cases exceeded.

The CAR team found that there were no quick or easy solutions in making contract aircraft repair cost and time more effective. There were no "silver bullets" that will transform it into a model of efficiency. Rather, the team found that the contract aircraft repair process needs a re-emphasis of basic economic and management principles.

The CAR team focused on one sub-process of the entire contracting process--aircraft repair contract execution. A closer examination of this sub-process led to the determination that five areas contain the most potential for achieving the project goals: (1) workloading, (2) scheduling, (3) material support, (4) over and above support, and (5) organizing for success. There were several other areas that were also studied that resulted in team recommendations. This report suggests ways in which improvements can be applied to these areas.

 

Although the government determines what work is to be done and when, it is not, however, free to mandate how contractors perform that work. In fact, the government is specifically limited in its involvement in contractor processes by the Federal Acquisition Regulation (FAR). This being the case, any initiatives put forth in this report addressed how the government should influence how the contractor accomplishes its activities and performance without specifying and requiring specifics in the contract.

Because of the necessity to "stay out of the contractor box", the team’s initiatives are intended to address the things that are external to the contractor but controlled by the government--the inputs, constraints and mechanisms of the process. The focus areas mentioned earlier--workloading, scheduling, material, over and above, organizing for success, plus others--are areas where government changes can influence contractor output.

In studying the CAR process, the team found some key concepts or "truisms" that applied to the contract aircraft repair process:

Any cost to the contractor becomes a cost to the customer.

The ability to achieve production efficiency is directly related to production quantity.

Effective contract execution requires effective planning; planning requires early and complete knowledge of what is to be done.

Contractors will not improve performance unless doing so has a clear, significant impact on their bottom line.

All the factors of production (facilities, material, labor, equipment, and technical data) must come together--synchronization.

The following sections highlight each of the CAR team’s major study areas and initiatives/recommendations in changing the way the contract aircraft repair process is contracted, administered and supported.

 

Workloading

 

The team found that the most significant area impacting PDM contract aircraft repair cost and flowdays was a steady and sufficient amount of workload. A relationship between the number of aircraft worked and production cost follows a curve like the one shown above. Repetition allows workers to become better at their jobs and encourages specialization. As operators move down the learning curve, efficiency and quality gains are realized.

On the negative side, a lack of sufficient workload can increase flowdays and impact cost significantly. Unless workload is steady, some expensive skilled mechanics have reason to "stretch" work out to remain employed in lean times. They wind up sweeping hangar floors until more work arrives. All of these conditions are anticipated when contractors develop bids.

It is important to remember that the goal of this study was not to give all the government workload to the contractor. Overloading a contractor with work has the negative effect of increasing flowdays as requirements outpace resources. There is, however, an optimal range that efficiently utilizes the contractor’s resources and will produce savings. Determining that optimal range and then contracting quantities within it, is crucial in meeting the reduction goals.

 

Scheduling

 

Scheduling is a basic function of any production effort. Clearly, in performing contract aircraft repair, the development and execution of a schedule for aircraft going in and out of a contract facility has a major impact on the contractor's ability to satisfy the contract and for the customer to receive the services/products when promised. Failing to schedule aircraft with production needs in mind sets up the cycle shown below. Customers have missions to fly, and often cannot input an aircraft into PDM until a replacement is completed. Uncertainty of aircraft input for PDM prevents contractors from delivering aircraft to the output schedule as well. Unlike workloading, which determines the number of aircraft to be worked and manpower allocation, the schedule determines when the work is to be accomplished. Knowing and being able to predict when a production effort is to commence is a major and critical step in resource planning.

An equally important factor that greatly impacts production is unchanging or stable workload. An input schedule that allows the contractor to "normalize" operations at steady manpower and facility utilization levels goes a long way toward delivering aircraft on promised due dates.

Material Support

Failure to put emphasis on material support will undermine the best efforts to properly workload and schedule aircraft repair. The CAR team discovered that unless it is known what parts are needed and aggressive actions to have the parts in place, delays are going to occur. The CAR team used many of the concepts coming out of the WR-ALC Lean Logistics organic aircraft repair team study in its recommendations. Foremost among those is the need for the development of an accurate bill of materials for each weapon system and a call for overhaul of the parts requisitioning system. Also, because aircraft repair contracts historically use Government Furnished Material (GFE), incentives need to be exerted to make the contractor more accountable for parts and shift the risk for schedule to the contractor. There will always be times when an unanticipated part need--a "stumble-on"--occurs. When this happens, it is imperative the government supply system, that contractors rely on for material support, is efficient and responsive. Creating and deploying a Shop Support Center (SSC), similar to those being established in the organic repair functions, addresses this need. Simply put, the SSC is a support team that includes the expertise and authority to handle many contractor issues--the greatest one being material.

Over And Above

Not surprisingly, despite all the best planning, unexpected inspection and repair work occurs on every aircraft. Consequently, aircraft repair contracts employ the use of over and above clauses to handle this work. This study identifies concrete recommendations for expediting these efforts to reduce the impact on schedule and cost. The CAR team member from Defense Contract Management Command (DCMC) played a crucial and major role in addressing this area. The CAR team found that a lot of historical information concerning PDM has been compiled over the years--and it's not only available at the ALCs. A wealth of knowledge can be gleaned from this data--knowledge that can help the government work smarter in the area of over and above support. The application of statistics to this information can help, for instance, in predicting an expected over and above allowance for a weapon system. Historical data, from both the ALC and DCMC databases sources, can better tell which items should have standards developed, and what those standards should be. Applying this information in the early stages of contract formulation, intelligent partnering with contractors, and allowing DCMC the opportunity to provide the total oversight streamlines the over and above process for both the government and contractor--resulting in faster throughput and at a reduced cost.

DCMC is the government representative at the contractor’s facility. The CAR team, as well as a joint AFMC and DCMC team, found this valuable resource is often under-utilized, as the ALCs historically retain control and management oversight over many support functions from a remote location. Utilizing the DCMC asset to its fullest potential would have a significant positive impact on contract PDM production and reduces redundant government resources.

ORGANIZING FOR SUCCESS

One of the areas the team found needing change concerned the organizational structure of the Air Logistics Centers. This became apparent during a visit to a private company that contracted its aircraft heavy maintenance. The team found a clean organization that focused solely on maintenance actions--both organic and contractual. In the contracting portion of the organizational structure, the perspective was not solely procurement actions, but focused on total program management--especially as it related to partnering with contractors and getting the most benefits for both--a WIN-WIN situation! Based on DOD guidance and current events, the team sees contract aircraft repair activities increasing in the DOD as downsizing, privatizing, outsourcing and budgetary crunches become worse--not better. The CAR team also found that aircraft repair, in itself, was a service that delivered a specific product to a customer. In itself, aircraft repair did not appear to fall into the Integrated Weapon System Management (IWSM) preview of having to have, under a single weapon system manager, a production function. Instead, the CAR team concluded that aircraft PDM inspection and repair was just another service (an extremely big and costly one) that customers expected ALCs to provide them. Generally, from the customer perspective, it did not matter to them whether their PDM work was accomplished organically or by contract--just so long as it was done in a predictable and effective method.

The scope of aircraft repair is large and is somewhat a discipline in itself. Division of this function into weapon system unique organization is somewhat inefficient, has duplication of effort and fragments support. Contract aircraft repair actions accomplish the identical work of organic maintenance functional--just not under the day-to-day management of the government. It is in this area that the CAR team felt realignment of responsibilities by organizational changes could be made. Doing so would result in more efficient, effective and institutional changes that allow, across the ALC and other support agencies, significant improvements in the throughput, cost and customer satisfaction of aircraft undergoing PDM inspections and repair--at both the organic and contract activities. One possible organizational change the CAR team considered revolved around removing the production activities from the individual SPOs and aligning them under a single function responsible for depot level aircraft repair. (Of particular note is that the CAR team did not advocate eliminating or transferring the single weapon system manager’s responsibility of satisfying the customers need for aircraft repair--the SPO still retains the single manager responsibilities and is the single "face to the customer"). The CAR team looked at a possible change using the concept that would have the SPO "hire" an aircraft repair function to repair the customer's aircraft--determining the WHAT AND WHEN. The aircraft repair function would determine the WHERE and HOW.

Although the CAR team did not recommend a specific organization to support the CAR initiatives, the team does recommend that another team be formed. The purpose of the team would be to study the need for organizational change and if warranted, recommend an organization that would better support the CAR process.

The results of the CAR team’s study provides 30 plus specific recommendations for improving the CAR process. The major ones being: (1) provide a economic workload to the contractor, (2) develop and follow an input schedule, (3) overhaul the government parts requisitioning system, (4) create and operate a Shop Service Center to support the contractor, (5) turn over more responsibility to DCMC, and (6) form another team to study and if warranted recommend organizational changes at the ALC to support the CAR process. Most of the recommendations mean minor changes in philosophy or direction at the SPO level in applying smart decisions to the CAR process; however, some recommendations require changing the very way the government approaches the business of aircraft repair--THINKING OUT OF THE BOX! Those recommendations needing center level or MAJCOM approval can best be processed first at the SPO level by requesting the support agencies/functions obtain the policy/guidance changes necessary to implement these recommendations.

 

CHAPTER 1

Background

 

LEAN LOGISTICS BACKGROUND

In late 1995, the Warner Robins Air Logistics Center (WR-ALC) Commander established 6 center level Lean Logistics "Chain" teams, in concert with 8 Lean Logistics "Link" teams, to develop implementation plans for changing the way the center provided core services and products to the war-fighters--the CUSTOMER!

 

The task of each team was to use the umbrella principles of LEAN LOGISTICS and the specific initiatives and concepts of reengineering, acquisition reform, 2-level maintenance, just-in-time inventories, intelligent partnerships, integrated product teams, and all the other smart business practices available to the teams. The basics of Lean Logistics are defined below:

COMMERCIAL PRACTICES VERSUS GOVERNMENT PRACTICES

The CAR team recognized that government and commercial contracting practices differ in several fundamental ways. Commercial procurement actions attempt to obtain best value for the company to maximize profit. Government actions, however, are geared, by public law, to:

The government’s goals are more complex than those of the commercial sector, but the government can consider, at least in parts, many of the commercial acquisition practices. Some that the CAR team felt may be considered in contracting for aircraft repair services are:

 

This study addresses many of these practices. Use of these practices to the maximum extent possible under the Federal Acquisition Regulations (FAR), DOD guidance and good business practices during the procurement process of contracting aircraft repair, coupled with the other initiatives in this report, can and will result in providing to the user faster, cheaper and higher quality aircraft.

 

CAR FOCUS – CONTRACT PROGRAMMED DEPOT MAINTENANCE

Air Force weapon systems are routinely scheduled for Programmed Depot Maintenance (PDM) at predetermined intervals to accomplish the heavy maintenance and inspections. Appendix A--Description of PDM--contains an overview of how the PDM process takes place. The majority of PDM work is accomplished "in-house" or organically, yet the trend is to contract more of this type work in the private sector. Although there is more aircraft repair work that is contracted (i.e., unscheduled depot-level maintenance, modifications, time compliance technical order, etc.), the CAR team focused primarily on those areas relating to contracting of aircraft PDM.

 

Even though the CAR team did not study CORE issues, it is important background to consider. As the DOD solidifies the definition of CORE depot maintenance capabilities to meet essential wartime demands, promote competition and sustain institutional expertise, the considerations to contract workload will adjust as necessary. The recently published Policy Regarding Performance of Depot-Level Maintenance and Repair, March 1996, by the Office of the Secretary of Defense is must reading for ALC managers as they consider workload factors--now and the future.

 

 

 

 

STUDY PURPOSE/GOALS

The purpose of the CAR Lean Logistics study was to examine the aspects of the CAR process in which government participation can be used to enhance the overall CAR performance, and to recommend any appropriate process modifications.

Simply put, the charter the team was given was to develop ideas/initiatives that system program offices could use in preparing, administering and supporting contract aircraft repair actions that would result in substantial improvements in throughput (flowtime), cost and customer satisfaction.

 

CAR CHARTER

DEVELOP IDEAS AND INITIATIVES

WR-ALC AIRCRAFT COMPANIES (SPOs) CAN USE TO

REDUCE THROUGHPUT (BY 50%),

REDUCE COST (BY 30%), AND

IMPROVE CUSTOMER SATISFACTION (BY 20%)

IN THE CONTRACT AIRCRAFT REPAIR CAR PROCESS

(EMPHASIS ON PDM PROCESS)

 

 

CONTRACT AIRCRAFT REPAIR TEAM CHAMPION

The CAR Team was provided advice and assistance from the past and current C-130 System Program Directors and Deputy System Program Director (WR-ALC/LB):

Col Ben McCarter (past C-130 SPD)

Col Greg Siegel (Current C-130 SPD)

Mr. Mike Hatcher (GM-15) (Deputy C-130 SPD)

 

 

 

 

THE CAR LEAN LOGISTICS TEAM

The initial CAR team was formed in September 1995 and consisted of representatives from various Air Logistics Center support functions, WR-ALC aircraft single manager program offices, Defense Logistics Agency (DLA), Defense Contract Management Command (DCMC), contractors, and customers associated with contracting aircraft repair--especially as it related to programmed depot maintenance (PDM). Since there was an on-going effort to renew the C-130 weapon system PDM contract, a large majority of the team consisted of representatives from the C-130 System Program Office (SPO). The team composition changed throughout the study based on findings and new areas of study; however, a core number of people were members during the duration of the study. Individual members of the CAR Team are:

Name Organization Name Organization

* Tim Annis (Team Lead) WR-ALC/LBP Florine Crane WR-ALC/LBRA

* Ed Humphreys WR-ALC/LB (MTC) Jenny Thompson WR-ALC/LKSA

Denise Yawn WR-ALC/LBPLC Mike Earehart DCMC/PEMCO

Carolyn Green WR-ALC/RE/LL Bill Clark WR-ALC/LBRSD

Hugh Nelson WR-ALC/LBRA Chuck Gibson HQ AFRES/LGMA

Ed McDowell McDonnell Douglas Capt. Mike Nowaczyk WR-ALC/FML-1

Perry C. Doyle 78ABW/LGSP Wade Summer WR-ALC/FMLMC

Ralph Hill WR-ALC/FMLMC * Franklin Kee WR-ALC/LJK

Gerald Barron WR-ALC/LBPCA John McGraw 78ABW/LGSIC/LBP

Tammy Phelps WR-ALC/LBRS Annick Woodlock WR-ALC/PKPB

Margie Tyner WR-ALC/LBKA * Joel Murphy WR-ALC/LFPC

Maj. O.B. Mercer DLA/DDWG/E Lt. David Flynn WR-ALC/LB-PIT

Melvin Gillis 78ABW/LGTPL Mike Bishop DCMDE-AOB

Glenna Abney 78ABW/LGTPM Jim Harper WR-ALC/LBRA

Cheryl Maddux DCMDE-AT * Jimmy Rogers WR-ALC/FMLMC

* John McDonald WR-ALC/LBRA Roy Abbot WR-ALC/RE/LL

* Ron Harlow Intergraph * Mike Denson Intergraph

Carol Thomas WR-ALC/LU

* Core Member (Core Team biographies are at Appendix K)

METHODOLOGY (OVERVIEW)

As part of the CAR study, information about the current processes was gathered through team modeling meetings, interviews, symposiums, site visits and surveys.

Intergraph Corporation used the following software tools to model and simulate portions of the CAR "As-Is" process:

Deliverable Software Tool Vendor

IDEF0 Model AI0Win KBSI

IDEF3 Model Prosim KBSI

Simulation Witness AT&T Istel

DOCUMENTING A PROCESS

Although the "As-Is" portion of the CAR study contains Integrated Definition model levels (IDEF) process models and computer process simulations, it is much more than that. There are several areas of consideration that have to be taken into account when documenting a process:

The Stakeholders And Their Objectives--most processes are shared by several groups of people, and each group is a stakeholder in that process. It is important to understand who those stakeholders are as well as their interests (or objectives) in the process. The importance and relevance of any portion of the process are different from stakeholder to stakeholder, and each perspective has to be considered.

The Process Steps--processes are composed of process steps, and each step is carried out by some individual, organization or machine at some location and consumes some amount of time and cost. Each process step should contribute in some way to the process itself, and can be characterized as value-added or non value-added. An IDEF model allows the definition and detailing of these steps in a graphical way.

The Process Technology--the mechanisms that are used to carry out a process are important. Many process steps can be automated by taking advantage of current technology in ways that vastly improve the overall process performance.

The Motivational Elements Of The Process--processes themselves are not always to blame for poor process performance, as many processes are not used, misused and abused. More often than not, process steps are performed by people, and the efficiency and effectiveness with which those process steps are executed depend greatly on the individuals involved. There is more to be gained in overall process performance by providing motivation for performance than by changing and even eliminating process steps.

To accomplish the study, the CAR team used the following meetings/symposiums in the fact finding portion of the effort.

Contractor Symposium (See Appendix E for details)--Representatives from twelve different contractor companies gathered to discuss with the CAR team the issues that impacted their performance.

Contractor Site Visit (See Appendix E for details)--The CAR team made a trip to a contractor’s facility to observe the operation first hand, and to discuss the areas being addressed by the team.

Process Modeling (See Appendix D for details)--IDEF process models were developed for three of the focus areas (over and above, parts, and engineering support) by interviewing functional experts in each area.

Customer Symposium (See Appendix G for details) -- Representatives from all of the customer groups met with the team to explain their concerns and priorities as related to CAR.

Commercial Comparison (See Appendix H for details)--The CAR team traveled to Memphis, Tennessee to meet with a representative of FedEx. FedEx contracts out its air fleet for maintenance much the same as the Air Force.

THE PROCESS STAKEHOLDERS AND THEIR OBJECTIVES

In order to fairly and accurately analyze the CAR process, it was necessary to understand and document the perspectives of each of the stakeholders. That information was gathered in the following ways:

THE CAR CONTRACTOR’S PERSPECTIVE

The contractors are businesses independent from the Air Force that provide PDM services to the Air Force for profit. Their role is to bid on work to be done and perform that work in compliance with the time frame and cost of a contract. The contractors are interested in:

THE CAR ALC PERSPECTIVE

The ALC is the Air Force agency that executes the PDM requirements for a given weapon system for the customer group as a whole. The PDM requirements and time window for completion for each weapon system tail number are agreed upon by the customers and the ALC. The ALC is responsible for contracting the work to be done in either organic (Air Force) facilities or contractor facilities. In addition to contracting, the ALC provides a large amount of the support for both organic and contract repair sites. This support includes material, equipment, engineering support, quality support and funding modifications. The ALC is interested in:

THE CAR CUSTOMER PERSPECTIVE

The customers own and fund the aircraft that are inspected and repaired by the PDM activities, which can be carried out by organic (Air Force) depots or contractor depots. For any weapon system, there are multiple customers such as the Air National Guard, Air Force Reserve, Air Combat Command, etc. The role of the customer in this process is to submit aircraft for PDM with as little impact as possible on operations and readiness. The customers are interested in:

With this as background, the next chapter takes a closer examination at the specific CAR team focus areas and the team’s recommendations for improving the CAR process.

Chapter 2

INITIATIVES

This portion of the study focuses on the CAR processes that the CAR team found needed improvement. It outlines the recommended changes to the government controlled conditions, that when implemented, positively alter the contractor’s operations.

The basic premise of the CAR study is that the government, primarily the ALC, cannot, by itself, impose or dictate improvements in the contractor's performance--instead, contractors must be incentivized to improve their own performance. In incentivizing the contractor, the ALC can indirectly influence the contractor's performance by establishing positive conditions for contract aircraft repair:

  1. Develop and maintain a "PARTNERSHIP" relationship between the contractor and the government. (A WIN-WIN situation for both).
  2. Create an environment and infrastructure which will support the contractor performance at the desired performance levels.
  3. Motivate and incentivize the contractor to achieve these performance levels.

The CAR team felt that when these conditions are met, contractors will perform up to the goals set forth in this report. This is not wishful thinking, nor is it a hap-hazard guess. During the course of this CAR investigation, the team saw substantial evidence to support this claim. Other organizations that contract aircraft repair --both in and out of the Air Force--experienced performance levels that met or exceeded the goals stated in this study.

In presenting the following CAR team initiatives, the Chapter 2 format was standardized for continuity. The individual initiative discussions start with a general background of the particular area, followed by a short impact summarization on the PDM process. The specific CAR team recommendations are then presented. The individual initiative area is concluded with examples of metrics or measurement tools that SPOs or managers could use in tracking implementation success.


WORKLOADING INITIATIVE

 

DISCUSSION/BACKGROUND

From the CAR Team’s perspective, providing the contractor a sufficient amount of workload at a steady rate is the most important area that needs to be considered and implemented when contracting aircraft repair--especially programmed depot maintenance. Pre-determining the amount of workload a contractor can efficiently and effectively accomplish, coupled with a firm input/output schedule (discussed in a following section), will ensure achievement of the majority of the expected flowdays and cost savings with the increased customer satisfaction goals detailed in this report.

Workloading refers to the amount of work being submitted for contract aircraft repair. In addition to the number of aircraft input to a contractor’s facility, workloading also defines the type of work to be done on those aircraft. PDM work makes up the majority of work, but other types of work such as modifications, Time Compliance Technical Orders (TCTO), Unscheduled Depot Level Maintenance (UDLM) and Organizational & Intermediate (O&I) level maintenance have significant impact on workload.

At the contractors symposium (see Appendix E-1), contractors told the CAR team that they needed to maintain a stable work force and support core teams if they are to be able to reduce flowdays. The team verified this statement as being valid by thorough research at organic government facilities and other commercial activities. Reducing flowdays provided contractors the opportunity to apply better business practices and reduce operating/overhead expenses which in turn means they will be able to pass the savings on to the government in their bids.

The CAR team found that in today’s CAR process, the priority in assigning workload is to fill--and even overfill--organic facilities first, and send the remainder out on contract. In some cases, this remainder is not enough to allow the contractor to be efficient in the contract execution. In addition, some contracts contain large bid ranges that are designed to give the government maximum flexibility. While this does provide flexibility to the ALC, it also drives up the contractor’s cost because of the impact this uncertainty has on material levels, manloading and facility availability. In short, the ALC is purchasing a high capacity and utilizing only a portion of that capacity. Yet this does allow the government to surge if the need arises.

There is a direct relationship between the amount of work done at a facility and the efficiency, cost and quality of that work. Numerous skills (aircraft mechanic, sheet metal mechanic, electrician, etc.) are needed to accomplish the different work operations in the PDM package. These skills are used throughout the aircraft repair process and are moved to different operations as workload demands. However, there will be some skills that cannot be fully employed and will be idle if there are too few aircraft on station to work. When this constraint is not alleviated, the inefficiencies result in idle time and higher cost to the customer. Government decisions to contract too few aircraft or to provide erratic inputs directly impact the contractor's ability to perform efficiently and cost effectively.

The Cost Of Unlevel Workloading

Contractors, like any other commercial business, are most productive and efficient when the input workload level matches the workforce capacity. In reality though, workload is seldom (if ever) level--even though level workload is the most desirable situation. A fluctuation in workload causes cost and schedule overruns. The production organization, in this case a government contractor for aircraft repair, typically operates in one of four modes depicted in the below chart:

 

Capacity Operation--this is the fine line where the amount of work to be done on an ideal schedule matches the man-hours available. This situation is ideal for the contractor, but is not always possible--and almost never happens for a significant length of time. The flexibility of the contractor determines how far above or below the regular hour capacity line that operations can work efficiently.

Overtime Production--This occurs when the man-hour demands for a period of time exceed the regular-hour man-hour availability for that same period, but can be met with overtime work. This causes a cost increase.

Demand Beyond Capacity--when man-hour demand rises above even the overtime capacity, there is no other means to increase production. The result of operation in this mode is increased flow days and cost.

Idle Workforce--The skilled workforce employed by the contractor is not a temporary resource pool. Since that workforce cannot be fired and re-hired to match production cycle fluctuations, additional cost is incurred whenever the workload demand drops below the man-hours available. This extra cost is caused by workers remaining on the payroll without production return, and by deliberate cuts in work efficiency in an effort to remain billable--meaning increased flowdays and cost.

Basically, the chart above is depicting that there is a minimum number of aircraft inputs a contractor needs to efficiently and effectively utilize the numbers and skills of the workforce required to accomplish the work requirements of the PDM workload. Without this steady input of work, the dynamics of capacity negatively impact both flowdays and cost. In decreasing both, the contractor must have an efficient quantity and a steady workload.

Another factor in considering workload has to do with properly man-loading the work. Man-loading means applying manpower to the work. Significant flow day reductions can be achieved by fully man-loading the critical path jobs of the work--on multiple shifts. The contractor must know the critical path of the work and identify the manpower quantity and skills, with material, needed to meet the scheduled completion for all major jobs. All things being equal, if decreasing flowdays is the sole objective, this is an important event that needs to occur to reduce flowdays! Since the government does not have direct control or management responsibility over the contractor's workforce, the government must offer incentives to the contractor so the contractor will apply maximum manpower to the critical jobs on at least two shift operations. Doing so will result in reduced flow days. Conversely, spreading the same manpower on a single shift, over multiple aircraft, results in inadequately manloaded aircraft that produces increased flow days and cost. The team found that FedEX Corporation wanted their aircraft down for a minimum amount of time and thus they required 24 hour, 7 day a week contractor coverage on their aircraft. They did this via the contract vehicle.

In order for the contractor to do either of the above, they must have a clear understanding of what the workload is and what will be expected of them. Unknown and undefined work requirements drastically affect contract cost and schedule. Providing the contractor sufficient lead time for developing standardized repair procedures, material requirements and provisioning has a major impact on the contractor reducing cost and schedule impacts to the contract. Another consideration the CAR team looked at was to assess the condition of the scheduled PDM aircraft before it arrived at the contractors facility. Doing so would reduce the uncertainty or unknown work by allowing the contractor to plan and lay in necessary parts to expedite repair actions. Adding Time Compliance Technical Orders ’s (TCTO’s), modifications and AFTO Forms series 781 and AFTO Form 103 discrepancies to a basic PDM work package generate most of the variable unplanned requirements. Although mission requirements may drive accomplishment of these requirements, there is a strong need for analysis of repetitive requirements to allow for the development of standard work packages.

An efficient number of aircraft, properly manloaded on the critical path jobs, will clearly positively impact schedule and cost performance. However, the single most important aspect of ensuring that proper workloading produces savings is having the right part on hand when it is needed. Since most of the parts and material currently provided the contractor are GFM, the government and contractor must have an in-place process that assures material is on-hand, when needed by the mechanic, to complete the job. The Material Support Initiative is discussed later in this report.

IMPACT

The benefits of having an economical number of aircraft are many: work repetition, retention of higher quality skilled workers, justification for multiple shifts and core teams, investment in equipment that reduces man-hours, and so forth. None of these ideal working conditions are possible with less than economical workloads. At the other extreme, too many aircraft create a situation where some constraint limits throughput--whether it be manpower, facilities, tooling, etc. In this case, the flowdays for all aircraft will go up because aircraft are waiting for some resource. With consistent scheduling/workloading, the contractor can retain a stable, trained, experienced work force capable of achieving reduced flow days, reduced cost and increased customer satisfaction.

 

 

RECOMMENDATIONS

  1. The SPO should determine if contracting should be done at all. The same principles of production efficiency that apply to contractors apply equally to organic facilities. If there are not enough aircraft in a fiscal year to support economic workloads for both organic and contract facilities--do not contract or expect higher contractor cost and increased flowdays.

  1. Once the decision is made to contract aircraft PDM and prior to determining the number to contract, the System Program Office benefiting from this effort should conduct an analysis to determine the minimum quantity of aircraft that constitutes a consistent workload to a contractor. This is the minimum number of aircraft that should be required in the contract. The number should be such that it allows a contractor to support a stable, trained and experienced work force. In determining this number of aircraft, the contracting SPO should also consider the amount of required work, the desired flowdays, and the maximum number of aircraft MAJCOMs would be willing to place in PDM status--at all facilities. This analysis should include an input/output schedule that supports the workload.

  1. Encourage the contractor to employ multiple shift man-loading. Significant flow day reduction can be achieved by fully man-loading the critical path jobs on multiple shifts. The contractor should apply maximum manpower to the critical jobs on at least two shifts to minimize repair flow days and the number of aircraft in plant. Conversely, spreading the same manpower over multiple, inadequately manloaded aircraft increases flow days. The major jobs not on the critical path must also be managed so they are completed prior to impacting the critical path jobs. These can be used to effectively balance the skill's mix needed to support the PDM tasks.

  1. Incentivize the contractor to develop a critical path for the PDM process that specifically identifies manpower and material requirements by major job. The contractor must then manage the PDM work flow and assign his work force by the critical path. This intensified manloading requires firm commitment from the contractor and from the government. The contractor must develop a critical path that identifies when skills and material are needed to meet the scheduled completion for all major jobs. Critical path jobs obviously impact schedule immediately; but, the other jobs will impact schedule also.
  2. Since most of the parts and material are GFM, the government and contractor must have in place a Shop Service Center, similar to that being created in the C-130 and C-141 SPO organic facilities that assures the material is provided when needed to complete the job
  3. Provide standard workload package vs variable ones. Unknown and undefined work requirements drastically affect contract cost and schedule. Sufficient lead time for developing standardized repair procedures, material requirements and provisioning will reduce cost and schedule impacts to the contract. TCTO’s, modifications and AFTO Form 781/103 write-ups generate most of the variable unplanned requirements. Although mission requirements may drive accomplishment of these requirements, analysis of the repetitive requirements will provide recommendations for development of standard work packages for future cost and schedule reductions.
  4. To allow for variances in outyear number of aircraft requiring PDM (see the example of C-130 PDM outyear projections at Appendix A) and unknown contingencies, the contracting SPOs Request For Proposal (RFP) should request pricing quotations from contractors for accomplishing work on an incremental range of aircraft numbers (For example, 10 to 20, 20 to 30, etc.). The RFP should provide a best economic quantity (BEQ) number for each range to allow for establishing evaluation criteria in selecting a contractor. Or an average of the unit price of each range could be used for the BEQ price. Additionally the government must provide, as early as possible, to the contractors, the range options the government will exercise with each option. The SPO should assign a probability of occurrence for each range to use in evaluating the various contractor proposals. This allows the government and the contractor to work together in a cooperative partnership as requirements change due to force reductions, new purchases, catastrophic events, etc. This also provides the government cost-benefit analysis data for use in deciding the final number of aircraft to contract.

 

 

WORKLOADING METRIC

There are two major metrics to consider in this area. The first is to chart the number of aircraft placed in the contractor facility compared to the computed economical number and at what rate they are placed in the facility. The second area is charting the scheduled amount of work against what is actually accomplished.


SCHEDULING INITIATIVE

BACKGROUND/DISCUSSION

Scheduling is the process by which aircraft are assigned arrival and departure dates at a contractor facility. It attempts to anticipate the flowdays of the aircraft in accordance with the individual work packages, and provide sufficient information prior to aircraft arrival for the contractor to plan work efficiently.

Scheduling is a basic function of any production effort. Clearly, in performing contract aircraft repair, the development and execution of a schedule for aircraft going into and out of a contract facility has a major impact on the contractor's ability to satisfy the contract and for the customer to receive the services/products when promised. Unlike workloading, which determine the number of aircraft to be worked and manpower allocation, the schedule determines when the work is be accomplished. Knowing and being able to predict when a production effort is to commence is a major and critical step in resource planning. And as the CAR team found, resource planning and proper execution are key factors in a contractor being able to satisfactorily perform the contract.

Currently, the PDM schedule for the contractor is driven basically by two things--the ability of the customer to deliver an aircraft for PDM and the workload needs of organic facilities. When an aircraft is projected to be available from the customer, the first decision made is whether or not it can be sent to an organic facility--even if that facility is fully loaded. If the decision is to not accept or perform the work organically, then "it goes to the contractor". Very little consideration appears to be given to the impact of receiving or not receiving an aircraft to the contractor or the timing of the input. In several cases the CAR team found that contractors often are not aware that an aircraft is arriving until it arrives, and the costs of the inability to plan materials and manpower become quite high.

Below is a specific example of a previous input schedule for aircraft into a contractor PDM facility .

PEMCO FY94 C-130 Arrival Intervals PEMCO FY95 C-130 Arrival Intervals

Aircraft Arrival Date Days between arrivals Aircraft Arrival Date Days between arrivals

1 Nov. 3, 1993 N/A 1 Oct 24, 1994 25

2 Dec. 20, 1993 47 2 Nov. 8, 1994 15

3 Jan. 6, 1994 37 3 Nov. 10, 1994 2

4 Feb. 8, 1994 33 4 Nov. 11, 1994 1

5 Feb. 24, 1994 16 5 Feb. 2, 1995 83

6 May 29, 1994 94 6 Feb. 7, 1995 5

7 June 10, 1994 12 7 Feb. 8, 1995 1

8 July 13, 1994 33 8 Apr. 18, 1995 69

9 Sept. 12, 1994 60 9 May 22, 1995 34

10 Sept. 30, 1994 18 10 July 13, 1995 51

11 Sept. 30, 1994 0 11 Sept. 25, 1995 73

12 Sept. 28, 1995 3

13 Oct. 5, 1995 7

 

In looking at this input schedule graphically (see below) we visually see the disruptive nature of an uneven input schedule, especially when compared to the workflow problems that are depicted in the Cost of Unlevel Workloading portion of this handbook.

Scheduling for contract aircraft repair is not only a contractor issue. The CAR team found that the government’s major focus and reporting/metric products for contract aircraft repair scheduling revolved around when an aircraft is scheduled out of the contractor's facility. And although no one would disagree that this is a primary measurement in depicting the contractor's ability to meet the contract, the government must consider the total schedule performance/execution before judging contractor performance--especially since government’s actions directly impact the contractor's ability to execute the schedule. This scheduling problem is amplified for some weapons systems based on a wide variance in the numbers of aircraft requiring PDM during a given year. Compounding this even further is the difficulty of developing a PDM schedule for weapon systems that have PDM accomplished at multiple facilities (organic and contract) (see C-130 outyear PDM projection chart at Appendix A-5).

 

IMPACT

During the CAR Contractor Symposium (see Appendix E), discussions with Federal Express Corporation (see Appendix H), and in the "As Is" process (see Appendix D), the CAR team found that improvements in workloading and scheduling were areas that had the most potential for changes that could result in reaching the goals for this effort.

As part of the CAR project, Intergraph Corporation developed or used a computer model to simulate, in a general sense, the process of PDM in a contractor facility. Naturally, the complexity of repairing aircraft cannot be easily captured in a computer model, if at all, however, it was used to illustrate to the CAR team the effect of variability in workload scheduling on manpower needs, which is not as complicated.

In this model, aircraft entering the PDM system were assigned some number of required labor hours between 12,000 and 16,000. In addition, these aircraft entered the PDM facility according to a pre-determined time schedule with built-in variance to that schedule. It was assumed that the available manpower at the facility was divided evenly across all aircraft at the facility. When the assigned labor hours for an aircraft had been accomplished, the aircraft left and the flow days were recorded. From a facility standpoint, the fluctuation in workload--caused by variability in the incoming schedule--resulted in either increased flowdays (requirements greater than resources) or idle manpower (resources greater than requirements).

The results of this simulation verified what the team expected--that the contractor's performance, in terms of cycle time and cost, are greatly impacted by variability in workload.

Scheduling plays a critical role in the production efficiency of the contract facility in several areas. First, the regularity of aircraft arrival impacts the manloading of the tasks to be done. When aircraft arrivals are too far apart, resources are greater than requirements. This results in skilled labor personnel being either temporarily laid off, put to work sweeping floors, or switched back and forth between different jobs such that the learning curve is never fully realized. When aircraft arrivals are too close together, requirements are greater than resources, which result in an increase in flow days. Material and manload planning are also very important. The way scheduling impacts planning is by providing the contractor with as many work package specifics for each tail number aircraft, as early as possible. Many parts have long lead times or are temporarily unavailable, and need attention long before the aircraft arrives. Assessing the aircraft scheduled for contract repair before it arrives can mitigate some of the unknown and result in better planning.

In the CAR Customer Symposium (Appendix E-1), customers (war-fighters) were asked if they would commit to a firm input PDM schedule if it meant a more reliable and predictable output date for their aircraft. The customers indicated they would agree to a more rigid schedule. However, they did caveat their commitment by indicating input dates are normally driven by the output dates of aircraft currently in PDM. This was especially important to those customers who have small numbers of aircraft assigned to various locations and are unable to operationally have more than one aircraft in PDM at any particular time. It was also discussed that since PDM are accomplished at both organic and contractor facilities, sometimes inputs are delayed at one facility due to an output date slippage at another. It was interesting to note that during this discussion, the customers looked to the Air Logistics Center to develop the PDM schedule based on the capabilities of the organic and contractor facilities and the known numbers and dates PDM were due. They implied they would follow the ALC developed schedule.

Breaking the "failure to meet schedule" cycle

Introducing variations and unknowns into the schedule sets up a cycle where unpredictable PDM input results in unpredictable PDM output. On the other side of a coin, the customer cannot input an aircraft until he knows when a replacement will return from PDM, so the unpredictable PDM output results in unpredictable PDM input.

In order for the contractor to output an aircraft at a predicted time (which is the customers Number # 1 objective) at a reduced cost that meets customer expectations, the contractor must have a firm input schedule. This schedule must be properly executed and with sufficient advanced notice of known workload. Without the government providing the contractor these basic production principles, there can be little expectation from the government that the contractor will be able to meet an output schedule, at a cost or quality product that will be acceptable to the government.

In the workloading section, the CAR team recommended that the government commit to the contractor an optimum or economical number of aircraft to work. This allows the contractor to reach proficient and economical goals that in turn can result in reduced flow days and cost and increased customer satisfaction. To obtain these "rewards," the government must work in concert with the contractor in providing the aircraft on a schedule that allows the contractor to reach and maximize efficiencies

In addition to scheduling an economical number of aircraft into a contractor's facility based on an even and predetermined flow, the team found that contractors needed known, specific aircraft tail number work that could be scheduled into their basic workflow. This work should be known well before the aircraft arrives at their facilities. This workload should include variable work that is associated with each specific aircraft undergoing programmed depot level maintenance. Examples of this variable work would be field level maintenance request (AFTO Form 103 and AFTO Form 781A), modifications and Time Compliance Technical Orders (TCTO). From the contractor perspective, the earlier this information is provided to them, the better they can plan and prepare for the work. Having this information in advance of the aircraft arriving at the contractor facility allows the contractor to lay in the needed materials, ensure the appropriate number of trained, skilled manpower are available and to "blend" in the additive work to the basic PDM workflow package.

RECOMMENDATIONS

  1. The SPO PDM Program Manager should conduct annual PDM outyear schedule conferences (at least 6 months in advance of the last scheduled aircraft schedule review) with all the "players"--customers, DCMC, contractor(s) and organic maintenance division(s).
  2. The contracting SPO should publish an annual schedule for all aircraft and all PDM facilities (organic and contractor). The team suggest making the PDM schedule an Memorandum Of Agreement (MOA) signed by all parties.
  3. The SPO should "evolve" the annual PDM schedule, each month by replacing the last month with a new month--making it a "living" schedule. This should be the control schedule--measure how well the schedule is met by all parties!
  4. The SPO should develop an implementation process or system that provides contractors and customers access to the scheduling program/data. One quick way to provide interim visibility to the PDM schedule is to place the schedule on the Internet. This should also be well addressed in any Request For Proposal (RFP).
  5. The SPO PDM Program Manager and each weapon system customer should develop an MOA that commits the customer to identify and if necessary input an "alternate" aircraft (in an agreed upon time) into the contractors PDM facility. This would occur when the "primary" aircraft is unable, due to operational or mechanical reasons, to be placed in the contractor PDM facility at the scheduled date. The purpose of using this basic scheduling principle is to preclude any disruption of the contractors PDM workflow.
  6. The SPO PDM Program Manager should provide the contractor all known work for specific tail number aircraft at least six months in advance (modifications, TCTOs, AFTO Form 103 with the AFTO Form 781 series discrepancies). In order to accomplish this, the customer must provide the ALC a list of requested/approved/funded customer work (AFTO Forms 103) at least seven months in advance of the PDM scheduled input date and be willing to limit the work requested (within operational limitations) to this list. The customer would update this list 60 days prior to the scheduled input date. (Note: Only Safety of Flight AFTO Form 781A discrepancies should be added to the work package after this update.)
  7. The SPO, the contractor, and customer should establish an agreement whereas the contractor could perform field visits to pre-inspect specific tail number aircraft scheduled for PDM. The purpose being to pre-plan unusual or difficult work to be accomplished during the contractor PDM.

SCHEDULING METRICS

The basic metric for this initiative is scheduling effectiveness. The measurement should consist of how well the customer meets the input "living" schedule and how well the contractor meets the "living" output schedule. The example below is a format with notional data that could be used for each schedule.

MATERIAL SUPPORT INITIATIVE

 

DISCUSSION/BACKGROUND

Material support is the process by which government furnished material (GFM) is anticipated, requisitioned, and delivered to contractors. The CAR team, as well as several other study teams/efforts, came to the same conclusion: there is only one way to describe the government material support system today--broken! For example, in many cases, once a part is requested by a contractor it takes as many as five days just find out the status of a needed part in the government system; much more time is required to actually receive the part. The Bill Of Material (BOM) for the PDM aircraft is notoriously inaccurate, which produces an additional load on the part's acquisition system, further slowing the system.

The CAR team looked at how the AF requires contractors to obtain parts on aircraft repair contracts. Parts can be divided into three categories, contractor furnished material (CFM), government furnished material (GFM) and contractor acquired property (CAP). CFM as the name implies are those parts and materials the contractor furnishes as he performs the maintenance. The cost for these materials are recouped through his bid price. These materials are primarily indirect materials or in other words, materials that do not remain on the aircraft. Some examples would be rags, sanding discs for corrosion removal, masking tape during paint and stripping operations and so forth. The team found that it is very rare for indirect parts to cause delays in aircraft repair flowdays.

GFM is material requisitioned by the contractor from the government and is provided at no cost to the contractor. These parts are usually classified as direct parts, or in other words, parts that remain on the aircraft. Some examples of GFM would be fasteners, structural parts, paint, and avionics equipment. These parts are requisitioned by the contractor through the D034 system and tracked at the contractor’s facilities through the G009 system. Typically, these parts are responsible for most of the delays in PDM aircraft.

The last category of parts is CAP. CAP is a term used to denote those parts that the government would normally furnish as GFM but is unable to do so in a timely manner (these are non-RSD items). After requisitioning the part and receiving an unacceptable due-in date, the contractor is authorized to purchase these parts on his own and is reimbursed on a cost plus administrative fee basis. This is usually spelled out in detail in the appropriate contract vehicle.

Currently most of the risk for providing parts rests with the government. Ideally, the government should shift the risk for supplying parts to the contractor. When asked at the contractor symposium about complete CFM contracts or increasing the amount of CFM, contractors expressed reluctance to sign up to such an effort. They are more comfortable with the government assuming the majority of the risk

Some of their reasons are not without merit. For instance, many of the parts that are required for PDM inspections/repair are only available from the government since some sole source suppliers will only sell to the government. Also, because the government is buying many of these parts on a recurring basis to support every day requirements, it is difficult for contractors, needing small quantities, to match the discounts the government receives for large quantity buys. Consequently, it currently makes sense to have some level of GFM--but this should be less and less as the government becomes "leaner". However, conscience decision should be made, depending on the weapon system and the capability of the contractor, on what that level should be.

Many of the contractors expressed dissatisfaction with the untimely support of GFM. After a requisition is requested from the government by the contractor, a significant amount of time elapses (as much as 3-5 days) before they are provided a status. Consequently, if the part is not available or has an unacceptable estimated delivery date (EDD), valuable time was lost which the contractor could have used to develop an alternative strategy for obtaining or repairing the needed part (i.e., CAP or cannibalization). When work stoppage parts are required, delays translate directly into increased flow days. Because of the importance of knowing the status of a part requirement, the CAR team felt that it would make sense for the contractor to share or have access to the government material system.

Direct information links with government legacy systems could give the contractor real-time status of his parts requisitions giving them additional time to make sound business decisions. During the CAR team visit to FedEx, the team found that FedEx maintenance contractors have shared access to the FedEx material system. This allowed them to obtain the parts status within 2 hours after requesting the part--not days like the government system (see Appendix H).

We asked the CAR customers at the Customer Symposium what they thought about allowing the contractor to supply more of the parts. They said they did not care who bought the parts as long as the parts conformed to the technical order requirements. They did express some reservation about not having government oversight on parts purchased by the contractor. However, the CAR team found in follow-on discussions that most of the customer representatives were unaware that DCMC has a government property manager providing oversight on contractor purchased items for government PDM contracts.

Another problem the CAR team identified had to do with timely identification and requisition of parts requirements. Many times government parts could have been made available in time if enough lead-time was provided. Currently, few weapon systems have an accurate, up-to-date material requirements list or Bill of Materials (BOM). Though there will always be "surprises" when performing maintenance, steps need to be taken to minimize the unknowns. Systematic reviews and updates of the BOM is a MUST!

The CAR team identified another constraint in the area of Readiness Spares Division (RSD) parts. PDM contractors are not allowed to perform repair on RSD items slated for overhaul. Consequently, when a reparable item fails, the contractor must requisition another part, ship the carcass to the depot, and either wait for it to be repaired, hope a replacement is shipped or cannibalize the part from another aircraft. Waiting for these parts has a significant impact on cost and schedule. In many cases, the contractor has the capability to overhaul the part in-house or can subcontract with a vendor (in many cases the contractor would go to the same vendor the government uses to perform the repair). This has the advantage of allowing the contractor to assume more risk, still maintain the RSD asset under government control and maintain RSD requirements and funding.

IMPACT

At the contractor symposium, the contractors indicated that the material support issue has a great effect on performance. Most contract flowday extensions requested are in relation to some part need. A properly manloaded aircraft, in a properly equipped facility, becomes nothing but an inefficient effort when parts are not available to repair the aircraft. An accurate bill of materials (BOM) for the basic PDM is critical for the contractor to lay in the known material requirements, and a responsive parts acquisition system is imperative to support the unknown material requirements.

RECOMMENDATIONS

1. The SPO should invest the time to ensure the accuracy of the bill of materials (BOM) and establish a Material Requirements List (MRL) for aircraft PDM. An accurate bill of materials (BOM) must be developed and utilized to ensure required parts are on-hand when needed. Waiting to order parts the day the aircraft arrives is courting disaster since lead-time for some parts are as long as the PDM flow cycle. To reduce this, there has to be an early "shake-down" and inspection of the aircraft once it is placed in the contractor facility and advance notice of work to be done so that up front planning is accomplished to get the parts when they are needed.

2. The contractor’s access to the government parts system should be enhanced. The communications technology to accomplish this is readily available. The data systems used for requisitioning need to be overhauled. Technology is available that could provide real time data for contractors. Current lean logistics efforts underway to revamp the legacy systems need to exploit this technology so that contractors are able to have all the information they need to make smart business decisions.

  1. Allow the contractor more flexibility in establishing GFM/CAP stock levels and buying more contractor acquired material (CAP). (In Lean Logistics terms, this level corresponds to the Readiness Base Levels (RSD). Although it is true that the government can obtain a better price and availability for most parts, many can be just as easily bought by the contractors. The government does not need to specify the amount of CAP/CFM required for each aircraft. Contractors should be able to estimate this from experience or good business sense. Permitting contractors to select those parts that they can easily obtain would shift responsibility and parts workload away from the government. Apply Lean Logistics principles.
  2. Negotiate with contractors on parts they may be better suited to obtain as CFM rather than GFM. In some cases, they may be able to negotiate as good a price and better delivery times. At the same time, it would shift more of the risk for supply support to the contractor and make him more accountable for the schedule.

  1. The contracting SPO should develop and implement, in concert with the contractor and DCMC, a Shop Support Center (SSC) concept similar to that being used by the organic production functions in the C-141 and C-130 SPOs. The members of this support center would be accountable for the resolution of all material, engineering, financial and contractual issues for the contractors. This SSC should to be augmented with DCMC personnel.

  1. Authorize the contractor, if within their capabilities, to repair/overhaul in-house or subcontract the repair/overhaul of reparable RSD components removed from aircraft when depot turnaround times are unacceptable.
  2. Reduce government oversight by allowing the contractor to solely track and account for all GFM at their facility.
  3. List in Appendix B of the RFP the stock class and National Stock Number (NSN) of the items that will be CFM--stretch this number to the maximum. CFM should include items that are commercially available and are used by any function performing aircraft repair (commercial or government). Some examples are paint, sealant, batteries, raw material, cleaners, grease and lubricants, fluids, oils, abrasives, etc. The pricing of CFM should be part of the Fixed Price Basic PDM CLIN and all Fixed Price Over and above CLINs. CFM associated with Negotiated Over and Above should be treated as time and material (T&M) effort. A T&M clause needs to be inserted into the Negotiated Over and Above area of the RFP.

 

 

 

 

 

 

 

 

 

 

MATERIAL SUPPORT METRICS

In measuring this initiative, there should clear evidence that there is a direct correlation in moving the material support risk from the government to the contractor by seeing reduced flowdays and cost. The notional chart above tracks what some could call ISSUE EFFECTIVENESS and can be used by both the government and the contractor to see how well implantation of the above recommendations are affecting operations. Other measurements to consider are the number of cannibalization actions, the size of the GFM inventory, plus others that portray how well material support is being provided to the PDM process.

 

THE OVER & ABOVE PROCESS

DISCUSSION/BACKGROUND

Over and Above (O&A) is work discovered during the course of performing overhaul, maintenance, and repair efforts that is: (a) within the general scope of the contract; (b) not covered by the line item(s) for the basic work under the contract; and (c) necessary in order to satisfactorily complete the contract.

Over and Above Work performed on aircraft during Programmed Depot Maintenance (PDM) can be divided into two categories:

Normally in PDM contracts, a period ranging from 10 to 20 days is allotted for the contractor to perform an initial inspection of the aircraft. The purpose of this inspection is to determine what work needs to be performed on the aircraft. Contractors estimated to the CAR team that approximately 70-80 percent of unanticipated repair items, or over and above items, are discovered during this inspection.

Before the inspection period is complete, the Administrative Contracting Officer (ACO) issues a blanket work request authorization that provides the funding and authorization for the contractor to work over and above discrepancies. Individual work requests are submitted to the DCMC Quality Assurance Representative (QAR), who performs the initial review and determines if the repair is covered under the basic contract provisions and if not, whether the repair should be made. Once the determination has been made to work the discrepancy, the DCMC Industrial Specialist (IS) and the contractor enter discussions/negotiations to reach an agreement on the number of hours required to perform the work. Unless there is a work stoppage situation, agreement must be reached prior to contractor commencement of work. Once all over and above negotiations are complete, (usually when the PDM is complete), the contractor submits a consolidated work request package of all completed work requests to the ACO for definitization and incorporation into the contract.

The primary tool used by DCMC to track the over and above process is the Over and Above Centralized Information System (OACIS). OACIS is a database developed and administered by DCMC to provide visibility of the O&A process. It provides the following over and above information on each aircraft: a description of each discrepancy; the proposed hours to repair the discrepancy; the DCMC IS recommended hours; the negotiated hours; the material associated with the work request; the total dollars authorized for the over and above effort; and the balance remaining after negotiation of each work request. In addition, the system provides a total of all costs of over and above effort per aircraft.

IMPACT

As outlined above, the over and above process is labor intensive for both the contractor and the Government. The greater the number of people involved and the more checkpoints required, the slower the process.

A major drawback of over and above work is the unpredictability of the cost associated with the effort. By definition, the cost of over and above work is not included in the basic effort of the contract. Therefore, it is difficult for the customer to determine up-front the total cost of PDM for each aircraft. Some of that uncertainty can be reduced by providing firm-fixed prices (FFP) for as much over and above effort as possible. There are also hidden costs involved in the processing of work requests. DCMC informed the CAR team that the average administrative cost associated with processing one over and above work request is approximately $275.00.

The O&A process is time consuming because it requires the input of various technical specialists. The time spent determining to work or not work a discrepancy, and then agreeing to the amount of time required to perform the work could possibly have an impact on the schedule of the aircraft. Also, if additional funding requirements are not identified early, there could also be a delay in receiving funding and the authorization to work. Each day the aircraft schedule slips increases the likelihood of customer dissatisfaction. Streamlining the entire over and above process will greatly enhance savings in cost and time, which will ultimately result in customer satisfaction.

RECOMMENDATIONS

1. Involve the Defense Contract Management Command (DCMC) in the pre-contractual phase of acquisitions and delegate complete responsibility of contract administration to DCMC.

Air Force Material Command (AFMC) Re-engineering Initiative # 14, Increase Reliance on the Defense Contract Management Command (DCMC), dated 6 May 1996, addresses this issue in its entirety. The purpose of the initiative was to identify duplication of effort between AFMC and DCMC as well as unexploited DCMC capabilities. The key recommendations of the initiative are highlighted below.

In the past, DCMC did not become involved in the acquisition cycle until late in the process, usually after contract award. Early Contract Administration Services, or Early CAS, allows AFMC to take advantage of the wealth of DCMC expertise available in the pre-award phase. DCMC maintains historical data to determine contractor capabilities and performance as well as over and above data to facilitate the identification of fixed-priced over and above candidates. Recommendation 1-1 from the study suggests that "Buying activities involve DCMC in pre-contractual efforts leading to a solicitation or award." DCMC is the primary agency established to provide contract administration for all of the Department of Defense. In many instances, AFMC and even the using agency are integrally involved in contract administration of the PDM process, duplicating many of DCMC’s efforts. Recommendation 1-3 states "Program managers establish and annually update a joint DCMC/buying office Memorandum of Agreement or similar document that outlines roles, responsibilities, resources, and structure of the Integrated Product Team (IPT)." Recommendation 2-1 states "Restrict the practice of withholding normal contract administration functions delegated to the CAO." Formal retention of any of these functions must be approved by the Contract Clearance Approval Authority." The study also addressed government oversight of contractor technical and quality functions. In this area, the following recommendations were made, which would also be applicable in the PDM environment: 4-1 Require AFMC program offices to rely primarily on DCMC to conduct in-plant review, witness and verify in-plant testing, and approve all related test procedures; 4-2 Require AFMC program offices to eliminate the duplication of contractor document reviews; 4-3 Require AFMC to eliminate the duplication of evaluating Engineering Change Proposals (ECPs) and ensure all possible ECP functions are delegated to DCMC. Following these guidelines will streamline the process and eliminate duplication of effort, resulting in reduced cycle time.

2. Include a detailed Over and Above Clause in the contract.

As a minimum, the over and above clause should include a listing of the information to be included on each work request (compatible with OACIS), a definition of hands-on labor, and a general description of how work requests will be processed. Though it should provide detail, it should also allow the contractor some flexibility to adapt to the processes already in use at the facility. Specific detail on the requirements for the processing of over and above is usually documented in a Memorandum of Agreement (MOA), which should be developed as soon as possible after contract award. The ACO and the contractor mutually agree to the procedures for Government administration and contractor performance of over and above work requests. The MOA is the vehicle used to clearly delineate the responsibilities of the Government representatives and the contractor.

The requirements of the clause will ensure that the key players involved in the process know exactly what their roles and responsibilities are, thereby making the process flow more smoothly and efficiently. Including the correct information on the work requests will provide the historical data necessary for the development of standards and identification of FFP candidates.

3. Develop/maintain a historical database of over and above actions to facilitate the development of standards and FFP of over and above effort.

As stated earlier, the over above process is labor intensive and involves unpredictable costs. The optimum contracting situation for over and above is to significantly reduce the number of over and above discrepancies requiring negotiation by developing standards and firm-fixed prices for the effort up-front. This can only be accomplished if complete and accurate over and above historical data exists.

The information can be used in numerous ways. If an item is occurring frequently, there will be a historical record of the discrepancy and the time required to repair it. This information can be used to identify candidates for FFP and standards development. Once the information from several aircraft has been consolidated, an average cost of over and above per aircraft can also be provided. Better estimates of the total cost of O&A work per aircraft can be provided, which will reduce the uncertainty associated with the effort. Requiring the use of the OACIS database provides all of these benefits. Additionally, contractors should be allowed READ ONLY access to the OACIS.

4. Reduce the number of over and above discrepancies requiring negotiation.

Paragraphs a, and b are recommended methods for reducing O&As requiring negotiation before contract award and are initiated by the buying activity:

    1. Include the cost of over and above in the basic effort of the contract.

This method requires extensive historical data on the O&A tasks commonly performed on the aircraft, which is made available to prospective contractor’s in the buying activity’s bid library. Instructions to offerors on how to prepare the proposal would be listed in sections L and M of the RFP. Using historical data, determine the over and above effort with the highest frequency of occurrence (example: 80 percent of the effort are at 35 hours or less--this will vary by aircraft or program). Determine the cost to perform this effort per aircraft and include the cost in the basic portion of the contract. Any over and above effort up to 35 hours (or what ever limit the program sets) is not negotiated, and is worked at no additional cost. Any work request for 36 hours and above will be negotiated. Since the 35 hours has already been included in the basic effort, the difference between the negotiated amount and the 35 hours will be allowed as additional effort (example: The work request is submitted for 70 hours, is negotiated to 60 hours and the contractor is allowed 25 hours for the work request: 60 - 35 = 25).

    1. Use developed standards from the OACIS database and Materiel Requirements Review Board (MRRB) brochure to develop Fixed Price Over & Above Contract Line Item Numbers (CLINs) or for use as standards to be used under the Negotiated Over & Above CLIN.

If a Fixed Price Over & Above CLIN or a Negotiated standard is used then no negotiations are required for that task. The more Fixed Price Over & Above CLINs and standards are used the fewer negotiations will be required for over and above tasks. Each standard used during in the RFP (as either a Fixed Price Over & Above CLIN or a standard for negotiated Over & Above) will require an occurrence factor based on OACIS database and MRRB historical data. High occurrence and low cost tasks should remain negotiated standards while high cost-low occurrence items should be priced as a Fixed Price Over & Above CLIN. The standards should be reviewed and updated annually during the exercise of the yearly contract option.

Paragraphs c and d are recommended methods for reducing O&As requiring negotiation (during contract performance) and are initiated by DCMC representatives.

c. Develop standards for over and above tasks. Over and above tasks performed on a repetitive basis are candidates for the development of standards. The Industrial Specialist (IS) and the contractor reach agreement on the amount of time required to perform a specific task, and apply that standard each time a work request is submitted for the effort. Pre-negotiated standards greatly reduce the amount of time required to process a work request. Once the decision is made to repair an item, the contractor can proceed with the work. Established standards may be unilaterally withdrawn by either party upon written notice.

The same method can be used to develop firm-fixed prices for O&A tasks. The only difference is that the effort and associated cost are incorporated into the contract.

d. Develop weighted average for over and above tasks

The following method can be used to develop weighted averages for tasks for which standards cannot be developed:

Considering historical data, usually O&A data on several aircraft, determine the O&A occurrences with the highest frequency (example: 80 percent of the work effort is 5 hours or less, per work request--this number will vary by aircraft or program). Develop a weighted average for the effort by determining the average negotiated hours, the average actual hours and then determining the average of the two (example: 2.5 average negotiated hours + 2

average actual hours = weighted average of 2.25 hours). The weighted average is then applied to all work requests submitted at or below the threshold (example: work requests from .10 hours to 5 hours are adjusted to 2.25 hours).

This may not be necessary if there is Fixed Price Over & Above and negotiated standards for tasks less than the weighted average hours. Tasks that require a large amount of man-hours but vary in scope each time might be best left as negotiated maintenance tasks. Tasks that do not vary in scope for each occurrence should have a standard developed. This method reduces processing time because the work request is reviewed by Quality Assurance only and the ACO is not involved. Any effort proposed at or below the threshold will automatically have the weighted average applied; therefore, the need for negotiations is not needed. The actual time to perform each work request is recorded by the contractor and submitted by CDRL to allow the contractor and the government to renegotiate the weighted average, if needed, on a periodic basis.

5. Ensure customer understanding of contract requirements.

Often, the customer does not have a clear understanding of what is actually contained in the Statement of Work and what work the contractor is contractually required to perform. There is often confusion between what meets contract requirements and what the customer considers "cosmetically" acceptable. This can result in increased cost to the customer and also increased cycle time due to rework.

Having the customer participate in MRRB and PDM Specification development and attending Program Management Reviews will enhance the customer’s understanding of the requirements. If the customer has a better grasp of what is required and has participated in the development of those requirements, he will have a more realistic viewpoint of what to expect once the aircraft completes PDM. This also applies to AFTO Form 103 requirements and AFTO Form 781 discrepancies. The customer must know and understand that the only work beyond the PDM specification and Contractor’s SOW that will be accomplished during PDM are approved AFTO Form 103 requirements. and only those AFTO Form series 781 discrepancies that DCMC determines as safety of flight, economical repair, and/or quality defect discrepancies on the aircraft during acceptance inspection.

In addition, every customer should be provided with a copy of the Contractor’s Statement of Work, PDM Specification, and MRRB documents in order for them to reference in preparing and receiving aircraft for PDM input.

OVER AND ABOVE INITIATIVE METRICS

There are quite a few areas that can be measured in tracking Over and Above improvements. In fact, the DCMC is probably ahead of the ALCs in measuring this area because they do it on a day-to-day basis in many contractor facilities. SPOs would be encouraged to review the DCMC metrics on a recurring basis to get a sense of how well this area is being improved. One particular that is a good indicator of how well improvements are progressing is keeping track (hopefully a decreasing amount) of the total number of negotiated O&A actions that occur per PDM. Another important measurement is to track the actual O&A dollars the contractor charges per aircraft--this should progressively decrease as more O&A issues are worked "up front" in contracting and MOA actions. Other specific areas to measure are (1) the Number of O&A Work Request processed per aircraft, (2) the number of actual delays that occurred due to having to negotiate O&A repair actions, and/or (3) the number of Firm Fixed Price O&A Items included in a contract.

 


ENGINEERING SUPPORT INITIATIVE

 

BACKGROUND/DISCUSSION

 

Engineering support is the process by which the ALC oversees and provides assistance for those engineering needs that are outside the contractor’s authority or capability. Engineering support can, and at times does, impact the flow days of an aircraft. It is, however, a necessary part of PDM that engineering authority be at the ALC level in order to maintain configuration control on the aircraft. It is the process for obtaining engineering disposition that can impact flowdays, because the responsible engineers are remote from the contractor and the problem.

Three different perspectives of engineering support from the contractor, the customer and the SPO are summarized below:

"Contractors think that they could process airplanes faster if they were given more engineering authority--either internally or by having more AF engineering authority (responsible persons) on site. Also, contractors perceive that there are too many layers of engineers (contractor, DCMC, ALC, etc.) that slow things down."

"As a customer, I am concerned about configuration control. I would want to have assurance that AF oversight capability is retained."

"As a SPO engineer we have more insight in what’s happening with the weapon system, new problems and repairs, and customer concerns because we deal with all Depots and field units whereas the contractor engineer has very limited insight into anything that is not occurring at the PDM facility where he is located."

Currently the format, process, and level of SPO Engineering support supplied to contractor PDM facilities varies greatly for each weapon system. Each SPO (Chief Engineer) decides what level of engineering authority to give the contractor and the process the contractor must follow to obtain SPO engineering support. Usually the contractor engineering support is limited to one or two engineers who have been certified by the SPO to have limited engineering authority. The majority of engineering support required during a PDM deals with aircraft structure.

Usually the repair of aircraft commodity (RSD) items beyond O & I level T.O. requirements is not allowed during PDM. The item is usually removed and returned to the USAF supply system and a new/overhauled item installed. For many of these items the SPO does not retain engineering authority and thus cannot give the contractor engineering personnel engineering authority for those items.

When any repair is to be done that falls outside of the scope of the negotiated PDM contract or has no standardized procedure, an approved procedure is required to ensure that the repair is performed to design specification. Many times, the repair has been standardized and is documented in the technical manuals for the aircraft. In this case, the contractor need only to follow the technical manual procedure.

When the repair required is not documented in the technical manual, the contractor or SPO engineer must provide an engineering disposition. SPO Engineering support is provided to contractors when technical assistance is needed or required by contract during the course of PDM activity. For the most part, engineering support requirements do not have a direct impact on the flow time of an aircraft, except when a stumble-on repair item is discovered near the end of the PDM schedule.

The discovery of a stumble-on repair item triggers three concurrent processes: (1) Acquisition of the part(s) needed for the repair (if not in contractor’s inventory), (2) Over & Above negotiations to fund the repair (if not fixed- price repair), and (3) Engineering support for technical guidance (if repair is not in tech manuals). The current method of communication between contractor and SPO engineering personnel is usually telephone and FAX.

Today, contractors rely on government engineering services for dispositions during the contract activities. This dependence adds flow days every time a discrepancy is discovered and must be dispositioned. In order to achieve a significant reduction in this process time, contractors must, by contract agreement, maintain some level of engineering capability at the contractor site. A program by which this engineering capability could be certified to perform some of the government engineering functions would greatly reduce the interruptions to the schedule. There is a similar delegation of engineering authority in the Federal Aviation Administration (FAA) by use of a Designated Engineering Representative (DER) certification.

Commercial Process:

FAA rules state that major repairs not in FAA approved maintenance manuals (developed by the original manufacturer) must have engineering approval by the original manufacturer before implementation. All engineering dispositions must be signed by an FAA certified DER.

RECOMMENDATIONS:

1. Contractor Engineering Certification: The weapon system Chief Engineer should certify all contractor engineers prior to them providing any engineering dispositions on the aircraft. The certification process should determine if the engineer has an FAA DER certification (and what type), education, and experience. The review process could also include interviews and training/orientation at an organic PDM facility where government engineers could determine first hand the contractor engineer’s qualification. The weapon system Chief Engineer should certify contractor engineers by letter once satisfied they are qualified. This letter should specifically state the level of engineering authority the contractor engineer is authorized and should match contract language in the PDM contract. At a minimum the DER certification should be a structural DER.

  1. Contractor Engineering Authority and SPO Engineering Support Process:

    1. Contractor engineering personnel that have a FAA DER certification and have the experience and education required by the weapon system chief engineer should be certified to provide repair instructions for repairs covered by DOD Technical Orders (T.O.) and for repairs not in DOD T.O.s on secondary structural and system components that the SPO has engineering authority over without SPO approval prior to implementation.
    2. Contractor engineering personnel that have an FAA DER certification and have the experience and education required by the weapon system should be certified to provide repair instructions for repairs not in DOD T.O.s on primary structural and system components that the SPO has engineering authority over with SPO engineering approval prior to implementation. The contractor engineer should provide a suggested repair disposition for the SPO engineer to review and not require the SPO to provide the disposition. The SPO engineer should only have to accomplish a review and approval. When contractor engineers cannot develop an engineering disposition they should immediately contact SPO engineering for support.

    1. This limited engineering authority would only require the contractor to come to the SPO prior to implementation for defects on primary structural and system components, and when the contractor engineer requires SPO assistance. This would be a small percentage (10-15%) of the total number of requests for engineering assistance (AFMC Form 202).

  1. There should be no on-site DCMC engineering review of contractor engineering dispositions for technical content. DCMC should only review the disposition when determining if it is O&I level discrepancy that should not be corrected and for determining man-hours associated with negotiated over & above.

4. RSD items: Review the reparable policy to determine if contractors could make minor part repairs as opposed to submitting a failed part to the repair cycle and having to wait for a replacement. This would require the SPO to obtain engineering authority from each responsible commodity engineering authority.

5. Reporting: All contractor engineering dispositions should be completed on AFMC Form 202 or similar form. A monthly report, to include copies of completed AFMC Form 202s, should be sent to the SPO engineering organization for review and storage. These reports should be sent and stored electronically.

6. Automated discrepancy review (remote teleconferencing): Utilize PC video-conferencing technology for sharing photographic information in conjunction with audio (speaker phones) between contractor and engineering support. Require contractors to have PC video-conferencing equipment per an industry standard. Select the industry standard. Require contractor to have scanning equipment to digitally scan repair sketches to support video teleconferences and electronic submittals and storage of AFMC Form 202s.

ENGINEERING SUPPORT METRICS

Number of AFMC Form 202’s sent to SPO engineering for review and time to respond.

Number of AFMC Form 202’s sent to SPO engineering for assistance and time to respond.

Time required for contract engineers to process AFMC Form 202 requests.

 


ORGANIZING FOR SUCCESS INITIATIVE

DISCUSSION /BACKGROUND

If one considers the Secretary of Defense’s Depot Maintenance Overview policy paper (a portion of which is covered in Appendix A of this report), and the projected downsizing of DOD compared to scheduled workload (for example: see C-130 PDM projected workload chart, Appendix A), the assumption has to be made that contracting out organic workload is going to increase in the DOD. In considering this, coupled with the CAR teams visit to Federal Express Corporation. and exploring ways the commercial world accomplishes contract aircraft repair, the CAR team believes that there is a need to consider ways to restructure the System Program Offices and/or the Air Logistics Center to better provide the services and products of contract aircraft repair to the customer.

The team looked at several options and spent many hours discussing the pros and cons of each; however, the team quickly found there was not a sufficient number of people, with the right expertise, on the team to consider an organizational change. Nonetheless, the team did study this area as discussed in the following sections. However, there are no specific recommended organizational changes in the SPOs and the ALC. Although the team felt this was a fertile ground for improving and institutionalizing the changes suggested in this handbook, the team felt that a further study should be chartered to propose any specific changes.

1. The CAR team organizational focus considered 4 areas that related to the CAR process. The first area concerned the multitude of services and support ALCs and other DOD agencies provide contractors. In the CA