Build it up module by module

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.

Your log runs on your own address (e.g. log.yourco.com), and its emails come from there too. The free yourco.operex.eu subdomain is included with every module — this is for when you want more than that.

Your 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.

We review OPEREX's recommended permit-issuing rules — risk assessment, issuing conditions, policy — with an occupational-safety expert periodically and after every significant legal change. We tell you what changed and why, and on request load the update into your organisation's settings. A new installation always starts with the latest recommendation; this service brings you the later changes. You can deviate from the recommendation at any time: the decision is yours, and your justification stays on record.

Employees, 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 and goes through the usual event handling; the reporter’s details are kept separately, with a configurable retention period. The add-in also has a public (resident) tier: a public reporting page per site (odour, noise, smoke, flare, dust), switched on separately for each organisation, with a “not an emergency line — 112” band, bot protection (ALTCHA, no third-party service) and quarantine: a resident’s report arrives as a “New” event tagged “Public” in the inbox, never in the shift log. The reporter can follow the report’s status on a secret link from the receipt (Received, Under review, Closed), ask for e-mail notifications (after confirmation, only when the status changes) and see the handler’s public reply; the internal reason and notes are never shown. On the page the reporter picks a zone, the page can also be embedded in the organisation’s own website (the organisation decides where — even on any site), handlers get a single alert when several reports arrive from one zone within a short time (the system counts reports), and duplicates can be merged. The organisation admin switches the public tier on themselves and tailors the privacy notice text too (pre-filled with the OPEREX suggestion).