Enterprise platforms · Oil and gas
Asset integrity and inspection management system
We build custom asset integrity and inspection management systems for oil and gas operators: an equipment register, risk-based inspection planning, corrosion and thickness monitoring, anomaly and repair tracking, and management of safety-critical elements. It connects to your maintenance and engineering systems so inspection findings turn into planned work, 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
Equipment and tag register
A hierarchy of facilities, systems, equipment, piping circuits and components with design data, materials and service conditions, aligned with the maintenance system. - 02
Risk-based inspection
Likelihood and consequence of failure by damage mechanism, with risk rankings that set inspection scope and interval for each item. - 03
Inspection planning and scheduling
Inspection tasks by method and due date, packaged into work scopes for shutdowns and routine campaigns, with status and backlog. - 04
Thickness and corrosion monitoring
Thickness readings at monitoring locations, corrosion rates, remaining life and the next inspection date calculated from the trend. - 05
Inspection results and reports
Findings captured in the field with photos and measurements, reviewed by an engineer and stored against the item inspected. - 06
Anomalies and repairs
A register of defects and anomalies with assessment, disposition, repair or monitoring decision, due dates and closure. - 07
Safety-critical elements and barriers
Performance standards for safety-critical equipment, assurance tests and verification results, with the status of barriers visible to operations. - 08
Integrity operating windows
Limits on temperature, pressure, chemistry and flow that protect equipment, with excursions recorded and linked to inspection planning. - 09
Management of change and reporting
Links to change management, regulator and internal reporting, and dashboards of integrity status by asset and system.
Reference architecture.
Standards and interfaces
What we design against.
- API 580 and API 581
- Risk-based inspection practice and the quantitative methodology for ranking equipment and setting inspection plans.
- API 510, 570 and 653
- Inspection codes for pressure vessels, piping and storage tanks, which define inspection types, intervals and repair rules.
- ISO 55000
- Asset management systems standard, as the framework for policy, objectives and performance review.
- ISO 14224
- Collection of reliability and maintenance data for equipment, used for taxonomy and failure coding.
- Safety case and barrier management practice
- Regulatory and industry guidance on safety-critical elements, performance standards and verification.
- Maintenance system interfaces
- Interfaces to the maintenance and engineering systems so inspection output becomes work.
Data model
The core entities.
- Equipment and component
- Tag, type, design conditions, material, installation date and position in the hierarchy.
- Damage mechanism and risk
- Mechanism, likelihood, consequence, risk rank, assessment date and assumptions.
- Inspection task and result
- Method, scope, due and done dates, inspector, findings and attachments.
- Thickness reading
- Location, date, value, instrument, corrosion rate and remaining life estimate.
- Anomaly
- Description, assessment, disposition, repair or monitoring plan, due date and closure.
- Safety-critical element and test
- Performance standard, assurance task, result and barrier status.
- Operating window excursion
- Parameter, limit, duration, assessment and the inspection actions triggered.
When custom development is the right call.
Controls designed in, not added later.
Engineering review
Risk assessments, remaining life estimates and dispositions are reviewed and approved by named engineers.Controlled change
Changes to equipment data, inspection intervals and performance standards need an approver and a reason.One-way process data
Process data is read from the operational side only.Evidence retention
Inspection reports and assurance records are retained for the life of the asset and beyond, with tamper-evident storage.Offline field capture
Inspectors record readings offline and synchronise later without losing data.
From discovery to a system you run.
- 01
Integrity process review
We review the inspection process, codes in force, current registers and the data held with integrity, inspection and maintenance teams. - 02
Data and method design
Equipment hierarchy, risk methods, monitoring locations and interfaces to maintenance are agreed. - 03
Build and load one facility
One facility's register, inspection history and thickness data are loaded and checked against existing reports. - 04
Pilot an inspection campaign
A campaign runs through the system, from plan through field capture to results and anomalies. - 05
Roll out and extend
More facilities and the barrier and operating window modules are added, with dashboards for management.
Relevant work
Where to see our work.
Common questions.
- Does this replace our maintenance system?
- No. The maintenance system keeps work orders and the equipment master. The integrity system adds risk, inspection and anomaly management and sends work to maintenance.
- How is remaining life calculated?
- From thickness readings over time at each monitoring location, using the corrosion rate method your engineers specify, with the result reviewed by an engineer before it changes an inspection interval.
- Can inspectors work offline?
- Yes. Readings, photos and findings are captured offline on a tablet and synchronised, with conflicts shown for review.
- Does it support safety-critical elements?
- Yes. Performance standards, assurance tasks and results are tracked, and the status of barriers is visible to operations as well as to the integrity team.
- Who owns the code and the data?
- You do. The code, the methods and the data stay yours.