0% found this document useful (0 votes)
8 views20 pages

Understanding TPM and TOC in Business

The document provides an overview of various business process improvement methodologies including Total Productive Maintenance (TPM), Theory of Constraints (TOC), Failure Modes and Effects Analysis (FMEA), and the Iceberg Model of Safety. Each methodology is explained with key terms and illustrated through scenario-based examples from different companies, showcasing how these concepts can effectively address operational issues. The outcomes highlight improvements in efficiency, reduction in errors, and enhanced compliance across the organizations.

Uploaded by

abeesid32
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views20 pages

Understanding TPM and TOC in Business

The document provides an overview of various business process improvement methodologies including Total Productive Maintenance (TPM), Theory of Constraints (TOC), Failure Modes and Effects Analysis (FMEA), and the Iceberg Model of Safety. Each methodology is explained with key terms and illustrated through scenario-based examples from different companies, showcasing how these concepts can effectively address operational issues. The outcomes highlight improvements in efficiency, reduction in errors, and enhanced compliance across the organizations.

Uploaded by

abeesid32
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Here’s a simple explanation of TPM-related terms in the context of business process and design, followed by a

realistic scenario-based example that ties them all together:

✅ TPM (Total Productive Maintenance) – Simplified Explanation


TPM is a proactive maintenance approach that involves everyone in the organization—not just technicians—to keep
machines and processes running smoothly. The goal is zero breakdowns, zero defects, and zero accidents to improve
productivity and quality.

🔹 Key Terms and Their Roles in Process Design:


1. Autonomous Maintenance
2. Operators themselves take responsibility for routine tasks like cleaning, lubricating, and inspecting machines.
3. → Benefit: Fewer breakdowns and faster detection of small issues.
4. Planned Maintenance
Scheduled checks and servicing of equipment before problems happen.
→ Benefit: Minimizes unexpected downtimes.
5. Office TPM (Total Productive Maintenance for Office)
Applying TPM principles to administrative processes—like regularly cleaning and updating digital files or organizing
workflow systems.
→ Benefit: Reduces processing errors and improves communication speed.
6. JIDOKA (Automation with Human Intelligence)
Machines automatically stop when they detect a problem, preventing bad output.
→ Benefit: Ensures quality at the source.
7. ANDON (Visual Alert System)
Light or signal system on the production floor that shows the current status—green (normal), yellow (attention needed),
red (problem).
→ Benefit: Real-time issue tracking and response.
8. OEE (Overall Equipment Effectiveness)
A key metric that combines availability, performance, and quality to show how well a machine is utilized.
→ Benefit: Helps identify and prioritize areas for improvement.
9. MTTR (Mean Time to Repair)
Average time taken to fix a machine after it breaks down.
→ Lower MTTR = quicker recovery and better uptime.
10. MTBF (Mean Time Between Failures)
Average time a machine runs without breaking down.
→ Higher MTBF = more reliable process.
11. Installation Qualification (IQ)
Check whether the machine or system is installed correctly as per the design.
→ First step in setting up reliable equipment.
12. Operational Qualification (OQ)
Verify that the equipment works as intended under all expected conditions.
→ Ensures it performs within expected limits.
13. Performance Qualification (PQ)
Final validation that the equipment performs consistently in real-life operations.
→ Confirms the machine is ready for daily production use.
14. Equipment Qualification Report
A document that summarizes IQ, OQ, and PQ.
→ Ensures compliance, safety, and readiness before machine launch.

📘 Scenario-Based Example
Company: FastPack Pvt. Ltd.
Industry: Packaging Materials
Problem: Frequent machine breakdowns led to delays in customer orders and increased rework.
How TPM Solves the Problem
1. TPM Program Launch:
The company sets up a TPM team and trains machine operators.
2. Autonomous Maintenance:
Operators clean, lubricate, and inspect their packing machines every shift.
→ They find a misaligned sensor before it causes a breakdown.
3. Planned Maintenance:
The maintenance team creates a schedule to replace worn-out belts and check motors monthly.
→ Prevents last-minute surprises.
4. Office TPM:
In the sales office, standard response templates and digital file maintenance are implemented.
→ Quotation errors are reduced and order processing becomes faster.
5. JIDOKA:
Sensors are installed on the sealing machines. If the temperature is too low, the machine stops automatically.
→ Prevents faulty sealing and saves material.
6. ANDON System:
Red, yellow, and green lights are placed above each machine.
→ When a fault occurs, operators press a button, turning the light red and alerting the maintenance team instantly.
7. OEE Monitoring:
The company calculates OEE for each machine weekly.
→ They discover one machine runs slower due to operator delays. A quick training fixes this.
8. MTTR & MTBF Tracking:
• MTTR for the main conveyor was 2 hours → reduced to 40 minutes with better spare parts readiness.
• MTBF increased from 1 day to 4 days due to proactive inspections.
9. IQ, OQ, PQ during New Machine Setup:
• IQ: Verified all electrical and mechanical components are installed correctly.
• OQ: Tested machine speed, temperature range, and sealing precision.
• PQ: Ran real production for 2 weeks with zero issues.
• Equipment Qualification Report was signed and filed for audit.

✅ Outcome
• Equipment uptime increased by 35%
• Customer order delays reduced by 60%
• Product defect rate dropped by 40%
• Maintenance cost decreased due to fewer emergencies

