Machine history: each row of an uploaded export is one stop. Its alarm text is matched to the guide by the alarm name the machine shows (for example "Outlet full: Outlet 2" is alarm 1.5). Texts that are not in the guide are listed as "Not in the guide".
Downtime: from a duration column (minutes unless the column says seconds or hours), otherwise from the end time.
Category, root cause, criticality, part, shift, response and repair time: read from a maintenance log's columns when it has them (technician names are not stored). "Part replaced" counts only repairs that replaced a part.
Waiting: the response time (stop to start of the repair) as a share of response plus repair time.
Chat questions: each answered question that was about 1 to 3 alarms counts once per alarm, from 18 November 2026 on. Only the alarm and the time are stored, no names and no question text. It shows what people ask about, not how often the machine stops.
Alarms 1.18 to 1.21 have no alarm code on the machine, so they never appear in a machine export; they can appear under questions.
The 80% line marks the "vital few": the smallest group of alarms or areas that together make 80% of the total.
Upload maintenance data (admins)
Upload an alarm export from the HMI, PLC or CMMS (.csv or .xlsx). It needs a column with the alarm text and a column with its time; an end-time or duration column adds downtime. Uploading an overlapping export again does not count events twice.