What a downtime record contains

A PlantWatch downtime record connects a production stop with its time, duration, and configured controller context. Depending on the installation, this context can include state changes, alarms, interlocks, loads, or other process values.

The record is evidence for an investigation. It does not automatically prove a root cause unless the configured signals support that conclusion.

Review the event sequence

Begin with the stop time, then inspect the events immediately before it. A useful sequence can show, for example, a rising load, a lost sensor signal, an active interlock, and the subsequent production stop.

Check whether the same sequence occurs on other stops. Repetition is often more useful than a single isolated event when deciding what to investigate next.

Compare duration and recurrence

Duration shows the production impact of an event. Recurrence shows how often the same or similar condition affects the plant.

Use both dimensions when prioritizing work: one long stop and many short stops can require different responses even when their total downtime is similar.

Confirm the signal context

PlantWatch can only show signals connected and configured for the installation. If the event history ends before the suspected cause becomes visible, review whether another controller state, alarm, or process value should be added.

Do not change control logic based on a dashboard observation alone. Confirm findings with the responsible production, maintenance, or automation team.

Continue the analysis

Use Historical trends to compare values and states across a wider time window. Use Automated reports to make recurring downtime visible over regular reporting periods.