Feeds:
Posts
Comments

Posts Tagged ‘ISO’

Wreckage of theTrinity Spirit floating production, storage and offloading (FPSO) vessel is seen after an explosion and fire broke out at Shebah Exploration & Production Company Ltd (SEPCOL) offshore production site on Wednesday, in Warri, Nigeria February 4, 2022. REUTERS/Tife Owolabi
Trinity Spirit FPSO

Two weeks after the Trinity Spirit FPSO fire offshore Nigeria we still don’t know the fate of the crew. Neither the operator nor the regulator websites include any mention of the fire. The last operator statement (more than a week ago) advised that 3 workers were confirmed dead and others were still missing. There has been no subsequent update and the media have moved on, as is usually the case when there is no ongoing oil spill.

The absence of transparency in reporting major incidents and subsequent findings is not unique to Nigeria. BOE has commented on US shortcomings in that regard and the failure to release important information about past incidents worldwide.

We need an international standard that identifies incident information to be publicly disclosed and specifies the timeframes and methods for releasing this information. An API or ISO committee would seem to be the best means of developing such a standard. If these organizations are unwilling to take the lead, perhaps the International Regulators’ Forum can do so. The credibility of the offshore industry is at stake.

Read Full Post »

Oh no, industry standards!

Despite the stunning post-Macondo media revelation that regulators <gasp> use “industry standards” (you can’t slip anything past these folks!), there is no need to be fearful or anxious. Regulators of most technologically advanced industries, in the US and throughout the world, depend on such standards. Almost every US Federal agency uses standards to fulfill some of their objectives.

“Industry” standards are really consensus standards developed by experts who work for manufacturers, operators, service companies, universities, regulators, NGOs, and even consultants (for whom I suddenly have great respect :)).  Standards development, which is in accordance with specific protocols, is closely monitored and audited by designated organizations.

In the US, the use of standards is mandated by legislation that stipulates:

All Federal agencies and departments shall use technical standards that are developed or adopted by voluntary consensus standards bodies, using such technical standards as a means to carry out policy objectives or activities determined by the agencies and departments

However, it is important to note that regulators have the final say about which standards or parts of standards they incorporate in their regulatory programs. Regulators are under no obligation to incorporate standards that they believe would compromise safety or environmental objectives.

US standards programs are administered by ANSI.  ISO, a network of the national standards institutes of 163 countries, with a Central Secretariat in Geneva, Switzerland, administers standards worldwide.

While standards developed by API and other organizations have served the US offshore oil and gas program well, improvements can be made.  A few suggestions follow:

  1. Increase the participation by technical specialists from all sectors of industry.  In some cases, corporate mergers and low participation have reduced the diversity of opinion and expert input needed to develop the best possible standards.  All offshore operators, service companies, and contractors should recognize their obligation to participate on standards committees.  Their plans for such participation should be outlined in their safety and environmental management programs.
  2. Increase regulator participation.  While resource constraints limit the involvement of regulators, participation in offshore standards committees should be a high priority.  Wherever possible, Federal, State, and international regulators should pool resources to ensure that standards committees are effectively monitored.
  3. Standards should be available online at no charge to any interested party.  API has taken an important step in that regard by agreeing to provide free access to standards referenced in OCS regulations.
  4. Spin-off API’s standards programs into a new entity.  While API has managed standards development independently from its advocacy functions, the credibility of the standards programs would be enhanced if that work was performed in a separate organization. API’s highly visible advocacy work could be perceived as influencing standards development practices and priorities.  Such perceptions are detrimental to public confidence in critical safety and pollution prevention standards.

Read Full Post »