Lean and Jidoka Notes

  • TGM Consultancy & Training presents a Lean Introduction in collaboration with UTM Johor Bahru.

Tools for 3P

  • Involves Production Preparation Process.

7 Ways

  • Refers to a methodology, likely for problem-solving or process improvement.

Pugh Matrix

  • When to Use:

    • To narrow down a list of options to a single choice.

    • For decisions based on multiple criteria.

    • After list reduction has made the options manageable.

  • Typical Situations:

    • Selecting an improvement opportunity or problem to address.

    • Choosing a single solution or problem-solving approach.

    • Deciding on one new product to develop.

  • Steps to Use/Construct Pugh Matrix:

    1. Choose/Develop Criteria for Comparison:

    • Examine customer requirements.

    • Generate engineering requirements and targets.

    • Set evaluation criteria appropriate to the situation.

    1. Select Alternatives to Compare:

    • Discuss and define the list of criteria.

    • Identify criteria that must/must not be included.

    • Reduce criteria using list reduction and multi-voting.

    1. Generate Scores:

    • Assign relative weights to each criterion based on importance (distribute 10 points among criteria).

    • Scores assigned after team discussion and consensus or individual assignment followed by aggregation.

    1. Compute Total Score:

    • Draw an L-shaped matrix.

    • Write criteria and weights along one edge, options along the other.

    • The group that fe of options usually occupies the vertical edge.

    1. Find Variations on the Scoring:

    • Evaluate each choice against the criteria.

    • Method 1:

    • Establish a rating scale for each criterion (e.g., 1, 2, 3 or 1, 2, 3, 4, 5 or 1, 4, 9).

    • Ensure rating scales are consistent.

    • Word criteria and scales so that the high end of the scale is the rating that would lead to selection (e.g., most impact on customers, greatest importance, least difficulty, or greatest likelihood of success).

  • Pugh Matrix Example Method 1

    • Rating Scale: 5 - Excellent, 4 - Above Average, 3 - Average, 2 - Below Average, 1 - Poor, 0 - N/A

    • Various operations numbered from 10 to 160, and criteria such as Meet Takt Time, One Piece Flow, and Minimum Operator Involvement are rated.

    • Method 2:

    • Establish a baseline (alternative or current product/service).

    • Rate other alternatives compared to baseline: worse (–1), same (0), or better (+1).

    • Finer scales can be used (e.g., 2, 1, 0, –1, –2 or 3, 2, 1, 0, –1, –2, –3).

    • Positive numbers should reflect desirable ratings.

    • Multiply each option’s rating by the weight, then add the points for each option.

    • Select the top 3 highest scores to foster meaningful discussion and team consensus.

  • Pugh Matrix Example (Method 2):

    • Needs including Cost Effective, Reliable, Low Maintenance, Flexible, and Environmentally Friendly are ranked.

    • Design Concepts (Robotic, GPS Guided, Astroturf, Neighbor kid) are compared against a DATUM concept.

  • Consideration:

    • Criteria often fall under effectiveness, feasibility, capability, cost, time required, support, or team enthusiasm.

    • Commonly used criteria:

    • Within team's control.

    • Financial payback.

    • Resources required.

    • Customer’s pain points.

    • Urgency of problem.

    • Team’s interest.

    • Effect on other systems.

    • Management’s interest/support.

    • Difficulty level.

    • Time required.

Solution Selection

  • Root causes addressed by the solution.

  • Extent of problem resolution.

  • Cost to implement.

  • Return on Investment (ROI) and resource availability.

  • Ease of implementation.

  • Time until full implementation.

  • Cost to maintain.

  • Ease of maintenance.

  • Support/opposition to the solution.

  • Team enthusiasm.

  • Team control of the solution.

  • Safety, health, and environmental factors.

  • Training factors.

  • Potential effects on other systems, customers, or suppliers.

  • Value to customer.

  • Problems during implementation.

  • Potential negative consequences.

  • Select the top 3 scores.

  • Mock up line based on the highest score first.

  • If the flow is not smooth, change the mock up to use the 2nd or 3rd higher score.

