Why forty stations produce forty incompatible thickness datasets
Numbers fail to roll up because each site defines them differently: different CML naming, different minimum-thickness basis, different corrosion-rate convention, different handling of negative rates. The fix is not forcing every location to re-key its history. It is storing raw readings with full provenance, keeping local identifiers as aliases against one canonical tag, and recomputing every rate centrally from the readings themselves.
Midstream makes the problem structural rather than cultural. A single operator's regulated footprint spans buried line pipe assessed by in-line inspection under 49 CFR 192 subpart O or 195.452, above-ground station piping inspected under API 570, breakout tanks under API 653, and dig verifications that compare a magnetic flux leakage call against a manual UT grid. Those four record types do not share units, baselines or tolerances: an ILI tool reports metal loss as a percentage of nominal wall within a stated certainty, typically ±10 percent of wall at 80 percent confidence for standard resolution MFL, while a field grid reports absolute remaining thickness against whatever baseline that station chose. Subtracting one from the other is a category error that survives every spreadsheet it is pasted into. Rolling the fleet up honestly means recording, for each number, which method produced it and what it was measured against.
Source: Sources: 49 CFR Part 192 subpart O (gas transmission integrity management) and 49 CFR 195.452 (hazardous liquid integrity management); ASME B31.8S Managing System Integrity of Gas Pipelines; ASME B31.4 and B31.8 pipeline design codes; ASME B31G and API 579-1/ASME FFS-1 for remaining strength of corroded pipe; API 1160 Managing System Integrity for Hazardous Liquid Pipelines; API 570 Piping Inspection Code and API 653 Tank Inspection, Repair, Alteration and Reconstruction for station and terminal assets; API 1163 In-Line Inspection Systems Qualification; AMPP/NACE SP0102 for in-line inspection of pipelines and SP0502 for external corrosion direct assessment; ASNT SNT-TC-1A and ISO 9712 for personnel qualification.
| Convention | How sites actually differ | Effect on the consolidated number |
|---|---|---|
| Thickness baseline | Some sites trend against nominal wall, others against the first measured wall, others against a purchase-order minimum wall including mill tolerance | Total loss to date differs by the mill under-tolerance, up to 12.5 percent of nominal on some line pipe; fleet loss totals are not additive |
| Minimum thickness basis | Pressure design t-min from the applicable code, structural minimum, a flat administrative floor, or a manufacturer default | Remaining life for identical measured walls varies by years between sites; the fleet worst-case list is populated by whichever site set the strictest floor |
| Corrosion rate method | Last two readings, long-term from first to latest, linear regression across all points, or a rolling window | Short-term and long-term rates diverge on any circuit with a service change; mixing them makes the fleet distribution meaningless |
| Negative rate handling | Floored at zero, replaced by a default rate, discarded, or reported as measured | Assumed rates and computed rates become indistinguishable once aggregated, and the fleet appears more certain than it is |
| Units and rounding | Mils, thousandths of an inch, decimal inches and millimetres, rounded at capture or at report | Unit inference on import silently rescales values by 25.4 or 1000; the error is invisible until a remaining-life figure looks absurd |
| CML identity | Station-local numbering, contractor numbering, drawing bubble numbers, or a corporate tag scheme applied unevenly | The same physical location appears as several CMLs, or several locations collapse into one, destroying the trend either way |
| Measurement method recorded | Some sites record UT spot, others UT grid or PAUT map, many record nothing | A map minimum and a spot reading are compared as if equivalent, systematically overstating loss at the changeover |
Forty sites, forty conventions, none of them wrong
A midstream operator's mechanical integrity data is produced at compressor and pump stations, meter and regulator stations, pig launchers and receivers, breakout tank farms and terminals, spread across states and often across companies that were acquired rather than built. Each location has its own contractor relationship, its own inspection history, its own drawings and its own person who has been doing it a particular way for fifteen years. The result is not chaos; it is forty internally coherent systems that do not compose.
The corporate integrity group discovers this when someone asks a fleet question. What is our total measured wall loss this year. Which are our twenty worst circuits. What proportion of station piping is within five years of retirement thickness. Every one of those questions requires adding numbers together, and the numbers were produced under different definitions. The answers that come back are either obviously wrong, or worse, plausible and wrong.
The instinct at that point is to issue a standard and require compliance. It rarely works, because the standard collides with a decade of local history that nobody has budget to re-key, and because field crews keep using the identifiers physically stencilled on the pipe regardless of what a corporate document says. The durable fix is to accept local variation at capture and enforce consistency at aggregation, which is a data model decision rather than a governance one.
The baseline nobody wrote down
Total metal loss to date is a subtraction, and the number you subtract from is a choice. Some sites subtract from nominal wall as printed on the isometric. Some subtract from the first measured wall, on the reasonable grounds that the pipe never actually was nominal. Some use the purchase specification minimum wall, accounting for mill under-tolerance, which on line pipe can legitimately be up to 12.5 percent below nominal on some product specifications.
On a 0.375 inch nominal wall those three baselines can span more than forty mils before a single molecule of iron has left the pipe. Trend an accurate set of readings against nominal when the pipe was rolled thin, and you will report loss that never happened and a corrosion rate that never occurred. Trend against a first measured wall taken with an uncalibrated gauge and you inherit that error permanently as the origin of every subsequent calculation.
Neither practice is indefensible in isolation, and both are common. What is indefensible is not recording which one was used. The baseline, its source and the date it was set belong on the CML record as explicit fields, with the ability to hold more than one — nominal, specified minimum and measured baseline together — so that a fleet report can state which basis it used and switch bases without touching a single reading.
Corrosion rate is an opinion until you say which one
Inspection codes deliberately ask for more than one rate. A short-term rate from recent readings catches an acceleration. A long-term rate across the full history smooths measurement scatter and is usually the more stable planning number. API 570 and API 510 both expect the more conservative of the two to drive the interval. Sites apply this differently: some compute short-term as the last pair, some as the last three years; some compute long-term from installation, some from the first reliable reading after a known measurement problem.
Then there is the negative rate. On any large population of CMLs, a substantial share of consecutive pairs will show apparent wall gain, because measurement repeatability is of the same order as one cycle of slow corrosion. Sites handle this in at least four ways: report it as measured, floor it at zero, substitute a default rate, or drop the pair. Each of those choices produces a different fleet distribution, and once the rates are aggregated there is no way to tell an assumed rate from a computed one.
This is the single strongest argument for centralising raw readings rather than centralising computed results. If corporate holds the readings, corporate computes every rate with one documented method, publishes both the short-term and long-term figures, and marks every value that came from a rule rather than a measurement. Sites can still compute their own numbers locally for their own use; the difference between the two is then a visible reconciliation item rather than a hidden inconsistency.
In-line inspection and manual ultrasonics are not the same measurement
A large part of a midstream operator's wall-loss information does not come from a technician with a gauge at all. It comes from an in-line inspection tool run through the pipeline: magnetic flux leakage for metal loss in most gas and many liquid lines, ultrasonic wall measurement tools in liquid service, and increasingly combined technologies. These tools report anomalies with a depth expressed as a percentage of wall, a length and width, and — crucially — a sizing tolerance at a stated confidence. Standard resolution MFL is commonly quoted around ten percent of wall at eighty percent certainty for general metal loss.
Manual UT at a dig site reports something different: absolute remaining thickness at specific points on a grid, with its own much tighter tolerance. The comparison between the two is not a correction; it is a tool performance assessment, and API 1163 together with AMPP/NACE SP0102 sets out how unity plots and unbatched comparisons should be built from dig data. Treating a dig UT reading as a correction to be applied to the ILI call, or averaging the two, destroys exactly the information that qualification requires.
In the data model this means measurement type is not a label, it is a structural attribute. An ILI anomaly record carries its tool, run date, vendor, technology, sizing tolerance and confidence. A dig record carries the grid, the technician, the instrument and the excavation. They link by location and are compared explicitly, producing a comparison record. What they must never do is merge into one thickness series, because a mixed series inherits the worse tolerance and misleads every calculation downstream, including B31G and API 579 remaining strength assessments.
Aliases, not renaming: migrating without destroying the history
The practical obstacle to standardisation is that the field will not stop using local names. The CML number is stencilled on the insulation cladding, drawn on a laminated sheet in the station, and known to the contractor crew who have measured it for eight years. A corporate initiative that renames it succeeds on the server and fails at the pipe, which produces the worst outcome: readings taken against the old name and stored against nothing.
The workable pattern is an alias table. Each physical location gets one canonical identity that never changes. Alongside it sit any number of aliases — the station-local number, the drawing bubble reference, the previous owner's tag from before the acquisition, the contractor's internal reference. Field capture accepts any alias. Reporting uses the canonical identity. Nobody in the field has to change anything, and nothing in the history has to be re-keyed.
Aliasing also solves the two failure modes that migrations otherwise produce. Duplicate creation, where an unrecognised identifier silently becomes a new CML and splits one location's history into two shorter, less useful series. And collapse, where two genuinely different locations that happened to share a local number are merged into one impossible trend. Both are caught by quarantining unmatched identifiers for human review at import instead of auto-creating, which is the first behaviour to test in any evaluation.
What the regulator asks for and what rolls up to the board
Midstream operators answer to two audiences with different questions. A PHMSA inspection asks whether the integrity management programme was followed for a specific segment: whether the assessment method and interval met 49 CFR 192 subpart O or 195.452, whether anomalies were evaluated and remediated within the required response times, whether records support each of those decisions. That is a per-segment, evidence-first question, and it is answered by depth of record.
The board and the capital planning process ask something else: where is the fleet trending, which assets will require replacement in the next five years, is the integrity spend going to the right places. That is a roll-up question, and it is answered by comparability across sites. The same underlying dataset has to serve both, which is why local flexibility at capture and central consistency at aggregation is not a compromise but the actual requirement.
There is a third audience worth designing for: the site itself. Standardisation initiatives that only produce corporate reports get complied with grudgingly and decay. The ones that survive give the site something back — a coverage figure that justifies its own budget request, a contractor quality comparison, an automatic flag when a reading is inconsistent with the location's history. If a station engineer can see a benefit from entering the provenance fields, the fields get entered accurately, and the corporate roll-up becomes reliable as a by-product.
Evaluating a system for multi-site standardisation
Test the identity model first, because everything else depends on it. Ask whether one physical location can carry multiple identifiers with one canonical tag, whether an import with an unrecognised identifier quarantines for review rather than creating a new record, and whether merging two records that turn out to be the same location preserves both histories with their sources intact. A system without aliasing will force a renaming programme, and the renaming programme is what fails.
Then test the computation model. Ask whether corrosion rates are stored as data or computed on demand from raw readings. Stored rates cannot be recomputed when the method changes, and the method will change. Ask whether a site's own originally reported rate can be retained beside the centrally recomputed one, because the reconciliation between the two is what earns local acceptance during the first year. Ask how negative rates are handled and whether that handling is a configurable, documented rule rather than a hidden default.
Finally, test the measurement type model with an ILI file and a dig report from the same location. If the system flattens them into one thickness series, it will produce confident and wrong remaining-life figures for the buried portion of your system. If it keeps them separate, links them by location and can produce an unbatched comparison for tool performance assessment, it understands what midstream data actually is. To review how your station, terminal and ILI data would consolidate under a single schema, request a demonstration at info@atlantisndt.com.
Why does standardising thickness data across sites usually fail?
Because it is attempted as a renaming exercise. A corporate tag scheme is imposed, sites are asked to re-key years of history into it, the effort stalls partway, and the fleet ends up with two incompatible schemes instead of one. Standardisation succeeds when the canonical identity is added alongside the local one as an alias, so field crews keep using the names painted on the pipe while the roll-up uses the corporate tag.
Can corrosion rates from different sites simply be averaged?
Not if the sites computed them. A short-term rate from the last two readings and a long-term regression rate across ten years are different quantities, and averaging them produces a number with no defensible meaning. The only reliable approach is to store raw readings centrally and compute every rate with one method, then report short-term and long-term separately as the inspection codes intend, rather than blending them into a single figure.
How should ILI results and manual UT readings live in the same history?
As distinct measurement types with their own tolerance and baseline, linked by location rather than merged into one series. ILI reports metal loss as a percentage of wall with a stated confidence and a sizing tolerance; manual UT reports absolute thickness at a point. A dig verification compares them and produces an unbatched comparison record that feeds tool performance assessment under API 1163, which is a different output than a corrosion rate.
What is the risk in letting each site set its own minimum thickness?
It is not that local judgement is wrong — pressure design minimum, structural minimum and administrative floors all have legitimate uses. The risk is that the basis is not recorded, so a consolidated remaining-life list ranks assets by an inconsistent yardstick. Store the t-min basis on the CML itself, with the code reference and the calculation inputs, and the roll-up can group like with like or recompute on a common basis on demand.
Do station piping and buried line pipe belong in the same system?
They belong in one system with different assessment logic. Above-ground station and terminal piping is inspected under API 570 with CML thickness trending; buried regulated pipeline is assessed under 49 CFR 192 subpart O or 195.452 by in-line inspection, pressure testing or direct assessment. Keeping them apart hides the fact that station piping is often the least monitored and most corroded part of a midstream footprint.
How is a multi-site migration done without losing history?
Import raw readings exactly as recorded, including the local CML identifier, the file they came from and the site's own computed values, then map identities as aliases rather than overwriting. Recompute rates centrally and store the recomputed value beside the original so discrepancies are visible instead of erased. A migration that discards the site's original numbers cannot be reconciled, and reconciliation is what earns the sites' trust in the new figure.
Built for any business that runs on operations
Most companies do not fail at their craft. They lose time, margin and goodwill in the gaps between the tools they use to run the place — a quoting spreadsheet that does not talk to the job sheet, a job sheet that does not reach accounts, and a compliance folder nobody can search when a client asks. Atlantis closes those gaps by putting the whole operation on one platform, so information is entered once and everything downstream stays in step.
What you can run on it
- Sales and CRM — leads, quotes, follow-ups and the pipeline that tells you what next month looks like.
- Projects and job costing — plan the work, track the hours and materials against it, and see the margin while the job is still live rather than at final account.
- Field and service teams — dispatch, schedules, mobile capture that works with no signal, and sign-off from site.
- Inventory and purchasing — stock, suppliers, reorder points and goods receipt, joined to the jobs that consume them.
- People — records, qualifications and licences with renewal reminders, timesheets, leave and payroll.
- Quality and documents — procedures and forms under revision control, with the audit trail an inspection or accreditation body actually asks for.
- Accounts — invoicing, expenses, multi-currency and the reporting your accountant stops chasing you for.
Affordable, accessible, fully customizable — and we mean each word
Affordable because the whole suite is included rather than sold to you a module at a time, and because implementation is done by people who have run operations rather than by a chain of subcontractors. Accessible because it runs in a browser and on a phone, works for a small team on day one, and does not need a specialist on staff to keep it alive. Fully customizable because your process is the thing that makes you competitive — the software should bend to it, not the other way round.
Industries we configure for
Service businesses and contractors, manufacturing and fabrication, trading and distribution, laboratories and testing houses, engineering consultancies, construction and facilities, and asset owners across energy, marine, aerospace and infrastructure. Inspection and testing is where we started, and it remains the sector we go deepest in — but the platform underneath is general-purpose, and most of what it does has nothing to do with inspection at all.
What happens when you get in touch
A short conversation, not a sales sequence. We ask how the business runs today and where it hurts, show you the platform doing that work, and send a written quote shaped to your region, your team size and the scope you actually need. No obligation, nothing to install first, and no pressure to decide on the call. Reach out and tell us what you are trying to fix.
Related: business management platform · inspection management software · choosing the right category of software · modules · by industry · asset integrity platform. Book a free consultation.