Problem-Solving optimizes the time required to drill down to the cause of a problem and provides instruction for problem-solving within manufacturing using RCA.
Root Cause Analysis (RCA)
RCA is a systematic approval used to identify the fundamental cause of a problem or failure. The goal is to understand why an issue occurred, rather than just addressing its symptoms. By pinpointing the root cause, organizations can implement effective solutions to prevent recurrence:
- Define the Problem: Clearly articulate what the issue is and its impact.
- Collect Data: Gather information related to the problem, including when and where it occurred, and any relevant conditions.
- Identify Possible Causes: Brainstorm all potential causes of the problem. This can involve techniques like the "5 Whys," fishbone diagrams (Ishikawa), or other analytical methods.
- Analyze Causes: Evaluate the potential causes to determine which one(s) are most likely responsible problem.
- Implement Solutions: Develop and implement corrective actions to address the root cause.
- Monitor Results: After implementing solutions, monitor the situation to ensure that the problem does not recur.
- Document and Share: Record the findings and the process to help others learn from the experience.
Benefits of RCA:
- Reduces the likelihood of recurring issues
- Improves processes and systems
- Enhances overall efficiency and effectiveness
- Promotes a culture of continuous improvement.
Notifications, Settings, and Routing Rules
Email Notification Settings:
These notifications use a True, False dropdown to enable emails for significant events.
- Send a notification to the new owner of a Significant Event when routing rules are used. (True or False)
- Notify the owner if a Significant Event is canceled (True or False)
- Notify the owner if a Significant Event is completed (True or False)
Sigdowntime Settings
These are used to track and report on events that exceed significant downtime criteria. They are used in the report for significant occurrence (Breakdown) Pareto and also to set up the launch of a new Significant Event in the problem-solving module when a dispatch crosses the threshold of the set time.
You can choose to Launch A Sig Event when a Dispatch duration crosses the significant downtime threshold for a specific dispatch type.
Note: the Significant Event will not be created until after that originating dispatch is Completed. This is by design to ensure that the work on the previous Dispatch is completed before launching that event.
Problem-Solving Security Settings:
- Manager: Can manage settings and categories.
- Administrator: Can manage settings and categories as well as permissions.
Initial Problem-Solving Routing Rules
Significant Events can be routed to the correct person for research via the routing rules below. When a new significant event comes in, each rule below is evaluated in order until the significant event matches a rule and then the significant event is routed to the user identified by the matching rule.
NOTE: The user must have a valid email address to be routed to or notified.
Problem Solving Categories
You will see under the Problem-Solving menu the options of different categories. If you plan to track any of the Root Cause, Significant Details or Cost Saving Details within your sig event, you can create these categories to help track where the issues stem from.
Examples:
Root Cause Categories: Man, Machine, Material, Zparts, Resource, etc.
Significant Detail Categories: Machine, Man, Material, Method, etc.
Cost Saving Categories: Downtime, Labor Savings, Material Savings, Spare Parts Savings, etc.