Here's a simple explanation of the Theory of Constraints (TOC) and related terms, followed by a real-world business
scenario tying them all together:

✅ Theory of Constraints (TOC) – Simplified Overview


The Theory of Constraints is a business improvement method that focuses on identifying the biggest bottleneck
(constraint) in a process and resolving it so the overall system can perform better.
In simple terms:
"A system is only as strong as its weakest link."
TOC helps you find and fix that link.

🔹 Key Terms Explained:


1. Backlog
2. Unfinished work that piles up behind a bottleneck.
3. If a machine or team is slower than the rest, work queues up behind it.
4. Operational Blindness
When teams can't see where the real problem lies—they focus on busy work, not productive work.
It's like cleaning the floor when the fire alarm is ringing—missing the priority.
5. Constraint-related concepts in Time & Motion Activity
Time and motion studies track how long each task takes.
Helps reveal which task or activity is the slowest (the constraint).
6. 3Vs – Volume, Variety, Variation
These factors impact process flow:
• Volume: Quantity of work
• Variety: Different types of work or products
• Variation: Inconsistency in how or when tasks are done
Any of these can stress a constraint.
5. Mitigation Plan
An action plan to ease or eliminate the impact of the constraint.
Could involve more resources, automation, shifting tasks, or process redesign.

📘 Scenario-Based Example
Company: SmartBoxes Ltd.
Industry: E-commerce packaging supplier
Issue: Late deliveries despite having enough staff and machines.

🧩 Step-by-Step Breakdown Using TOC Concepts


1. Backlog Detected:
Orders are piling up at the box folding station while other areas are idle.
→ There’s a backlog specifically at one workstation.
2. Operational Blindness Identified:
Managers were pushing for faster packing and labeling, but ignored the folding area, thinking it's “not a big issue.”
→ Classic case of operational blindness—focusing on non-constraints.
3. Time & Motion Activity Conducted:
A study showed it takes 3 minutes to fold a box but only 1 minute to pack and label.
→ Folding is the slowest step—the constraint is identified.
4. Analysis Through 3Vs:
• Volume: Surge in orders after a new product launch
• Variety: Different box sizes needing different folding techniques
• Variation: Some operators fold faster than others
→ All three factors stressed the folding station, reinforcing it as the constraint.
5. Mitigation Plan Created:
Trained more staff on box folding
Introduced pre-folded box stocks for common SKUs
Installed a semi-automatic folding machine
→ These steps reduced folding time by 50%

✅ Outcome
• Order backlog was cleared within 3 days
• On-time delivery improved from 78% to 96%
• Floor workers better understood which step needed help most
• The team learned to focus on constraints, not just busy tasks

Here's a simple explanation of FMEA (Failure Modes and Effects Analysis) and related terms, followed by a realistic
business scenario that ties everything together, especially RPN (Risk Priority Number) and its components:
✅ FMEA – Simplified Explanation
FMEA (Failure Modes and Effects Analysis) is a structured method used to identify potential failures in a process,
product, or system, assess their impact, and prioritize actions to prevent them.
It helps businesses prevent problems before they occur, instead of reacting to them after damage is done.

🔹 Key Terms Explained


1. Failure Mode
2. What can go wrong in a process or system.
3. Example: Incorrect product labeling.
4. Effect of Failure
What happens if the failure occurs.
Late delivery, wrong shipment, customer complaints.
5. Severity (S)
How serious the effect is if it happens. Rated from 1 (low) to 10 (very serious).
High if it affects customer safety or reputation.
6. Occurrence (O)
How likely the failure is to happen. Rated 1 (rare) to 10 (frequent).
Based on historical data or team judgment.
7. Detection (D)
How likely the failure will be detected before reaching the customer. Rated 1 (easily detected) to 10 (hard to detect).
Low if current checks won’t catch the problem.
8. RPN (Risk Priority Number)
A numerical score used to prioritize risks:
RPN=Severity×Occurrence×Detection\text{RPN} = \text{Severity} \times \text{Occurrence} \times \text{Detection}
7. Detection Link Control
Existing controls or checkpoints that help detect or prevent the failure mode.
Example: Barcode scanners, quality checks, alarms.

📘 Scenario-Based Example
Company: FreshDelight Foods Pvt. Ltd.
Industry: Packaged food delivery
Problem: Occasional customer complaints about wrong food labeling and delayed delivery

🧩 FMEA Table – Applying the Method


Step/Proces Failure Sever Occurre Detect RPN = S × Detection Link
Effect
s Mode ity (S) nce (O) ion (D) O×D Control
Printing food Wrong Wrong allergen Manual check before
9 4 6 216
labels product label info, complaint sealing
Delivery Wrong
Package delayed or App GPS + address
dispatch address 7 3 3 63
lost scan at dispatch
step printed
Missing
Packaging Spoilage risk, Visual QC at end of
freshness 8 2 7 112
step brand damage line
seal

🔎 Interpretation:
• Highest RPN (216) is for wrong food labeling, a high-severity issue with limited detection.
• The team prioritizes this risk for immediate action.

🛠️ Mitigation Action Plan:


1. Label printing upgraded to barcode-based system (to reduce human error).
2. Extra digital verification step added before sealing.
3. New control: Alarm if label mismatches the product code.

✅ After Improvement
• New Detection Rating: Drops from 6 → 2 (easier to catch errors)
• New RPN:
9 (S)×4 (O)×2 (D)=729 \text{ (S)} \times 4 \text{ (O)} \times 2 \text{ (D)} = 72
• Huge reduction from 216 → 72 in risk level

