Operator rounds: the readings in the shift log, not on paper
In continuous production the operator walks the plant at regular intervals and writes pressure, temperature, current, level and status onto a sheet. On paper or in a separate spreadsheet that data never reaches the shift log, cannot be trended, and there is no proof afterwards that the round took place. Operator rounds is a Shift log add-in: the sheet is a template, a walk is a round the operator fills in on a phone, and the values connect to the shift log, the data series and analysis.
In short
- The tenant edits the template without code or JSON: sections, points, limits (flag or hard), display conditions by another point’s value or the plant state. Publishing creates a new, unchangeable version.
- The schedule creates a round when the log opens: every shift, daily, on set days of the week or month, or every N hours; a missed round is closed as missed and does not roll over.
- On a phone it pages by section; it can be interrupted, a value waits on the device when the connection drops and uploads by itself; a correction asks for a reason and the previous value stays.
- The closing setting warns or blocks, with a justified override; values go to a data series and to Analytics, and the round to a PDF.
What is wrong today?
The round lives on a paper sheet or in a separate spreadsheet. The value does not reach the log or a data series, so it cannot be trended, and if a reading is missed nobody sees it.
A big sheet is long even for one operator: many fields are needed only for the line or product that is running. If the sheet cannot hide what is not needed, the operator fills empty fields or skips what matters.
How it works
The production manager builds the template, the operator fills it in on a phone, and the log does not let a skipped round slip away unnoticed.
Template
Sections (an area or an equipment group) and points: a number with a unit and limits, status (OK / not OK), yes / no, a choice, text, a photo. Required, comment and photo rules are set per point. A published version cannot be changed.
Visibility
A point or section is shown only if another point’s value or the plant state (which line is running) matches. If the Production plan is switched on, the plant state is read from it, otherwise the operator is asked at the start of the round.
Schedule and log
The schedule creates the round when the log opens, and the log shows an Operator rounds element with status and due window. A missed round can be closed with a reason.
Walk on a phone
Paged by section with large fields. An out-of-limit value is flagged at once; with a hard limit it cannot be recorded. Skipping asks for a reason, a photo can be uploaded. Several operators can write into one round; a second write is saved as a correction.
Closing
A round can be finished as done when every required point has a value or was skipped with a reason. When the log is closed by hand, the closing setting warns (the open round is closed as missed) or blocks (with a justified override). The nightly automatic close is not stopped by blocking.
What the plant sees
The same value says the same thing everywhere.
- Shift log
- The shift’s rounds with status (Due, In progress, Done, Missed) and due window; you start or continue a round here.
- Walk-through (phone)
- Sections, progress (“N / M points recorded”), a note on values waiting on the device, who else is working here, earlier values next to a correction.
- Shift PDF and round PDF
- The shift PDF gets one summary line per round; the separate round PDF has per section the point, value, recorder and time, with an out-of-range value marked in words.
- Data series
- A numeric point can be linked to a data series column: the value of a finished round goes into the series with its own reading time.
- Analytics
- Rounds due, completed, completed late and missed, and out-of-range values; completion is computed from the two counters.
| Point | Type | Lower | Upper | Unit | Limit |
|---|---|---|---|---|---|
| Discharge pressure | number | 4.0 | 6.0 | bar | flag |
| Bearing temperature | number | — | 75 | °C | hard |
| Leak | status | — | — | — | comment if not OK |
- Discharge pressure6.4 barout of limit — upper limit 6.0 (asks for a comment)
- Bearing temperature68 °COK
What it needs, and how to order it
- A Shift log add-in, separately orderable, part of a custom quote: request it on the Add-ins tab of the Control panel, and OPEREX switches it on.
- Display by plant state uses the Production plan (without it, the operator is asked at the start of the round), the data series link needs Data series, and the metrics need the Analytics module; none is needed for the basic operation.
- Without activation the shift log, the shift PDF, the data series and Analytics do not change at all. Rights come in four parts: view, record, edit templates, settings.
What it does not do
So you know what to expect, and what not.
- It is not location proof: there is no QR or NFC reading on the equipment; presence is given by the recording’s timestamp and author.
- It does not open an event or task by itself: from an out-of-range finding you can open a prefilled event with one click, but automatic opening does not exist.
- It does not open a CMMS fault report from a finding.
- It is not a Maintenance inspection round: the CMMS inspection round is maintenance work (a strategy and tasks for a functional location), Operator rounds is the operator’s per-shift reading; the two stay separate.
- It does not interpret: the round records, trends and metrics are Analytics’ job.
Further reading
Frequently asked questions
How is Operator rounds different from a Maintenance inspection round?
The Maintenance inspection round is a CMMS template package: it creates a maintenance strategy and tasks for a functional location. Operator rounds is the operator’s per-shift reading, tied to the shift log and the data series, and creates no maintenance task.
What happens if the signal drops during a round?
The value waits on the device and uploads by itself when the connection returns; the page says how many values are still waiting, and the round cannot be finished while there are any. A value that waited more than 12 hours cannot be recorded afterwards and has to be recorded again.
Can an open round stop the log from closing?
It depends on the closing setting: in warn mode the open round is closed as missed, in block mode closing the log by hand needs the round to be closed or a justified override. The nightly automatic close is not stopped by blocking: open rounds are closed as missed with a system marker.
Let's start a pilot
We'll show you OPEREX on your own operational processes — no strings attached.
Request a demo