alarm managementWhat is PHMSA’s intent with this guideline? One of PHMSA’s functions is to study pipeline incidents and make policy suggestions for improving pipeline safety.
PHMSA regulations has identified “individuals” as a vital aspect in pipeline safety. Individuals are typically involved in avoiding pipeline events– occasionally triggering them, in some cases aggravating them and always striving to reduce their unfavorable results.
In examining incidents, PHMSA has discovered that a pipeline controller (controller as used herein is specified as the person seated in the chair facing the control system) may be certified but is not always effective in managing unusual circumstances or events. In fact, the controller’s ability to manage unusual situations may be affected by inadequate treatments, fatigue or even limitations in the SCADA system itself. To supply a balance in between systems, execution and treatments that assist controllers be more effective, PHMSA offers the method “Prevention through People.”.
There are two parts to the rule: 1) Part 192 (gas) and 2) Part 195 (liquids). The guideline passed in December 2009 and ended up being effective Feb. 1, 2010. To satisfy this guideline, owners and operators with pipeline systems managed by controllers using SCADA systems have to have a compliance strategy finished by Aug. 1, 2011 and implemented by Feb. 1, 2013. However, a newly proposed rule would speed up the execution date to Aug. 1, 2011 for many products with a full application by Aug. 1, 2012. At the time this short article was written, the accelerated rule was still under consideration.
Guidelines Vs. Guidance.
API has released a variety of advised practices. API 1165 (Displays), API 1167 (Alarm Management) and API 1168 (Control Room) are released. It must be noted that API 1167 was only recently published. These practices provide high-level assistance however are not authoritative. For instance, API, AGA and others all have tiredness management strategy guidelines tied to fundamental science, but they are irregular in their recommendations.
PHMSA has specified publicly that it does not wish to recommend how pipelines run under the CRM rule as each pipeline operator can very well make its own choices. Additionally, as a SCADA pipeline implementer, the business values the fact that procedures commonly do not provide specific directions on the best ways to construct and deliver control systems that support controllers. Rather, they offer assistance. For that reason, considerable invention is frequently required.
Having actually experienced a variety of other regulative changes throughout the years, consultants started looking for options. Particularly, searching for professionals who understood the rationale and science behind the requirements to aid craft our solutions. Our method was to form relationships with key outside specialists and bring them into our procedure. One such expert is Doug Rothenberg, a Ph.D. engineer who sits on the API 1167 as well as the ISA-18.2 committees on alarm management. For more than 20 years, he has operated in alarm management and incident investigation for the power, petrochemical, refining and process markets. His textbook on alarm management consists of detailed approach on ways to execute an efficient alarm management program.
Our technique integrates the best practices of Rothenberg and Nimmo– including their books and methods– and adapts them to the application needed in the pipeline market. Integrating the pipeline operations experience with the CRM experience of Rothenberg and Nimmo produces a special understanding of not only the requirements, however also the “why” behind the requirements.