Engineering-Driven Standardization and Automated Validation of Inline Inspection Deliverables: An Enbridge Case Study

Thursday - January 28 | 8:30 · 7.1 ILI Analysis 1

Brandon Bandoni1, Sheri Baucom2

1Enbridge, Houston, USA, 2Irth, Colorado, USA

Inline Inspection (ILI) data is essential for pipeline integrity engineering, enabling defect characterization, growth modeling, regulatory compliance, and informed repair decisions. However, inconsistencies in vendor deliverables, such as variations in templates, terminology, completeness, and calculation logic, can degrade data quality, increase engineering effort, and reduce confidence in the data provided. Addressing these inconsistencies at the source, within the vendor workflow itself, offers a path to both higher data quality and faster delivery. This case study describes how Enbridge and Irth addressed these challenges by designing and implementing an automated, engineering-driven vendor validation framework that applies validation before data ingestion and gives vendors direct visibility into results. The solution centers on the Universal Feature Listing (UFL), a standardized deliverable supported by a formal reporting guide and clearly defined vocabulary. This standardization enabled advanced automated checks for data consistency and integrity across all vendors. Prior to implementation, Enbridge's ILI data ingestion process relied on manual quality assurance and quality control (QA/QC) reviews performed after vendor delivery. These reviews were limited in scope and capability, focusing primarily on basic formatting and obvious errors rather than comprehensive validation. Because these checks depended heavily on the variable knowledge level of individual analysts, they were prone to error and lacked consistent in-depth validation. This led to delayed downstream engineering analysis and additional cost during times of higher report volume when contracted support was required. With the new approach, automated validation rules are applied before data ingestion to evaluate template conformity, data formatting, permissible values, completeness of required feature attributes (such as length, width, and depth), and calculation logic (such as pressure assessments and interacting defects). The validation logic distinguishes between critical errors that prevent ingestion and non-blocking warnings that inform engineering reviews. Vendors receive direct access to validation results, allowing them to correct issues iteratively before final submission, which significantly reduces the need for back-and-forth communication. Implementation shifted validation from a post-delivery quality review activity to an upstream vendor-facing control point. This change allowed Enbridge and Irth to identify deliverable issues earlier, standardize how vendors interpreted reporting requirements, and reduce the amount of engineering effort required to prepare ILI data for downstream integrity analysis. Quantitative results demonstrate substantial engineering and operational benefits: the average number of revision cycles per inspection decreased from approximately three to one, processing time per inspection dropped from 2.5 days to 0.5 days, and on-time delivery of inspection data improved from 76% to 98% in the three years following implementation. These improvements reduced manual validation effort and expenditure on contracted QA/QC services, while enhancing consistency across multiple ILI vendors. From an engineering perspective, the standardized and validated datasets increased confidence in automated defect sentencing, reduced variability in integrity assessments, and improved traceability of inspection data. This case study demonstrates that embedding engineering validation logic directly into vendor workflows, supported by standardized vocabulary and reporting formats, can materially improve data quality and efficiency. The approach provides a scalable model for operators seeking to strengthen ILI data governance, integrity decision-making, and regulatory compliance.

Read/Download PaperGradeAvailable after the event