API issues new refinery safety standards aimed at reducing risks

April 23, 2010
The American Petroleum Institute issued two new refinery safety standards on Apr. 22 that it said will help refiners reduce risks at their installations.

Nick Snow
OGJ Washington Editor

WASHINGTON, DC, Apr. 23 -- The American Petroleum Institute issued two new refinery safety standards on Apr. 22 that it said will help refiners reduce risks at their installations. It said that the first will help processors identify and use safety indicators to reduce risks, while the second will provide guidance on reducing fatigue risks.

API said both standards were developed after the US Chemical Safety Board recommended that API and other stakeholders develop them following CSB’s investigation of the 2005 explosion and fire at BP Products North America Inc.’s Texas City refinery which killed 15 and injured 127 people.

“The industry is constantly looking for ways to enhance worker safety and lower the level of incidents: The only acceptable level is zero,” said Bob Greco, API’s downstream and industry operations group director. The trade association develops recommended standards and practices for the oil and gas industry.

The first standard, Recommended Practice 754, provides companies with leading and lagging process safety indicators for recognizing and evaluating events that may predict safety issues. API said it was developed for the refining and petrochemical industries, but may apply to other businesses with operating systems and processes where loss of containment can cause harm.

API said the second standard, Recommended Practice 755, provides guidance to help manage fatigue risk. It was developed for refineries, petrochemical and chemical operations, natural gas liquefaction plants, and other facilities, API said.

The American National Standards Institute (ANSI) approved both of the standards as meeting its essential requirements. ANSI is the accrediting body for US organizations which develop standards, according to API.

Contact Nick Snow at [email protected].