Overview
The Issues module helps teams track, tag, and analyze machine downtime and other events. It includes three tabs — Issues, Analysis, and Alert Settings — that work together to generate issues, assign reasons, and review trends. This guide explains how each tab works and how to use them in daily operations.
Prerequisites
Access to the Issues module
Permissions to create or tag issues
At least one alert configured in Alert Settings
Step-by-Step Instructions
1. Configure Alert Settings
Go to Issues > Alert Settings.
Set up rules for when an alert should trigger:
Define the condition (e.g., machine state, downtime duration).
Choose when alerts should appear (e.g., first, second, or third shift).
Select notification recipients, including escalation rules if needed.
Save the alert.
Each alert will automatically generate an issue when triggered.
2. Review and Tag Issues
Open the Issues tab to see all issues generated from alerts.
Click an issue to open details such as the load curve and event history.
Apply a reason code by selecting Tag.
Best practice: use one reason code per issue.
3. Analyze Issues
Go to the Analysis tab for in-depth reporting.
Choose from multiple chart types:
Pareto (duration or frequency of issues)
Time series
Overview
Filter results by date range, devices, tags, assignees, status, or type.
Click on a chart segment to drill into specific categories (e.g., mechanical issues).
Tips & Best Practices
Use the Pareto chart to quickly identify the top causes of downtime.
Apply filters to focus on relevant shifts, devices, or tags.
Review issues in shift handovers, weekly performance meetings, or team reviews to align on priorities.
Ensure issues are consistently tagged for accurate reporting.
Troubleshooting
Issue appears untagged → Apply a reason code manually in the Issues tab.
No issues showing in Issues tab → Confirm alerts are set up correctly in Alert Settings.
Alerts not notifying the right people → Check the notification hierarchy in Alert Settings.