Overview
Sidekick is a simple HMI designed for operators to quickly tag downtime events. With Sidekick, operators can apply downtime reason codes, add comments, or split issues when multiple causes occur. This guide walks through the three ways operators can tag downtime in Sidekick.
Prerequisites
Access to Sidekick
Alerts configured to automatically generate issues
Pre-configured downtime tags available in your Guidewheel account
Step-by-Step Instructions
1. Tag by Updating an Existing Issue
In Sidekick, hover over the downtime event.
Click Update issue.
Select the appropriate tag for the downtime.
(Optional) Under Actions, type a comment explaining the reason.
(Optional) Use Split issue if multiple causes occurred (e.g., feeder issue followed by a jam).
Click Save.
2. Tag from Recent Issues
Scroll to the Recent Issues section at the bottom third of Sidekick.
Find the ongoing issue you want to tag.
Click the Tag icon.
Scroll through the tag list or type to search.
Select the correct tag and save.
3. Create a New Issue
In Sidekick, click + New Issue (use only if an alert did not generate an issue automatically).
Enter the reason code and the time the event occurred.
Click Save to create the new issue.
4. Add Additional Information
In the Recent Issues section, click + Info.
Enter a comment or note.
Click Save so supervisors and managers can review later.
Tips & Best Practices
Use Update issue or Recent Issues whenever possible — creating new issues should be rare if alerts are set up correctly.
Apply one tag per issue for consistent reporting; only split if two distinct causes occurred.
Use the comment field for extra context that helps supervisors understand downtime causes.
Troubleshooting
No issues showing in Recent Issues → Check that alerts are configured in Alert Settings.
Wrong tag applied → Reopen the issue, select the correct tag, and save.
Accidental duplicate issue created → Delete the unnecessary issue if permissions allow.