Alerts are designed to notify the right people on your team of a potential issue with a machine so they can act quickly to address it. They can be configured to trigger based on a defined set of conditions and can send a notification to one or more recipients, assign an owner, add a tag, escalate if not resolved within a specific timeframe, and automatically resolve when runtime returns.
This article walks you through the steps to take to create a new alert.
Who should set up your alerts?
Anyone with an Admin profile in Guidewheel. If you’re not sure which members of your team are Admins, contact [email protected]
Steps
1. In Guidewheel, select 'Issues' in the left menu and choose the 'Alerts' tab
2. On the upper right side, click the 'New Alert' button, which brings up the New Alert window
3. Choose which device you want to set up the alert for
4. Select what condition will trigger the alert
5. Choose when the alert should be triggered and when the alert should end. For example, you might create an alert to trigger 5 minutes after a machine goes down, and to end 1 minute after the machine comes back up.
6. In the right hand column, customize the message that will appear when this alert is triggered. We suggest a clear and concise message, such as “is down” or “is idling”
7. (Optional) Select which tag should be associated with this alert. If you select a tag, it will automatically be applied to the issue every time this alert is triggered. This makes sense for conditions like “late start” and “lunch break” that follow a specific pattern and timing, but not for conditions like “no operator” or “mechanical issue” that do not.
8. (Optional) Choose which team member(s) should be assigned to fix the issue. If you want an owner automatically assigned to the issue every time this alert is triggered, select an “Assignee.” This can make sense for events like a machine becoming overloaded (you want to automatically assign a maintenance person) or a machine running after hours (you want to automatically assign someone to turn it off) but not for issues you’ll assign on a case-by-case basis.
9. Choose how each team member(s) should be notified about the alert and when to escalate
Choose if the team member(s) should received notifications via SMS or email or both
Choose how long after the alert is triggered to notify this person
Choose how often to notify the user(s) if the issue remains unresolved
Choose if additional team members should be notified if the issue remains unresolved
10. (Optional) Select the “Alert Window” tab to select specific days and times that you wish to receive a notification when an alert is triggered or when you want to automatically tag an issue
Use case 1: This can be useful when breaking alerts down according to each shift, so the corresponding supervisor gets the alert when they are on shift
Use case 2: This can be useful to automatically tag recurring daily events, such as a lunch break
11. Once completed, click “Show Preview” to make sure the alert conditions are set up correctly
12. Finally, click “Create Alert” once you’re happy with your selections
These are suggestions for teams to get started, however, given that all roles, teams, and organizations are not the same, you should personalize your reports however you see fit. We recommend you use this information as a starting point.
Learn more about what types of alerts you should set up and how to decide who should receive alerts.
Questions? Email [email protected]