How to Fill up 7 Ways Template

  • Idea / Option:

    • #1. Fill in the process sketch (e.g., current line layout, material flow, sequence).

    • #2. Fill in CTQs/Quality requirements (e.g., output needed, outcome expected).

    • #3. Put down each idea; use sketches/drafts/layouts/pictures.

How to Fill up Idea Evaluation Sheet Template

  • Assessment Criteria:

    • #1. Fill in all CTQs for evaluation, including those defined in quality requirements in 7 Ways.

    • #2. Put down the Weight (Wtg) based on criteria (1 = Good to Have, 2 = In between, 3 = Mandatory).

    • #3. For each idea, put down the score based on each criterion (1 = Poor, 2 = Below Average, 3 = Average, 4 = Above Average, 5 = Excellent).

    • #4. Multiply each score with Wtg to get Wtg score for each criterion.

    • #5. Total up all Wtg scores.

    • #6. Compare each total Wtg score; select top 3 scores to proceed with try storming, mock up, or trial run.

Example

  • Current Layout Issues:

    1. Too much WIP.

    2. Low UPPH.

    3. Too many headcounts used.

    4. Water spider overloaded.

    5. Low output due to output not sync.

  • Quality Requirements:

    1. Improved material flow.

    2. Optimize space utilization.

    3. Optimize headcount utilization; optimize water spider workload.

    4. Reduce WIP quantity in line.

    5. Improve output and UPPH.

Idea Evaluation Sheet Example:

  • Assessment Criteria includes Material flow, Space, Headcount, WIP, Output with corresponding weights and scores for each idea (Idea 1 to Idea 7).

  • Total scores are calculated for each idea.

5 Why Analysis

  • A structured approach to repeatedly ask “Why” to:

    • Understand the underlying cause of an issue.

    • Generate effective corrective action to mitigate the issue.

    • Prevent future occurrences.

  • Problem Statement -> Root Cause

  • A simple root cause analysis tool used to explore “Why” five times to reveal the actual root-cause.

    • 1st Why – Symptom

    • 2nd Why – Excuse

    • 3rd Why – Blame

    • 4th Why – Cause

    • 5th Why – Root-Cause

  • Asking “Why” leads upstream in the process.

Why do a 5 Why analysis?

  • Due to factors that challenge the effectiveness and sustenance of implemented solutions:

    • Problem analysis at the cause  no deep-dive into the actual root-cause.

    • Analysis and countermeasures with assumption and pre-defined solutions  not 3 GEN.

    • Countermeasures or solutions to the problem at surface  symptom level.

    • Workaround the problem instead of solving it  shortcut for problem-solving.

5 Why as part of the Practical Problem Solving Approach

  • Grasp the situation

  • 5 WHY Methodology Analysis

  • Countermeasure Implementation

  • Evaluation & Adjustment

  • Practical Problem Solving Steps:

    • Countermeasure Implementation: Establish ideas (may apply 7 Ways methodology), try-storm the ideas through trial-run or simulation, and implement the countermeasure in a smaller scale.

    • Grasp the Situation: Identify and clarify the problem, and locate the Point of Origin (POO).

  • Evaluation and Adjustment: Evaluate the effectiveness of the countermeasure, make adjustments, monitor, and yokoten (proliferate) to all areas.

    • 5 WHY Methodology Analysis: Select top actual defects for analysis, apply 3G at POO - Genchi (Actual Place), Genbutsu (Actual Product/Process/Part), Genjitsu (Actual Fact/Data/Value). Open Mind - Repeatedly ask questions (5 ‘Why’) with no assumptions, no pre-defined answers. I – reasons outside I-Circle are excuses, and reasons inside I-Circle are root-cause.

5 Why Funnel

  • Grasp of Situation:

    1. Initial problem perception (large, vague & complicated).

    2. Clarify the problem; find the "Real" problem.

    3. Locate POO.

  • Investigation of root cause:

    1. 5 WHY methodology; basic Cause & Effect analysis investigation leads to Root Cause.

    2. Countermeasure.

    3. Evaluate.

    4. Yokoten.

