What Does Asset Integrity Management Software Actually Cost?

Every integrity manager who has tried to get an asset integrity management (AIM) or risk-based inspection (RBI) system approved has hit the same wall in the same order. You can build the technical case. You can build the safety case. Then finance asks what it costs, and you discover that almost nobody in this sector will tell you.

Search for the price of integrity management software and you will find product pages, demo request forms and the words “contact us for a quote”. That is not unreasonable — these are configured enterprise systems, not seats of office software, and a number given without knowing your asset count or your data condition would be misleading. But it leaves you with a real problem: you cannot run a procurement until you can build a budget, and you cannot build a budget from a contact form.

So rather than publish a price that would not apply to you, this article sets out the thing that is genuinely portable between buyers — the structure of the cost. What the elements are, which of them are capital and which are operating, which one is most often underestimated, and what actually moves the total up or down. Take it into your own budget exercise and into conversations with any vendor, including us.

Capex or opex is the first question, not the last

In most organisations the commercial model is decided before the software is. A capitalised purchase and a subscription travel through completely different approval routes, land on different budget lines, and are owned by different people. Working out which route your organisation can actually get through is often a better use of early effort than comparing feature matrices.

The two shapes break down like this:

The element most often underestimated: getting the data trustworthy

If a project of this kind overruns, the asset data build is usually why.

The software is the straightforward part. The difficult part is that on an ageing brownfield refinery, platform, terminal or pipeline network, the technical information needed to run a credible integrity programme is scattered. Equipment registers sit in one system and corrosion circuits in a spreadsheet. P&IDs and isometrics may not reflect what was built, let alone what has since been modified. Thickness readings exist as PDF reports from several contractors using several conventions. Inspection history lives partly in a database, partly in a filing room and partly in the memory of an engineer approaching retirement.

Defining corrosion circuits and damage mechanisms, reconciling the equipment register against the plant as it actually stands, normalising historical readings so a corrosion rate can be trended, and getting all of it into a state the engineers will stand behind — that is real engineering effort, and it is frequently the single largest line in the capital cost. An entire category of vendors now exists to address exactly this problem, which tells you how common it is.

The honest point for a buyer: treat any proposal that prices data migration as a nominal line item with suspicion, and ask how it was scoped. The cost does not disappear by being left out of the quotation. It simply arrives later, as a change order or as a programme that stalls.

Capex and opex: the trade-off, stated even-handedly

Neither model is inherently better. They suit different organisations.

A capitalised or perpetual model can be capitalised and depreciated, which matters where capital and operating budgets are approved by different routes and on different timescales. It gives a predictable cost of ownership across a long horizon, which suits assets whose remaining life is measured in decades. It usually carries a higher entry cost, and it leaves the organisation carrying more of the upgrade and infrastructure responsibility.

A subscription model has a lower entry cost and a faster start, scales up and down as the estate and the user population change, and moves upgrade and hosting risk to the vendor. In exchange it becomes a permanent line in the operating budget that has to be defended every year, and over a long ownership horizon the cumulative position looks different from the first-year position.

The decision is as much about your budget structure and approval process as about the software. An organisation whose capital approval route is well-trodden and whose operating budget is squeezed will reach a different answer from one with the opposite constraint — and both answers can be right.

What actually drives the total up or down

These are the levers worth examining before you ask anyone for a number, because they are mostly within your control.

• Scale of the asset population. Equipment items, tags, circuits and components in scope. This is the primary driver of both licensing and study effort.
• Number of sites, and the rollout sequence. A phased rollout across sites spreads cost and lets the second site benefit from what was learned at the first. A simultaneous rollout is faster and usually more expensive per unit of elapsed time.
• Maturity of existing data. The single biggest swing factor. A well-maintained register with clean inspection history is a different project from a scattered one.
• Depth of methodology. Qualitative screening, semi-quantitative assessment, and fully quantitative API 581 analysis demand increasing amounts of data and engineering time. Many operators sensibly run different depths on different parts of the estate.
• Integration scope. Each interface to EAM, ERP, document management or inspection data sources adds build and ongoing maintenance.
• Users — number and type. Full engineering users, reviewers and approvers, field inspectors on mobile devices and read-only management users do not all need the same access.
• Delivery route. Direct from the vendor, or implementation through a local partner.
• Pace. How quickly you need to be live changes the resourcing profile and therefore the cost.

When procurement decides the commercial model

For national oil companies, state-owned enterprises and large multi-site operators, the commercial model is not a purely financial preference. It is frequently decided by the procurement framework before anyone opens a technical specification.

The commercial model has to fit the procurement model. In many national oil companies, state-owned enterprises and state-linked operators, capitalised spend and multi-year tendered contracts fit established delegation of authority and approval routes far more readily than an open-ended annual subscription. A subscription with no defined term can be genuinely difficult to place against a budget head, even when it is the better technical fit. A vendor who cannot present cost in a form your tender process accepts is creating work for you, regardless of how good the product is.

