Oil & Gas

Manages the fiscal measurement asset base and the proving cycle at pipeline receipt and delivery points, terminals and truck racks, with meters, provers and flow computers held in IFS Cloud as Serial and Equipment Objects. Proving is scheduled as PM Actions driven by contract terms, elapsed time and throughput, and each proving Work Order records meter factor and repeatability Measurements against the applicable API MPMS Chapter 4 criteria. Out-of-tolerance results trigger repeat runs, a Fault Report and, where the shift cannot be resolved, removal of the meter from custody transfer service.

Manages the end-to-end integrity management programme for midstream transmission pipelines in IFS Cloud, from registering pipeline segments as Linear Assets with High Consequence Area coverage through threat and risk assessment, baseline and reassessment planning, and remediation scheduling. Assessment cycles are held as Maintenance Plans / PM Actions so that the regulator-mandated five-year (not to exceed 68 month) reassessment intervals generate Work Orders automatically. Anomaly evaluation outcomes drive prioritised remediation Work Orders against the immediate, 60-day and 180-day condition categories.

Covers cleaning pig runs and smart-tool in-line inspection campaigns on midstream transmission pipelines, executed in IFS Cloud as Maintenance Events and Work Orders against the pipeline Linear Asset and its launcher and receiver Functional Objects. ILI vendor results are loaded as anomaly measurements positioned along the line, then classified against the regulatory immediate, 60-day and 180-day condition criteria. Verification digs are raised as Work Orders and their field measurements are fed back to validate reported tool tolerance.

Runs the external corrosion control programme for buried transmission pipelines and terminal assets in IFS Cloud, registering rectifiers, anode beds, test stations and bonds as Functional and Equipment Objects on the pipeline Linear Asset. Regulator-mandated inspection frequencies are held as PM Actions - rectifier checks six times a calendar year at intervals not exceeding two and a half months, and annual protected-pipeline testing at intervals not exceeding fifteen months. Pipe-to-soil potentials are captured as Measurements against the NACE SP0169 criteria and readings outside criterion raise Fault Reports and corrective Work Orders.

Executes the frozen turnaround scope in IFS Cloud through Work Orders and Work Tasks organised into discipline work packs. Each Work Order is prepared, material-kitted and resource-loaded before being released, then executed under permit-to-work with daily progress and punch-list control. IFS Cloud Work Task statuses from Under Preparation through Prepared, Released, Work Started, Work Done, Reported and Finished give the shutdown its execution spine.

Structures recurring wellsite and facility operator rounds in IFS Cloud as route-based Maintenance Plans that generate scheduled inspection Work Orders with a defined checkpoint list per Functional Object. Field operators execute the round on mobile, recording readings as Measurements and observations against each object. Out-of-limit readings raise Fault Reports that seed follow-up corrective Work Orders, giving a defensible inspection record for HSE and regulatory audit.

Manages the run life, performance and maintenance of artificial lift systems - ESP, rod pump, gas lift and PCP - by holding each lift unit as a Serial Object in IFS Cloud with full installation and pull history. Operating measurements such as motor load, intake pressure and pump fillage are captured as Measurements and evaluated against the optimisation envelope. Underperformance triggers an optimisation change or a pull-and-replace Work Order, with failure data recorded to an ISO 14224-aligned taxonomy so run-life trends drive the next maintenance strategy revision.

Delivers the preventive and corrective maintenance regime for gas compressors, process pumps, turbines and drivers held as Serial and Equipment Objects in IFS Cloud. Criticality and a risk-based maintenance strategy drive Maintenance Plans on both calendar and running-hour triggers, with task templates, spare parts and permit requirements pre-loaded onto the Work Order. Executed work is closed out with failure and maintenance data recorded to an ISO 14224-aligned taxonomy so reliability history can revise PM intervals.

