Electronic Permit to Work · Offshore & Onshore Facilities

The conflicts your permit board may not see. Found before work starts.

PERMITA is a configurable electronic Permit to Work platform with a deterministic work-control reasoning layer. It is configured to the operator's PTW procedure, authority matrix, isolation philosophy, permit taxonomy, and facility topology, then models permits, equipment, work locations, isolations, and simultaneous activities as a live graph to surface multi-step conflict chains that may be difficult to identify through conventional permit-board review.

Offline-first. Single-tenant deployment. Deterministic safety logic.

Interactive · Illustrative scenario based on common SIMOPS conflict patterns

Two permits. Three decks apart. One conflict chain.

A coordinator scanning the permit board sees two unrelated jobs. The graph can trace a path between them through equipment, isolations, topology, and concurrent work. Run the traversal.

CONFLICT TRAVERSAL — LIVE PERMIT GRAPH
OPEN 3D PLATFORM VIEW
MAIN DECK MEZZANINE CELLAR DECK CW-017 · COLD WORK Break containment — pump P-201 CLOSED DRAIN HDR shared system · 30-HD-002 ATM VENT V-114 cellar deck east HW-042 · HOT WORK Grinding — 8 m from V-114 CONFLICT: HW-042 ⟷ CW-017 · 3-EDGE PATH
Cold work permit Hot work permit Plant topology node Traversed conflict path
// permit board view: CW-017 (main deck) and HW-042 (cellar deck) — different decks, different crews, no shared equipment tag. No conflict flagged by manual review.

Architecture

Your PTW procedure on top. One reasoning engine underneath.

Every operator's permit forms, approval chains, and validity rules are different, so PERMITA treats them as configuration and mirrors them from your existing PTW procedure. The platform architecture is configurable; implementation focuses on your authority matrix, isolation philosophy, permit taxonomy, and facility topology. What never changes is the deterministic reasoning layer that evaluates work interactions through explicit rules and traceable relationships.

CONFIGURATION LAYER — YOURS

Your permit types, forms & approval chains

Permit categories, field layouts, validity windows, revalidation rules, and authority hierarchies configured from your PTW procedure. Crews see the permit they already know.

REASONING ENGINE — INVARIANT

Graph ontology + deterministic rule engine

Permits, isolations, energy sources, and plant topology as a live graph. Every state change triggers a traversal: spatial, energy-source, activity-class, and multi-hop system conflicts — computed, logged, explainable.

Built for the deck, not the demo room

Capabilities beyond conventional forms-digitization ePTW.

CONFLICT TRAVERSAL

Multi-hop SIMOPS detection

Manual reviews often focus on same-area, same-shift pairs. PERMITA traverses the plant graph — containment breaks, shared headers, vent routes, load paths, and linked work scopes — and can identify conflict chains that may be difficult to spot through conventional permit-board review.

OFFLINE-FIRST

Full function with zero WAN

Permit authority lives on the platform node. Issue, endorse, suspend, and close permits with no shore link; local actions are retained and synchronization occurs when connectivity returns. Designed for offshore intermittent-connectivity environments where data integrity and conflict handling remain important.

ISOLATION INTEGRITY

Isolations as first-class objects

Isolations carry their own lifecycle, linked many-to-many to permits. "If I break this isolation, which live permits are affected?" is a one-line query — not a coordinator's memory.

Integration layer

Keep your ePTW. Add a reasoning layer.

Already operating an electronic Permit to Work system? PERMITA does not have to replace it. PERMITA can operate as an intelligence and analysis layer connected to your existing work-control environment.

Your ePTW continues to manage the permit workflow. PERMITA analyses the work context around it. Integration architecture is configured according to the operator's existing systems, available interfaces, and cybersecurity requirements.

EXISTING ePTW

Operational system of record where applicable. Permit workflow remains under operator control.

CONTROLLED DATA INTERFACE

API integration, approved data exchange, scheduled synchronisation, or operator-defined interface, subject to implementation scope.

PERMITA REASONING LAYER

Evaluates relationships across permits, equipment, isolations, work locations, facility topology, simultaneous activities, and workflow status.

TRACEABLE FINDINGS

Detected conditions, SIMOPS indicators, affected permits or activities, traversed paths, triggered rules, and natural-language explanations.

OPERATIONAL REVIEW / EXISTING WORKFLOW

Findings return to authorised personnel for review and action within the operator's existing process.

Subject to the operator's available data interfaces and implementation scope, PERMITA may analyse active permits, planned permits, permit type, work scope, equipment references, isolation references, work locations, facility topology, simultaneous activities, and workflow status.

CONFIGURABLE ePTW PLATFORM

Implementation model 1

Configure permit types, workflows, authority hierarchy, isolation philosophy, forms, and facility topology around the operator's work-control requirements.

ePTW INTELLIGENCE LAYER

Implementation model 2

Retain the existing ePTW and connect relevant work-control data to PERMITA for graph-based relationship analysis and traceable findings.

The safety case

"The model doesn't reason. The system reasons. The model speaks."

— Engineering Reasoning Model (ERM), AIMAILABS

PERMITA keeps work-control decisions grounded in explicit rules and traceable relationships. Deterministic logic identifies the condition and exposes the conflict path. The language model explains the result in clear operational language. AI does not approve permits or independently change workflow states.

Deployment & adoption

Configured for your PTW procedure. Built for controlled rollout.

PERMITA deploys single-tenant — on-premises or in your private cloud — and provides a configurable platform architecture for your PTW procedure, authority matrix, isolation philosophy, permit taxonomy, and facility topology. The goal is to fit the operator's workflow, not replace it with a generic form layer.

STEP 1

Procedure mapping

Your PTW procedure and hardcopy forms become the configuration layer: permit types, approval DAG, validity and revalidation rules, required fields, and authority hierarchy.

STEP 2

Topology load

Plant areas, adjacencies, key systems, and isolation points loaded into the graph from existing registers and P&ID data.

STEP 3

Parallel-run pilot

One asset runs PERMITA alongside the paper system. Every conflict the engine finds that the board missed is logged — your evidence file for full cutover.

STEP 4

Cutover & support

Electronic permits go primary with an agreed paper fallback protocol, audit trail live, and platform-local support arrangements in place.

Design-partner program

Run it against your permit history.

Send us a redacted month of closed permits and your PTW procedure. We'll load them into the graph and show you every conflict chain the manual review missed — before you commit to anything.

AIMAILABS Sdn Bhd · Malaysia · APAC · Anthropic Registered Partner