📈 Outcome
• Labeling complaints dropped by 85%
• Audit scores improved due to better documentation
• Team became proactive in identifying process risks

Here’s a simple explanation of each term under “Issues and Its Types” in the context of business process and design,
followed by a scenario-based example that ties them all together.

✅ Issues and Its Types – Simple Definitions


Term Explanation
Deviation A process not followed as planned, even unintentionally.
Non-Conformance (NC) A product or process does not meet the set quality standard.
Non-Compliance A regulatory rule or policy is violated, usually legal or statutory.
Corrective Action Steps taken to fix a problem after it has occurred.
Preventive Action Steps taken to stop a potential problem before it happens.
Recall Pulling back faulty products from the market to avoid risk to customers.
Root Cause The real, underlying reason for the problem.
Direct Cause The immediate reason the issue occurred.
Contributory Cause Secondary or supporting factors that made the issue worse or more likely.
Action Plan A detailed plan to address and resolve an issue.
Interim Control Temporary measures used until the final fix is implemented.
Trial and Error A method of testing different fixes when the best solution isn’t clear.
Human-Based Error An error caused due to manual mistake or decision-making.
FAT (Factory Acceptance
Final test done before a system or machine is accepted for use.
Testing)
A formal approval required to carry out a risky or controlled activity (e.g., electrical,
Work Permit
maintenance).

📘 Scenario-Based Example
Company: PharmaClean Pvt. Ltd.
Industry: Pharmaceutical packaging
Product: Blister packs of tablets

🎯 Situation:
A batch of medicine was packed with wrong expiry date on the label and shipped to a distributor. This triggered an issue
investigation.

🧩 Step-by-Step Issue Flow Using All Terms:


1. Deviation
2. A packaging operator skipped the verification step before printing labels. This was a deviation from the SOP
(Standard Operating Procedure).
3. Non-Conformance (NC)
The finished product did not meet quality standards—wrong expiry date on the label.
4. Non-Compliance
This issue also violated FDA labeling regulations, making it a regulatory non-compliance.
5. Recall
Company initiated a recall to bring back the wrongly labeled medicines from the market.
6. Root Cause
The label template was accidentally edited due to lack of system lock. That’s the root cause.
7. Direct Cause
The operator failed to double-check the template before printing.
8. Contributory Cause
• The system allowed unauthorized editing
• Lack of digital interlock
• Inadequate training on label software
8. Human-Based Error
Yes, this was manual input error—human mistake in printing.
9. Corrective Action
• Correct the label template
• Reprint labels
• Train staff again on SOP
10. Preventive Action
• Lock the label template to prevent changes
• Add system validation before printing
• Introduce double-check step in the software
11. Action Plan
A detailed timeline and task list was created to implement corrective and preventive actions within 2 weeks.
12. Interim Control
Until changes were implemented, an extra label check was added manually at the line.
13. Trial and Error
To test the new label verification method, several test runs were conducted using different label designs and
failure scenarios.
14. FAT (Factory Acceptance Testing)
Before re-starting production, a Factory Acceptance Test was done to ensure the labeling system works as
intended with controls.
15. Work Permit
To modify the labeling system hardware, the technician obtained a “Work Permit” from the EHS (Environment,
Health & Safety) team since the system was high-voltage.

✅ Outcome
• Issue closed with proper documentation
• No further incidents occurred for 3 months
• Regulatory audit praised the corrective measures
• Human errors decreased by 40% due to process changes

Here’s a simple explanation of the Iceberg Model of Safety and the related terms in a business context, followed by a
scenario-based example to tie them all together.
✅ Iceberg Model of Safety – Simple Explanation
The Iceberg Model of Safety helps visualize how visible accidents are just the tip of the iceberg. Beneath every major
incident, there are many unseen unsafe acts, near misses, or minor issues that often go unnoticed — but if ignored, they
can lead to serious accidents.

🧊 The Iceberg Analogy



Fatality
---------------- ← Tip of the Iceberg (Visible)
LTA (Lost Time Accident)
RWC (Restricted Work Case)
PDA (Partial Disability Accident)
---------------- ← Below the Surface (Hidden)
Unsafe Acts
Near Misses
Unsafe Conditions
Non-compliance
Poor training

🔹 Key Terms Explained


Term Simple Definition
LTA (Lost Time Accident) Injury where the worker misses work days.
RWC (Restricted Work Case) Worker returns to work but with restricted duties.
PDA (Partial Disability
Worker suffers permanent partial disability, e.g. loss of finger.
Accident)
Fatality Death due to a workplace incident.
SHE (Safety, Health,
Policies and practices that protect people and the environment.
Environment)
A safety procedure that ensures machines are turned off and can’t restart during
LOTO (Lockout/Tagout)
maintenance.
Administrative Control Rules, signs, SOPs, and training used to control risks (vs. physical barriers).

📘 Scenario-Based Example
Company: TechMetal Industries
Industry: Steel fabrication plant
Process: Operating a hydraulic metal press for shaping steel sheets.

🎯 Safety Incident Story


An experienced technician, Raj, suffers a hand injury while cleaning the metal press machine.

🔎 Breakdown Using Iceberg Model & Safety Terms:


1. Incident Outcome:
2. Raj’s injury was serious enough to keep him off work for 15 days.
3. This is a Lost Time Accident (LTA).
4. Investigation reveals:
• Machine was not locked out properly before cleaning.
LOTO procedure was not followed.
• He was not reminded about LOTO during daily briefing.
Lack of Administrative Control.
3. Hidden Layer – Below the Surface:
• Several unsafe conditions were observed:
o Warning sign faded
o LOTO keys not kept in visible location
• Past 2 months, 4 near misses were logged involving the same machine.
• Another worker earlier had a Restricted Work Case (RWC) from a similar near-miss (sprained shoulder from
emergency brake failure).
• A previous contract worker had a Partial Disability Accident (PDA) – lost part of his thumb due to improper
guarding.
4. SHE (Safety, Health, Environment) Review:
The Safety Manager performs a SHE audit and finds:
• Training not refreshed in 8 months
• Many LOTO tags missing
• Safety logs not reviewed weekly
5. Corrective Action:
• Re-train all machine operators on LOTO
• Replace all faded signs and missing tags
• Introduce Administrative Controls like digital SOPs and quiz-based safety checks

❗ Learning from the Iceberg


Even though only one injury (LTA) was reported this time, the “iceberg” revealed a systemic safety issue:
“If we ignore 10 near misses and 100 unsafe conditions today, tomorrow we might face a fatality.”

✅ Outcome:
• LOTO compliance increased to 100%
• Near-miss reporting went up by 60% due to proactive culture
• No LTAs or PDAs reported in the next 6 months
• Safety awareness improved, and SHE goals became part of daily KPIs

Here's a simple explanation of the Fishbone (Ishikawa) Diagram and its related tools in the context of business process
and design — followed by a scenario-based example that ties everything together.

🐟 Fishbone (Ishikawa) Diagram – Simple Explanation


Also known as the Cause and Effect Diagram, this tool is used to identify the root causes of a problem. It looks like a
fishbone, with the "head" representing the problem, and the "bones" representing major categories of potential causes.

🔹 Key Terms Explained


Term Simple Definition
Fishbone Diagram / Cause &
A structured tool used to visually display all possible causes of a specific problem.
Effect Diagram
5M The 5 major categories of causes in manufacturing:
→ Man, Machine, Material,
Method, Management
A technique where you ask “Why?” multiple times (usually 5) to find the root cause
Why-Why Analysis
of a problem.
5W & 1H A questioning approach to analyze a problem:
→ What, Why, When, Where,
Who, and How
Observing the actual workflow closely (especially Man, Material, Method,
Process Observation
Management) to identify inefficiencies or problems.
📘 Scenario-Based Example
Company: SpeedPack Solutions
Industry: Packaging of consumer goods
Problem: "Too many defective boxes in final quality check"

🧠 Step 1: State the Problem


Problem Statement (Head of the Fish):
“High rate of defective packaging boxes (10% rejection)”

🐟 Step 2: Build the Fishbone (Using 5M Categories)


Man (People):
• Inexperienced workers
• Fatigue during long shifts
Machine:
• Sealer temperature not consistent
• Conveyor belt misaligned
Material:
• Boxes not pre-folded properly
• Flimsy quality of glue
Method:
• Manual checking process, no automation
• Packing steps skipped in busy hours
Management:
• Poor training schedule
• No clear accountability for quality errors

👀 Step 3: Use Process Observation


The supervisor visits the floor and closely watches the process. She observes:
• The Material glue is sticking late.
• Man (operator) skips a sealing step during high volume rush.
• Method includes a manual quality check, which is rushed.
• Management hasn’t revised SOPs in 9 months.

❓ Step 4: Apply 5W & 1H


Question Answer
What is the issue? Defective packaging boxes
Why is it happening? Improper sealing and skipped checks
When does it occur? Mostly during peak hours
Where? End-of-line packaging station
Who? Operators on afternoon shift
How? Process rushed; machine maintenance overdue

🔍 Step 5: Conduct Why-Why Analysis


Why 1 – Why are boxes defective?
Because the seal is incomplete.
Why 2 – Why is the seal incomplete?
Because the operator skipped one step.
Why 3 – Why did the operator skip the step?
Because during rush, he wanted to catch up.
Why 4 – Why is there a rush?
Because the output target is high and there’s only one quality checker.
Why 5 – Why only one checker?
Because of cost-saving decisions by management without reviewing workload.

✅ Corrective Actions
1. Man: Train operators better & rotate shifts to avoid fatigue
2. Machine: Schedule preventive maintenance for the sealer
3. Material: Source better-quality glue or test curing time
4. Method: Add automated sensor for quality checks
5. Management: Align targets with actual manpower capacity

🏁 Result
By using the Fishbone Diagram with 5M, 5W1H, Why-Why, and Process Observation, the company:
• Reduced packaging defects from 10% to 2% in one month
• Increased on-time dispatch by 12%
• Improved operator satisfaction

Would you like a visual fishbone chart or a template for team use?

Here’s a simple explanation of TIMWOOD and related Lean concepts like MUDA, MURI, ENVA, SMED, etc., along with a
scenario-based example to show how these ideas apply in real business processes.

🧱 TIMWOOD (7 Wastes in Lean) — Simplified


TIMWOOD is a memory aid for identifying the 7 wastes in any process that don’t add value to the customer:
Letter Waste Simple Meaning
T Transportation Moving materials unnecessarily
I Inventory Having more stock than needed
M Motion Unnecessary movement of people/machines
W Waiting Delays between steps
O Overproduction Making more than needed
O Overprocessing Doing more work than necessary
D Defects Errors or rework

