Operations Management

Need for Six Sigma

Six Sigma is a mechanism to deliver near zero defects in operations by applying process control principles. A defect is any unacceptable state of a product or service from a customer’s perspective. At Six Sigma quality levels, defects become extraordinarily rare – e.g., a few defects per million units produced or per million service opportunities.

Why 99% quality is not enough
Two examples illustrate the tangible impact of seemingly high quality levels.

Example 1: Five-star hotel at 99% quality

Process	Consequence of 99% quality
Guest checkout	1 guest leaves without paying every 3 days
Facilities upkeep	15 tables have soiled linen daily
Training & development	250 plates broken every day
Order taking & delivery	40 guests’ drinks mixed up daily
Laundry	20 guests receive wrong laundry daily

Example 2: Insurance firm

Customer segment	Policies issued	Error rate	Defects
Business	247,010	0.5%	~1,235
Retail	2,520,874	1.1%	~27,730
Total	2,767,884	~1.05%	28,965

28,965 defects per year – hardly acceptable. Quality levels must far exceed 99–99.5%.

Why high quality reduces total cost
A superior quality management system leads to fewer disruptions, smoother output, less rework, higher quality finished goods, and lower indirect costs (inspection, correction). Net effects: lower inventory, higher productivity, less labour, and lower overall cost – contradicting the old belief that quality improvements are uneconomical.

Exam tip: The shift from “quality costs more” to “quality costs less” is a foundational insight of modern quality management.

Measurement Metrics for Six Sigma Quality

Traditional metrics (AQL, AOQL) are based on percentages and inadequate for near-zero defect targets. Six Sigma uses two equivalent metrics:

• Parts Per Million (PPM) – defects per million units produced (manufacturing).
• Defects Per Million Opportunities (DPMO) – defects per million defect opportunities (services).

DPMO formula
Let

• $K$ = number of opportunities for a defect per unit of process execution
• $n$ = number of units observed
• $d$ = number of defects observed

$$\text{DPMO} = \frac{d}{n \times K} \times 1{,}000{,}000$$

Worked example – hotel check-in process

• $K = 11$ (e.g., wrong name, missing details)
• $n = 1{,}250$ guests handled
• $d = 357$ defects observed

$$\text{DPMO} = \frac{357}{1{,}250 \times 11} \times 1{,}000{,}000 = \frac{357}{13{,}750} \times 1{,}000{,}000 \approx 25{,}964$$

Premises of Six Sigma Quality

To achieve PPM/DPMO levels, quality management must rest on four premises:

1. Continuous and data-driven – not a one-time event.
2. Prevention and elimination, not detection and correction.
3. Performance standard is zero defects (practically, near-zero).
4. Primary responsibility lies with those who produce and deliver (not with a separate quality control department).

DMAIC Methodology

The Six Sigma program provides a structured, five-phase improvement cycle:

flowchart LR
    D[Define] --> M[Measure]
    M --> A[Analyze]
    A --> I[Improve]
    I --> C[Control]
    C -.->|Continuous cycle| D

• Define – scope, project charter, goals.
• Measure – identify variables, data collection, baseline metrics.
• Analyze – graphical tools, identify variation sources, vital few root causes.
• Improve – generate and validate alternatives, new process maps.
• Control – control plan, revised standards, training, prevent backsliding.

Organizational Structure for Six Sigma

Sustainable improvement requires clear ownership, mandate, and support. Key roles:

Role	Description
Process owner	Supervisor/manager responsible for process steps.
Team leader / members	Employees with day-to-day operational control; drive improvements.
Master Black Belt	Highest expertise – trains and coaches Black Belts.
Black Belt	Full-time project leader; deep knowledge of tools.
Green Belt	Part-time project member; works under Black Belt.
Six Sigma coach	Expert (internal/external) in statistics, process design, change management.
Sponsor / champion	Senior management – approves projects, provides resources, resolves cross‑organisational issues.

Exam tip: Know the hierarchy: Sponsor -> Master Black Belt -> Black Belt -> Green Belt. The process owner is often the person whose area is being improved.

Key takeaways

• Six Sigma aims for near-zero defects, measured in PPM or DPMO.
• 99% quality is unacceptable – demonstrated with hotel and insurance examples.
• Higher quality reduces total cost via fewer disruptions and lower waste.
• DPMO = (defects) / (units × opportunities per unit) × 1,000,000.
• DMAIC (Define–Measure–Analyze–Improve–Control) is the core improvement cycle.
• A dedicated structure (process owner, belts, coach, sponsor) ensures ownership and sustainability.

Quality Gurus and their Teachings

The modern quality movement did not arise from a single insight. Instead, several thinkers – quality gurus – reshaped how organizations view defects, management’s role, and the tools needed for sustained improvement. Their combined teachings form the foundation of contemporary quality assurance.

The Major Gurus and Their Core Contributions

Guru	Key Ideas	Practical Contribution
W. Edwards Deming	Top management must lead quality; PDCA cycle (Plan–Do–Check–Act); 14-point agenda for quality improvement.	Father of Japanese quality management; Japan’s Deming Award is named after him.
Joseph Juran	Quality Trilogy: (1) Quality planning – setting goals, (2) Quality control – using statistical tools during operations, (3) Quality improvement – systematic breakthroughs to unprecedented performance.	Provides a three-part framework for any quality program.
Philip Crosby	Five Absolutes of Quality: (1) definition is conformance to standards, (2) system is prevention, (3) performance standard is zero defects, (4) measurement is price of non-conformance, (5) there is no such thing as a quality problem – only a mindset shift.	Introduced explicit zero-defects target and a quality costing system.
Kaoru Ishikawa	Cause-and-effect diagram (fishbone diagram) for root-cause analysis; CEDAC (Cause-and-Effect Diagram with Action Cards).	Simple visual tool that operational teams can use to trace problems.
Shigeo Shingo	Poka-yoke (mistake-proofing / fool-proofing).	Eliminates defects by designing processes that make errors impossible.
Genichi Taguchi	Loss function – any deviation from target creates a loss; emphasis on design of experiments to hit the target precisely.	Moves quality focus from inspection to robust design.

Four Overarching Prescriptions from the Gurus

1. New definitions of quality – e.g., conformance to standards, target-driven performance.
2. New methods to build quality in – prevention, mistake-proofing, robust design.
3. New tools to assess performance – control charts, cause-and-effect diagrams, quality costing.
4. Changed roles for managers – from control to facilitation; middle managers become enablers, not inspectors.

Exam tip: The gurus are often tested by matching the person to the concept (e.g., “Who introduced zero defects?” → Crosby; “Who developed the Quality Trilogy?” → Juran). Know the pairings cold.

Key takeaways

• Deming: top management leadership + PDCA + 14 points.
• Juran: Trilogy (planning, control, improvement).
• Crosby: five absolutes, zero defects, prevention.
• Ishikawa: fishbone diagram, CEDAC.
• Shingo: poka-yoke (mistake-proofing).
• Taguchi: loss function, design of experiments.
• Four broad directions: alternative definitions, build-in methods, assessment tools, facilitation roles.

---

Total Quality Management (TQM)

TQM is an organization-wide mechanism, backed by top management mandate, to systematically and sustainably solve problems. (Contrast with JIT, which exposes problems; TQM solves them.)

The Four Pillars of TQM

flowchart TD
    A[Quality System<br>documentation, ISO, continuous learning] --> B[Top Management Commitment]
    A --> C[Employee Involvement & Training]
    A --> D[Tools & Techniques]
    B --> E[“Total” = Everyone, Everywhere, Every Time]
    C --> E
    D --> E

• Top management commitment: Lead by example; signal quality’s importance at every opportunity; help middle management resolve short-term vs. long-term trade-offs (e.g., temporary production loss for lasting improvement).
• Employee involvement: Build a culture of process ownership; train staff in simple tools; foster teamwork; implement project-by-project continuous improvement (structured, not ad hoc).
• Tools and techniques: Provide operational personnel with data-driven methods to identify, analyze, and solve problems.
• Quality system: A systematic way to capture and report quality issues – documentation, learning, and certification (e.g., ISO).

The “Total” in TQM: Three Dimensions

• Everyone – every employee participates.
• Everywhere – all functions and locations.
• Every time – continuous, not one-off.

Components of a Robust Quality Assurance System

1. Top management commitment to quality.
2. Mechanisms to understand customer needs.
3. Translation of needs into measurable operating targets.
4. Mechanisms to identify quality problems.
5. A set of tools and techniques for employees (root-cause tracking, corrective actions).
6. Employee involvement driving continuous improvement.
7. Methods for preventing recurrence of problems.
8. Documentation of all initiatives for learning.
9. Quality certification and benchmarking (e.g., ISO).

Exam tip: The contrast between JIT (“expose problems”) and TQM (“solve problems”) is a frequent short-answer question. Also remember that TQM requires mandate and top management support.

Key takeaways

• TQM = systematic, sustainable problem-solving across the whole organization.
• Four pillars: top management, employee involvement, tools, quality system.
• “Total” = everyone, everywhere, every time.
• Top management leads, signals, and resolves trade-offs.
• Employee involvement requires process ownership, training, teamwork, and structured projects.
• Quality system = documentation + certification (ISO).

---

Tools for Quality Management in Operations – Part I

Quality tools serve two overarching purposes:

1. Ensure data-based decisions – no quality initiative without measurement.
2. Engage operational personnel – tools empower frontline workers to participate.

Two Categories of Tools

Purpose of Use	Category	Examples
Highlighting problems	Quality control at operations	Control charts
Identifying improvement opportunities	Quality control at operations	Data-collection tools, plots, charts that reveal patterns
Analyzing problems and root causes	Operations level	Cause-and-effect diagram (fishbone diagram), CEDAC
Analyzing problems and root causes	Planning / higher level	Affinity diagram, relationship diagram
Building quality into products/services	Quality planning and design	Tree diagram, metrics diagram, metrics data analysis, poka-yoke
Strategic quality planning	Quality planning and design	Quality Function Deployment (QFD), quality costing

• Quality at operations tools are used by frontline teams to spot issues, analyze causes, and drive day-to-day improvements.
• Quality planning and design tools are used during product/service development and for strategic alignment (e.g., translating customer needs into design targets, quantifying the cost of quality).

Key takeaways

• Two roles of tools: ensure data-driven action and involve operational staff.
• Category 1 – operations: control charts, fishbone, CEDAC, and general data plotting.
• Category 2 – planning/design: tree diagrams, poka-yoke, QFD, quality costing.
• Root-cause analysis can be done at operations level (fishbone) or planning level (affinity/relationship diagrams).

Operational Tools

Histogram and Pareto Diagram

A histogram is a bar chart of frequency of occurrence. It gives an immediate visual sense of which problems occur most often.
Example: In an earth-moving equipment manufacturer, data collected over a month showed frequencies of quality issues:

Issue	Occurrences
Reworks	26
Leakage-related adjustments	24
Missing parts	24
(Other issues)	…

A Pareto diagram reorders the histogram bars in descending order and adds a cumulative percentage line (in blue). This makes the vital few stand out. In the example, the first three categories together contributed ~85% of all problems.
A deeper rework analysis revealed:

Rework cause	Occurrences
Design-related issues	33
Lack of drawing clarity	23
(Other)	…

Exam tip: The Pareto principle (80/20 rule) is embedded here: focus on the tall bars first to achieve the largest improvement with the least effort.

Cause-and-Effect (Fishbone) Diagram

Also called Ishikawa diagram or fishbone diagram. The effect (the quality problem) is placed at the right end of a horizontal arrow. Bones (branches) represent major cause categories — typically methods, men, machines, materials (or process, equipment, labour). Sub-causes branch off each bone.

Example: Head breakage of a screw.

• Material: less grade, hardness variation
• Method: less strength due to thread runout not provided or specification missing
• Machines and Men also had sub-causes.

The diagram is built through group brainstorming.

CEDAC (Cause-and-Effect Diagram with Addition of Cards)

A variation of the fishbone diagram. Instead of a fixed group, an open board is used with two sets of blank cards: problem cards and solution cards. Any employee can contribute, tapping the expertise of the entire workforce. Kaoru Ishikawa proposed both the fishbone and CEDAC.

Key takeaways – Operational Tools

• Histograms display frequency; Pareto diagrams sort frequencies descending with cumulative line to highlight vital few.
• Cause-and-effect diagrams systematically organize potential causes under major categories.
• CEDAC opens problem-solving to all employees via cards.
• These tools improve visibility of quality problems, fuel imagination, and motivate thinking about causes and solutions.

---

Design and Planning Tools

Poka‑Yoke (Mistake‑Proofing)

Poka‑Yoke is a Japanese term meaning fool-proofing or mistake-proofing. Its premise: many defects are avoidable; errors and defects have cause–effect relationships, so removing the cause eliminates the defect. A product or process is modified so that errors cannot occur or are detected immediately.

Examples:

• SIM card, pen drive, RAM: shaped asymmetrically so they cannot be inserted wrongly.
• Radial drilling machine: Two sensors and a contact lever ensure a through‑hole is always drilled. The lever must touch the lower sensor before the wheel can be retracted upward. A counter automatically increments each time the lever touches the lower sensor; when it reaches 100 pieces, the batch is sent to the next process—improving both quality and productivity.

Matrix Diagram

A two‑dimensional matrix used for strategic analysis. Dimensions:

• Importance of attributes: Order winning, Order qualifying, Less important
• Company performance relative to competition: Worse, Same, Better

Attributes are plotted to create zones:

• Excess zone: attribute is unimportant but company performance is better than competition.
• Critical zone (urgent action): attribute is highly important (order winning) but company performance is worse.
• Appropriate zone: middle ground.

Example from an earth-moving equipment manufacturer (10 attributes):

• Attribute A (product cost): order qualifying, worse → moderate priority.
• Attribute F (delivery reliability): order winning, worse → high priority (consistent with high lead times found in the study).

Quality Function Deployment (QFD) — House of Quality

QFD (also called House of Quality) links customer needs all the way to process plans through four stages. The first stage builds a “house” with these elements:

1. Customer requirements (the WHATs) — e.g., steaming hot food, easy to carry home, quick order processing.
2. Importance ratings for each requirement (e.g., steaming hot = very important).
3. Product characteristics (the HOWs) — e.g., temperature of cooked item, time to cook, order processing time, number of tables.
4. Relationship matrix — symbols (e.g., double plus, minus) indicate how strongly each characteristic affects each requirement.
5. Trade‑off matrix (the roof) — shows correlations between characteristics (positive or negative).
6. Competitive benchmarking — compares own company with competitors on each requirement.

A restaurant example:

• Steaming hot is strongly positively related to temperature and cooking time.
• Quick order processing is negatively related to cooking time (longer cooking hurts speed).
• Order processing time is negatively correlated with number of service counters during peak time.

The output of the first house becomes the input to the second house, and so on, until customer needs drive the final process plan.

Key takeaways – Design and Planning Tools

• Poka‑Yoke prevents errors by design; examples include shaped slots and sensor‑controlled machines.
• Matrix diagram prioritizes improvement actions by plotting attribute importance vs. company performance.
• QFD (House of Quality) systematically translates customer requirements into product/process characteristics, capturing trade‑offs and competitive benchmarks.
• All these tools support the DMAIC methodology for continuous improvement.

Statistical Process Control Fundamentals

Statistical Process Control (SPC) is a set of tools and techniques to systematically analyze process variations and distinguish between harmless random noise and signals of real problems. The core question is not whether variation exists — it always does — but whether we can make meaningful sense of it.

Two Types of Process Variation

All business processes exhibit variation. The critical task is to classify it:

Type	Name	Nature	Examples	Action
Common causes	Chance variation	Random, uncontrollable, inherent to the process	Ambient temperature, humidity, normal wear and tear	Accept as part of normal process; rarely can be eliminated
Assignable causes	Non‑random variation	Specific, traceable, often correctable	Operator skill differences, equipment change, new procedure	Investigate and correct to bring process back under control

Exam tip: The goal of SPC is to detect when assignable causes have shifted the process, not to eliminate common cause variation. A process affected only by common causes is said to be in statistical control.

---

Voice of the Customer – Specifications

Customer requirements define acceptable limits. These are expressed as:

• Target: the ideal value the customer desires (center of the specification).
• Upper Specification Limit (USL) and Lower Specification Limit (LSL): the maximum and minimum acceptable values.
• Tolerance: the allowable range, $\text{Tolerance} = \text{USL} - \text{LSL}$.

Example 1 – Service (Hotel checkout time)
Target = 90 s, tolerance ±20 s → USL = 110 s, LSL = 70 s, tolerance = 40 s.

Example 2 – Manufacturing (Pen diameter)
Target = 8 mm, tolerance ±0.5 mm → USL = 8.5 mm, LSL = 7.5 mm, tolerance = 1 mm.

---

Voice of the Process – Control Limits

The process itself has its own natural behavior, described by:

• Process average (center of process distribution).
• Upper Control Limit (UCL) and Lower Control Limit (LCL), set at ±3 standard deviations from the process average.
• Spread: $\text{UCL} - \text{LCL}$, the range of natural process variation.

Control limits are not specification limits – they reflect what the process actually does, not what the customer wants.

---

How to Measure Process Quality

Before launching an SPC program, decide what to measure and how. Two fundamental measurement approaches:

Feature	Attribute‑based	Variable‑based
What is measured	Count of items classified as good/bad or number of defects	Actual numerical value of a characteristic (e.g., time, length, weight)
Example	7% of patients admitted after 26 min (defect rate)	Admission times: 24.95 min, 21.87 min, …
Cost & effort	Quick, cheap, easy	More time‑consuming, detailed, expensive
Information revealed	Little – only proportion defective	Rich – average, standard deviation, distribution shape
Use when	High‑level monitoring needed, many items	Detailed process understanding required

Choosing the measurement method determines which control chart to use later.

---

The Statistical Basis of Control Charts

The foundation is the normal distribution and the empirical rule:

$P(\mu - 3\sigma \leq X \leq \mu + 3\sigma) \approx 0.9973$

• Observations falling within ±3σ almost certainly (99.73 %) arise from common causes (random variation).
• An observation outside ±3σ is so unlikely under random variation that we suspect an assignable cause – the process may be out of control.

Hence control limits are set at $\mu \pm 3\sigma$:

$\text{UCL} = \mu + 3\sigma, \quad \text{LCL} = \mu - 3\sigma$

When all plotted points lie within the control limits, the process is said to be in a state of statistical control.

flowchart LR
    A[Process Data] --> B{Point inside ±3σ limits?}
    B -->|Yes| C[Process in control – common cause variation only]
    B -->|No| D[Signal of assignable cause – investigate]

---

Types of Control Charts

Measurement Method	Chart Name	Description
Attribute (proportion defective)	P chart	Monitors fraction of defective items per sample
Attribute (count of defects)	C chart	Monitors number of defects per unit
Variable (continuous data)	X‑bar & R charts	Monitors process average (X‑bar) and process range (R) using sample subgroups

---

Steps to Set Up a Control Chart

1. Choose the characteristic to measure (e.g., checkout time, pen diameter).
2. Select the measurement method (attribute or variable).
3. Choose the appropriate control chart (P, C, X‑bar+R).
4. Decide on a sampling plan – how many samples, how frequently.
5. Collect data and calculate control limits using statistical formulas.
6. Plot the data and analyze – are all points within limits? Any patterns?

A process with points outside the limits or with non‑random patterns signals the need for root‑cause investigation and corrective action.

---

Key Takeaways

• Two sources of variation: common causes (random, always present) and assignable causes (traceable, fixable).
• Specification limits (USL, LSL) reflect customer tolerance; control limits (UCL, LCL) reflect process capability.
• Measurement can be attribute‑based (good/bad count) or variable‑based (numerical values); choose based on cost and information needed.
• Control limits are set at $\mu \pm 3\sigma$; a point outside signals an assignable cause.
• The six‑step procedure: choose characteristic → choose measurement → choose chart → plan sampling → collect data & compute limits → plot & analyze.
• A process with only common causes is in statistical control; assignable causes indicate the process is out of control and needs investigation.

Variable Control Charts

Control charts monitor process stability over time. For variable data (continuous measurements like diameter in cm), the paired $\bar{X}$-chart (tracks the mean) and R-chart (tracks the range) are used. Their setup follows the same six-step methodology as attribute charts, differing only in parameter extraction.

Six-Step Setup (Variable Example: Cylinder Diameter)

1. Measurement characteristic – e.g., diameter of a cylindrical component (cm).
2. Measurement method – exact measurement (continuous).
3. Control chart type – $\bar{X}$-chart and R-chart.
4. Sampling plan – e.g., sample 5 consecutive pieces every 20 minutes; collect 15 such samples.
5. Collect data and establish control limits (detailed below).
6. Plot and analyse – check if all points fall within control limits.

Extracting Process Parameters from Sample Data

For each sample $i$ (size $n=5$), compute:

• $\bar{X}_i = \frac{1}{n}\sum_{j=1}^{n} X_{ij}$ (sample mean)
• $R_i = \max(X_i) - \min(X_i)$ (sample range)

Then the grand averages:

• $\bar{\bar{X}} = \frac{1}{k}\sum_{i=1}^{k} \bar{X}_i$ (overall mean)
• $\bar{R} = \frac{1}{k}\sum_{i=1}^{k} R_i$ (average range)

From the transcript example: $\bar{\bar{X}} = 12.417$, $\bar{R} = 0.119$.

Control Limits Using Standard Constants

Constants $A_2$, $D_3$, $D_4$ are read from a standard table based on sample size $n$. For $n=5$:

Constant	Value
$A_2$	0.577
$D_3$	0
$D_4$	2.114

$\bar{X}$-chart limits
$\text{UCL}_{\bar{X}} = \bar{\bar{X}} + A_2 \bar{R} = 12.417 + 0.577 \times 0.119 = 12.486$
$\text{LCL}_{\bar{X}} = \bar{\bar{X}} - A_2 \bar{R} = 12.417 - 0.577 \times 0.119 = 12.348$

R-chart limits
$\text{UCL}_{R} = D_4 \bar{R} = 2.114 \times 0.119 = 0.252$
$\text{LCL}_{R} = D_3 \bar{R} = 0 \times 0.119 = 0$

All sample $\bar{X}_i$ and $R_i$ plotted within these limits → process is in statistical control.

Exam tip: The constants depend only on sample size $n$. Memorise common values (e.g., $n=5$: $A_2=0.577$, $D_3=0$, $D_4=2.114$) or know how to read the table.

---

Attribute Control Charts (P and C Charts)

When measurement is attribute (pass/fail, defect count), two common charts are used.

P-Chart (Proportion of Defects)

• Characteristic: proportion of defective items in a sample.
• Sampling plan: e.g., sample 100 pieces every 30 minutes; 12 samples.
• Data: count of defects per sample → proportion $p_i = \text{defects} / n$.
• Centre line: $\bar{p} = \frac{\sum p_i}{k}$ (e.g., $\bar{p}=0.105$).
• Standard deviation: $\sigma_p = \sqrt{\frac{\bar{p}(1-\bar{p})}{n}}$.
• Control limits (using $3\sigma$):
  $\text{UCL}_p = \bar{p} + 3\sigma_p,\quad \text{LCL}_p = \bar{p} - 3\sigma_p$

Example with $n=100$, $\bar{p}=0.105$:
$\sigma_p = \sqrt{\frac{0.105 \times 0.895}{100}} \approx 0.031$
$\text{UCL}_p = 0.105 + 3 \times 0.031 = 0.198$
$\text{LCL}_p = 0.105 - 3 \times 0.031 = 0.012$
All plotted points inside → process in control.

C-Chart (Count of Defects per Unit)

• Use when: counting defects per constant unit (e.g., blemishes per $m^2$ of paint, thread runs per $m^2$ of cloth).
• Data: $c_i$ = number of defects in sample $i$; $m$ samples.
• Centre line: $\bar{c} = \frac{\sum c_i}{m}$.
• Standard deviation: $\sigma_c = \sqrt{\bar{c}}$.
• Control limits (3$\sigma$):
  $\text{UCL}_c = \bar{c} + 3\sqrt{\bar{c}},\quad \text{LCL}_c = \bar{c} - 3\sqrt{\bar{c}}$

The setup and interpretation mirror the P-chart; only the parameter formulae differ.

---

Using Control Charts for Operational Decisions

Once control charts are established, two operational questions arise:

1. Process Out of Control? – Handling an Outlier

