What a thickness record has to preserve when an LNG plant leaves its legacy system
A thickness reading history for LNG must retain every individual measurement with its date, technician, instrument, probe mode and method, plus every documented exclusion and its justification. Migration fails when a legacy system stored calculated corrosion rates instead of the readings behind them, or merged grid points into a single minimum, because neither can be rebuilt afterwards.
LNG assets make the exclusion record as important as the reading record. A full-containment storage tank built to API 620 Appendix Q has a 9% nickel inner shell that cannot be gauged in service at all; its CMLs are legitimately empty for the tank's entire operating life, and a migration that silently drops them destroys the evidence that the gap was deliberate. Cryogenic lines are gauged only during warm-up, so the interval between two readings may be a decade of plant time but only days of measurable ambient exposure. Insulated cold-service circuits are often screened with pulsed eddy current, which reports an averaged wall over a footprint of tens of square centimetres rather than a point thickness. Loading those averages into the same column as manual ultrasonic points produces corrosion rates that are artefacts of the technique change. The method field is what prevents it.
Source: Sources: API 620 Appendix Q and API 625 for cryogenic storage tank design and construction; API 510 and API 570 for in-service vessel and piping inspection; API RP 571 and API RP 583 for corrosion under insulation including cold service; ASME Section VIII Division 1, UCS-66 and the thickness-ratio credit of UCS-66.1; ASME Section V Article 23 for ultrasonic thickness measurement practice; NFPA 59A as incorporated by 49 CFR Part 193 for US LNG facilities; ASNT SNT-TC-1A for technician qualification.
| Legacy field as exported | What the new record must hold | What breaks if it is flattened |
|---|---|---|
| Corrosion rate (mm/yr), stored as a number | The two or more readings, dates and CMLs that produced it, with the rate recomputed on demand | The rate can never be audited, corrected or re-based; a single bad historical reading is frozen into the asset forever |
| Grid minimum (one value for a six-point grid) | Every point in the grid, each with its own coordinate and value | You cannot tell whether the minimum walked across the grid (general wastage) or stayed on one point (local pitting or erosion) |
| Thickness, units implied by the file | Value plus explicit unit, plus the design basis unit of the circuit | Metric EPC design and imperial operator practice collide; a 0.5 mm loss becomes 0.5 mil, or a 12.7 mm wall becomes 12.7 in |
| Blank cell | Either no inspection scheduled, or an exclusion with a coded reason, a decision owner and a date | Deliberate non-inspection of a cryogenic tank or a sealed vapour barrier looks identical to a missed CML in an audit |
| Inspector initials in a report header | Technician identity on each reading, with the certification level and method valid on that date | A campaign carried out by one technician cannot be isolated and re-examined when a systematic bias is later found |
| Screening survey result | Technique (manual UT, PEC, profile RT), probe mode, footprint and stated tolerance | Pulsed eddy current averages sit in the same column as point ultrasonic readings and manufacture step changes that look like real metal loss |
The migration is a records problem, not a data problem
Most LNG migration projects are scoped as a data transfer: count the rows in the old system, count them in the new one, declare success. That test passes on records that are already ruined. A legacy database that stored a computed corrosion rate but discarded the second-oldest reading will migrate every row intact and still leave you unable to answer the only question that matters, which is how you arrived at the remaining life you published last year.
The useful framing is evidentiary. Each thickness value is a claim about a piece of metal at a moment in time, and its worth depends entirely on the metadata that lets someone else test the claim. Who took it. On what instrument. Using which probe and which mode. Against which calibration block. At what surface temperature. Whether the coating was subtracted. Strip any of those and the value survives as a number while ceasing to be evidence.
LNG plants make this acute because they are long-lived and heavily documented from birth. A train commissioned in 1978 has manufacturer's data records, hydrotest reports, original mill certificates and baseline ultrasonic surveys, most of them in PDF and some of them on microfilm. The new system either becomes the place where a reading joins back to its mill certificate and its baseline, or it becomes another island and the migration has bought nothing.
Cryogenic service changes what a reading interval means
On a warm hydrocarbon line, elapsed time between two readings is a reasonable proxy for exposure. On a cryogenic line it is not. Metal at minus one hundred and sixty degrees is not corroding internally in any practical sense, and the external mechanism runs on the condensation and freeze-thaw behaviour of the insulation system rather than on process chemistry. The damage clock runs during commissioning, warm-ups, upsets and shutdowns, and it runs hard when a vapour barrier has been breached.
This has a direct consequence for the record. A history that stores only date and thickness cannot separate the two regimes, so the corrosion rate is a calendar average across a period that was mostly dormant and partly aggressive. What you need alongside each reading is the service condition at the time of measurement and, ideally, the operating state history of the circuit between readings, so an engineer can compute a rate against warm hours rather than clock years.
API RP 583 treats cold service explicitly and is the right basis for a corrosion-under-insulation strategy on an LNG plant, including the awkward fact that removing insulation and a vapour barrier to inspect can admit moisture and create the damage you were looking for. That trade-off is a documented engineering decision, and it belongs on the CML as an exclusion with a justification, not as an absence.
The tank you cannot gauge, and why its empty CMLs are evidence
A full-containment LNG tank has a 9% nickel steel inner shell inside a prestressed concrete outer container, with perlite and resilient blanket between them. There is no meaningful in-service ultrasonic access to the inner shell. The tank may run twenty-five or thirty years before a planned warm-up and internal entry, and some never see one. This is not a gap in your programme; it is the design.
Legacy systems handled this in two bad ways. Some created no CMLs at all for the inner tank, so a migration inherits an asset with no thickness structure and an auditor concludes the tank was never in scope. Others created CMLs and left them blank for three decades, indistinguishable from a missed inspection. The correct pattern is a populated CML carrying an explicit exclusion class, the technical basis, the accountable engineer and the event that will lift the exclusion, which is normally the next scheduled warm-up.
When that warm-up does happen, the system has to accept a burst of internal readings against CMLs that have been dormant since construction and compute a corrosion rate against a baseline that is thirty years old. That is only possible if the construction thickness, the plate identity and the original survey survived every earlier migration. It is the clearest argument there is for never discarding the oldest reading in a set.
Pulsed eddy current averages are not ultrasonic points
Insulated cold-service circuits are frequently screened without removing insulation, using pulsed eddy current or profile radiography. PEC does not measure a point. It reports an average remaining wall over a footprint that scales with insulation standoff, commonly tens of square centimetres, and it is quoted with a tolerance that is a percentage of wall rather than a fraction of a millimetre. It is an excellent screening tool and a poor trending tool.
The migration trap is mechanical. Legacy exports usually deliver one thickness column, so PEC results and manual ultrasonic results land in the same field. The new system then computes a corrosion rate between a 2019 PEC average and a 2023 UT point and produces a step change of one or two millimetres that reflects nothing except a change of technique. On an LNG plant, where insulation removal is restricted and PEC use is therefore heavy, this can contaminate a large fraction of the cold-service circuits at once.
The fix is to make method a mandatory attribute of the reading and to enforce technique compatibility in the rate calculation. Two readings of different techniques may sit in the same history and be plotted together, but they should not silently define a trend. An integrity engineer who wants to bridge them should have to say so and record why.
Where the warm side of an LNG plant actually corrodes
It is easy to write about LNG as if it were all cryogenic. In practice most of the thickness loss on a liquefaction plant is on the warm side: inlet facilities and feed gas lines carrying CO2 and any H2S, the acid gas removal unit with its amine circuit, regeneration overheads, the dehydration and mercury removal sections, refrigerant loops, fractionation columns and the flare and blowdown system. These are conventional mechanisms and they behave conventionally.
Amine service in particular repays granular history. Rich amine lines corrode at velocity-dependent rates that spike at elbows, tees and downstream of level control valves, and the regenerator overhead sees a different mechanism again. A CML-level record with per-point history lets you see the pattern; a circuit-level minimum tells you only that something somewhere got thinner. Migration decisions that collapse points into circuit minima to save rows destroy exactly the resolution that makes the amine unit manageable.
Regas terminals shift the picture again. Open rack vaporizers put aluminium alloy panels in continuous seawater, submerged combustion vaporizers put flue gas condensate against carbon steel, and the seawater intake system is its own corrosion problem. A thickness history designed only for a liquefaction train will not have the material and environment attributes to make sense of a regas facility, which matters if one system is meant to cover both ends of the chain.
Thickness loss spends your brittle-fracture credit before your pressure margin
On carbon steel equipment in LNG service that can see auto-refrigeration during depressurisation, the governing limit is often not pressure at all. ASME Section VIII Division 1 exempts material from impact testing based on curve assignment and thickness, and UCS-66.1 grants a reduction in minimum design metal temperature based on the ratio of required thickness to actual thickness. The thinner the wall becomes relative to what the pressure requires, the smaller that ratio and the more credit you hold.
The direction of travel is the point. As a vessel corrodes, actual thickness falls, the ratio of required to actual rises, and the MDMT credit shrinks. A vessel that was comfortably exempt at commissioning can drift toward its curve as it wastes, and the failure mode this exposes is brittle fracture on a cold depressurisation, not a leak from general thinning. Remaining-life arithmetic based on pressure alone will never show it.
This is why an LNG thickness history has to retain the specific actual thickness used in any past MDMT assessment, tied to the assessment document, rather than only the current minimum. When someone revisits the calculation five years later, they need to know whether the number in the original report was a point reading, a governing minimum or an averaged value, and which technician and instrument produced it. A migration that keeps only the latest minimum makes the old assessment unreproducible.
Reconstructing a corrosion rate the old system reported
The single most useful acceptance test for an LNG migration is also the cheapest. Pick twenty CMLs across cryogenic, amine and refrigerant service. For each, take the corrosion rate and remaining life the legacy system last published, then ask the new system to reproduce both from the migrated readings alone, with the legacy rate column hidden. Compare.
Expect disagreement, and treat disagreement as the finding rather than the failure. Most mismatches trace to one of a small set of causes: a legacy rate computed against nominal rather than the earliest measured thickness, a t-min that was typed as a constant and never revised after a re-rate, a unit conversion applied once too often, a reading that was superseded in the old system without the supersession being exported, or a rate that was manually overridden by an engineer years ago for a reason nobody recorded. Each of those is worth knowing about before go-live, not after.
Document the reconciliation as a deliverable of the migration, CML by CML, with a disposition for every mismatch. That document is what you show an auditor, an insurer or a new integrity manager when they ask why the numbers changed on the day the system changed. Without it, the migration itself becomes the unexplained step in your history.
How to evaluate the migration before you commit to it
Ask for a pilot on your worst data, not your best. Vendors will happily migrate a clean recent circuit. The circuits that decide the project are the ones from the plant's first decade: inconsistent CML naming, readings in imperial on a metric design, inspector initials only, and rate columns whose inputs are gone. Give the vendor a thousand of those rows and see what comes back, including what the system refuses to import and how it tells you.
Then test the shape of the record rather than the volume. Can it hold two readings on the same CML on the same day from different techniques? Can it store a reading flagged suspect and pending re-shoot without deleting it or letting it drive remaining life? Can it show the full audit trail of a value that was later corrected, including who corrected it and why? Can it reproduce, on demand, exactly what the remaining life was on a given past date, using only the data known at that date?
Finally, test the exclusions. Create a CML that cannot be measured, give it a reason, an owner and a review trigger, and confirm it appears in the inspection plan as a managed item rather than disappearing from every report. On an LNG plant, where a large fraction of the asset is deliberately not gauged, a system that cannot represent a justified absence is not a thickness history at all.
Can a legacy export of corrosion rates be loaded without the underlying readings?
It can be loaded, but it should be loaded as a legacy assertion, not as a calculated field. Keep the imported rate in a clearly separated column that the new system never recomputes and never uses for remaining life without an engineer's sign-off. The moment a rate is treated as live data, every future recalculation inherits an input nobody can inspect. LNG plants running since the 1970s often have three generations of such assertions stacked on one CML.
What happens to CMLs that were never measured because access was impossible?
They migrate as records with an exclusion reason, not as empty rows. An inner tank shell behind a prestressed concrete outer wall, a cold box interior, a spool inside a cryogenic vacuum jacket: each is a legitimate permanent or long-term exclusion, and the justification is the deliverable. Auditors and insurers do not object to a CML that was never gauged; they object to one that appears never to have been considered. The exclusion carries the decision, the basis and the review date.
How should pulsed eddy current screening data be stored alongside ultrasonic readings?
In the same history, in different lanes. PEC reports an average remaining wall over a footprint and is quoted with a tolerance far wider than a manual ultrasonic point. Store it with the technique, the footprint dimension and the stated tolerance, and never let a PEC value and a UT value form the two ends of a corrosion rate calculation. Use PEC to decide where insulation comes off, then let the follow-up ultrasonic points carry the trend.
Does API 653 govern thickness history for an LNG storage tank?
Generally not in the way it governs an atmospheric hydrocarbon tank. Full-containment LNG tanks are built to API 620 Appendix Q with API 625 as the system standard, and the inner tank is inaccessible in service, so course-by-course shell thickness trending in the API 653 sense has no in-service equivalent. A migration that forces the LNG tank into an API 653 data model creates plate and course records that will never be populated and audit findings that will never close.
Why does the reading date matter more on a cryogenic circuit than on a hot line?
Because plant time and exposure time diverge. A cryogenic circuit is gauged during warm-up or turnaround, so two readings ten years apart may bracket a period when the metal spent almost all of it at minus one hundred and sixty degrees, where the internal mechanism is effectively dormant and the external mechanism is driven by condensation cycles. Dividing loss by elapsed calendar years understates the rate during the warm periods that actually caused it.
Is API 510, 570 or 653 inspector training part of this offer?
No. Atlantis NDT delivers NDT training to ASNT SNT-TC-1A and ISO 9712 across UT, RT, MT, PT, ET, VT, PAUT and TOFD, plus ASNT Level III consulting, inspection management and reporting software, digital twins, 3D laser scanning and report validation. API inspector certification is administered by API's Individual Certification Programs and is obtained through them. The software records which certifications a technician held on a given reading date, whatever body issued them.
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.