Maintenance / Compare approaches

Pipeline Inline Inspection (ILI) Pigging Tally Alignment, Excavation Dig-Sheet Verification, and Repair Closure Governance

By Vikasraj YadavPublished Editorially reviewed 18 min read

For Maintenance lead, operations manager and ERP/EAM owner

TL;DR — what you’ll learn

  • Midstream pipeline operators running Magnetic Flux Leakage (MFL), Ultrasonic (UT), or Caliper smart pigs receive vendor pipe tallies containing thousands of metal-loss and dent features whose raw odometer distances drift by $0.1\%\text{--}0.4\%$ against field GIS chainages.
  • A governed **Inline Inspection (ILI) reconciliation register** anchors vendor pipe tallies to Above-Ground Markers (AGMs) and upstream/downstream reference girth welds (`GW`), applying joint-specific odometer scaling so excavation crews expose the exact target pipe joint on the first dig.
  • Every anomaly is evaluated under ASME B31G / Modified B31G / RSTRENG and ASME B31.8S / API 1160 to classify **Immediate**, **Scheduled / One-Year**, or **Monitored** response clocks, enforce temporary operating pressure reductions ($\text{TMP}$) when predicted burst pressure falls below $\text{MAOP}$, and close the loop with field Phased-Array Ultrasonic Testing (PAUT) **Unity Plots** and sleeve/recoating certificates.
  • Software aligns odometer tallies, computes code-based remaining strength, and tracks repair deadlines, but never overrides pipeline SCADA pressure relief setpoints or substitutes for a qualified Pipeline Integrity Engineer's fitness-for-service signoff.
AI-generated illustration of an oil and gas processing facility with steel columns, pipework and maintenance walkways
Illustration: NextEdge Labs, generated with AI. An illustrative setting, not a client facility.

Topics: inline inspection pigging anomaly software, midstream oil and gas software, pipeline maintenance software.

Pipeline integrity managers and midstream maintenance teams ask a recurring execution question: How should pipeline operators reconcile smart-pig Inline Inspection (ILI) vendor tally runs, odometer girth-weld alignment, excavation dig-sheet verification, and sleeve/recoating repair closure? Distinct from pipeline volumetric imbalance accounting (O019) and in-plant static vessel mechanical integrity (O101), this workflow governs the end-to-end pigging integrity loop: from launcher/receiver trap run acceptance and odometer-to-GIS girth-weld matching through excavation dig-sheet generation, in-ditch NDE verification, unity-plot vendor performance validation, and permanent repair closure.

Without a structured ILI alignment and dig-sheet register, midstream operators suffer three high-cost integrity breakdowns:

  1. Odometer slippage and "missed-joint" dry holes: A $180\text{ km}$ smart-pig run accumulates $250\text{ m}$ of odometer wheel slippage across wax deposits or girth welds. If the dig sheet uses raw pig distance from the launcher instead of scaling between the nearest AGM and the immediate upstream/downstream girth welds (GW), excavation crews dig up the wrong pipe joint $12\text{ m}$ away—wasting $₹12\text{--}18\text{ lakh}$ per bell-hole excavation.
  2. Untracked regulatory repair clocks and temporary pressure derates: When the preliminary or final ILI report identifies an Immediate Condition (such as metal loss $\ge 80%$ of nominal wall thickness or predicted burst pressure below $\text{MAOP}$), PHMSA 49 CFR 192/195 and ASME B31.8S require immediate pressure reduction (typically to $80%$ of the pressure at discovery or safe operating pressure) and timely excavation. Tracking these clocks in email threads risks statutory violation.
  3. Unreconciled field NDE vs ILI unity plots: Excavation technicians measure actual corrosion pit depth and axial length in the ditch with laser profilometry or Phased-Array UT (PAUT) and install a Type-B sleeve, but the as-found dimensions are never fed back into an API Std 1163 Unity Plot. As a result, systemic ILI sizing bias goes undetected across the remaining unexcavated anomalies on the pipeline.

Scope and pipeline integrity engineering boundary

