POF 303 ILI Data Feedback Form - Nov 2021

POF 303 ILI data feedback form November 2021
In-line inspection data feedback form

For latest version of this Data Feedback Form refer to the POF Website
(www.pipelineoperators.org).
Note: Although quite extensive, the contents included in this document are provided only as
examples. They are not intended for adoption without review and customizing for all circumstances.
Operators or other users choosing to adopt a similar form should base it on their own organization,
structure responsibilities and permitting procedures.
Part 1 - general
The information provided can be used to track performance across all Operating/Business units of
the pipeline operator. It is advised to send this form to the operator’s ILI coordinator.
Press “tab” to advance to each field (or click on the field) to be completed.
Operating/Business Reference No:

unit: ILI Team will allocate
ILI contractor: ILI run date:

Line segment: Final report
accepted: Date:
Length of segment : km / miles Email:
Delete km/ miles as appropriate
Contact: Tel Contact:
Length helps track km inspected over time
Tool Type (Check One)
Standard High Level Standard High Level UT

Geometry Geometry MFL MFL Metal Loss
UT High Level High Level High Level EMAT

Crack Geo/MFL MFL/UT Circumferential
Combo Combo MFL
Other:
First run success.

Was the first run successful? Yes No
If no, how many subsequent attempts were made?
If no, also complete and return Part 2 of this feedback form which includes the root cause analysis.
Was a successfully run eventually achieved? Yes No
Failed run(s) was due to: ILI contractor Operator Unknown
Probable cause of failure:
Comments:
Pipeline Operators Forum – www.pipelineoperators.org 1

Budget, cost and reporting.

Budgeted cost of the ILI services included in the work order $
Final invoice or estimated cost of the ILI services provided $
Comments:
Was the report late? Yes No: Number of days late
Was tool performance and reported features in specification? Yes No Unknown
Are there procedural changes needed for the Operating/Business unit or centrally with the ILI contractors?
Yes No
Comments:
Part 2 – Root Cause Analysis

Operating/Business unit: Error: Reference Reference No Error: Reference
source not found source not found
From ILI team
ILI contractor: Error: Reference ILI run date: Error: Reference
Line segment: Error: Reference Length (km/ miles) Error: Reference
Contact: Email Tel Contact Final report
Error: Reference source not Error: Reference accepted Date:
found source not found Error: Reference
source not found
This section will be used to track root causes and costs to target areas for improving best practices
for improving first run success rates:
Summary from root cause assessment

Failed Run Due To:
Missing data without tool damage
Missing data and minor tool damage (lost sensor)
Severe tool damage & significant loss of data
Stuck tool
Project Preparation:
Insufficient information provided by operator
Poor communications
Short mobilization time
No site visit
Wrong tool selection
Other:
Cleaning and Gauging:
Pipeline not adequately cleaned
Calliper not run
Final gauge / profile tool not run
Inadequate interpretation of gauge or calliper report
Other:
Operation Procedures:
Procedures inadequate
Tool set up check list not followed
Launch receive problems

Operating procedures not followed

Pipeline conditions changed (e.g. valve position)
Speed control problems
Other:
Tool reliability:
Electronics failure -
Electronics
Software
Battery
Mechanical failure -
New component
Not suited for environment (fatigue/ mechanical damage)
Other:
Data analysis:
Incorrect feature identification or sizing
Other:
Lessons learnt:
Known problem but data not available from previous operations
Other:
Impact of failed run

Number of additional runs:
Cleaning
ILI
Number of days final inspection delayed:

Days:
Other:
(Note: please describe - e.g. impact on production above)
Additional Operator costs:

Man hours:
Tool damage:
Production:
Other:
Supplier (if known):
Estimated total impact:
Comments:
Areas to improve:
Has global network been alerted and advised? Yes No
Tool damage (attach photographs):

Part 3 – Contractor Input
After Parts A and B are complete, please forward this report to the contractor in order to get their
feedback on the tool as well as their feedback on the overall inspection process. The information
provided can be used to track Operating/Business unit’s and contractor’s performance.
Operating/Business unit: Error: Reference Reference No Error: Reference

From ILI team
ILI contractor: Error: Reference ILI run date: Error: Reference
Line segment: Error: Reference Length (km/ miles) Error: Reference
Contact: Email Tel Contact Final report
Error: Reference source not Error: Reference accepted Date:
found source not found Error: Reference
source not found
Days beyond payment terms

Was the report late? Yes No: Number of days late
Comments/explanation:
Was tool performance and reported features in specification? Yes No Unknown
Are there procedural changes needed by the operator or with the ILI contractors? Yes No
Comments:
Please have all three (3) parts of the form completed and returned to the operator’s ILI coordinator.
If tool gets stuck or is severely damaged please fill in an early assessment.

POF 303 ILI Data Feedback Form - Nov 2021

Uploaded by

Copyright:

Available Formats

POF 303 ILI Data Feedback Form - Nov 2021

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

POF 303 ILI Data Feedback Form - Nov 2021

Uploaded by

Copyright:

Available Formats

POF 303 ILI data feedback form November 2021

In-line inspection data feedback form

Operating/Business Reference No:

ILI contractor: ILI run date:

Tool Type (Check One)

Standard High Level Standard High Level UT

UT High Level High Level High Level EMAT

First run success.

Pipeline Operators Forum – www.pipelineoperators.org 1

Budget, cost and reporting.

Part 2 – Root Cause Analysis

Summary from root cause assessment

Pipeline Operators Forum – www.pipelineoperators.org 2

Operating procedures not followed

Impact of failed run

Number of days final inspection delayed:

Additional Operator costs:

Has global network been alerted and advised? Yes No

Tool damage (attach photographs):

Pipeline Operators Forum – www.pipelineoperators.org 3

Part 3 – Contractor Input

Operating/Business unit: Error: Reference Reference No Error: Reference

Days beyond payment terms

Pipeline Operators Forum – www.pipelineoperators.org 4

You might also like