Skip to content

Operator rounds: data series link, Analytics metrics, PDFs and opening an event

A round records; interpreting (trend, compliance, metrics) is Analytics’ job. This article describes where the values go next.

A numeric point (Number (decimal) or Whole number) can be linked to a numeric column of a data series in the template editor: in the point’s ⋮ menu, Link to data series, choosing the Data series and the Column.

  • When does the value pass? When a round is done, at its own reading time (recorded_at), so it shows together with other data on the Data series page, in the trend and on Analytics tiles. A value of an open round is not mirrored mid-way.
  • What does not pass? The value of a hidden point, a skip, and the values of a missed round (those stay on the round and in the round PDF).
  • Corrections. Correcting a done round also corrects the series row (the previous value is kept); there is no delete. A repeated submission does not duplicate.
  • If the series rejects it (e.g. an archived series, the back-dating limit), the round is not blocked: the point does not pass and the audit says so.
  • What is needed? A new link needs the Data series add-on and the editor’s own right to record series values (series:record). An existing link can be removed without them. With differing units the link warns (“Units differ: …”) but does not forbid.

Analytics (if switched on) gets a new metric family, per plant, by day / week / month / year (the day is the round’s business day):

Metric What it counts
Rounds due All rounds scheduled for the day, in any status.
Rounds completed Done rounds.
Rounds completed late Finished after the end of the due window.
Rounds missed Missed with a reason or by system close.
Out-of-range values (rounds) Out-of-limit values on the visible points of finished rounds.

Completion (completed / due) is a formula over the two counters, not a stored ratio. The metrics show in the metric picker and on dashboard tiles only where Operator rounds is switched on; the running day’s completion is a lower estimate mid-shift. There is no backfill: the projection counts from the first write.

  • Shift PDF. The closed log’s PDF gets one summary line per round: status, window, who closed it (or the reason missed), points recorded, number of out-of-range values. With no round, and with the add-in off, the PDF is as before.
  • Round PDF. On the round’s page, Download round as PDF: header, the round’s data, per section point · value · who, when · note. An out-of-range value is marked in words (“Out of range”), a skip reason, a correction reason and earlier values on separate rows; a hidden point is marked (“not shown, not counted”). The PDF is not a stored record: it gives the round’s current state, with the time of generation and the generator.

If the walk-through marks a value out of range, an Open event button sits next to it. One click takes you to the log’s event form, prefilled: point, value, limit, round, time. The prefill is a suggestion; saving goes the usual way. Requirements: you have the right to create events (event:create) and the log is an open draft. There is no automatic event opening, and the finding does not open a CMMS fault report.

  • An Analytics metric forms from finished rounds and the round’s status; an open round’s value does not count among out-of-range values until then.
  • A value that became hidden stays on the round but does not go into the series or the metric.

Last updated: