Cyber Blue – Team 234 Continuous Improvement Through

Slides:



Advertisements
Similar presentations
Cyber Blue – Team 234 Continuous Improvement Through Root Cause & Corrective Action “How To Learn From Your Mistakes” Presented by: Matt Fultz and David.
Advertisements

BA 301 Week 4. Homework Assignment – Read pages 40 – 56 (Yuthas) List all your activities for the last week and time spent to the closest hour e.g. Study,
Supercharging DMAIC IT’S TIME TO USE THE POWER OF THE COLLECTIVE MIND.
1.3 ORGANIZATIONAL PLANNING & DECISION MAKING: FISHBONE ANALYSIS HL (HIGHER LEVEL CONTENT)
Quality Control and Improvement
Corporate Leadership Council © 2009 The Corporate Executive Board Company. All Rights Reserved. Managing Poor Performers Identify Poor Performers on Your.
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
Chapter 10 Contemporary Project Management Kloppenborg
Cyber Blue – Team 234 “Care and Feeding of Your Sponsors” Presented by: Matt Fultz and David Hoff At the 2005 Championship Forums Preparation – Chris Fultz.
Improving Quality and Reducing Risks Positive and Powerful Quality Assessment.
Problem Solving.
Insert: Title of Improvement Read Out Date:. 2 Objectives for Today’s Session Share results of improvement effort Demonstrate fact-base, analytical approach.
Project Risk Management Planning Stage
Kaizen Event Flow Kaizen Facilitation Project Management.
Improvement Tools Interactive Lecture Tools Offer Assistance Understand the current state of a process Determine whether the process is in control Find.
FishboneFishbone Six Sigma Foundations Continuous Improvement Training Six Sigma Foundations Continuous Improvement Training Six Sigma Simplicity.
Root Cause Analysis Analyze Kaizen Facilitation. Objectives Learn and be able to apply a fishbone diagram Utilize “Why” analysis technique to uncover.
1 Analyze : Fishbone diagram. 2 Cause-effect diagram - A tool for analyzing process dispersion. It is also referred to as the "Ishikawa diagram," because.
IB Business & Management
Six Sigma Project Coding Performance Improvement Project Global Communication, Inc.
18 March 2004 / Rev. 01 Cyber Blue – Team 234 Perry Meridian High School Indianapolis, IN Design Review Process Documentation This document is intended.
Objectives of the session
LB160 (Professional Communication Skills For Business Studies)
Ms. Kelly 6th Grade Health
Green Belt Project Storyboard Template See Green Belt Storyboard Checklist for required contents Visit GoLeanSixSigma.com for more Lean Six Sigma Resources.
OPS 571 help / ops571helpdotcom
Service Management World Class Operations - Impact Workshop.
Team Skill 1 - Analyzing the Problem
Lean Six Sigma DMAIC Improvement Story
Facilitation Tool: Team Agreement
Unvieling Jet Express: What it offers the GP Community
Participant and Leader Training
Peer Review and Testing
FORGE AHEAD Program Transformation of Indigenous Primary Healthcare Delivery : Community-driven Innovations and Strategic Scale-up Toolkits Module.
Thinking with Technology Course Module 9
Bar Graphs & Histograms
PROBLEM SOLVING MODULE
Lunch Order Cycle Time Project Storyboard Bahama Bistro Example
Prepared by nsreen alkhatib MSN
BUSINESS AND MANAGEMENT
Balanced Scorecard Designer
Lean Six Sigma DMAIC Improvement Story
PDCA Problem Solving Guide
Lean Six Sigma DMAIC Improvement Story
Internet Protocol Version4
Hannah Hirschland, LMSW, Managing Director of Analytics & Evaluation
© 2013 American College of Cardiology
Introduction to Projects
Overview What Are Cause & Effect Diagrams?
Fast, free, fun Weebly web sites.
Developing Strong Action Plans
4th Edition Chapter 20 Design Teams.
Enterprise Program Management Office
Fishbone Diagram/ Cause & Effect Diagram
The Educator Development Solution
Dr. Rob Hasker SE 3800 Note 9 Reviews.
Overview What Are Cause & Effect Diagrams?
Note Taking & Study Skills…
1 Hour Training Bubbles Problem Solving Techniques
Building Leadership Capacity Maximizing Performance Case Studies
Implementing the Child Outcomes Summary Process: Challenges, strategies, and benefits July, 2011 Welcome to a presentation on implementation issues.
Overview of Networking
Edgerton School Practices
Cause and Effect Diagrams
CAUSE AND EFFECT DIAGRAM
Implementing the Child Outcomes Summary Process: Challenges, strategies, and benefits July, 2011 Welcome to a presentation on implementation issues.
CAPA, Root Cause Analysis, and Risk Management
Lesson 3.2 Product Planning
COMM 464 class 3 Agenda Marketplace news
Presentation transcript:

