Multi-shift by design
Handles your full rota — continuous or batch, any number of shifts and crews. The system knows which shift is on from the time of day.
In one auditable place: structured shift handover, event and incident log, and an append-only audit trail. For any shift-based operation — offline and on your own servers, too.
Production Excellence (operations)
Reactor feed stable, pressure 2.4 bar within the normal band.
Pump P-204 vibration near the upper limit — heightened monitoring.
Gasket leak at the heat exchanger, dripping into the drip tray.
Handover: keep monitoring P-204 for the next shift.
OPEREX runs the operating rhythm of a multi-shift operation: the right people record the right things, every shift's log opens and closes on schedule, and nothing — an instruction, a recurring task, an event — slips between shifts.
Handles your full rota — continuous or batch, any number of shifts and crews. The system knows which shift is on from the time of day.
Operator, shift supervisor, plant manager, data steward… — you decide who records, sees and finalises what (role-based access).
Each shift's log is generated and closed automatically, on schedule — nobody has to remember to open or finalise it.
Push standing orders to the floor; every shift acknowledges what's active — with a trace of who saw what.
Assign one-off and recurring tasks; unfinished ones carry over to the next shift, recurring ones reappear on schedule.
Capture events and near-misses, escalate to incidents, and keep an append-only audit trail — who recorded what, and when.
One auditable system for the daily rhythm of a shift-based plant — from role to report, in one place.
Separately orderable paid add-ins — the base log is complete without them. The interface grows as you switch them on.
Continuous recording whose lifetime belongs to the process, not the shift: lab results, in-process sampling, batch tracking. The next shift keeps writing into the same series and sees the history.
Details & pricingYour shift records in its own language; your foreign colleague reads the log in theirs, with a toggle, right in the app — and the finalized log's report can reach each recipient in their own language too, attached alongside the original PDF. The original document stays unchanged and authoritative — the translation is a marked, non-authoritative layer on top: it renders the intent (not word-for-word), keeps equipment identifiers and names untouched, and flags anything uncertain. English for now; more languages on request.
Details & pricingEmployees, contractors and visitors can report an event without signing in, from a posted QR code or a link — to a plant, a site or the whole company. The report lands in the plant’s shift log or the Events inbox; the reporter’s details are kept separately, with configurable retention. An optional public tier adds a public reporting page with bot protection and quarantine, plus a secret status link for the reporter.
Details & pricingFor batch production: campaign phases per plant with signed gates, every step recorded in a hash chain. A start-up checklist, a phase indicator in the log, progress against plan and a campaign PDF with QR verification — with Training, also who takes which exam.
Details & pricingBatch production batch by batch, across shifts: template-based steps or an event log (dosing, measurement, correction), hourly data and lab results on one sheet, with a summary box per vessel, also as a PDF and in analytics. Correction helper: the template formula suggests a correction from the latest measurement; the operator decides. Works without campaigns; it needs the Data series that roll across shifts add-in.
Details & pricingFor continuous production lines: daily plan rows per line (product, grade, quantity, target tank), the running product with changeovers and stops, and an Overview per line. Plan vs actual from the quantities of the shift log's line periods, with a produced-quantity calculation helper (the formula suggests, the operator decides). Start-up on a production line: start-up checklist, signed gates, production gate.
Details & pricingGrades per product with versioned limits, per sampling point: an in-process target range and a release limit. On Batch records it is the target grade (measurements are judged against it; changing it needs a reason), on a Production plan row the planned grade, and on Analytics trends a target range with the share within it.
Details & pricingA batch does not end with the shift. The template sets out the steps, the next shift picks up where the last one stopped, and the steps, hourly data and lab results stay on one sheet.


