Service · Software development

Custom oil and gas software development.

Custom software for oil and gas organisations — from offshore field-services apps and Permit-to-Work flows to HSE incident management, Asset Integrity tracking and compliance reporting under NORSOK, API and IEC 61511. We don't replace your SAP, AVEVA, Maximo or OSIsoft PI, but build targeted applications around them.

HSE & PTWSIL/ATEX zonesOffshore offlinePI & AVEVA integration

Software for the oil and gas industry is rarely found in a single package.

An operator, service company or engineering firm in oil and gas runs on a dense stack of enterprise systems — SAP S/4HANA for finance and supply, AVEVA or Maximo for Asset Performance Management, OSIsoft PI or AVEVA PI for process data, Petrel or IHS for subsurface, IFS for asset-heavy operations, Honeywell PHD for process safety. For onshore, offshore, midstream and downstream environments, that layer works well.

We don't replace those platforms. We're brought in for the layer around or on top of them: a Permit-to-Work system tailored to your own safety procedures, an offshore field-services app that works offline on a platform, an HSE incident flow that feeds straight into Health, Safety and Environment reporting, or a compliance module that generates the right NORSOK, API or DNV reports in a single click. For the broader context of what we do in enterprise software development, see our main page.

The target group is broad: upstream operators such as Wintershall Noordzee and international majors, service companies in well services, subsea and heavy lift, midstream parties around pipelines and LNG terminals, downstream refineries and petrochemicals, plus engineering firms and decommissioning specialists. The system landscape differs for each of these roles, but the pattern is the same: a dense enterprise layer surrounded by work processes that are hard to squeeze into standard packages. That's where we come in.

At the same time, the whole industry is moving towards the energy transition: CCUS projects, hydrogen pilots, biofuel blends, hybrid installations on existing sites. These new data fields and KPIs aren't yet built into packages such as SAP, AVEVA, Maximo and OSIsoft PI, yet operators still have to measure and report them and show them to the auditor. A lightweight custom layer on top of your existing system is then often more practical than waiting for your enterprise vendor to release a module for it.

Three patterns we build in oil and gas.

Custom software for oil and gas is a broad field. We're usually brought in for three types of projects, and most assignments combine two of them.

Operational safety project · fixed sprint budget

HSE, Permit-to-Work and shift handover

An integrated layer for Health, Safety & Environment incidents, Permit-to-Work (PTW), Lock-Out/Tag-Out (LOTO) and structured shift handover. Incident reports from the shop floor or the platform via mobile, automatic routing to the HSE coordinator, root-cause analysis, CAPA registration and an integration with your existing safety procedure library. A PTW flow with isolation checks, a risk assessment per zone and electronic sign-off by the issuing and performing authority.

The shift handover module connects to this: at the end of a shift, operators record in a structured way what is running, which deviations are in progress, which permits are open and which points need attention from the next shift, directly linked to PTW, incidents and current work orders. This shortens the handover and meets the OpEx requirements that both onshore refineries and offshore platforms apply under ISO 45001 and the company's own Safety Management System.

HSE incident managementPermit-to-WorkLOTOShift handoverCAPAProcedure library
Asset and inspection project · fixed sprint budget

Asset integrity, inspection and predictive maintenance

For rotating equipment (turbines, compressors, pumps) and static assets such as vessels, pipelines and pressure systems. An asset hierarchy in line with ISO 55000, an inspection flow based on API 510/570/653, condition monitoring via OSIsoft PI or AVEVA PI, and predictive models that pick up signals before a threshold is exceeded. For the wider maintenance side, we often work alongside or on top of an existing CMMS (maintenance management system).

The inspection flow itself is a separate sub-module: risk-based inspection planning per asset class, recording forms with thickness readings, corrosion mapping, NDT results and weld defects, plus automatic report generation for the verifier or regulator. SIL- and ATEX-zoned equipment gets its own flow with the associated risk assessment and calibration history. The integration with process data via PI or AVEVA is one-way when your security architecture requires it.

Asset Integrity ManagementAPI 510/570/653PI/AVEVA integrationPredictive maintenanceSIL/ATEX inspectionISO 55000
Field services and compliance project · fixed sprint budget

Offshore field services, compliance and the energy transition

A field app for inspectors and engineers on offshore platforms, pipelines or decommissioning sites. It works fully offline and syncs via satellite as soon as the connection returns. Compliance reporting under NORSOK, DNV, ATEX and IEC 61511 in one consolidated flow, plus tracking modules for CCUS, hydrogen and biofuel projects, where the energy transition calls for new data fields that existing oil and gas packages don't yet cover.

