Which Report Do I Use? Matching Common Questions to L2L Reports
Last updated: November 5, 2026
L2L has dozens of reports, and several look alike. This guide starts from the question you're trying to answer and points you to the report built for it. It also explains why two reports can show different numbers for what looks like the same thing.
For background on where report data comes from (hierarchy, dispatch data, and production data), see How to use L2L Reports.
Downtime and Maintenance
Your question | Use this report | Good to know |
|---|---|---|
Where are we losing the most time to downtime? | Ranks by minutes. Drill down from area to line to machine. | |
What breaks most often? | Occurrence Pareto | Ranks by count of dispatches created in the date range. Frequent, recurring events often drain more resources than one long event. |
Which events were long enough to matter? | Only counts events over the Significant Event threshold set in Setup. | |
Which actions or components are driving downtime? | Time Pareto, drilled into Actions and Components | Minutes go up when you drill in. See Downtime Pareto for Action and Components. |
How much time are technicians spending, and where? | Shows dispatch time by resource. | |
How long do dispatches sit in each status? | Useful for finding waiting time (for example, waiting on parts). | |
I need the actual list of dispatches, with comments and who worked them. | Shows every dispatch open at any time in the date range. Also opens from the History Detail link on most reports. | |
Which dispatches are still open? | Dispatch History with Currently Open/Not Completed checked | Check only one status box at a time, or the report may return no data. |
Preventive Maintenance (PM)
Your question | Use this report | Good to know |
|---|---|---|
Did we complete this period's PMs, and were they on time? | Shows On Time, Past Due, Completed, and Missed counts. Only includes PMs from the Scheduler. | |
Is our PM on-time rate getting better or worse? | Narrow it to one area or machine first to find patterns. |
Production
Your question | Use this report | Good to know |
|---|---|---|
How is our OEE trending? | OEE = Availability × Quality × Performance. | |
Which lines have the lowest OEE? | Can differ slightly from the Trend report because of rounding settings. | |
How long were we not running, and why? | Breaks lost time into downtime, non-execution, scrap, and non-production minutes. | |
What are our biggest scrap reasons? | Needs operators to enter scrap with categories. | |
Is scrap going up or down? |
Spares and Notifications
Your question | Use this report | Good to know |
|---|---|---|
Which spare parts come up most often? | ||
Did a notification actually go out, and to whom? | Helpful when someone says they never got an alert. |
Questions No Standard Report Answers
If you need to compare sites, combine data in a new way, or build a chart that doesn't exist, use L2L Analytics. See L2L Analytics: Getting Started with Datasets, Charts, and Dashboards.
Why Don't My Numbers Match?
Reports are built for different questions, so they count different things. The most common mismatches:
Dispatch History vs. Occurrence Pareto: Occurrence Pareto counts dispatches created in the date range. Dispatch History lists dispatches open at any time in the range, including ones created earlier. See Dispatch History vs. Occurrence Pareto results.
Time Pareto vs. Lost Production Time: Lost Production Time only counts downtime during scheduled production pitches. Time Pareto counts all downtime, including after the shift ends, so it is often higher.
Time Pareto vs. Actions and Components: When you drill into actions and components, each dispatch's downtime is counted once per action/component entered, so the total goes up.
A report vs. its History Detail: Dispatches that started before or ended after your date range are cut off in the report but listed in full in History Detail.
OEE Pareto vs. OEE Trend: The two use different rounding (precision) settings.
Tips
Stop exporting to Excel every week. Save your filters as a report template and schedule the report to email you. See Saving & Scheduling Reports.
Start broad, then drill down. Begin at the area level, then click into lines and machines.
Good data in, good reports out. Reports are only as accurate as what's entered. Close dispatches promptly and enter actions, components, and scrap, not just notes.