DNV GL launches risk-based shale development verification service


DNV GL launches risk-based shale development verification service

HOUSTON -- DNV GL has launched an independent verification service based on the provisions of its Recommended Practice for risk management of shale gas developments and operations (RP), regulatory requirements and other publicly available standards. 

The new service will be used as a tool to help assure stakeholders that an independent assessment can assist in preventing incidents, reducing operational costs and limiting the environmental footprint of shale gas developments. Best practices measured in the assessment process include environmental, occupational and process safety, human factors, well integrity, and other elements that may help address the low probability, high consequence incidents under review today.

The verification process determines whether a comprehensive, transparent risk management approach related to risk identification and mitigation has been implemented to allow sustainable shale gas project development or expansion. 

The verification service may be used by operators, regulators, insurance companies, banks and other oil and gas stakeholders to frame the risk dialogue, based on international approaches to risk identification, mitigation and monitoring best practices. 

DNV GL’s verification protocol will issue a conformance statement for all or part of the RP provisions and applicable publicly available standards and regulations.

“As shale gas and liquids development are experiencing exponential growth in North America, a wide range of operational risks have been realized, including gas flaring, fugitive emissions, rail transport incidents, water management, fracing chemicals, explosions, fires, infrastructure limitations, occupational risks, and asset integrity issues,” said Elisabeth Tørstad, CEO of DNV GL Maritime and Oil & Gas. “Industry can gain stakeholder acceptance only by implementing best practices and proactive risk management.”

Related News ///


Comments ///

comments powered by Disqus