Cyber Blue – Team 234 Continuous Improvement Through Root Cause & Corrective Action “How To Learn From Your Mistakes” Presented by: Matt Fultz and David Hoff At the 2005 Championship Forums Preparation – Chris Fultz

Cyber Blue – Team 234 What is Continuous Improvement? Learning from mistakes Finding a better way Avoiding “that always happens” Moving your program to the “next level”

Cyber Blue – Team 234 There are several good processes for Root Cause / Corrective Action Six Sigma – DMAIC Define, Measure, Analyze, Implement, Control 5 Why’s Structured Brainstorming Ishikawa (Fishbone)

Cyber Blue – Team 234 Cyber Blue implemented a Root Cause and Corrective Action process by using the “Ishikawa” or “Fishbone Diagram”. Straight-forward, easy, well suited for groups and brainstorming activities

Cyber Blue – Team 234 Fishbone (how it got its’ name) Category 1 Result Category 4 Category 5

Cyber Blue – Team 234 The Process – six steps 1. Agree on the ‘result’ to be analyzed 2. Identify the bones of the fish 3. Brainstorm ideas and place them 4. Review and select common themes 5. Identify actions and action plans 6. Prioritize and Complete the actions

Cyber Blue – Team 234 Sample Process – Fictional Team Good Robot, Good Team Did not compete as well as they wanted Want to identify what they can correct for the next season

Cyber Blue – Team 234 1. Agree the result to be analyzed Category 1 Did not compete as well as we wanted Category 4 Category 5

Cyber Blue – Team 234 2. Identify Main Bones Material Measurement Machine Did not compete as well as we wanted People Methods

Cyber Blue – Team 234 3. Brainstorm Ideas - Classify Material Measurement Machine Did not compete as well as we wanted Wiring messy Heavy material Weight Tracking Loose connectors Availability Broke P-fitting Scheduling Communication No practice Time No module testing Rely on a few Wiring layout difficult to troubleshoot People Methods

Cyber Blue – Team 234 4. Review and Group items into common themes Communication People Controls

Cyber Blue – Team 234 5. Identify actions and action plans Actions should be Specific Measurable Assigned & Accepted A specific person or small group Tracked

Cyber Blue – Team 234 5. Identify actions and action plans Weight Tracking Make better use of Inventor (Bob) Find weight of ‘canned’ parts (Mike) Get an accurate small scale (Kelly) Force a weight margin - ie 10 lbs (Mr. Jones) Heavy Material Find lighter, stronger materials (Mike, Jan) Weld frame instead of bolts (Mr. Jones) Requires a welder (tool) and welder (person)

Cyber Blue – Team 234 5. Identify actions and action plans Availability (of materials) Buy standard parts and stock them (Kyle) Create a nightly shopping list (Kyle) Communication Force nightly discussion session (Captain) Create “to-do” lists (Sub-Team Leads) Use / read web-site for notices (ALL)

Cyber Blue – Team 234 5. Identify actions and action plans No Practice Time Set a build schedule and stick to it (Mr. Jones) Build another chassis for controls (Fab Team) Work weekends - maintain schedule (ALL) Rely on a Few Assign work to more people (Sub-Team Leads) Assign leader roles (Mr. Jones) Develop other students (Sub-Team Leads)

Cyber Blue – Team 234 5. Identify actions and action plans Wiring layout difficult / messy / difficult to troubleshoot More time to wire (schedule) (Mary) Make a schematic (Luke) Number / Label wires on each end (Luke) Loose Connectors Buy good crimpers (Kyle) Train a crimper person (Mr. Jones) Buy high quality connectors (Kyle & Mary)

Cyber Blue – Team 234 5. Identify actions and action plans Broken Pneumatic Fitting Add protective cover to all fittings (Mike) Route fittings in protected areas (Mike) Don’t use pneumatics (Whole Team Decision) Scheduling (Team Leaders) Create a schedule and stick to it Force late work / evenings to maintain schedule Drop work if needed to keep schedule

Cyber Blue – Team 234 5. Identify actions and action plans No Module Testing Create mini versions (Sub-Team Leads) Build modules and test them (Sub-Team Leads) Use old robot for new ideas (Sub-Team Leads)

Cyber Blue – Team 234 6. Complete the Actions! Just making the list does no good Create a large action board Track progress Follow-up to see if the actions made a difference Then start all over for next year!

Cyber Blue – Team 234 Summary FIRST teams can improve year to year by utilizing formal continuous improvement processes Many businesses use the same tools and there is a wealth of information available in libraries and on the internet. Your sponsor companies or local colleges / universities might offer a facilitator!

Cyber Blue – Team 234 Questions?