International entity for standardization of Arctic shelf operations should be set up according to Gazprom
Between September 14 and 15 Moscow is hosting the 31st plenary meeting of the Technical Committee for Standardization – ISO/TC 67 “Materials, Equipment and Offshore Structures for Petroleum, Petrochemical and Natural Gas Industries”.
Today Vlada Rusakova, Member of the Management Committee – Head of the Strategic Development Department of Gazprom delivered a speech at the meeting.
She informed the audience on Gazprom's project focused on the Arctic shelf and the Yamal Peninsula development as well as creating the necessary gas transmission facilities.
It was noted that the new oil- and gas-bearing regions featured severe natural and climatic conditions. The harsh Arctic climate demands absolutely new approaches and technical solutions and, therefore, new standards. By now, no company has a track record of oil and gas production in such environment.
Vlada Rusakova noted that launching a program aimed at elaborating international-level standards for developing the Barents Sea shelf as part of the Barents 2020 project will be the first step towards meeting this goal.
At the same time, it will be expedient to establish a permanent international entity for standardization to form a comprehensive legal framework for the Arctic region development. Setting up a new subcommittee named “Arctic Operations” and managed by Russia (Gazprom) could be the best option. The speaker noted Gazprom's success in shaping corporate standards to ensure safety and efficiency of the Company's business. They are based on Gazprom's long-standing track record combined with the best skills of global oil and gas industry leaders.
Legal Disclaimer:
EIN Presswire provides this news content "as is" without warranty of any kind. We do not accept any responsibility or liability for the accuracy, content, images, videos, licenses, completeness, legality, or reliability of the information contained in this article. If you have any complaints or copyright issues related to this article, kindly contact the author above.