Skip to content
Oil & Gas · Pipeline integrity

Your integrity program, cited to the record.

Ask your own ILI runs, dig reports, and integrity records plain questions, every answer cited to the exact page and the controlling 49 CFR clause. Runs air-gapped.

Natural gas Crude oil Products HGL
Every answer cited to its source page Air-gapped on your own hardware SOC 2 Type II · ISO 27001
A question against your own run reports and dig sheets returns the assessment history for a joint, cited to the page, so the comparison to the last run is on the record rather than in someone’s memory.
The app for this work

The triage you do after every run, run once

It ranks what the run found against what you already assessed, and stops for the engineer who signs the dig list.

Input ILI run, line 12, 1,412 anomalies

Dig list, 11 candidates, all sourced
  • Three grew beyond threshold since 2021
  • Two have no prior assessment on record
Run report, p.44Prior assessment 2021, p.8
Click a step to jump to it

Issuing a dig list is a decision with a cost attached, so the app assembles the candidates and their history and waits for the engineer to sign it.
Who it's for

Built for the people who own the line.

Integrity teams who carry the consequence of a wrong disposition, and the hours of digging behind every defensible one.

Integrity managers & engineers

Own the integrity-management program and the dig decisions that come out of it.

IM managers · pipeline integrity engineers

ILI & data analysts

Turn inline-inspection runs into prioritized features, digs, and repairs.

ILI analysts · data integration

IM / compliance coordinators

Keep the program records audit-ready and traceable to the controlling code.

IM coordinators · risk & compliance

The problem, in your words

The records exist. The answer still takes hours.

It lives across ILI runs, dig sheets, alignment sheets, MOCs, and a stack of codes, in different systems, in different formats.

“Which damage mechanism, and which code controls?”

The industry recognizes roughly 70 damage mechanisms, and which rule controls depends on your service and jurisdiction. The answer is real, it is just buried.

The scope About 70 recognized damage mechanisms to narrow on every call.

“Is it in an ILI report, a dig sheet, or a 1985 record?”

You know the answer is somewhere, in a run report, a prior dig, the federal code, or a decades-old test record, but not which one, or where.

What happens Engineers lose 3–5 hrs/day hunting for references.

The engineer who knows the line is retiring.

Decades of “why we dug there” and “what that anomaly really was” never made it into a system. When they leave, it leaves.

The exposure Up to 70% of integrity know-how is tacit and at retirement risk.
How it helps

Apps that do the integrity work.

knowledgeXpert ships as focused apps built on your own ILI runs, dig records, codes, and SOPs, each one returns a cited answer or a defensible deliverable.

ILI Expert

Ask across your inline-inspection runs, features, growth, prior calls, and get a cited answer tied to the run report and joint, not a web guess.

Dig Expert

Pull the dig criteria, the prior excavation, and the disposition logic for a feature, each step cited to your own records and the controlling code.

Damage-Mechanism & Code Lookup

Narrow the ~70 recognized damage mechanisms to what applies in your service, with the controlling 49 CFR 192 clause cited to the part.

Integrity Record Q&A

Plain questions across ILI runs, dig reports, MOCs, and inspection history, cited answers in seconds, not file cabinets.

On the Marketplace

The integrity reference set, pre-loaded and cited.

Before you load a single record, knowledgeXpert ships with cited public integrity knowledge on the Marketplace, so you're never assessing an anomaly from a blank box.

PHMSA incident reports

3,900+ pages of federal incident investigations, whether a feature or failure mode has shown up before, and what the investigation found, cited to the report.

PPIM / Clarion integrity library

Pigging & integrity-management conference proceedings and technical papers, 2011–2025.

Title 49 CFR (Part 192 / 195)

The federal pipeline-safety code, cited to the controlling clause.

PHMSA technical reports & data

The agency's own analyses and pipeline-safety data, ready to query.

Your ILI runs and dig records come in alongside, so you can ask whether an anomaly or failure mode has appeared in PHMSA incidents, and get the findings cited next to your own data.

Proof

Specific numbers, not slogans.

25 %
Productivity lift
Measured at Vista Engineering.
100 %
Answers cited
Every answer traced to the exact page it came from.
<30
Days to deploy
From first document load to live on your team.
Questions

Straight answers.

Why not just ask Copilot about our ILI reports?

It only sees the documents you control, your ILI runs, dig records, codes, and SOPs, never the open web. It cites every answer to the exact page and clause, and when something is not in your records it says so instead of guessing. Copilot is capable, but it has never read your integrity manuals.

Does our integrity data stay private / on-prem?

Yes. Your documents stay in your own tenant and we do not train models on your data. For operators who cannot send records off-site, knowledgeXpert runs air-gapped on your own hardware, records never leave the building. SOC 2 Type II and ISO 27001.

Does it handle 49 CFR Part 192 and our own standards?

It reads the federal code alongside your own records, so an answer can cite the controlling clause next to the dig sheet or ILI feature it applies to.

How fast can an integrity team be live on this?

Most teams go from first record load to a live, queryable knowledge base in under 30 days. A scoped pilot on a slice of your ILI and dig records can be running in days.

See it on your own records

See cited answers running on your integrity records.

Thirty minutes, a slice of your own ILI runs and dig records, and you see the citations before anyone signs anything.