Ishikawa fishbone diagram Skorkovský ESF MU KPH. Introduction (FBD= fishbone diagram) FDB is a tool to find out relationships: FDB is a tool to find out.

Slides:



Advertisements
Similar presentations
Air Education and Training Command I n t e g r i t y - S e r v i c e - E x c e l l e n c e Time Management MSgt Pablo Morales HQ AETC/LG-EM 05 Sep 2002.
Advertisements

Managing IT Risk during a Global Business Merger Cheryl Danson April 2005.
CAUSE & EFFECT DIAGRAM (Fishbone or Ishikawa Diagram) Dr
TOOLS OF TQM Abdulla Jassim Abdulla. INTRODUCTION Data-Driven Methodology Data generated by processes Statistical interpretation Seasonal variations New.
A3 Training Session. Introduction…. We all are involved in… – Looking for ways to save resources – Finding ways to improve quality – Fixing problems –
A3 PROBLEM SOLVING TOOL: Date: Contact: SOLUTIONS / COUNTERMEASURES What solutions will solve the root causes? (Tools: Brainstorming and Affinity Diagram)
1 McGraw-Hill/Irwin Copyright © 2004, The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Enterprise e-Business Systems.
Ishikawa fishbone diagram
ISHIKAWA DIAGRAM – Tool for quality management Marit Laos IS Project Management
Business Operating System
Customer Service & Customer Protection in MANSELL
Total Quality Management
Root Cause Analysis Presented By: Team: Incredibles
Effective Problem-Solving: Getting to the Heart of the Matter © Copyright 2011– Lean Homecare Consulting Group, LLC This presentation is distributed for.
Introduction to SAP R/3.
Practicum November 16, 2006 Group 4 Jeff Dittman, Bret Haney, Ryan Knapp and Elizabeth Wong.
Ensuring Quality and Productivity If you forget the customer, nothing much else matters. —Anne Mulcahy, CEO, Xerox Corporation Chapter 2 Copyright © 2010.
Pinnacle Seven Technologies - Gateway to Solutions Pinnacle Seven Technologies - Gateway to Solutions.
Pareto analysis-simplified J.Skorkovský, KPH. What is it ? tool to specify priorities which job have to be done earlier than the others which rejects.
Eleventh Edition 1 Introduction to Information Systems Essentials for the Internetworked E-Business Enterprise Irwin/McGraw-Hill Copyright © 2002, The.
Process Management Process improvement (for Chronic problems) Process control (for Sporadic problems)
Introduction to MS Dynamics NAV IX. Ing.J.Skorkovský,CSc. MASARYK UNIVERSITY BRNO, Czech Republic Faculty of economics and business administration Department.
Information Systems for Business Integration: EDI, SCM, CRM Systems
Traditional Approach Two steps forward, one back
Quality Prepared By: Ali Siddiqi.
BM Unit 2 - L051 Higher Business Management Unit 2 Learning Outcome 5 Operations.
2 Breakout Session # 205 Tim Ortel, CPCM, Intuitive Surgical Date 15 April 2008 Time 2:10 PM – 3:10 PM Can Contracting Be “Leaned”?
Florida Quarterly Meeting Root Cause Analysis Florida Quarterly Meeting Root Cause Analysis January 12, 2011 Christy Hormann, MSW, CPHQ Project Leader-PIPs.
SANILAB THE LOGICAL INDUSTRY CHOICE. SANILAB Industry edition Risk management is costly and stressing for production, quality and any other people of.
BASIC ERP ARCHITECTURE Skorkovský, KPH, ESF MU,Brno.
Root Cause Analysis Training and Explanation 1.
Very concise introduction MPH_AOMA Jaromír Skorkovský, KPH,ESF MU BRNO.
Quality Tools Instructor: Hank Sobah
Oracle Business Models
MS Dynamics – nothing simpler
MS Dynamics NAV – nothing simpler Skorkovský KPH ESF MU.
Vanguard meeting 18 July 2014 Ministry od Labour and Social Affairs.
Total Quality Management. What is Quality? Quality is a relative concept. Quality is in the eye of the beholder Perfection Doing it right at the first.
1 1 Introduction to Navision 4.00 ESF –MU, Czech Republic Jaromír Skorkovský, MS., PhD.
2015 NetSymm Overview NETSYMM OVERVIEW December
Gerhard Steinke1 Enterprise Requirements Planning (ERP) Customer Relationship Management (CRM) Data Warehousing.
Seven Old Tools of Quality Management
Introduction to MS Dynamics NAV II. (Sales Order) Ing.J.Skorkovský,CSc. MASARYK UNIVERSITY BRNO, Czech Republic Faculty of economics and business administration.
© 2005 Wiley1 Total Quality Management Chapter 5.
-To insert a Zurich picture click on the "camera"-icon in the Zurich CI toolbar and follow the instructions. -To insert a picture from your personal files,
Determining the Root Cause and Corrective Action of a Problem World Class Solutions for Global Applications Riverhawk.
Risk management. Definition and Aim  Risk management is examine systematically all risks and react on them, taking into account all the effects of.
QUALITY MANAGEMENT II Total Quality Management. LEARNING OBJECTIVES …to understand the concept of Total Quality Management …to be able to use the tools.
Bridge Reading T1 Lesson 22. Objectives You will learn several note-taking techniques that you can use to monitor and increase your reading comprehension.
BASIC ERP ARCHITECTURE Skorkovský, KPH, ESF MU,Brno.
BASIC ERP ARCHITECTURE Skorkovský, KPH, ESF MU,Brno.
Introduction to MS Dynamics NAV XVI. (CRM) Ing.J.Skorkovský,CSc. MASARYK UNIVERSITY BRNO, Czech Republic Faculty of economics and business administration.
1 Information Systems for Business Integration BUS Abdou Illia, Spring 2007 (Week 13, Thursday 4/5/2007)
South African project Masaryk University
Ishikawa fishbone diagram
Ishikawa fishbone diagram
Ishikawa fishbone diagram
Overview (1 of 2) Definition Use within organizations
Introduction to MS Dynamics (Customer Relationship Management)
Ishikawa fishbone diagram
Abdulla Jassim Abdulla
Introduction to Projects
Ishikawa fishbone diagram
Fishbone Diagram Tool Management Is the machine calibrated?
Ishikawa fishbone diagram
Ishikawa fishbone diagram
Fishbone Diagrams (cause and effect, or Ishikawa diagrams)
Ishikawa fishbone diagram
Ishikawa fishbone diagram
Presentation transcript:

