Process safety, end to end

Work permits and gate control, on one plant record.

Permit360 issues and approves work permits. Gate360 knows who is on site and whether they are cleared to be there. Buy either on its own — or both, and share one company, one sign-in and one set of plants, departments and people.

Two products, sold separately

Each is a complete system on its own. Neither needs the other to be useful.

  • Permit360

    Electronic work permits — raised from a template, routed through an approval flow, activated, closed, and audited at every step.

    • Templates and approval flows a plant authors itself
    • Lockout/Tagout and the equipment register on the same record
    • Every permit frozen with the wording it was signed under
    • Dates decided in the plant’s own time zone, never the server’s
  • Gate360

    Contractors, visitors and gate entry. Who is inside, what their documents say, and whether the rules let them through.

    • Contractor firms, their workers, and the papers each one owes
    • Visits booked ahead, with the areas each visitor may enter
    • One scan box at the barrier, with the reason for any refusal
    • Emergency roll call as a frozen snapshot, not a live list

How it works

The same four steps whether you run one product or both.

  1. 1

    Set the company up once

    Plants, departments, sections and the people who work in them. Both products read the same rows.

  2. 2

    Give each person what they need

    One account and one sign-in. Which products it opens, and what they may do in each, is decided per product.

  3. 3

    Run the work

    Permits are raised and approved; contractors and visitors are cleared at the gate. Each product keeps its own rules.

  4. 4

    Answer for it afterwards

    Every decision is on the record with who made it and when — the question an inspector actually asks.

And if you run both

Nothing is merged that should not be. Each product keeps its own rules; what they share is the company underneath.

One organisationA plant renamed once is renamed everywhere. There is one set of rows, not a copy per product that drifts apart within a month.
One person, one accountSomebody joins once and is suspended once. Suspending reaches every product at the same moment, which is a security argument rather than a convenience.
One place to administer itPeople, roles and the structure move into a single Console. Buy one product and nothing changes — they stay exactly where they are.