Our blogs Blogs home



Leak Detection and API 1149 – do you have an advantage?

Leak DetectionSo here is another episode from the DNV GL – Software “Whiteboard Videos” repository.  A variety of videos are available on the DNV GL – Software website, as well as in Vimeo and YouTube. These videos provide some high level information about topics that are important to the industries that we serve. In this episode, we talk about Leak Detection and API 1149.  So now you may be asking, “what is API 1149?”

Recently, the American Petroleum Institute released the second edition of their Technical Report 1149 titled “Pipeline Variable Uncertainties and Their Effects on Leak Detectability” (API 1149 R2).

Directly from the API folks themselves:

“This document describes procedures for predicting uncertainties in the detection of leaks in pipelines using computational methods based upon physical hydraulic state measurements. This class of pipeline leak detection methods is commonly called computational pipeline monitoring (CPM). A large number of factors are known to contribute to the effectiveness of CPM and it is essential to understand the uncertainty in the prediction made by the CPM algorithm in use regarding the existence, or absence of leaks.”

So in laymen’s terms, the API listed all the issues that they see with leak detection systems.  Then they claim that any computational leak detection system has an inherent uncertainty.  However…

DNV GL’s Synergi Pipeline Simulator based Leak Detection systems do not suffer the challenges of other leak detection solutions.  Regarding the uncertainties defined in API 1149, SPS has a distinct advantage.  And here is Mark Walsh, with a high level explanation about how DNV GL overcomes them:

Leak Detection: Uncertainties Defined in API 1149:

This is just one of many of DNV GL – Software’s informative videos.  So feel free to browse the library of all the videos that are available. Also, let us know what you want to hear more about next!

0 Comments Add your comment

Reply with your comment

Your email address will not be published. Required fields are marked *