Inventory Management
Operations Performance Objectives and Process Design
Interdependence of Design Activities:
Product and service design cannot be separated from process design; they are fundamentally interrelated and must be evaluated together.
Products and services must be designed so they can be produced effectively, while operational processes must be configured to produce all current and anticipated future products and services.

Operational Performance Objectives and Design Translations:
Quality: Focuses on providing appropriate process resources capable of consistently meeting product or service specifications, achieving error-free processing, and preventing defect propagation.
Speed: Aims to minimize throughput time (the duration between entering and exiting the process) while ensuring that the production output rate matches demand.
Dependability: Focuses on providing dependable, stable process resources that ensure reliable, predictable output timing and volume.
Flexibility: Requires resources with a broad range of capabilities and the ability to switch smoothly between processing states, including changes to what is processed (specification flexibility), how it is processed (route flexibility), and how much is processed (volume flexibility).
Cost: Ensures appropriate operational capacity to meet demand without incurring excess capital expenditure, while eliminating process waste such as:
Excess capacity.
Excess process capability beyond required specifications.
In-process delays and idle time.
In-process rework and errors.
Inappropriate or non-conforming process inputs.
Process Typologies in Manufacturing and Services
The Volume-Variety Continuum:
Operational processes are defined by the volume of output and the variety of items produced.
Low-volume, high-variety systems require diverse, complex, and intermittent process tasks.
High-volume, low-variety systems require standardized, repeated, divided, and continuous flows.
Manufacturing Process Types:
Project Processes:
Deal with highly customized, complex, large-scale, one-off products with high work content.
Exhibit low volume and high variety.
Feature a defined start and finish with strict time, quality, and cost constraints.
Require the coordination of diverse, highly specialized skills over long operational durations (e.g., civil construction, shipbuilding, large software rollouts).
Jobbing Processes:
Handle very small quantities (one-offs or very low volume) with high product variety.
Characterized by low repetition, where every item is tailored to customer specifications.
Rely on broad, multi-skilled craftspersons or teams who complete all or most of the product using general-purpose machinery (e.g., bespoke furniture makers, custom machine shops).
Batch Processes:
Produce higher volumes than jobbing processes with moderate product variety.
Output standard items on a repeating schedule while retaining the capacity to produce specialized variations.
Demand specialized, narrower worker skill sets compared to jobbing.
Require formal changeovers and machine set-ups between different production runs (e.g., commercial bakeries, garment manufacturing).
Mass (Line) Processes:
Produce high volumes of standardized, repeating goods ("runners").
Involve dedicated, highly synchronized assembly line machinery with low or near-instantaneous setup times.
Utilize work divided into short, repetitive cycles requiring narrow, low-to-medium operator skills (e.g., automotive assembly lines, consumer electronics manufacturing).
Continuous Processes:
Operate at extremely high volumes and virtually zero variety, typically producing a single standard, nondiscrete output.
Highly capital-intensive, automated, and continuous in physical flow.
Changeovers are rare, and stopping or starting the process involves significant cost, complexity, and downtime (e.g., petrochemical refineries, water treatment facilities, electricity generation).
Service Process Types:
Professional Services:
High-contact organizations where clients spend considerable time within the service delivery process.
Characterized by high customization, flexible processes, and substantial discretionary judgment exercised by front-line professionals.
People-based rather than equipment-based (e.g., management consultants, legal practices, specialized surgeons).
Service Shops:
Positioned at medium customer volumes, medium or mixed contact levels, moderate customization, and moderate staff discretion.
Service delivery combines front-office customer interaction with standardized back-office support systems (e.g., banks, commercial fitness centres, standard restaurants).
Mass Services:
Deliver high-volume, standardized services with low to moderate contact time per client.
Defined by low customization, limited staff discretion, strict procedures, and extensive reliance on automation, equipment, or physical infrastructure (e.g., supermarkets, retail mass transit systems, amusement parks).
The Product-Process Matrix and the Natural Diagonal:
The line of fit (or natural diagonal) matches volume-variety characteristics to process design:
High variety / low volume aligns with project, jobbing, and professional service environments.
High volume / low variety aligns with mass production, continuous flow, and mass services.
Deviating above the diagonal results in higher process flexibility than needed, leading to excessive capital and overhead costs.
Deviating below the diagonal results in insufficient process flexibility for the required variety, causing disruption, quality failures, and elevated operational costs.