An ILI anomaly and dig-sheet software register is an alignment, remaining-strength calculation, work-package tracking, and NDE feedback system; it is not an autonomous pipeline pressure-control system or a substitute for licensed engineering judgment.

  • Pipeline Integrity Engineer authority: Selection of the remaining-strength assessment method (Original ASME B31G, Modified B31G $0.85,dL$, or RSTRENG effective area river-bottom profile), corrosion growth rate ($\text{CGR}$) assumptions, temporary pressure reduction ($\text{TMP}$) limits, and repair method selection (recoating, composite wrap, Type-A reinforcing sleeve, or Type-B pressure-containing welded sleeve) must be reviewed and signed off by a qualified Pipeline Integrity Engineer.
  • No automated SCADA setpoint manipulation: While the software calculates the required temporary operating pressure ceiling when an Immediate anomaly is logged, any actual discharge pressure reduction at pump or compressor stations must be executed by authorized Pipeline Control Room Controllers under formal Management of Change (MOC) / abnormal operating procedures.
  • Compliance with governing pipeline standards: Workflow logic must reflect API Std 1163 (In-line Inspection Systems Qualification), ASME B31.8S (Managing System Integrity of Gas Pipelines), API Std 1160 (Managing System Integrity for Hazardous Liquid Pipelines), ASME B31G, and U.S. DOT PHMSA 49 CFR Parts 192 and 195 (or equivalent national pipeline regulations such as PNGRB T4S in India).
Integrity Phase Primary Data Artifact Alignment / Engineering Formula Acceptance / Action Threshold Audit & Closure Evidence
1. Pigging Run Qualification Trap Launch/Receive Log & Run Quality Sheet Velocity window ($0.5\text{--}4.0\text{ m/s}$); working channel coverage ($\ge 97\%$) Reject run segments where pig speed exceeded MFL magnetization saturation limit Signed API 1163 Run Acceptance Certificate
2. Odometer & Girth-Weld Alignment Master Pipe Tally & AGM Reference Table $d_{\text{corr}} = d_{\text{ILI,GW}} \times \left(\frac{L_{\text{GIS,joint}}}{L_{\text{ILI,joint}}}\right)$ Three upstream & three downstream joint lengths must match within $\pm 0.15\text{ m}$ in the ditch Excavation Dig Sheet with clock orientation ($12:00$ top-of-pipe)
3. Anomaly Severity & Repair Clock Remaining Strength Ledger (Modified B31G / RSTRENG) $P_{\text{safe}} = \frac{P_f}{\text{SF}}$; Immediate if $d/t \ge 0.80$ or $P_f \le 1.10 \times \text{MAOP}$ Immediate pressure reduction ($\le 80\%$ discovery pressure) + immediate dig mobilization Time-stamped Discovery Date, TMP order, and regulatory clock tracker
4. Ditch Verification & Unity Check In-Ditch PAUT / Laser Scan & Sleeve Weld Pack $\Delta(d/t) = (d_{\text{field}} - d_{\text{ILI}})/t_{\text{nom}}$ vs $\pm 10\%\,t$ at $80\%$ confidence Recalibrate remaining tally if $>20\%$ of digs exceed vendor sizing tolerance Unity Plot, NDE clearance of Type-B sleeve, and MAOP restoration signoff
Figure 1 — Operational governance and handoff sequence: Pipeline Inline Inspection (ILI) Pigging Tally Alignment, Excavation Dig-Sheet Verification, and Repair Closure Governance
  1. Step 1 — Record intake & baseline identification: Midstream pipeline operators running Magnetic Flux Leakage (MFL), Ultrasonic (UT), or Caliper smart pigs receive vendor pipe tallies containing thousands of metal-loss and dent features whose raw odometer distances drift by $0.1\%\text{--}0.4\%$ against field GIS chainages.
  2. Step 2 — Cross-system reference & custody linkage: A governed **Inline Inspection (ILI) reconciliation register** anchors vendor pipe tallies to Above-Ground Markers (AGMs) and upstream/downstream reference girth welds (`GW`), applying joint-specific odometer scaling so excavation crews expose the exact target pipe joint on the first dig.
  3. Step 3 — Exception quarantine & authority check: Every anomaly is evaluated under ASME B31G / Modified B31G / RSTRENG and ASME B31.8S / API 1160 to classify **Immediate**, **Scheduled / One-Year**, or **Monitored** response clocks, enforce temporary operating pressure reductions ($\text{TMP}$) when predicted burst pressure falls below $\text{MAOP}$, and close the loop with field Phased-Array Ultrasonic Testing (PAUT) **Unity Plots** and sleeve/recoating certificates.
  4. Step 4 — Verified disposition & audit trail closure: Software aligns odometer tallies, computes code-based remaining strength, and tracks repair deadlines, but never overrides pipeline SCADA pressure relief setpoints or substitutes for a qualified Pipeline Integrity Engineer's fitness-for-service signoff.

