SmartLink
Energy

Oil and gas ERP in Pakistan: cost, timelines and maintenance evidence

Oil and gas ERP in Pakistan is bought for the maintenance and asset side far more often than for the ledger, because that is where the consequence sits. SmartLink Services works from Karachi on asset registers, work order management, critical spares and contractor control for energy operations. This page sets out the three things an engineering manager asks before a business case is written: what published market rates put on the work, how long a rollout runs when the plant only stops on its own schedule, and what the record has to prove when an inspector, an insurer or an incident review asks. Figures below are market ranges rather than our quotation.

Discuss your systems
Core
Asset and maintenance
Controlled
Permits and contractors
Evidence
Inspection records
Spares
Criticality based
Overview

In asset heavy operations, the record is part of the safety case

When an asset fails in this sector the cost is rarely just the repair. Downtime, environmental exposure and safety consequence dominate, which is why maintenance and inspection records are not administration, they are part of the safety case.

The systems work follows from that. Asset registers have to reflect the plant as it is, with hierarchy and criticality that mean something. Preventive maintenance has to be scheduled and evidenced. Inspection findings have to lead to work orders rather than sitting in a report nobody actioned.

Contractor and permit control is the other recurring theme. Knowing who is on site, under which permit, with which certification current, is a question that has to be answerable immediately rather than reconstructed afterwards.

The work

Where oil and gas systems break

Drawn from the problems that come up repeatedly in this sector rather than from a generic capability list.

Where it usually hurts

  • Asset registers that no longer match the plant
  • Preventive maintenance planned but not evidenced
  • Inspection findings recorded in reports that generate no work order
  • Critical spares either missing or heavily overstocked
  • Contractor certification and permit status tracked on spreadsheets
  • Shutdown planning built from memory and personal knowledge

What the work covers

  • Asset register, hierarchy and criticality that reflect the plant as built
  • Preventive and predictive maintenance scheduling with evidence
  • Work order management from inspection finding through to close out
  • Critical spares planning based on criticality and lead time
  • Permit to work, contractor certification and site access tracking
  • Shutdown and turnaround planning with a documented scope

Typically involves

ERP EAM and CMMS Mobile apps SCADA integration
Discuss your systems
01

Why the asset register stops matching the plant

An asset register is usually accurate on the day it is loaded and drifting within a year. The reasons are ordinary. A pump is replaced with a different model because the original is obsolete. A temporary repair becomes permanent. A line is rerouted during a shutdown and the drawing is marked up but never reissued. None of those events has a clear owner in the system, so the record is updated by whoever happens to remember, which is a category of person no organisation should depend on.

Structurally the fix is to separate functional location from the equipment installed in it. A functional location is a position in the process and it stays stable for decades. Equipment is the serialised item currently occupying that position, and it moves. It goes to the workshop, gets refurbished, and comes back into a different bay. Registers that collapse the two lose maintenance history the moment a pump is swapped, and then reliability analysis becomes an argument about which records belong to which machine.

The second half is process. Where a modification cannot be closed out until the affected tags are updated, drift slows sharply, because the engineer who wants the paperwork finished has a reason to care. Add a field verification walk down for critical systems on a defined cycle, with the discrepancy list raised as work rather than filed. Neither step is technically difficult. Both are routinely skipped, and both are the difference between a register you can plan from and one you check by walking outside.

  • Functional location and equipment held separately, so history follows the right object
  • Register update as a mandatory step in management of change close out
  • Walk down verification on critical systems, with discrepancies raised as work
  • Tag numbering that matches the P&ID and the labels actually on the plant
  • Retired and temporarily installed equipment visible rather than quietly deleted
02

Criticality is a judgement about consequence

Criticality drives almost everything downstream. Maintenance frequency, inspection interval, spares policy, response time and escalation all hang off it. Yet in a great many registers it was set once, at data load, by somebody working from how often the equipment runs rather than what happens when it stops. The predictable result is a register where most items sit in the top class, which carries the same information as no classification at all and costs considerably more to maintain.

A defensible assessment scores consequence across safety, environment, production and cost as separate dimensions before combining them. Separation matters. A small pump whose failure releases hydrocarbon to atmosphere is a different problem from a large pump whose failure costs throughput, and blending them into one number hides the distinction that actually drives the maintenance strategy. Adopting the ISO 14224 taxonomy for equipment classes and failure data at load time is worth the effort, because it makes comparison and reliability analysis possible later.

Predictive work needs the same discipline applied to readings. Vibration, thermography and oil analysis produce values that mean nothing in isolation and a great deal against the same point measured last quarter. Where a historian or a condition monitoring package is already installed, the useful engagement is normally the interface rather than a replacement: land readings against the correct tag and route, hold the trend, and raise an exceedance as a work request that somebody owns instead of an email that somebody reads.

  • Consequence scored across safety, environment, production and cost rather than blended into one guess
  • ISO 14224 equipment taxonomy adopted at load time so failure data stays comparable
  • Criticality reviewed on a cycle with engineering and operations, not frozen at go live
  • Condition monitoring readings landed against tag and route, with exceedances raised as work
  • A documented maintenance strategy per criticality class, so the schedule can be defended
03

The inspection finding that never became a work order

Inspection is where this sector spends heavily and captures least. Reports arrive as documents. Findings live inside them as prose, sometimes as a table in an appendix, and the anomaly that mattered is read once by the person who commissioned the survey. Six months later somebody asks whether it was addressed and the answer requires reading the report again. That is not a technology limitation. It is a modelling failure, because the finding was never given an identity of its own.

Modelled properly, a finding is a record with a severity, a location tied to a real tag, a recommended action, a due date and a named owner. It generates work directly and it stays open until that work closes. Deferral has to be allowed, because deferral is a legitimate engineering decision, but it should require a named technical authority, record the justification and set a revised date. What must not happen is a due date sliding quietly because nobody was asked to approve the slide.

Code driven inspection adds a scheduling layer on top. API 570 for in service piping and API 653 for aboveground storage tanks derive intervals from measured condition and corrosion rate rather than from the calendar, so the system has to hold thickness readings, calculate remaining life and drive the next date from the calculation. Risk based approaches under API 580 change the interval logic again. Whichever applies, the evidence behind an interval has to be retrievable years afterwards without a search through folders.

  • Findings held as records with severity, owner and due date, not paragraphs inside a document
  • Work orders generated from findings, closed only when the work itself is closed
  • Deferral requiring a named technical authority, a justification and a revised date
  • Thickness readings and corrosion rates held so intervals are calculated rather than assumed
  • Temporary repairs on a register with review dates, because they outlive their intent
01

What asset and maintenance systems cost in Pakistan

Market pricing groups this work into three bands. The lowest, PKR 800,000 to 1,500,000 over two to three months, covers purchase, stores and accounting at a single location, which in energy usually describes a support office. Five to seven modules with a mobile application sit at PKR 1,500,000 to 3,000,000 across three to four months. Anything covering an operating asset with maintenance planning, spares and contractor control starts at PKR 3,000,000 and runs four to six months or longer. Energy operations sit in that top band because the asset register is the system, and one with fifteen thousand tagged items is not a configuration exercise.

Add on ranges give the shape. Manufacturing and plant functionality is quoted at PKR 300,000 to 600,000, multi location capability at PKR 200,000 to 500,000, accounting and finance at PKR 200,000 to 400,000, and a mobile application at PKR 400,000 to 800,000. Mobile is not optional here. A technician standing at a pump will not update a work order at a desk three hours later with any accuracy, and the data that follows is worse than none.

Two things push the number and neither is a licence. The asset register comes first: hierarchy, criticality and the tag numbering that everything else hangs on. We have loaded registers where the drawings showed equipment that had been removed in a previous turnaround and missed two skids installed since, and the reconciliation walk took longer than the configuration. Interfaces are the second. A process historian, a SCADA feed or a condition monitoring system each carries its own protocol, and the value is in agreeing what a reading means and who acts on it, which is a conversation with engineers rather than a piece of code. Treat all of the above as market pricing. A real figure follows discovery, once the tag count, the criticality method and the interface list are agreed.

  • Tagged asset count and hierarchy depth established before pricing
  • Mobile field capture quoted in the market at PKR 400,000 to 800,000
  • Historian, SCADA and condition monitoring interfaces costed individually
  • Criticality method agreed with engineering before configuration
  • Register reconciliation against the plant as built, scoped as real work
02

How long a maintenance system rollout takes

Reported timelines give three to six months for a mid sized rollout and nine to twelve months for a large programme with several sites and real integration work. Energy operations land in the second range more often than the first, and the reason is access rather than complexity.

Site access is slow by design and it should be. Inductions, permits and escorted visits mean a consultant who needs four days on a plant may need six weeks to get them, and a walkdown of the asset register cannot be done remotely, however good the drawings look. We plan for that explicitly and front load the visits, because a team that keeps returning for one more question burns the client's goodwill before it burns the budget.