Process Mapping, Lean Waste Analysis, and Layout Design
Purpose and Foundations of Process Mapping:
Disambiguates actual workflows from formal or imagined procedures.
Identifies value-adding tasks alongside non-value-adding waste.
Aids in designing simplified, reliable operational systems and evaluating alternative process architectures.
Provides a shared visual language for cross-functional stakeholders.
The Seven Lean Wastes (TIMWOOD):
Transport: Unnecessary movement of materials, parts, or tools between processes. Caused by poor facility layout, decentralized storage, and poor material flows. Leads to longer lead times, risk of product damage, and excess work-in-progress.
Inventory: Storing raw materials, work-in-progress, or finished goods that are not actively undergoing value transformation. Caused by over-forecasting, large batch processing, push production, and unreliable suppliers. Ties up operating capital, consumes floor space, increases storage and insurance costs, and hides quality defects.
Motion: Unnecessary physical movement by operators during execution (e.g., reaching, bending, searching). Caused by poorly organized workstations, lack of standardized work routines, and poor ergonomics. Results in worker fatigue, safety risks, and lost cycle time.
Waiting: Time that workers or materials spend idle between work steps. Caused by processing bottlenecks, unbalanced production lines, material shortages, and equipment downtime. Results in lost capacity and delayed delivery schedules.
Over-production: Producing output sooner, faster, or in greater quantities than required by customer demand. Driven by "just-in-case" mentalities, push scheduling, and oversized batch incentives. Compounds all other wastes by creating excess inventory, consuming warehouse capacity, and masking processing defects.
Over-processing: Performing work beyond customer requirements or technical specifications. Caused by outdated procedures, redundant inspections, and poor design guidelines. Consumes excess labor, equipment capacity, and utilities.
Defects: Producing scrap, rework, or non-conforming items that fail to satisfy quality criteria. Caused by operator error, out-of-control processes, inaccurate machine calibration, or substandard raw materials. Incurs direct material loss, extra inspection labor, and risks customer dissatisfaction.
Value Classifications:
Value-Adding (VA): Activities that transform material or information, are executed right the first time, and directly satisfy customer needs for which they are willing to pay.
Non-Value-Adding (NVA): Pure waste activities that consume resources without advancing the product or service; targets for elimination.
Necessary Non-Value-Adding (NNVA): Activities that do not add direct value to the end customer but are required by regulatory, legal, reporting, or technical constraints (e.g., accounting audits, mandatory safety compliance inspections).
Waste Reduction Principles:
Elimination: Completely removing redundant tasks, unnecessary checks, delays, and secondary transport legs.
Time Compression: Reducing duration through better tools, standardized work procedures, and simplified steps.
Concurrency: Running independent processing steps in parallel rather than sequentially to shorten total throughput time.
Process Mapping Symbology:
Scientific Management Symbols (ASME Standard):
Circle (): Operation (activity that directly modifies material, information, or customer state).
Arrow (): Transport (movement of materials, documents, or personnel between locations).
Square (): Inspection (verification of quality, volume, or specifications).
Half-Circle / "D" (): Delay (waiting or queueing for subsequent steps or resources).
Inverted Triangle (): Controlled Storage (deliberate retention in an authorized inventory or archive).
Systems Analysis Symbols:
Diamond: Decision junction representing conditional routing or discretionary judgment.
Solid Lines with Arrows: Direction of material or information flow.
Rounded Box / Pill: Beginning or end termination point of the process flow.

