Root Cause Analysis Workshop Pima Medical Institute, Albuquerque, New Mexico Friday; May 18, 2007; 8:30 am.

Slides:



Advertisements
Similar presentations
EICC Working Hours Taskforce KPI Scorecard
Advertisements

DIGNITY THROUGH ACTION WORKSHOP
Radiopharmaceutical Production
Root Cause Analysis for Effective Incident Investigation Christy Wolter, CIH Principal Consultant Environmental and Occupational Risk Management (EORM.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
Integration of Quality Into Accident Investigation Processes ASQ Columbia Basin Section 614 John Cornelison January 2008.
Introduction to effective Incident/Accident Analysis
Software Measurement and Process Improvement
Fundamentals of Information Systems, Second Edition
Systems Analysis I Data Flow Diagrams
[Insert Exercise Name] Evaluator Briefing and Guidance.
Root Cause Analysis: Why? Why? Why?
ESC/EN Engineering Process Compliance Procedures August 2002.
1-2 Training of Process FacilitatorsTraining of Coordinators 3-1.
Overview of DMAIC A Systematic Framework for Problem Solving
Michael Solomon Tugboat Software Managing the Software Development Process.
What is Business Analysis Planning & Monitoring?
1 Software Reviews - FTR SWENET Module QUA2. Formal Technical Review u Features – Formal v Scheduled event v Defined procedure v Reported result – Technical.
Systems Analysis and Design: The Big Picture
1-2 Training of Process FacilitatorsTraining of Coordinators 4-1.
Degree and Graduation Seminar Project Management Processes
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Part 4:
1 Accreditation and Certification: Definition  Certification: Procedures by which a third party gives written assurance that a product, process or service.
Guidance Notes on the Investigation of Marine Incidents
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Company Confidential Improvement Opportunities for Audit Reporting Tony Marino and Rick Downs July 19-20, 2012 Registration Management Committee RMC Workshop.
Accident Investigation. Accident Investigation Goals Preparing the investigation team Conducting the investigation Quiz.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Root Cause Analysis Training and Explanation 1.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
SacProNet An Overview of Project Management Techniques.
Virginia’s Person Centered Planning Process. The Four Phases of Planning Sharing Information Getting ready for planning Planning Together Keeping Track.
Project monitoring and Control
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Participate in a Team to Achieve Organizational Goal
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 2 Project Management Cycle.
Lecture # 17 PRM 702 Project Risk Management Ghazala Amin
26 November 2007 Revision 4 RCM2 Case Study Project Plan Cooling Fan System (topic link)
STAKEHOLDER MEETING Selecting Interventions to Improve Utilization of the IUD City, Country Date Insert MOH logoInsert Project logoInsert USAID logo (Note:
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
Reading First Overview of 2004 Site Visits Jane Granger, M.S.
Initiation and Planning for Success Sridhar Seshagiri Rao, PMP Innova Solutions Inc. Santa Clara, CA. April 9 th 2004.
Test status report Test status report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis(
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Corrective Action Programs. 2 HSEEP Homeland Security Exercise and Evaluation Program Provides a common exercise policy and program guidance that constitutes.
1 Home Care Support Outcome Based Specification Workshop 26 th November 2009.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
© 2005 Nova Scotia Government All rights reserved. Quotas & Reporting.
Root Cause Analysis Systems Safety Technique used to identify the “Root Causes” of accidents A root cause is the most basic cause for a accident that can.
© BLR ® —Business & Legal Resources 1501 Accident Investigation.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Human Performance Enhancement System Park Young Ho Dept. of Nuclear & Quantum Engineering Korea Advanced Institute of Science and Technology December 23.
Root Cause Analysis Roger Brauninger
Chapter 11 Project Management.
Project Quality Management
Module 1 Configuration Status Accounting (CSA)
IAEA E-learning Program
11 viii. Develop capacity for signal detection and causality assessment Multi-partner training package on active TB drug safety monitoring and management.
OPS/571 Operations Management
Director, Quality and Accreditation
Root Cause Analysis for Effective Incident Investigation
Movement Control Processes Overview
Root Cause Analysis: Why? Why? Why?
Project Management Chapter 11.
MODULE 7 Definitions Module 7 page 1.
Radiopharmaceutical Production
Presentation transcript:

Root Cause Analysis Workshop Pima Medical Institute, Albuquerque, New Mexico Friday; May 18, 2007; 8:30 am

Agenda Welcome Introductions and Participant’s Goals How root cause analysis can be used Group Work Student Retention Student Placement Group Report Brief workshop assessment

Welcome Goal of workshop Purpose of workshop Process of workshop

Introductions Tell me about yourself Role of the facilitator, Linda Hawkins

How Root Cause Analysis Is Used & Example Can be used across the board in many different areas Takes time, effort, and should be have a cost benefit, but the overall goal is to take an occurrence, find out what happened and make sure it never happens again. Example: Joe is absent again and was late for 3 classes before mid-terms. When he is in class, he participates in the activities, takes good notes, turns in his homework and adheres to the dress code. He had a 78 average going into the mid-term but last week he took the mid- term exam and did poorly. He is at risk of failure.

Overview Discussion What is Root Cause Analysis? A tool designed to help identify not only what and how an event occurred, but also why it happened. Understanding why an event occurred is key to developing effective recommendations Answering the why question helps to identify root causes to prevent recurrences

Overview Discussion Definition Root causes are specific underlying causes More specific the better

Overview Discussion Definition Root causes are those that can reasonably be identified Must be cost beneficial

Overview Discussion Definition Root causes are those management has control to fix Know exactly why a failure occurred

Overview Discussion Definition Root causes are those for which effective recommendations for preventing recurrences can be generated Should directly address the identified root causes

Overview Discussion Four Major Steps: Data Collection Causal factor charting Root cause identification Recommendation generation and implementation

Overview Discussion Data Collection Goal of the data collection is: Probe the data to determine what happened during the occurrence Describe how it happened Understand why it happened

Overview Discussion Casual Factor Chart Sequence diagram that describes events Shape convention: What happened (the occurrence)? Logic questions? Causal factors: Start Causal Factor Chart with beginning data collection. It should drive the data collection process. When the occurrence is charted, start identifying the major contributors with logic questions. What are the causal factors?

Overview Discussion Casual Factor Chart Joe is absent Why is Joe absent ? Joe missed the bus Why did Joe miss the bus? Joe didn’t have right change Joe was late for the bus Why was Joe late for the bus? Joe didn’t have a bus schedule Joe worked overtime Joe works during banking hours & couldn’t get change Why didn’t Joe have change? Joe leaves for work then class CFCF CFCF

Overview Discussion Root Cause Identification Shape convention: Primary issue: Problem category: Root cause category: Near root cause: Root cause: Develop Root Cause Map Purpose is to identifying the underlying reason or reasons for each causal factor

Overview Discussion Root Cause Identification Start here w/each CF Equipment difficulty Equipment availability problem? Admin/Mgt Availability Problem? Student Resource Problem? Procedures Issue? Change machine Bus pass dispenser Problem ID Control Problem reporting Problem analysis Audits Corrective Action Corrective actions not yet implemented  Design Input  Design Output No training  Decision not to train  Training requirements not identified Training records system  Training records incorrect  Training records not up to date Training  Job/task analysis  Program design/objectives  Lesson content  Training resources Not used  Not available/inconvenient  Procedure difficult to use  Use not required but should be  No procedure or task Misleading/confusing  Format confusing  More than 1 action per step  Inadequate checklist  Difficult to identify

Overview Discussion Root Cause Summary Table Recommendation Generation and Implementation Goal: Achievable recommendations for preventing its reoccurrence Provide Joe a bus route schedule and map Provide Joe a bus pass As required, develop an implementation plan for achievable recommendations

Overview Discussion Root Cause Summary Table Casual FactorPaths Through Root Cause MapRecommendations Description Equipment difficultyContact City of Albuquerque for supply of bus routes & maps Joe didn't have a bus ScheduleEquipment reliability program implementationSet up distribution area No ProgramCommunicate to students about availability Description Joe didn't have the right changeEquipment DifficultyProvide bus passes for students through a dispenser Installation/fabricationProvide bus passes for students paid by a grant program Administrative/management systems Procurement control Purchasing specifications Contractor selection Customer interface/services Customer requirements not identified Customer needs not addressed Implementation

Overview Discussion Presentation of Results Root Cause Summary Tables Purpose 1. Organize the information compiled during data analysis 2. Root Cause identification 3. Recommendation generation Process 1. First column: general description of causal factor w/background information 2. Second column: path or paths through the Root Cause Map associated with the causal factor 3. Third column: presents recommendations to address each of the root causes identified

Group Work Student Retention, Team One Problem description: Student retention at Pima Medical Institute is……. It has caused ……., resulting in….. Student Placement, Team Two Problem description: Student placement at Pima Medical Institute is …… It has caused….., resulting in……

Group Reports Student Retention, Team One Student Placement, Team Two

Workshop Assessment Did the workshop meet your goals? Do you have any recommendations to improve the workshop? Will you be able to take the information you learned from the workshop and use it? In what way?