For decommissioning projects, such as North Sea islands being returned to the seabed, we often build a separate project module that keeps phasing, plug and abandonment, material tracking, recovery and environmental reporting in one place. For energy transition portfolios, we deliver a dashboard that measures CO₂ emissions, captured volumes and hydrogen purity per stream alongside your existing oil and gas data. It is fed from the same PI or AVEVA layer where your process data already arrives, so you keep a single source of truth.

Offshore appOffline modeSatellite syncNORSOK/DNV reportingCCUS & hydrogenDecommissioning

What you have at the end.

Working oil and gas software in production, plus everything around it so you can manage, audit and extend it yourself within the applicable standards.

  • Production and staging environmentsTwo separate environments in your own cloud (GCP, AWS, Azure) or in a dedicated EU tenant with us, with zone segmentation between office, business and process IT as your security architecture requires.
  • Web and offshore appA browser application for the office and operations centre, plus a mobile field app for offshore platforms, pipeline inspection and decommissioning sites, with full offline mode and satellite sync.
  • Full codebase and documentationSource code, build instructions, an architecture overview, an integration map covering SAP, AVEVA, Maximo, OSIsoft PI and Petrel, plus mappings for every integration. No vendor lock-in.
  • Compliance packageAudit trails, electronic signatures in line with IEC 61511 and API standards, a NORSOK and DNV report generator, plus a validation file you can hand to your own auditor or regulator.
  • Training and knowledge transferSessions for key users (HSE coordinators, inspection leads, planners, IT administrators), plus short video tutorials for operators offshore and in the field. An incident response runbook for your IT team.
  • Management contract (optional)Monitoring, backups, security patches and ongoing development for a fixed monthly fee. Suitable for 24/7 operations, with agreed response-time levels for mission-critical components.

When custom software pays off in oil and gas.

Four patterns where an off-the-shelf package gets stuck and targeted software adds value, based on projects we encounter in operator, service and engineering contexts.

Compliance density

Stacked standards need their own flow

NORSOK, API 510/570/653, IEC 61511 for functional safety, ATEX and SIL for explosion safety, ISO 55000 for asset management, ISO 45001 for HSE and ISO 14001 for the environment: in oil and gas, these standards often apply together to a single project. Standard modules in SAP or Maximo cover parts of this, but the specific combination for your site and region calls for a dedicated, custom reporting and audit flow.

Remote operations

Offshore and remote work

Offshore platforms in the North Sea, pipelines running through remote areas and offshore decommissioning sites have only limited connectivity, often just via satellite. A field app has to keep working fully offline there, build up data locally and sync consistently the moment a connection is available. Standard SaaS packages assume always-on connectivity and fail in these conditions.

OT and explosion safety

Getting SIL and ATEX zones on board

When inspection or work processes run through SIL-certified and ATEX-zoned areas (zone 0, 1 or 2), strict requirements apply to both the hardware (intrinsically safe) and the software flow. PTW procedures have to factor in zonal risk assessments, and signal paths from the process safety system (Honeywell PHD, AVEVA) must be handled cleanly, often through unidirectional flow architectures that respect security zones.

Energy transition

From pure oil and gas to a hybrid energy mix

Operators and service companies are in the midst of the transition to CCUS, hydrogen, biofuel and hybrid installations. Existing oil and gas packages do not yet track these data fields, KPIs and reporting requirements. Custom modules that connect to your existing PI, AVEVA or Maximo layer can measure and report on the transition portfolio without you having to wait for a replacement platform.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Modules that appear in almost every oil and gas project.

The building blocks we draw on. The combination and depth differ per organisation and per asset portfolio, but these elements come up again and again.

Security

HSE and incident management

A mobile HSE flow for reporting near-misses, incidents and environmental events, with direct routing to the coordinator and management. It includes root-cause analysis, CAPA registration and a reporting layer that aligns with ISO 45001, ISO 14001 and your own Safety Management System, for both onshore refineries and offshore platforms.

Work permits

Permit-to-Work and LOTO

An end-to-end PTW system covering the request, risk assessment per zone (including SIL/ATEX), isolation checks, Lock-Out/Tag-Out registration and sign-off between issuing and performing authority. It is linked to the asset hierarchy and to the live process safety status from Honeywell PHD or AVEVA System Platform.

Inspection

Risk-based inspection and NDT

Risk-based inspection planning per asset class, with recording forms for thickness readings, corrosion mapping and NDT results on tablet or handheld. Reports are generated automatically in line with API 510 (vessels), API 570 (piping) and API 653 (storage tanks), with an audit trail for the verifier, DNV or regulator.

Field services

Offshore app with offline mode

A field app for inspectors, operators and maintenance engineers on platforms, pipelines and decommissioning sites. It works fully offline with a local data model, conflict resolution and version management, syncing via satellite, 4G/5G or on return to the quayside.

Process data

OSIsoft PI and AVEVA PI integration