It needs the Data series that roll across shifts add-in. It works without Campaign start-up and can be linked to a campaign. Part of a custom quote.
Two add-ins for continuous production lines. The plan says what should run, the shift log records what ran and how much was made, and Quality specifications set per product what a sample is measured against.
Plan rows per production line and day; the shift records the product actually running.
Grades and their limits per product in one place, versioned — Batch records, the Production plan and Analytics all read from it.
Both are Shift log add-ins and part of a custom quote: request them on the Add-ins tab of the Control panel, and OPEREX switches them on. Plan vs actual uses per-line recording in the shift log's operating-mode element; the target grade needs Batch records, and the target-range trend and the plan vs actual grid need the Analytics module.
Solution briefs, the guide, datasheet and security brief — as PDF, always generated from the latest product information.
Same shift, two worlds. Toggle and see the difference.
Continuous or batch, hazardous or not, from a single production unit to large multi-site organisations. Common settings:
Works for a single production unit too — a few shifts, no IT department.
Operations, process technology, maintenance and HSE all see the same log. When goals are aligned the team's rope pulls together (1+1+1+1=4); when they aren't, the effort cancels out (1+1+1−1=2). The shift log is where that daily alignment lives.
The shift's events and handover in one place.
An entry becomes an incident or near-miss record.
A maintenance-relevant event raises a task.
An auditable, finalized shift report.
The audit log is append-only: you can add a new row, but you can't rewrite or delete an existing one. Click the lock on a row and see.
The audit trail is the immutable, timestamped history of the shift log and its events: who recorded what, and when. You can only append — never rewrite or delete an existing entry. That's what gives an ISO 45001 §10.2 investigation trustworthy, tamper-evident evidence.
This demo illustrates the idea: in production it's enforced server-side by an append-only database policy (FORCE RLS — inserts only); even the app can't rewrite an existing row.
Set your own numbers — the calculator gives a conservative estimate. Illustration, not an offer.
This freed-up time can go to autonomous maintenance, preventive work, or other value-creating activity — not lost hours, but recovered capacity.
Assumptions (tunable): 40% of documentation time and 50% of audit prep can be saved; documentation time is counted per person per shift. This is an illustration, not a contractual promise.
A shift log is the official handover document for shift changes at any operation that runs in shifts (continuous or batch): what happened during the shift, and what the next team needs to know. OPEREX digitizes it — with immutable, timestamped entries.
Every entry and status change gets an append-only audit trail (who, what, when) that cannot be altered afterwards. The shift log and incident handling thus provide auditable evidence.
Any operation that runs in shifts — continuous or batch, hazardous or not, from a single production unit to large multi-site organisations. Common settings include chemical and process plants, food production, energy, utilities and manufacturing — oil & gas among them.
In the EU, under GDPR. On request, a dedicated or on-premise (air-gapped) deployment (Enterprise).
The shift log is the lowest-risk entry point: structured shift handover can go live for one unit within days to weeks via a pilot. We fit the rollout to the team's pace.
Role-based access (RBAC): operator, shift supervisor, plant manager, data steward, etc. — who sees, records and finalises what. Every change leaves an audit trail.
The shift log is the daily execution layer of operational excellence — its 'last meter'. The top-down OE framework (process safety, reliability, efficiency) becomes a concrete, auditable datapoint here: the KPI fact, the gap to target and the triggered action are recorded shift by shift.
Yes — that is usually the first step. What the printed shift log or event log book holds (handover, events, instructions, tasks) becomes structured, searchable entries with an immutable audit trail; the log structure is shaped to the book you use today. Where a printed copy is still needed, the log can be exported to PDF.
Yes, with the Batch records add-in. The template sets out the steps, shifts carry the same batch sheet forward, hourly data and lab results stay in one place, and the batch can be downloaded as a PDF. The add-in is part of a custom quote, needs the Data series that roll across shifts add-in, and works without campaigns.
Yes, with the correction helper of the Batch records add-in. A formula set in the template suggests a correction from the latest measurement, the batch mass or a manual input; two clicks turn it into an event, and the operator enters or overrides the quantity. The server recalculates with the batch's template version and stores only a matching result. It is a suggestion, not automatic dosing — the formula comes from your own process engineers.
Yes, with the Production plan add-in. You write plan rows per production line and day (product, grade, quantity, target tank); the actual is the quantity of the shift log's line periods, which the calculation helper can suggest from a formula, with the operator deciding. Open periods and periods without a quantity do not count, and the system says what is missing. Grades and their limits come from the Quality specifications add-in: an in-process target range and a release limit, and the target grade on Batch records. Both are part of a custom quote.
Help describes the product: a concrete task, numbered steps, and what to do when you get stuck. Public, searchable, in Hungarian and English.
A taste of one article: “Log an event in the diary”
From the built-in types (HSE, technical fault, quality deviation, maintenance-requiring, process, material release, other) or your own; plus a subcategory, if there is one.
Near miss, incident or accident. For other types the field does not even appear.
The date comes from the diary — you only enter hours and minutes, and only within the shift window.
Go deeper into the methodology behind this module.
One module among several — all built around operational excellence, sharing data with each other.
The shift log is the daily execution layer of operational excellence — where the KPI fact, the gap to target and the triggered action are recorded shift by shift, auditably.
A trust surface for the whole OPEREX platform — not a module-level claim. The details are each on one page, with the limits stated.
We'll show you OPEREX on your own operational processes — no strings attached.
Request a demoNew modules, industrial shift-log tips and ISO 45001 practices — once a month at most, no spam.