Inspection management software for API 510, 570 and 653 contractors: what the owner-side systems leave out
Software for API 510, 570 and 653 work splits along asset ownership. Owner-side systems — the VisualAIM platform now held by Prometheus Group, MISTRAS PCMS, and Codeware INSPECT — hold code calculations, CML history and risk-based inspection plans for one operator's assets. Contractors need quoting, crew dispatch, inspector certification currency, per-client data segregation and utilisation reporting. None of those systems ship that, so contractors run two.
The API inspection contractor sits in a gap that neither end of the software market addresses. At one end are inspection data management systems built for asset owners, where the organising object is a vessel, a piping circuit or a tank that the buyer owns and will still own in twenty years. At the other end are generic field service platforms that dispatch crews and raise invoices but know nothing about a thickness reading, a corrosion rate or a certified qualification level. The contractor needs both halves at once: enough inspection domain to produce a report a plant's authorised inspector will accept, and enough commercial machinery to quote work, mobilise crews, prove every technician was current on the day, and keep one operator's data from ever appearing next to a competitor's. This page describes what each category actually does, taken from published vendor documentation, and what a contractor still has to solve on its own.
Source: Prometheus Group acquisition of the VisualAIM business assets, announced 5 August 2026 (asset purchase); MISTRAS Group PCMS and PCMS Mobile published product documentation; Codeware INSPECT published product documentation; API Individual Certification Programs, Program Document ICP-PD-102-Inspector, revision date 15 September 2025; API ICP published certification schedule and fees (2026 exam windows; initial certification $875 member / $1,125 non-member; recertification $745 member / $855 non-member); ISO/IEC 17020:2012; ASNT Recommended Practice No. SNT-TC-1A (2024).
| Job to be done | Owner-side IDMS (VisualAIM, PCMS, INSPECT) | Generic field service software | What the contractor's system must do |
|---|---|---|---|
| Remaining life, tmin and corrosion rate under API 510/570/653 | Core capability, deeply implemented | Absent | Reproduce enough of it to defend a recommendation, or hand off to the owner's system |
| CML history across successive turnarounds | Core capability, owned by the asset owner | Absent | Read and write the owner's CML identifiers without becoming the system of record |
| Risk-based inspection planning to API 580/581 | Core capability where licensed | Absent | Not required; the owner plans, the contractor executes |
| Quoting and bid turnaround for scoped inspection packages | Absent — assets are owned, not quoted | Generic quoting, no method or code awareness | Price by method, weld count, shift pattern, mobilisation and standby |
| Crew dispatch, mobilisation and site access readiness | Absent | Present but credential-blind | Block a mobilisation when a ticket, medical or induction is not current |
| Inspector certification currency (API CPD, ASNT, ISO 9712) | Absent | Absent or a generic expiry date field | Track distinct clocks per scheme and per inspector, with evidence attached |
| Data segregation between competing client operators | Single-tenant by design — one owner's plant | Generic customer records, weak isolation | Hard partition per client, enforced on records, users and exports |
| Technician utilisation and job-level margin | Absent | Present in generic form | Billable versus paid hours by technician, method and contract |
The split that decides which software you actually need
Every product in this market is built around an assumption about who owns the asset. Get that assumption right and the shortlist writes itself. If the buyer owns the vessel, the piping circuit or the tank, the software's job is to hold decades of condition history for that specific equipment, calculate remaining life, and plan the next inspection. If the buyer inspects other people's equipment for a fee, the software's job is to win work, mobilise qualified people, capture evidence at the workface, produce an accepted deliverable, and prove afterwards that everyone involved was properly certified.
Those two jobs share almost no data model. The owner's system is organised by equipment tag and lives forever. The contractor's system is organised by job and client, and each job closes. The owner cares about corrosion rate trending across fifteen years of turnarounds. The contractor cares whether the crew that flew to the site on Tuesday was billable for the full shift and whether the report cleared document control on Thursday.
This is why so many API inspection contractors end up running two systems and reconciling by hand. It is not a failure of procurement. It is a genuine gap in the market between products built for plants and products built for generic field service, and the mid-market contractor of ten to a hundred inspectors falls squarely into it.
What the owner-side systems genuinely do well
Three products define the owner-side category, and each is strong in its lane. The VisualAIM platform — acquired by Prometheus Group in an asset purchase announced on 5 August 2026 — gives fixed-equipment teams a structured system for inspection history, corrosion logic, condition monitoring locations, remaining-life calculation, equipment documentation and risk-based inspection planning, and its published material describes converting AutoCAD P&IDs into structured digital drawings with assets catalogued and linked to their records.
MISTRAS PCMS is positioned as an inspection data management system for asset integrity, corrosion and inspection data across a facility's equipment, with a risk-based inspection module for prioritising work, a maintenance management link that pushes findings into a CMMS as work orders, and PCMS Mobile for field capture with offline access and synchronisation. It is one of the most established products in the category and it is built to be the operator's system of record.
Codeware INSPECT approaches the same problem from the calculation side. Its published documentation describes performing API 510 tmin calculations and API 579 fitness-for-service assessments in one platform, supported by full ASME Section VIII Division 1 and Division 2, ASME B31.3, B31.4 and TEMA calculations, with API 653 tank assessment covering shell settlement, floor bulges and patch plates. For run-repair-replace decisions on owned equipment, that depth is exactly right.
The contractor jobs none of them cover
Start with the one that comes first chronologically and gets automated last: quoting. An API inspection contractor prices work by method, by weld or component count, by shift pattern, by mobilisation distance, by standby exposure and by the client's rate schedule. None of that exists in an owner-side IDMS, because owners do not quote themselves for inspecting their own tanks. Most contractors quote in a spreadsheet that lives on one estimator's laptop, which is why bid turnaround is the most common bottleneck in the business.
Then dispatch. Owner-side systems assume the inspector is already there and already qualified, because the operator employs them. A contractor is assembling a specific crew for a specific site with specific access requirements, and the binding constraint is not availability but eligibility. The system has to know that this technician's site induction lapsed last month before the truck leaves the yard, not after they are turned away at the gate.
Third, the commercial view. Which contracts made money last quarter. Which technicians are billable against paid hours. Which method lines are being underpriced. Which jobs consistently overrun their quoted hours. That is the contractor's only real management dashboard and there is nowhere in an owner's IDMS for it to live, because the owner has no margin to measure.
Certification currency is the contractor's highest-frequency failure mode
A plant employing its own inspectors manages a handful of certifications for a stable roster. A contractor manages several per person across a roster that changes, against schemes with different clocks, and every one of those dates is a potential job stoppage. This is the operational problem contractors report most often, and it is almost never solved by the software they bought.
The clocks are genuinely independent. API's Individual Certification Programs, per Program Document ICP-PD-102-Inspector (revision date 15 September 2025), require 24 continuing professional development hours for every three-year certification cycle, in addition to continued inspection experience and a six-year web quiz — so an API 653 inspector's file has an expiry date, a CPD ledger and a periodic quiz obligation running simultaneously. Under ASNT Recommended Practice No. SNT-TC-1A (2024), method certifications run on the employer's own written practice with its own intervals. ISO 9712:2021 certificates carry a maximum five-year validity with a defined renewal window after expiry.
Layer on annual vision tests, client-specific site inductions, medicals, confined space and working-at-height tickets, and radiation safety cards where relevant. The software requirement is unglamorous and specific: one record per person per credential, with issue date, expiry date, scanned evidence, and a mobilisation block that fires before the crew is assigned rather than a reminder email that gets filtered. Recertification also has a cash side — API publishes recertification at $745 for members and $855 for non-members against initial certification at $875 and $1,125 — so lapsing into a full re-examination is an avoidable cost as well as an avoidable outage.
Quoting and bid turnaround: the money line nobody automates
Contractors lose more revenue to slow quoting than to underpricing. A refinery planner assembling a turnaround scope sends the same enquiry to four contractors on a Monday and shortlists on Wednesday. The contractor whose estimator is on a site visit until Thursday is not in the running, regardless of rate. Speed is a qualification criterion long before price is a decision criterion.
Quoting for API inspection work is structured enough to be systematised. The inputs repeat: method mix, component or weld count, access provisions, expected standby, mobilisation distance and duration, shift pattern and rotation, consumables, equipment allocation, and the client's negotiated rate schedule where a framework agreement exists. Build those as a template per client and per work type and the estimator's job becomes selecting and adjusting rather than rebuilding from a blank sheet.
The second-order benefit matters more than the speed. Once quotes are structured data rather than spreadsheet attachments, quoted hours can be compared against actual hours job by job. That comparison is the single most valuable report a contractor can produce, because it tells you which work types you are systematically underpricing — and no owner-side inspection system can generate it, because it has never seen a quote.
Dispatch, mobilisation and the site access checklist
Mobilisation is where contractor software either earns its keep or does not. The decision to send a named technician to a named site on a named date depends on availability, method qualification for the scope, current certification under the applicable scheme, valid site induction for that specific facility, current medical, and equipment that is both allocated and in calibration. Six conditions, and every one is a hard stop that a generic scheduler will happily ignore.
The right behaviour is to make the assignment impossible rather than to warn about it. If a technician's ticket expires before the job ends, the assignment should be refused at the point of scheduling with the reason stated, so the coordinator finds a substitute in the office instead of at the gate. The same logic applies to instruments: an ultrasonic thickness gauge whose calibration expires mid-campaign should not be allocatable to that campaign at all.
Equipment calibration deserves the same rigour as personnel certification and is usually managed far more loosely. Every instrument needs a calibration certificate, a due date, a traceable record linked to each report it produced, and a recall workflow. When an out-of-calibration instrument is discovered after the fact, the exposure is every report it touched since the last valid certificate — and reconstructing that list from spreadsheets is precisely the kind of week no operations manager has spare.
Client data segregation: one contractor, many competing operators
This requirement has no analogue on the owner side, which is why owner-built systems have no answer for it. A contractor working for two refineries in the same market holds corrosion data, weld reject rates and equipment condition for both. That information is commercially sensitive to a degree that few software buyers appreciate until an auditor from one client asks how the other client's data is isolated.
Segregation has to be structural rather than procedural. Access scoped by client entity and enforced on every query, not just on report headers. Exports and reports that default to a single client and require deliberate action to widen. Attachment stores partitioned so a filename search cannot cross the boundary. Audit logging on every access so that a challenge can be answered with a record rather than an assurance. Anything softer than that is a policy, and policies do not survive staff turnover.
There is a contractual dimension too. Master service agreements with major operators increasingly specify data handling, retention periods and deletion obligations at contract end. A system that cannot delete or export one client's complete data set cleanly, without disturbing the others, creates a compliance problem at exactly the moment the relationship is ending. Build the requirement into procurement — our NDT software RFP requirements checklist covers how to test it during evaluation rather than after.
Writing into the client's system without owning it
The deliverable question decides more implementations than the feature list does. Some operators require findings entered directly into their IDMS by the contractor's inspector. Some require a structured import file in a defined layout. Some accept a signed PDF into a document management portal. Some want all three for different asset classes. A contractor working across five operators is working across five delivery formats, and this cannot be negotiated away.
The workable architecture is one system of record for the contractor's own work and a mapping layer per client. Capture once in the field, in a structure rich enough to satisfy the most demanding client — CML identifier, nominal and measured thickness, previous reading and date, instrument and calibration reference, technician and certification level, procedure and revision — then render that into whatever each client requires. Capturing to the lowest common denominator and enriching later is how re-keying and transcription errors get built in permanently.
Getting instrument output into that structure is its own engineering problem, covered in our walkthrough of moving OmniScan data into a client report. And where an operator is moving toward 3D asset visualisation rather than tabular records, the boundary between the two categories is worth understanding directly — see digital twin versus IDMS and the UT thickness overlay workflow.
Utilisation and job margin: the contractor's real dashboard
Every other section of this page describes avoiding a loss. This one describes finding money. A contractor's economics reduce to a simple question asked at three levels: what fraction of paid technician hours got invoiced, by person, by method line, and by contract. Firms that can answer it weekly price better, staff better and negotiate framework renewals from a position of fact. Firms that cannot are guessing, and usually guessing optimistically.
The gap between paid and invoiced hours hides in predictable places — standby during permit delays that nobody logged, travel the contract allows but the timesheet never claimed, overtime worked before written approval landed, scope added verbally at the workface and never converted into a variation. Each is a capture failure at the point of work, which means it is fixed at the point of work with mobile capture and supervisor sign-off, not in the office two weeks later.
Job-level margin is the other half. Quoted hours against actual hours, by work type, tells you which services subsidise which. Contractors routinely discover that one method line has been priced from a rate card written years earlier and has been losing money on every job since. The arithmetic for putting a defensible number on all of this is set out in our NDT software ROI model.
Scoping it: build, buy, or configure
Three routes exist and each fails in a characteristic way. Buying an owner-side IDMS gives you code depth you mostly will not use and none of the commercial machinery, so the spreadsheets survive alongside it. Buying generic field service software gives you dispatch and invoicing and leaves certification currency, calibration traceability, qualified-signature control and client segregation unaddressed. Building from scratch gives you exactly what you want and a maintenance obligation your business is not structured to carry.
The fourth route is configuring a business platform that already handles projects, people, equipment, quoting, invoicing and document control, and adding the inspection-specific layer on top of it. That is the approach Atlantis takes with an Odoo-based ERP configured for NDT and API inspection contractors — technician certification tracking, equipment calibration recall, per-client data partitioning, method-aware quoting and inspection reporting sitting on a commercial core that already works. Affordable, accessible and fully customisable, quoted against your scope.
Scope it against your own job list before you talk to anyone. Write down your annual job count, your client count, your inspector count, the certification schemes you hold, and the delivery formats your top three clients demand. That single page determines the answer more reliably than any product comparison. Send it to us at /contact or info@atlantisndt.com and we will tell you which of the four routes fits — including when the answer is that you do not need us.
Can an API inspection contractor just work inside the client's IDMS?
For the deliverable, often yes — many operators require findings to land in their system. For running your business, no. The client's IDMS has no record of your quote, your crew roster, your technicians' certification status, your equipment calibration schedule or your job margin, and it will never show you your other clients. It is a delivery destination, not a management system. You need both.
What does certification currency mean for an API 510 inspector in software terms?
It means tracking several independent clocks per person and refusing a mobilisation when any has run out. API's ICP requires 24 CPD hours per three-year certification cycle alongside continued inspection experience and a six-year web quiz, per Program Document ICP-PD-102-Inspector. Layered on that sit ASNT or ISO 9712 method certifications with their own intervals, annual vision tests, site inductions and medicals. Each needs an expiry date, an evidence file and a hard block.
How should contractor software handle data segregation between competing clients?
Partition at the record level, not the report-cover level. A refinery and its direct competitor must never share a searchable index, an attachment store, an export or a user's default scope. Enforce it in three places: role-based access tied to the client entity, exports scoped to a single client by default, and audit logging of every cross-client query. Many master service agreements make this an explicit contractual obligation, not a preference.
Do API 510/570/653 contractors need API 579 fitness-for-service calculations in their own system?
Only if fitness-for-service is a service you sell. Codeware INSPECT performs API 579 assessments alongside API 510 tmin calculations, and firms doing FFS work as a deliverable buy that capability deliberately. A contractor supplying inspection execution and reporting does not need it in the management system — the owner's engineering function or a specialist runs the assessment. Do not pay for code depth you will not use.
What changes when a contractor holds ISO/IEC 17020 accreditation?
Recordkeeping stops being internal housekeeping and becomes evidence an assessor will sample. You must show impartiality controls, documented competence per inspector for each inspection type performed, controlled procedures and revisions, calibrated equipment traceable to each inspection, and complaint and appeal handling. The system has to make any one report traceable to all of that on demand. Our ISO 17020 software page maps clause to record.
Is a generic field service management tool enough for an NDT or API inspection contractor?
It covers dispatch, timesheets and invoicing competently and nothing above that line. It will not know that a technician's UT Level II expired, that a probe is out of calibration, that a report needs a qualified signature before release, or that this client's data must never surface in that client's export. Contractors who start there almost always end up bolting a spreadsheet onto it for exactly those four things.