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.
Record what happens in your plant — and the work each shift completes
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)
Shift · 06:00–14:00Plant: Phosgene production unitShift supervisor: B. Kovács
- 06:14
Reactor feed stable, pressure 2.4 bar within the normal band.
- 09:02
Pump P-204 vibration near the upper limit — heightened monitoring.
- 11:37
Gasket leak at the heat exchanger, dripping into the drip tray.
- 13:50
Handover: keep monitoring P-204 for the next shift.
The module
Built for the daily rhythm of a multi-shift plant
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.
Roles you assign
Operator, shift supervisor, plant manager, data steward… — you decide who records, sees and finalises what (role-based access).
Logs open and close on their own
Each shift's log is generated and closed automatically, on schedule — nobody has to remember to open or finalise it.
Standing orders & shift instructions
Push standing orders to the floor; every shift acknowledges what's active — with a trace of who saw what.
Recurring & carried-over tasks
Assign one-off and recurring tasks; unfinished ones carry over to the next shift, recurring ones reappear on schedule.
Events, incidents & audit trail
Capture events and near-misses, escalate to incidents, and keep an append-only audit trail — who recorded what, and when.
Everything the shift log takes care of
One auditable system for the daily rhythm of a shift-based plant — from role to report, in one place.
Role assignment
Operator, supervisor, plant manager, data steward — you decide who records, sees and finalises what, with custom roles too.
Multiple plants
Several plants in one organisation, with quick switching, per-plant log setup and access.
Multiple sites
Geographically separate sites under one account — each with its own plants, logs and roster.
Automatic log lifecycle
The system opens and closes logs on their own, from your rota and timezone — no manual start.
Instructions and tasks
Standing orders and one-off or recurring tasks; unfinished ones carry over to the next shift.
Events and incidents
Capture with HSE severity and an open→investigating→closed lifecycle, tied to the log.
Shift attendance
Record who worked the shift — from a managed roster, with name and position.
Customisable log
A drag-and-drop builder and ready templates: text, numbers, lists, tables, images — your log.
Archive and search
Filterable, searchable past logs — by status, date, who finalised, and plant.
PDF report
A tamper-proof PDF for every closed shift — saved to the server, downloadable and previewable.
Automatic delivery
The end-of-shift report emailed to your contacts on schedule — no login required.
Audit trail
Every change is recorded (append-only, ISO 45001 §10.2) — nothing can be rewritten silently.
Data export
Any datapoint into a CSV/Excel report with a point-and-click builder; saved definitions re-run anytime.
EU data residency
Your data stays in the EU (GDPR); self-hosted or on-premise on request.
Multilingual interface
Interface language is configurable per organisation — Hungarian and English today, extendable to more; dates and formats follow the locale.
Excel isn't auditable. Paper gets lost.
Same shift, two worlds. Toggle and see the difference.
- Scattered Excel tabs — everyone on a different version.
- Handwritten log: “who changed it, and when?”
- The near-miss gets lost between shifts.
- At audit time you hunt for evidence for days.
- One structured entry — with timestamp and user.
- Append-only audit trail: can't be rewritten afterwards.
- The near-miss is escalated and tracked end to end.
- At audit time, the full trail is one click away.
Who it's for
Built for any operation that runs in shifts
Continuous or batch, hazardous or not, from a single production unit to large multi-site organisations. Common settings:
- Chemical & process plants
- Food production
- Energy & utilities
- Pharmaceuticals
- Manufacturing
- Oil & gas
Works for a single production unit too — a few shifts, no IT department.
Where the asset team pulls in one direction
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.
One auditable workflow
Shift log
The shift's events and handover in one place.
Event
An entry becomes an incident or near-miss record.
CMMS trigger
A maintenance-relevant event raises a task.
Report
An auditable, finalized shift report.
Try it: the audit trail can't be rewritten after the fact.
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.
- 06:14B. KovácsShift start, systems in normal operation.
- 09:02K. NagyPump P-204 vibration near the upper limit.
- 11:37K. NagyGasket leak at the heat exchanger — near-miss, escalated.
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.
How much time can you free up in a year?
Set your own numbers — the calculator gives a conservative estimate. Illustration, not an offer.
—Documentation hours saved / year
—Audit hours saved / year
—Total hours freed up / year
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.
Plans
Current prices apply to the Shift log module.
Starter
Recommended for
A single production unit or SME on one site — no dedicated IT, cloud is fine.
€99/ site / month
- Own subdomain
- Supabase Auth
- EU data storage
Business
Recommended for
Multi-department or multi-site teams that need data isolation, white-label and their own domain.
€299/ site / month
- Custom domain
- white-label
- dedicated project
Enterprise
Recommended for
Large, regulated, multi-site operations that need data sovereignty — on-premise or air-gapped.
Custom quote
- Own SSO (Keycloak)
- self-hosted storage
- Seveso-capable
Indicative pricing — final amounts are being finalised. For an exact quote, let's talk.
Frequently asked questions
What is a digital shift log?
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.
How does OPEREX support the ISO 45001 §10.2 audit?
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.
Which operations is it for?
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.
Where is the data stored?
In the EU, under GDPR. On request, a dedicated project or on-premise (air-gapped) deployment in the Business and Enterprise plans.
How long does it take to roll out the shift log?
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.
Who can access it, and with what role?
Role-based access (RBAC): operator, shift supervisor, plant manager, data steward, etc. — who sees, records and finalises what. Every change leaves an audit trail.
How does the shift log relate to operational excellence?
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.
The platform
Part of the OPEREX system
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.
The systemOperational excellence — the full platform.Coming soonIncident investigationNear-miss and incident investigation, RCA and action tracking.Coming soonPermit to WorkPTW workflow and interlock-bypass tracking.Coming soonMaintenance (CMMS)Work orders and maintenance triggers straight from the log.
Let's start a pilot
We'll show you OPEREX on your own operational processes — no strings attached.
Request a demo