Pipeline regulatory research for an integrity management program.
Keep the research behind your team’s integrity decisions.
When an assessment reopens a procedure decision, your team needs to show the basis for it, not rebuild it from memory. KONDWIT keeps that basis attached to the citation, so the reading behind a Part 192 or Part 195 conclusion survives the assessment cycle and the people who did the work.
The basis has to outlast the person who built it
Keep institutional knowledge in the record, not in one engineer’s head
The riskiest thing your program loses when an experienced engineer retires is not the answer. It is the reasoning: which source they read, which edition, what they assumed, and what they left open. When that lives in email threads and personal drives, the next reviewer starts the same research from zero.
Research collects each question, the source passages that were read, and the assumptions and open items behind a conclusion into a resumable session. Positions records an adopted regulatory position with its citations and a reviewable history of how it changed. The work behind a decision stays attached to the citation, so a new team member inherits the basis instead of reconstructing it.
One reading of a source, shared across the team
Read a provision the same way, from the same source
Two engineers can read the same paragraph of 49 CFR and reach different conclusions, usually because they read different sources, different editions, or different guidance without noticing. On a team, that drift is a process risk: the program says two things at once and cannot tell which is current.
Every source carries its identity, edition and import date, so a citation points to a specific passage rather than a paraphrase. Positions lets your team record the reading it has adopted, with the citation and the history behind it, so the next question starts from a shared basis. Whether that reading is correct and fits your system stays your engineer’s call.
Show the basis, don’t rebuild it
When a decision is reopened, reopen the record behind it
An integrity assessment, an incident review or an internal self-assessment can reopen a procedure decision made years earlier. The question is always the same: what did you know, from what source, when. If the answer is a reconstruction, the basis is already weaker than the decision it supported.
Freeze the research behind a conclusion into a memo a reviewer can reopen, with its cited sources and their import dates intact. Use Audit to organize inspection preparation, follow-up and response materials against that record. KONDWIT controls process risk, not outcome risk: it makes the basis inspectable and reopenable. It does not certify compliance, tell you what an inspector will ask, or predict a finding.
Fits the program you already run
Choose the apps for your integrity management program
Start with Research and add the workflow apps your program needs. They map to the work an integrity management program already produces: gap analysis, procedure revision, and the records behind a self-assessment. Each app is separately enabled for your account.
Add-on
Procedures
Review your procedure library alongside coverage and gap-analysis findings, and keep the source behind each finding in view.
Add-on
Positions
Record adopted regulatory positions with citations and a reviewable history, so the team’s reading of a provision stays consistent.
Add-on
Audit
Organize inspection preparation, audit work, follow-up and response materials against the record that supports them.
Add-on
Assets
Maintain pipeline asset context to inform which requirements apply to which segment.
Add-on
Rulemaking
Track rulemaking and examine how a proposed change could affect your procedures before it takes effect.
Add-on
Enforcement
Research collected enforcement cases and operator context as historical reference, not as a prediction of your own findings.
Know the boundaries
Analysis findings and historical enforcement records inform your review. They do not certify compliance or determine what an inspector will conclude; the engineering judgment stays with your team.
The state layer: A state-source and adoption research index for 50 states, DC and Puerto Rico. State regulatory text is not yet verified for publication. Source availability and adoption qualifications vary by jurisdiction. The adoption-posture index is research with evidence and qualifications recorded per jurisdiction, not a determination of final legal applicability for any operator. The federal corpus does not substitute for missing state law: where a jurisdiction’s regulatory text is not carried, no federal result stands in for it. An import date is not a legal effective date, and a category with no results may simply not be carried. Check the source and its date before deciding what applies.