5 Why – Day to Day Example

  • Situation: Traffic ticket!

  • Problem Statement Battery flat (no power)!

  • Root Cause: Over slept!

  • Why’s:

    • Why? Over Speeding!

    • Why? Late for work!

    • Why? Alarm clock not working!

    • Why? Change new battery!

    • Why? Battery flat (no power)!

  • How to Prevent ???

    • Change evaluation policy for purchasing agent. Battery changing frequency to be set or Alarm clock to be connected to the main power supply.

5 Why Example

  • Question (Why)? - Causes - Condition - Correspondence

  • Example of Puddle of oil on the floor.

  • Countermeasure:

    • Change evaluation policy for purchasing agent.

  • Why did we get those gaskets at a good price ? Because the purchasing agent gets evaluated on short-term cost savings.
    -Why did we buy Gaskets made from Inferior Material ? Because we got those gaskets at a good price.
    -Why has the gasket deteriorated ? Because we bought gaskets made of inferior material.
    -Why is machine leaking ? Because the gasket has deteriorated.
    -Why there is a puddle of oil on the shop floor ? Because the machine is leaking oil

OJidoka

Introduction to Jidoka

  • JIDOKA

    • Inspection

    • Autonomation

  • Stop @ Abnormality

    • Poka-Yoke

    • A-B System

    • Inspection

    • Fish Market

    • Andon

    • Hanedashi

Toyota Production System (TPS)

  • Jidoka serves as one of the two sturdy pillars (the other is Just-in-Time production) supporting the roof structure of Flex Lean Enterprise (FLE).

Introduction to Jidoka

  • Jidoka is the principle used in autonomation to complement the automation process with human intelligence.

  • The principle requires early detection of abnormality and stops to correct it at the earliest stage possible.

  • Zero Defect is the aim

  • After zero defect is achieved, the next step is going for productivity improvement through Autonomation

Elements of Jidoka

  • Jidoka consists of 2 elements

    1. Element 1: Stop at Abnormality

    • Consists of 5 core tools

    • Stopping at Abnormality will ensure that the process does not continue when an error is detected

    • The goal for Stop at Abnormality is to achieve Zero Defect

    • Poka-Yoke ( Fool Proof)

    • A-B System

    • Inspection

    • Fish Market

    • Andon (abnormality notification system)

    1. Element 2: Autonomation

    • Consist of 1 core tool

    • After zero defect is achieved element 2 is to improve productivity

    • Hanedashi (auto unload)

Key Elements of Jidoka

  • These Methods Sustain the Just in Time Production System

  • Jidoka can be further split into

    • Element 1: Stop at Abnormality

    • Stopping at Abnormality will ensure that the process does not continue when an error is detected

    • Element 2: Autonomation

    • Autonomation could further defect generation.

  • Make Problems Visible & Stop To Fix Them (Root Cause)

    • Visual Controls / Andon

    • Automatic Machine Stops

  • Build In-Station Quality

    • Mistake Proofing / Poka-Yoke

    • TPM

    • Root Cause

  • Separate Machine Tasks from Human Tasks

    • Processing, Holding, Feeding, Stopping, Returning and Unloading

What is Zero Defect?

  • Zero defect is a way of thinking and doing that reinforces the notion that:

    • Defects are not acceptable

    • Everyone should “do things right the first time”

    • Convey the idea that you can increase profits both by eliminating the cost of failure and increasing revenues through increased customer satisfaction.

    • 1. Do not pass defect

    • 2. Do not make defect

    • 3. Do not accept defect

    • 4. Do not rework

4 Steps to achieve Zero Defect

  1. Data collection and initial analysis of the data received from customer or from the internal process

  2. Root Cause Analysis (Use 5 Whys + 1 How and 3G)

  3. Counter Measure (Poka-Yoke)

  4. Evaluation and Deployment

