Operator Workflow

Pipeline Leak Detection Programs: CPM, Aerial Patrols and the Silence Between Alarms

Leak detection on a pipeline is not one sensor. It is a layered program that combines real-time software, ground patrols, aerial surveys, and sometimes satellite or drone passes. Each method catches a different kind of release, and each method depends on alarms, schedules, and written follow-up. The program only works when the alarm or the survey result becomes a ticket, a dispatch, and a record.

Methods and what they catch

Computational pipeline monitoring, or CPM, uses flow and pressure imbalance to flag a likely leak in real time. A sudden volume imbalance on a balanced line is one of the clearest signals available. Aerial patrols look for visual signs: dead vegetation, sheens, ground disturbance, or vapor. Ground patrols add the same observation on foot and can check fence lines, drainage, and signs of digging. Drones and satellites can inspect large or remote segments faster than a crew on the ground, but they are not real time and they depend on weather and flight windows.

Program design, audit and follow-through

Federal integrity management rules require operators to have a leak detection program and to evaluate it against the line's risk profile. Control room management rules require documented alarm response. The program has to define what happens when an alarm sounds, who responds, how long the response takes, and how the closure is recorded. An alarm that gets acknowledged and never investigated is still a finding. A survey that finds nothing and never gets filed is a day that never happened.

The record that closes the loop

Leak survey logs and follow-up work orders are exactly the kind of structured field data tracked in OpsFlo, ticket, dispatch, timesheet, approvals and document software built for field crews. The operator who can pull the alarm record, the patrol log, and the repair order from the same system can defend the program in an audit. The operator who cannot has a story instead of a record.

Sources and further reading

• eCFR 192.639: Integrity management
• eCFR 195.579: Pipeline integrity management
• eCFR 195.442: Control room management
• API RP 571: Damage mechanisms