π Lecture 29 β Network Scheduling Techniques
π Overview: This lecture focuses on slack (float) time in project networks β how to calculate it, identify it, and use it for effective project control. It also covers network re-planning techniques, including resource leveling and allocation, which are essential for adjusting schedules when the unexpected occurs during project execution.
ποΈ Topics Covered
The lecture covers four main areas: Slack Terminology defining TE and TL and the slack formula; Slack Time Calculation with forward and backward passes through a PERT network; Slack Identification as an early warning system for project managers including negative slack causes; and Network Re-planning discussing techniques like resource leveling, resource allocation, parallelization, and methods for reducing project time.
π Lecture Summary
29.1 Slack Terminology
Slack is defined as the difference between the latest allowable date and the earliest expected date for an event in a project network. Two key terms are used: TE = the earliest time (date) on which an event can be expected to take place, and TL = the latest date on which an event can take place without extending the completion date of the project. The formula for slack is straightforward.
π Definition β Slack Time: The amount of time an activity or event can be delayed without affecting the project completion date. π Formula: Slack time = TL β TE π Example: For event 1 in Figure 29.1, TE = 0 and TL = 0, so slack = 0 β 0 = 0. This is the reference point. For event 3, TE = 2 weeks and TL = 5 weeks, giving a slack of 5 β 2 = 3 weeks.
29.2 Slack Time Calculation
The calculation for slack time is performed for each event in the network by identifying the earliest expected date and the latest starting date. Events on the critical path have no slack (i.e., TL = TE) and provide boundaries for non-critical path events. The earliest time for an event not on the critical path assumes starting as early as possible, while the latest allowable date is found by working backward.
For complex networks containing multiple paths, the earliest starting dates must be found by proceeding from start to finish through the network (forward pass), while the latest allowable starting date must be calculated by working backward from finish to start (backward pass).
The importance of knowing exactly where slack exists cannot be overstated β Donald Marquis observed that companies making proper use of slack time were 30 percent more successful than average in completing technical requirements. PERT charts can be reconstructed with time scales, requiring a decision on whether to use early or late time requirements for slack variables.
To make full use of PERT/CPM capabilities, four values are identified: ES (earliest start), EF (earliest finish), LS (latest start), and LF (latest finish). The earliest starting time of a successor activity is the latest of the earliest finish dates of its predecessors. The latest finishing time for an activity entering a node is the earliest finishing time of the activities exiting that node.
29.3 Slack Identification
The identification of slack time can function as an early warning system for the project manager. If total slack time begins to decrease from one reporting period to the next, this could indicate that work is taking longer than anticipated or that more highly skilled labor is needed β a new critical path could be forming.
Negative slack (or negative float) occurs when work units show a negative value after subtracting the earliest start from the latest start. This typically happens when performing a backward pass from the customer's end date milestone, not where the forward pass ends. If the forward pass extends beyond the customer's end date (position 4 in Figure 29.5), negative slack is created.
π‘ Why this matters: Negative slack is an early warning indicator that corrective action is needed to maintain the customer's end date.
Negative slack most likely results when: the original plan was highly optimistic but unrealistic; the customer's end date was unrealistic; one or more activities slipped during project execution; assigned resources did not possess correct skill levels; or required resources would not be available until a later date.
29.4 Network Re-planning
Much iteration is normally made during the planning phase before the PERT/CPM chart is finished. Slack times form the basis from which additional iterations, or network replanning, can be performed. This is done either at program conception to reduce the length of the critical path, or during the program should the unexpected occur.
29.4.1 Network Replanning Techniques
Two network replanning techniques are based almost entirely upon resources: resource leveling and resource allocation.
- Resource leveling is an attempt to eliminate manpower peaks and valleys by smoothing out period-to-period resource requirements. The ideal situation is to do this without changing the end date, though in reality, the end date moves out and additional costs are incurred.
- Resource allocation is an attempt to find the shortest possible critical path based upon available or fixed resources. The problem is that employees may not be qualified technically to perform on more than one activity in a network.
Several other methods for reducing expected project time include: elimination of some parts of the project; addition of more resources; substitution of less time-consuming components or activities; parallelization of activities; shortening critical path activities, early activities, longest activities, easiest activities, or activities least costly to speed up; shortening activities for which you have more resources; and increasing work hours per day.
Parallelization involves accepting a risk by assuming a certain event can begin in parallel with a second event that would normally be in sequence. For example, four weeks can be saved by sending out purchase orders after contract negotiations but before signing the contract. This risk is normally overcome by issuing a long-lead procurement letter immediately following contract negotiations.
Two other common risk types: (1) manufacturing must order tooling before engineering finishes the prototype, and engineering may design the prototype to fit the tooling; (2) a subcontractor may work without completed blueprints, and blueprints are later changed to represent the as-built end-item.
For large programs, it is often better to have each department develop its own PERT/CPM networks based on the work breakdown structure, then integrate them into one master chart to identify total program critical paths. Segmented PERT charts can also be used when multiple contractors work on the same program β the prime contractor integrates all subcontractors' PERT charts.
β Key Takeaways
Slack (float) is the difference between latest and earliest event times (TL β TE), and events on the critical path have zero slack. Slack time calculation requires both forward passes (left to right) and backward passes (right to left) through the network. Negative slack occurs when forward pass work extends beyond the customer's end date, serving as a critical early warning signal. Network re-planning uses resource leveling (smoothing peaks) and resource allocation (shortest path with fixed resources), plus methods like parallelization and activity shortening. For complex programs, individual department PERT charts are integrated into a master chart to identify total program critical paths.
π§ Quick Revision Questions
- What is the formula for calculating slack time, and what do TE and TL represent?
- How do you identify which events are on the critical path in terms of their slack?
- What causes negative slack, and why is it considered an early warning indicator?
- What is the difference between resource leveling and resource allocation in network re-planning?
- When parallelizing activities, what risk does the contractor incur, and how is it typically managed?
π Lecture 30 β NETWORK SCHEDULING TECHNIQUES
π Overview: This lecture examines the methodologies for estimating activity times and total program times in network scheduling. It covers the full PERT/CPM planning process, crash time analysis for cost-time trade-offs, common problem areas in implementing these techniques, and alternative PERT/CPM models. Understanding these concepts is crucial for effective project scheduling, resource allocation, and cost control.
ποΈ Topics Covered
The lecture covers estimating activity time using three-point estimates (optimistic, pessimistic, most likely) and the beta distribution; calculating total program time using standard deviation and variance; the six-step total PERT/CPM planning process; crash time analysis in CPM for cost-time trade-offs; common problem areas in PERT/CPM including human factors, cost control, and historical data limitations; and alternative models such as PERT/cost and PERT/performance.
π Lecture Summary
30.1 Estimating Activity Time:
To determine elapsed time between events, functional managers must evaluate the situation and submit their best estimates based on historical data. For non-repetitive activities, managers submit estimates using three possible completion assumptions. The most optimistic completion time assumes everything goes according to plan with minimal difficulties, occurring approximately 1 percent of the time. The most pessimistic completion time assumes maximum potential difficulties will develop, also occurring approximately 1 percent of the time. The most likely completion time is what would most often occur if the effort were repeated over and over again.
Two assumptions must be made before combining these three times into a single expression for expected time. First, the standard deviation (Ο) is one-sixth of the time requirement range, based on probability theory where endpoints are three standard deviations from the mean. Second, the probability distribution of time required for an activity must be expressible as a beta distribution.
π Definition β Expected Time (te): The weighted average time for completing an activity, calculated from optimistic, pessimistic, and most likely time estimates. π Formula: te = (a + 4m + b) / 6 where a = most optimistic time, b = most pessimistic time, and m = most likely time π Example: If a = 3, b = 7, and m = 5 weeks, then te = (3 + 4(5) + 7) / 6 = (3 + 20 + 7) / 6 = 30/6 = 5 weeks. This becomes the activity time in the PERT chart. If a = 2, b = 12, and m = 4 weeks, te = (2 + 16 + 12) / 6 = 30/6 = 5 weeks, but with higher uncertainty due to wider spread between optimistic and pessimistic times.
π‘ Why this matters: The three-point estimate method accounts for uncertainty in non-repetitive activities, but managers must carefully evaluate risks since different combinations of a, b, and m can yield the same te with vastly different levels of uncertainty.
30.2 Estimating Total Program Time:
To calculate the probability of completing the project on time, the standard deviations of each activity must be known. The variance (ΟΒ²) is the square of the standard deviation and is primarily useful for comparison to expected values. The total path standard deviation is calculated by the square root of the sum of the squares of the activity standard deviations.
π Definition β Variance (ΟΒ²): The square of the standard deviation, used for comparing to expected values in project time analysis. π Formula for standard deviation: Ο = (b - a) / 6 where b = pessimistic time and a = optimistic time π Formula for total path standard deviation: Ο(total) = β(ΟβΒ² + ΟβΒ² + ΟβΒ² + ... + ΟnΒ²) π Example: From Figure 30.1, the critical path of Figure 29.1 shows activity times with their corresponding standard deviations. The total path standard deviation is calculated by taking the square root of the sum of squares of individual activity standard deviations along the critical path.
30.3 Total PERT/CPM Planning:
PERT scheduling is a six-step process. Steps one and two: The project manager lays out a list of activities and places them in order of precedence, creating logic charts (also called arrow diagrams, work flow, or networks). These diagrams look like networks but without activity times or critical paths identified.
Step three: Review the arrow diagrams with line managers (the true experts) to ensure correct activity identification and interrelationships. Step four: The functional manager converts the arrow diagram to a PERT chart by identifying time duration for each activity, based on the assumption of unlimited resources since calendar dates are not yet defined.
Step five: The first iteration on the critical path examines whether critical calendar dates satisfy project requirements. If not, the project manager must shorten the critical path by asking line managers to take the "fat" out of their estimates. Step six (often most overlooked): The project manager places calendar dates on each event, converting from unlimited resource planning to limited resource planning. If line managers cannot commit to calendar dates, replanning is necessary.
PERT re-planning should be an ongoing function during project execution. Primary objectives on a schedule are: best time, least cost, and least risk. Secondary objectives include studying alternatives, optimum schedules, effective use of resources, communications, refinement of estimating, ease of project control, and ease of time or cost revisions. These objectives are limited by constraints such as calendar completion, cash flow restrictions, limited resources, and management approvals.
30.4 Crash Times:
The basic difference between PERT and CPM lies in the ability to calculate percent complete. PERT is used in Research and Development or development activities where percent-complete determination is almost impossible, making PERT event oriented rather than activity oriented. Funding is normally provided for each milestone achieved. CPM is activity oriented because in construction-type activities, percent complete along the activity line can be determined.
Crashing involves speeding up project phases. Requirements for CPM crashing include: (1) emphasis on activities, not events; (2) consideration of both time and cost for each activity; and (3) considering only critical path activities, starting with those having the lowest crashing cost per unit time.
π Definition β Crashing: The process of speeding up project activities by adding resources, typically at increased cost, to reduce total project duration. π Example: In Figure 30.2, activity A (on critical path) has a weekly crashing cost of $2,000 per week for maximum 2 weeks. Activity C has lower crashing cost but is not on critical path, so it is not considered first. After A, activity F at $3,000 per week for maximum 3 weeks is considered. Total crashing from base $120,000 to $157,500 reduces time from 23 weeks to 15 weeks (Figure 30.3). Crashing non-critical path elements would cost $7,500 without reducing total project time.
π‘ Why this matters: As each activity is crashed, a new critical path may develop. The purpose of balancing time and cost is to avoid wasteful resource use. Direct and indirect costs create a region of feasible budgets (Figure 30.4), bounded by early-start (crash) and late-start (normal) activities. CPM also contains the concept of slack time β the maximum time a job may be delayed beyond its early start without delaying project completion (Figure 30.6).
30.5 PERT/CPM Problem Areas:
PERT/CPM models have several disadvantages and problems. PERT is end-item oriented, making it difficult for many companies to incorporate. Upper-level managers may feel PERT/CPM removes their power and decision-making ability, especially when forced to accept it as part of contractual requirements.
A distinct contrast exists between planners and doers. Planning is performed by the program office and functional management, but once the network is constructed, planners become observers relying on doers. Management must convince doers of their obligation toward successful completion. Unless the project is repetitive, there is usually a lack of historical information for cost estimates of optimistic, pessimistic, and most likely times. Problems can involve poor predictions for overhead costs, indirect costs, material and labor escalation factors, and crash costs.
PERT networks assume all activities start as soon as possible, assuming qualified personnel and equipment are available. Cost control presents problems because the project cost and control system may not be compatible with company fiscal planning policies. Many people expect too much from PERT-type networks. Subdividing work packages further by identifying all sub-activities (Figure 30.7) has the advantage of easy direct charge number identification, but the time and cost for this detail may be prohibitive. Managers must ensure the original purpose of identifying prime and supporting objectives is still met.
30.6 Alternative PERT/CPM Models:
Advantages of PERT/time include capabilities for: trade-off studies for resource control, contingency planning in early stages, visually tracking performance, demonstrating integrated planning, providing visibility down through work breakdown structure levels, providing regimented control structure, and increasing functional members' ability to relate to the total program.
However, PERT/time has proved ineffective in controlling resources in many situations. Three parameters are necessary for resource control: time, cost, and performance. Companies developed PERT/cost and PERT/performance models. PERT/cost is an extension of PERT/time that attempts to overcome problems with optimistic and pessimistic time estimates. It is a cost accounting network model based on the Work Breakdown Structure (WBS), capable of subdivision down to work packages. Advantages include containing all PERT/time features and permitting cost control at any WBS level. The primary reason for developing PERT/cost was so project managers could identify critical schedule slippages and cost overruns in time for corrective action.
Attempts to develop effective PERT/schedule models include the Accomplishment/Cost Procedure (ACP). However, development of PERT/schedule techniques is still in its infancy, and many companies feel locked in with their present control methods.
β Key Takeaways
The expected time formula te = (a + 4m + b)/6 is fundamental for estimating activity durations using three-point estimates, but managers must recognize that different combinations of a, b, and m can produce the same te with vastly different uncertainty levels. The six-step PERT planning process progresses from activity identification through unlimited resource planning to limited resource scheduling with calendar dates β step six is the most commonly overlooked yet critical step. Crashing in CPM focuses only on critical path activities starting with the lowest cost per unit time, but crashing can create new critical paths that must be monitored. The fundamental difference between PERT (event-oriented, used in R&D) and CPM (activity-oriented, used in construction) lies in ability to calculate percent complete. PERT/cost was developed to overcome PERT/time's limitations in resource control by enabling identification of schedule slippages and cost overruns in time for corrective action.
π§ Quick Revision Questions
- What is the formula for expected time (te) and what does each variable represent?
- How is the standard deviation of an activity calculated from optimistic and pessimistic times?
- List the six steps of the total PERT/CPM planning process in order.
- Why should only critical path activities be considered for crashing, and what caution must be observed when crashing?
- What is the primary difference between PERT and CPM regarding percent complete, and what was the main reason for developing PERT/cost?
π Lecture 31 β PRICING AND ESTIMATION
π Overview: This lecture explores the critical intersection of pricing strategies and estimation techniques in project management. It covers computerized project management software, various types of cost estimates from order-of-magnitude to definitive estimates, and the structured pricing process that integrates the Work Breakdown Structure (WBS) with functional units. Understanding these concepts is essential for developing rational, competitive bids and effectively controlling project costs.
ποΈ Topics Covered
The lecture begins with an examination of computerized software packages and their capabilities, including precedence networks and activity constraints. It then covers the art and science of pricing and estimation, including cost estimating relationships. Two global pricing strategies (Type I and Type II acquisitions) are defined. The lecture details four main types of estimates: order-of-magnitude, approximate, definitive, and learning curves. Finally, it explains the pricing process, including the role of the Work Breakdown Structure and the vertical-horizontal interface between program and functional management.
π Lecture Summary
31.1 COMPUTERIZED SOFTWARE PACKAGES
There has been an explosion in project management software packages, with prices ranging from a few thousand dollars to $70,000. Computerized project management can answer questions about limited resources, changes in requirements, cash flow, overtime impact, and resource needs. Sophisticated packages can provide schedule and cost answers based on adverse weather, weekend activities, unleveled manpower requirements, variable crew size, splitting of activities, and assignment of unused resources.
Most software systems today use precedence networks, which are activity-on-node methods. The arrow represents the relationship or constraint between activities, while the work is accomplished during the activity.
π Precedence relationships define the logical connections between activities:
- Finish-to-Start (FS): Activity 2 can start no earlier than the completion of activity 1.
- Start-to-Start (SS): Activity 2 cannot start prior to the start of activity 1.
- Finish-to-Finish (FF): Activity 2 cannot finish until activity 1 finishes.
- Percent-Complete Constraint: A specified percentage of one activity must be complete before the last percentage of another can start (e.g., the last 20% of activity 2 cannot start until 50% of activity 1 is completed).
π Example: In Figure 31.1 of the lecture, task 1 and task 2 are related by a solid line. Task 3 and task 4 can begin when task 2 is half finished. Dotted lines indicate slack, and the critical path can be identified with asterisks, different colors, or boldface type.
31.2 PRICING AND ESTIMATION
Many business managers consider pricing an art. While having intelligence on customer budgets and competitor pricing helps, such information is often unreliable. A disciplined approach to pricing helps develop a rational recommendation and documents assumptions for later analysis. Estimates are not blind luck; they are well-thought-out decisions based on the best available information.
Cost estimating relationships (CERs) are typically the output of cost models. Typical CERs include:
- Mathematical equations based on regression analysis
- Costβquantity relationships such as learning curves
- Costβcost relationships
- Costβnoncost relationships based on physical or performance characteristics
π‘ Why this matters: A disciplined pricing process not only leads to more rational bids but also creates documentation that contributes to the learning experiences needed for effective future business decisions.
31.3 GLOBAL PRICING STRATEGIES
Two specific situations prevail in competitive project acquisitions:
- Type I Acquisition: A one-of-a-kind program with little or no follow-on potential.
- Type II Acquisition: An entry point to larger follow-on or repeat business, representing planned market penetration.
The objective for Type I is to win the program and execute it profitably. The objective for Type II is often to win and perform well, gaining a foothold in a new market, sometimes in place of profit.
| Feature | Type I (Profitable Acquisition) | Type II ("Must Win" Acquisition) |
|---|---|---|
| Bid Price Determination | Based on actual cost | Determined by market forces |
| Core Objective | Win and execute profitably | Win and gain market entry |
Effective pricing begins long before proposal development. It starts with preliminary customer requirements, well-understood subtasks, and a top-down estimate with should-cost targets. This allows functional organizations to design a baseline to meet cost targets and gives management time to review and redirect the design before submission.
31.4 TYPES OF ESTIMATES
Projects can range from feasibility studies to complete construction. The desired estimate type and accuracy differ radically. The lecture defines four main types of estimates:
-
Order-of-Magnitude Analysis: Made without detailed engineering data, with an accuracy of Β±35 percent. It uses past experience, scale factors, parametric curves, or capacity estimates (e.g., $/product unit, $/KW electricity).
-
Approximate Estimate (Top-Down Estimate): Also made without detailed engineering data, with an accuracy of Β±15 percent. It is prorated from similar previous projects (estimating by analogy, parametric curves, rule of thumb, indexed cost).
-
Definitive Estimate (Grassroots Buildup Estimate): Prepared from well-defined engineering data (vendor quotes, complete plans, specifications, unit prices), with an accuracy of Β±5 percent.
-
Learning Curves: Graphical representations of repetitive functions showing that continuous operations lead to a reduction in time, resources, and money.
Many companies standardize procedures with an estimating manual, which usually gives better estimates than industrial engineering standards because they include downtime, cleanup time, lunch, and breaks. Estimating manuals work best for repetitive or similar tasks.
For in-house projects, the type of estimate can vary over the project life cycle:
- Conceptual Stage: Venture guidance/feasibility (minimum-scope info)
- Planning Stage: Authorization of funds (preliminary design/scope)
- Main Stage: Detailed work
- Termination Stage: Re-estimation for major scope changes
31.5 PRICING PROCESS
This activity schedules the development of the Work Breakdown Structure (WBS) and provides management with two of the three operational tools for project control. The integration of the functional unit into the project environment occurs through the pricing-out of the WBS. The total program costs obtained by pricing out activities provide the third management tool.
The WBS and activity schedules are priced out through the lowest pricing units of the company. Costing information is rolled up from the task level to the project level and then to the total program level. Cost data must be analyzed for their potential impact on company resources (people, money, equipment, facilities). Proper analysis provides management with a strategic planning model for integrating the current program with others.
π Vertical-Horizontal Interface: The pricing-out of the Work Breakdown Structure provides the basis for effective communication between functional management (vertical hierarchy) and program management (horizontal hierarchy), giving both parties one common goal. After pricing, the WBS continues to be a communications tool, documenting agreed performance and establishing criteria against which performance costs will be measured.
β Key Takeaways
The lecture establishes that effective pricing and estimation for projects require a disciplined, structured approach rather than relying on intuition or unreliable intelligence. The choice of pricing strategy depends on whether the project is a one-time opportunity (Type I, profit-driven) or a market entry point (Type II, market-share-driven). Project managers must understand the four key types of estimates (order-of-magnitude, approximate, definitive, and learning curves), as each provides a different level of accuracy for different stages of a project. The pricing-out of the Work Breakdown Structure is the central mechanism for integrating functional and program management, turning the WBS into a vital communications and control tool. Finally, the pricing process is not a last-minute activity; it must begin early with preliminary requirements and cost targets to allow for effective design and decision-making.
π§ Quick Revision Questions
- What are the four types of precedence constraints used in computerized project management software, and how does each define the relationship between activities?
- What is the fundamental difference between a Type I and a Type II pricing strategy, and what distinguishes the basis for determining the bid price in each?
- Name the three main types of estimates discussed in the lecture and list their respective accuracy ranges (Β± percentages).
- How does the pricing-out of the Work Breakdown Structure (WBS) serve to bridge the gap between functional management and program management?
- What is a "cost estimating relationship" (CER), and what are four examples of typical CERs?
π Lecture 32 β Pricing and Estimation (Contd.)
π Overview: This lecture continues the discussion on pricing and estimation in project management, focusing on how organizations provide input for pricing, how labor distributions are managed, and how overhead costs are calculated and controlled. Understanding these processes is critical for accurate project budgeting, cost control, and competitive bidding.
ποΈ Topics Covered
The lecture covers three main areas: organizational input requirements for pricing, including the kickoff meeting and proposal timelines; labor distributions, detailing how man-hours are submitted, converted to dollars, and the dynamics between functional and program managers; and overhead rates, explaining how they are calculated, applied, and how they can impact project cost-effectiveness through examples and detailed elements of overhead expenses.
π Lecture Summary
32.1 Organizational Input Requirements:
Once the work breakdown structure and activity schedules are established, the program manager calls a meeting for all organizations required to submit pricing information. It is imperative that all pricing or labor-costing representatives be present for this "kickoff" meeting, where the work breakdown structure is described in depth so each pricing unit manager knows their responsibilities. The kickoff meeting also resolves power struggles between functional managers whose responsibilities may overlap, such as quality control during different program phases. One meeting is not always sufficient, so follow-up status meetings are held with concerned parties. Some companies have all members attend to keep everyone familiar with total effort and problems, while others have only a divisional representative attend to save time, though this can become a bottleneck if communication fails.
Time is extremely important during proposal activities. A Request for Proposal (RFP) often requires bids by a specific date, and the proposal manager's schedule has little flexibility. The RFP indirectly defines how much time pricing units have to identify and justify labor costs. Justification of labor costs may take longer than original estimates, especially without historical standards. Some proposals require comprehensive labor justification immediately, while others permit vendors to submit it later. Ultimately, it is the responsibility of the lowest pricing unit supervisors to maintain adequate standards for an immediate response to pricing requests.
π Definition β Kickoff Meeting: The first meeting where the program manager describes the work breakdown structure to all pricing unit managers so they know their exact responsibilities. π Example: Quality control activities: during Research & Development, research personnel perform their own quality control, but during production, the quality control department has overall responsibility.
32.2 Labor Distributions:
Functional units supply their input to the program office in the form of man-hours for each task, assuming the task is the lowest pricing element, and are time-phased per month. These man-hours are converted to dollars after multiplication by appropriate labor rates. Labor rates are generally known with certainty over twelve months but are estimates thereafter. If a company underestimates salary structures, increased costs and decreased profits occur; if overestimated, the company may not be competitive, or the salary structure becomes an item under contract negotiations for government-funded projects.
The development of labor rates for projection is based on historical costs in business base hours and dollars for the most recent month or quarter. Average hourly rates are determined for each labor unit by direct effort at the department level, including both highest-paid and lowest-paid employees, department manager, and clerical support. These base rates are then escalated as a percentage factor based on past experience, approved budget, local outlook, and similar industries.
Labor hours submitted by functional units are quite often overestimated for fear that management will "massage" and reduce them. Many times management reduces man-hours due to insufficient funding or to remain competitive, causing heated discussions between functional and program managers. The most common solution rests with the program manager: if they select team members knowledgeable in man-hour standards for each department, an atmosphere of trust can develop, allowing man-hours to be reduced in the company's best interests.
The man-hours submitted provide the basis for total program cost analysis and control. π Formula: Labor Cost = Man-hours Γ Labor Rate π Example 32.1: On May 15, Apex Manufacturing decided to bid for modifying an assembly line. A work breakdown structure was developed. On June 1, each pricing unit was given the WBS and schedule (Figure 32.2). All labor data must be submitted by June 15. During proposal activities, the proposal manager, pricing manager, and program manager must work together, though the program manager has the final say. After planning and pricing charts are approved by program team members and program managers, they are entered into an Electronic Data Processing (EDP) system. The computer prices hours using applicable department rates for preparing the direct budget time plan and estimate-at-completion reports. The direct budget time plan remains the same for the contract's life except for customer-directed changes or management-approved reductions (which cannot be increased without customer approval).
π‘ Why this matters: Time plans are monthly mechanical printouts of all planned effort by work package and organizational element, serving as the data bank for status completion reports. Initially, the estimate-at-completion report is identical to the budget report, but changes throughout the program's life to reflect performance degradation or improvement.
32.3 Overhead Rates:
Controlling program costs involves more than tracking labor dollars and hours. Overhead dollars can be a major headache and must be tracked along with labor. Although most programs have an assistant program manager for cost who performs monthly overhead rate analysis, the program manager can increase program success by ensuring each team member understands overhead rates. For example, if overhead rates apply only to the first 40 hours of work, program dollars can be saved by performing work on overtime where the increased salary has a lower burden.
π Definition β Overhead Rate: The indirect costs applied to direct labor, expressed as a percentage of direct labor dollars. π Formula: Total Cost = (Labor Hours Γ Hourly Rate Γ Overtime Multiplier) Γ (100% + Overhead Burden %) π Example 32.2: Apex Manufacturing needs 500 man-hours at $15.00/hour for a report. Regular shift overhead = 75%; overtime overhead = 5%. Overtime is paid at time and a half.
- Regular time: (500 hours Γ $15.00/hour) Γ (100% + 75%) = $13,125
- Overtime: (500 hours Γ $15.00/hour Γ 1.5) Γ (100% + 5%) = $11,812.50 The company saves $1,312.50 by performing work on overtime. This difference can be very large in manufacturing divisions with overhead rates between 300-450%.
Regardless of the project, all costs must have associated overhead rates. The preparation and assignment of overheads to each functional division is a science. While the total dollar pool for overhead rates is relatively constant, management decides how to distribute overhead among divisions. A company supporting Research & Development through competitive bidding may keep R&D overhead rates low, but other divisions may absorb additional costs and become uncompetitive.
The development of overhead rates depends on three elements: direct labor rates, direct business base projections, and projection of overhead expenses. Direct business base projection involves determining anticipated direct labor hours and dollars along with direct materials and other direct costs. Factors used include: actual costs to date and estimates to completion, proposal data, marketing intelligence, management goals, and past performance and trends.
Projection of overhead expenses is made by analyzing each element constituting overhead expense. A partial listing includes items from Table 32.1. Projection is based on: historical direct/indirect labor ratios, regression and correlation analysis, manpower requirements and turnover rates, changes in public laws, anticipated changes in company benefits, fixed costs in relation to capital asset requirements, changes in business base, Bid and proposal (B&P) tri-service agreements, and IR&D tri-service agreements. In aerospace and defense, the federal government funds a large percentage of B&P and IR&D activities to stimulate research and competition.
The annual budget is the prime factor in controlling overhead costs. This budget, resulting from CEO-established goals, is reviewed and approved at all management levels. It is established at the department level, and the department manager is responsible for identifying and controlling costs against the approved plan. Departmental budgets are summarized for higher management levels, who are made aware of authorized indirect budgets in their areas of responsibility.
π‘ Why this matters: Monthly reports indicate current month and year-to-date budget, actuals, and variances for each management level. Analysis is made by the budget department through coordination with management. Each directorate's total organization is reviewed with the assigned budget analyst, and a joint meeting is held with directors and the vice president/general manager to review overhead performance.
β Key Takeaways
This lecture emphasizes that accurate pricing and estimation require coordinated organizational input from kickoff meetings, careful management of labor distributions with realistic man-hour estimates, and thorough understanding of overhead rates to control total program costs. The critical skills include knowing how to calculate labor costs using appropriate rates, understanding when overtime can be cost-effective due to lower overhead burdens, and recognizing that overhead rate development involves analyzing direct labor rates, business base projections, and overhead expense elements. Students must remember that the program manager's ability to select knowledgeable team members can build trust and improve cost estimation, and that annual budgets and monthly variance reports are essential for overhead cost control.
π§ Quick Revision Questions
- What is the purpose of the kickoff meeting in organizational pricing, and what common problem does it resolve?
- How are man-hours from functional units converted into dollar costs, and what challenge arises when predicting labor rates beyond twelve months?
- In Example 32.2, why is overtime more cost-effective than regular time for the report, and what overhead rate difference makes this possible?
- What are the three elements upon which overhead rate development depends, and what factors are used for direct business base projection?
- How does the direct budget time plan differ from the estimate-at-completion report, and what conditions allow changes to the direct budget time plan?