Checks each vendor file against the deliverable list and the data checks.
- Never edits vendor data
- Holds a failed file
In-line inspection report review that applies the vendor's own written caveats to the listing rows they change, before the discovery clock runs out.
Follow one feature from page 212 to a dig package ↓The feature listing lands first, tens of thousands of rows, and the written final report follows weeks later, hundreds of pages long. By then the clock on the assessment is well under way. The engineer lines the new run up against the old ones in a spreadsheet, runs the deep features through the calculation tool, and skims the report when there is time.
So a speed excursion, a dark sensor carrier or a slipped odometer stays in the PDF, and the rows it affects are decided as if the tool were in spec. Old dig sheets sit in the document system and rarely meet the neighbors they describe. And the call not to dig a feature is often one row in a spreadsheet, with nothing an auditor could follow.
Built forIntegrity engineersIntegrity managersDig coordinatorsVendor liaisonsCompliance auditors
Each run brings a huge listing and a long report, and what the report says in words rarely reaches the rows.
Compared by hand today
Built-in controls
Engineers spend their time on the features whose reading changed, with each no-dig decision on record.
The newest run's final report arrived four days ago. Overnight it was read page by page against the listing, and one passage changes how 37 features in a six-mile stretch should be read.
demoAll sample data: Line 12, its three runs, the vendor, the crews and each reading on these screens.
The line opens as three runs stacked over one pipe, the same feature joined across them and each small line rising to the latest call. Between MP 58.02 and 64.15 the stretch is shaded. The note at the top says it touches 37 features at 20% or deeper, and 5 fall under the dig line at the wider bound. Section A has 19 days left.
Speed, lost sensors, a slipped odometer, heavy wall at crossings, boxed clusters and near-weld lengths, each with its page. Page 212 opens with the vendor's own sentence highlighted: depth sizing in this interval is outside specification, plus or minus 20% of wall at 80% certainty, and field verification is recommended. The engineer reads the passage herself before trusting the count.
The stretch holds 1,174 listed features, and these 37 are metal loss at 20% of wall or deeper, where a sizing error changes the response. Filtered to proposed digs, five rows remain, each with three runs' calls, growth a year, the bound at plus 20 and failure pressure at that bound, from 1,105 to 1,211 psig.
MP 61.27 rises from 26% to 44% of wall, 3.13% a year. The oldest run's match is 81% sure, below the 85% line, so it is shown and kept out of the growth. The 18-point change is inside the two tools' combined error of about 22 points, and the screen says the listing alone cannot prove the rate. 525 welds after the valve tie the runs together.
The dig sheet came back years ago and was never read against its neighbors. Carried forward at its own rate, 24% becomes 29.9% expected, so 38% is inside the combined tolerance and proves no tool error. It does show active corrosion under disbonded tape, as much as 3.7% of wall a year against 1.57% on that feature's calls.
Failure pressure comes from the engineer's own calculation tool, in a batch she ran the day before. The agents prepare the inputs and read the results back. At the listing's call it is 1,322 psig, 1.49 times the maximum allowed. At the report's bound of 64% it is 1,211 psig, under the procedure's line for a dig within 12 months.
Decide stays locked until all three items are opened, and no reason comes preselected. She picks the fact the decision rests on, from this feature's own record: failure pressure at the bound is under the line. Discovery is recorded today, and the repair clock runs from it. On the listing alone this feature would have been monitored.
Her opening them does not count for him. He opens page 212, the dig sheet and the calc record himself, and only then can he countersign. The panel records both positions, the times and what each person opened. A delay in signing would not have moved discovery. The new dig falls due 365 days out, with its package still to build.
Filtered to the report, the dig list shows the signed dig at MP 61.27 and six still proposed, waiting for the engineer. Above them sits the one dig-now condition on the line: 941 psig at the call, under the 979 psig line, with Section B held at 680 psig and an owner named. Sample cost is $95,000 a dig.
The odometer is not trusted in this stretch, so the package for the field crew locates the feature by weld count from the mainline valve, then distance past the weld and clock position. It asks for a laser scan of depth and length, a coating record, and the sheet back within 30 days. Nothing goes in the ground before the excavation permit.
The same feature read three ways, from the engineer's own calculation tool. Only the report's bound takes it under the line.
| Depth used | Failure pressure | Against maximum allowed |
|---|---|---|
| Listing's call, 44% | 1,322 psig | 1.49 × |
| Report's bound, 64% | 1,211 psig | 1.36 × |
| At the next run, 59.7%, on the call | 1,239 psig | 1.39 × |
| Procedure line, dig within 12 months | 1,237 psig | Sample value |
demoSample data, from the working solution. Procedure values are sample values; the operator loads its own.
A response for each feature, by route. The monitored ones keep their own evidence.
| Repaired after the preliminary report | 8 |
| Digs from the listing | 41 |
| Digs from the report's words | 7 |
| Monitored to the next run2,814 in six groups signed on a sample, 76 touched by a caveat and decided one by one | 2,890 |
| Features with a response | 2,946 |
demoSample data, from the working solution.
What the integrity manager, the vendor liaison and the compliance auditor open on this run.
demoSample data, from the working solution.
Seven readers, and a named person owns what comes out of each. None of them picks a response.
Checks each vendor file against the deliverable list and the data checks.
Aligns girth welds from fixed points, then features by distance and clock, with a confidence.
Reads the final report, run logs and vendor answers page by page and lists the rows each caveat touches.
Works out depth change a year between matched runs and compares it with both tools' error.
Sets each dig sheet beside the tool's call carried forward to the dig date.
Applies the operator's procedure and prepares inputs for the engineer's calculation tool.
Reads returned dig sheets and links each to its feature.
Read only. A value on screen cites the row, page or sheet it came from.
In-line inspection report review is the reading an integrity engineer owes each run: the listing against earlier runs, the tool against what digs measured, and the written report for anything it says only in words. Here agents do that reading and show the rows each caveat touches, and a named engineer decides each response.
Girth welds are aligned first, anchored on valves, tees and known pipe changes, then features by distance from the weld and clock position. Each match has a confidence. A match below the line is shown and kept out of growth until the engineer writes why it holds and the manager opens it and agrees.
Growth between matched runs is worked out and compared with the two tools' combined error, so a rate the listing cannot prove is marked as such. Failure pressure stays in the engineer's own calculation tool. The agents prepare its inputs and read the results back.
It keeps its own evidence: the call, the sizing, the growth, predicted depth at the next run and the pressure sentence. Large groups are signed by a second person only after each feature in a random sample has been opened, and rows outside the sample say they were not opened.
Each field measurement is set beside the tool's call carried forward to the dig date at that feature's rate, with the combined tolerance. The plot and the run verdicts follow from that, and a run waits for final acceptance until it has as many comparisons as the procedure asks.
The integrity engineer decides each feature and each dig. The integrity manager countersigns after opening the same evidence, and nobody checks their own decision. A dispute, or a decision that would drop a proposed dig, goes to the VP of pipeline integrity. The auditor reads and exports only.
Every meter check tied to its clause, every miss priced with the working shown.
1-min demoRight-of-Way Encroachment ManagementCrossing requests answered in writing inside the clock, every condition cited.
1-min demoStorage Tank Inspection ManagementNext due dates reworked from the readings, with the sum shown.
1-min demoWe’ll show which rows your report's own pages change, against your older runs and dig sheets.