Reading a job report

Open Jobs, then any completed job. The report is built the first time you open it and kept from then on.

Notes come first

If there is a coloured About this report panel at the top, read it before anything else. It lists everything that qualifies the numbers below — a gap in the data, an approximate end time, a plan that does not store readings, a period that was never rule-evaluated.

These are not disclaimers. Each one changes how a figure below should be read, which is why they are at the top rather than in a footnote.

Header

Machine, operator, start, end, duration, and — if the machine has GPS — the coordinates where the job took place, linked to a map.

How it started / ended tells you where the boundary came from. manual means a person pressed the button. sweep or timeout means nobody did and Synacl closed the job itself, in which case the end time is the latest it could have been, not a measurement.

Summary figures

Duration, alarms, rule fires, actions, readings recorded, and coverage.

Coverage is the share of expected readings that actually arrived. Below 100% means readings are missing — usually the machine was offline for part of the job. The notes panel says when.

Before / after

Each chosen reading at the start of the job, at the end, and the change. Green is an increase, red a decrease.

A dash in the Change column means one of the two boundary readings was not available, so no change can be calculated. This is not the same as no change, and the report never shows a zero in its place. Hover the ⓘ next to a reading to see how each boundary value was obtained — a live value at the boundary, or the closest stored reading either side of it.

Readings

One chart per group of readings that share a unit. Readings in different units are never plotted together — overlaying °C on bar produces a picture that looks informative and means nothing.

A dashed red line is that tag's configured alarm limit.

A break in the line is real. It means nothing was recorded for that period, and the chart deliberately does not join across it. A continuous line through an outage would read as "steady" when it means "we heard nothing".

Alarms

Every alarm raised during the job, with the value that triggered it, the configured limits, when it cleared, and how long it lasted.

An alarm that had not cleared when the job ended shows open at end rather than a duration. Timing it to the end of the job would invent a resolution that never happened.

A cleared alarm is one row, not two: the clear is shown as the end of the alarm it belongs to.

Rule & action activity

Which of your rules fired during the job and how many actions were dispatched, with any failures called out.

If the machine was offline for part of the job, these counts cover only the period it was online. Readings buffered on the gateway are replayed without rule evaluation, so nothing in that window could have fired. The notes panel says so explicitly, because a zero here otherwise reads as "nothing happened" rather than "nothing was checked".

Exporting

PDF, CSV and Excel buttons are at the top right.

PDF — the formatted report, for handing over.
CSV — every section in one file with a section column, for pivot tables.
Excel — the same content across separate sheets: Summary, Before-After, Readings, Alarms, Notes.

All three are produced on the server from the stored report, so an export always matches what you are looking at on screen.

Report versions

The footer shows the report version, when it was generated, and a content fingerprint.

Regenerate produces a new version rather than overwriting the existing one, so a report you have already sent to someone stays exactly as they received it. Regenerate after correcting something that affects the figures — a tag's scale factor or its alarm limits, for example.