Time series are read from PI or AVEVA PI via the PI Web API or a gateway to TimescaleDB or InfluxDB, for analytics, dashboards and predictive maintenance models running on a derived stream. The integration respects the zoning between process IT, business IT and office IT.

Security architecture

Unidirectional flow between zones

When your security architecture requires one-way traffic between high-security process zones and lower-security business or office zones, we design the software flow around it. Typically this means a unidirectional gateway or data diode on the network side, with only low-pull integrations on the software side and strict audit trails of everything that passes through.

Compliance

NORSOK, DNV and API reporting

A single consolidated reporting layer that serves NORSOK, DNV, API 510/570/653, IEC 61511, ATEX zoning, ISO 55000 and ISO 45001 from the same data set. It includes electronic signatures where the standard requires them and a validation dossier you can hand to your own auditor or regulator.

Energy transition

CCUS, hydrogen and biofuel tracking

Tracking and reporting modules for CO₂ emissions, captured volumes, hydrogen purity and biofuel blends, fed from the same PI or AVEVA layer that already receives your oil and gas process data. One source of truth for both the traditional portfolio and the transition pilots.

How an oil and gas project works.

1

Introduction

A conversation in which we establish what bottleneck you face on the installation or in operations, which enterprise systems you run (SAP, AVEVA, Maximo, OSIsoft PI, Petrel) and which standards and compliance stack apply to your site.

2

Process, system and compliance analysis

We model your operational flow with HSE, inspection and field services. That means interviews with operators, inspection leads and HSE coordinators, plus a systematic review of your integration landscape and the applicable standards. The result: a scope document, a plan and a first screen flow.

3

Building in sprints

Working builds every two weeks, ready to test at a pilot site. For offshore apps we test offline mode and satellite sync early, and for PTW and HSE flows we join you in the field. Direct feedback from your operations, immediate adjustments.

4

Rollout, validation and management

A phased rollout per site or asset group, a validation package for your auditor, training sessions onshore and offshore, plus ongoing management for security patches, further development and expansion towards energy transition modules.

Frequently asked questions.

What clients in operator, service and engineering contexts usually want to know before we start.

Will you replace our SAP, AVEVA, Maximo or OSIsoft PI?
No, and we are explicit about that. There is no point in rebuilding working implementations of SAP S/4HANA, AVEVA, Maximo Oil & Gas, IFS, Honeywell PHD or OSIsoft/AVEVA PI. We build the custom layer around them (HSE flow, Permit-to-Work, field services, inspection portal, compliance reporting) and integrate via the standard APIs and data flows of your existing platforms.
Does the offshore app really work offline on a platform or pipeline?
Yes. The field app keeps a local data model and lets inspectors and technicians carry out their checks, photos, measurements and sign-offs completely offline. It then synchronises as soon as there is a connection again, via satellite, 4G/5G or on returning to site. Conflict resolution and version management are included as standard.
How do you handle PI System integration and process data?
We read time series from OSIsoft PI and AVEVA PI via the standard PI Web API or via a gateway to our own time-series database (often TimescaleDB or InfluxDB) for analyses and dashboards. For predictive maintenance models we work on a derived stream, so we don't put unnecessary load on the PI server. The integration respects the security zoning between process IT and business IT.
Can you handle SIL, ATEX and NORSOK requirements?
Our software layer is generally not part of a SIL-certified safety loop itself, but it does sit around it: PTW flows, inspection procedures, sign-off trails and reporting under NORSOK, API 510/570/653, IEC 61511, ATEX and DNV. We document explicitly which functions run in which zone (office, business, process) and, where needed, use unidirectional flow architectures to shield high-security areas.
How relevant is this for the energy transition: CCUS, hydrogen, biofuel?
Very relevant. Many operators and service companies now run a hybrid portfolio, and their existing oil and gas packages do not yet track CCUS, hydrogen or biofuel data in a structured way. We build tracking and reporting modules on top of your existing PI, AVEVA or Maximo layer, so the transition portfolio is included in HSE, asset integrity and compliance reporting.
What determines the cost of a project like this?
The breadth of scope (a single module or a connected set), the number and complexity of integrations (SAP, AVEVA, Maximo, OSIsoft PI, Petrel), the compliance domain you need to cover, whether offshore offline capability is required, and the size of the rollout in sites or assets. We work in fixed sprints with a transparent budget per sprint, so scope and costs grow under your control.

Talk to us about your oil and gas software.

A no-obligation introductory call of half an hour. We listen to your operations flow, ask follow-up questions on compliance and integrations, and give you direction you can actually use, even if custom software turns out not to be the answer. For the broader context of where this type of project fits, see our page on manufacturing software, our work on an MES system or our API integration practice.

A complementary angle on this topic can be found on applatenmaken.com: Building back-office software for oil and gas.

For tanker drivers, with the route per compartment and a digital delivery note, there is our tanker planning app for fuel delivery.

Edit content