Customer Experience Mapping:
Maps emotional, cognitive, and physical touchpoints over time from the customer's perspective.
Evaluates differences between what management intends the customer to experience and what the customer actually experiences.
Case Study: Computerized Tomography (CT) Scan Visit:
Park Car: Intended to feel convenient and unhurried; actually generates frustration and anxiety over finding open parking.
Check-In: Intended to be welcoming and swift; actually creates mild confusion followed by relief at finding the check-in desk.
Wait: Intended to be comfortable and relaxed; actually causes anxiety regarding wait times and the upcoming procedure.
Scan: Intended to be quick and reassuring; patients generally find the process easier and less intimidating than feared.
Wait for Results: Intended to be an informed, structured wait; often generates heightened anxiety and confusion over processing delays.
Results Explained: Intended to deliver clarity; successfully reassures patients when medical professionals address specific questions directly.

Process Diagnostics and Systematic Questioning:
Four Process States:
What people say the process is (stated policy).
What they perceive it to be (individual assumptions).
What it actually is (empirically observed reality).
What it should be (the improved target state).
Primary Examination (Status Quo Investigation):
Purpose: What is achieved? Is it necessary?
Place: Where is it done? Why there?
Sequence: When is it done? Why then?
Person: Who does it? Why that person?
Means: How is it done? Why that way?
Secondary Examination (Generation of Improvements):
Purpose: What else could or should be done?
Place: Where else could it be done?
Sequence: When else could it be done?
Person: Who else could do it?
Means: How else could it be done?
Line Balancing, Cycle Time, and Balancing Loss:
Cycle Time (): The time between completions of consecutive units at a processing station, dictated by the bottleneck stage:
Balancing Loss (): The proportion of total capacity lost due to unequal work distribution across line stages:
Worked Numerical Example:
A four-stage assembly line has stage durations:
Cycle time is governed by the longest stage:
Total idle time per cycle:
Balancing loss calculation:

Layout Architectures: Long-Thin vs. Short-Fat:
Long-Thin Arrangement: Sequential layout where an item moves through many sequential, specialized workstations with short individual task durations.
High equipment utilization, simple routing, low individual work content, but susceptible to line balancing losses and bottleneck stoppages.
Short-Fat Arrangement: Parallel layout where an item is handled by fewer stations (or a single operator) performing a broader collection of tasks over longer cycle times.
Higher worker autonomy, robust against single-station breakdowns, flexible to changing product mixes, but requires wider worker skills and duplicate tooling.
Example (60-minute total work content, target cycle time = 15 minutes):
Long-Thin: Four sequential stations of each (yields 1 unit every ).
Intermediate: Two parallel lines of two stations ( each).
Short-Fat: Four parallel single-operator stations of each (yields 1 unit every collectively).

Inventory Fundamentals and Cost Structures
Definition of Inventory:
The stored accumulation of material resources, components, goods, or operational items used to support production, administrative tasks, or end customer delivery.
The Four Primary Types of Physical Inventory:
Raw Materials: Inputs purchased from external suppliers awaiting introduction into the transformation process.
Work-In-Progress (WIP): Semi-finished parts, subassemblies, and materials actively moving through processing stages.
Finished Goods: Completed products packaged and ready for distribution or sale to customers.
Maintenance, Repair, and Operating (MRO): Consumables, spare components, and tooling used to maintain plant machinery and support business operations.
Service and Manufacturing Inventory Analogues:
Hotel:
Physical Inventories: Food supplies, beverages, toiletries, linens.
Queues of Customers: Front desk lines at check-in and check-out.
Information in Databases: Guest reservation details, loyalty program accounts, supplier records.
Hospital:
Physical Inventories: Surgical dressings, disposable syringes, pharmaceuticals, donated blood units.
Queues of Customers: Outpatient waiting lists, admitted patients waiting for operating rooms, recovering patients in post-op wards.
Information in Databases: Electronic health records, surgical schedules, pathology records.
Credit Card Processing Center:
Physical Inventories: Blank plastic cards, printed statement stock, envelopes.
Queues of Customers: Callers holding on customer service telephone lines.
Information in Databases: Credit histories, personal records, identity verification data.
Computer Manufacturer:
Physical Inventories: Microprocessors, memory modules, chassis, completed laptops ready for shipment.
Queues of Customers: Orders queued in the production backlog awaiting assembly.
Information in Databases: Component inventory levels, shipping tracking databases, customer purchase histories.
Strategic Reasons for Holding Inventory:
Buffers against unexpected fluctuations in customer demand or supplier replenishment delays.
Decouples sequential processes, allowing separate steps to run at different production rates.
Allows operations to take advantage of bulk purchasing discounts.
Hedges against expected inflation, supplier shortages, or upward price fluctuations.
Smoothes seasonal demand variations, enabling level production schedules.
Reduces customer delivery lead times.
The Structure of Inventory Costs:
Holding (Carrying) Costs (): The expense of maintaining items in inventory over time. Typically expressed as an annual cost per unit () or as a percentage of unit cost.
Ordering / Setup Costs (): The fixed administrative, clerical, handling, and transportation expenses incurred each time a purchase order or factory setup is initiated, regardless of order size.
Shortage / Stock-Out Costs: Costs incurred when inventory is insufficient to satisfy demand, including lost profits, contract default penalties, expedited freight costs, and damaged customer goodwill.
The Inventory Iceberg Model:
While managers often focus primarily on direct capital interest expenses, significant carrying costs remain hidden below the surface.
Total inventory carrying costs typically reach approximately of total inventory value annually:
Cost of Money (Financing / Interest):
Storage and Warehousing Facilities:
Taxes:
Obsolescence:
Shrinkage (Theft / Pilferage):
Insurance:
Total Annual Carrying Cost:

