Operator Workflow

Hazardous Liquid Pipeline Integrity Management: What the Rule Actually Requires

A liquid pipeline may carry crude, condensate or refined products across miles of changing terrain. Integrity management for those lines is not a single report. It is a program that identifies the risks, sets thresholds for action, schedules assessments, and tracks repairs until the line is either confirmed sound or taken out of service. Federal rules under 49 CFR Part 195 define what that program must contain and how operators document it.

The baseline assessment and the risk picture

The integrity management rule starts with a baseline assessment. For high consequence areas, the baseline is usually a smart pig run, a pressure test, or a direct assessment, depending on what the operator can justify. The operator identifies each high consequence area, maps the line segments that reach it, and chooses an assessment method that can detect the defects that matter most. The choice is not arbitrary. It has to match the damage mechanisms likely to be present: internal corrosion, external corrosion, cracking or mechanical damage. The operator writes down the basis for the choice because that justification is part of the program record.

Scheduling, thresholds and the repair clock

After the baseline, the program runs on a schedule. The operator re-assesses each segment on a cycle that reflects the risk and the assessment method. When an assessment finds a defect, the repair clock depends on severity. Some anomalies get a repair plan and a completion deadline measured in months. Others require action in days. The operator must analyze the threat, evaluate the anomaly against acceptance criteria, and document the repair or the rationale for continued operation. The repair file includes the discovery method, the measurement, the repair type and the verification after the repair. When the operator uses OpsFlo to link tickets and approvals, the record stays connected from anomaly to closure.

Records, control rooms and follow-through

The rule is explicit about documentation. Operators must keep records of threat identification, risk assessment, assessment methods and results, remediation, and re-assessment. Control room management under 49 CFR 195.442 also feeds this program because controllers are responsible for recognizing conditions that could indicate a release and initiating the response. Patrol logs, damage reports and follow-up tickets are exactly the kind of field paperwork tracked in ticket, dispatch, timesheet, approvals and document software built for field crews. When assessments stay in spreadsheets and follow-up calls happen in the truck, the audit trail is not there.

Sources and further reading

• eCFR 195.579: Pipeline integrity management
• eCFR 195.410: Pipeline integrity management in high consequence areas
• eCFR 195.442: Control room management
• API RP 571: Damage mechanisms