Odometer-to-GIS alignment and dig-sheet mathematics

Smart pigs measure axial distance using spring-loaded odometer wheels rolling along the internal pipe wall. Over long runs, wheel wear, paraffin slip, and weld bounce cause the raw odometer distance $X_{\text{ILI,raw}}$ to diverge from true survey chainage $X_{\text{GIS}}$. A two-tier scaling algorithm eliminates this error before generating an excavation dig sheet:

  1. Macro AGM segment scaling: Between two GPS-surveyed Above-Ground Markers (or mainline block valves) $\text{AGM}_{n-1}$ and $\text{AGM}_n$, the macro scale factor is:

$$k_{\text{macro}} = \frac{X_{\text{GIS}}(\text{AGM}n) - X{\text{GIS}}(\text{AGM}{n-1})}{X{\text{ILI,raw}}(\text{AGM}n) - X{\text{ILI,raw}}(\text{AGM}_{n-1})}$$

  1. Micro joint-by-joint girth-weld scaling: Once the target pipe joint bounded by Upstream Reference Girth Weld $\text{GW}u$ and Downstream Reference Girth Weld $\text{GW}d$ is matched against the historical construction or prior-ILI master joint tally ( checking the sequence of the $3$ preceding and $3$ succeeding pipe joint lengths to form an unmistakable "bar-code" signature), the local joint scale factor $k{\text{joint}}$ and corrected anomaly offset $d{\text{corr}}$ from $\text{GW}_u$ are:

$$k_{\text{joint}} = \frac{L_{\text{GIS,joint}}}{L_{\text{ILI,joint}}}, \qquad d_{\text{corr}} = d_{\text{ILI,raw}} \times k_{\text{joint}}$$