Deterministic Inventory Models: Economic Order Quantity (EOQ) and Quantity Discounts
Inventory Level Profiles:
Under steady, predictable demand, inventory levels decline linearly over time.
Replenishment is instantaneous, producing a characteristic "sawtooth" profile.
For an order quantity of units, the average physical inventory level is:
Number of orders placed per period:
Cycle duration between order receipts:

Comparison of Inventory Plans:
For annual demand :
Plan A (): Average inventory = ; order cycle = ; orders per year = .
Plan B (): Average inventory = ; order cycle = ; orders per year = .

Basic Economic Order Quantity (EOQ) Assumptions:
Demand () is continuous, known, and constant over time.
The inventory policy covers a single product.
Supplier replenishment lead time () is constant and known.
Entire order quantity () arrives instantaneously in a single batch.
No shortages or stockouts are permitted.
The holding cost rate () is constant and proportional to average stock.
The fixed order cost () is constant and independent of the order size.
Planning horizon is infinite, and no space or budget constraints apply.
EOQ Mathematical Derivation:
Annual Holding Cost:
Annual Ordering Cost:
Total Annual Cost ():
Differentiating with respect to and setting the derivative to zero:
At the optimal batch size , annual holding costs equal annual ordering costs.

Comprehensive Numerical Example:
Parameters: Annual demand , order cost , annual holding cost .
Analytical solution:
Orders per year:
Total cost breakdown table:
Order Quantity () | Number of Orders () | Annual Order Cost () | Annual Storage Cost () | Total Annual Cost () |
|---|---|---|---|---|
EOQ Model with All-Units Quantity Discounts:
When suppliers offer discounted item purchase prices () for larger volumes, total annual cost must include purchasing costs:
Decision Procedure for Quantity Discounts:
Calculate using the standard EOQ formula.
If the unadjusted falls in the highest discount bracket, it is feasible and optimal.
If not, calculate the total annual cost at and compare it against the total costs evaluated at the minimum quantity breakpoints of all higher discount tiers.
Select the order quantity that yields the lowest total annual cost.
Numerical Discount Application:
Using , , :
Tier 1: for
Tier 2: for
Tier 3: for
Base unadjusted EOQ is , which falls within Tier 2 ().
Evaluate total cost at :
Evaluate total cost at the next price breakpoint (, qualifying for ):
Conclusion: The company should order , saving per year.
Re-Order Level (ROL) and Re-Order Point (ROP):
Under deterministic conditions, the re-order point is the stock level at which a new order must be placed to arrive exactly as inventory reaches zero:
For example, with demand and lead time , the order must be placed when stock reaches .

