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.
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
- Three grew beyond threshold since 2021
- Two have no prior assessment on record
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 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?”
About 70 damage mechanisms in API 571. Which rule controls depends on your service and jurisdiction. The answer is real, it is just buried.
“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.
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.
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 about 70 damage mechanisms in API 571 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.
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 are never assessing an anomaly from a blank box.
PHMSA incident reports
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 to 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.
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.