Turnaround windows set the second constraint. A shutdown is planned months ahead, the scope is fixed, and a systems change that wants to ride along has to be in that scope or wait for the next one. Where the go live is genuinely tied to a turnaround, the date is immovable in a way that commercial deadlines never are, and the plan is written backwards from it. Data preparation is the third and quietest consumer of time, because building a spares master with lead times and criticality flags means someone in your stores has to make several thousand small decisions, and nobody has released them from their day job to do it.

  • Mid sized rollouts reported at three to six months, larger programmes nine to twelve
  • Site access, induction and permit lead times built into the schedule
  • Go live tied to a turnaround window planned backwards from a fixed date
  • Asset walkdown treated as fieldwork rather than a document review
  • Spares master decisions resourced by name, with time released to do them
03

Permits, contractor records and reporting in oil and gas

In an asset heavy operation the record is part of the safety case, which changes what a system has to do. A preventive maintenance task that was planned, performed and never evidenced is indistinguishable, after the fact, from one that was skipped. So the system holds the completion, the reading taken, the person who did it and the date, and it holds them where they cannot be quietly amended afterwards. That is the difference between a maintenance schedule and maintenance evidence.

Inspection findings need a route out of the report and into work. A finding recorded in a document that generates no work order is a known defect with no owner, and it will be quoted back at the operation if something happens. We build the link so a finding raises a work order with a due date and a responsible person, and so that closing it requires a record rather than a tick.

Contractor control is the third strand. Certification expires, insurance lapses, and the gate is where that gets discovered or missed. Holding certification and permit status against the contractor and the individual, with expiry visible before the day it matters, turns an argument at the gate into a scheduling decision the week before. Permit to work records belong with the same data, because the question after an incident is never only what happened, it is what authorisation was in force.

On tax, the same rules apply here as elsewhere. Section 3(9A) of the Sales Tax Act requires Tier-1 retailers and other notified persons to integrate with the FBR computerised system for real time reporting, and where an operation is notified the build is identical. Two boundaries are worth stating plainly. We are not a safety adviser and do not interpret regulatory obligations: your own advisers and your HSE function define what has to be evidenced, and we build the system to hold it. On tax, classification goes to your own tax adviser and we configure to their written instruction.

  • Preventive maintenance evidenced with reading, person and date, held unaltered
  • Inspection findings raising work orders with an owner and a due date
  • Contractor certification and insurance expiry visible before the gate
  • Permit to work records retained alongside the work they authorised
  • Regulatory obligations defined by your advisers, then built to that definition
How we deliver

Delivering in oil and gas

The six steps are the same on every engagement. What changes in an asset heavy operation is that nothing is signed off until the maintenance planners and the HSE function who will live with it have said so in writing.

  1. 01

    Discover

    We walk the plant with your maintenance planner, drawings in hand, checking tags against the labels actually on the equipment, then read twelve months of closed work orders to see what the register is worth.

  2. 02

    Blueprint

    Functional location structure, criticality basis and the route from inspection finding to work order are agreed in writing with engineering and operations before a single tag is loaded.

  3. 03

    Build

    Register load, preventive schedules and permit control are configured area by area. Your planners see each area working before we move on to the next one.

  4. 04

    Test

    A finding is taken through to a closed work order. A permit is issued, extended and returned. Field capture is proven offline, on the equipment, by a technician wearing gloves.

  5. 05

    Go live

    Cutover is scheduled around the maintenance calendar rather than the project plan, with open work orders and live permits carried across deliberately and a rollback point that has been rehearsed.

  6. 06

    Run

    Hypercare covers the first full preventive cycle, because a monthly schedule only proves itself over a month. After that, support, register housekeeping and a criticality review your own planners run.

Working together

Where this work usually starts

In practice the first engagement is rarely a system. It is an honest look at the register, the criticality basis and the last twelve months of work orders, because those three things tell you whether the problem is the software or what has been put into it. Quite often the existing platform is capable and the data underneath it has been neglected, and saying so early saves a great deal of money that would otherwise be spent replacing something that was never the constraint.

From there the sequence tends to hold. Get the tag structure right on one area. Establish criticality with engineering and operations in the same room. Make work orders close properly, including the ones raised from inspection findings. Only then extend into permits, contractor control and turnaround planning, where the value is real but the dependency on clean asset data is absolute.

We are comfortable being told that part of the scope is not worth doing yet. Asset systems in this sector reward patience, and a narrow implementation that people actually use is worth considerably more than a complete one they work around. If you want to talk through where your own estate sits, the conversation is more useful than a demonstration.

Credentials

Compliance for oil and gas clients

Energy buyers ask two things before anything technical: what we are accredited on, and how records that may end up in front of a regulator or an insurer are handled.

Oracle

Partner