Inventory Control and ABC Classification Analysis
Pareto Principle in Inventory Management:
Inventory items do not carry equal financial importance; control should focus on the critical few rather than the trivial many.
Class A Items: Approximately of all SKU line items account for roughly of total Annual Monetary Volume (AMV).
Class B Items: Approximately of SKU line items account for roughly of total AMV.
Class C Items: Approximately of SKU line items account for roughly of total AMV.

Step-by-Step Procedure for ABC Analysis:
Obtain annual demand () and unit purchase cost () for each inventory item .
Calculate Annual Monetary Volume for each item:
Sum all individual values to find total AMV:
Sort all SKUs in descending order of .
Calculate each SKU's percentage contribution to total AMV:
Compute cumulative percentages across the ranked items.
Assign items to categories A, B, or C based on their cumulative contribution.
Complete 10-SKU Numerical Analysis:
Total Annual Monetary Volume: .
Item SKU | Annual Demand | Unit Cost () | Annual Monetary Volume () | Percent of AMV () | Cumulative AMV () | ABC Category |
|---|---|---|---|---|---|---|
#14567 | A | |||||
#61718 | A | |||||
#36778 | B | |||||
#92001 | B | |||||
#43753 | C | |||||
#47349 | C | |||||
#73292 | C | |||||
#81924 | C | |||||
#83293 | C | |||||
#83295 | C |
Managerial Policies Driven by ABC Classification:
Category A Items:
Apply tight control, continuous review, and secure storage to prevent theft and shrinkage.
Use sophisticated demand forecasting and conduct regular cycle counts.
Focus supplier relationship management and contract development on these high-value items.
Category B Items:
Use periodic review cycles, standard order control routines, and moderate buffer stocks.
Category C Items:
Keep ordering simple (e.g., two-bin systems), use large batch sizes to reduce administrative overhead, maintain generous safety stocks, and perform physical audits infrequently.
Alternative Classification Criteria: Beyond monetary volume, items may be elevated to Class A based on high risk of stockouts, long supplier lead times, rapid technical obsolescence, or strict storage requirements.
Fundamentals of Project Management and Scope Definition
Core Definition and Properties of Projects:
A project is a temporary endeavor undertaken to create a unique product, service, or result.
Characterized by finite lifespans, defined start and end dates, non-routine tasks, budget constraints, and dedicated cross-functional teams.
Process Management versus Project Management:
| Dimension | Process Management | Project Management | | :--- | :--- | :--- | :--- | | Output | Repeating standard product or service | Unique, one-off deliverable | | Objectives | Continuous optimization across several metrics | Single primary objective (triple constraint) | | Lifespan | Ongoing, indefinite life | Temporary, defined endpoint | | Personnel | Homogeneous teams, stable reporting lines | Heterogeneous, multi-disciplinary teams | | Operating Context| Established operating practices, high certainty | Novel systems, higher uncertainty | | Culture | Supports the organizational status quo | Challenges and changes the status quo |
The Four Phases of the Project Life Cycle:
Conceptualization: Recognize organizational needs, establish technical parameters, identify primary stakeholders, and establish initial feasibility.
Planning: Develop work specifications, detailed activity network diagrams, baseline budgets, and staffing plans.
Execution: Carry out planned work packages, allocate the majority of resources, and monitor operational performance.
Termination: Hand over deliverables to the client, reassign staff and resources, resolve contracts, and perform post-project audits.
Over the project lifecycle, uncertainty declines steadily as knowledge increases, while financial stakes and cumulative expenditures rise through planning and execution before tapering off at project close.
Criteria for Project Success:
The Iron Triangle: Meeting Cost (Budget envelope), Time (Schedule milestones), and Quality (Performance/technical specifications).
Broader Value Dimensions: Client acceptance, commercial viability, organizational learning, and future preparedness.
Scope Management and Conceptual Development:
Scope encompasses all project work required to deliver specified outcomes.
Steps in Conceptual Development: Problem/need statement formulation, requirements gathering, information gathering, constraint identification, alternative analysis, objective definition, and business case justification.
Core Project Scope and Governance Documents:
Statement of Work (SOW): Detailed narrative detailing the work required, project context, deliverables schedule, and technical criteria.
Project Charter: Formal authorization issued by executive sponsors that officially sanctions the project and gives the project manager authority to apply resources.
Scope Statement: Defines baseline boundaries, key deliverables, milestone gates, resource estimates, and performance metrics.
Work Breakdown Structure (WBS) and Organizational Linkages:
WBS: Hierarchical decomposition of total project scope into manageable, trackable components.
Work Package: The lowest level of the WBS. Represents an independent, assignable unit of work with a single owner, defined budget, clear milestone deliverables, and short duration.
Organizational Breakdown Structure (OBS): Integrates work packages with functional departments, linking activities and budgets directly to organizational units.
Scope Change Control, Configuration Management, and Closeout:
Configuration Management: Formal procedures used to document physical and functional attributes, evaluate change requests, approve adjustments, and audit conformance.
Baseline: The approved scope, schedule, and cost plan established at a specific milestone against which progress is measured.
Causes of Scope Changes: Planning errors, emergence of new environmental conditions, regulatory mandates, and client change requests.
Closeout Documentation: Maintaining historical archives, conducting post-project performance reviews, completing financial accounting, and recording lessons learned.
Project Scheduling: Network Logic and Critical Path Method (CPM)
Project Scheduling Terminology:
Project Network Diagram: A graphical diagram showing the logical sequence and dependencies of project activities.
Path: A continuous sequence of connected activities through the network from start to finish.
Node: An intersection or junction point in the network representing an activity (in Activity-on-Node systems) or an event.
Event: An instantaneous point in time marking the start or completion of a task.
Predecessor: An activity that must be completed before a subsequent activity can begin.
Successor: An activity that cannot begin until its immediate predecessor is completed.
Early Start (): The earliest time an uncompleted activity can begin based on network logic.
Early Finish (): The earliest time an activity can finish:
Late Finish (): The latest time an activity can finish without delaying the overall project completion date.
Late Start (): The latest time an activity can begin without delaying project completion:
Forward Pass: Working forward through the network from left to right to calculate and for each activity.
Backward Pass: Working backward through the network from right to left to calculate and for each activity.
Merge Activity: A node with two or more immediate predecessor activities.
Burst Activity: A node with two or more immediate successor activities.
Float (Slack): The time an activity can be delayed without delaying the completion of the project:
Critical Path: The continuous path from start to finish with the longest duration. Activities on this path have zero slack, and any delay to them directly delays the final project completion date.
Activity-on-Node (AON) Architecture:
Each activity is represented by a rectangular node divided into standardized tracking cells.