Tender and framework structures shape how cost must be presented. Multi-year frameworks, two-envelope technical and commercial submissions, rate-contract structures and defined price validity periods all require cost to be broken down in a particular way — typically with licence, implementation, data services, training and annual support as separately identified lines, with defined quantities and clear scope boundaries. It is reasonable to ask a vendor early whether they have submitted into your tender format before.

Data residency and hosting location frequently decide the deployment model. Where national regulation, group IT policy or contract terms require integrity data to remain in-country, the choice between hosted and on-premise deployment can be made for you — and that choice changes the cost shape, moving spend between capital infrastructure and recurring hosting.

Currency, contracting entity and in-country support. Whether contracting is in local currency or a hard currency, whether a local entity or partner invoices, how withholding tax and import of services are handled, and what in-country support presence is expected during your working hours and local holidays — all of these belong in the commercial conversation early, not at contract signature.

Partner-led delivery. In many markets, implementation is delivered through a local partner rather than directly by the software vendor. For a buyer, the practical questions are consistent: who holds the licence relationship, who holds the implementation contract, who you escalate to, which party provides first-line support and in what hours, how the vendor’s product roadmap reaches you, and how the partner’s and vendor’s scopes are separated so nothing falls between them. Done well, partner delivery gives you people in your time zone who know your regulatory environment. Those questions simply need clear answers in writing.

Twelve questions to ask any integrity software vendor about cost

Print this. Use it on every vendor on your list, including us.

1. What exactly is included in the licence, and what is a separately chargeable module? Ask for the boundary in writing, not in a demo.
2. How is the licence counted — by user, by site, by asset or tag count, by enterprise? And what happens when that count grows?
3. How is data migration scoped and priced? What specifically are you assuming about the condition of our data, and what happens commercially if that assumption turns out to be wrong?
4. What is in the implementation fee and what is chargeable extra? Configuration, workflow changes, report development, additional training days, travel and site attendance.
5. What does annual support and maintenance cover, how is it calculated, and is it mandatory?
6. What triggers a price increase during the term, what is the cap, and what is the notice period?
7. What happens at renewal? What are the renewal mechanics, the term, the notice required to exit, and the uplift mechanism?
8. Who carries the cost of upgrades? Are new versions included, and does our configuration survive an upgrade or is re-work chargeable?
9. How are additional users, sites and modules priced, and are those rates fixed for the term or quoted at the time?
10. What are the exit and data portability terms? In what format do we get our asset register, assessment history, inspection results and anomaly records, how complete is it, and what does extraction cost?
11. What support response is included? Response and resolution targets by severity, hours of cover in our time zone, language, and who provides first line — the vendor or the partner.
12. What will this cost us in year three and year five, not year one? Ask for the full-term view including support, growth and reassessment, under both commercial models if both are offered.
    

If a vendor answers all twelve clearly, you have learned something valuable about how they will behave once the contract is signed. If they will not, you have learned something valuable too.

Why we do not publish a price, and what we will do instead

We do not publish a price list for ONE, and we would rather explain that than hide behind it. Any figure we published would be either so heavily caveated as to be useless, or wrong for most of the people reading it. A credible number depends on the size of the asset population, the number of sites and the rollout sequence, the depth of methodology you need, the integrations required, the deployment model your data residency rules allow, and above all the state of your existing asset data. Those vary enormously between a single storage terminal and a group running refineries, petrochemical plant and an LNG receiving terminal under one integrity function.

What we will do is go through the cost structure openly for your specific situation — the elements above, applied to your asset count, your data condition and your procurement framework, under whichever commercial model fits your approval route. That conversation is useful even if it ends with you buying nothing, because you will leave it able to build a budget.

If that is where you are, get in touch or request a demo and we will walk through it with you.

Frequently Asked Questions

How much does asset integrity management software cost?

The cost depends mainly on the number of assets and components in scope, the number of sites, the depth of risk-based inspection methodology, the integrations required and the condition of existing asset data. Most vendors quote per project rather than publish a price list, because these variables change the total substantially from one operator to another.

Is asset integrity software a capital or operating expense?

It can be either. A perpetual or multi-year term licence, with the initial data build and configuration, is usually treated as capital expenditure. A subscription or software-as-a-service licence, annual support, hosting and ongoing data stewardship are usually operating expenditure. The right model often depends on which budget and approval route an organisation can get through.

What is the biggest hidden cost in implementing integrity software?

The asset data build is usually the largest and most underestimated cost. Reconciling equipment registers, defining corrosion circuits and damage mechanisms, and normalising historical inspection and thickness data takes significant engineering effort. Proposals that show data migration as a small fixed line should be checked carefully for the assumptions behind them.

What should you ask a vendor about integrity software pricing?

Ask what the licence includes, how it is counted, how data migration is scoped, what triggers price increases and how renewal works. Also ask who pays for upgrades, how additional users and sites are priced, what the exit and data-export terms are, and what the total cost will be in years three and five, not only year one.