If a point falls outside the control limits (e.g., sample #6 in a C-chart):

flowchart TD
    A[Outlier detected] --> B[Remove outlier, recompute control limits]
    B --> C[Investigate for assignable causes]
    C --> D{Assignable cause found?}
    D -->|Yes| E[Implement countermeasures, change process]
    D -->|No| F[Resume with revised limits]
    E --> F
    F --> G[Stabilise and monitor]

• Step 1: Remove the outlier and recompute $\bar{\bar{X}}$, $\bar{R}$, limits.
• Step 2: Detailed root-cause investigation.
• Step 3: If no assignable cause → resume with revised chart. If cause found → implement countermeasures, then resume.
• Step 4: Re-establish limits, monitor to ensure control.

2. Early Detection of Impending Drift – Zone Rules

Even when all points are within limits, non-random patterns may signal a developing problem. Zones are defined relative to the centre line and $\pm 1\sigma$, $\pm 2\sigma$, $\pm 3\sigma$ lines:

Zone	Region
Zone C	Between $\pm 1\sigma$ (closest to centre)
Zone B	Between $\pm 1\sigma$ and $\pm 2\sigma$
Zone A	Between $\pm 2\sigma$ and $\pm 3\sigma$

Common rules to flag potential drift (stop and investigate):

Rule	Pattern
1 point beyond Zone A (outside $\pm 3\sigma$)	Obvious outlier
9 consecutive points in Zone C or beyond (same side)	Shift in mean
6 points in a row steadily increasing or decreasing	Trend
14 points in a row alternating up and down	Cycling / systematic pattern
2 out of 3 consecutive points in Zone A or beyond	Early warning of shift
4 out of 5 consecutive points in Zone B or beyond	Early warning of shift
15 points in a row in Zone C	Over‑dispersion? (too little variation)

All these rules share the logic: the pattern appears non-random, suggesting an assignable cause may be developing. Proactive investigation can avert a quality problem.

Exam tip: Always distinguish between “out of control” (points outside limits) and “unusual pattern” (zone rules). Both require action, but the rules allow earlier detection.

Key Takeaways

• Variable control uses $\bar{X}$-chart (mean) and R-chart (range) with constants $A_2$, $D_3$, $D_4$ from sample size $n$.
• Attribute control uses P-chart (proportion of defects) or C-chart (count of defects per unit); limits based on $\bar{p}$ or $\bar{c}$ and $3\sigma$.
• An outlier beyond limits demands removal, recomputation, and investigation for assignable causes.
• Zone rules (e.g., 9 points in a row, 6 increasing, 2 out of 3 in Zone A) detect non-random patterns before defects escalate.
• A process in statistical control can be used to predict future defect rates — a key managerial insight.

Process Capability and the Voice of the Customer

Once a process is statistically stable and in control (using control charts), the next step is to assess its performance against the voice of the customer – expressed as a target value, an upper specification limit (USL), and a lower specification limit (LSL). Superimposing these on the process’s own control limits (UCL, LCL) reveals whether the process can consistently meet customer requirements.

Spread vs. Centering: Two Dimensions of Process Capability

Even before comparing with specifications, the inherent capability of a process can be evaluated along two independent dimensions:

1. Spread (variation) – How wide the process distribution is.
2. Centering (location) – How close the process mean is to the target.

Consider two processes, A and B, both normally distributed and centered identically.

• Process A (blue): large spread, extends beyond USL and LSL → capable of producing defects.
• Process B (red): smaller spread, fits within specification limits → inherently better.

General rule: All else equal, smaller spread = more capable process.

Now consider two processes with identical spread but different centering.

• Process A (grey): centered exactly on the target → most output within specs.
• Process B (red): offset from the target → more output falls beyond USL or LSL → higher defect propensity.

General rule: All else equal, a process centered on the target is more capable than one that is off-centre.

Cp (Potential Capability)

The ratio of the specification range to the process's natural spread (6σ, representing ±3σ) measures the potential capability – what the process could achieve if perfectly centered.

$C_p = \frac{USL - LSL}{6\sigma}$

• Ignores centering – assumes process is positioned ideally.
• A higher $C_p$ indicates greater potential to meet specifications.

Cpk (Actual Capability)

Cpk adjusts $C_p$ for the offset (deviation) of the process mean $\mu$ from the target (or closer spec limit). It is the actual capability of the process as it currently runs.

$C_{pk} = \min\left( \frac{USL - \mu}{3\sigma}, \; \frac{\mu - LSL}{3\sigma} \right)$

• Captures both spread and centering.
• Used to predict defect rates and set improvement targets.

Cpk and Defect Rate

Cpk	Defects (PPM)	Equivalent Sigma Level
0.25	453,255	~1.5σ
0.5	~158,655	~2σ
1.0	2,700	~3.4σ
1.5	3.4	~5σ
2.0	0.0018 PPM (1.8 PPB)	6σ

Exam tip: A Six Sigma organisation is defined as one that achieves Cpk = 2.0 – only 1.8 defects per billion opportunities (assuming a ±1.5σ shift). Memorise the Cpk-to-PPM relationship for Cpk = 1.0 and 2.0.

Practical Use of Cpk

• Monitor Cpk over time and set improvement targets (e.g., from 0.5 to 0.75 to 1.0).
• Supplier evaluation – require suppliers to report and maintain specified Cpk levels.
• Continuous improvement – reducing spread and improving centering pushes Cpk toward 2.0.

Key takeaways

• Process capability has two dimensions: spread (smaller = better) and centering (closer to target = better).
• $C_p$ measures potential; $C_{pk}$ measures actual capability accounting for off-centering.
• Cpk directly predicts defect rate (ppm).
• Six Sigma = Cpk = 2.0 = 1.8 defects per billion.
• Cpk is used for internal improvement targets and supplier performance monitoring.

---

Service Quality: Unique Challenges and the Gaps Model

Services are fundamentally different from products – they are performances, not objects. This makes quality assurance more complex.

Why Service Quality is Different

• Intangible & inseparable: Services cannot be counted, measured, inventoried, tested, or verified in advance.
• Heterogeneous: Vary across producers, consumers, and even day-to-day. Consistency of employee and customer behaviour is hard to ensure.
• Perishable & delivered in real time: Quality occurs during interaction with the customer. Consumer input is critical; managers have less real-time control.
• Difficult to recover: Failed services cannot be recalled like products. Poor service leads to customer exit.

Examples of poor service quality:

• Airline delay kept passengers in the dark.
• Weekend B-school programme far below participant expectations.
• E-tailers failed to deliver Christmas gifts on time (1999).

The Service Quality Gaps Model

Service quality is defined as the gap between perceived service and expected service (called Gap 5). The model proposes that Gap 5 can be explained by four other gaps (Gap 1–4).

flowchart LR
    A[Customer Expectations] --> B[Gap 5: Service Quality]
    C[Management Perceptions] --> D[Gap 1]
    D --> E[Gap 2: Service Quality Specifications]
    E --> F[Gap 3: Service Delivery]
    F --> G[Gap 4: External Communications to Customers]
    G --> B
    B --> H[Perceived Service]

Gap 1: Knowledge Gap – Management does not fully understand customer expectations.

• Cause: Lack of research, misinterpretation of customer needs.
• Fix: Better market research and customer listening.

Gap 2: Design Gap – Even if expectations are known, there is no adequate service design or standards.

• Cause: Absence of management commitment to quality, lack of know-how.
• Fix: Invest in service design, benchmarking, clear quality specifications.

Gap 3: Delivery Gap – The service performed does not meet the set specifications.

• Cause: Employee performance variability, poor training, inadequate procedures.
• Fix: Training, standard operating procedures, employee empowerment.

Gap 4: Communication Gap – What is promised in external communication differs from what is actually delivered.

• Cause: Overpromising in ads/brochures; neglecting to inform customers about invisible quality efforts.
• Fix: Realistic external communications; manage expectations transparently.

Gap 5: Perceived Service Quality – The overall service quality experienced by the customer.

• Result of gaps 1–4. Reducing those gaps narrows Gap 5.

Closing the Gaps

Instead of treating service quality as unmeasurable, the gaps model pinpoints where and why quality fails. Organisations can then invest in:

• Employee training (reduces Gap 3).
• Better service design and standards (reduces Gap 2).
• Realistic external communications, revised brochures (reduces Gap 4).
• Improved customer insight (reduces Gap 1).

Exam tip: Gap 5 = f(Gap 1, Gap 2, Gap 3, Gap 4). Any question on service quality measurement will likely revolve around identifying which gap is present in a given scenario. Be able to match the example to the gap.

Key takeaways

• Service quality is intangible, heterogeneous, and produced in real-time – different from product quality.
• The gaps model decomposes service quality (Gap 5) into four underlying gaps.
• Gap 1: not understanding expectations; Gap 2: no proper specs; Gap 3: poor delivery; Gap 4: overpromising.
• Closing gaps requires targeted investments in training, design, and communication.
• The model provides a diagnostic framework for improving service quality at the planning stage.

X Bar & R Chart

X-bar and R charts are paired control charts used for continuous (variables) data—like weight, length, or time—to monitor both the central tendency (mean) and the dispersion (range) of a process over time. Intuitively, the process might produce pouches that average exactly 500 g (mean is fine) while individual pouches swing wildly (variation is out of control). Monitoring only one chart can miss the other problem.

Why Use Both Charts?

Aspect monitored	Chart	What it signals
Process mean	X-bar chart	Are the subgroup averages stable around a target? Shifts in mean (e.g., due to a new batch of raw sugar).
Process spread	R chart	Is the within-subgroup variation stable? Spikes in range (e.g., due to machine wear or operator drift).

If either chart shows an out-of-control signal, the process is out of control. A process can be “on target” but have excessive variability – or have tight variability but drift off target.

Computing Control Limits

Steps (illustrated with Shakti Foods data: 16 subgroups, each of size $n=5$):

1. Collect subgroups – e.g., 5 sugar pouches sampled periodically.
2. For each subgroup $i$, compute:
   • Sample mean: $\bar{x}_i$
   • Range: $R_i = \max - \min$
3. Grand mean and average range: $\bar{\bar{x}} = \frac{1}{k}\sum_{i=1}^{k}\bar{x}_i \quad,\quad \bar{R} = \frac{1}{k}\sum_{i=1}^{k} R_i$
4. Look up constants from standard control chart tables (based on $n=5$):

Constant	Value	Use
$A_2$	0.577	X-bar chart limits
$D_3$	0	Lower limit for R chart
$D_4$	2.114	Upper limit for R chart

X-bar chart: $UCL_{\bar{x}} = \bar{\bar{x}} + A_2\bar{R}$ $LCL_{\bar{x}} = \bar{\bar{x}} - A_2\bar{R}$

R chart: $UCL_R = D_4\bar{R}$ $LCL_R = D_3\bar{R} = 0 \quad (\text{since } D_3=0 \text{ for } n\le6)$

Worked Example: Shakti Foods Sugar Pouches

• Specification: 500 g per pouch.
• Data collected: 16 subgroups of 5 pouches each. Subgroup weights ranged from approximately 488 g to 531 g.
• Calculated: $\bar{\bar{x}}$ and $\bar{R}$ from the 16 means and 16 ranges.
• Constants (as above): $A_2=0.577$, $D_4=2.114$, $D_3=0$.
• X-bar chart limits: $\bar{\bar{x}} \pm 0.577\bar{R}$.
• R chart limits: $UCL_R = 2.114\bar{R}$, $LCL_R = 0$.

Interpretation:

• All 16 sample means fell between the upper and lower control limits on the X-bar chart → mean appears in control (random variation only).
• However, one subgroup range exceeded $UCL_R$ on the R chart → dispersion is out of control (a special cause has increased variability).

How to read the combined picture:

flowchart LR
    A[X-bar in control?] -->|Yes| B[Mean is stable]
    A -->|No| C[Mean out of control → investigate]
    D[R chart in control?] -->|Yes| E[Variation is stable]
    D -->|No| F[Variation out of control → investigate]
    B --> G{Both stable?}
    E --> G
    G -->|Yes| H[Process in control]
    G -->|No| I[Out of control]
    C --> I
    F --> I

In the Shakti example: the mean is stable but variation is not → overall process is out of control. The quality engineer should pause and look for an assignable cause (e.g., worn filling nozzle, inconsistent raw material) that made one subgroup’s range spike.

Exam tip: A common mistake is to declare a process “in control” based only on the X-bar chart. Always review both charts. The X-bar chart can look fine while the R chart reveals a problem – or vice versa. Both must be in control for the process to be stable.

Key Takeaways

• X-bar chart monitors the process mean; R chart monitors the process dispersion.
• Both charts are needed for continuous data to get a complete stability picture.
• Control limits depend on subgroup size $n$ (constants $A_2, D_3, D_4$ from standard tables).
• A point above $UCL$ or below $LCL$ on either chart signals an out-of-control process.
• Shakti Foods example: means in control, but one large range → dispersion out of control.

Capability Problem

Process capability quantifies how well a process can consistently produce output that meets customer specifications. Intuitively: given the natural variation of a process (its "voice"), can it fit within the tolerance window set by the customer (the "voice of the customer")? Two indices measure this fit: Cp (for mean-centered processes) and Cpk (for any process, penalizing off-center means).

Definitions and Formulas

• Voice of the customer: the acceptable range $USL - LSL$ (Upper Specification Limit – Lower Specification Limit).
• Voice of the process: the natural spread of the process, assumed to be $\pm 3\sigma$ from the mean, i.e., $6\sigma$.

Cp – Process capability for a perfectly mean-centered process where the process mean $\mu_p$ equals the specification target $\mu_s$: $C_p = \frac{USL - LSL}{6\sigma}$ A value $<1$ indicates the process spread exceeds the tolerance; $>1$ indicates room to spare.

Cpk – Conservative capability index used when the process mean is not centered (or in all cases, as it is always ≤ Cp): $C_{pk} = \min \left( \frac{USL - \mu_p}{3\sigma},\ \frac{\mu_p - LSL}{3\sigma} \right)$ Cpk penalizes shift: even if the spread is small, an off-center mean reduces capability.

Index	Condition	Interpretation
$C_p$	$\mu_p = \mu_s$	Ratio of tolerance width to process spread
$C_{pk}$	$\mu_p \neq \mu_s$ (or general)	Capability accounting for mean location; the smaller of the two one-sided distances in units of $3\sigma$

Decision Logic

flowchart TD
  A[Compute process mean μp and sigma σ] --> B{Is μp = μs?}
  B -->|Yes| C[Use Cp]
  B -->|No| D[Use Cpk]
  C --> E[Cp = (USL-LSL)/(6σ)]
  D --> F[Cpk = min of two Z-values]

Worked Example: Shakti Foods (Original Process)

Data

• Process: filling raw sugar pouches
• Target: 0.5 kg per pouch
• Process parameters: $\mu_p = 0.5\ \mathrm{kg}$, $\sigma = 0.006\ \mathrm{kg}$
• Customer specifications: $USL = 0.51\ \mathrm{kg}$, $LSL = 0.49\ \mathrm{kg}$
• Specification mean: $\mu_s = (0.51 + 0.49)/2 = 0.5\ \mathrm{kg}$

Step 1: Check centering – $\mu_p = \mu_s$ → process is mean-centered → use $C_p$.

Step 2: Compute $C_p$

$$C_p = \frac{0.51 - 0.49}{6 \times 0.006} = \frac{0.02}{0.036} \approx 0.56$$

Interpretation: $C_p = 0.56 < 1$ – the process spread (6σ = 0.036 kg) is wider than the tolerance (0.02 kg). A high defect rate is expected even when centered.

Changed Process: Mean Drift

After some weeks, the process mean shifts to $\mu_p' = 0.505\ \mathrm{kg}$ (σ unchanged at 0.006 kg). Specifications remain the same.

Check centering – $\mu_p' \neq \mu_s$ → use $C_{pk}$.

Compute $C_{pk}$

$$\frac{USL - \mu_p'}{3\sigma} = \frac{0.51 - 0.505}{3 \times 0.006} = \frac{0.005}{0.018} \approx 0.278$$ $$\frac{\mu_p' - LSL}{3\sigma} = \frac{0.505 - 0.49}{3 \times 0.006} = \frac{0.015}{0.018} \approx 0.833$$ $$C_{pk} = \min(0.278,\ 0.833) = 0.278$$

Capability dropped from 0.56 to 0.278. The shift increases the tail probability above the USL dramatically, more than offsetting the reduction below LSL.

Exam tip: $C_{pk} \leq C_p$ always. A large drop from $C_p$ to $C_{pk}$ signals mean shift. Here $C_p$ (if computed for the changed process ignoring shift) would still be 0.56, but $C_{pk}$ reveals the true performance.

Improvement Strategies

Two levers exist to restore (or improve) capability:

1. Recenter the process – bring $\mu_p$ back to 0.5 kg. This restores $C_p = 0.56$.
2. Reduce variability – if recentering is impossible (e.g., engineering constraint), shrink $\sigma$ so that even with the shifted mean, the tails fall within specifications. For example, if $\sigma$ were halved to 0.003 kg, $C_{pk}$ would double.

Combining both actions yields the greatest improvement.

Key Takeaways

• $C_p$ measures potential capability when the process is perfectly centered; $C_{pk}$ measures actual capability, penalizing off-center means.
• $C_p = (USL - LSL) / 6\sigma$; $C_{pk} = \min(\frac{USL - \mu}{3\sigma},\ \frac{\mu - LSL}{3\sigma})$.
• A capability index below 1 implies the process cannot consistently meet specs without defects.
• Mean drift reduces $C_{pk}$ even if spread remains the same.
• Improvement: (1) recenter the mean, (2) reduce variation, or both.

What is the Productivity Paradox?

Organisations often invest heavily in specific functions (e.g., manufacturing, CRM, inventory) yet fail to win orders or improve business performance. This gap between local productivity gains and global business outcomes is the Productivity Paradox.

Intuitively: a factory may be highly efficient, but customers still complain of delays or shortages. The traditional measure of productivity —$\text{Productivity} = \frac{\text{Output}}{\text{Input}}$— can show improvement in one area while the organisation as a whole stagnates or deteriorates. The paradox arises because output must be replaced with useful output — only activities that contribute to order-winning create real value. The rest is waste.

Illustrative Examples

1. Excessive Travel Distance for a “Good” Product

A company with four product lines (A–D) introduced products C and D late, expecting them to be strong. Data on total distance travelled on the shop floor (raw material → sub-assembly → final assembly):

Product Line	Total Distance Travelled (km)	Number of Parts	Avg Distance per Part (m)
A	375	1,080	348
B	548	—	—
C	959	—	—
D	733.6	—	—

Product C is supposed to be good, but it travels far too much on the shop floor. The result: high cost and long lead time, making it uncompetitive. The manufacturing system itself is inefficient, despite the product’s potential.

2. Non‑Manufacturing Activities Dominate Lead Time – Standard Orders

Data from 79 standard orders:

Stage	Average Days	% of Total Lead Time
Order Handling	—	—
Scheduling	17.9	46%
Production	—	—
Assembly & Testing	—	—
Packing & Invoicing	4	—

Nearly half the total lead time is consumed by scheduling – a non‑manufacturing planning activity. Good manufacturing exists, but scheduling inefficiency makes the product uncompetitive.

3. Order Handling + Scheduling Dominate – Special Orders

Data from 13 custom orders:

Stage	Average Days	% of Total Lead Time
Order Handling	—	84% combined
Scheduling	~150 days	(order handling + scheduling)
Production	—	—
Assembly & Testing	—	—
Packing & Invoicing	—	—

Understanding customer requirements, estimating cost, communicating, obtaining approval (order handling), then detailed planning (scheduling) together consume 84% of total lead time (~5 months). The manufacturing system is efficient, but the front‑end processes destroy competitiveness.

4. Back‑and‑Forth in Capital Goods Order Processing

A company selling customised machine tools follows a lengthy chain:

flowchart LR
    A[Customer] --> B[Marketing Branch]
    B --> C[Marketing HQ]
    C --> D[Unit Head Office]
    D --> E[Design]
    E <--> F[Process Planning]
    F <--> G[Cost Estimation / Casting]
    G --> D --> C --> B --> A

Design, process planning, and cost estimation iterate (two‑way arrows). After weeks, the final quote reaches the customer – but the delay may be unacceptable. Again, good technical capability exists, but the process is slow and uncoordinated.

Causes of the Productivity Paradox

1. Piecemeal improvements (local optima ≠ global optima) – Excelling in one function (e.g., manufacturing) while ignoring others (e.g., order handling) does not guarantee order‑winning.
2. Productivity is moderated by the supply chain – Even if one entity improves, weak links elsewhere block value delivery.
3. Yesterday’s order winners become today’s order qualifiers – Customer preferences shift. E.g., in the 1980s, “quality” was an order winner; today it is merely an order qualifier.
4. Value migration – As markets and demographics change, organisations must realign; failure to do so leads to profitless turnover (top line growth, bottom line shrinks).

Exam tip: The Productivity Paradox warns against measuring productivity in isolation. Always ask: Does this improvement contribute to order‑winning? If not, it may be waste.

Ground Rules for Managing Productivity

• Rule 1: Only activities that create value contribute to productivity; everything else is cost or waste.
• Rule 2: The locus of reference for value is the customer, not the organisation.
• Rule 3: Multiple entities (suppliers, distributors, service providers) significantly influence value creation.

The Notion of a Value Stream

A value stream is the path along which value flows, from initial concept (value proposition) through multiple entities, to the ultimate customer.

Example: Passenger Car

Ore mining → tiers of component/sub‑assembly suppliers → vehicle assembly → outbound logistics → dealership network → sales → after‑sale service.

Example: Holiday Package

Conceptualisation of the package → travel & ticketing → resort management → facilities at each destination (language, culture, policies) → inter‑destination travel → food & beverages.

All these entities collectively create the value.

Value Stream Competition

“Company A competes with Company B” is superficial. More accurately: the value stream associated with Company A competes with the value stream associated with Company B.

• A company may have an excellent product and manufacturing, but a badly developed supply base → value is blocked.
• A company may have a unique service, but last‑mile franchisees fail to deliver → value is blocked.

When a value stream is poorly configured (blockages exist), the productivity paradox emerges: local excellence does not reach the customer.

Key Takeaways

• The Productivity Paradox occurs when local productivity improvements do not translate into business gains.
• Causes include piecemeal focus, supply chain weaknesses, shifting order winners/qualifiers, and value migration.
• Use useful output (only what wins orders) in productivity measures: $\text{Value-based Productivity} = \frac{\text{Useful Output}}{\text{Input}}$.
• A value stream encompasses all entities that contribute to value creation; it is the unit of competition.
• Blockages in the value stream – not just internal inefficiency – are the root of the paradox.

Non-Value Added Activities and Lean Management

Value is the central lever for productivity. Only activities customers pay for are value-adding. Many business activities add no value—or even subtract value—and directly harm productivity. Eliminating such waste is the core of Lean Management, a structured framework built on Just‑in‑Time (JIT) and Total Quality Management (TQM).

---

Non‑Value Added Activities

Any activity that consumes resources without creating value the customer is willing to pay for. Examples:

• Accumulating inventories (raw material, WIP, finished goods)
• Machine breakdowns, defects, rework
• Waiting for materials, tools, information
• Moving parts over long distances (excess material handling)
• Double handling, over‑production
• Unnecessary paperwork, data entry, counting parts
• Poorly planned meetings, excessive approvals

Categories of Waste

Category	Manufacturing Examples	Service Examples
Inventory‑related	Accumulating inventory, waiting for material, stock verification, part shortage, temporary storage	Overflowing inboxes (mailboxes), duplication of work, excessive paperwork, pending decisions due to incomplete info
Process‑related	Defects, rework, machine breakdowns, watching machines run (no actual work)	Late payments, wrong service delivery, delayed proposals, long customer order fulfilment
Planning‑related	Looking for tools, carrying heavy pieces, long material transfer, double handling, over‑production	Complicated office layouts, poorly planned meetings, documents handled many times, too many decision‑makers, teams without clear direction

Common Characteristics of Non‑Value Added Activities

• The customer will not pay for any of them.
• They negatively impact time, cost, quality, and delivery.
• They are value‑subtracting → productivity suffers.

Exam tip: Memorise the three categories with 2–3 examples each. The “customer will not pay” test is the quickest way to identify waste.

Key Takeaways

• Non‑value added activities = waste → lower productivity.
• Three categories: inventory, process, planning.
• All waste degrades time, cost, quality, delivery.
• Customers pay only for value‑adding steps.

---

Lean Management Framework

Lean enterprise – an organisation that deploys mechanisms to define value, identify the value stream (e.g. concept‑to‑launch, order‑to‑delivery, raw material‑to‑finished product), and systematically remove Muda (waste). Other forms of waste: Mura (unevenness), Muri (excess).

Basic Premise

Eliminate waste to create a smooth value stream.

flowchart LR
    A[Eliminate Waste] --> B[Create Value Stream]
    B --> C[Enabling Mechanisms]
    C --> D[JIT & TQM]
    D --> E[Tools & Techniques]
    E --> F[Benefit: Less is More Productive]

Enabling Mechanisms

• Just‑in‑Time (JIT) – systematically expose problems by reducing inventory.
• Total Quality Management (TQM) – systematically and sustainably solve problems.

Tools & Techniques (representative)

Physical / Structural	Planning / Methodological
Setup time reduction	Process mapping
Smart lot‑size processing	Continuous improvement (Kaizen)
Pull‑type scheduling	Benchmarking
Simplified operational control	Quality circles

The Benefit: “Less is More Productive”

With the same capacity, produce more; or for a given output, use fewer resources. Comparative example – Toyota vs. GM (automotive industry):

Metric	Toyota (Japan)	GM (USA)
Production volume	4 million vehicles	8 million vehicles
Number of employees	37,000	850,000
Parts with detailed engineering	30% (3,000 of 10,000)	81% (8,100 of 10,000)
Employees in purchasing	337	~5,700 (≈17×)
Suppliers for upholstery (one model)	1 (Nissan)	25

Exam tip: The Toyota/GM table illustrates that doing less (fewer engineered parts, fewer suppliers, fewer employees) can yield more output per employee. This is the essence of lean productivity.

Key Takeaways

• Lean = define value → map value stream → remove waste (Muda, Mura, Muri).
• Two pillars: JIT (expose problems) and TQM (solve problems).
• Tools range from setup reduction to process mapping.
• “Less is more productive” – fewer resources, same or higher output.

---

The Two Main Pillars: Just‑in‑Time and Total Quality Management

Water Flow Analogy

• Ship = daily operational rate (e.g. cars per shift, loan applications processed per day)
• Water = inventory (materials, excess people, idle machine capacity, unused space)
• Rocks = problems (poor quality, defective material, bottlenecks, machine breakdowns, managerial constraints)

Two approaches:

1. Pour water (increase inventory) – raises water level so the ship sails over the rocks, but hides the problems.
2. Chisel the rocks (reduce inventory) – lower the water level deliberately; when the ship cannot sail, expose the rock and fix it.

Lean chooses only to chisel – never to pour water.

flowchart TD
    Start[Deliberately reduce inventory / water] --> Obstacle{Rock / problem appears?}
    Obstacle -->|Yes| Fix[Solve problem using TQM]
    Fix --> Lower[Inventory level drops further]
    Lower --> Obstacle
    Obstacle -->|No| Continue[Operations run smoothly with less inventory]
    Continue --> Repeat[Continue reducing inventory periodically]

Progressive Waste Elimination

1. Remove some inventory (water)
2. Problems (rocks) surface → ship cannot sail
3. Use JIT to expose the problem; use TQM to solve it
4. Repeat → water level (waste) declines continuously

Lean is a relative state – no absolute “lean”; organisations become progressively leaner.

Exam tip: The water‑rock analogy is the classic explanation for why JIT and TQM are inseparable. Always connect: reduce inventory → expose problem → solve problem → further reduce inventory.

Key Takeaways

• JIT = systematically expose problems (by reducing inventory).
• TQM = systematically solve problems (root‑cause fixes).
• Lean requires an organisation‑wide mechanism with top management support.
• Inventory includes materials, people, capacity, and space – any idle resource.
• The process is iterative: expose → solve → reduce → expose again.

Elements of a JIT Manufacturing System

Just-in-time (JIT) manufacturing systematically exposes and eliminates waste (inventory, excess manpower, idle capacity, unnecessary space). The water-flow analogy: inventory is water that hides rocks (problems); lowering the water level reveals problems that must be solved. Modifying structural and planning methods removes the “water” – i.e., waste.

Three fundamental modifications are needed:

1. Redesign the manufacturing system into a chain of internal customers.
2. Pull-based production planning and control (supermarket model).
3. Setup-time reduction → lot-size reduction.

Internal Chain of Customers

Each process is physically and logically linked to the next: the preceding process serves the succeeding process as its internal customer.

• Traditional layout: resources grouped by function (all grinders in one area, all mills in another). Material moves long distances, creates waiting, hides waste.
• JIT layout: resources regrouped by product family. Each product line has its own dedicated cell containing the needed machines and support (stores, material planning).

flowchart LR
    subgraph Traditional Functional Layout
        A1[Grinding] --> B1[Turning] --> C1[Milling]
        D1[Stores] --> B1
    end
    subgraph JIT Product-Focused Layout
        P1[Raw Material] --> Cell1[Cell: Grind, Turn, Mill, Stores]
        Cell1 --> FG1[Finished Goods Store]
    end

Advantage: simpler, more effective control; reduced travel distances and waiting; waste becomes visible.

Pull-Based Planning (Supermarket Model)

Instead of pushing work via schedules, each downstream step pulls what it needs from the upstream step – exactly as a supermarket shelf is replenished by the back store, which in turn triggers procurement.

• Downstream process withdraws required items.
• Upstream process only produces enough to replace what was taken.
• Eliminates overproduction and excess inventory.

Setup-Time Reduction and Lot-Size Reduction

• Setup = changeover time between product variants.
• Long setup → large batch sizes (to absorb the cost of downtime).
• Reducing setup time allows smaller batches, eventually single-piece flow.
• Methods: tool pre‑setting, quick‑change fixtures, parallel operations.

Kanban System for Inventory Reduction

Kanban (card or signal) controls the flow between stages using standard containers.

• Suppose 1,000 pieces of inventory exist between two stages. Put them in 10 containers of 100 each = 10 Kanban cards.
• Periodically remove one container → inventory drops to 900, revealing problems (e.g., machine breakdowns, defects) that were hidden by the buffer.
• The number of Kanban cards is deliberately reduced over time to force continuous improvement.

Supplier Collaboration

• Long-term partnerships with suppliers ensure defect-free, on-time deliveries.
• Reduces incoming inspection, rejects, and buffer stock.

Common Goal

All JIT elements aim to lower waste. As waste is removed, the proportion of value‑adding activities increases. The paradox “less is more productive” becomes reality – the organization becomes lean.

Exam tip: The “water flow” analogy is a classic exam question. Inventory hides problems; lowering it exposes them. Be ready to explain how each JIT element (cell layout, pull, Kanban, setup reduction) contributes to waste removal.

Key takeaways

• JIT requires physical restructuring into product-focused cells – an internal chain of customers.
• Pull planning controls production via downstream demand (supermarket model), eliminating push-driven overproduction.
• Setup-time reduction → smaller lot sizes → less work-in-process inventory.
• Kanban uses cards and standard containers to cap and systematically reduce inventory.
• Supplier collaboration ensures quality and on-time delivery, cutting inspection waste.
• All elements work together to expose and eliminate waste, raising the share of value-added time.

---

Process Mapping for Non-Value-Added (NVA) Analysis

Process mapping chronologically lists every step in a process, classifying each activity to identify waste. It is the essential first step toward eliminating non-value-added (NVA) work.

Example: Subassembly Process Map (81 activities)

A factory suspected long lead times in a subassembly were delaying final assembly. They traced every step from material request to completion. Activities were categorised as:

Category	Label	Description
Waiting	WT	No action – material sits idle
Moving	MV	Physical transport between locations
Adding Value	AV	Direct transformation that the customer would pay for
Adding Cost	AC	Rework, inspection (customer would not pay for this)

Summary of the 81 activities (lead time for one batch):

Category	Number of activities	Hours consumed	% of total time
Waiting	53	1,098	65.4%
Moving	(rest)	(remaining)	(rest)
Adding Value	—	106	6.3%
Adding Cost (rework, etc.)	—	(balance)	(balance)
Total	81	1,680	100%

Only 6.3% of total lead time (106 out of 1,680 hours) actually added value from the customer’s perspective. The other 93.7% is waste – the customer would not pay for it.

Exam tip: The 6.3% value-add figure is a striking demonstration of how much waste typical processes contain. Expect to interpret a similar summary table and calculate the proportion of NVA activities.

Four Methods to Map a Process

Method	Description	Reliability
Customer order walkthrough	Trace a completed order (or product) physically through the process, recording what happens at each step.	Highest – uses real data, though time‑intensive.
Collaborative discussions & charting	Assemble a group of experienced workers (20 people, 3 groups). Give them 30 minutes to map the process on a whiteboard based on their daily experience.	Good – leverages tacit knowledge.
Bottom‑up interviews	Interview people across functional areas; aggregate their snapshots into one map.	Moderate – may miss cross‑functional links.
Executive judgment	Senior managers sketch the process based on their perception.	Approximate; least reliable.

Types of Data to Collect

• Distance travelled by materials.
• Elapsed time (timestamps from start to finish).
• Assets and people deployed (headcount, equipment used).
• Activity category (waiting, moving, value-add, cost-add, etc.).
• Ownership – who is responsible for each step.

Example: Procurement Process Data

A procurement process was mapped into three high-level activities:

Activity	Time spent by category of staff	Travel %	Telephone %
Supplier selection	…	40% (liaison)	48% (follow‑up)
Purchasing material	…	…	…
Vendor servicing	…	…	…

The same data can be sliced differently (resource consumption, cost, defect rates) depending on the improvement goal.

Purpose

Process mapping provides the detailed snapshot needed to:

• Identify the largest sources of waste (e.g., waiting, rework).
• Launch targeted improvement efforts (e.g., “Why do we wait 53 times? How can we reduce moving?”).
• Measure baseline performance before and after changes.

Key takeaways

• Process mapping chronologically lists every step and classifies it as value-add, waiting, moving, or cost-add.
• In the example, only 6.3% of lead time was value-add – the rest is waste.
• Four methods: customer walkthrough (most reliable), collaborative charting, interviews, executive judgment (least reliable).
• Collect data on time, distance, people, category, and ownership.
• The map is the basis for waste elimination – after mapping, one can analyse causes and plan improvements.

The Process Improvement Methodology

Process improvement requires a structured, sustainable methodology to eliminate waste. A service organization example: customers complained of excessive delays, errors, and too much paperwork.

Broad objectives set for the exercise:

• Reduce time and paperwork by at least 25%
• Develop better job descriptions and procedures
• Deliver tangible cost savings
• Implement an online system

Process mapping (from previous step) identified 79 activities. Data collected on a sample of past cases:

Metric	Value
Average response time	2.8 days (range 2–6)
Distance travelled per request	1.85 km
Rejects (month 1)	5.11%
Rejects (month 2)	4.6%
Rejects (month 3)	8.7%

Brainstormed improvement ideas were colour-coded by implementation horizon:

• Low-hanging fruit (e.g., process same day, send incomplete requests back) – implementable immediately with approval.
• Medium-term (e.g., change data collection format, share customer info) – takes weeks or up to a month.
• Long-term (e.g., online system) – significant time and investment.

Results after implementation (all ideas executed):

• Response time: average dropped to 1.1 days (sample of 25)
• Rejects: reduced to 0%
• Non-value added activities eliminated: 17

The 7-Step Methodology

A generalizable, structured approach any organization can adopt:

flowchart TD
  A[Step 1: Identify problem areas & set project scope] --> B[Step 2: Define value-adding categories]
  B --> C[Step 3: Obtain measures to assess process]
  C --> D[Step 4: Brainstorm improvement opportunities]
  D --> E[Step 5: Prioritize options for implementation]
  E --> F[Step 6: Present options, obtain mandate & budget]
  F --> G[Step 7: Implement, measure results, document improvements]

Step 2 requires classifying all activities into three categories:

• Value-adding (VA): Activities the customer is willing to pay for.
• Non-value adding (NVA): Activities the customer will not pay for.
• Necessary but non-value adding (NNVA): Activities that must remain temporarily (e.g., inspection) but should eventually be eliminated via better process control.

Organization Structure for Continuous Improvement

After high-level process mapping, detailed projects are carved out. Each project follows the 7-step methodology. This structure aligns with lean management and ensures waste elimination is tackled systematically.

Exam tip: The three activity categories (VA, NVA, NNVA) are central to process mapping. NNVA is a practical concession – it is still waste, but cannot be eliminated immediately. Distinguish it from pure NVA.

Key takeaways: Process Improvement Methodology

• A structured methodology prevents the "productivity paradox" – wrong improvements that waste effort.
• Necessary but non-value adding activities are temporary; the goal is their eventual elimination.
• Low-hanging fruit should be implemented first to build momentum.
• The methodology is consistent with lean management and supports sustainable productivity gains.

Performance Metrics for Productivity Improvement

Traditional performance measures (financial reports, variance analysis, spend analysis) serve control – they are like a scoreboard: historical, for top management, and tied to incentives. But for real-time operational improvement, workers need trajectory-of-the-ball measures.

Basketball analogy: Players cannot look at the scoreboard while playing; they need to track the ball's trajectory. Coaches watch both. In business, employees need operational, non-financial measures to adjust on the fly; managers need financial reports (scoreboard) for strategic overview and evaluation.

New role for performance metrics: Learning and improvement – not just control or incentives. Measures should be:

• Operational (not purely financial)
• Process-oriented
• Available to everyone doing the work

Categories of Performance Metrics

Measures for Improvement (local and/or global)

Metric	Description	Ideal
Lead Time to Work Content	Total lead time ÷ actual work content time	1–2.5
Process Speed to Sales Rate	Process speed vs market demand rate	1
Schedule Adherence	% of orders completed on time	100%
First Pass Yield	% of units defect-free without rework	100%
Non-Value Adding Content	% NVA activities	0%
Cost of Quality	Prevention + appraisal + failure costs	Minimized
Indirect to Direct Labor Ratio	Indirect labor hours / direct labor hours	Low
Number of Days of Inventory	Inventory days of supply	Low (per demand)

Worked example – Lead Time to Work Content
From the process mapping case:
Work content (VA) = 106 hours, Total lead time = 1,680 hours.
$\text{Ratio} = \frac{1680}{106} = 15.85$
This indicates very low productivity; an ideal ratio would be 1–2.5.

Measures for Learning and Innovation (global – division/organization level)

Metric	Interpretation
Average number of suggestions per employee	Higher suggests engaged, learning culture
Average training time per employee	More training → capability building
Number of certified deliveries (suppliers ship directly, no QC)	Indicates trust and process reliability
Delivery code for customized products	Lower time → better learning
New product introduction time	Shorter cycle shows faster learning
Average number of engineering change notices (ECNs)	Fewer ECNs after launch → better initial learning

All these measures, when improved, directly increase productivity by reducing waste and enhancing capability.

Exam tip: Distinguish "measures for improvement" (operational, local/global) from "measures for learning and innovation" (more strategic, often global). Both are non-financial and process-oriented – opposite of traditional control metrics.

Key takeaways: Performance Metrics

• Shift from financial control to operational learning – treat metrics as "trajectory of the ball", not just the scoreboard.
• Lead time to work content ratio > 5 indicates process waste; ideal is 1–2.5.
• Improvement metrics are local or global; learning metrics are typically global.
• ECNs, certified deliveries, and training time signal how fast the organization learns and improves.

Visual Control Aids for Productivity Improvement

Lasting productivity improvement rests on three pillars: it must be data-driven (not gut-feeling), employee-centred (the people doing the work drive the changes), and continuous (not a one-off event). Visual control aids are a single mechanism that satisfies all three simultaneously.

A visual control system is an operational measurement system that:

• Provides the trajectory of performance (not just end results) – analogous to watching the ball’s path in a basketball game, not only the final score.
• Is maintained by the operating personnel themselves (manufacturing or service).
• Is visually displayed – prominently on a board, screen, or in the work area – showing chosen measures monitored on an appropriate time basis (hourly, daily, weekly).

Examples of Measures

Daily/shift production, number of rejects, daily shipments, stoppages/interruptions per hour, schedule adherence, lead time, cost of wastage, quantum of improvements – all can be captured on a visual board.

Schematic Representation

In a manufacturing (or service) work area, a visual display board is placed alongside the workspace. For example, the board might show three measures: Quality, Lead Time, and Schedule Adherence, plotted over time. The group of employees uses this data to investigate and implement improvements.

Feature	How it satisfies the three pillars
Data-driven	Real metrics are plotted and analysed.
Employee-centred	Operators collect and plot the data themselves.
Continuous	Regular (e.g., weekly) meetings review and act on the trends.

Options for Visual Control Systems

• Prominent display boards with charts.
• Andon lights: coloured lights (red/yellow/green) that signal status (e.g., stop production, need help, normal).
• Floor paintings: visual demarcation of areas, paths, or inventory levels.
• Colour coding: e.g., red paint on a stack of steel sheets marks safety stock level; yellow marks reorder level; green indicates sufficient inventory.
• Kanban cards: visual signals for pull production.
• Poka-yoke (fool-proofing) devices: often visual, preventing errors.
• Electrical signals and other creative solutions.

Exam tip: The key is that options are limited only by creativity. Any visible indicator that triggers action qualifies.

Worked Example: Oil Waste Reduction

In a factory using machine tools with high-speed lubricant oil, excessive oil wastage occurred. The operating team set up a visual control board monitoring oil consumption (in monetary terms). Seeing the trend, they fabricated a simple gravity-based structure from slotted steel angles:

• Drilled angles are welded into a sloped trough.
• Collection trays are placed on both sides to catch dripping oil.
• After machining, components are placed on top of the sloped structure instead of on a pallet.
• Oil drips down the slope into the trays.

Result: Within the first month, 80% of the wasted oil was recovered – a huge saving. The idea came from the employees themselves, not from industrial engineers (who later built a more sophisticated version).

This example shows how visual control aids engage employees with the problem, capture their mind-space, and push them into thinking about solutions. They complement productivity improvement and waste elimination by fostering ownership.

Key Takeaways

• Visual control systems are data-driven, employee-centred, and continuous.
• They display real-time trajectory of key metrics, not just final outcomes.
• Options include boards, Andon lights, floor markings, colour codes, Kanban, Poka-yoke.
• The oil recovery example demonstrates how employee-driven visual controls can yield immediate, large savings.
• Visual aids capture attention and stimulate problem-solving on the shop/office floor.

---

Implementation Challenges in Lean Management

All concepts covered so far (JIT, Lean, Pull Scheduling, Process Mapping) are simple – even obvious. Yet the track record of implementation is poor. Why?

Two core features of improvement:

1. Desire for excellence is a cultural issue – it must be invested in as a habit, not a technology.
2. God is in the details – improvement is data-intensive, time-consuming, patient work. No shortcuts.

Three Key Challenges

Challenge	Description
Starting Trouble	Difficulty transitioning from knowledge to practice. Even with willingness, people don’t know how and where to apply the ideas.
Midway Breakdown	After a start, top management commitment may fade, leaving middle management squeezed between targets, status quo, and change pressures.
End-of-the-Road Syndrome	After initial successes (e.g., clean shop floor, reduced inventory), the organization feels “everything is done” and sees no further areas for improvement.

Middle Management Issues

Common complaints from middle managers:

• “We are not familiar with the tools.”
• “It's not my job; no one feels motivated.”
• “We do not feel empowered.”
• “Department is too busy.”
• “We can’t communicate well with other areas.”

How to Address End-of-the-Road Syndrome

Expand the improvement journey along three dimensions:

flowchart LR
    A[Current state: shop floor improvements] --> B[Step out of shop floor]
    A --> C[Step out of own organization]
    A --> D[Step out of current mindset]
    B --> E[Improve office, service, customer support areas]
    C --> F[Expand to supply chain]
    D --> G[Identify future domains of value creation]

Reasons Why Implementation Fails Despite Simple Concepts

• Gap between preach and practice: when leadership talks lean but behaves oppositely.
• Lack of stamina: improvement requires enormous, sustained effort.
• Leading is difficult: top management must lead from the front.
• Empowerment issues: middle management may refuse empowerment, or top management holds control tightly.
• Tunnel vision: top management lacks long-term perspective; cultural change is a long affair.
• Crisis paradox: either when there is no crisis (complacency) or when crisis is so severe that improvement efforts are deferred.

Exam tip: The three challenges (Starting Trouble, Midway Breakdown, End-of-the-Road Syndrome) are high-yield. Remember the middle management complaints and the three “step out” directions for overcoming End-of-the-Road.

Key Takeaways

• Concepts are simple, but implementation is difficult due to cultural and detail-oriented nature.
• Three key challenges: Starting Trouble, Midway Breakdown, End-of-the-Road Syndrome.
• Middle management faces tool unfamiliarity, lack of empowerment, and time pressures.
• To escape End-of-the-Road: step out of shop floor, step out of organization, step out of current mindset.
• Failure often stems from preach-practice gaps, insufficient stamina, poor leadership, and short-term thinking.

Project Management

Organizations perform work to create value. Work is classified into operations and projects.

• Operations: Ongoing, repetitive, day-to-day activities (e.g., running metro services, ticketing, regular maintenance).
• Projects: Temporary, unique endeavours with a defined start and end, aimed at creating a unique product, service, or output (e.g., building a new metro corridor, upgrading stations, implementing new signalling systems).

Example – Delhi Metro Rail Corporation (DMRC):
Operations = running trains daily, fare collection, routine maintenance.
Projects = constructing a new line, modernising ticketing technology.

Project Management Goals – The Four Dimensions (Q, C, D, F)

The same four competitive dimensions from operations (Quality, Cost, Delivery, Flexibility) apply to projects, reinterpreted:

Dimension	Project Interpretation
Delivery (D)	Complete the project by the agreed due date.
Cost (C)	Meet the predefined budget; manage resources efficiently.
Quality (Q)	Output meets required performance standards and specifications.
Flexibility (F)	Ability to adapt to necessary changes (from clients, environment) without compromising D, C, or Q.

Why Projects Fail (Time and Cost Overruns)

Common reasons (from business media) for exceeding budgets or missing deadlines:

• Inadequate preparation and planning
• Inaccurate time/cost estimates
• Lack of knowledge or technical talent
• Wrong site choice
• Insufficient infrastructure/equipment
• Regulatory changes
• Funding constraints

Project Life Cycle – The S‑Curve

flowchart LR
    S[Start – slow] --> M[Quick momentum] --> F[Slow finish]

When plotting % of project completed vs. time, the curve is S‑shaped:

1. Slow start – Team learns specifications, scope, new tools/methods; initial planning, resource mobilisation, site preparation consume time.
2. Quick momentum – Groundwork complete; actual work (construction, coding, installation) occurs; workflows stabilised, resources fully utilised, productivity peaks.
3. Slow finish – Testing, module integration, quality checks, documentation, final approvals, handover activities slow progress.

Exam tip: The S‑curve explains why early delays often amplify – the slow start is natural, but inadequate planning can extend it and jeopardise the momentum phase.

Project Network Diagrams

A project network diagram visually represents the sequence and dependencies of activities. It is used to determine the total project duration, identify the critical path, and manage schedule risk.

Steps to Construct (from Activity Data)

1. List all activities with their predecessor(s) and duration.
2. Represent each activity as a circle (node) labelled ActivityName (Duration).
3. Draw arrows from each predecessor to its dependent activity.
4. Place activities with no predecessor at the start; activities with multiple predecessors wait until all are complete.

Worked Example (Transcript Data)

Note: The spoken example from the lecture provided durations for most activities but omitted durations for activities B and G. The network diagram below reconstructs the given information faithfully; missing durations are marked ?.

Activity	Duration (weeks)	Predecessor(s)
A	6	– (none)
B	?	A
C	7	B
D	2	A
E	4	D
F	10	E
G	?	– (none)
H	10	G
I	6	H, J
J	13	– (none)
K	9	A
L	3	C, K
M	5	I, L

Constructed network diagram (arrows represent “→ starts after”):

A(6)
├──→ B(?) ──→ C(7) ──┬──→ L(3) ──┐
├──→ D(2) ──→ E(4) ──→ F(10)      │
├──→ K(9) ──────────→ L(3) ──────→ M(5)
G(?)
└──→ H(10) ──┬──→ I(6) ──────────→ M(5)
J(13) ──────→ I(6)

The diagram shows all dependencies. Because durations for B and G are unknown, the total project duration cannot be computed from the transcript alone.

Exam tip: When building a network diagram, ensure all predecessors are satisfied before an activity can start. Missing durations are common in exam questions – you will be given a complete data table.

Key Takeaways

• Projects are temporary and unique; operations are ongoing and repetitive.
• Project success is judged on the same four dimensions as operations: quality, cost, delivery, flexibility.
• The project life cycle follows an S‑curve: slow start → rapid momentum → slow finish.
• A project network diagram maps activity dependencies and durations; it is essential for schedule analysis.
• When constructing a diagram, place activities in the order of dependencies and label each node with its activity name and duration.

Key Definitions

• Early Start (ES) – the earliest possible time an activity can begin, given predecessor constraints.
• Early Finish (EF) – the earliest time an activity can complete (ES + duration).
• Late Start (LS) – the latest time an activity can start without delaying the entire project.
• Late Finish (LF) – the latest time an activity can finish without delaying the project.
• Slack (or Float) – the amount of time an activity can be delayed without affecting project completion.
  • $\text{Slack} = \text{LF} - \text{EF} = \text{LS} - \text{ES}$
• Critical Path – the sequence of activities with zero slack; its total duration determines the project’s minimum completion time. Any delay on a critical activity directly delays the project.

Forward Pass – Computing ES and EF

Procedure:

1. Start from the beginning node(s). Set ES = 0 for any activity with no predecessor.
2. For each activity, $\text{EF} = \text{ES} + \text{Duration}$
3. For a successor activity, $\text{ES} = \max(\text{EF of all immediate predecessors})$
4. The project completion time is the maximum EF among all ending nodes.

Exam tip: In a forward pass, the ES of a merge point equals the largest EF among its predecessors – you wait for the longest preceding path.

Worked example – given network (activities and durations in weeks)

Activity	Duration	Immediate Predecessors
A	6	–
K	9	A
B	4	A
C	7	B
L	3	K, C
D	2	A
E	4	D
F	10	E
G	2	–
H	10	G
J	13	–
I	6	H, J
M	5	L, I

Forward pass calculations (left to right):

• A: ES = 0, EF = 0+6 = 6
• K: ES = max(EF of A) = 6, EF = 6+9 = 15
• B: ES = 6, EF = 6+4 = 10
• C: ES = max(EF of B) = 10, EF = 10+7 = 17
• L: ES = max(EF of K, EF of C) = max(15,17) = 17, EF = 17+3 = 20
• D: ES = 6, EF = 6+2 = 8
• E: ES = max(EF of D) = 8, EF = 8+4 = 12
• F: ES = max(EF of E) = 12, EF = 12+10 = 22
• G: ES = 0, EF = 0+2 = 2
• H: ES = max(EF of G) = 2, EF = 2+10 = 12
• J: ES = 0, EF = 0+13 = 13
• I: ES = max(EF of H, EF of J) = max(12,13) = 13, EF = 13+6 = 19
• M: ES = max(EF of L, EF of I) = max(20,19) = 20, EF = 20+5 = 25

Project completion time: max(EF of F, EF of M) = max(22,25) = 25 weeks.

Backward Pass – Computing LS and LF

Procedure:

1. Start from the ending node(s). Set LF equal to the project completion time (25 weeks).
2. For each activity, $\text{LS} = \text{LF} - \text{Duration}$
3. For a predecessor activity, $\text{LF} = \min(\text{LS of all immediate successors})$

Backward pass calculations (right to left):

• M: LF = 25, LS = 25−5 = 20
• F: LF = 25, LS = 25−10 = 15
• E: successor F → LF = LS of F = 15, LS = 15−4 = 11
• D: successor E → LF = 11, LS = 11−2 = 9
• I: successor M → LF = 20, LS = 20−6 = 14
• J: successor I → LF = 14, LS = 14−13 = 1
• H: successor I → LF = 14, LS = 14−10 = 4
• G: successor H → LF = 4, LS = 4−2 = 2
• L: successor M → LF = 20, LS = 20−3 = 17
• C: successor L → LF = 17, LS = 17−7 = 10
• B: successor C → LF = 10, LS = 10−4 = 6
• K: successor L → LF = 17, LS = 17−9 = 8
• A: successors K, B, D → LF = min(LS of K, B, D) = min(8,6,9) = 6, LS = 6−6 = 0

Slack and Critical Path

Slack = LF − EF (or LS − ES). Summarising all activities:

Activity	Dur	ES	EF	LS	LF	Slack
A	6	0	6	0	6	0
B	4	6	10	6	10	0
C	7	10	17	10	17	0
L	3	17	20	17	20	0
M	5	20	25	20	25	0
K	9	6	15	8	17	2
D	2	6	8	9	11	3
E	4	8	12	11	15	3
F	10	12	22	15	25	3
G	2	0	2	2	4	2
H	10	2	12	4	14	2
J	13	0	13	1	14	1
I	6	13	19	14	20	1

Critical Path: A → B → C → L → M (all slack = 0).
Duration = 6 + 4 + 7 + 3 + 5 = 25 weeks – matches project completion.

flowchart LR
    A(("A<br/>ES:0 EF:6<br/>LS:0 LF:6<br/>Slack:0")) --> B(("B<br/>6->10<br/>6->10<br/>0"))
    B --> C(("C<br/>10->17<br/>10->17<br/>0"))
    C --> L(("L<br/>17->20<br/>17->20<br/>0"))
    L --> M(("M<br/>20->25<br/>20->25<br/>0"))
    A --> K(("K<br/>6->15<br/>8->17<br/>2"))
    K --> L
    A --> D(("D<br/>6->8<br/>9->11<br/>3"))
    D --> E(("E<br/>8->12<br/>11->15<br/>3"))
    E --> F(("F<br/>12->22<br/>15->25<br/>3"))
    G(("G<br/>0->2<br/>2->4<br/>2")) --> H(("H<br/>2->12<br/>4->14<br/>2"))
    H --> I(("I<br/>13->19<br/>14->20<br/>1"))
    J(("J<br/>0->13<br/>1->14<br/>1")) --> I
    I --> M

Exam tip: The critical path is the longest path through the network – it governs project duration. Non‑critical activities have positive slack; they can slip within that slack without delaying the whole project.

Connection to Process Bottlenecks

The critical path is the project’s equivalent of a process bottleneck: it determines the maximum throughput (minimum completion time). Just as the resource with the least capacity constrains a process, the critical path – the longest sequence of dependent activities – constrains the project duration. Activities on the critical path are critical; any delay there directly lengthens the project.

Key Takeaways

• Forward pass: ES = max(EF of predecessors); EF = ES + duration. Project completion = max(EF of ending nodes).
• Backward pass: LF = min(LS of successors); LS = LF − duration. Start with LF = project completion at ending nodes.
• Slack = LF − EF = LS − ES. Zero slack → critical.
• Critical path is the longest path; it defines the minimum project duration (25 weeks in the example).
• More than one critical path can exist – all must be managed as bottlenecks.

Critical Path Identification: Alternate Path Enumeration Method

Finding the critical path (the sequence of activities that determines the shortest possible project duration) can be done by computing slack from early/late starts and finishes (the method covered earlier). However, for small-scale networks a more intuitive approach works: enumerate all possible paths from the start node to the end node, sum the durations of activities on each path, and identify the path with the longest total duration. That path is the critical path, and its duration equals the project duration.

Worked example: Six-activity network (A–M)

Paths and durations (durations in weeks):

Path	Activities	Duration (weeks)
1	A → B → C → L → M	$6+4+7+3+5 = 25$
2	J → I → M	$13+6+5 = 24$
3	G → H → I → M	(not computed in transcript, assumed ~23)
4	A → D → E → F	$6+2+4+10 = 22$
5	A → K → L → M	(not computed in transcript, assumed ~23)

The longest duration is 25 weeks (Path 1). Therefore:

• Critical path: A → B → C → L → M
• Project duration: 25 weeks

This result matches the slack-based analysis from the previous video, confirming Path 1 as the critical path.

Exam tip: Path enumeration is efficient only when the network has few paths. For large, complex networks (many activities, many dependencies), enumerating all paths becomes impractical. The slack method (early/late start/finish) scales better.

Comparison: Enumeration vs. Slack Method

Method	When to use	Strength	Drawback
Path enumeration	Small networks (e.g., ≤ 10 activities, few merge points)	Intuitive, fast manual calculation	Exponentially more paths as network grows
Slack (forward/backward pass)	Any size	Systematic, works for complex networks	More computation steps

Key takeaways

• The critical path is the longest path through the project network.
• Its length gives the minimum project duration.
• For small networks, list all start-to-end paths, sum durations, pick the max.
• For large networks, compute slack (zero-slack activities lie on the critical path).

---

Project Cost Structures and Cost-Time Trade-Offs

Projects involve two broad categories of cost, and managers must balance them to find the optimal project duration.

Direct Costs

Direct costs are expenses directly tied to executing project activities: labour wages, equipment rental, materials, overtime, and the cost of accelerating an activity (e.g., using air freight instead of sea freight, hiring specialist consultants, renting extra machines).

• If the project runs slowly (long duration), fewer resources are used per week → low direct cost.
• If the project is accelerated (short duration), more resources are packed into each week → high direct cost.

Indirect Costs

Indirect costs are general overheads of running the project itself: site office, supervision salaries, utilities, project management team, interest on blocked capital, and opportunity cost (lost revenue due to project delay).

• Indirect costs increase as project duration increases (longer overhead period).

Total Cost and Optimal Duration

Total cost = Direct cost + Indirect cost. The trade-off is:

• Very short project → direct cost dominates (high acceleration expenses).
• Very long project → indirect cost dominates (high overhead).

The optimal project duration minimises the total cost.

flowchart TD
    subgraph Cost vs. Duration
        A[Project Duration] -- "Shorter duration" --> B[Direct cost rises]
        A -- "Longer duration" --> C[Indirect cost rises]
        B & C --> D[Total cost = Direct + Indirect]
        D --> E[U-shaped total cost curve]
        E --> F[Optimal duration at minimum total cost]
    end

Crashing: Accelerating Activities

Crashing means reducing an activity’s duration by spending additional direct cost. Each activity has a crash time (the shortest technically feasible duration) beyond which it cannot be reduced, no matter how much money is spent. The cost per week of accelerating is the extra direct cost incurred for each week saved.

Example dataset (from the transcript's ongoing example)

Activities A–M have current durations and crash data. For illustration:

• Activity B: current time 4 weeks, crash to 3 weeks costs ₹700 per week saved.
• Activity F: current 10 weeks, can be crashed down to a minimum of 7 weeks, each week saved costs ₹500.
• Indirect cost: ₹1000 per week of project duration (overall project overhead).

Exam tip: The cost of accelerating an activity is a direct cost increase. The trade‑off is between paying more to crash (direct) vs. paying less overhead (indirect) because the project finishes earlier. The goal is to minimise total cost.

Key takeaways

• Direct cost: cost of executing and accelerating activities. Rises when project is shortened.
• Indirect cost: project overhead. Rises when project is extended.
• Total cost = Direct + Indirect. The optimal duration balances these.
• Crash time is the minimum possible duration for an activity; crashing costs extra per week.
• The optimal project duration is found by comparing direct cost increases from crashing against indirect cost savings.

Cost-Time Trade-off in Project Networks

Project crashing is the process of reducing the total project duration by accelerating individual activities, at some cost. The goal is to find the optimal project duration that minimises the sum of direct costs (crashing) and indirect costs (overheads).

1. Two Cost Structures

• Direct cost – the cost of crashing or accelerating a single activity (e.g., overtime, extra labour, equipment). This cost is incurred per week of reduction.
• Indirect cost – overheads of the project (rent, supervision, utilities) that accrue per unit of time – here, ₹1000 per week.

The trade-off: crashing reduces indirect cost (shorter project → fewer overhead weeks) but increases direct cost (pay to speed up activities). The optimal duration is where total cost (direct + indirect) is minimised.

2. Crashing Rules

Crashing is performed one week at a time on the critical path (the longest path in the network, which determines project duration).
Only crashable activities may be reduced – some cannot be crashed (e.g., A and M in this example) or cannot be crashed below a minimum technical time (e.g., L minimum = 2 weeks).

Decision rule at each step:
Crash the crashable activity on the critical path with the lowest crashing cost per week.

Exam tip: Always re-identify the critical path after every crash – the set of critical paths may change, creating multiple bottlenecks.

---

Worked Example: From 25 Weeks to Optimal 23 Weeks

Initial project data (same as previous lecture):

• Activity durations, predecessors, and the project network are already defined.
• Critical path: A→B→C→L→M, duration = 25 weeks.
• Only activities B, C, L are crashable on that path (A and M not crashable).

Activity	Normal Duration	Crash Cost per Week	Minimum Time (cannot go below)
B	4 weeks	₹700	2 weeks
C	7 weeks	₹500	unknown
L	3 weeks	₹300	2 weeks

• Indirect cost = ₹1000 per week.

Step 1 – Crash L (₹300/week) → duration 25 → 24 weeks

• Benefit: project shorter by 1 week → save ₹1000 indirect cost.
• Net gain = ₹1000 – ₹300 = ₹700.
• Update network: L now 2 weeks. Recompute all paths.

New critical paths (both 24 weeks):

1. A–B–C–L–M
2. J–I–M (J=13, I=6, M=5? Actually JIM path originally 13+6+5=24? Wait, check: transcript says after first crash, two critical paths: ABCLM=24 and JIM=24. We'll trust data.)

Crashable activities now: On path 1: B (700), C (500). On path 2: J (400), I (700). L already at minimum.

Step 2 – Crash C (₹500) and J (₹400) simultaneously → duration 24 → 23 weeks

• Why both? To reduce project duration, both critical paths must be shortened by 1 week each.
• Choose lowest-cost on each: C (500) on path 1, J (400) on path 2.
• Total crashing cost = 500 + 400 = ₹900.
• Benefit: save ₹1000 indirect cost (1 week).
• Net gain = ₹1000 – ₹900 = ₹100.
• Update: C now 6 weeks, J now 12 weeks.

New critical paths (all 23 weeks):

1. A–B–C–L–M
2. G–H–I–M (GHIM) – now appears as critical
3. J–I–M (JIM)

(Actually JIM was 23, GHIM also 23, ABCLM 23.)

Step 3 – Consider further crash to 22 weeks

Now three critical paths. To reduce project duration, each path must be shortened by 1 week.

Crashable activities:

Path	Crashable activities (and cost per week)
ABCLM	B (700), C (500) – L already crashed to minimum
GHIM	H (200), I (700) – G not crashable
JIM	J (400), I (700)

Strategy options:

• Crash a common activity on two paths (e.g., crash I, which lies on both GHIM and JIM) – cost ₹700. Then crash C on ABCLM (₹500). Total = ₹1200.
• Crash non-common activities – on GHIM crash H (₹200), on JIM crash J (₹400), on ABCLM crash C (₹500). Total = ₹1100.

The cheaper option is the second: crash H, J, and C at total direct cost ₹1100.

• Benefit: save ₹1000 indirect.
• Net loss = ₹1000 – ₹1100 = –₹100.

Since net loss arises, do not crash further. The optimal project duration remains 23 weeks.

---

Summary of the Crashing Process

flowchart TD
    A[Start: project normal duration] --> B[Identify critical path(s)]
    B --> C{Any crashable activity<br>on at least one critical path?}
    C -->|Yes| D[Select cheapest crash option(s)<br>to reduce all critical paths by 1 week]
    D --> E[Compute net benefit:<br>Indirect saving - Direct cost]
    E --> F{Net benefit ≥ 0?}
    F -->|Yes| G[Crash, update network,<br>recompute critical paths]
    G --> B
    F -->|No| H[Optimal duration reached]
    C -->|No| H
    H --> I[Stop]

Exam tip: When multiple critical paths exist, you must reduce all of them by the same amount to shorten the project. Crashing only one path leaves the project duration unchanged.

---

Key Takeaways

• Direct cost = cost to crash an activity (per week); indirect cost = overhead per week (here ₹1000).
• Always crash the cheapest activity on the critical path first, but only if the net benefit (indirect saving minus crash cost) is positive.
• After each crash, recompute critical paths – they can multiply.
• When multiple critical paths appear, you need to crash one activity on each path (or a common activity) to reduce project duration.
• The optimal project duration is the point where an additional crash yields a net loss (total cost increases). In this example, it is 23 weeks.
• Activities have minimum technical times – cannot be crashed beyond that limit.

Gantt Charts

Gantt Charts are a visual tool that display project activities along a time dimension. They complement the project network diagram (critical path method) by showing when each activity starts and finishes, and which activities run in parallel. The X-axis represents time; the Y-axis lists the project activities.

Reading the Gantt Chart

• Each activity is drawn as a horizontal bar spanning its start to finish time.
• The total length of the bar equals the activity’s duration.
• Activities on the critical path appear as a continuous chain with no gaps between them. Their combined duration equals the project duration.
• Non‑critical activities may have slack — gaps before or after their bar where they can shift without delaying the project.

Visualizing the Critical Path

From the earlier analysis (forward/backward pass, slack calculation), the critical path was A → B → C → L → M, with durations 6, 4, 7, 3, 5 weeks respectively.

• Project duration = $6 + 4 + 7 + 3 + 5 = 25$ weeks.
• On the Gantt chart, these five bars appear sequentially (no overlap, no gaps). The total time from start of A to finish of M is 25 weeks.

gantt
    title Gantt Chart – Critical Path (A, B, C, L, M)
    dateFormat  W
    axisFormat %W
    section Critical
    A : a, 0, 6w
    B : b, after a, 4w
    C : c, after b, 7w
    L : l, after c, 3w
    M : m, after l, 5w

Exam tip: The critical path is the longest chain of activities with zero slack. Any delay on a critical path activity directly delays the entire project.

Non‑Critical Paths and Slack

Take path A → D → E → F (non‑critical). On the Gantt chart, these bars may have gaps or start later than their predecessor.

• If activity E is delayed by 1 week, the bar shifts right, but because E has slack, the overall project duration remains 25 weeks.
• Discipline: Non‑critical activities can absorb small delays as long as the delay does not exceed their slack. Only delays on the critical path lengthen the project.

Resource Mapping and Parallelism

The Gantt chart reveals which activities are scheduled in parallel — a critical insight for resource allocation.

• At a given time, multiple bars may be running concurrently.
• For example, activities B and D may overlap in time. If both require the same specialised team, one team cannot execute both simultaneously. You need either multiple teams or must re‑schedule one activity to avoid overlap.

Time period	Number of parallel activities
Early weeks	5 (example)
Mid weeks	4
Later weeks	2–3

• The chart helps identify resource bottlenecks and decide whether to add parallel teams or sequence activities differently.

Key Takeaways

• Gantt chart = time‑based visual of project activities (X‑axis = time, Y‑axis = activities).
• The critical path appears as a continuous, gap‑free chain; its total duration = project duration.
• Slack on non‑critical paths allows small delays without affecting the project finish.
• Delaying a critical path activity always delays the project; delaying a non‑critical activity may not.
• Parallel activities in the Gantt chart imply parallel resource needs — one team cannot cover overlapping activities if the same skill is required.
• Gantt charts complement network diagrams by adding the time dimension and resource visibility.

Components of a Supply Chain

A supply chain is the network of entities and activities that deliver a product to the end customer. Intuitively: every morning’s milk carton has a long journey behind it — from farm to plant to shop. Understanding the components of that journey reveals the three universal building blocks of any supply chain.

The Mother Dairy Example (Worked Example)

Consider how fresh milk reaches Delhi households at 6 a.m.:

• Procurement (Inbound): Mother Dairy sources raw milk from hundreds of cooperatives across Punjab, Rajasthan, Uttar Pradesh, Haryana, and Gujarat. The milk is transported to the Patparganj plant in East Delhi.
• Processing (In-house): The plant homogenises, pasteurises, and stores milk in large tanks. Capacity: 650,000 litres per day. Products include skimmed, toned, double-toned, full cream milk (in half- and one-litre packs), plus 30+ ice‑cream flavours and other dairy items.
• Distribution (Outbound): Nearly 100 tankers criss‑cross Delhi, supplying:
  • 600 booths
  • 200 manually operated containers (loose milk in congested areas)
  • 400 delivery agents (home delivery)
  • 850 retail shops (polythene packs)

These three stages — inbound, in-house, and outbound — form the supply chain.

Three Generic Components of Any Supply Chain

Component	Also called	What it includes	Example (Mother Dairy)
Inbound supply chain	Procurement, inbound logistics	Supplier identification, strategic sourcing, supply management, raw material transport	Milk cooperatives → Patparganj plant
In-house supply chain	Manufacturing, internal logistics	Material handling, master scheduling, material requirements planning (MRP), capacity layout, production	Homogenising, pasteurising, packaging
Outbound supply chain	Distribution, outbound logistics	Warehousing, channel management, 3PL/4PL, delivery to end customer	Tankers → booths / retailers / home delivery

Exam tip: Any supply chain, regardless of industry (manufacturing, healthcare, services), can be decomposed into these three components. Memorise the labels and their typical issues — they are a frequent exam frame.

Key takeaways

• A supply chain consists of three components: inbound (sourcing), in-house (processing), outbound (distribution).
• The Mother Dairy example illustrates each component with concrete numbers and entities.
• Inbound issues: supplier development, strategic sourcing, supply management.
• In-house issues: master scheduling, MRP, capacity planning, material handling.
• Outbound issues: warehousing, distribution, channel management, third‑party logistics.

---

Supply Chain Structure

Supply chain structure refers to the entities involved in delivering goods and services to the ultimate customer, their relative positioning, roles, and responsibilities. It also determines the nature and volume of information flow and material flow across the chain.

Layers of a Supply Chain

A typical structure has multiple layers (or tiers) from the original supplier to the final customer. In the diagram below, there are six layers (supplier + 4 intermediaries + customer):

flowchart LR
    subgraph Upstream
        S[Supplier]
    end
    subgraph Chain
        S --> L1[Tier 1 Supplier]
        L1 --> L2[Tier 2 Supplier] 
        L2 --> F[Factory]
        F --> W[Factory Warehouse]
        W --> D[Distributor]
        D --> R[Retailer]
        R --> C[Customer]
    end
    subgraph Downstream
        C
    end

• Upstream (material flows toward the customer): from supplier to customer.
• Downstream (information flows toward the supplier): customer → retailer → distributor → … → supplier.

Note: In made‑to‑order or turnkey environments, retailers and distributors may be absent — the product goes directly from factory to customer. However, the three‑component decomposition still holds.

Information and Material Flows

In a multi‑layer chain, each layer operates with a review cycle and processing delay, causing cumulative lead time.

Information flow (upstream) — example timings:

Layer	Review frequency	Order transmission time
Retailer	Every 7 days	1–2 days
Distributor	Every 5 days	2 days
Factory warehouse	—	1 day (order entry)
Factory (internal)	Variable	2 days to send to supplier

Material flow (downstream) — example timings:

Layer	Preparation time	Transit time	Other
Supplier	3 days	2 days	—
Factory stores	—	—	Receiving, inspection
Manufacturing	26 days (lead time)	1 day to factory warehouse	—
Factory → Distributor	—	1 day	—
Distributor → Retailer	—	varies	—
Retailer → Shelf	—	paperwork + stacking	—

The total lead time to fulfil a customer order is the sum of all delays across layers — information flows upstream, then material flows downstream. Each layer adds its own delay, so the structure directly impacts responsiveness.

Exam tip: Be ready to compute total lead time by adding all review, processing, and transit times. A common trap is forgetting that information must flow upstream before material can flow downstream — both contribute to the delay.

Additional Issues in Supply Chain Management

Beyond the three components, managers must address:

• Designing an appropriate supply chain structure (number and role of layers).
• Inventory planning and control.
• Performance metrics for the chain.

Key takeaways

• Structure defines the number of layers (tiers) and the flow of information (upstream) and material (downstream).
• Each layer introduces its own review frequency and processing delay, accumulating total lead time.
• Information must travel from customer to supplier before material can return — this double flow creates the total order‑to‑delivery delay.
• Supply chain management also encompasses structure design, inventory control, and performance measurement.

Bullwhip Effect in Supply Chains

The bullwhip effect describes how a small change in downstream demand (e.g., from customers) becomes increasingly amplified as orders travel upstream through the supply chain — like the crack of a whip. This distortion causes excessive inventory, poor demand management, and operational inefficiency.

Observations from the Beer Game

The Beer Game is a simulation (24–40 weeks) that reproduces real-world supply chain fluctuations. A typical result:

• Customer order: 4 crates/week (weeks –2 to 4) → increases to 8/week from week 5.
• Retailer orders from wholesaler: peaks at 20.
• Wholesaler orders from factory warehouse: peaks at 45.
• Factory orders from raw-material supplier: peaks at 68.

Plot of order quantities across layers:

flowchart LR
    C[Customer: 4→8] --> R[Retailer peak: 20]
    R --> W[Wholesaler peak: 45]
    W --> F[Factory peak: 68]

Backlogs also vary both in magnitude and timing (phase lag): e.g., factory backlog peaks at week 16, next layer at week 17.

Key Observations

1. Downstream demand is amplified upstream (4 → 68).
2. All levels experience the effect, though in different magnitudes.
3. The farther from the end customer, the greater the amplitude.
4. Phase lag exists — peaks occur at different times across layers.
5. Demand becomes mixed with noise as it travels upstream.

Causes of the Bullwhip Effect

Three structural drivers:

• Number of layers – more layers → more amplification.
• Delay – finite transit and communication delays between layers.
• Rate of change – larger demand fluctuations trigger stronger whip.

Behavioural and policy factors:

• Each layer uses its own forecast (not shared).
• Order timing differs (e.g., weekly vs. bi‑weekly reviews).
• Price fluctuations and promotions create artificial demand surges.
• Rationing of supply during shortages – buyers inflate orders to secure a larger share.

Exam tip: The bullwhip effect is tested by explaining why a small consumer change (4→8) leads to huge upstream swings (68). Memorise the Beer Game numbers and the five observations.

Methods of Reducing the Bullwhip Effect

Approach	Specific Tactics
Minimise layers	Use 3PL/4PL logistics (third‑/fourth‑party logistics) and electronic markets (internet‑based direct sales) to bypass intermediaries.
Reduce delays	Cut lead times and fixed ordering costs — lower fixed costs reduce batching and thus dampen order variability.
Improve demand intelligence	- Point‑of‑Sale (POS) data – immediate demand signal to manufacturer.<br>- Electronic Data Interchange (EDI) – seamless, real‑time information sharing.<br>- Share sales, capacity, and inventory data across partners.<br>- Invest in better demand forecasting and management systems.
Smooth demand patterns	Use everyday low pricing (EDLP) to avoid price‑driven surges.

Exam tip: “Everyday low pricing” is a classic real‑world countermeasure – link it directly to removing promotion‑induced bullwhip.

Key takeaways

• Bullwhip effect: small downstream changes → large upstream swings (4→68).
• Caused by layers, delays, rate of change, and behavioural factors (own forecasts, different order timing, promotions, rationing).
• Remedies: reduce layers (3PL, e‑commerce), cut delays (EDI, POS), share data, and stabilise pricing.

---

Inventory in Supply Chains

Inventory exists throughout a supply chain (manufacturing, retail, hospitals, hotels) due to both external and internal factors. Managing these six types is critical for operational efficiency.

Reasons for Inventory

flowchart TD
    A[Inventory Exists] --> B[External Factors]
    A --> C[Internal Factors]
    B --> D[Demand fluctuations → Seasonal inventory]
    B --> E[Price fluctuations → Hedging inventory]
    C --> F[Operational policy]
    C --> G[Design of operations]
    F --> H[Cyclic inventory]
    F --> I[Safety stock]
    F --> J[Pipeline inventory]
    G --> K[Decoupling inventory]

External Factors

Factor	Inventory Type	Example
Demand fluctuations (e.g., seasonality)	Seasonal inventory	Retailers stock up for holiday peaks.
Price fluctuations (e.g., commodity prices)	Hedging inventory	Airlines buy fuel forward when crude oil prices are low.

Internal Factors

Category	Inventory Type	Description
Operational policy	Cyclic inventory	Inventory that cycles with each order batch (e.g., order 100 units, consume to 0, reorder).
	Safety stock	Buffer against demand or supply uncertainties (demand variability, supply lead‑time changes, quality issues).
	Pipeline inventory	Inventory in transit or processing – required for the total lead time (e.g., 7 days lead time → 7 days of pipeline stock).
Design of operations	Decoupling inventory	Held between stages of production to allow independent operation (e.g., buffer between assembly lines).

Key takeaways

• Inventory exists for six distinct reasons: seasonal, hedging, cyclic, safety, pipeline, decoupling.
• External drivers: demand and price fluctuations.
• Internal drivers: operational policies (ordering patterns, uncertainty buffers, lead‑time stocks) and system design (decoupling).
• Understanding each type helps tailor inventory policies to the specific source of variability.

Why organizations hold inventory

Inventory is deliberately placed in supply chains to manage complexity, uncertainty, and timing differences. Six distinct categories emerge from the discussion.

1. Decoupling inventory – Splits a long production process into independent stages.
A 10‑station production line is complex: a problem at station 3 disrupts downstream stations. By grouping stations into stages (stations 1–3, 4–7, 8–10) and holding inventory between stages, each stage can operate semi‑independently. This reduces the impact of local disruptions and simplifies control.

Decoupling inventory is a design choice – the system is deliberately split.

2. Cyclic inventory – Arises from ordering in batches rather than continuously.
Every time an order of size $Q$ arrives, it is consumed at a steady rate. A new order is placed when stock reaches a reorder point, creating a repeating sawtooth pattern. Cyclic inventory is the stock that cycles through between order arrivals.

3. Pipeline inventory – Exists because of lead time.
When an order is placed, it takes time (lead time) to arrive. During that interval, consumption continues. Pipeline inventory is the quantity already in transit or in process; its average equals the demand during the lead time.

4. Safety stock – Buffers against uncertainty in demand, supply quantity, lead time, or quality.
Safety stock is held above the normal cycle stock. The sawtooth pattern sits on top of a baseline of safety stock that is never intentionally consumed under normal conditions.

5. Hedging inventory – Used to protect against price fluctuations (e.g., in international commodity markets).
The goal is to ensure material availability at reasonable prices over a long horizon.

6. Seasonal inventory – Absorbs predictable demand peaks and troughs.
Production can be smoothed by building inventory during low‑demand periods to meet high‑demand periods.

From an operational control perspective, the last three categories – cyclic inventory, safety stock, and pipeline inventory – are the most relevant for day‑to‑day planning.

Key takeaways

• Decoupling inventory reduces production complexity; it is a system design choice.
• Cyclic inventory results from batch ordering; its average is $\frac{Q}{2}$.
• Pipeline inventory is due to lead time; its average equals lead‑time demand.
• Safety stock handles uncertainty in demand, supply, or lead time.
• Hedging and seasonal inventory address price volatility and demand seasonality, respectively.
• For routine inventory planning, focus on cyclic, pipeline, and safety stock.

---

The two fundamental decisions

Every inventory planning problem must answer:

1. How much to order? – the order quantity $Q$.
2. When to order? – the reorder point (time or stock level).

Without structured methods, organizations risk both excess inventory (blocking capital, obsolescence) and shortages (stoppages, lost customer goodwill, rush purchases at higher cost).

The three key costs

Cost type	Description	Key components
Ordering cost ($C_o$)	All administrative costs incurred each time an order is placed.	Supplier search, negotiation, price/delivery/terms setting, order monitoring, receiving, quality certification, storage placement; manpower and infrastructure.
Holding (carrying) cost ($C_h$)	Cost of keeping one unit in inventory for a period (typically one year).	Interest on locked‑up capital, warehouse rent, insurance, obsolescence, damage, manpower, infrastructure. Increases with average inventory.
Shortage cost	Cost of running out of stock.	Production disruption, productivity loss, loss of customer goodwill, cancelled orders. Hard to measure directly.

Exam tip: Shortage cost is the hardest to quantify. In many models it is treated as a penalty per unit short or per stockout event.

The planning problem: choose $Q$ and the reorder point so that the total of these three costs is minimised.

Key takeaways

• The two decisions are order quantity (how much) and reorder point (when).
• Three costs: ordering, holding, shortage.
• Ordering cost is incurred per order; holding cost is proportional to average inventory; shortage cost is uncertain but real.
• Unplanned inventory management leads to excess stock, shortages, and emergency costs.

---

Intuition

The EOQ model answers “how much to order” when demand is known and constant. It ignores uncertainty for now. The insight: ordering in large batches reduces ordering cost but increases holding cost; ordering in small batches reduces holding cost but increases ordering cost. An optimal quantity balances the two.

Assumptions

• Demand rate $D$ is constant and known (e.g., annual demand = 10,000 units).
• Lead time is known and constant (for now).
• No quantity discounts.
• Instantaneous replenishment.
• Only ordering and holding costs matter (shortage cost is avoided by ordering exactly in time).

Derivation of total cost

Let:

• $D$ = annual demand (units)
• $Q$ = order quantity (units per order)
• $C_o$ = cost per order ($)
• $C_h$ = holding cost per unit per year ($)

Number of orders per year = $D / Q$
Average inventory = $Q/2$ (assuming consumption from $Q$ to 0)

Total annual cost: $TC(Q) = \frac{D}{Q} C_o + \frac{Q}{2} C_h$

The cost curve is U‑shaped:

flowchart LR
    subgraph Costs
        direction LR
        TC[Total cost] -- sum of --> OC[Ordering cost: D/Q * Co]
        TC -- sum of --> HC[Holding cost: Q/2 * Ch]
    end

The minimum occurs where the two cost components are equal (derivative = 0):

$\frac{dTC}{dQ} = -\frac{D C_o}{Q^2} + \frac{C_h}{2} = 0$

Solving: $Q^* = \sqrt{\frac{2 D C_o}{C_h}}$

This is the Economic Order Quantity (EOQ).

Worked example

Given:

• $D = 10{,}000$ units/year
• C_o = \200$ per order
• Unit cost = $400; holding cost = $16\%$ of unit cost = 0.16 \times 400 = \64$ per unit per year

$Q^* = \sqrt{\frac{2 \times 10{,}000 \times 200}{64}} = \sqrt{\frac{4{,}000{,}000}{64}} = \sqrt{62{,}500} = 250 \text{ units}$

Derived decisions:

• How much? Order 250 units each time.
• When? Number of orders per year $= 10{,}000 / 250 = 40$. Working days per year = 320, so order every $320 / 40 = 8$ working days.
• Total cost:
  Ordering cost: 40 \times 200 = \8{,}000$Holding cost:$(250/2) \times 64 = 125 \times 64 = $8{,}000 **Total = \16,000**

Exam tip: At the EOQ, ordering cost exactly equals holding cost. This is a quick check for correctness.

Robustness of the model

The total cost curve has a flat bottom – small deviations from $Q^*$ do not increase total cost significantly. This means the model is robust: even if parameters are slightly misestimated, the cost penalty is small.

Summary table of the example

Item	Value
Annual demand $D$	10,000
Ordering cost $C_o$	$200
Holding cost $C_h$	$64/unit/year
EOQ $Q^*$	250 units
Orders per year	40
Reorder interval	8 working days
Total annual cost	$16,000

Key takeaways

• EOQ balances ordering and holding costs: $Q^* = \sqrt{2DC_o/C_h}$.
• At $Q^*$, ordering cost = holding cost.
• The total cost curve is flat near the optimum – deviations matter little.
• The model assumes known, constant demand; it provides a foundation for more realistic models (with uncertainty, discounts, etc.).

Intuition: The Ordering vs. Holding Trade-off

A firm sources a product from a supplier to meet customer demand. It must decide how many units to order each time (order quantity (Q)).

• Large (Q) → fewer orders per year (low ordering cost) but high average inventory (high holding cost).
• Small (Q) → low average inventory (low holding cost) but many orders (high ordering cost).

The economic order quantity (EOQ) is the (Q) that minimises total annual inventory cost — the sum of ordering and holding costs.

Cost Components

Let:

• (D) = annual demand (units/year)
• (S) = ordering cost per order ($$$/order)
• (H) = unit holding cost ($$$/unit/year)
• (C) = unit purchase cost ($$$/unit) — fixed, independent of (Q)

Quantity	Expression	Rationale
Number of orders per year	(\frac{D}{Q})	Total demand divided by batch size
Annual ordering cost	(\frac{D}{Q} \cdot S)	Number of orders × cost per order
Average inventory	(\frac{Q}{2})	Maximum = (Q), minimum = 0; linear depletion
Annual holding cost	(\frac{Q}{2} \cdot H)	Average inventory × unit holding cost
Annual purchase cost	(D \cdot C)	Constant – does not affect optimal (Q)

Total annual relevant cost (TAC) = ((D/Q)S + (Q/2)H).

Deriving the EOQ Formula

Minimise TAC with respect to (Q). Set the derivative to zero:

[ \frac{d\text{TAC}}{dQ} = -\frac{DS}{Q^{2}} + \frac{H}{2} = 0 ]

Solving:

[ \frac{H}{2} = \frac{DS}{Q^{2}} \quad\Rightarrow\quad Q^{2} = \frac{2DS}{H} ]

[ \boxed{Q^{*} = \sqrt{\frac{2DS}{H}}} ]

Exam tip: The same formula is obtained by setting annual ordering cost equal to annual holding cost: (\frac{D}{Q}S = \frac{Q}{2}H) → solve for (Q).

Sensitivity: What changes EOQ?

Parameter change	Effect on EOQ	Intuition
Demand (D \uparrow)	EOQ (\uparrow)	More demand → larger batches justified
Ordering cost (S \uparrow)	EOQ (\uparrow)	Expensive to order → place fewer, larger orders
Holding cost (H \uparrow)	EOQ (\downarrow)	Costly to hold → order smaller batches

Inventory Buildup (Sawtooth) Pattern

• Order of size (Q) arrives → inventory jumps to (Q).
• Demand depletes inventory linearly at rate (D/365) per day.
• When inventory reaches zero, a new order arrives immediately.
• Cycle repeats.

Key Takeaways

• EOQ balances ordering cost and holding cost.
• Formula: (Q^{*} = \sqrt{2DS/H}).
• Larger demand or ordering cost → larger EOQ; larger holding cost → smaller EOQ.
• Purchase cost is not part of the EOQ decision (it is constant).
• The trade-off is visualised by the sawtooth inventory diagram and the U‑shaped total cost curve.

Intuition and Setup

When a firm manufactures goods in-house rather than sourcing from a supplier, it must decide how many units to produce in each production run (the lot size). Consider:

• Annual demand $D$ (constant over the year).
• Daily demand $\bar{d} = D / 365$ (assuming 365 operating days).
• Daily production capacity $\bar{c}$ (units per day).

The firm can run production lots of size $Q$. For example, with $D = 20{,}000$ and $\bar{c}=100$ per day:

• Produce all $20{,}000$ in one run → run equipment for 200 days, then stop. Huge inventory builds up.
• Produce in lots of $2{,}000$ → 10 runs, each taking 20 days. Inventory is lower but more changeovers are needed.

Tradeoff: Large $Q$ → high holding cost (inventory). Small $Q$ → many setups → high setup cost (changeover cost). This mirrors the EOQ tradeoff, but now production happens at a finite rate $\bar{c}$ while demand $\bar{d}$ is continuous.

Inventory Buildup Pattern

During a production run of $t$ days ($t = Q / \bar{c}$), inventory accumulates at rate $\bar{c} - \bar{d}$ because production outpaces consumption. After the run ends, inventory is consumed at rate $\bar{d}$ until zero, then the next run begins.

graph TD
    subgraph One Cycle
        A[Start production] --> B[Run for t days<br/>Inventory builds at rate (c-d)]
        B --> C[Production stops<br/>Inventory = Q * (1 - d/c)]
        C --> D[Consumption at rate d<br/>until inventory = 0]
        D --> A
    end

Thus the inventory level follows a sawtooth pattern with peak at the end of the production run.

Average Inventory

• Maximum inventory = $(\bar{c} - \bar{d}) \times t = (\bar{c} - \bar{d}) \times \frac{Q}{\bar{c}} = Q \left(1 - \frac{\bar{d}}{\bar{c}}\right)$.
• Minimum inventory = 0.
• Since the pattern is triangular, average inventory = $\frac{\text{max}}{2} = \frac{Q}{2} \left(1 - \frac{\bar{d}}{\bar{c}}\right)$.

Cost Components (Annual)

Cost	Expression	Notes
Setup cost	$\displaystyle \frac{D}{Q} \times S$	Number of runs per year = $D/Q$; $S$ = setup cost per run
Holding cost	$\displaystyle \frac{Q}{2} \left(1 - \frac{\bar{d}}{\bar{c}}\right) \times H$	$H$ = holding cost per unit per year
Manufacturing cost	$D \times C_m$	$C_m$ = unit manufacturing cost; constant w.r.t. $Q$ (ignored in optimisation)

Total annual cost:

$$TC(Q) = \frac{D}{Q}S + \frac{Q}{2}\left(1 - \frac{\bar{d}}{\bar{c}}\right)H + D C_m$$

Optimisation: The EPQ Formula

Take derivative w.r.t. $Q$ and set to zero:

$$\frac{dTC}{dQ} = -\frac{DS}{Q^2} + \frac{H}{2}\left(1 - \frac{\bar{d}}{\bar{c}}\right) = 0$$

Solve for $Q$:

$$Q^* = \sqrt{\frac{2 D S}{H \left(1 - \frac{\bar{d}}{\bar{c}}\right)}}$$

This is the Economic Production Quantity (EPQ) – the lot size that minimises total annual cost.

Intuition of Parameter Effects

Parameter increases	Effect on $Q^*$	Reason
Annual demand $D$	↑	Need more output → bigger lots
Setup cost $S$	↑	Avoid frequent setups → larger lots
Holding cost $H$	↓	Costly to hold → smaller lots
Daily capacity $\bar{c}$	↓	Faster production reduces the time to build inventory → smaller lots
Daily demand $\bar{d}$ (holding $D$ fixed)	↑	Higher utilisation $(\bar{d}/\bar{c})$ reduces the denominator → larger lots

Exam tip: When $\bar{c} \to \infty$ (instantaneous production), $\left(1 - \frac{\bar{d}}{\bar{c}}\right) \to 1$, and EPQ reduces to the EOQ formula: $Q^* = \sqrt{\frac{2DS}{H}}$. The EPQ is always larger than the EOQ for the same $D$, $S$, $H$ because the finite production rate reduces the average inventory.

Key takeaways

• EPQ model decides lot size for in-house production under continuous demand and finite production rate.
• Average inventory = $\frac{Q}{2} \left(1 - \frac{\bar{d}}{\bar{c}}\right)$, which is smaller than the EOQ average ($Q/2$) because consumption occurs during production.
• Optimal lot size: $Q^* = \sqrt{\frac{2DS}{H (1 - \bar{d}/\bar{c})}}$.
• Increased capacity ($\bar{c}$) reduces $Q^*$; increased demand ($D$) increases $Q^*$.
• The tradeoff is between setup cost (fixed per run) and holding cost (proportional to average inventory).
• Manufacturing cost is a constant add‑on and does not affect the optimal $Q$.

EPQ Estimation – Worked Example

Economic Production Quantity (EPQ) determines the lot size that minimises total setup and holding costs when production and consumption occur simultaneously. Unlike the EOQ model (instantaneous replenishment), EPQ accounts for a finite production rate – inventory builds up gradually while demand is drawn down concurrently.

The formula (derived in the preceding lecture) is:

$Q_{EPQ} = \sqrt{\frac{2DS}{H \left(1 - \frac{d}{p}\right)}}$

where

• $D$ = annual demand
• $S$ = setup cost per production run
• $H$ = annual holding cost per unit
• $d$ = daily demand rate
• $p$ = daily production (capacity) rate

Below is a worked‑through example that applies the formula and then computes the resulting annual setup cost, annual holding cost, and production run length.

---

Data

A scooter manufacturer needs seat cushions. Relevant data:

Symbol	Value	Description
$D$	60,000 / year	Annual demand for cushions
$p$	1,000 / day	Daily production capacity
$N$	300 days	Operating days per year
$d = D / N$	$60\,000 / 300 = 200$ / day	Daily demand rate
$H$	₹12 / unit / year	Holding cost per unit per year
$S$	₹6,000	Setup cost per production run

---

1. Compute EPQ

Plug into the EPQ formula:

$$\begin{aligned} Q_{EPQ} &= \sqrt{\frac{2 \times 60\,000 \times 6\,000}{12 \times \left(1 - \frac{200}{1\,000}\right)}} \\[6pt] &= \sqrt{\frac{720\,000\,000}{12 \times 0.8}} \\[6pt] &= \sqrt{\frac{720\,000\,000}{9.6}} \\[6pt] &= \sqrt{75\,000\,000} \\[6pt] &\approx 8\,660 \text{ units} \end{aligned}$$

Each production run therefore consists of 8,660 cushions.

---

2. Annual Setup Cost

Number of setups per year = $\dfrac{D}{Q_{EPQ}} = \dfrac{60\,000}{8\,660} \approx 6.928$ runs.

Annual setup cost = (Number of setups) × $S$

$= 6.928 \times 6\,000 \approx ₹41\,570$

---

3. Annual Holding Cost

The inventory profile in one cycle is:

flowchart LR
    subgraph Production Phase
        A[Start production] --> B[Inventory builds at rate p - d = 800/day]
    end
    subgraph After Production
        B --> C[Production stops; inventory drawn down at rate d = 200/day]
    end
    C --> D[Inventory reaches zero; next cycle begins]

Average inventory during a cycle is:

$I_{avg} = \frac{ \left(1 - \frac{d}{p}\right) \times Q_{EPQ} }{2}$

Proof: maximum inventory = $(p - d) \times t$, where $t = Q_{EPQ}/p$ is the production time. Hence maximum inventory = $(p - d) \times \frac{Q_{EPQ}}{p} = \left(1 - \frac{d}{p}\right) Q_{EPQ}$. Since minimum inventory is zero, average inventory equals half of the maximum.

Plug values:

$$\begin{aligned} I_{avg} &= \frac{ \left(1 - \frac{200}{1\,000}\right) \times 8\,660 }{2} \\ &= \frac{0.8 \times 8\,660}{2} \\ &= 3\,464 \text{ units} \end{aligned}$$

Annual holding cost = $I_{avg} \times H = 3\,464 \times 12 \approx ₹41\,570$.

Note that the annual holding cost equals the annual setup cost – a property of the optimal lot size.

---

4. Production Time per Cycle

Production time $t$ is the number of days the production line runs per cycle:

$t = \frac{Q_{EPQ}}{p} = \frac{8\,660}{1\,000} = 8.66 \text{ days}$

Interpretation: Each cycle starts a production run that lasts 8.66 days, during which 8,660 cushions are produced. After production stops, the accumulated inventory is consumed by demand until stock hits zero, at which point the next 8.66‑day run begins.

Exam tip: Always check that the EPQ denominator $1 - d/p$ remains positive. If $d \ge p$, production cannot keep up with demand – the system is not sustainable without overtime or subcontracting.

Key takeaways

• EPQ extends EOQ by replacing instantaneous replenishment with a finite production rate $p$.
• The optimal lot size is $Q_{EPQ} = \sqrt{ \frac{2DS}{H(1 - d/p)} }$.
• Average inventory in EPQ equals $\frac12 \left(1 - d/p\right) Q_{EPQ}$.
• At the optimum, annual setup cost equals annual holding cost.
• Production time per cycle = $Q_{EPQ} / p$; the full cycle length = $Q_{EPQ} / d$.

Buy Strategy (Sound Max Case)

The Sound Max case evaluates whether to continue buying a critical plastic enclosure from a supplier or to produce it in‑house. This section covers the buy‑strategy analysis: given demand, ordering cost, purchase cost, and holding cost, determine the optimal order quantity and the resulting annual total cost.

Problem Setup

• Sound Max buys the component from a supplier.
• Annual demand is known, and the firm can order in any lot size. Larger lots reduce ordering frequency but increase inventory holding; smaller lots reduce holding but increase ordering cost.
• The goal is to find the Economic Order Quantity (EOQ) that minimises total annual cost (ordering + holding + purchase cost).

Data Summary

Parameter	Symbol	Value	Notes
Annual demand	$D$	24,000 units/year	Working days: 300/year → daily demand ≈ 80 units
Ordering cost per order	$S$	₹1,000	Administrative cost of placing an order
Unit purchase cost (supplier price)	$C_s$	₹650 per unit
Holding cost rate	$h$	18% of unit cost per year	Given as 18% of $C_s$
Unit holding cost	$H$	$0.18 \times 650 = ₹117$ per unit per year

Applying EOQ: The Trade-off

flowchart LR
    A[Order quantity Q] --> B{Balance}
    B --> C[Large Q: fewer orders, low ordering cost]
    B --> D[Large Q: higher average inventory, high holding cost]
    B --> E[Small Q: many orders, high ordering cost]
    B --> F[Small Q: lower average inventory, low holding cost]
    C & D --> G[EOQ: minimises total of ordering + holding cost]
    E & F --> G

The Economic Order Quantity (EOQ) is the lot size that balances ordering and holding costs:

$Q^* = \sqrt{\frac{2DS}{H}}$

Worked Example: Optimal Order Quantity

Plug in the values:

$Q^* = \sqrt{\frac{2 \times 24000 \times 1000}{117}} = \sqrt{\frac{48,000,000}{117}} \approx \sqrt{410,256.41} \approx 641 \text{ units}$

Thus Sound Max should order in batches of 641 units each time.

Annual Cost Breakdown

1. Annual Ordering Cost

Number of orders per year = $\frac{D}{Q^*} = \frac{24000}{641} \approx 37.44$
Cost = $\frac{D}{Q^*} \times S = 37.44 \times 1000 = ₹37,440$ (rounded to ₹37,470)

The transcript gives ₹37,470 (slight rounding). Exact value: $\frac{24000}{641} \times 1000 \approx 37,444$. We'll use the transcript's figure.

2. Annual Holding Cost

Average inventory = $\frac{Q^*}{2} = \frac{641}{2} = 320.5$ units
Cost = $\frac{Q^*}{2} \times H = 320.5 \times 117 = ₹37,498.5$ (transcript: ₹37,470)

3. Annual Purchase Cost

Total units bought = $D = 24,000$
Cost = $D \times C_s = 24,000 \times 650 = ₹15,600,000$

4. Total Annual Cost (Buy Strategy)

$\text{Total Cost} = \text{Ordering Cost} + \text{Holding Cost} + \text{Purchase Cost}$ $= 37,470 + 37,470 + 15,600,000 = ₹15,674,940$

(Transcript states ₹15,647,940 – a small arithmetic difference; the logic is identical.)

Exam tip: The purchase cost dominates the total, but it is independent of lot size. The EOQ minimises only the ordering + holding cost. Do not confuse total cost with inventory‑related cost when comparing strategies.

Key Takeaways

• The buy strategy uses the EOQ model: $Q^* = \sqrt{2DS/H}$.
• Optimal order quantity = 641 units (rounded), balancing ordering cost (₹1,000/order) and holding cost (₹117/unit/year).
• Annual ordering cost ≈ ₹37,470; annual holding cost ≈ ₹37,470; annual purchase cost = ₹15,600,000.
• Total annual cost under the buy strategy ≈ ₹15.67 million.
• This baseline will be compared with the proposed in‑house production strategy to decide which is cheaper.

Make Strategy (In-House Production)

The make strategy evaluates whether SoundMax should produce the plastic enclosure in-house rather than buy from an external supplier. The key operational decision is the production lot size (how many units per production run), because it creates a trade-off between setup cost (cost per run) and holding cost (cost of carrying inventory). The Economic Production Quantity (EPQ) model finds the lot size that minimises total annual cost.

Data for the make-scenario

Parameter	Symbol	Value
Annual demand	$D$	24,000 units
Working days per year	—	300
Daily demand	$d$	$24\,000 / 300 = 80$ units/day
Daily production capacity	$\bar{c}$	300 units/day
Unit manufacturing cost	$C_m$	₹620/unit
Setup cost per production run	$S$	₹6,000
Holding cost (per unit per year)	$H$	18% of $C_m = 0.18 \times 620 = \text{₹111.6}$

The EPQ Model

When producing in-house, inventory accumulates at rate $\bar{c} - d$ during a production run and is consumed at rate $d$ during the rest of the cycle. The optimal lot size that balances setup and holding costs is:

$$Q_{EPQ} = \sqrt{\frac{2 D S}{H \left(1 - \frac{d}{\bar{c}}\right)}}$$

Plugging in the numbers:

$$Q_{EPQ} = \sqrt{\frac{2 \times 24\,000 \times 6\,000}{111.6 \times \left(1 - \frac{80}{300}\right)}} = \sqrt{\frac{288\,000\,000}{111.6 \times 0.7333}} \approx 1\,876 \text{ units}$$

Thus the optimal production batch size is 1,876 units per run.

Inventory Profile

The cycle works as follows:

flowchart LR
    A[Production run for t days] --> B[Inventory builds at rate (c_bar - d)]
    B --> C[Run ends, inventory max = (c_bar - d) * t]
    C --> D[Inventory consumed at rate d until zero]
    D --> A[Next production run starts]

where $t = Q_{EPQ} / \bar{c}$ is the production run length.
Average inventory in the system:

$$\text{Avg inventory} = \frac{\text{max inventory}}{2} = \frac{Q_{EPQ}}{2} \left(1 - \frac{d}{\bar{c}}\right)$$

For SoundMax:

$$\text{Avg inventory} = \frac{1\,876}{2} \times \left(1 - \frac{80}{300}\right) \approx 938 \times 0.7333 \approx 688 \text{ units}$$

Total Annual Cost Under Make Strategy

The total annual cost has three components:

1. Annual setup cost
   Number of runs per year $= D / Q_{EPQ}$
   $\text{Setup cost} = \frac{D}{Q_{EPQ}} \times S = \frac{24\,000}{1\,876} \times 6\,000 \approx ₹76\,760$

2. Annual holding cost
   $\text{Holding cost} = \text{Avg inventory} \times H = 688 \times 111.6 \approx ₹76\,760$

3. Annual production cost
   $\text{Production cost} = D \times C_m = 24\,000 \times 620 = ₹1\,48\,80\,000$

Total make cost = ₹1,48,80,000 + ₹76,760 + ₹76,760 = ₹1,50,33,520 per year.

Comparison with Buy Strategy

From the previous analysis (not shown in this transcript), the total annual cost under the buy strategy is ₹1,56,74,940.

Because ₹1,50,33,520 < ₹1,56,74,940, making in-house is the optimal decision.

Exam tip: In EPQ, the average inventory expression $\frac{Q}{2}(1 - d/\bar{c})$ is the only difference from the EOQ formula. When $d/\bar{c}$ is small (capacity much larger than demand), the term approaches 1 and EPQ behaves like EOQ. Always check whether production capacity is binding.

Key takeaways

• EPQ determines lot size for in-house production, trading off setup cost vs. holding cost.
• Formula: $Q_{EPQ} = \sqrt{2DS / [H(1 - d/\bar{c})]}$.
• Average inventory depends on the ratio $d/\bar{c}$; the closer demand is to capacity, the lower the average inventory.
• Total cost = setup cost + holding cost + production cost (material cost).
• Compare make vs. buy total cost to choose the optimal strategy.