Non-destructive examination
For NDE analysts who own the wall thickness. Take the reading or stream the scan, and one compute engine turns it into a corrosion rate, a remaining life, and the verdict integrity reads.
Built in, not bolted on
Each layer of the wall carries its own reading, corrosion rate, and ASME basis, then hands the remaining life to integrity.
The outer wall
The coupon, cut free
The wall in section
Capabilities
03 layers · scroll to stack
Short, long, and maximum rates on one engine, so every analyst reaches the same number.
Minimum wall to ASME B31.3 or VIII Div 1, then the years left before it runs out.
The threshold date per circuit, with the critical band flagged for review today.
Spectra drafts circuits and CML points from the drawing, for an engineer to approve.
UT, PAUT, TOFD, RT, MT, PT, and ET land on the same CML, one timeline not seven.
Automated corrosion maps import native, so coverage is the component, not a few points.
Permanent sensors and automated scanners stream in and reconcile to the CML on one engine.
Vision assist flags indications on imported scans for the analyst to confirm, never auto-called.
Due dates roll up into work packages, the digital clipboards a crew takes to the field as one session.
For the NDE analyst
Real screens from the platform, not mockups
Grounded by design
Proof
Standards referenced
Explore
03 related modules
Evaluation path
Answers
UT straight-beam and thickness, PAUT, TOFD, RT including digital and computed radiography, MT, PT, and ET, plus screening methods like guided-wave UT and pulsed eddy current. Every method attaches to the same CML and asset record.
No. intelliNDT is the data-and-compute layer, not the instrument. The encoded scanners, crawlers, and permanent sensors you already run stream their readings in, and the module reconciles them to the CML on one engine. Manual readings and streamed data sit side by side.
The CML Corrosion Rate Calculator computes short-term, long-term, and maximum corrosion rates per point using API 510 and API 570 methodology, with scope selectable at the point, circuit, asset group, or program level.
The CML tMin Calculator applies ASME B31.3 for piping circuits or ASME VIII Div 1 for pressure vessels, drawing on the configured design basis for each CML point to produce a code-grounded minimum thickness value.
Yes. The CML Thickness Survey wizard supports offline sync, readings queue locally and push to the server on reconnect, keeping field work uninterrupted when signal is unavailable.
It drafts equipment references, corrosion circuits with component type, service fluid, operating conditions, and damage mechanisms, plus CML point locations for engineer review. Nothing writes to the program until the engineer approves the reviewed rows.
The CML Anomaly Detection calculator runs physical checks (impossible wall growth, non-physical values) and statistical checks (extreme rate outliers relative to point history) on every reading before it can be approved into the integrity dataset.
Due dates, set by RBI or by code interval, roll up into work packages, the digital clipboards a crew takes to the field, such as a turnaround piping NDT package. Each package is assigned as a field session the crew captures offline and syncs on reconnect.
Yes. Forecasting projects the threshold date per circuit, maps each risk band to an intervention of inspect, repair, or replace, and places the cost in the fiscal year it lands. A what-if run compares a baseline corrosion rate against a mitigated one, such as an inhibitor, and reports the deferred cost between them.
Optimization flags redundant CMLs where rates track together and gaps where a damage mechanism is unmonitored. It will not let you remove a CML that is critical or below a statutory remaining-life threshold, so the safety-driven points stay protected.
Both directions. A visual finding in intelliINSPECT can call up an NDE survey here, and approved CML readings flow on to intelliINTEGRITY, where they trigger assessments and update the RBI loop without export or re-keying.
See one asset workflow, from field record to audit evidence.
