Enterprise platforms · Oil and gas
Permit to work and HSE management system
We build custom permit to work and HSE management systems for oil and gas operations: electronic permits with isolations and gas tests, simultaneous operations checks, shift handover, incident and near-miss reporting, investigation and action tracking, and safety performance indicators. The system enforces the sequence a safe job requires, and you own the code.
Requirements spec · Oil and gas
Upstream operations system requirements
A requirements specification you can adapt for an upstream production management or surveillance system: master data, acquisition, allocation, deferment, exceptions, reporting and the IT and OT boundary.- 01Eight requirement areas written as testable statements.
- 02Questions on data sources, quality flags and restatement rules.
- 03The IT and OT boundary items security teams ask about.
- 04Seven questions to put to any vendor or development partner.
Free download
Get it on screen in a few seconds.
What the system does, module by module.
- 01
Work request and job hazard analysis
Work requests with a task description, location, equipment and hazards, and a structured job hazard analysis attached to the permit. - 02
Electronic permits
Permit types such as hot work, confined space, working at height and electrical, each with its own steps, roles and validity rules. - 03
Isolations and lock-out
Isolation plans and certificates linked to the equipment, with a record of every point isolated, verified and returned. - 04
Gas testing and conditions
Gas test results and the conditions required before and during the work, with permit suspension when a reading goes out of limits. - 05
Simultaneous operations
A matrix and map of active permits that flags conflicting work in the same area, with escalation before it starts. - 06
Competency and authority
Checks that issuers, approvers and workers hold the training and authority the permit type needs, with expiry alerts. - 07
Shift handover
Open permits, isolations and outstanding actions presented at handover, with acknowledgement by the incoming team. - 08
Incident and near-miss reporting
Fast reporting from the field with photos, a classification of severity and potential, and notifications to the right people. - 09
Investigation, actions and indicators
Root cause analysis, corrective actions with owners and due dates, and safety performance indicators reported by site and period.
Reference architecture.
Standards and interfaces
What we design against.
- UK HSE guidance on permit-to-work systems (HSG250)
- Widely used guidance on the principles and practice of permit-to-work systems, used as a benchmark in many regions.
- ISO 45001
- Occupational health and safety management systems, as the framework for objectives, audits and review.
- API RP 754 and IOGP safety performance indicators
- Process safety and personal safety indicator definitions that the reports follow.
- IOGP Life-Saving Rules
- A common set of rules for high-risk activities that permit types and checks can be aligned with.
- ATEX and IECEx
- Requirements for equipment used in hazardous areas, which apply to the tablets and devices used in the field.
- Regulator incident reporting
- National rules on reportable incidents, content and timing, generated from the incident record.
Data model
The core entities.
- Work request
- Description, location, equipment, hazards, requester and linked work order.
- Permit
- Type, status, validity, issuer, approver, workers, conditions and extensions.
- Isolation
- Plan, points, lock and tag identifiers, verification and return.
- Gas test and condition
- Reading, instrument, time, limits and the permit action taken.
- Competency record
- Person, training, authority, issue and expiry dates.
- Incident and investigation
- Event, severity, potential, causes, findings and linked actions.
- Action
- Description, owner, due date, status and the evidence of closure.
When custom development is the right call.
Controls designed in, not added later.
Enforced sequence
The system will not issue a permit until the required checks are complete, and it suspends a permit when conditions fail.Role and competency enforcement
Only people with valid authority can issue, approve or work under a permit type.Offline resilience
Permits and isolations remain available at the site during connection loss, with a defined fallback to paper and later reconciliation.Tamper-evident record
Every step, signature and change is recorded with user and time, and retained for the period regulations require.Hazardous-area devices
Field clients run on rated devices managed under your device policy.
From discovery to a system you run.
- 01
Permit process review
We observe how permits, isolations and handovers work at a site and list the permit types, forms and sign-offs in use. - 02
Process and rule design
Permit flows, isolation rules, competency checks and SIMOPS logic are agreed with operations, HSE and maintenance. - 03
Build and pilot at one site
The core permit types and isolations go live at one site, with paper as a fallback. - 04
Add handover, incidents and actions
Handover, incident reporting and action tracking are added, with safety indicators generated from the data. - 05
Roll out across sites
Remaining sites and permit types follow, with feedback from supervisors shaping each release.
Relevant work
Where to see our work.
Common questions.
- Does an electronic permit system make work safer?
- It makes the checks consistent and visible. It cannot replace supervision and judgement, but it stops a permit being issued with a step missing and shows conflicts between jobs before they start.
- What happens if the network is down at the site?
- Permits and isolations are available offline on site devices. A defined fallback applies if devices fail, and records are reconciled when the link returns.
- Can the system link to our maintenance system?
- Yes. Work orders create work requests, and permit status flows back so planners and crews see the same position.
- How are safety indicators produced?
- From the incident and permit data with definitions agreed in design, so reports to management and regulators come from the same records.
- Who owns the code and the data?
- You do. The code, the permit definitions and the data stay yours.