This ensures that when the excavation crew locates $\text{GW}u$ in the trench and pulls a steel tape downstream by $d{\text{corr}}$ at the specified circumferential clock position (e.g., $05:30\text{ o'clock}$ looking downstream), they land directly on the corrosion cluster.

Figure 2 — Control checkpoint and exception ownership matrix (O105): Illustrative verification gates.
  • Primary control scope: inline inspection pigging anomaly software across maintenance and connected ERP/EAM records.
  • Segregation boundary: Operational status updates never auto-close engineering, safety, or finance sign-off gates.
  • Verification cadence: Reconcile open exceptions, overrides, and late adjustments at each shift or period close.

Illustrative worked example: $24\text{-inch}$ crude pipeline ILI alignment, Immediate dig, PAUT unity check, and Type-B sleeve closure

All figures below are illustrative and synthetic. Consider a $184.50\text{ km}$, $24\text{-inch}$ ($D = 609.6\text{ mm}$ outside diameter, nominal wall thickness $t_{\text{nom}} = 12.70\text{ mm}$, API 5L Grade X65 with Specified Minimum Yield Strength $\text{SMYS} = 448.0\text{ MPa}$, design factor $F = 0.72$, Maximum Allowable Operating Pressure $\text{MAOP} = 96.0\text{ barg}$ [$9.60\text{ MPa}$]) crude oil transmission pipeline (LINE-24-WEST) inspected by a high-resolution axial MFL + geometry smart pig.

Step 1: Macro AGM and local girth-weld odometer reconciliation

Between Launch Trap KP 0.000 ($X_{\text{GIS}} = 0.00\text{ m}$) and Above-Ground Marker AGM-142 ($X_{\text{GIS}} = 112,420.00\text{ m}$), the raw ILI odometer records $X_{\text{ILI,raw}} = 112,689.81\text{ m}$ (an accumulated raw odometer over-read of $+269.81\text{ m}$, or macro scale factor $k_{\text{macro}} = 112,420.00 / 112,689.81 = 0.9976057$).

Within that segment, the vendor tally flags a severe external corrosion cluster ANOM-4418 on Pipe Joint PJ-9410, bounded by Upstream Girth Weld GW-9410 and Downstream Girth Weld GW-9411:

  • GIS / Master Joint Tally for PJ-9410: Upstream weld GW-9410 is at true chainage $X_{\text{GIS}}(\text{GW-9410}) = 108,240.500\text{ m}$; Downstream weld GW-9411 is at $X_{\text{GIS}}(\text{GW-9411}) = 108,252.380\text{ m}$. True joint length:

$$L_{\text{GIS,joint}} = 108,252.380 - 108,240.500 = 11.880\text{ m}$$

  • Raw ILI Odometer Tally for PJ-9410: GW-9410 is recorded at $108,500.120\text{ m}$ and GW-9411 at $108,512.030\text{ m}$. Raw ILI joint length:

$$L_{\text{ILI,joint}} = 108,512.030 - 108,500.120 = 11.910\text{ m}$$

  • Local joint scale factor and exact dig-sheet target: Anomaly ANOM-4418 is reported at a raw odometer offset $d_{\text{ILI,raw}} = 4.650\text{ m}$ downstream of GW-9410 at $05:30\text{ o'clock}$. The software computes:

$$k_{\text{joint}} = \frac{11.880}{11.910} = 0.9974811$$

$$d_{\text{corr}} = 4.650 \times 0.9974811 = 4.638\text{ m}\text{ downstream of }\text{GW-9410}$$

$$X_{\text{GIS}}(\text{ANOM-4418}) = 108,240.500 + 4.638 = 108,245.138\text{ m}$$

Had the field crew dug at the raw unscaled ILI distance ($108,500.120 + 4.650 = 108,504.770\text{ m}$), they would have excavated $259.632\text{ m}$ downstream of the actual defect ($22$ pipe joints away).

Step 2: Modified B31G remaining strength, Immediate classification, and temporary pressure derate

For ANOM-4418, the ILI vendor reports peak metal-loss depth $d_{\text{ILI}} = 7.37\text{ mm}$ ($d_{\text{ILI}}/t_{\text{nom}} = 7.37 / 12.70 = 58.03%$) and axial corrosion length $L_{\text{ILI}} = 165.0\text{ mm}$. Using the Modified ASME B31G ($0.85,dL$) equations with flow stress $S_{\text{flow}} = \text{SMYS} + 68.95\text{ MPa} = 448.0 + 68.95 = 516.95\text{ MPa}$:

  1. Dimensionless length parameter $z$:

$$z = \frac{L^2}{D \cdot t_{\text{nom}}} = \frac{165.0^2}{609.6 \times 12.70} = \frac{27,225.0}{7,741.92} = 3.51657$$

  1. Folias bulging factor $M$ (for $z \le 50$):

$$M = \sqrt{1 + 0.6275,z - 0.003375,z^2} = \sqrt{1 + 0.6275(3.51657) - 0.003375(12.36626)}$$

$$M = \sqrt{1 + 2.20665 - 0.04174} = \sqrt{3.16491} = 1.77902$$

  1. Predicted failure hoop stress $S_f$ and burst pressure $P_f$:

$$S_f = S_{\text{flow}} \times \left[\frac{1 - 0.85,(d/t_{\text{nom}})}{1 - 0.85,(d/t_{\text{nom}})/M}\right] = 516.95 \times \left[\frac{1 - 0.85(0.580315)}{1 - 0.493268 / 1.77902}\right]$$

$$S_f = 516.95 \times \left[\frac{0.506732}{1 - 0.277269}\right] = 516.95 \times \left(\frac{0.506732}{0.722731}\right) = 516.95 \times 0.701135 = 362.45\text{ MPa}$$

$$P_f = \frac{2 \cdot S_f \cdot t_{\text{nom}}}{D} = \frac{2 \times 362.45 \times 12.70}{609.6} = 15.102\text{ MPa}; (151.02\text{ barg})$$

  1. Safe Operating Pressure $P_{\text{safe,ILI}}$ (applying pipeline safety factor $\text{SF} = 1 / F = 1 / 0.72 = 1.3889$, or multiplier $0.72$) and added $5\text{-year}$ corrosion allowance ($2.0\text{ mm}$ growth to $d_{\text{proj}} = 9.37\text{ mm}$, $73.78%$ wall): At current ILI depth, $P_{\text{safe,curr}} = 0.72 \times 151.02 = 108.73\text{ barg}$, but when accounting for the vendor depth sizing tolerance ($+10%,t_{\text{nom}} = +1.27\text{ mm}$, giving upper-bound depth $d_{\text{UB}} = 7.37 + 1.27 = 8.64\text{ mm}$, or $d_{\text{UB}}/t_{\text{nom}} = 68.03%$), the upper-bound failure stress drops to:

$$S_{f,\text{UB}} = 516.95 \times \left[\frac{1 - 0.85(0.680315)}{1 - 0.578268 / 1.77902}\right] = 516.95 \times \left(\frac{0.421732}{0.674951}\right) = 323.02\text{ MPa}$$

$$P_{f,\text{UB}} = \frac{2 \times 323.02 \times 12.70}{609.6} = 13.459\text{ MPa}; (134.59\text{ barg}), \qquad P_{\text{safe,UB}} = 0.72 \times 134.59 = 96.90\text{ barg}$$

With a local external corrosion growth rate of $0.45\text{ mm/yr}$ since the pig run ($6\text{ months}$ to report delivery $= +0.225\text{ mm}$, bringing effective upper-bound depth to $8.865\text{ mm}$ [$69.80%$]), the safe pressure at discovery drops to $P_{\text{safe,disc}} = 94.1\text{ barg} < \text{MAOP}$ ($96.0\text{ barg}$). Under company integrity rules and 49 CFR 195.452 / API 1160, the register classifies ANOM-4418 as an Immediate Repair Condition, logs Discovery Date $T_0$, enforces an immediate temporary operating pressure ceiling of $\text{TMP} = 0.80 \times P_{\text{op,disc}} = 0.80 \times 92.5 = 74.0\text{ barg}$, and generates Excavation Work Package DIG-2026-019.

Step 3: In-ditch PAUT verification, Unity Plot check, and Type-B sleeve closure

Excavation crew exposes PJ-9410 at $X_{\text{GIS}} = 108,245.14\text{ m}$, confirms joint length $11.88\text{ m}$ between GW-9410 and GW-9411, and locates the disbonded tape coating blister within $18\text{ mm}$ of the predicted $4.638\text{ m}$ tape mark.

  • Field PAUT & 3D laser scan: Actual maximum pit depth is measured at $d_{\text{field}} = 7.82\text{ mm}$ ($61.57%$ of nominal $12.70\text{ mm}$ wall; remaining ligament $t_{\text{rem}} = 12.70 - 7.82 = 4.88\text{ mm}$) and axial length $L_{\text{field}} = 178.0\text{ mm}$.
  • API Std 1163 Unity Plot variance:

$$\Delta d = d_{\text{field}} - d_{\text{ILI}} = 7.82 - 7.37 = +0.45\text{ mm}$$

$$\Delta\left(\frac{d}{t_{\text{nom}}}\right) = \frac{+0.45}{12.70} = +0.03543 \approx +3.54%\text{ of nominal wall}$$

Because $+3.54%$ is well inside the MFL tool's $\pm 10.0%$ wall-thickness tolerance ($\pm 1.27\text{ mm}$), the tool remains within statistical qualification.

  • Permanent repair & closure: A full-encirclement welded Type-B pressure-containing steel sleeve (SLV-B-019, $1.50\text{ m}$ length, API 5L X65) is welded over the defect, $100%$ UT/MPI inspected on longitudinal and circumferential fillet welds, coated with liquid epoxy, and signed off on Day $11$ after discovery—lifting the $74.0\text{ barg}$ temporary pressure restriction and avoiding $₹18.60\text{ lakh/day}$ in curtailed crude throughput.

Scroll horizontally to see all columns.

Assessment Stage Axial Position / Joint Length Defect Depth ($d$ & $%t_{\text{nom}}$) Defect Length ($L$) Governing Pressure / Status
Raw ILI Vendor Tally GW-9410 $+ 4.650\text{ m}$ ($L_{\text{ILI}} = 11.910\text{ m}$) $7.37\text{ mm}$ ($58.03%$) $165.0\text{ mm}$ Unscaled chainage off by $+259.63\text{ m}$
GIS-Scaled Dig Sheet (DIG-2026-019) GW-9410 $+ 4.638\text{ m}$ ($L_{\text{GIS}} = 11.880\text{ m}$) $8.865\text{ mm}$ ($69.80%$ w/ tol + CGR) $165.0\text{ mm}$ $P_{\text{safe,disc}} = 94.1\text{ barg} < 96.0\text{ barg}$ ($\text{TMP} = 74.0\text{ barg}$)
In-Ditch Field PAUT / Laser Scan GW-9410 $+ 4.620\text{ m}$ ($18\text{ mm}$ axial error) $7.82\text{ mm}$ ($61.57%$; $t_{\text{rem}} = 4.88\text{ mm}$) $178.0\text{ mm}$ Unity error $+0.45\text{ mm}$ ($+3.54%,t$, within $\pm 10%,t$)
Post-Repair Closure (SLV-B-019) Span $4.00\text{ m}$ to $5.50\text{ m}$ from GW-9410 Encapsulated by $14.2\text{ mm}$ Type-B sleeve $1,500\text{ mm}$ sleeve Closed Day $11$; $\text{MAOP} = 96.0\text{ barg}$ restored

Independent arithmetic verification

  • Odometer scaling: Macro difference $= 112,689.81 - 112,420.00 = +269.81\text{ m}$. Joint scaling $k_{\text{joint}} = 11.880 / 11.910 = 0.9974811$. Corrected offset $= 4.650 \times 0.9974811 = 4.63829\text{ m}$. True chainage $= 108,240.500 + 4.638 = 108,245.138\text{ m}$ vs raw $108,504.770\text{ m}$ (error if unscaled $= 259.632\text{ m}$).
  • Modified B31G check: $z = 165.0^2 / (609.6 \times 12.70) = 27,225 / 7,741.92 = 3.51657$. Folias factor $M = \sqrt{1 + 0.6275(3.51657) - 0.003375(3.51657^2)} = \sqrt{3.16491} = 1.77902$. At $d/t = 7.37/12.70 = 0.580315$, $S_f = 516.95 \times (1 - 0.493268)/(1 - 0.493268/1.77902) = 362.45\text{ MPa}$ and $P_f = 2 \times 362.45 \times 12.70 / 609.6 = 15.102\text{ MPa}$ ($151.02\text{ barg}$).
  • Unity plot error: $\Delta d = 7.82 - 7.37 = +0.45\text{ mm}$; relative wall error $= 0.45 / 12.70 = +3.543%$, Remaining wall $t_{\text{rem}} = 12.70 - 7.82 = 4.88\text{ mm}$, independently verified.

Workflow, owner roles, exception handling and recovery controls

Scroll horizontally to see all columns.

Workflow Step Responsible Owner Role Primary System Record Exception / Boundary Condition Recovery & Escalation Control
1. Pigging Run & Data Qualification Pipeline Pigging & ILI Specialist ILI-Run-Acceptance-Log Pig velocity exceeds $4.0\text{ m/s}$ or $>3%$ sensor channel loss over a segment Reject degraded segment; mandate vendor speed-correction analysis or re-run pig before accepting tally
2. Girth-Weld Tally Alignment GIS & Pipeline Integrity Analyst Master-Pipe-Tally-Register Uncharted pup joint or hot-tap repair breaks the 3-upstream / 3-downstream joint length signature Flag alignment discrepancy; cross-check ultrasonic weld map and require wider bell-hole exposure
3. Remaining Strength & Dig Clock Initiation Senior Pipeline Integrity Engineer Anomaly-Severity-Ledger Predicted safe pressure $P_{\text{safe}} < \text{MAOP}$ or metal loss $\ge 80%,t_{\text{nom}}$ Log statutory Discovery Timestamp; issue formal TMP pressure reduction order to Control Room; mobilize immediate dig crew
4. In-Ditch NDE & Unity Plot Entry Level II/III PAUT Inspector & Field Engineer Dig-Verification-Sheet In-ditch PAUT depth exceeds ILI prediction by more than vendor tolerance ($\pm 10%,t$ at $80%$ conf.) Update API 1163 Unity Plot; trigger systematic depth bias upward adjustment across all unexcavated anomalies in the run
5. Sleeve Repair & MAOP Restoration Pipeline Maintenance Supt. & Integrity Lead Repair-Closure-Certificate Field UT discovers cracking or lamination that prohibits Type-A sleeve or composite wrap Escalate to Integrity Engineer for Type-B pressure-containing welded sleeve or cut-out spool replacement before lifting TMP

Bounded pilot and implementation check

Validate the ILI anomaly and dig-sheet reconciliation system on a single pigged pipeline section ($50\text{--}100\text{ km}$, covering at least $10$ verification digs) using four acceptance tests:

  • ACT-O105-01 (Odometer-to-GIS girth-weld scaling accuracy): Verify that the software ingests a vendor pipe tally, anchors to AGMs and master girth welds, verifies the $\pm 3$ adjacent joint-length signature, and outputs dig-sheet offsets $d_{\text{corr}}$ that land within $\pm 0.10\text{ m}$ of the in-ditch anomaly location.
  • ACT-O105-02 (Modified B31G / RSTRENG calculation & clock trigger): Confirm that the engine reproduces ASME B31G / Modified B31G failure and safe operating pressures within $\pm 0.05\text{ barg}$ of independent reference calculations and starts the statutory Immediate / 180-Day / 1-Year countdown clock from the logged Discovery Date.
  • ACT-O105-03 (API Std 1163 Unity Plot & bias alert): Enter $10$ synthetic or historical in-ditch PAUT verification records where $3$ records exceed the $+10%,t_{\text{nom}}$ vendor depth tolerance; verify that the Unity Plot flags a binomial confidence violation and prompts the Integrity Engineer to apply a conservative depth calibration offset.
  • ACT-O105-04 (Repair closure & TMP lift gate): Attempt to close an Immediate anomaly and lift a Temporary Operating Pressure ($\text{TMP}$) restriction without attaching a signed in-ditch PAUT report and repair NDE clearance certificate; confirm the software blocks closure.

Next actions

  1. Build a canonical Master Girth-Weld Tally per piggable line: Reconcile prior ILI runs, as-built construction weld books, and GPS AGM surveys into a single GIS-linked joint register before the next smart-pig launch.
  2. Standardize digital excavation dig sheets: Replace free-text work orders with structured dig sheets that mandate three-joint upstream/downstream length tape verification in the trench prior to coating removal.
  3. Automate API Std 1163 Unity Plot feedback: Require NDE contractors to upload structured PAUT/laser depth and length grids directly against the ILI feature ID within $48\text{ hours}$ of bell-hole inspection so tool sizing bias is tracked in real time.
  4. Enforce closed-loop TMP and repair clock governance: Link the anomaly severity ledger to Control Room operating envelopes and executive integrity dashboards so no Immediate or Scheduled repair clock approaches expiry without escalated action.

Frequently Asked Questions

How should pipeline operators reconcile smart-pig Inline Inspection (ILI) vendor tally runs, odometer girth-weld alignment, excavation dig-sheet verification, and sleeve/recoating repair closure?

Teams should govern inline inspection pigging anomaly software by linking every transaction to its source evidence, timestamp, and assigned owner before permitting downstream posting. Distinct from O019 (pipeline imbalance accounting) and O101 (plant AIM); O105 covers pigging launch/receive traps, ILI metal-loss/dent feature matching against GIS girth-weld registers, field ultrasonic dig-sheet feedback, and repair clock tracking. Rather than relying on informal spreadsheet overrides, the workflow enforces a documented verification gate and preserves the original observation whenever a correction is recorded.

How does midstream oil and gas software handle exceptions and mismatches?

When a discrepancy occurs during midstream oil and gas software, the system routes the blocked record into an owned exception queue rather than silently dropping or auto-adjusting the balance. Assigned operational, quality, and finance owners must review and approve exceptions before posting. Each exception retains the original quantity, date, and counterparty reference until the designated reviewer resolves the variance with supporting evidence.

What should teams test before automating pipeline maintenance software?

Before scaling pipeline maintenance software, run a bounded pilot using historical records that include partial receipts, late updates, duplicate messages, and rejected lines. Verify that the integration preserves idempotency, maintains a clear segregation of duties between operational entry and financial approval, and produces an auditable trail for every state transition.

Summary and next actions

  1. Map the current inline inspection pigging anomaly software record boundaries, system of record, and named approval owners before changing workflow rules.
  2. Separate operational status updates from engineering, safety, or financial disposition sign-off.
  3. Validate exception queues, duplicate handling, and cutoff reconciliation in a bounded pilot before production rollout.

Assess your inline inspection pigging anomaly software controls

Map the record states, evidence links, exception routing and review owners for inline inspection pigging anomaly software. Technical and regulatory sign-off stays with the site authority.

Prepare a focused assessment

References

Sources checked 15 October 2026. Vendor examples retain their stated release scope. Catalogue entries do not replace the full applicable standards.

About the author

Vikasraj Yadav writes about operational records, software and AI automation for NextEdge Labs. The worked examples and all 70 collection diagrams are original editorial illustrations, not client results.

Published 20 October 2026. This guide discusses software and record design; qualified site authorities (Maintenance lead, operations authority and ERP/EAM system owner) determine the requirements for a specific operation — Record state separation, exception reconciliation and audit trail governance for inline inspection pigging anomaly software.