Forward and Backward Pass Decision Rules:
Forward Pass (Left to Right):
For activities with no predecessors: .
Calculate early finish: .
At a merge node, the early start is the maximum early finish of its predecessors:
Backward Pass (Right to Left):
For the terminal node: Set .
Calculate late start: .
At a burst node, the late finish is the minimum late start of its successors:
Full 10-Activity Project Planning Case Study:
Activity data table:
Activity | Preceding Tasks | Duration () |
|---|---|---|
A | — | |
B | A | |
C | A | |
D | C | |
E | A | |
F | E | |
G | E | |
H | F, G | |
I | H, D | |
J | B, I |
Network Step-by-Step Calculations:
Activity A: , .
Activity B: , .
Activity C: , .
Activity D: , .
Activity E: , .
Activity F: , .
Activity G: , .
Activity H (Merge: F, G): , .
Activity I (Merge: H, D): , .
Activity J (Merge: B, I): , .
Normal Project Duration = .
Backward Pass:
Activity J: , .
Activity I: , .
Activity B: , .
Activity H: , .
Activity D: , .
Activity C: , .
Activity F: , .
Activity G: , .
Activity E: , .
Activity A: , .
Activity Slack and Critical Path Identification:
Activity | Slack () | Critical Status | ||||
|---|---|---|---|---|---|---|
A | Critical | |||||
B | Non-Critical | |||||
C | Non-Critical | |||||
D | Non-Critical | |||||
E | Critical | |||||
F | Critical | |||||
G | Non-Critical | |||||
H | Critical | |||||
I | Critical | |||||
J | Critical |
Critical Path:
Total Duration: .

