What Changes When Thickness Readings Live on the 3D Model

The CML number is a pointer that points nowhere

A condition monitoring location is defined by API 570 as a designated area where repeat readings are taken, marked on inspection drawings so the same spot is measured over the life of the system. That definition works. What breaks is everything downstream: the CML becomes an identifier in a database, the drawing becomes a PDF, and the physical marking on the pipe fades under insulation cladding or a coat of paint applied three turnarounds ago.

So the thickness review happens in a table. Rows sorted by date, one line per CML, a corrosion rate column and a remaining-life column. The engineer reading it holds the plant layout in their head. When that engineer retires or moves units, the spatial knowledge, which CML sits at the bottom of the dead leg and which one is on the elbow that gets the impingement, leaves with them. The table survives. The meaning does not.

Thickness trending on asset geometry is the correction. Each reading is stored against a coordinate on a modelled component rather than only against a label in a register. The identifier still exists and still governs the record. What changes is that the identifier becomes redundant for the purpose of finding the spot, because the spot itself is visible on the model. The plant stops depending on one engineer's memory of where CML 14-B sits and what it was watching.

Corrosion rate stops being a column and becomes a surface

API 570 asks for two corrosion rates at every location: a long-term rate calculated from the original or earliest recorded thickness to the current one, and a short-term rate from the previous inspection to the current one. The governing rate is the higher of the two. Computed per CML and displayed per CML, this produces a column of numbers that have no stated relationship to each other, and the engineer supplies the relationships from memory.

Painted onto geometry, the same numbers describe shapes. General corrosion looks like an even wash across a component. Erosion-corrosion downstream of a control valve looks like a streak that fades with distance. Under-deposit attack at the six o'clock position on a horizontal run looks like a stripe. Corrosion under insulation clusters at penetrations, supports and low points where water collects, and API 571 places carbon and low-alloy steel CUI between 10 °F and 350 °F with the worst attack between 212 °F and 350 °F, so the geometry tells you which parts of the line sit inside that window.

None of those patterns are visible in a sorted table, because a table has no adjacency. Two readings 400 mm apart and two readings on opposite ends of a unit occupy neighbouring rows with equal weight. Adjacency is the information the spreadsheet throws away, and it is exactly the information that separates a general wastage problem from a localised mechanism needing a different inspection method.

Remaining life per location, and the one location that sets the interval

Remaining life is per location by definition: t-actual minus t-required, divided by the governing corrosion rate. A component does not have one remaining life. It has as many as it has monitored points, and the smallest one governs. In a spreadsheet, finding the smallest means sorting a column and trusting that the column is complete and that every reading in it belongs to the component you think it does.

On the geometry, the governing location is simply where the shading is darkest. That sounds trivial until you are looking at a crude unit with several thousand monitored points across hundreds of circuits, four days before a scope freeze, deciding which lines get a scaffold. The question is not what the average remaining life is. The question is which specific locations are short, and where they sit relative to each other.

The clustering matters as much as the minimum. Three short-life locations scattered across a unit are three separate repair decisions. Three short-life locations on consecutive spools of the same line are one replacement decision, and it is an entirely different conversation with the planner and the materials group. Spatial display is what makes those two cases look different at a glance, which is why circuit-level review beats point-level review as the place to start.

Next-inspection dates driven by the worst trend, not the average

API 570 caps the thickness-measurement interval at the lesser of the class maximum or half the calculated remaining life. Class 1 piping tops out at five years, Class 2 and Class 3 at ten, with external visual inspection running on its own schedule. The half-remaining-life rule means the interval is driven entirely by the shortest remaining life in the circuit. The average is irrelevant to the code.

That makes the governing location the single most consequential number in a thickness programme, and the one most easily lost. A location that starts trending badly between turnarounds changes the due date for the whole circuit. When that shift is a cell change in a spreadsheet, it gets noticed by whoever happens to re-sort the column. When it is a component changing colour on a plant view, it gets noticed by whoever opens the model.

The practical output is a due-date list generated from the worst trend in each circuit rather than from a fixed cycle inherited from the last revision. Feeding that list into scheduling, through an NDT inspection software layer, a work-order system, or both, is what turns a visualisation into an actual change in behaviour. A picture that nobody schedules against is a poster, and plants already have enough of those.

