Timeline Analysis
A report page for reviewing machine behavior over time through timeline-oriented analytics.
Overview
Access: Admin or Page Access reports_timeline, with relevant Machine Access. Roles and access.
Show how machine time is distributed across states and timeline categories.
Users open it from the Reports section in the main navigation.
Access
- Visibility: Protected
- Primary routes:
/reports/timeline-analysis
What You Can See
- Date and machine filters.
- Timeline-focused charts and summaries.
- Shift-aware reporting views.
In Reports → Timeline, a period of several days now includes time since the last state change, just like Machine History. After more than 20 minutes without a sensor signal, the last state counts only until the last signal; for a sensor powered by the machine, the silent time counts as Off.
What You Can Do
- Narrow the analysis to specific machines and dates.
- Compare how time was spent across machine states or reasons.
- Use the page to spot recurring downtime patterns.
When you request an export, the report may take time to create. If it takes longer than usual, Administrators can find it in Report archive once it is ready. Open the archive with the button next to the Timeline / Trend switch at the top of the page. Other users do not see the archive and should try the export again later. See Download and Update Reports.
In the archive, Revision identifies an updated report, while Version 2 beside the period identifies its layout. Point to either for an explanation. Downloads always contain the latest revision; emails already sent are not sent again. See Report Archive.
Choose a Version for an Export
Open Timeline Analysis through Reports in the side menu. Choose machines and dates, then select Generate report → Download Report (XLSX). The dialog now asks everyone who can export to choose Report version. Your current newsletter preference is selected each time it opens; without a saved choice, it starts with Version 1.
Select Version 1 or Version 2, compare What you get, or use Download an example for made-up data. Select Generate report to create the selected workbook. Follow the progress in the step list.
Your choice applies to this export only. Version 2 includes cycles, downtime reasons, and orders and operations worked on in the selected period. Version 2 also separates work centers from machine figures and shows Production without an order when your company recorded at least 5 intervals of real operations in the report period, excluding test orders. Work centers are excluded from that measure. With fewer than 5 intervals, order figures and the orders sheet are also absent. Get more out of this report with the PDA page on the first page explains why and how recording operations on the PDA page helps. Test orders are excluded from report lists and counts. Exports have no outlook for planned work. See Report Versions or follow create an export.
States, Reasons, and Duration Buckets
Timeline Analysis examines the state timeline of a period; Trend Analysis compares KPI trends across days. Switch between the Reports views and match their machine, date, and shift scope.
Downtime is Idle (orange) or Off (red). Downtime Analysis (labeled) groups it by assigned reason. An unlabeled warning means a reason is still missing. Timeline ranges / Time range are duration buckets, such as 1–5 or 5–30 minutes, used in Idletime Distribution. Focus Mode enlarges the analysis by hiding surrounding controls.
Automatic timeline reasons follow the specific reason rule, its DEFAULT rule, then Global rules. Admin-defined reason type and level 1–5 effects are unconfirmed. The calculations reference explains AVL, PRO, and the role of the selected period.
Since November 5, 2026 (v1.5.153), Downtime reason rules apply to more idle and off downtimes when the machine operator has chosen no reason. On machines with rules, more downtime can therefore receive a reason, changing the totals by reason in reports and charts. Downtimes from before the update remain unchanged. A reason chosen by the machine operator always takes priority. See automatic rules.
Read Automatically Labelled Breaks
If an administrator enables automatic break labels, finished idle or off downtime can receive the reason of a scheduled shift break. A person's choice takes priority. Earlier completed downtime is not relabelled when the setting is turned on.
With Label only the break (recommended), a longer downtime can appear as several parts: the break with its tolerance, plus the time before or after it. Each part counts as one downtime in counts and averages by reason. The remaining parts use the rules for their own length. Total time in each machine state stays the same. With Label the whole downtime, a long breakdown can appear entirely under the break's reason.
Read Downtime Reason Codes
Downtime chart labels include a reason's code when one is set. Short labels may be cut off; hover over a bar or pie slice to read the full name, code, and category. Categories help identify reasons; the charts still group by reason.
See downtime reason settings for how administrators maintain these labels.
Main Entities
- Machine
- Shift
- Timeline Event
- Timeline Reason
Outcomes and Limits
Common Outcomes
- Users identify which time categories are taking too much of the day.
Limits and Empty States
- Sparse data windows can make the report less useful.