Gas pipeline safety management system based on neural network

2022 ◽  
Author(s):  
Syed Muhammad Mujtaba ◽  
Tamiru Alemu Lemma ◽  
Seshu Kumar Vandrangi
Author(s):  
Karen Collins ◽  
Michelle Unger ◽  
Amanda Dainis

Abstract Standards and regulations are clear: all staff who work on pipelines need to be both “competent” and “qualified.” Standards such as API 1173 are clear about competence within a safety management system: “The pipeline operator shall ensure that personnel whose responsibilities fall within the scope of the PSMS [Pipeline Safety Management System] have an appropriate level of competence in terms of education, training, knowledge, and experience.” The burden of defining and specifying competence falls on pipeline operators, but they have little guidance regarding the required skills, knowledge and levels of competency. Additionally, we are all biased — different operators will have different ideas and emphases on competencies, which will affect their decision-making. The only way to avoid these cognitive biases is to use consensus standards supported by rigorous surveys that capture the required competencies. This paper explores some of the more common biases that can affect decisions and presents the results of a controlled, independent, survey aimed at both specifying and quantifying the necessary competencies needed by a specific engineer working within a PSMS: a pipeline integrity engineer. The paper identifies and ranks these necessary competences. The survey was completed by 100 pipeline integrity engineers from 25 different countries. Its specific objective was to investigate the key skills and knowledge requirements needed in a junior engineering position (i.e., a pipeline engineer with less than three years of relevant experience) working under supervision to be ‘competent’. It listed eight core competencies (identified by subject matter experts) considered essential for a pipeline integrity engineer. Each of these core competencies contained a set of skills. Respondents were first asked to rank the eight core competences, and then rank the skills within the competency. An analysis of the data provides insights into how 100 pipeline integrity engineers view the key skills required to be “competent.” The results of the survey can assist pipeline companies in setting objective competency requirements for their engineering personnel, developing learning programs to address any gaps, and improve the overall safety of their pipeline system.


Author(s):  
Megan Weichel

As many pipeline operators embark on the journey of developing a Pipeline Safety Management System (PSMS), the first question is typically, “Where do we begin?” Management systems can be intimidating, and the thought of taking on the task of developing one can seem overwhelming. Companies want to know if it is necessary to start from scratch, if they can use existing processes or programs, and which step to take first for a successful PSMS. There are many ways to begin, but one of the most effective ways is to first ask two questions, “What do we already have?” and “What are our biggest problems?” Armed with these answers, a path forward can be developed, and the foundation for the management system can begin to take shape. One effective way to choose where to begin when developing the PSMS is to determine which elements have been related to the root causes of incidents and near misses in the past. Likewise, continuing to determine and monitor the causes of incidents after the implementation of the PSMS will provide guidance for continual improvement of the management system. Using the elements and sub-elements of existing management system standards or practices, such as API RP 1173, Pipeline Safety Management System Requirements [1], as a starting point for determining root causes is a good way to break down, categorize, and trend the causes of each incident. Combining these with a gap analysis of both the undocumented and documented processes and procedures will provide a basis for determining the priorities for development and implementation of each management system element.


2014 ◽  
Vol 635-637 ◽  
pp. 478-483
Author(s):  
Shu Jiang ◽  
Li Jing Zhang ◽  
Gang Tao ◽  
Zhong Yu Wang

With the arrival of China's oil and gas pipeline network era, the security of oil and gas pipelines confront great challenges. Scientific pipeline safety management methods and concepts are needed. In this paper the SHEM model which is composed of hardware, software, environment and management is put forward to explain the cause of oil and gas pipeline accident. According to the control system of management failure, the oil and gas pipeline accident model based on failure of generalized management is established to provide effective methods for accident prevention and construction of safety management system for oil and gas pipeline.


2021 ◽  
Author(s):  
Alexa S. Burr ◽  
Colin M. Frazier ◽  
S. David Toth

Abstract The American Petroleum Institute (API) represents all segments of the natural gas and oil industry, aiming to accelerate safety and environmental progress across operations while meeting global demand for affordable, reliable, and cleaner energy. Through API and in partnership with the U.S. Pipeline and Hazardous Materials Safety Administration (PHMSA), state pipeline regulators, and other interested stakeholders, pipeline operators developed API Recommended Practice (RP) 1173: Pipeline Safety Management Systems. API RP 1173 users understand how to systematically manage pipeline safety and continuously measure progress to improve overall pipeline safety performance. The core principle of API RP 1173 is the "Plan-Do-Check-Act" cycle. It requires the operator to determine the goals, objectives, and targets needed to be undertaken, complete those initiatives, and periodically review the Pipeline Safety Management System (PSMS) on an operator's determined cycle or at a minimum of a three-year cycle. API RP 1173 and the Pipeline SMS Maturity Model and Tools are primary resources to support API Energy Excellence® implementation. API Energy Excellence (launched in 2021) is another critical API program in which all API members commit to enhance the integrity of operations across the industry by applying standards, implementing workforce training programs, and participating in performance initiatives. Ultimately, these conditions drive the industry towards its zero-incident goal by ensuring that the PSMS's various components are regularly reviewed and continually evolving. To that point and as part of the industry's ongoing commitment to continuous pipeline safety improvements, API, in collaboration with industry partners, developed a not-for-profit Pipeline SMS Assessment Program in 2019 and fully launched the offering in January 2020. Unlike most Pipeline Safety or SMS assessments, the API Third-Party Assessment Program utilizes a diverse set of assessors with multiple affiliations, ranging from traditional SMS firms to retired industry executives who wish to give back to the industry by sharing their experience with others. API has conducted many assessments to date, and the benchmarking from these assessments helps operators gauge how their implementation is relative to their peers. Also, because API is the custodian of RP 1173, learnings from these assessments can naturally be fed back into the standards development process to ensure the next version of RP 1173 is an even better Plan-Do-Check-Act Process. The API Pipeline SMS Assessment (PSMS Assessment) program gives the operator access to the most experienced and knowledgeable assessors. It provides the operator with the opportunity to learn notable practices utilized across the pipeline industry. In 2021 and beyond, API looks forward to taking the assessment program worldwide, increasing industry lessons learned, cataloging good practices, looking for opportunities to increase effectiveness, and giving industry valuable benchmarking, all aimed at our shared goal of zero incidents


2020 ◽  
Vol 9 (3) ◽  
pp. 25-30
Author(s):  
So Yeon Jeon ◽  
Jong Hwa Park ◽  
Sang Byung Youn ◽  
Young Soo Kim ◽  
Yong Sung Lee ◽  
...  

Sign in / Sign up

Export Citation Format

Share Document