Handing a surveyor a walkthrough instead of a folder

Third-party review is where the twin earns visible time back. A jurisdictional inspector, insurance surveyor or client auditor arrives with a sampling plan: show me the history on these twelve locations, show me how you set this interval, show me the coverage on this circuit. Answering that from a document set means pulling isometrics, report PDFs, calculation sheets and a CML register, then explaining to a stranger how they relate to each other.

Answering it from a twin means clicking the component. The reading history, the two corrosion rates, the remaining life and the interval basis are attached to the thing being asked about. Reviewers stop spending their time on retrieval and spend it on the questions that matter, which is better for the site even when the answers are uncomfortable. Retrieval time is not a small share of an audit. It is most of it.

Be precise about status. The signed inspection report, the calculation and the inspector's certification remain the evidence. The twin is an index over that evidence, fast and not a substitute for it. Sites that present the model as the record invite exactly the challenge they were trying to avoid. If your programme needs that boundary set formally and defended in front of an auditor, that is what an ASNT Level III consulting engagement is for.

What thickness trending on geometry does not do

It does not take readings. A technician with a calibrated gauge, couplant and a current qualification still takes every measurement, and the quality of the twin is bounded by the quality of that work. Gauge calibration status, probe selection and surface preparation govern accuracy, which is why calibration records belong under active control in a system such as equipment calibration tracking rather than in a folder on somebody's desk.

It does not predict where new damage will start. Colour on a model is history rendered forward at the observed rate. A mechanism that has not yet initiated leaves no trace to extrapolate, and a rate calculated from two readings taken four years apart says nothing about what happened in month nine. Straight-line projection is an assumption, and the model displays that assumption with the same visual confidence as measured data, which is the honest hazard in every visualisation of this kind.

It does not create coverage. If a circuit has eleven CMLs on 200 metres of line, the twin shows eleven coloured points and a large volume of unmeasured pipe. Visualising that gap is genuinely useful, because it converts an invisible absence into an obvious one, but the fix is more inspection rather than more software. Nor does it replace the engineering judgement that decides where the next CML belongs.

Registration is the whole job

The technical difficulty of this use case is not rendering. It is reconciliation: matching a CML register written over twenty years by different people to components in a model captured last month. Line numbers get revised. Spools get replaced with different geometry. A CML described as the elbow downstream of PV-1204 has to become a specific point on a specific elbow. That mapping is manual work, and it is where the schedule goes.

Geometry accuracy is the easy half. Terrestrial laser scanning of congested industrial environments lands in the 1 mm to 3 mm band, and modern scanners capture on the order of a million points per second. That is more than adequate for this purpose. The tolerance that actually matters is whether a reading sits on the right component, not whether a flange face is modelled to a millimetre of true position.

Two decisions save the most time. First, register at circuit level before point level, so a partially reconciled unit is still usable by planners. Second, accept that some historical CMLs cannot be located and mark them as unreconciled rather than guessing. A twin with 80 percent of points placed and 20 percent honestly flagged is trustworthy. One with every point placed and a fifth of them wrong is worse than the spreadsheet it replaced.

Where this sits next to the IDMS and the reporting stack

The twin is a view, not a database. Thickness records, corrosion-rate calculations, interval logic and inspection history belong in an inspection data management system, which is also where the audit trail lives. The twin reads from it. We set out the division of responsibility in detail on digital twin vs IDMS, because the failure mode of treating the visualisation as the system of record is common, expensive, and slow to unwind once auditors notice.

Upstream, readings arrive from field data capture. The tighter that path, from technician entering a reading against a CML, to the reading landing in the record, to the record updating the model, the more current the picture stays. Where sites are still re-typing values from paper into a spreadsheet before anything reaches the database, the reporting software layer is the constraint rather than the twin.

Start with one unit and one damage mechanism. A crude preheat train with sulfidation, or an insulated line network with CUI, gives enough monitored points to prove whether spatial trending changes a decision your team would otherwise have made differently. If it changes nothing, the pilot has told you something useful for the cost of a scan. Talk to us about scoping that pilot on a unit you already know well.

Request a consultation