Manages in-service and out-of-service inspection of aboveground storage tanks at terminals and breakout tank farms in IFS Cloud, with each tank registered as a Functional Object carrying its API 653 inspection scope - foundation, bottom, shell, structure, roof, appurtenances and nozzles to the first flange. Routine, formal external and internal inspection cycles are held as PM Actions with the interval driven by measured corrosion rate. Ultrasonic thickness Measurements feed remaining-life calculation, which either sets the next interval or drives repair, alteration or removal of the tank from service.

Delivers the mechanical integrity inspection programme for pressure vessels, associated process piping and pressure relief devices at pump stations, compressor stations and terminals, held in IFS Cloud as Equipment and Serial Objects with design and set-pressure attributes. Inspection intervals are configured as PM Actions bounded by the API 510 and API 570 ceilings, and relief device shop test and overhaul cycles follow the API 520 Part II maximum interval. Thickness Measurements at condition monitoring locations drive remaining-life evaluation, rerating, repair or removal of the item from service.

Manages the lifecycle integrity of producing, injection and suspended wells by representing wells and their barrier elements in the IFS Cloud asset structure and driving periodic barrier verification through Maintenance Plans and Work Orders. Annulus pressure, subsurface safety valve tests and barrier element inspections are captured as Measurements against the well object, evaluated against defined limits, and exceptions raised as Fault Reports. Degraded barriers escalate to remedial Work Orders or a controlled shut-in, with the full evidence trail retained in IFS Document Management.

Establishes condition-based maintenance across production-critical assets by defining condition parameters in IFS Cloud, ingesting vibration, temperature, oil analysis and process data from CBM and SCADA sources as Measurements, and evaluating them against alarm limits. Limit breaches and adverse trends automatically generate condition-based Work Orders ahead of functional failure. Executed interventions are reviewed against the original prediction so alarm limits and models are tuned, moving the fleet from calendar-based PM toward evidence-driven intervention.

Plans a refinery, gas plant or offshore turnaround (TA) in IFS Cloud from scope call-off through to a hard scope freeze and baselined schedule. The turnaround is registered as a Maintenance Event that drives PM Action generation, and mirrored as a Project with a WBS of Project Activities for cost, schedule and progress control. Scope candidates are drawn from due PM Actions, deferred Work Orders, Fault Reports and inspection recommendations, then challenged, ranked and frozen against the Functional Object hierarchy.

Runs a risk-based inspection programme for fixed equipment and piping using API RP 580 and API RP 581 methodology, where risk is assessed as the product of probability of failure and consequence of failure and used to prioritise and schedule inspection. IFS Cloud carries the resulting inspection plan as PM Actions and Work Orders against the Functional Objects, with condition data captured as Measurements and integrity operating window excursions raised as Fault Reports. The RBI analysis itself, including corrosion loops and damage mechanism registers, has no standard IFS Cloud object and is normally held in a specialist integrity data management system.

Establishes the maintenance strategy for oil and gas assets using RCM as defined by SAE JA1011 and JA1012, supported by FMECA to the MIL-STD-1629A method for criticality ranking. The resulting task selection is loaded into IFS Cloud as revision-controlled PM Actions and maintenance plans against Functional Objects, and the failure data captured on Work Orders and Fault Reports is coded to the ISO 14224 taxonomy so the strategy can be reviewed on evidence. The FMECA worksheet itself has no standard IFS Cloud object.

Closes the monthly production cycle by validating metered volumes at well, battery and custody transfer points, running the allocation model that distributes measured sales volumes back to wells and joint venture partners, and reconciling allocated against custody transfer quantities. Validated volumes and values are posted into IFS Cloud Financials for revenue, royalty and partner billing, with the reporting pack issued to regulators and partners before the period is locked. The allocation engine itself sits outside IFS; IFS holds the meter and equipment master, the resulting financial postings and the reporting evidence.