Critical Path Analysis Pros and Cons:
Advantages: Highlights tasks that cannot slip, identifies schedule float, prevents misallocation of capital, and enforces sequential logic.
Disadvantages: Dependent on initial duration estimates, does not guarantee execution success on its own, and requires computerized tools for complex project networks.
Project Crashing, Fast-Tracking, and Time-Cost Trade-Offs
Definitions of Project Acceleration Techniques:
Crashing: Shortening specific activity durations by adding resources (e.g., overtime, additional staff, specialized equipment), typically incurring direct costs.
Fast-Tracking: Rescheduling sequential activities to run in parallel. Increases project risk, site congestion, and coordination complexity without necessarily adding direct labor costs.
Strategic Drivers for Crashing:
Avoiding late-completion contract penalties (liquidated damages) that exceed acceleration costs.
Meeting early client delivery requests or critical market windows.
Freeing organizational resources early for higher-return initiatives.
Cost Slope Formula:
The marginal direct cost incurred per unit of time saved by expediting an activity:
The Core Rules of Project Crashing:
Only shortening activities on the current critical path reduces overall project duration.
Always select the critical path activity with the lowest cost slope.
Recalculate durations across all network paths after every crashing step.
Stop crashing an activity once it reaches its minimum crash time limit.
If multiple parallel critical paths emerge, shorten all critical paths simultaneously by either crashing a shared critical activity or crashing one activity on each path.

Complete 6-Activity Crashing Case Study:
Activity data:
Activity | Predecessors | Normal Time () | Crash Time () | Normal Cost () | Crash Cost () | Max Crash Days | Cost Slope () |
|---|---|---|---|---|---|---|---|
A | — | ||||||
B | A | ||||||
C | A | ||||||
D | B | ||||||
E | C | ||||||
F | D, E |
Initial Path Durations:
Path 1 (): .
Path 2 (): .
Initial Critical Path: Path 1 ().
Step-by-Step Crashing Sequence:
Stage 1 (Crash A by 1 day):
Critical path cost slopes: , , , .
Activity A is the cheapest option and is shared by both paths.
Duration of A drops from to .
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Stage 2 (Crash A by second day):
Duration of A drops from to (A reaches its crash limit).
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Stage 3 (Crash B by 1 day):
Lowest eligible cost slope on critical path is B ().
Duration of B drops from to .
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Stage 4 (Crash B by second day):
Duration of B drops from to .
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Stage 5 (Crash B by third day):
Duration of B drops from to (B reaches its crash limit).
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Stage 6 (Crash F by 1 day):
Available critical activities: F () and D (). F is cheaper.
Duration of F drops from to (F reaches its crash limit).
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Stage 7 (Crash D by 1 day):
Only remaining critical activity on Path 1 is D ().
Duration of D drops from to .
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Milestone: Both paths now have equal duration (); two critical paths exist.
Stage 8 (Crash D on Path 1 and C on Path 2 simultaneously):
Shortening only Path 1 will not reduce total project duration.
Path 1 can crash D by 1 final day at .
Path 2 can crash C () or E (). C is the cheapest option.
Crash D by 1 day and C by 1 day in tandem.
Duration of D drops from to (D reaches crash limit).
Duration of C drops from to (C reaches crash limit).
Path 1 = , Path 2 = . Project duration = .
Added cost = , Cumulative crash cost = .
Crash Limit: Path 1 has no further crashable tasks. Absolute minimum project duration is .
Final Project Crashing Schedule Summary:
Stage | Activity Crashed | Project Duration () | Added Cost () | Cumulative Crashing Cost () |
|---|---|---|---|---|
Normal | — | |||
1 | A | |||
2 | A | |||
3 | B | |||
4 | B | |||
5 | B | |||
6 | F | |||
7 | D | |||
8 | D + C |
Total time saved: ().
Total direct crashing cost: .
Gantt Charts in Project Scheduling:
Provide a clear, bar-chart view of schedule milestones and activity durations over time.
Define the schedule baseline, track percentage completions against target dates, display resource assignments, and visualize dependency lag relationships.