🧩 Related Concepts Explained Simply


Term Simple Meaning
MUDA Japanese term for waste — anything that doesn’t add value
ENVA (Essential Non-Value Adding) Necessary steps that don’t add direct value (e.g. regulatory documentation)
MURI Overburdening people or equipment, causing breakdowns or errors
SMED (Single-Minute Exchange of Dies) Reducing machine setup/changeover time to under 10 minutes
Time & Motion Study Observing and analyzing tasks to eliminate inefficient steps
Operational Blindness Repeating inefficient processes without realizing they're wasteful

🏭 Scenario-Based Example
Company: SwiftPrint Packaging Ltd.
Industry: Printing and Packaging
Problem: Delayed order deliveries and high operational cost
🎯 Step 1: Identify Wastes Using TIMWOOD
1. Transportation
Boxes are moved between 3 buildings for printing, packing, and QC — too much back-and-forth.
2. Inventory
Overstock of printed labels sitting idle for weeks “just in case.”
3. Motion
Workers walking to far corners for tools & labels — no fixed location.
4. Waiting
Packaging team waits 45 mins daily for printed sheets due to batch delays.
5. Overproduction
Team prints 10% more than needed — anticipating rework — wasting material.
6. Overprocessing
Double-checking items manually even though automated scanners are available.
7. Defects
Ink smudges due to improper drying times — 8% of output reworked.

🧠 Step 2: Dig Deeper with Other Concepts


🔸 MUDA
All the above are MUDA — pure wastes. They don’t add customer value.
🔸 ENVA
Monthly quality audit paperwork — doesn’t add value but is necessary for ISO compliance.
🔸 MURI
Operators are given 10-hour shifts without breaks to meet rush orders — they make more errors.
🔸 Operational Blindness
Workers still walk across the floor for label rolls — “we’ve always done it this way.”
🔸 SMED
Changing the printer setup takes 45 minutes between designs. After SMED implementation, it was reduced to 9 minutes —
increasing capacity.
🔸 Time & Motion Study
An engineer observed the packing line and redesigned the workstation layout. Workers now walk 40% less and complete
tasks faster.

✅ Improvements After Lean Application


• Set up kanban zones to reduce overproduction
• Implemented SMED to cut changeover times
• Rearranged tools using 5S to reduce motion waste
• Digitized audits to reduce ENVA paperwork burden
• Cross-trained workers to reduce waiting time

📊 Result:
Metric Before After
On-time delivery 78% 96%
Setup time 45 mins 9 mins
Wastage (rework) 8% 2%
Employee fatigue score High Moderate

Here’s a simple explanation of Product Lifecycle Management (PLM) along with a scenario-based example that shows
how each of the listed terms fits into the business process and product design journey.

🌀 What is PLM (Product Lifecycle Management)?


PLM is the management of a product from idea to disposal — covering every phase:
Concept → Design → Manufacturing → Quality Testing → Usage → Service → End -of-Life (Recall/Disposal)
Think of it as a roadmap for the entire life of a product, ensuring quality, compliance, efficiency, and cost control across
departments.

🔧 Key PLM Terms — Explained Simply


Term Meaning
Design to Order / Engineer to Order (ETO) Custom products designed from scratch based on client needs
Make to Order (MTO) Standard product made after customer places order
Assemble to Order (ATO) Pre-made parts are assembled when the order comes in
Make to Stock (MTS) Products made in advance and kept in inventory
Product Qualification (IQ, OQ, PQ) Testing done to qualify a product/process (Installation, Operation, Performance)
FAT (Factory Acceptance Testing) Final testing at the factory before shipping the product to the customer
Recall Withdrawing the product from the market if it’s defective or non-compliant

🏭 Scenario: "NovaMed Instruments" – Surgical Equipment Manufacturer


Step-by-step Journey in PLM:

🧠 1. Product Design Phase


NovaMed receives a hospital request for a custom surgical tool.
• Engineer to Order (ETO):
• R&D team designs a brand-new tool based on specific surgical requirements.
• Multiple prototypes are made and improved.

🏗 2. Manufacturing Strategy Selection


NovaMed offers 3 product lines with different strategies:
Product Type Model Strategy
Customized tool Model A Design to Order / Engineer to Order
Standard tool Model B Make to Order — made after the hospital places order
Common kit Model C Assemble to Order — parts are ready; assembled per order
Disposable scalpel Model D Make to Stock — mass produced, stored in warehouse

✅ 3. Product Qualification (for New Models)


Before full-scale production, they test the new tool using 3 qualification stages:
Stage Description
IQ (Installation Qualification) Check if the machines/tools needed for production are properly installed
OQ (Operational Qualification) Test if the equipment works as intended under expected conditions
PQ (Performance Qualification) Confirm the final product consistently meets performance specs

🧪 4. Factory Acceptance Testing (FAT)


Once production is complete:
• The tool is tested thoroughly at the factory with simulated surgical conditions.
• Client's quality team witnesses this test before accepting the shipment.

🚚 5. Delivery, Use, and Market Monitoring


The tool performs well and enters regular use in hospitals.
However, 6 months later, a batch shows minor defects in handle insulation.

⚠️ 6. End-of-Life / Recall Management


