Operating Excellence is built on Corrective & Preventive ActionsAtanu Dhar
You see an issue and you simply set it right, but do you make the effort to find out what is the "corrective" action behind it, so that it never re-occurs?
And, do you take another extra step to come up with a "preventive" action - so that there is no other manner that issue comes up?
Invented in the 1930’s by Toyota Founder Kiichiro Toyoda’s father Sakichi and made popular in the 1970s by the Toyota Production System, the 5 Whys strategy involves looking at any problem and asking: “Why?” and “What caused this problem?”
8D Problem Solving WorksheetGroup NumberGroup Member Nam.docxransayo
8D: Problem Solving Worksheet
Group Number:
Group Member Names:
Date:
8-D is a quality management tool and is a vehicle for a team to articulate thoughts and provides scientific determination to details of problems and provide solutions. Organizations can benefit from the 8-D approach by applying it to all areas in the company. The 8-D provides excellent guidelines allowing us to get to the root of a problem and ways to check that the solution actually works. Rather than healing the symptom, the illness is cured, thus, the same problem is unlikely to recur.
Step
0
1
2
3
4
5
6
7
8
Action
The Planning Stage
Establishing the Team
Problem Definition / Statement & Description
Developing Interim Containment Action
Identifying & Verifying Root Cause
Identifying Permanent Corrective Actions (PCA)
Implementing & Validating PCA
Preventing Recurrence
Recognizing Team Efforts
0
The Planning Stage:
The 8-D method of problem solving is appropriate in "cause unknown" situations and is not the right tool if concerns center solely on decision-making or problem prevention. 8-D is especially useful as it results in not just a problem-solving process, but also a standard and a reporting format. Does this problem warrant/require an 8D? If so comment why and proceed.
Is an Emergency Response Action Needed?
(If needed document actions in Action Item Table)
1
Establishing the Team: (Your group is the team)
Establish a small group of people with the process/ product
knowledge, allocated time, authority and skill in the required technical disciplines to solve the problem and implement corrective actions.
Team Goals:
Team Objectives:
First and Last Name (put an asterisk * after the name of the team leader)
Current Job Position
Skills (related to the problem)Years of Hospitality Work Experience
2A
Problem Definition
Provides the starting point for solving the problem. Need to have “correct” problem description to identify causes. Need to use terms that are understood by all.
Sketch / Photo of Problem
Product(s):
Customer(s):
List all of the data and documents that might help you to define the problem more exactly?
Action Plan to collect additional information:
Prepare Process Flow Diagram for problem
use a separate sheet if needed
2B
IS
IS NOT
Who
Who is affected by the problem?
Who first observed the problem?
To whom was the problem reported?
Who is not affected by the problem?
Who did not find the problem?
What
What type of problem is it?
What has the problem (food, service, etc)?
What is happening with the process & with containment?
Do we have physical evidence of the problem?
What does not have the problem?
What could be happening but is not?
What could be the problem but is not?
Why
Why is this a problem (degraded performance)?
Is the process stable?
Why is it not a problem?
Where
Where was the problem observed?
Where does the problem occur?
Where could the problem be located but is not?
Where else could .
Operating Excellence is built on Corrective & Preventive ActionsAtanu Dhar
You see an issue and you simply set it right, but do you make the effort to find out what is the "corrective" action behind it, so that it never re-occurs?
And, do you take another extra step to come up with a "preventive" action - so that there is no other manner that issue comes up?
Invented in the 1930’s by Toyota Founder Kiichiro Toyoda’s father Sakichi and made popular in the 1970s by the Toyota Production System, the 5 Whys strategy involves looking at any problem and asking: “Why?” and “What caused this problem?”
8D Problem Solving WorksheetGroup NumberGroup Member Nam.docxransayo
8D: Problem Solving Worksheet
Group Number:
Group Member Names:
Date:
8-D is a quality management tool and is a vehicle for a team to articulate thoughts and provides scientific determination to details of problems and provide solutions. Organizations can benefit from the 8-D approach by applying it to all areas in the company. The 8-D provides excellent guidelines allowing us to get to the root of a problem and ways to check that the solution actually works. Rather than healing the symptom, the illness is cured, thus, the same problem is unlikely to recur.
Step
0
1
2
3
4
5
6
7
8
Action
The Planning Stage
Establishing the Team
Problem Definition / Statement & Description
Developing Interim Containment Action
Identifying & Verifying Root Cause
Identifying Permanent Corrective Actions (PCA)
Implementing & Validating PCA
Preventing Recurrence
Recognizing Team Efforts
0
The Planning Stage:
The 8-D method of problem solving is appropriate in "cause unknown" situations and is not the right tool if concerns center solely on decision-making or problem prevention. 8-D is especially useful as it results in not just a problem-solving process, but also a standard and a reporting format. Does this problem warrant/require an 8D? If so comment why and proceed.
Is an Emergency Response Action Needed?
(If needed document actions in Action Item Table)
1
Establishing the Team: (Your group is the team)
Establish a small group of people with the process/ product
knowledge, allocated time, authority and skill in the required technical disciplines to solve the problem and implement corrective actions.
Team Goals:
Team Objectives:
First and Last Name (put an asterisk * after the name of the team leader)
Current Job Position
Skills (related to the problem)Years of Hospitality Work Experience
2A
Problem Definition
Provides the starting point for solving the problem. Need to have “correct” problem description to identify causes. Need to use terms that are understood by all.
Sketch / Photo of Problem
Product(s):
Customer(s):
List all of the data and documents that might help you to define the problem more exactly?
Action Plan to collect additional information:
Prepare Process Flow Diagram for problem
use a separate sheet if needed
2B
IS
IS NOT
Who
Who is affected by the problem?
Who first observed the problem?
To whom was the problem reported?
Who is not affected by the problem?
Who did not find the problem?
What
What type of problem is it?
What has the problem (food, service, etc)?
What is happening with the process & with containment?
Do we have physical evidence of the problem?
What does not have the problem?
What could be happening but is not?
What could be the problem but is not?
Why
Why is this a problem (degraded performance)?
Is the process stable?
Why is it not a problem?
Where
Where was the problem observed?
Where does the problem occur?
Where could the problem be located but is not?
Where else could .
Managerial and Technical skills of supervisorsNabila Naik
Supervisors work closely with employees of any given business. While some supervisors act as managers and tell people how to do their work, others work as part of a team and supervise with respect, loyalty and a positive tone of voice. It is often the small characteristics that define a good and enjoyable employee supervisor. Rather than telling people how to work, a good supervisor serves as an inspiration and provides guidance for hardworking employees.
Root Cause Analysis - Tools, Tips and Tricks to Get to the Bottom of Root CauseCraig Thornton
This webinar discusses and investigates how to conduct root cause analysis. Root cause analysis is something that companies really struggle with. There will be plenty of practical advice in the webinar to help with you understand the concepts and the tools.
If you would like to watch the recording of this webinar then copy and paste the below link into your web browser:
http://www.mangolive.com/blog-mango/root-cause-analysis-tools-webinar
The RCCA PPT is an excellent training tool to implement into your functional group or business.
It basically forces you to peel the onion on a failure as far back until you’ve reached the root cause whereas in some cases it could be several.
It incorporates the 5 whys and the problem solving technique.
8D Training Material From VDiversify.com | 8D Training Material PDF Free Down...VDiversify
Note: Whoever is using this Training Material on their Website shall Link back to www.vdiversify.com as the Original Author...
The 8D (Eight Disciplines) approach is a robust and systematic problem-solving process or methodology, that is widely adopted in the manufacturing, process and other industries.
This 8D training material is completely free and can be used by any organization, professionals, engineers, trainers or teachers all over the world for teaching its employees or students.
Fixing the Problems in Your Operations Problem-Solving MethodsSafetyChain Software
Learn why manufacturers struggle to quickly and clearly define production issues, determine the complexity of a problem, and why there may be confusion over problem-solving methodologies versus problem-solving tools.
Presented by: David Hicks and Tim Nickerson of TBM Consulting
This is the final session in a four part series on Operational Management Systems.
Watch the full presentation: https://info.safetychain.com/fix-problem-solving
Managerial and Technical skills of supervisorsNabila Naik
Supervisors work closely with employees of any given business. While some supervisors act as managers and tell people how to do their work, others work as part of a team and supervise with respect, loyalty and a positive tone of voice. It is often the small characteristics that define a good and enjoyable employee supervisor. Rather than telling people how to work, a good supervisor serves as an inspiration and provides guidance for hardworking employees.
Root Cause Analysis - Tools, Tips and Tricks to Get to the Bottom of Root CauseCraig Thornton
This webinar discusses and investigates how to conduct root cause analysis. Root cause analysis is something that companies really struggle with. There will be plenty of practical advice in the webinar to help with you understand the concepts and the tools.
If you would like to watch the recording of this webinar then copy and paste the below link into your web browser:
http://www.mangolive.com/blog-mango/root-cause-analysis-tools-webinar
The RCCA PPT is an excellent training tool to implement into your functional group or business.
It basically forces you to peel the onion on a failure as far back until you’ve reached the root cause whereas in some cases it could be several.
It incorporates the 5 whys and the problem solving technique.
8D Training Material From VDiversify.com | 8D Training Material PDF Free Down...VDiversify
Note: Whoever is using this Training Material on their Website shall Link back to www.vdiversify.com as the Original Author...
The 8D (Eight Disciplines) approach is a robust and systematic problem-solving process or methodology, that is widely adopted in the manufacturing, process and other industries.
This 8D training material is completely free and can be used by any organization, professionals, engineers, trainers or teachers all over the world for teaching its employees or students.
Fixing the Problems in Your Operations Problem-Solving MethodsSafetyChain Software
Learn why manufacturers struggle to quickly and clearly define production issues, determine the complexity of a problem, and why there may be confusion over problem-solving methodologies versus problem-solving tools.
Presented by: David Hicks and Tim Nickerson of TBM Consulting
This is the final session in a four part series on Operational Management Systems.
Watch the full presentation: https://info.safetychain.com/fix-problem-solving
Adjusting primitives for graph : SHORT REPORT / NOTESSubhajit Sahu
Graph algorithms, like PageRank Compressed Sparse Row (CSR) is an adjacency-list based graph representation that is
Multiply with different modes (map)
1. Performance of sequential execution based vs OpenMP based vector multiply.
2. Comparing various launch configs for CUDA based vector multiply.
Sum with different storage types (reduce)
1. Performance of vector element sum using float vs bfloat16 as the storage type.
Sum with different modes (reduce)
1. Performance of sequential execution based vs OpenMP based vector element sum.
2. Performance of memcpy vs in-place based CUDA based vector element sum.
3. Comparing various launch configs for CUDA based vector element sum (memcpy).
4. Comparing various launch configs for CUDA based vector element sum (in-place).
Sum with in-place strategies of CUDA mode (reduce)
1. Comparing various launch configs for CUDA based vector element sum (in-place).
Techniques to optimize the pagerank algorithm usually fall in two categories. One is to try reducing the work per iteration, and the other is to try reducing the number of iterations. These goals are often at odds with one another. Skipping computation on vertices which have already converged has the potential to save iteration time. Skipping in-identical vertices, with the same in-links, helps reduce duplicate computations and thus could help reduce iteration time. Road networks often have chains which can be short-circuited before pagerank computation to improve performance. Final ranks of chain nodes can be easily calculated. This could reduce both the iteration time, and the number of iterations. If a graph has no dangling nodes, pagerank of each strongly connected component can be computed in topological order. This could help reduce the iteration time, no. of iterations, and also enable multi-iteration concurrency in pagerank computation. The combination of all of the above methods is the STICD algorithm. [sticd] For dynamic graphs, unchanged components whose ranks are unaffected can be skipped altogether.
As Europe's leading economic powerhouse and the fourth-largest hashtag#economy globally, Germany stands at the forefront of innovation and industrial might. Renowned for its precision engineering and high-tech sectors, Germany's economic structure is heavily supported by a robust service industry, accounting for approximately 68% of its GDP. This economic clout and strategic geopolitical stance position Germany as a focal point in the global cyber threat landscape.
In the face of escalating global tensions, particularly those emanating from geopolitical disputes with nations like hashtag#Russia and hashtag#China, hashtag#Germany has witnessed a significant uptick in targeted cyber operations. Our analysis indicates a marked increase in hashtag#cyberattack sophistication aimed at critical infrastructure and key industrial sectors. These attacks range from ransomware campaigns to hashtag#AdvancedPersistentThreats (hashtag#APTs), threatening national security and business integrity.
🔑 Key findings include:
🔍 Increased frequency and complexity of cyber threats.
🔍 Escalation of state-sponsored and criminally motivated cyber operations.
🔍 Active dark web exchanges of malicious tools and tactics.
Our comprehensive report delves into these challenges, using a blend of open-source and proprietary data collection techniques. By monitoring activity on critical networks and analyzing attack patterns, our team provides a detailed overview of the threats facing German entities.
This report aims to equip stakeholders across public and private sectors with the knowledge to enhance their defensive strategies, reduce exposure to cyber risks, and reinforce Germany's resilience against cyber threats.
Show drafts
volume_up
Empowering the Data Analytics Ecosystem: A Laser Focus on Value
The data analytics ecosystem thrives when every component functions at its peak, unlocking the true potential of data. Here's a laser focus on key areas for an empowered ecosystem:
1. Democratize Access, Not Data:
Granular Access Controls: Provide users with self-service tools tailored to their specific needs, preventing data overload and misuse.
Data Catalogs: Implement robust data catalogs for easy discovery and understanding of available data sources.
2. Foster Collaboration with Clear Roles:
Data Mesh Architecture: Break down data silos by creating a distributed data ownership model with clear ownership and responsibilities.
Collaborative Workspaces: Utilize interactive platforms where data scientists, analysts, and domain experts can work seamlessly together.
3. Leverage Advanced Analytics Strategically:
AI-powered Automation: Automate repetitive tasks like data cleaning and feature engineering, freeing up data talent for higher-level analysis.
Right-Tool Selection: Strategically choose the most effective advanced analytics techniques (e.g., AI, ML) based on specific business problems.
4. Prioritize Data Quality with Automation:
Automated Data Validation: Implement automated data quality checks to identify and rectify errors at the source, minimizing downstream issues.
Data Lineage Tracking: Track the flow of data throughout the ecosystem, ensuring transparency and facilitating root cause analysis for errors.
5. Cultivate a Data-Driven Mindset:
Metrics-Driven Performance Management: Align KPIs and performance metrics with data-driven insights to ensure actionable decision making.
Data Storytelling Workshops: Equip stakeholders with the skills to translate complex data findings into compelling narratives that drive action.
Benefits of a Precise Ecosystem:
Sharpened Focus: Precise access and clear roles ensure everyone works with the most relevant data, maximizing efficiency.
Actionable Insights: Strategic analytics and automated quality checks lead to more reliable and actionable data insights.
Continuous Improvement: Data-driven performance management fosters a culture of learning and continuous improvement.
Sustainable Growth: Empowered by data, organizations can make informed decisions to drive sustainable growth and innovation.
By focusing on these precise actions, organizations can create an empowered data analytics ecosystem that delivers real value by driving data-driven decisions and maximizing the return on their data investment.
Explore our comprehensive data analysis project presentation on predicting product ad campaign performance. Learn how data-driven insights can optimize your marketing strategies and enhance campaign effectiveness. Perfect for professionals and students looking to understand the power of data analysis in advertising. for more details visit: https://bostoninstituteofanalytics.org/data-science-and-artificial-intelligence/
2. CLARIOS
Confidential and Propietary
Eight Disciplines of Problem Solving (8D)
8D method is a team based problem solving approach/process of 8 critical steps with a
focus on actions to contain, correct and prevent recurrence of the problem
Establish the team from different departments and choose a team leader
1D
ESTABILISHING
THE TEAM
Clearly describe the problem in order to understand what went wrong
2D PROBLEM DESCRIPTION
Stop the process, put a temporary fix in place (e.g., introducing 100% inspection)
Brainstorm on finding the root cause(s) of the problem, why was is not detected
3D CONTAINMENT ACTION
Choose and verify the permanent action plan
4D ROOT CAUSE
Summarize the learnings and close the case
5D CORRECTIVE ACTION
6D
VALIDATE CORRECTIVE
ACTIONS
7D PREVENT RECURRENCE
8D
CONCLUDE AND
CONGRATULATE TEAM
Validate whether corrective action(s) are efficient, problem is monitored
Improvements in systems and processes would prevent problem from recurring
3. CLARIOS
Confidential and Propietary
1D – Establishing the team
First step is establish the team consisting of persons, that will be responsible for realizing particular steps of 8D
Quantity of team and their making-up depends of the complexity of the problem and taken decision
The team should fulfill the following steps :
• Have a good knowledge of the product and processes
• Multidisciplinary – people from different departments
• Have adequate capability to introduce proper solution of the problem
• The team should have a Leader, who supervises and closes 8D
4. CLARIOS
Confidential and Propietary
2D – Problem description
During this step, you need to describe the problem in the most accurate way
It is recommended that the description of the problem includes :
• Proper description of the problem, not restricted to laconic statements
• Place problem detected.
• Scale of problem, eg. % of reject or qty of pcs / range deviations beyond the tolerance
• etc.
It’s very important that the problem is „measurable”,
How many %, ppm or in any another unit of measure
Later, this allows to properly assess whether corrective actions are implemented efficiently or not
Problem Definition => clear and accurate, problem defined as the customer sees it,
do not add cause(s) into the problem definition
5. CLARIOS
Confidential and Propietary
3D – Containment action (emergency action)
This is the step where the right containment action is taken to prevent escalation of the problem
(further making defects) or at the worst delivering not conforming products to the customer
Example of action(s) :
• Stoppage of production/shipment
• Additional visual control
• Informing the customer about the problem (for verification of the goods at the customer)
• Segregation goods on OK/NOK
• Informing operators about the problem
Check if similar products or processes, there is a similar risk
(if yes - should be implemented within the containment action)
6. CLARIOS
Confidential and Propietary
4D – Root Cause
To really eliminate the problem, the real cause(s) of the problem needs to be identified.
This is not a simple step, therefore it is important to work in a team and to look at the
problem from different sides
䕮 Several tools can be used
The production process often throws up the cause of the problem on "operator error".
This is a mistake, the reason(s) are much deeper :
• Lack of properly tools
• Lack of training and/or training are not efficient
• Overtime work in a hurry (effect of wrong decisions of the management)
• The production process is not suitable for quality requirements
7. CLARIOS
Confidential and Propietary
5D – Corrective action
The Team determines which action(s) should be introduced in a mid term period of time
to ensure that the process/product is under control
Examples :
• Introducing additional control in the process
• Introducing additional other process (e.g., component reworked, test corrected)
• Rework defective units found inside
• Rework units returned from customer
• Inform the supplier about defective part delivered and their exchange, etc.
8. CLARIOS
Confidential and Propietary
6D – Validate corrective action
Verify that the corrective action(s) taken are efficient.
It should be based on "real data" from the process.
Examples :
• Less reject % (ppm) in process
• Test/control results show improvement
• Engineering’s measurements (dimension, units appearance ) are correct,
according to tolerance, specification
• Supplier deliver goods of better quality
9. CLARIOS
Confidential and Propietary
7D – Prevent recurrence
Next step is to determine what action(s) should be taken to prevent recurrence of the problem
Examples :
• Modify or make proper tooling
• Change the process parameters in order to prevent defects
• Change process/tools by supplier which make the parts
• Change procedure(s) (organization change)
• Change documentation (FMEA, PCP, Work Instruction …) /specification (if it was incorrect)
10. CLARIOS
Confidential and Propietary
8D – Verify and congratulate Team
The Leader of the Team will verify the 8D before closing the case
Draw conclusions as the Team worked, what the individual members have learned and what
are the conclusions for the future - what other process can be improved, what tools, etc…
Lessons learned should be documented, and at the end of the process, congratulate the team.
11. CLARIOS
Confidential and Propietary
5 Why
5-Why is a simple approach for exploring root causes, it is applicable when you are facing problems
where responses can be given through a discussion rather than analysis and/or experimentation.
Analysis of 5-Why must include 2 aspects :
1/ Why did the problem exists ?
We are wondering about root cause(s) of the problem and why the defect was produced ?
2/ Why was it not detected ?
We have to think why our current system/method of control/monitoring process did not detect
the problem when it has occurred ?
12. CLARIOS
Confidential and Propietary
How to use 5-Why?
1. Collect all possible information
What exactly happened ? When ? What is the scale of the problem ? What is the risk for customer ?
2. Create the Team
Find the right people that could help to determine the cause
3. Clearly describe the problem
4. We begin to question
Method 5-Why is all about to ask 5 times questions Why ?
Why?
Why?
Why?
Why?
Why?
Problem Root
cause
May be
more than 5 Whys
or
less than 5 Whys
13. CLARIOS
Confidential and Propietary
5-Why – Drill Deep Analysis
1/ Specific - Problem statement
Why did we have this "Specific
Problem" ?
Why did we have the problem/the
specific non-conformance ?
2/ Detection
Why was the problem not detected
(internally) ?
Why did the problem reach the
customer ?
3/ Systemic
What system(s) failed ?
Why did the system allow it to occur ?
14. CLARIOS
Confidential and Propietary
Example of 5-Why
PROBLEM : Missing hole "A"
Question 1 : Why is hole "A" missing?
Answer : Skipped operations - a detail was not treated (drilling)
Question 2 : Why did the operator skipp operations and did not give detail treatment ?
Answer : Details before and after drilling are next to each other
Question 3 : Why are the details before and after drilling next to each other?
Answer : There is no clearly defined place on the machine, the parts before and after drilling the hole
Question 4 : Why is not there a clear space on the machine for parts before and after drilling the hole
Answer : Process of production area has not established rules for identification of parts before and after drilling
Question 5 : Why did this area of production technologist not establish rules for identification of parts before and
after drilling
Answer : There are no clear rules (guidelines) for the determination of products before and after the operation
in the entire factory machining
15. CLARIOS
Confidential and Propietary
5-Why
Advantages of 5-Why
• This method is simple to use and easy to apply to any organization
• Does not require knowledge of statistics
• You can easily and quickly make this method (simple and short training)
Summary : The method of 5-Why is just about to ask 5 questions “Why", but not all the time.
Sometimes when you are asking the fifth question, can lead to absurd answers, so sometimes it is better
to stop for e.g., on the 4th question. Of course, it may happen that you will ask 6-7 questions to get to the
bottom of the case. Everything depends on the common sense approach to the subject.
Notice than, in most of the cases, "operator error" (human error), the real cause of the problem usually is
somewhere in the system, organization, or in the method of operation.
16. CLARIOS
Confidential and Propietary
Ishikawa (fishbone diagram)
The left side of the diagram is where the causes are listed. The causes are broken out
into major cause categories. The causes you identify will be placed in the appropriate
cause categories as you build the diagram.
The right side of the diagram lists the effect. The effect is written as the problem
statement for which you are trying to identify the causes.
17. CLARIOS
Confidential and Propietary
Ishikawa (fishbone diagram)
1. Draw Problem Statement - Define problem correctly, that everyone agrees on the problem statement.
Once your problem statement is ready, write it in the box on the right hand side of the diagram
2. Draw Major Cause Categories.
Draw the major cause categories on the left hand
side and connect them to the "backbone"
of the fishbone chart
In a manufacturing environment,
the traditional categories are 6Ms
• Machines
• Methods
• Measurement Systems
• Mother Nature
• Materials
• Manpower
Machinery Methods Measurement system
Mother Nature Materials Manpower
18. CLARIOS
Confidential and Propietary
Ishikawa (fishbone diagram)
3. Brainstorm Causes
Brainstorming the causes of the problem is where most of the effort in creating your Ishikawa diagram
takes place
4. Categorize Causes
Once your list of causes has been generated, you can start to place them in the appropriate category
on the diagram
Machinery Methods Measurement system
Mother Nature Materials Manpower
19. CLARIOS
Confidential and Propietary
Ishikawa (fishbone diagram)
5. Determine Deeper Causes
Each cause on the chart is then analyzed further to determine if there is a more fundamental cause for
that aspect. This can be done by asking the question, "Why does it happen ?„ Use your judgment
to decide when to stop.
20. CLARIOS
Confidential and Propietary
Ishikawa (fishbone diagram)
6. Identify Root Causes
Identifying the root causes of the problem can be done in several ways ...
Look for causes that appear repeatedly
Select using group consensus methods
Select based on frequency of occurrence
In Conclusion Fishbone Diagram (FD)
FD is an excellent way to explore and visually depict the causes of a problem. The FD enables
to determine the root causes of a problem. This will help to be more effective by focusing the
actions on the true causes of a problem and not on its symptoms.