MagyarContact
Back — Permit to Work
Product updates

What's new

What's new in the Permit to Work module — every change that makes your day easier, in plain language, not developer-speak.

4 updatesupdated weekly

September 2026

4
Security

We restore-tested the backups end to end

A backup is worth what has been restored from it — so we did it. From the off-site backup (every 6 hours, to EU storage) we restored the entire database into a separate instance and counted: every table, every row and every user account came back intact. We checked the canonical shift-log PDFs separately: every one of them has its backed-up file, byte-for-byte identical to the original. The data itself restores in seconds. The full recovery time — which includes rebuilding a machine — is still being measured, and we will only state it once we can back it with a number.

  • Every table and every user account came back intact — counted, not assumed
  • Every canonical shift-log PDF is in the backup, byte-identical
  • What we have not measured, we say so — the full recovery time is not established yet

Security & trust

Feature

PTW phase ③: permit metrics in analytics

With the third phase, Permit to Work data flows into Operations Analytics: permits issued, gate-blocked attempts and throughput by type — broken down by site, plant and period. The data sits where the decision is: you can see which checkpoint stops work, and where.

  • Issued, gate-blocked attempts, throughput by type — on the dashboard
  • Site / plant / period breakdown, in one view with the other modules
Feature

PTW phase ② done: the checkpoints are live

The second phase is live: the pre-issue checkpoints are now real gates. A competence gate with expiry (person and document master, xlsx/csv import), isolation points (LOTO / blind-flange reference numbers), time-valid gas testing with a re-test on extension, a worker lock (one person on one open permit at a time), SIMOPS along the technical-location tree, and a last-minute risk assessment (LMRA). All off / warn / block, per site and per type.

  • Competence, isolation, gas testing, worker lock, SIMOPS, LMRA — all as gates
  • Every point off / warn / block, set per site and per permit type
Feature

New module: Permit to Work (PTW) — phase ①

The Permit to Work module has started, and its first phase is now live. Risky work now runs through a controlled permit lifecycle — from request to a two-sided hand-back — with every step recorded by an append-only, hash-chained signature that visibly breaks if anyone edits the permit afterwards. The permit shows up where the shift works: open permits appear in the log and the shift handover, and it is gated to the maintenance work order. This is the first phase; the further phases follow in their own entries.

  • Append-only, hash-chained signature trail, verifiable in the browser too
  • Issuer ≠ requester and a two-sided hand-back, enforced server-side
  • 3 ready templates (general / hot work / confined-space entry) + off/warn/block policy gates
Newsletter

Follow how OPEREX evolves

New modules, industrial shift-log tips and ISO 45001 practices — once a month at most, no spam.

You can unsubscribe anytime — the link is at the bottom of every email.