• NovaMed triggers a product recall for that batch.
• Clients are notified, defective units collected, and investigation begins.
• The product design and testing stages are reviewed and improved for the future.

💡 Summary of PLM in Action


Phase Action PLM Term Used
Design Custom tool concept ETO
Planning Decide how to make products ETO, MTO, ATO, MTS
Testing Ensure product readiness IQ, OQ, PQ, FAT
Manufacturing Make, assemble, or stock Strategy applied
Post-sale Customer use and monitoring Feedback loop
End-of-Life Handle defect, fix process Recall

✅ Business Outcome
• Reduced rework by 30% due to better FAT and qualification
• Improved customer trust through proactive recall
• Shorter delivery time on ATO and MTS products
• Higher compliance with global healthcare regulations

Here’s a simple explanation of key Lean Concepts along with a realistic scenario-based example that connects all the
listed terms to a business process and design flow.

⚙️ What is Lean?
Lean is a business philosophy focused on maximizing value to the customer while eliminating waste in processes. It
emphasizes efficiency, quality, and continuous improvement.

🏭 Scenario: "SwiftTech Electronics" – Assembly Line for Smart Sensors


SwiftTech manufactures electronic sensors used in smart homes. The company faces high rework, delayed deliveries,
and inefficiencies in assembly and packaging.

🛠 Applying Lean Concepts – Step by Step


1. 🔍 GEMBA – “Go to the actual place”
The operations manager visits the assembly floor (Gemba) to observe the real problems rather than relying on reports.
2. 📊 Process Mapping + Value Stream
They map the entire process from raw material to finished product and identify value-adding and non-value-adding
steps.
• Value Stream: Flow of materials and information needed to deliver the product.
• They highlight where delays, rework, or waste happen.

3. ♻️ MUDA, MURI, ENVA – The 3 types of waste


They categorize wastes found:
Term Meaning Example
MUDA Non-value adding Waiting for parts, extra movements
MURI Overburden One operator doing 3 tasks, fatigued
ENVA Essential Non-Value Add Quality check (needed, but doesn’t add direct value)

4. 🧹 5S – Workplace Organization
They implement 5S to bring structure to the assembly area:
1. Sort – Remove unused tools
2. Set in order – Arrange tools neatly
3. Shine – Clean the area
4. Standardize – Create SOPs
5. Sustain – Audit regularly to maintain
5. 🛑 POKA-YOKE – Error-proofing
To reduce wiring mistakes, they install color-coded slots and fixtures that only allow correct assembly (error-proof
design).

6. 📋 Kanban – Visual Scheduling


Instead of overproducing, they set up Kanban boards with color cards:
• Green = OK to start
• Yellow = Almost full
• Red = Stop production
This controls inventory and aligns production with demand.

7. 🔁 PDCA Cycle – Continuous Problem Solving


They use the PDCA loop to solve problems:
Step Action
Plan Identify root cause of delays
Do Test small fix
Check Measure results
Act Implement change company-wide

8. ⚙️ Time & Motion Study


They conduct a time study to measure how long each task takes.
Then optimize workstation layout to minimize walking and reaching.

9. ⏱ SMED – Quick Changeovers


The team works on SMED (Single-Minute Exchange of Dies) to reduce machine changeover time from 40 mins to 8 mins,
increasing uptime.

10. ✅ RFT – Right First Time


With training and error-proofing, 95% of products now pass inspection the first time – no rework or scrap.

11. 🔁 CIF (Continuous Improvement Framework) + Kaizen


They set up a Kaizen team that meets weekly to identify and act on small improvements — forming the CIF culture
company-wide.

✅ Lean Concepts in Summary


Concept Role in Scenario
Lean Overall strategy to reduce waste and boost value
GEMBA Observe real operations, not just data
Process Mapping Understand entire flow
Value Stream Identify value-adding vs. waste
MUDA / MURI / ENVA Classify waste types
5S Organize the workplace
POKA-YOKE Prevent errors
Kanban Visual control for production
PDCA Systematic improvement cycle
Time & Motion Study movements for efficiency
SMED Reduce changeover time
RFT Produce quality at first attempt
CIF / Kaizen Continuous improvement culture
🎯 Business Outcome
• 30% reduction in defects
• 40% faster changeovers
• 20% higher employee engagement through Kaizen
• Shorter lead times and higher customer satisfaction

Here's a simple explanation of Six Sigma and its key terms, using a realistic business process and design
scenario that shows how each concept works together.

• ✅ What is Six Sigma?


• Six Sigma is a data-driven approach to improve quality, reduce defects, and create consistent processes in
business operations and product design.
• Its goal is to achieve near perfection — just 3.4 defects per million opportunities (DPMO).

• 🏭 Scenario: "AquaPure Filters Ltd." – Water Purifier Manufacturer
• AquaPure is getting too many customer complaints about their home water filter system — mostly due to leaks,
weak flow, and delayed delivery.
• They apply Six Sigma to solve this and improve future designs.

• 1. 🎯 DMAIC – For Improving Existing Product/Process
• They use the DMAIC methodology to fix the problems in their current filter model.
Phase What They Do Example
Define Identify problem and goals Customers report 15% leakage in Model Z
Measure Collect data on defects 200 defects in 1,200 units; most from faulty seals
Analyze Find root causes Supplier seals inconsistent size; poor SOP compliance
Improve Implement solution Switch to better supplier, retrain staff, revise SOPs
Control Monitor improvements Install KPI dashboard and regular RFT audits