Step 1 – Data Collection and Analysis

  • Input (What is used as a starting point): Data. Sub-step A: Customer Data On Defects, Sub- step B: Internal Data On Internal Defects, Sub-step C: Observation / Findings.

  • Process or Methodology (How it should be done): Enforce containment (short-term fix), then do a Pareto chart, map to an Auto Quality Matrix.

  • Expected Output (What should you achieve): A prioritized list of issues, with identified owners empowered to solve them.

  • Suggested Tools: Pareto Chart, Auto Quality Matrix (What can help you do it).

Step 2 – Root Cause Analysis

  • Input (What is used as a starting point): a description of the problem.

  • Process or Methodology (How it should be done): Shop floor observation for Genchi, Genbutsu, Genjitsu (3G). Then use 5 Whys + 1 How) with Value Stream Mapping (Existing Process), and 7 QC tools.

  • Expected Output (What should you achieve): The root causes to the problem.

  • Suggested Tools (What can help you do it): 5 Why's, Value Stream Map, 7 QC Tools, DOE/DFSS.

Step 3 – Counter Measures

  • Input (What is used as a starting point): Root causes from the previous step

  • Process or Methodology (How it should be done): Use Value Stream Mapping, Initiate Kaizen, then apply Poka-Yoke and roll out applicable changes.

  • Expected Output (What should you achieve): Poka -yoke the solutions, Roll out applicable changes to the supplier and customer (as required), Roll out applicable changes to NPI and the DFM guidelines.

  • Suggested Tools (What can help you do it): Trouble shooting guides, DOE, 7 Ways, AB System, Inspection, Poka Yoke, Tolerance analysis.

Step 4 – Evaluation and Deployment

  • Input (What is used as a starting point): Counter measures from the previous steps.

  • Process or Methodology (How it should be done): Follow the modified process with Poka-yoke, monitor Poka-yoke effectiveness, then post in the Best Practice Library and reinforce during the weekly QMI calls to include the best practices for the world-wide deployment

  • Expected Output (What should you achieve): Customer and internal feedback, CSI scores and RMA values, A Preventive measure to stop the process before abnormalities occurs.

  • Suggested Tools (What can help you do it): Before and after measurements, Control charts and Hypothesis charts, Applicable statistical tools, Andon, Pokayoke, Fish Market.

Zero Defect Approach - Link to Jidoka

  • Compare traditional method against lean Method

Zero Defect Approach - Link to Jidoka

  • Identify root cause

  • Corrective + Preventive Action

    • Preventive Measures / Andon / Poka-Yoke

  • Productivity Improvement

  • Zero Defect Approach = Jidoka (Stop at Abnormality -> Autonomation)

Zero Defect Approach - Link to Jidoka

  • Quality is built into each process. Jidoka: Send 100% defect free product to the next step

Element 1 of Jidoka: Stop at Abnormality

  • Stop @ Abnormality

    • Poka-Yoke

    • A-B System

    • Inspection

    • Fish Market

    • Andon

Stop at Abnormality

  • Stop at abnormality is one of the core principles of Jidoka that uses the mechanism to immediately stop producing whenever a defect is found.

  • Examples of Stop at Abnormality. Daily life -> Fuel gauge. Office -> Wrong password. Supply Chain -> FlexPulse. Operations -> triggering system.

Tool Number One: Inspection

  • Stop @ Abnormality

  • Poka-Yoke

  • A-B System

  • Inspection

  • Fish Market

  • Andon

3 Types of Inspection

  • Inspection provides 100% inspection and prevents mistakes from occurring from the source. Example: Poka - Yoke

  1. Judgment: Defect discovery after-the-fact. Involves sorting defective parts. Not effective. Ex; Visual Inspection

  2. Informative: Visual and audio indicators that tell the operator the status immediately to prevent defects. Ex; Pressure gage indicator light and buzzer.

  3. Source: Defect prevention by controlling conditions that cause defects. EX: Error Proofing devices or Poka-Yoke.

