Table of Contents
Downtime Log Help Guide
Track repeated machine stoppages over time, then use Pareto analysis to focus on the biggest losses first.
Open ToolWhat this tool does
The Downtime Log is a machine-based record of downtime events. Instead of creating one report per incident, you keep adding events to the same machine log over time.
- One saved report represents one machine log
- Each log can contain many downtime events
- The log automatically summarizes total downtime, cost, and category Pareto patterns
When to use it
- You want to track recurring breakdowns or waiting losses on one machine
- You need a simple downtime Pareto without a full OEE system
- You want to connect downtime events to NCR, RCA, or SPC work
- You need a report you can revisit and update over days or weeks
1 Create the machine log
Enter the machine name, optional line or area, company name, and a default hourly cost rate. This creates the container for all future downtime events.
Click to view screenshot
2 Add the event details
Record the date, duration, category, planned/unplanned status, description, and reporter. Keep the description specific enough to recognize recurring failures later.
Click to view screenshot
3 Capture impact and linked reports
Add units lost, estimated cost, resolution, preventive action, and any linked NCR, RCA, or SPC report IDs. You can also jump directly to new NCR or RCA forms from this step.
Click to view screenshot
4 Review the log and Pareto chart
The log page shows total downtime, event count, average duration, and a Pareto chart by category. Click a Pareto bar to filter the event list to that category.
Click to view screenshot
5 Export and continue later
Download a PDF report or share the saved log. Because the tool uses saved reports, you can reopen the same machine log later from the dashboard and keep adding events.
Click to view screenshot
Practical tips
- Use consistent categories so the Pareto chart stays meaningful over time.
- Link quality-related downtime to NCRs and unstable-process downtime to SPC reports whenever possible.
- Review the log weekly to see whether breakdowns are clustering around one system or shift.