A refinery turnaround produces inspection reports on a defined population of vessels and piping circuits within a fixed outage window. A pipeline integrity program produces a continuous, decades-long stream of data across hundreds or thousands of miles of buried and above-ground pipe — in-line inspection (ILI) runs, direct assessment digs, hydrostatic test records, and direct examination NDT results from excavations — all of which has to reconcile against a single, continuously updated integrity model for the line. Companies providing integrity services to pipeline operators, or operators managing this work internally, need a system built around that reality, not a generic job-tracking tool repurposed for pipeline work.
\nPHMSA (the Pipeline and Hazardous Materials Safety Administration) regulates pipeline integrity management under 49 CFR Part 192 for gas transmission and gathering lines and Part 195 for hazardous liquid pipelines. Both frameworks require operators to identify High Consequence Areas (HCAs), assess threats to pipeline integrity, and run structured integrity management programs with defined reassessment intervals — for gas transmission lines in HCAs, the baseline reassessment interval is a maximum of seven years under Part 192, subject to the specific risk-based adjustments the operator's program justifies. API 1163, \"In-Line Inspection Systems Qualification,\" sets the standard for how ILI tool performance is qualified and how ILI data quality is validated — which matters enormously because everything downstream, from anomaly identification to repair prioritization, depends on the reported accuracy of the ILI vendor's tool for that specific run. A system supporting this work needs to track ILI tool qualification and reported tolerances alongside the actual anomaly data, not just the anomaly list on its own.
\nOn top of PHMSA's federal framework, API 1160 (Managing System Integrity for Hazardous Liquid Pipelines) and the broader integrity management practices referenced across API RP 1173 (Pipeline Safety Management Systems) shape how operators structure their programs. None of these standards care what software you use — but every one of them drives a documentation and data-traceability expectation that a well-built system needs to satisfy by design, not by heroic effort during an audit.
\nPipeline data is fundamentally linear — every anomaly, every dig, every ILI feature is located by distance along the line (often reconciled to a station or engineering stationing system, sometimes tied to GPS coordinates as well) rather than as an independent point location. A system built for plant or facility inspection, where every asset has a fixed tag number and location, doesn't naturally support this — pipeline integrity software needs linear referencing as a core data structure, with the ability to correlate features found in different ILI runs or different excavation digs to the same physical location on the line even as the referencing system gets refined over time.
\nEach ILI run — magnetic flux leakage (MFL), ultrasonic (UT) tools, or geometry/deformation tools — produces a feature list that has to be correlated against prior runs to calculate corrosion growth rates and against dig verification data to validate the ILI vendor's sizing accuracy. This correlation exercise is one of the most data-intensive and error-prone parts of pipeline integrity work when it's done manually across spreadsheets pulled from different ILI vendor formats over multiple run cycles.
\nWhen an ILI-reported anomaly gets excavated for direct examination, the field NDT work — UT wall thickness measurement, MT for crack-like indications, sometimes phased array for more detailed crack sizing — needs to feed back into the same system that holds the original ILI call, so the integrity engineer can compare reported vs. actual and adjust confidence in that ILI tool's performance for the rest of the run. Treating the dig NDT report as a standalone document disconnected from the ILI feature record defeats the entire purpose of the verification dig.
\nOnce an anomaly is confirmed and classified — immediate repair condition, scheduled repair, or monitored — PHMSA timelines apply (for gas transmission, immediate repair conditions generally require action within five days of discovery per Part 192 criteria, with scheduled conditions carrying longer but still defined windows). A system supporting integrity work needs to track these deadlines explicitly against each confirmed anomaly, not rely on an engineer's memory or a separate compliance spreadsheet running in parallel to the technical data.
\nExternal corrosion — one of the primary threats pipeline integrity programs manage — depends on cathodic protection system performance and coating condition, both of which get surveyed separately (close-interval surveys, DCVG, ACVG) from ILI and direct examination work but feed into the same overall threat assessment for a given segment. A system that silos CP survey data away from ILI and dig data makes integrated threat assessment — which is the actual point of an integrity management program — much harder than it needs to be.
\nA meaningful share of the US pipeline network, particularly older gas transmission and hazardous liquid lines installed before modern seam weld quality controls, carries longitudinal seam types — low-frequency electric resistance welded (LF-ERW), lap-welded, or flash-welded seams among them — with known susceptibility to seam-related threats like selective seam corrosion or long-seam fatigue cracking. PHMSA's integrity management rules require operators to specifically consider seam type and vintage when selecting ILI technology, since not every ILI tool detects every seam threat with equal reliability — an MFL tool optimized for corrosion detection isn't necessarily the right tool for a crack-like seam threat, which typically calls for a UT crack-detection tool or electromagnetic acoustic transducer (EMAT) technology instead. A system managing pipeline integrity data needs pipe seam type and vintage as a queryable attribute at the segment level, because that single data point drives which ILI technology and which direct examination NDT methods are actually appropriate for a given stretch of line — treating every segment as interchangeable for tool selection purposes is a documented cause of missed threats industry-wide.
\nPipeline integrity work rarely involves just one company end to end — an ILI vendor runs the in-line tool and delivers a feature list, a separate integrity engineering firm may perform the threat assessment and prioritize digs, and an NDT services company performs the actual field verification at each dig site. Each of these parties typically uses its own internal systems, and the data handoff points between them are exactly where information gets lost, reformatted with errors, or delayed. A services company that can accept ILI feature data in the vendor's native export format, correlate it automatically to prior runs and dig history inside its own system, and hand back structured direct examination results in a format the integrity engineering firm can ingest directly — rather than a standalone PDF report requiring manual re-entry on the other end — becomes a measurably easier company for an operator to work with across a multi-vendor integrity program. This kind of interoperability is often an underrated factor in how pipeline operators evaluate and retain integrity services providers over multi-year program relationships.
\nFor an NDT or integrity services company supporting pipeline operators rather than operating the line itself, the practical challenge is usually managing multiple clients' data cleanly — each with different pipeline systems, different ILI vendor relationships, and different reporting formats — while maintaining the crew certifications, equipment calibration, and job costing discipline that applies to any NDT operation. This is where a purpose-configured ERP system earns its keep: the same platform handling technician SNT-TC-1A certification tracking and equipment calibration for a refinery turnaround crew can be extended to handle dig-site scheduling, direct examination data capture, and client-specific reporting formats for pipeline integrity work, rather than running an entirely separate, disconnected system for this line of business.
\nExcavation and direct examination work on a buried pipeline right-of-way involves logistics that plant-based inspection work simply doesn't: landowner notification and access agreements, agricultural or seasonal access restrictions in some regions, one-call/utility locate coordination before any excavation, and often significant travel between dig sites spread across long linear distances rather than a compact plant footprint. Scheduling software built for facility-based inspection work — where every job happens at a fixed, known-access site — doesn't map cleanly onto this reality. A system supporting pipeline integrity field work benefits from tracking access agreement status, locate ticket numbers and their expiration windows (most one-call locate tickets are valid for a limited period before requiring renewal), and realistic travel time between dispersed dig sites as explicit scheduling constraints, the same way certification and calibration status function as hard constraints elsewhere in NDT operations.
\nBeyond routine integrity management documentation, PHMSA reporting requirements include incident and safety-related condition reports under defined timelines, and state pipeline safety agencies operating under certification from PHMSA often layer their own reporting expectations on top of the federal baseline. When a reportable condition is identified — whether from an ILI call, a direct examination finding, or an in-service event — having the supporting integrity data (inspection history, prior run comparisons, repair history at that location) already organized and retrievable inside one system meaningfully shortens the time it takes to assemble an accurate, complete regulatory submission. Operators and the integrity services companies supporting them that discover during a live reporting deadline that key supporting data is scattered across old spreadsheets, email attachments, and a prior contractor's now-inaccessible files are working under exactly the wrong conditions to produce a careful, accurate submission.
\nA dig crew performing direct examination in the field needs a fast, reliable way to capture UT thickness grids, MT indications, and photographic documentation on-site — often in remote right-of-way locations with limited connectivity — and have that data structured well enough to flow directly into both the client's integrity report and the ERP's job record without manual re-entry. This is precisely the gap purpose-built NDT reporting software closes, particularly when it supports offline data capture that syncs once the crew has connectivity again, which matters enormously for pipeline right-of-way work where cell coverage is often unreliable.
\nMost pipeline operators maintain a GIS layer representing their system's geographic footprint, and integrity data ultimately needs to reconcile against that same spatial reference so that a corrosion feature, a dig location, or a repair record can be viewed in context alongside population density (relevant to High Consequence Area determination), waterway crossings, and other pipelines or infrastructure in the vicinity. A services company whose data stays purely in a linear-referencing, station-based format without any GIS export capability creates extra translation work for the operator's own integrity team every time that data needs to be layered into a broader system view — while a system that can export located features in a standard geospatial format removes a recurring friction point in what's usually a long-term, multi-year client relationship built on regularly recurring data handoffs.
\nPipeline integrity work rewards precision and traceability more than almost any other NDT services segment, because the consequence of a missed repair deadline or a mishandled ILI-to-dig correlation isn't a bad report — it's a real risk to a line carrying hazardous liquid or gas through populated areas. Building operations on a system that natively understands linear referencing, ILI run management, and regulatory deadline tracking — integrated with the same certification and calibration discipline that governs every other NDT service line — is what separates an integrity services company that scales cleanly from one perpetually reconstructing data from vendor spreadsheets. Getting the underlying qualification structure right for crews performing this specialized work is also where ASNT Level III consulting and rigorous technician training pay dividends well beyond the software layer.
\nPipeline integrity work rewards the same operational rigor that underpins every other NDT service line:
\n\nAtlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.
\n