Type 1: Judgment Inspection

  • Definition (Defect discovery after-the-fact (post mortem) inspection performed at downstream processes). Involves sorting the defects. Also, “inspecting in quality” is not an effective quality management approach since it does not improve the process.
    -Characteristic (May not catch defects prior to the customer. Longer feedback loop. Visual Inspection at end of assembly line.

Type 2: Informative Inspection

  • Definition (Visual and audio indicators that tell the operator the status immediately to prevent defects). Such as self inspection and successive Inspection.

  • Characteristic (Defect reduction (medical exam) inspection which provides feedback to the process more quickly, Linked to in-process inspection. Provides relatively rapid feedback to the previous process). Visual Inspection at end of assembly line

Type 3: Source Inspection

  • Source Inspection is always the best choice as it keeps errors from becoming defects
    -Defect prevention by controlling conditions the that influence mistakes or cause defects. Example Poka-Yoke (Error Proofing or Mistake Proofing) devices, provides immediate feedback.
    Can include real time online Statistical Process Control. Enables Zero Defect Lines

Type 3: Source Inspection (Continued)

  • The only kind of inspection that focuses on complete elimination of defects.
    It catches errors and gives immediate feedback before processing, that keeps errors from becoming defects.
    Also Enables Zero Defect Lines

Tool Number Two: Andon

  • J I D O K A

    • 1 Stop @ Abnormality / Poka-Yoke / A-B System/Inspection/Fish Market/ Andon

    • 2 Autonomation /Hanedashi

Andon

  • Definition Japanese term referring to “lantern”, it is a visual control that would light up as a cue to inform operators about what type of problem has arisen and where does it happen. made to be triggered when an issue is ABOUT to happen so a remedial action can be taken.

  • Purpose Communicates important information and signals that are needed for immediate action by Team Leaders or Supervisor. Production line can be stopped automatically.

Andon – Signal for action and Management Escalation Process

  • Signal types can be heard it or see it and design a standard work process and escalation. The Supervisor is required to restart the process.

Andon – How does it work?

  • Workstation -> Andon cord is pulled for problem -> special tone is heard -> Team Leader responds and if he cannot resolve the problem -> line will stop at the Fixed Postion Stop and will only resume with Andon being deactivated once the problem is solved.

Andon Cycle

  • Andon Cycle: Defect occurrence -> Abnormality Detected -> Andon Activated -> Response/Decision Time->Process Stop Activated with time noted.

Andon Do and Don’t

  • What matters need to focus on (urgent issue) and issue that can be solve in verbal communication

Examples Andon

-Operations Andon at the production line, Yellow light at the traffic signal, Email reminder and Kanban Pull System.

Tool Number Three: A-B System

  • Stop @ Abnormality Poka
    Yoke Inspection Fish Market Andon A-B System Autonomation Hanedashi

A-B System

  • A way to regulate the working relationships between two machines or operations to control overproduction and ensure balanced use of resources. Daily Example Drive Thru operator at McDonalds.

Tool Number Four: Poka- Yoke

1 Stop @ Abnormality
Poka-Yoke
Inspection
Fish Market
Andon
A-B System
2 Autonomation
Hanedashi

Poka-Yoke

  • Poka-Yoke is a mechanism that is put in place to prevent human error. The purpose of a Poka-Yoke is to inhibit, correct or highlight an error as it occurs. Poka-yoke means avoid blunders in Japanese.

Poke-Yoke (Mistake Proofing) – In Station Quality

  • prevent making/sending/accepting defect, is build in to the process and example of right processing position.

Poka-Yoke Methods

  • can use 3 approaches to analyze process.
    -Fixed value method (detect feature of the product shape)
    -Motion Step Method (number of movements have been made)
    -Characteristics Approach(Identify if contact is made between the device an a future of the product ).

3 Levels of Poka- Yoke

Product, Process and Visual and audio Alets levels.

3 Levels of Poka-Yoke - Examples

Bend pin was found and the issue was solved through the introduction of a modified jig with proper guidance slot for alignment, and install labels on cables for the ease of identification

Red Flag Conditions

as fast ly similar parts such as O rings, clips and eners
environmental conditions, multiple steps or Ineffective standards

Guidelines for Mistake Proofing

  • describe defect , observe the sequence and steps, identifies errors contributing factors, test the effectiveness of the device required to prevent the error or defect

Tools for Mistake- Proofing

error detection and alarms/checklists, limit switches,counters, guide pins of different sizes

Examples of Poka- Yoke

-Wave Soldering,How it works is designed to catch the missing manual insert parts and also is able to detect wrong orientation and
Spelling and grammar check

Quiz

1.Level in poka Yoke: Labeed cord, medicine cup

Tool Number Five: Fish Market

2 Autonomation Hanedashi Fish Market Inspection Andon A-B System Poka-Yoke,

Fish Market

-Fish Market is a simple visual application that is triggered for immediate attention when a defect is found
The main aim of Fish Market is to transfer information about problematical products in realtime and provide solutions to the problem
and the defect will display on on public platform to everyone and use the automationbased andon system

Fish Market Set Up and Procedure

by operation team need to
Identify an area to set up Fish Market and need Andon light, escalation path, buzzle visual management
then Supervisor should highlight that defect unit to Fish market and escalate the defect and also Implement corrective actions and monitor the results.

Fish Market Guidelines

Display, procedure and escalation define responsibility, process
Only fresh defects display
Department are part of the discussion Visual Aids
Sensor Trigger system
Make sure defect can be Retrieved Easily then follow on activities.

Set-up of Fish Market

Fish market
832
0189
EPALLER
HOURLY DEFECT ACTION LIST
K TH PANEL
FRESH MARKET
DEFECT TRACKING SHEET
KEYSCRITIVE
STATION
Fish Market Scalation Organisation Chart
If not solved within 2 hours, MBU supervisor report to BU leader
It not solved within minites, Mpervisor report to Function team leader in Bo
MBU superviuepont to responsible POC
ME PE OA DEPT NAME M SHIFT NAME
Contact Contact Contact Contact
Escalation Process Andon Light

Quiz

Inspection method ,what it trigger,and point
Element 2 of Jidoka:
Autonomation
Autonomation
Hanedashi

Autonomation

autonomation. It describes machines that automate a process but are also intelligent enough to know when something is wrong and stop immediately.
it needs human attention only when it stops. processaiming to prevent the production of defective products, eliminate overproduction and focus attention on understanding the problems and ensuring that they do not recoccur..

Automation V S Autonomation

Compare between people of operate by a lot of move. Compare machine by needs Operators .breakdown constalty .all defact.need Operators to train.and minimum movement.Operators only need to load and un-load.breakdown is eliminited and all defact Stopa
neec. need Operators to train

Autonomation

Tool for Autonomation: Hanedashi A HanedashiInspection ndon A-B System Poka-Yoke Autonomation nedashi,
Key for of cycle is Comple then go to the next machine.

Autonomation

Criteria must be met to implement auto load then it ready .machine need to have same size then work station quality to implement Haneda

Examples of Autonomation

Functional Tester how about you? daily and Logistic automation.

Quiz

Which state of Fales .Autonomation requires minum movement-Autonomation helps in reduce power and find fake .1. It is a device that requires operators to pick up and load parts in order to work
Which Is Haneda a

Recap Jidoka

Jidoka Complementation to the automation process with human touch Autonomation Machine is enabled to stop automatically when a defect is found Zero Defects is a way of thinking and doing that reinforces the notion that defects are not acceptable.
It is not a system, 5 tools for Stop at Abnormality Inspect is for Judgment but used to it
Visual that uses the lighting cue to indicate defect occurrence-Andone or A-B System to ensure balanace.
Mistake Proofing device
displays new defects Hanedashi is one of the tools of AutonomatioA quick and final glance through the entire module Jidoka Stop at abn Normal.
Stop Jidoka approach aintained A qui
Jidoka+Zero Defect
Stop at Abnormality
Hanedashi