What Does API RP 1130 Require of a Leak Detection Program?
If your operator runs a hazardous-liquid pipeline with a software leak-detection system, someone eventually asks what API RP 1130 actually expects you to have in place. This page summarizes the program elements the recommended practice organizes its guidance around, so an engineer or integrity lead can sanity-check an existing program without reproducing the document. It is written for the person who has to answer an auditor, not for the person writing the standard.
API RP 1130 Program Requirements in one line: API RP 1130 is the American Petroleum Institute recommended practice for computational pipeline monitoring (CPM) leak-detection systems on liquid pipelines. It does not certify a system; it frames the work of designing, testing, operating, and maintaining a CPM system - covering method selection, performance evaluation, alarm handling, and the operational procedures around detection. Treat it as the framework your leak-detection program is organized against, not a pass/fail test.
What API RP 1130 Covers and Who Publishes It
API RP 1130, Computational Pipeline Monitoring for Liquids, is published by the American Petroleum Institute. It addresses the design, implementation, testing, and operation of internally-based leak-detection systems - the software methods that infer a leak from pressure, flow, temperature, and density data already flowing into pipeline SCADA. It is a recommended practice, which means it captures accepted industry approaches rather than imposing a single mandatory design.
The recommended practice sits alongside, and is referenced by, US pipeline safety regulation. It is not itself the law. Where a regulation such as 49 CFR Part 195 requires a leak-detection capability on a hazardous-liquid line, RP 1130 is the practice operators lean on to show the capability was engineered and is maintained deliberately. Always confirm the current regulatory requirement with your compliance team - the standard supports the program, it does not replace the regulation.
The Program Elements It Organizes Around
The recommended practice frames a CPM program as more than an algorithm. It expects a documented method choice matched to the pipeline, defined performance expectations, a testing and validation regime, controller-facing alarm procedures, and a maintenance and record-keeping discipline so the system does not silently degrade. In other words the deliverable is a living program, not a one-time commissioning report.
A useful way to read the structure is by lifecycle stage. Selection and design decide which computational method fits the hydraulics and the instrumentation you actually have. Commissioning and testing prove the configured system behaves. Operation covers how a controller responds when the system alarms, including the interaction with rupture detection where the leak is large and fast. Maintenance keeps tuning, instrument health, and documentation current as the line and its product mix change over years.
What Compliance Work Actually Looks Like
In practice, aligning to RP 1130 means being able to show three things on demand: that the method was chosen for a reason, that its performance was characterized, and that its alarms are acted on. The performance characterization is the part engineers underestimate - it is where the four evaluation attributes (sensitivity, reliability, accuracy, and robustness) get quantified for your specific line. The companion page on how to evaluate a CPM system per API 1130 walks those attributes.
The unglamorous half is records. Alarm logs, tuning changes, instrument calibration records, and test results are the evidence that the program is real. A computational pipeline monitoring system that alarms and is ignored is worse than none, because it creates a documented history of unactioned warnings. RP 1130 pushes operators to close that loop with defined controller procedures and a review cadence.
Common Misconceptions
The first misconception is that RP 1130 mandates a specific method - it does not. Mass balance, real-time transient modeling, statistical methods, and pressure-wave detection are all in scope; the standard asks you to justify the fit, not adopt a favorite. A real-time transient model may be right for one line and overkill for another.
The second is that a purchased system is automatically compliant. The vendor supplies the engine; the operator owns the program. Tuning to your hydraulics, integrating alarms into controller workflow, and maintaining the evidence trail are operator responsibilities that no product ships pre-done.
Frequently Asked Questions
Is API RP 1130 mandatory?
The recommended practice itself is voluntary, but US pipeline safety regulation for hazardous-liquid lines references leak-detection expectations that operators typically meet using RP 1130. Confirm the binding requirement with your regulatory compliance function - the standard is the how, the regulation is the must.
Does API RP 1130 apply to gas pipelines?
RP 1130 is written for liquid pipelines and computational monitoring of liquids. Gas leak detection uses different physics and different guidance. Do not assume a liquids CPM program transfers unchanged to a gas gathering or transmission line.
What is the difference between RP 1130 and a leak-detection system?
The system is the software and instrumentation that detects a leak. RP 1130 is the recommended practice for how you select, test, operate, and maintain that system as a program. One is a product; the other is the discipline around it.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.