Addressing breakdowns quickly and getting machines up and running again is one of the keys to reducing overall downtime. Guidewheel helps you do this by alerting the right people as soon as a breakdown occurs, and notifying others if the breakdown persists. It also allows you to capture granular data about the root cause of the breakdown so you can take action, like performing additional maintenance or revising planned maintenance schedules to prevent the issue from occuring in the future.
Key Guidewheel features:
Alerts | Tagging | Pareto Analysis |
Breakdown Issue in Guidewheel
How to use them:
Alert the right people at the right time
Configure Alerts to notify the right people on your Maintenance team as soon as an issue occurs.
Define an escalation path to engage others on the team and/or notify management of any issues that persist beyond a defined time period.
Your team can capture steps taken to fix the issue by responding to the Alert SMS (responses to Alerts are saved as comments on the Issue) or adding comments directly to the Issue in Guidewheel.
Use Tags to capture breakdown root causes
If you already have downtime codes in use on your factory floor, you can configure Guidewheel with those
If you are creating new downtime codes:
When deciding what Tags to create, consider what information you need to understand root causes of breakdowns so you can prevent them in the future.
We recommend creating a “Mechanical” tag so you can easily group all mechanical/breakdown issues in Guidewheel.
We also recommend creating a set of more granular tags for specific mechanical issues you see regularly. For example, a blade change or bearing replacement.
It’s best to start with a small set of Tags and add additional Tags as needed.
Review Pareto Analysis in shift handoff meetings
Review Pareto of downtime events due to breakdowns in shift handoff meetings. Navigate to Issues tab > Analysis > Pareto.
Identify patterns and make a plan to address them in the upcoming shift.
Track your progress
Review Pareto Analysis by issue and machine over the last day, week and month.
Track progress against downtime reduction goals and adjust plans accordingly.