As part of an ongoing investigation of, the August 6th incident at its Richmond refinery, Chevron (NYSE:CVX), today submitted an update to its 30-Day Report to Contra Costa Health Services. The report provides an update on the status of Chevron’s ongoing internal investigation, which will be completed prior to restart of the refinery’s crude oil processing unit, and an overview of the corrective actions it is taking at the refinery in response to the incident. According to Chevron spokesperson Sean Comey, “These comprehensive actions will strengthen process safety, mechanical integrity, and management oversight.”
According to Comey:
The refinery has begun to develop and implement these corrective actions based on preliminary observations from the investigation team. We have met with governmental agencies, including the Chemical Safety Board, Cal/OSHA, and Contra Costa County Health Services to discuss these efforts, and have previewed these corrective actions with our workforce. Additional actions may be identified upon completion of the investigation, but as detailed in the attached 30-Day Report, efforts are already underway. Specifically, the company is:
- Addressing the susceptibility of carbon steel piping components with low-silicon content to accelerated corrosion when exposed to high temperature sulfidation (“HTS”) conditions.
- Strengthening reliability programs for piping and equipment, and enhancing competency requirements for leaders, inspectors and engineers;
- Strengthening leak response protocols and reinforcing the authority that everyone has to shut down equipment;
- Creating more management oversight and accountability for process safety and re-emphasizing focus on process safety.
SEE FULL REPORT
Chevron submits 30-day report to COntra Costa Health Services by


Bill Gram-Reefer is Editor & Publisher of Halfway To Concord, founded in 2004. Halfway To Concord is the leading online source for community-driven political news, events, and opinion for Contra Costa County and the San Francisco East Bay.
{ 0 comments… add one now }