• 2. 🧪 RFT – Right First Time
• They make Right First Time a quality goal:
• Aim: 98% of units must pass all checks on first inspection
• Reduces rework, cost, and delays

• 3. 📏 KPI – Key Performance Indicators
• They track KPI metrics like:
• Defect rate (%)
• Average lead time (days)
• Customer complaints per 100 units
• RFT percentage
• On-Time Delivery (OTD)
• These KPIs show if improvements are working.

• 4. 🧾 SOP – Standard Operating Procedure
• To make sure everyone follows the new process:
• They update the SOPs for assembly, sealing, and inspection
• Workers are trained to follow them step-by-step

• 5. 🛠 COA – Corrective Action Report
• Every time a defect occurs:
• A COA report is filed
• It documents the issue, root cause, actions taken, and responsible teams
• Helps prevent the same problem from recurring.

• 6. 💡 ASMART Goals
• All Six Sigma goals are made ASMART (Advanced SMART):
Letter Stands for Example
A Ambitious Achieve 98.5% RFT
S Specific Fix leakage issue in seal line
M Measurable Reduce defect rate from 15% to <2%
A Achievable With supplier change and training
R Relevant Directly impacts customer complaints
T Time-bound Within next 60 days

• 7. 🧬 DMADV – For Designing a New Product
• Now, AquaPure wants to launch a new filter model (Model Q) without repeating old mistakes. They use DMADV
(Design for Six Sigma):
Phase What They Do
Define Understand customer needs (compact, no leaks, faster install)
Measure Gather market and competitor benchmarks
Analyze Use tools like QFD and FMEA to analyze design risks
Design Build prototypes using robust, tested components
Verify Test extensively with users; finalize production plan

• 8. 💸 COPQ – Cost of Poor Quality
• They calculate their COPQ to understand the financial impact of defects:
COPQ Category Example
Internal failure Scrap, rework due to leaking seals
External failure Customer returns, warranty claims
Appraisal cost Inspections and quality tests
Prevention cost Training, SOP writing, better design
• Reducing COPQ saves money and improves customer trust.

• 🔁 Six Sigma in Summary
Term What It Means How It Was Used
Six Sigma Methodology for reducing variation Used company-wide for defects
DMAIC Improve existing processes Fixed leakage problem in current model
DMADV Design better products from scratch Used for upcoming Model Q
RFT Make it right the first time Targeted 98% RFT rate
KPI Track measurable goals Monitored delivery time, defects, RFT
SOP Standard procedures Updated for sealing and QC
COA Report for each defect Documents causes and fixes
ASMART Specific goal setting Guided all improvement targets
COPQ Cost of bad quality Helped justify investment in improvements

• 🎯 Business Outcomes
• Defect rate dropped from 15% to 1.8%
• Customer complaints reduced by 70%
• Achieved 95% Right First Time
• Saved ₹7.5 lakh annually in rework and returns
Here's a simplified explanation of Problem Solving Tools in the context of business process and design, using a scenario
that integrates all the listed terms:

🔧 Problem Solving Tools – What Are They?


Problem-solving tools help businesses identify, understand, and fix issues in a structured and sustainable way. They
help improve efficiency, reduce waste, and enhance quality across processes and products.

🏭 Scenario: “SwiftPack” – A Packaging Company


SwiftPack manufactures boxes and cartons for food companies. Lately, customers have been complaining that the
cartons arrive damaged or wrongly labeled, affecting their production timelines.
The Operations Manager decides to apply a structured Problem Solving Framework to resolve this.

1. 🔍 RCA – Root Cause Analysis


Root Cause Analysis is used to find the real reason behind a recurring problem — not just its symptoms.
Problem: 18% of cartons are damaged when delivered.
RCA reveals:
• Weak glue used in folding
• Improper stacking during delivery
• Label print errors due to outdated software

2. 🧠 Why-Why Analysis
They use the Why-Why method to dive deeper into one issue: Why are boxes getting crushed?
1. Why crushed? → Poor stacking
2. Why poor stacking? → No stacking SOP
3. Why no SOP? → Training never included logistics
4. Why? → Logistics team was left out of process design
5. Why? → No process map for dispatch area
Now they know the problem is not just operations — it’s process design and cross-team alignment.

3. 🦴 Fishbone Diagram / Cause and Effect Diagram


They use a Fishbone Diagram to visually map the causes under categories like:
• Man – Inexperienced packers
• Machine – Weak glue machine setting
• Material – Low-quality cartons
• Method – No proper stacking SOP
• Measurement – No inspection checklist
• Environment – Wet warehouse area
This makes it easier to prioritize issues.

4. 🗺️ Process Mapping & Value Stream Map (VSM)


They then create a Process Map and a Value Stream Map (VSM):
• Process Map: Shows each step from carton printing to delivery
• VSM: Highlights which steps add value and which don’t (e.g., rework, waiting, inspection)
They discover:
• 2 rework loops
• 1 delay in labeling due to batching
• Quality checks are after packing — too late!

5. ✅ CAPA – Corrective and Preventive Action


They implement CAPA:
Type What They Do
Corrective Fix glue settings, retrain logistics team, repair delivery process
Preventive Introduce labeling software upgrade, new SOP for stacking, build a checklist for inspections

6. 📝 COA – Corrective Action Report