Ishikawa fishbone diagram Skorkovský ESF MU KPH

Introduction (FBD= fishbone diagram) FDB is a tool to find out relationships: FDB is a tool to find out relationships: Use in QM especially in automotive industry Use in QM especially in automotive industry On of the tool set used to create so called 8D report (8 disciplines=FBD+5WHYs+PA+QM) On of the tool set used to create so called 8D report (8 disciplines=FBD+5WHYs+PA+QM) Another tool : 5 WHYs – will be cleared later Another tool : PARETO=PA analysis will be shown later Another tool : 5 WHYs – will be cleared later Another tool : PARETO=PA analysis will be shown later EffectCause

Fishbone diagram Dissatisfied worker MachinesManagement Mother NatureMen ( Methods, Material, Manpower, Measurement, Machines, Mother Nature,Management) Training Salary Obsolete Dangerous Treacherous Incapable To hot Terrible cold

Some chosen problems which could be find out during ERP support process I long response time to requirements long response time to requirements requirement is directed to unsuitable consultant requirement is directed to unsuitable consultant bad documentation about service action (poor log) bad documentation about service action (poor log) people ask repeatedly same questions at different moments and different consultants are asked people ask repeatedly same questions at different moments and different consultants are asked solution of disputes :complaint- standard service solution of disputes :complaint- standard service payment asked for supplied services payment asked for supplied services 1. how much (to whom, type of task, type of the error- see diagram 2. starting time for invoiced services, response time 1. requirement is handed over till the problem is solved 2. time of starting solving -solved 3. start of implementaion of the bad object till end of testing 4. training

bad training methodology bad training methodology bad consultants bad consultants bad communication protocol bad communication protocol 1. telephone SKYPE lack of interest of the management of both parties lack of interest of the management of both parties right specification of reaction time right specification of reaction time specification to the error types and related response times specification to the error types and related response times response time of the distributor (ERP integrator ERP) response time of the distributor (ERP integrator ERP) Some chosen problems which could be find out during ERP support process II

Diagram – response time handed over requirement find suitable resource (K1) K1 starts solving K1 solved K1 did not solved K1 handed over to distributor (D) D started work D solved the problem D ->K1 K1 handed over to customer RESPONSE TIME RESPONSE TIME II = active work = idle time Telephone call

Fishbone diagram-support Dissatisfied customer MachinesManagement Mother NatureMen ( Methods, Material, Manpower, Measurement, Machines) Phlegmatic person reacts later than expected Bad SW for support (HELP DESK) Bad communication Interest in golf only Incapable Good weather Consultant is on sick leave Consultant takes holiday Bad weather Lower quality of the consultants Low salary Bad training HR have a bad recruitment policy heart of the problem

Fishbone diagram-SA Project Backbone Project can be delayed Interpersonal communication Management of the project Mother Nature Men ( Methods, Material, Manpower, Measurement, Machines) A lot of new functions were not implemented in prototype Communication betwwen department managers is insufficient Low Budget Not agile project management Power blackout Consultant is on sick leave Servers in Czech Republic are inaccessible Lower level of understanding Language imperfection Traíning underestimation Difficulty to undesrstand modern ERP Storms Intenet troubles Bad weather Cost world beats Throughput world No el. generators

Dissatisfied employee I

Dissatisfied employee II

5WHYs WHY 1 :Why my car had stopped ? WHY 1 :Why my car had stopped ? No petrol in tank No petrol in tank WHY 2 :Why i did not have a petrol in my tank ? WHY 2 :Why i did not have a petrol in my tank ? I did not buy in the morning on my way to work WHY 3 :Why i did not buy a petrol ? I did not buy in the morning on my way to work WHY 3 :Why i did not buy a petrol ? No money in my pockets No money in my pockets WHY 4 : Why no money i my pockets? WHY 4 : Why no money i my pockets? Evening poker Evening poker WHY 5 : Why i did not win a poker game? WHY 5 : Why i did not win a poker game? I do not know how to bluff! I do not know how to bluff!

5WHY s Cause Effect

TQM and Ishikawa FBD and Pareto Reject type (effects); Reason 1 (cause) Reason 2 (cause) Reason 3 (cause) Reason 4 (cause) L L L Manual for urgent reject cause elimination (to establish correct priority of remedy actions) Score Inventory Suppliers Machines Measurement Every reject type ->one Ishikawa diagram (electronic version) Reject statistics Filter date Filter Item Rejects Total Bad size, rusty, overflow, bad colour,…

Pareto chart : possibility to split up reject and setup priorities Lorenz curve High priorities

Pareto analysis per every type of reject – next step -> practical example of Pareto use in ERP MS Dynamics NAV 15 Type of rejectCause 1Cause 2Cause 3Cause 4Cause 5Cause 6Total L L L L L L L L L L CC5 %C1 %C3 %C2 %C4 %C6% L136,3631,8218,189,094,550,00100 Lorenz curve36,3668,1886,3695,45100,00 Higher priorities for reject type L1 36,36 36, ,82 We need to improve (remedy) firstly causes C5 a C1 !!!

Pareto analysis II

Pareto analysis II - data Difficulty Difficulty Resignation Resignation Underestimation Underestimation Low motivation Low motivation 6 - (35,29 )- (35,29) 6 - (35,29 )- (35,29) 5 - ( 29,41 )- (64,71) 5 - ( 29,41 )- (64,71) 4 - ( 23,53 )- (88,24) 4 - ( 23,53 )- (88,24) 2 - ( 11,76 )- (100,00) 2 - ( 11,76 )- (100,00) Frequency Freq (%) Freq accum(%)

Pareto analysis II

Vilfredo Pareto in person… Akira Ishikawa in person…