Oracle Database and E-Business Suite underpin a good deal of asset and maintenance work in this sector. We handle upgrades, migration and the query tuning that long inspection histories eventually demand.

Microsoft

Partner

Power BI carries most of the maintenance reporting we build, with SQL Server behind it. Azure matters where a corporate estate is already there and field devices need somewhere to sync.

Google

Partner

Less central here than Oracle or Microsoft. Where a group runs Workspace, we build document control and inspection report storage into it rather than adding another place to look.

FBR digital invoicing

Compliant integrations

Upstream and midstream operators are sales tax registered like anyone else. We integrate invoicing with the Federal Board of Revenue system so field service and product sales invoices report as they are issued.

HIPAA

Compliant practices

Rarely the leading concern on a plant. It applies where we handle occupational health records or a company medical scheme, and there we work to documented controls and a business associate agreement.

Client words

What oil and gas clients say

Comments from people running oil and gas systems day to day.

  • The handover was the part I judged them on. Configuration decisions documented with the reasoning, our administrators trained properly, and a checklist we actually worked through. We run it ourselves now, and calling them is a choice rather than a necessity.
    Head of Shared Services Multi site manufacturing group
  • What sold us was that they argued with our brief. We asked for a reporting layer and they came back saying the reporting was fine, the batch data underneath it was not, and fixing that first would cost less. That turned out to be right. Our first mock recall after go live took an afternoon instead of the better part of a week.
    Finance Director Food manufacturing group, Karachi
  • We had been through one failed implementation already, so we were sceptical of the whole category. The difference here was the migration work. Two full rehearsal loads before the real one, with a reconciliation pack we could check ourselves. Nobody had ever handed us evidence like that and asked us to sign it.
    Head of IT Wholesale distribution business
Questions

Questions about oil and gas systems

Published market pricing puts work covering an operating asset with maintenance, spares and contractor control at PKR 3,000,000 upwards, and a smaller scope of five to seven modules at PKR 1,500,000 to 3,000,000. Mobile field capture is quoted separately at PKR 400,000 to 800,000. Those are market ranges rather than our price, and our figure follows discovery once the tag count is known.

Reported timelines give three to six months for a mid sized rollout and nine to twelve for a large multi site programme, and energy work usually falls in the second range. Site access, induction and permits stretch every field task, and where go live is tied to a turnaround window the date is fixed months ahead.

No, and it matters that we say so. Your own advisers and your HSE function define what has to be evidenced, inspected and authorised. We build the system that holds that evidence, produces it on demand and stops a work order closing without it. Where a requirement is unclear, we ask your advisers rather than deciding on their behalf.

It depends on how much of the plant is genuinely critical. Straightforward preventive schedules sit comfortably inside ERP. Once criticality analysis, condition monitoring feeds and turnaround scope planning are involved, a dedicated maintenance layer earns its licence. We say which case you are in during discovery rather than after the licence has already been bought.

It is scoped as fieldwork, not as data entry, because a walkdown is the only honest way to reconcile drawings against the plant. The effort scales with tag count and site access rather than with module choice, and it usually runs alongside configuration. We price it after seeing a sample area rather than from a tag count alone.

Only if capture takes seconds and works without a signal. Screens get built for a gloved hand and a small number of large targets, records queue locally and sync when the device reaches coverage, and the first month is spent watching people use it rather than training them in a room. If capture is awkward, the paper comes back.

Other sectors

The other sectors we work in.

The same practices, applied to the problems each sector actually has.

01 Governmental Departments and authorities that need auditable systems, controlled access and procurement that survives scrutiny. 02 Food Manufacturing Batch traceability, shelf life and yield, joined up from goods in through to the despatch note. 03 Aluminum Alloy, coil and billet traceability with the costing detail that melting, extrusion and finishing actually need. 04 Retail Tills, stock and online joined to one set of numbers, with FBR digital invoicing where it applies. 05 Professional services Time, utilisation and project profitability made visible while a job can still be steered. 06 Wholesale Distribution Stock accuracy, route delivery and true landed cost across warehouses and vans. 07 Construction Project cost control, subcontractor certification and valuations that reconcile to the ledger. 08 Automotive Part traceability, supplier schedules and dealer systems joined to the plant. 09 Mining Production, grade, fleet availability and consumables measured where the cost is incurred. 10 Telecom High volume billing, provisioning and network asset data, joined without breaking the month end. 11 Textile Style, colour and size matrices, plus real costing across spinning, weaving, dyeing and stitching.
All industries

Working with oil and gas systems?

Tell us what you run today and where it breaks. The first conversation is a consultation, not a pitch.

Book a consultation All industries