Runs the leak detection and repair programme that keeps fugitive methane and VOC emissions inside permitted limits. In IFS Cloud each monitorable component is tagged as a Functional Object, survey rounds are driven by Maintenance Plans and PM Actions, screening values are captured as Measurements and every exceedance raises a repair Work Order with a re-monitoring check. The LDAR survey record itself has no standard IFS object and is retained as a controlled Document.

Manages the recurring statutory submissions an oil and gas operator owes its regulators - greenhouse gas and emissions returns, offshore safety performance measures, incident and dangerous occurrence reports. In IFS Cloud the obligation register is held as controlled Documents, each submission is scheduled so preparation work is generated ahead of the deadline, and the reported figures are traced back to Measurements, Work Orders and incident records. Submission itself remains an external electronic filing.

Governs how intrusive work on oil and gas facilities is authorised and how hazardous energy is isolated, verified and restored. In IFS Cloud the permit is anchored to the Work Order and Work Task for a Functional Object, so no execution is reported without a valid authorisation and a recorded zero-energy check. Permit and isolation certificates are held as controlled Document records because IFS Cloud has no standard permit-to-work object.

Keeps the safety and environmental critical elements that prevent loss of containment demonstrably fit for purpose. In IFS Cloud the barriers are Functional Objects carrying a Criticality classification, their performance standards become Maintenance Plans and PM Actions, and proof-test outcomes are captured as Measurements. Impairments are managed as controlled deviations and performance is reported against the API RP 754 tiered indicator framework.

Captures, investigates and closes out HSE incidents and near misses across oil and gas operations, and drives the statutory notifications that follow. IFS Cloud Health and Safety supports incident registration, investigation assignment, cause analysis with a calculated risk value, corrective action tasks and a closure questionnaire. Regulator notification timers and reportability rules are configured per jurisdiction because BSEE and HSE impose different windows and forms.

Identifies, stocks and procures the critical and long-lead spares that protect turnaround delivery and production availability in oil and gas. Criticality-ranked Inventory Parts are given deliberate stocking policies, then replenished through IFS Cloud Purchase Requisitions that are released, authorised and converted into Purchase Orders or called off against Supplier Agreements. Delivery of long-lead items is expedited and reserved against the turnaround Work Orders that depend on them.

Runs stock at wellpads, camps, supply bases and offshore installations where resupply is slow, expensive and weather-dependent. IFS Cloud supports this directly through the Remote Warehouse model, where shipment orders with receiver type Remote Warehouse resolve their default receive case and locations from the Warehouse Navigator Remote Warehouse tab. Receipt, inspection, serial and lot tracking and move into stock then follow the standard IFS Cloud arrival and receipt flow.

Plans and controls the movement of people and freight to and from offshore installations and remote sites against a hard bed limit. In IFS Cloud each mobilisation is traced back to the Work Order or Project that justifies the trip, eligibility is gated on Employee competency and certificate validity, and material moving on the same voyage is planned through Shipment records. The POB manifest itself has no standard IFS object and is held as a Document or in a specialist logistics system.

Controls changes to process chemicals, technology, equipment, procedures and facilities affecting a covered process, as required by OSHA PSM 29 CFR 1910.119(l), with replacements in kind excluded. Each change is screened, assessed for technical basis and safety and health impact, authorised, implemented and closed out only after process safety information, operating procedures and training have been updated and a pre-startup safety review is complete. IFS Cloud has no standard MOC record object, so the change itself is normally held in a dedicated MOC system while the physical work runs as IFS Cloud Work Orders and the updated documents are controlled in Document Management.

Manages the contractor lifecycle for oil and gas maintenance and turnaround work in IFS Cloud, from scope packaging and prequalification through Supplier Agreement award, competency verification, mobilisation, task allocation and demobilisation. OSHA PSM requires the operator to obtain and evaluate contractor safety performance, inform contractors of process hazards, control their entry and presence, periodically evaluate their performance and maintain a contract employee injury and illness log. IFS Cloud carries this through Supplier, Supplier Agreement, Purchase Order, Employee, Competency and Work Task objects.