Each corrective step is documented in a COA report. For example:
• Issue: Weak glue
• Root Cause: Pressure setting off
• Action Taken: Standardize settings, train team
• Owner: Maintenance Head
• Timeline: 3 days

7. 📋 Action Plan
Finally, a full Action Plan is built, listing:
• All problems identified
• Responsible departments
• Timeline
• Priority level
• Status tracking
This keeps accountability clear and measurable.

🔁 Full Summary Table


Tool What It Does Example in Scenario
RCA Finds true root causes Why 18% cartons arrive damaged
Why-Why Analysis Deep dive into root causes Poor stacking traced back to training gaps
Fishbone Diagram Visual map of all cause categories Mapped glue, SOP, stacking, labeling issues
Process Mapping Visual flow of process steps From printing → packing → labeling → dispatch
VSM Identifies value-adding and wasteful steps Found bottlenecks in inspection and labeling
CAPA Structured corrective & preventive solutions Retraining, system upgrades, SOPs
COA Formal report for each corrective action Logged each fix with cause-owner-deadline
Action Plan Master list for execution & tracking 12-point plan with owners and timelines

🚀 Business Results
• Carton rejection rate drops from 18% to 1.9%
• Customer complaints cut in half within a month
• Reduced rework saves ₹1.2 lakh/month
• New SOPs and training enhance long-term stability

Here’s a simple and clear explanation of MTTR, MTBF, and Manufacturing Environments, all tied together using a
realistic scenario to show how they work in a business process and design context:

🏭 Scenario: "TechCool Industries" – Air Conditioner Manufacturer


TechCool produces air conditioning units for residential and commercial buildings. It handles different customer
demands and tracks equipment efficiency and downtime using KPIs like MTTR, MTBF, and OEE.

🔧 1. Manufacturing Environments
TechCool uses different manufacturing strategies depending on the product and customer:
Environment What It Means TechCool Example
Products made in
Standard home ACs produced in bulk and stored in
Make to Stock (MTS) advance, stored, and sold
warehouses
later
Start production only after Custom commercial AC units with specific cooling
Make to Order (MTO)
receiving an order capacity
Pre-made components are Wall-mounted ACs where filters, bodies, and remotes are
Assemble to Order (ATO)
assembled after order assembled based on customer preference
Design to Order / Engineer Fully customized, Government project requiring eco-friendly, solar-powered
to Order (DTO/ETO) designed from scratch cooling system designed from zero

⚙️ 2. MTTR (Mean Time to Repair)


• What it means: The average time taken to repair a machine when it breaks down.
• Why it matters: Lower MTTR means less downtime and higher productivity.
🛠 Scenario: If the compressor assembly line stops due to a robotic arm fault, and it takes 4 hours to repair, MTTR = 4 hrs.
If this happens 3 times and takes 3, 4, and 5 hours, then MTTR = (3+4+5)/3 = 4 hours

🔁 3. MTBF (Mean Time Between Failures)


• What it means: The average time a machine runs before it fails.
• Why it matters: Higher MTBF means more reliable equipment.
Example: The stamping machine runs for 200, 250, and 300 hours before failing.
MTBF = (200 + 250 + 300) / 3 = 250 hours
This helps TechCool schedule preventive maintenance before machines break.

📊 4. OEE (Overall Equipment Effectiveness)


• Combines availability, performance, and quality to measure equipment efficiency.
• Formula:
OEE = Availability × Performance × Quality
Example:
• Availability: 90% (few breakdowns)
• Performance: 95% (runs near ideal speed)
• Quality: 97% (few defective units)
➡ OEE = 0.90 × 0.95 × 0.97 = 82.8%
A good OEE score is above 85%. TechCool sets this as a KPI.

📈 5. KPI (Key Performance Indicators)


TechCool tracks KPI metrics to monitor production and maintenance performance:
KPI Target
OEE ≥ 85%
MTTR ≤ 3 hours
MTBF ≥ 300 hours
Order Lead Time ≤ 7 days
On-Time Delivery ≥ 95%
Backlog ≤ 10% of monthly capacity

📦 6. Backlog
• What it means: Unfulfilled orders waiting to be produced or shipped.
• Why it matters: High backlog = production delays, customer dissatisfaction.
Example: TechCool receives 1,000 orders in a month, but produces only 850 units.
Backlog = 1,000 - 850 = 150 units (15%)
Exceeds the KPI limit (10%), needs extra shifts or process improvement.
🔁 Full Walkthrough of How It All Connects
1. Customer orders vary: MTS for standard ACs, MTO/ETO for special needs.
2. Production planning adapts to manufacturing environment.
3. Equipment monitored for performance using OEE, MTTR, and MTBF.
4. Downtime reduced by tracking MTTR and preventive maintenance scheduled based on MTBF.
5. Productivity and quality tracked using KPIs.
6. Delayed orders create backlog, so TechCool adjusts resources.

✅ Final Summary Table


Term Meaning Example
Make to Stock Produce in advance Standard ACs stored in warehouse
Make to Order Produce after order Commercial units built to spec
Assemble to Order Assemble parts post-order Wall ACs with custom filters
Design to Order Full custom product Solar-powered AC for govt building
MTTR Avg. time to repair 4 hours per repair
MTBF Avg. time before failure 250 hours of machine uptime
OEE Equipment effectiveness Target: 85%+
Backlog Pending unfulfilled orders 150 units pending
KPI Key metrics to track success MTTR, MTBF, OEE, backlog %

You might also like