<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><!-- generator="wordpress/2.3.3" --><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Risk and Safety Blog</title>
	<link>http://risk-safety.com</link>
	<description>Safety, Security, Reliability</description>
	<pubDate>Wed, 15 Jul 2009 03:08:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/RiskAndSafety" type="application/rss+xml" /><feedburner:emailServiceId>RiskAndSafety</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Will your Refresher Training Work?</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/qMPT5YprTtg/</link>
		<comments>http://risk-safety.com/will-your-refresher-training-work/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 03:08:22 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[Process Safety]]></category>

		<category><![CDATA[Training]]></category>

		<category><![CDATA[safety culture]]></category>

		<category><![CDATA[airline safety video]]></category>

		<category><![CDATA[flight safety annoucement]]></category>

		<category><![CDATA[refresher training]]></category>

		<category><![CDATA[safety e-courses]]></category>

		<category><![CDATA[safety e-learning courses]]></category>

		<category><![CDATA[safety training]]></category>

		<category><![CDATA[safety training video]]></category>

		<guid isPermaLink="false">http://risk-safety.com/will-your-refresher-training-work/</guid>
		<description><![CDATA[In the last two years, I have traveled significantly&#8230;have an elite status on three airlines and lots of frequent flyer miles. There are quite a few aspects of a trip that are routine and boring. One such thing is the safety announcement or video at the beginning of each flight. Why do they have it?
Now [...]]]></description>
			<content:encoded><![CDATA[<p>In the last two years, I have traveled significantly&#8230;have an elite status on three airlines and lots of frequent flyer miles. There are quite a few aspects of a trip that are routine and boring. One such thing is the safety announcement or video at the beginning of each flight. Why do they have it?</p>
<p>Now imagine you are on the US Airways flight that had to be crash-landed in the Hudson. Wouldn’t the instructions about emergency landing on water have been useful? I guess there is a reason landing on water is one of the scenarios in the airline safety announcement.</p>
<p><a href="http://risk-safety.com/wp-content/uploads/2009/07/3201676850_c87044dbb8.jpg" title="US Airways Landing on Hudson"></a></p>
<p style="font-size: 8pt"><a href="http://risk-safety.com/wp-content/uploads/2009/07/3201676850_c87044dbb8.jpg" title="US Airways Landing on Hudson"></a></p>
<p style="text-align: center"><a href="http://risk-safety.com/wp-content/uploads/2009/07/3201676850_c87044dbb8.jpg" title="US Airways Landing on Hudson"><img src="http://risk-safety.com/wp-content/uploads/2009/07/3201676850_c87044dbb8.jpg" alt="US Airways Landing on Hudson" /></a></p>
<p align="center"><span style="font-size: 8pt">Source: <align="center"><a href="http://www.flickr.com/photos/27048731@N03/" rel="cc:attributionURL">http://www.flickr.com/photos/27048731@N03/</a> / <a href="http://creativecommons.org/licenses/by-nc-sa/2.0/" rel="license">CC BY-NC-SA 2.0</a></align="center"></span></p>
<p>The reason frequent travelers ignore the flight safety announcement is <strong><font color="#ff6600">normalization of deviation</font></strong>&#8230; you have seen the message so many times that it begins to lose impact.</p>
<p>I’m therefore very surprised that organizations believe they can achieve effective safety training by having &#8220;canned&#8221; refresher e-courses.</p>
<p>These refresher courses are equivalent of airline safety instructions!!! Unless refresher courses are made more engaging, they cannot be effective. If a worker is asked to take the same refresher course year after year, I&#8217;m afraid he will fall into a &#8220;listen-and-ignore&#8221; mode.</p>
<p>In follow-up posts, I will discuss ways of increasing learning impacts from training courses. As an example, take a look at a recent <a href="http://www.youtube.com/watch?v=eyygn8HFTCo" title="Virgin Atlantic Safety Instruction Video" target="_blank">safety instruction video</a> from <a href="http://www.virginamerica.com/va/home.do" title="Virgin America" target="_blank">Virgin America</a> that is different from routine safety announcement.</p>
<p align="center"><a href="http://www.youtube.com/watch?v=eyygn8HFTCo">www.youtube.com/watch?v=eyygn8HFTCo</a></p>
<p align="left"> Did you find the video engaging?</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=qMPT5YprTtg:OpYXdTohvYE:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=qMPT5YprTtg:OpYXdTohvYE:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=qMPT5YprTtg:OpYXdTohvYE:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/qMPT5YprTtg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/will-your-refresher-training-work/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/will-your-refresher-training-work/</feedburner:origLink></item>
		<item>
		<title>Overview of Chemical Plant Security</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/xpjykBEuKLM/</link>
		<comments>http://risk-safety.com/overview-of-chemical-plant-security/#comments</comments>
		<pubDate>Tue, 07 Jul 2009 17:57:55 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[Regulations]]></category>

		<category><![CDATA[Security]]></category>

		<category><![CDATA[6 CFR 27]]></category>

		<category><![CDATA[chemical of interest (COI)]]></category>

		<category><![CDATA[Chemical Plant Security]]></category>

		<category><![CDATA[high-risk facilities]]></category>

		<category><![CDATA[Homeland security]]></category>

		<category><![CDATA[refinery secrurity]]></category>

		<category><![CDATA[risk based performance standard (PBPS)]]></category>

		<category><![CDATA[security vulnerability analysis (SVA)]]></category>

		<category><![CDATA[site security plan (SSP)]]></category>

		<category><![CDATA[terror threat to refineries]]></category>

		<category><![CDATA[threshold quantity (TQ)]]></category>

		<guid isPermaLink="false">http://risk-safety.com/overview-of-chemical-plant-security/</guid>
		<description><![CDATA[Chemical Facility Anti Terrorism Standard (CFATS) came into force on Nov. 20, 2007 as a Federal Regulation under 6 CFR 27. This set into motion the process of assessing threats to chemical plants and refineries in the U.S.


 Photo Courtesy: http://www.flickr.com/photos/8177037@N06/ / CC BY-NC 2.0 ;
Step 1: Is Your Facility Covered?
Under CFATS, if a facility [...]]]></description>
			<content:encoded><![CDATA[<p>Chemical Facility Anti Terrorism Standard (CFATS) came into force on Nov. 20, 2007 as a Federal Regulation under 6 CFR 27. This set into motion the process of assessing threats to chemical plants and refineries in the U.S.</p>
<p><a href="http://risk-safety.com/wp-content/uploads/2009/07/houston-refineries_view-from-san-jancito-monument.jpg" title="Houston Refineries"></a></p>
<p style="text-align: center"><a href="http://risk-safety.com/wp-content/uploads/2009/07/houston-refineries_view-from-san-jancito-monument.jpg" title="Houston Refineries"><img src="http://risk-safety.com/wp-content/uploads/2009/07/houston-refineries_view-from-san-jancito-monument.jpg" alt="Houston Refineries" /></a></p>
<p align="center"><span style="font-size: 8pt"> Photo Courtesy:<a href="http://" target="_blank"> </a><a href="http://" target="_blank" rel="cc:attributionURL">http://www.flickr.com/photos/8177037@N06/</a><a href="http://" target="_blank"> / </a><a href="http://" target="_blank" rel="license">CC BY-NC 2.0</a><a href="http://" target="_blank"> </a>;</span></p>
<p><strong>Step 1: Is Your Facility Covered?</strong><br />
Under CFATS, if a facility posses a chemical of interest (COI) above a certain threshold quantity (TQ), it must submit a <font color="#008000"><em>Top Screen</em></font> to assist Department of Homeland Security (DHS) in screening for high-risk facilities. DHS reviews the submission to make an initial determination if a facility is high-risk and categorizes it into a risk tier (Tier 1, 2, 3, 4).  To view COI and corresponding TQ <a href="http://www.dhs.gov/xlibrary/assets/chemsec_appendixafinalrule.pdf" title="6 CFR Part 27 Appendix to Chemical Facility Anti-Terrorism Standards" target="_blank">click here</a>.</p>
<p>If your facility has COI above TQ, you should have submitted top screen via <a href="http://www.dhs.gov/xprevprot/programs/gc_1169501486197.shtm" title="Chemical Security Assessment Tool (CSAT)" target="_blank">Chemical Security Assessment Tool (CSAT)</a> by January 2008.It is expected that around 40,000 top screens have been submitted to DHS.  DHS plans to track facilities by checking their business records to verify if they are covered and have not submitted top screen. Facilities that plan to have a COI above TQ on-site at some future time are encouraged to file a Top Screen.</p>
<p><strong>Step 2: Understand the Risks</strong><br />
The results from the Top Screen allow DHS to assign facilities to a preliminary risk tier and make an initial determination of facilities at higher risks. High-risk facilities are notified by DHS and these facilities must complete a Security Vulnerability Assessment (SVA) - i.e. analysis of high-risk scenarios, threat characterization, and associated risk reduction measures. The actual determination of high-risk status and the actual Tier ranking is made by DHS after SVA is submitted.</p>
<p>Tiers 1, 2, and 3 must use <a href="http://www.dhs.gov/xprevprot/programs/gc_1169501486197.shtm" title="Chemical Security Assessment Tool (CSAT)" target="_blank">CSAT SVA</a> tool to conduct SVA. Following the submission of the SVA, DHS will determine if the facility is indeed high-risk and it will notify the facility of its exact risk tier.</p>
<p><strong>Step 3: Developing Site Security Plan (SSP)</strong><br />
Facilities determined as high-risk by DHS following a review of their SVA should prepare a Site Security Plan (SSP). Instructions for preparing <a href="http://www.dhs.gov/xprevprot/programs/gc_1238784785789.shtm" title="Site Security Plan (SSP)" target="_blank">Site Security Plan (SSP)</a> were released in May 2009.  SSP should document how a high-risk facility meets (or intends to meet) the requirements of the 18 <a href="http://www.dhs.gov/xprevprot/programs/gc_1238784785789.shtm" title="Risk Based Performance Standard (RBPS)" target="_blank">Risk Based Performance Standards (RBPS)</a>.  RBPS guidelines include restrict area perimeter, screen and control assets, etc., and are intended to serve as a guidance. Preparation of SSP and submission thus appears to be a documentation exercise - it may be tedious but not difficult.</p>
<p>The RBPS document provides very general guidance on most topics but at the same time DHS is prohibited from providing specific guidance.  However, it is fair to say that RBPS guidelines reflect DHS&#8217; view on various security measures.</p>
<p>Once the SSP is submitted, DHS will notify the facility if the SSP is approved, or if it requires revision. DHS will work with facilities on revisions. Once the SSP is approved it becomes essentially a contract between DHS and the facility and will provide the basis for future facility inspections.</p>
<p>The SSP does not correlate directly with the RBPS and thus at the end of SSP submission a facility owner is not able to analyze the additional work needed to meet RBPS requirements. Thus an on-going task for facility security manager would be to figure out gaps between their existing security measures in place and the RBPS requirements.</p>
<p>For detailed information on Chemical Security, please refer to an excellent blog by <a href="http://chemical-facility-security-news.blogspot.com/">Patrick Coyle</a>.</p>
<p>If you have any specific questions about applicability of chemical security regulations to your facility, please <a href="http://risk-safety.com/contact/" target="_blank" title="Contact Form">contact me</a>.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=xpjykBEuKLM:ThBJ8bLoOyM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=xpjykBEuKLM:ThBJ8bLoOyM:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=xpjykBEuKLM:ThBJ8bLoOyM:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/xpjykBEuKLM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/overview-of-chemical-plant-security/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/overview-of-chemical-plant-security/</feedburner:origLink></item>
		<item>
		<title>GAO: CSB Not Meeting Its Statutory Mandates</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/L61ikk7sYoE/</link>
		<comments>http://risk-safety.com/gao-csb-not-meeting-its-statutory-mandates/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 21:11:03 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[Incident Investigation]]></category>

		<category><![CDATA[Process Safety]]></category>

		<category><![CDATA[Regulations]]></category>

		<category><![CDATA[Chemical Accidents]]></category>

		<category><![CDATA[Chemical Safety Board]]></category>

		<category><![CDATA[CSB]]></category>

		<category><![CDATA[fatalities]]></category>

		<category><![CDATA[GAO]]></category>

		<category><![CDATA[Government Accountability Office]]></category>

		<category><![CDATA[incident investigationU.S. Chemical Safety Board]]></category>

		<category><![CDATA[U.S. Chemical Safety Board]]></category>

		<category><![CDATA[US CSB]]></category>

		<guid isPermaLink="false">http://risk-safety.com/gao-csb-not-meeting-its-statutory-mandates/</guid>
		<description><![CDATA[According to a recent report (Aug. 2008) from the Government Accountability Office (GAO), the Chemical Safety Board (CSB) is not in compliance with its statutory mandates.  The CSB is an independent federal agency charged with investigating industrial chemical accidents and has been in operation since 1998. GAO report states that CSB is not investigating all [...]]]></description>
			<content:encoded><![CDATA[<p>According to a recent report (Aug. 2008) from the <a href="http://www.gao.gov" title="Government Accountability Office (GAO)" target="_blank">Government Accountability Office (GAO)</a>, the <a href="http://www.csb.gov" title="Chemical Safety Board">Chemical Safety Board (CSB)</a> is not in compliance with its statutory mandates.  The CSB is an independent federal agency charged with investigating industrial chemical accidents and has been in operation since 1998. GAO report states that CSB is not investigating all chemical releases that have a fatality, serious injury, substantial property damage, or the potential for a fatality, serious injury, or substantial property damage.</p>
<p>The following table summarizes CSB performance in 2006-2007.</p>
<p><strong><strong></p>
<table class="wptable rowstyle-alt" id="wptable-9"  cellspacing="1">
	<thead>
	<tr>
		<td style="width:300px" >&nbsp;</td>
		<th class="sortable" style="width:30px" align="center">2006</th>
		<th class="sortable" style="width:30px" align="center">2007</th>
	</tr>
	</thead>
	<tr>
		<td style="width:300px" align="left">Total accidents recorded in CSB database</td>
		<td style="width:30px" align="center">822</td>
		<td style="width:30px" align="center">920</td>
	</tr>
	<tr class="alt">
		<td style="width:300px" align="left">Accidents with Fatalities</td>
		<td style="width:30px" align="center">38</td>
		<td style="width:30px" align="center">35</td>
	</tr>
	<tr>
		<td style="width:300px" align="left">Accidents CSB Investigated</td>
		<td style="width:30px" align="center">6</td>
		<td style="width:30px" align="center">5</td>
	</tr>
	<tr class="alt">
		<td style="width:300px" align="left">Accidents with Fatalities CSB Investigated</td>
		<td style="width:30px" align="center">5</td>
		<td style="width:30px" align="center">1</td>
	</tr>
</table><p>
</strong></strong></p>
<p>CSB is limited by budget and resources as to how many incidents it can investigate. GAO has recommended that CSB request the necessary resources from Congress to meet CSB’s statutory mandate or seek an amendment to its statutory mandate. Alternatively, GAO makes the following recommendations to help CSB cover more incidents.</p>
<ul>
<li>consider using the work of government agencies, companies, and contractors, to a greater extent to maximize the board’s limited resources;</li>
<li>improve the quality of its accident-screening database by better controlling data entry and periodically sampling accident data to evaluate their consistency and completeness;</li>
<li>publish a regulation requiring facilities to report all chemical accidents, as required by law, to better inform the agency of important details about accidents that it may not receive from current sources;</li>
</ul>
<p>To download a pdf copy of the GAO report on CSB click on the link below:<br />
<a href="http://risk-safety.com/wp-content/uploads/2009/06/d08864r.pdf" target="_blank" title="Chemical Safety Board: Improvements in Management and Oversight Are Needed">Chemical Safety Board: Improvements in Management and Oversight Are Needed</a>.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=L61ikk7sYoE:dEsCV6aZ1sM:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=L61ikk7sYoE:dEsCV6aZ1sM:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=L61ikk7sYoE:dEsCV6aZ1sM:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/L61ikk7sYoE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/gao-csb-not-meeting-its-statutory-mandates/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/gao-csb-not-meeting-its-statutory-mandates/</feedburner:origLink></item>
		<item>
		<title>Is your Organization Making the Right Decisions?</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/QD6BdKoAiQU/</link>
		<comments>http://risk-safety.com/is-your-organization-making-the-right-decisions/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 20:10:39 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[Decision Analysis]]></category>

		<category><![CDATA[Human Factors]]></category>

		<category><![CDATA[Process Safety]]></category>

		<category><![CDATA[safety culture]]></category>

		<category><![CDATA[complex decision making]]></category>

		<category><![CDATA[group decisions]]></category>

		<category><![CDATA[Human Error]]></category>

		<category><![CDATA[human factors affecting safety]]></category>

		<category><![CDATA[multi-attribute decision analysis]]></category>

		<category><![CDATA[organizational safety]]></category>

		<category><![CDATA[wisdom of crowds]]></category>

		<guid isPermaLink="false">http://risk-safety.com/is-your-organization-making-the-right-decisions/</guid>
		<description><![CDATA[We make hundreds of decisions everyday in our lives – for example should I eat fries with my burger?

(Photo Courtesy of Amber on Flickr)
Eating a few fries this one time will not increase risks of a heart attack. Plus I like the fries from this joint. I’m ready to order!!
That was a relatively easy decision; [...]]]></description>
			<content:encoded><![CDATA[<p>We make hundreds of decisions everyday in our lives – for example should I eat fries with my burger?</p>
<p align="center"><a href="http://risk-safety.com/wp-content/uploads/2009/06/2891650601_4fa58ec3c6.jpg" title="Daily decision making"><img src="http://risk-safety.com/wp-content/uploads/2009/06/2891650601_4fa58ec3c6.jpg" alt="Daily decision making" /></a></p>
<p align="center"><span style="font-size: 8pt">(Photo Courtesy of Amber on <a href="http://www.flickr.com/photos/57719803@N00/2891650601/" title="Decision Making">Flickr</a>)</span></p>
<p><em>Eating a few fries this one time will not increase risks of a heart attack. Plus I like the fries from this joint. I’m ready to order!!</em></p>
<p>That was a relatively easy decision; however, there are certain decisions that are more complex and may have significant implications to your organization&#8217;s future including organizational safety.</p>
<p>For example, if your organization is deciding on future investments or acquisitions. One would think that the basis for such complex decisions would be financial metrics – return on investment (ROI), life-cycle analysis, Net present value (NPV). Clearly these economic figures incorporate cost-benefit analysis. However, in a real world situation one cannot mitigate all the risks in an investment and therefore some of the most complex decisions are influenced by various other factors – internal politics, stakeholder interests, lack of complete knowledge. How can we bring rationale to such decisions?</p>
<p><strong>Group Decisions</strong></p>
<p>Group decisions in particular are prone to be influenced by emotions rather than logic. It is therefore necessary that everyone in the group understands the basis of decision and agrees to conclusions being reached. Group decision situations can be very effectively dealt with using Multi-attribute decision analysis (MADA).</p>
<p>Let me give you a simple example. Say you are in the market looking for a car, first you have to decide upon criteria for buying decision. You come up with three main attributes you would want in your new car – price, mileage and safety. But which of these three is more important to you? Would you be willing to sacrifice safety for price? So you want to prioritize attributes. Then you go from one dealer to other and compare different models. Come decision time what you are doing is mentally creating a scorecards for cars you have looked at and figure out the winner based on price, mileage and safety.</p>
<p>The same thought process can be duplicated for group decisions. What attributes to select? How to weigh the attributes? All these decisions are taken by the group and thus the end result represents “Wisdom of the Crowds”.</p>
<p>Of course to do this methodically I recommend using Analytical Hierarchical Processing (AHP) to select attributes, decide their weights and then final outcome. If you need further information on this topic please <a href="http://risk-safety.com/contact/" title="Contact Form" target="_blank">contact me</a>.</p>
<p><strong>When Should you Consider Group Decision Methods? </strong></p>
<p>I recommend one should look into group decisions when considering investment of $5-million or more when you are trying to answer one of the following questions:</p>
<ul>
<li>Which projects to fund and to what extent?</li>
<li>How to adjust operations and maintenance resources?</li>
<li>How to adjust funding levels as resource constraints change?</li>
<li>What acquisitions best fit with organizations mission/goals?</li>
<li>How to create an investment risk portfolio based on available knowledge?</li>
</ul>
<p>Group decisions using MADA are an effective way of creating transparent decisions by efficiently capturing ideas of all stakeholders and providing a common decision platform.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=QD6BdKoAiQU:xPC2j8-Dl30:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=QD6BdKoAiQU:xPC2j8-Dl30:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=QD6BdKoAiQU:xPC2j8-Dl30:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/QD6BdKoAiQU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/is-your-organization-making-the-right-decisions/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/is-your-organization-making-the-right-decisions/</feedburner:origLink></item>
		<item>
		<title>Developing Trust While Communicating Risks</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/Rx2fJ6ZjyYY/</link>
		<comments>http://risk-safety.com/developing-trust-while-communicating-risks/#comments</comments>
		<pubDate>Sun, 07 Jun 2009 17:42:11 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[LNG]]></category>

		<category><![CDATA[Risk Communication]]></category>

		<category><![CDATA[Risk Perception]]></category>

		<category><![CDATA[BANANA]]></category>

		<category><![CDATA[Build Absolutely Nothing Anywhere Near Anyone]]></category>

		<category><![CDATA[hazards]]></category>

		<category><![CDATA[NIMBY]]></category>

		<category><![CDATA[Not in my backyard]]></category>

		<category><![CDATA[public right to know]]></category>

		<category><![CDATA[Risks]]></category>

		<category><![CDATA[risks from LNG terminals]]></category>

		<category><![CDATA[risks from nuclear power plants]]></category>

		<guid isPermaLink="false">http://risk-safety.com/developing-trust-while-communicating-risks/</guid>
		<description><![CDATA[Communicating risks to public from chemical or nuclear facilities is a major challenge. We notice this over and over again with EPA community-right-to-know, nuclear power plants and lately with the LNG facilities.
I want to focus on a critical aspect of this risk communication – winning the trust of the community.
There are two major cognitive social [...]]]></description>
			<content:encoded><![CDATA[<p>Communicating risks to public from chemical or nuclear facilities is a major challenge. We notice this over and over again with EPA community-right-to-know, nuclear power plants and lately with the LNG facilities.</p>
<p>I want to focus on a critical aspect of this risk communication – winning the trust of the community.</p>
<p>There are two major cognitive social psychology principles one must understand while planning a risk communication program:</p>
<p><font color="#ff8c00">1. If an individual has strong initial impressions of a hazard, then subsequent evidence will be influenced by these beliefs. New evidence will appear reliable <span style="text-decoration: underline">if it is consistent</span> with initial impressions. And similarly, new evidence will be dismissed if <span style="text-decoration: underline">it is contrary</span> to initial impression.</font></p>
<p>For example, if you are talking about risks from LNG terminals and the neighbors are concerned about explosion hazards or terror threats, you cannot simply dismiss them. I have noticed in some of these meetings citizens raising question about hazards and some PR firm answers LNG is a clean energy source. Within a minute this evidence will be dismissed!You have to acknowledging the hazards/risks consistent with initial impressions and then present your strategy for minimizing risks.</p>
<p>Remember people receive information from media, talking to other people, news, blogs, radio and all these come into account in risk perception. Without complete knowledge of the system, such as LNG terminal, decisions of a person are based on beliefs concerning likelihood of uncertain events. And we know these likelihoods are minimal – now all you have to do is show what steps are being taken in order to reduce the likelihood.</p>
<p><font color="#ff8c00">2. If an individual lacks strong prior opinions about a hazard, their risk perception will be influence by <span style="text-decoration: underline">HOW</span> the information is presented.</font></p>
<p>As an example, if a patient is offered a treatment option with 70% chance of survival (as opposed to 30% chance of death) he is more than likely to accept the treatment. Framing the statistics in terms of living rather than dying changes risks perceived by the patient.</p>
<p>So what does all this mean in context of developing a risk communication or crisis communication plan:</p>
<ol>
<li>Realize you will have two distinct categories of people – people who have developed prior opinions and people who have no prior idea</li>
<li>Plan your presentation for both these categories.</li>
<li>For audience without a prior belief system educate them with past statistics.</li>
<li>Audience who have a prior opinion you have to acknowledge the hazards and focus on risk mitigation measures</li>
</ol>
<p>You can keep the above guidelines and now you have to decide</p>
<ul>
<li>What information to communicate</li>
<li>How best to put across the information</li>
<li>Who should communicate</li>
</ul>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=Rx2fJ6ZjyYY:YEsrXZdqsvk:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=Rx2fJ6ZjyYY:YEsrXZdqsvk:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=Rx2fJ6ZjyYY:YEsrXZdqsvk:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/Rx2fJ6ZjyYY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/developing-trust-while-communicating-risks/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/developing-trust-while-communicating-risks/</feedburner:origLink></item>
		<item>
		<title>Maintaining Process Safety During Tough Economy</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/vRmOEC4V3S4/</link>
		<comments>http://risk-safety.com/maintaining-process-safety-during-tough-economy/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 01:44:25 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[PSM]]></category>

		<category><![CDATA[Process Safety]]></category>

		<category><![CDATA[Risk Communication]]></category>

		<category><![CDATA[accident prevention]]></category>

		<category><![CDATA[downturn]]></category>

		<category><![CDATA[economic downturn]]></category>

		<category><![CDATA[economic slowdown]]></category>

		<category><![CDATA[financial crisis]]></category>

		<category><![CDATA[preventive maintenance]]></category>

		<category><![CDATA[recession]]></category>

		<guid isPermaLink="false">http://risk-safety.com/maintaining-process-safety-during-tough-economy/</guid>
		<description><![CDATA[We appear to be in a global recession – companies all over are struggling to deal with impact of economic slowdown. In an attempt to maintain profits, companies are drastically reducing their spending and also trimming down their workforce. It is anticipated that one-fourth of the employers in the US will undergo workforce reduction in [...]]]></description>
			<content:encoded><![CDATA[<p>We appear to be in a global recession – companies all over are struggling to deal with impact of economic slowdown. In an attempt to maintain profits, companies are drastically reducing their spending and also trimming down their workforce. It is anticipated that one-fourth of the employers in the US will undergo workforce reduction in 2009. As a result of pessimism and uncertainty about future, there is an increased level of anxiety amongst the employees. There are a few issues that a chemical manufacturing firm must address to ensure safe operation during the downturn:</p>
<ol>
<li><u>Morale of the workers</u>:  The glooming uncertainty about jobs and increased level of anxiety leads to a disinterest amongst employees. It makes workers less productive and starts affecting their day-to-day decisions including the ones regarding safety.</li>
<li><u>Procedural risk mitigation</u>: There are many potentially dangerous scenarios where procedures are put in place as risk mitigation measures. In a state of anxiety and worry, a worker is more likely to commit an resulting in serious consequences.</li>
<li><u>Loss of knowledgeable personnel</u>: Trimming of workforce may result in loss of valuable tacit knowledge in the form of experienced employees.</li>
<li><u>Scheduled maintenance</u>: As a cost cutting measure, an operating company may decide to delay planned maintenance. John Bresland of CSB talks about this issues in the <a href="http://www.youtube.com/watch?v=zR7j5fb-cm4" title="Maintain Process Safety During the Recession">video</a> below:</li>
</ol>
<p align="center"><a href="http://www.youtube.com/watch?v=zR7j5fb-cm4" title="Maintain Process Safety During the Recession" target="_blank"><a href="http://www.youtube.com/watch?v=zR7j5fb-cm4">www.youtube.com/watch?v=zR7j5fb-cm4</a></a></p>
<p><strong>Recommendations for Managers</strong></p>
<ul>
<li>Revisit your high risk scenarios that require procedural risk mitigation measures. It may be worthwhile to investigate automation instead of human intervention.</li>
<li>Figure out ways to cheer employees and keep them in an upbeat mood. If you have any suggestions on boosting employee moral please write them in the comments section below this post.</li>
<li>Here is a free e-book (Author: Wendy Mack) - <a href="http://wendymack.com/anxietyintoenergy/" title="Transforming Anxiety to Energy">How to Prevent Panic and Promote Productivity in Turbulent Times</a>.</li>
</ul>
<p><a href="http://wendymack.com/anxietyintoenergy/" title="Transforming Anxiety to Energy"></a></p>
<p style="text-align: center"><a href="http://wendymack.com/anxietyintoenergy/" title="Transforming Anxiety to Energy"><img src="http://risk-safety.com/wp-content/uploads/2009/05/transforming-anxiety-into-energy-cover.jpg" alt="Transforming Anxiety to Energy" /></a></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=vRmOEC4V3S4:BUWesyAF6pc:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=vRmOEC4V3S4:BUWesyAF6pc:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=vRmOEC4V3S4:BUWesyAF6pc:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/vRmOEC4V3S4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/maintaining-process-safety-during-tough-economy/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/maintaining-process-safety-during-tough-economy/</feedburner:origLink></item>
		<item>
		<title>Safety Forecast for the 21st Century</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/a04TMxMqqqs/</link>
		<comments>http://risk-safety.com/safety-forecast-for-the-21st-century/#comments</comments>
		<pubDate>Sun, 24 May 2009 17:00:34 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[PSM]]></category>

		<category><![CDATA[Process Safety]]></category>

		<category><![CDATA[21st century predictions]]></category>

		<category><![CDATA[29 CFR 1910.119]]></category>

		<category><![CDATA[Accidents]]></category>

		<category><![CDATA[Bhopal accident]]></category>

		<category><![CDATA[Bhopal tragedy]]></category>

		<category><![CDATA[Chemical Accidents]]></category>

		<category><![CDATA[Flixborough]]></category>

		<category><![CDATA[fN curve]]></category>

		<category><![CDATA[incidents]]></category>

		<category><![CDATA[OSHA PSM]]></category>

		<category><![CDATA[Process Accidents]]></category>

		<category><![CDATA[process incidents]]></category>

		<category><![CDATA[Process Safety Management]]></category>

		<category><![CDATA[PSM incidents]]></category>

		<guid isPermaLink="false">http://risk-safety.com/safety-forecast-for-the-21st-century/</guid>
		<description><![CDATA[The 20th century was a time of great technological change that forever transformed how we live and work – changes that necessitated the birth and development of the field of Process Safety Management. The early years saw the evolution of mechanization into assembly lines and true industrialization.  Lack of access to South American nitrate during [...]]]></description>
			<content:encoded><![CDATA[<p>The 20th century was a time of great technological change that forever transformed how we live and work – changes that necessitated the birth and development of the field of Process Safety Management. The early years saw the evolution of mechanization into assembly lines and true industrialization.  Lack of access to South American nitrate during World War I, led to the creation of the synthetic chemical industry.  World War II fostered increased industrial growth and sophistication.  By the 1960s, we were building computers and beginning our race to the moon.  Industries grew becoming increasingly sophisticated and reliant on automated systems.  The 1970s brought the creation of the US EPA and OSHA.  The 1980s witnessed one of the greatest tragedies in the last century – an estimated 4,000 people died in the 1984 Bhopal accident. Since then, the process safety community has evolved in its approaches and methodologies to better manage risks.</p>
<p>But what have we, as process safety professionals, learned from the experiences of the 20th century? How can we use that learning to make the process industry safer in the 21st Century?</p>
<p><strong>20th Century Accident Data</strong><br />
Based on data from Lee’s Loss Prevention Handbook, 551 incidents occurred during the 81 years from 1911-1995.</p>
<p><img src="http://www.risk-safety.com/wp-content/themes/big-blue-01/images/accidents.jpg" alt="accidents" /></p>
<ul>
<li>Out of these 551 incidents, 270 (49%) resulted in a zero fatalities</li>
<li>374 (68%) of the accidents resulted in less than four fatalities</li>
<li>18 incidents (3% of 551) resulted in 100 or more fatalities</li>
</ul>
<p>A more elegant way to analyze the accident data is to construct a fN curve, where f is the cumulative frequency of incidents leading to N or more fatalities.</p>
<p>In this fN curve,</p>
<ul>
<li>The first point represents the 281 incidents that resulted in one or more fatalities.</li>
<li>The last point is the Bhopal accident, which is estimated to have resulted in 4,000 fatalities</li>
</ul>
<p><strong> </strong><img src="http://www.risk-safety.com/wp-content/themes/big-blue-01/images/fncurve.jpg" alt="accidents" /></p>
<p>Based on the 20th century fN curve, we observe</p>
<ul>
<li>In the 1911-1995 time frame there were 100 incidents that resulted in 10 or more fatalities – an average of 1.2 incidents per year in which 10 or more people were killed.</li>
<li>There were 18 incidents (3%) in which more than 100 people died – an average of 1 incident every six years.</li>
<li>There were 3 incidents (0.54%) in which more than 1,000 died – an average of 1 incident every 28 years.</li>
</ul>
<p><strong>Prognosis for the 21st Century </strong></p>
<p>How will the fN curve look for the 21st century? Without a crystal ball, a simplistic prediction is that the 21st century curve will be identical to the 20th century. So should we expect 551 process incidents again by 2099?</p>
<link href="file:///C:%5CDOCUME%7E1%5Cssaraf%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml" rel="File-List" /><!--[if gte mso 9]><xml>  <o:OfficeDocumentSettings>   <o:RelyOnVML/>   <o:AllowPNG/>  </o:OfficeDocumentSettings> </xml><![endif]-->
<link href="file:///C:%5CDOCUME%7E1%5Cssaraf%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx" rel="themeData" />
<link href="file:///C:%5CDOCUME%7E1%5Cssaraf%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml" rel="colorSchemeMapping" /><!--[if gte mso 9]><xml>  <w:WordDocument>   <w:View>Normal</w:View>   <w:Zoom>0</w:Zoom>   <w:TrackMoves/>   <w:TrackFormatting/>   <w:PunctuationKerning/>   <w:ValidateAgainstSchemas/>   <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>   <w:IgnoreMixedContent>false</w:IgnoreMixedContent>   <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>   <w:DoNotPromoteQF/>   <w:LidThemeOther>EN-US</w:LidThemeOther>   <w:LidThemeAsian>X-NONE</w:LidThemeAsian>   <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>   <w:Compatibility>    <w:BreakWrappedTables/>    <w:SnapToGridInCell/>    <w:WrapTextWithPunct/>    <w:UseAsianBreakRules/>    <w:DontGrowAutofit/>    <w:SplitPgBreakAndParaMark/>    <w:DontVertAlignCellWithSp/>    <w:DontBreakConstrainedForcedTables/>    <w:DontVertAlignInTxbx/>    <w:Word11KerningPairs/>    <w:CachedColBalance/>   </w:Compatibility>   <m:mathPr>    <m:mathFont m:val="Cambria Math"/>    <m:brkBin m:val="before"/>    <m:brkBinSub m:val="&#45;-"/>    <m:smallFrac m:val="off"/>    <m:dispDef/>    <m:lMargin m:val="0"/>    <m:rMargin m:val="0"/>    <m:defJc m:val="centerGroup"/>    <m:wrapIndent m:val="1440"/>    <m:intLim m:val="subSup"/>    <m:naryLim m:val="undOvr"/>   </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml>  <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267">   <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal"/>   <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>   <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>   <w:LsdException Locked="false" Priority="39" Name="toc 1"/>   <w:LsdException Locked="false" Priority="39" Name="toc 2"/>   <w:LsdException Locked="false" Priority="39" Name="toc 3"/>   <w:LsdException Locked="false" Priority="39" Name="toc 4"/>   <w:LsdException Locked="false" Priority="39" Name="toc 5"/>   <w:LsdException Locked="false" Priority="39" Name="toc 6"/>   <w:LsdException Locked="false" Priority="39" Name="toc 7"/>   <w:LsdException Locked="false" Priority="39" Name="toc 8"/>   <w:LsdException Locked="false" Priority="39" Name="toc 9"/>   <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>   <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title"/>   <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>   <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>   <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong"/>   <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>   <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>   <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>   <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>   <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>   <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote"/>   <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>   <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6"/>   <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6"/>   <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6"/>   <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>   <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>   <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>   <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>   <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>   <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>   <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>   <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6"/>   <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>   <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6"/>   <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>   <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>   <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>   <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>   <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>   <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>   <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>   <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>  </w:LatentStyles> </xml><![endif]-->As technology progresses, clearly it will impact the fN curve.Based on my experience, I’m going to propose a <font color="#ff6600">Saraf fN curve</font> predicting fatalities in the process industry for the 21st century.<br />
<style> <!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:1; 	mso-generic-font-family:roman; 	mso-font-format:other; 	mso-font-pitch:variable; 	mso-font-signature:0 0 0 0 0 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin-top:0in; 	margin-right:0in; 	margin-bottom:10.0pt; 	margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-bidi-font-family:"Times New Roman";} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	font-size:10.0pt; 	mso-ansi-font-size:10.0pt; 	mso-bidi-font-size:10.0pt; 	mso-ascii-font-family:Calibri; 	mso-fareast-font-family:Calibri; 	mso-hansi-font-family:Calibri;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --> </style>
<p><!--[if gte mso 10]></p>
<style>  /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} </style>
<p> <![endif]--></p>
<p><img src="http://www.risk-safety.com/wp-content/themes/big-blue-01/images/fncurve21st_century.jpg" alt="death vs accidents" /></p>
<p>Here are my predictions regarding the safety performance of the process industry in our  current century:</p>
<ul>
<li>There will be a drop in incidents that result in 1-10 fatalities because of increased hard hat safety requirements and awareness among workers due to better access to hazard communication and training.</li>
</ul>
<ul>
<li>In the last century, 18 incidents resulted in 100 or more fatalities. This number will decrease in the 21st century as risk mitigation measures for high consequence incidents become more reliable.</li>
</ul>
<ul>
<li>I believe the frequency of incidents that result in 10-20 fatalities will remain comparable. Such incidents are typically a result of human error, siting issues, proximity to community, poor plant design, and maintenance/inspection programs. Based on my understanding, I do not envision elimination of these key safety issues within a matter of a few decades. Zero incident plants are not a reality.</li>
</ul>
<p><strong>Final Word</strong></p>
<p><strong><font color="#ff6600">Every decade in the 21st century, the process industry will witness an incident that will result in at least 10 fatalities. </font></strong></p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=a04TMxMqqqs:bfDXLlMPMCw:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=a04TMxMqqqs:bfDXLlMPMCw:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=a04TMxMqqqs:bfDXLlMPMCw:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/a04TMxMqqqs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/safety-forecast-for-the-21st-century/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/safety-forecast-for-the-21st-century/</feedburner:origLink></item>
		<item>
		<title>OSHA Working on Dust Explosion Regulation</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/N1cSUzf0aRw/</link>
		<comments>http://risk-safety.com/osha-working-on-dust-explosion-regulation/#comments</comments>
		<pubDate>Mon, 18 May 2009 00:03:55 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[Dust Explosions]]></category>

		<category><![CDATA[Fires and explosions]]></category>

		<category><![CDATA[Regulations]]></category>

		<category><![CDATA[combustible dust]]></category>

		<category><![CDATA[CSB]]></category>

		<category><![CDATA[dust explosion]]></category>

		<category><![CDATA[Imperial sugar accident]]></category>

		<category><![CDATA[OSHA]]></category>

		<category><![CDATA[regulation]]></category>

		<guid isPermaLink="false">http://risk-safety.com/osha-working-on-dust-explosion-regulation/</guid>
		<description><![CDATA[OSHA is currently working on regulation for preventing dust explosions.
The first reported dust explosion was in 1890 in a sugar mill in Chicago. According to the CSB investigation, dust explosion has resulted in 130 deaths and 780 injuries since 1980. According to Combustible Dust Institute research of news reports, there were 200+ dust fires and [...]]]></description>
			<content:encoded><![CDATA[<p>OSHA is currently working on regulation for preventing dust explosions.</p>
<p>The first reported dust explosion was in 1890 in a sugar mill in Chicago. According to the CSB investigation, dust explosion has resulted in 130 deaths and 780 injuries since 1980. According to<a href="http://dustexplosions.blogspot.com/" title="Combustible Dust Institute" target="_blank"> Combustible Dust Institute</a> research of news reports, there were 200+ dust fires and explosions in the United States in 2008 alone. Following the 2006 recommendations from the Chemical Safety Board (CSB) to regulate &#8220;dust&#8221;, OSHA started investigating if the available dust explosion standards are adequate. After the 2008 sugar-dust explosion that killed 14 workers, OSHA has decided to regulate dust explosion.</p>
<p>A dispersed cloud of dust in a confined space when ignited can lead to an explosion. A major problem is workers are not aware of the hazard or they do not always know the dusts that can explode. Because dust explosions are manifestation of dust properties and confined space where the dust is released.  Dust comes as fine particles, chips, flakes made up of metals, wood, grains, foams, plastics, rubber, pharmaceutical drugs, coal, flour, or sugar.</p>
<p>There are existing NFPA standards aimed at dust explosions but the compliance is not mandated. It will interesting to see how OSHA approaches dust regulations.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=N1cSUzf0aRw:NftM5CntNrs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=N1cSUzf0aRw:NftM5CntNrs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=N1cSUzf0aRw:NftM5CntNrs:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/N1cSUzf0aRw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/osha-working-on-dust-explosion-regulation/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/osha-working-on-dust-explosion-regulation/</feedburner:origLink></item>
		<item>
		<title>External Damage: The Number 1 Cause of Natural Gas Pipeline Incidents</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/1P3L5NtnqzU/</link>
		<comments>http://risk-safety.com/external-interferencedamage-the-number-1-cause-of-natural-gas-pipeline-incidents/#comments</comments>
		<pubDate>Mon, 11 May 2009 03:47:23 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[Failure Data]]></category>

		<category><![CDATA[Fires and explosions]]></category>

		<category><![CDATA[Natural Gas Pipelines]]></category>

		<category><![CDATA[Explosion]]></category>

		<category><![CDATA[external interferance]]></category>

		<category><![CDATA[failure]]></category>

		<category><![CDATA[Fire]]></category>

		<category><![CDATA[Natural gas]]></category>

		<category><![CDATA[pipeline]]></category>

		<guid isPermaLink="false">http://risk-safety.com/external-interferencedamage-the-number-1-cause-of-natural-gas-pipeline-incidents/</guid>
		<description><![CDATA[I recently came across a report from European Gas Pipeline Incident Data Group (EGIG) titled &#8220;Safety Performance Determines The Acceptability of Cross Country Gas Transmission Systems&#8221;. The paper presents incident data contributed by six European gas transmission operators over a 30-year period of 1970-2001.
An incident within this failure database implies unintentional release of gas and [...]]]></description>
			<content:encoded><![CDATA[<p>I recently came across a report from <a href="http://www.egig.nl/" title="EGIG" target="_blank">European Gas Pipeline Incident Data Group (EGIG) </a>titled &#8220;Safety Performance Determines The Acceptability of Cross Country Gas Transmission Systems&#8221;. The paper presents incident data contributed by six European gas transmission operators over a 30-year period of 1970-2001.</p>
<p>An incident within this failure database implies unintentional release of gas and a release is classified in one of the three categories:</p>
<ol>
<li>Pinhole crack - diameter of leak is 2-cm or less</li>
<li>Holes -leak diameter greater than 2-cm but less than pipe diameter</li>
<li>Ruptures - diameter of leak is pipeline diameter</li>
</ol>
<p>According to the report, the main causes for pipeline releases are:</p>
<ol>
<li>External interference: Activities such as digging, pipling, ground works, excavation, ploughing, slabbing, casing and sleeves may damage the pipeline.</li>
<li>Corrosion: It can be external or internal</li>
<li> Material failure: Due to construction of material, defect specification</li>
<li>Ground movement: dike break, erosion, flood, landslide, mining</li>
</ol>
<p>Relative percentage of incidents based on incident cause is presented in table below - <font color="#ff6600"><strong>50% of the pipeline releases appear to be caused by external interference</strong></font>. Furthermore, when a pipeline is damaged by external interference there is a 75% chance that it will lead to a hole or a guillotine rupture.</p>
<p><strong> </p>
<h2>Initiating Events Leading to Pipeline Incidents</h2>
<table class="wptable rowstyle-alt" id="wptable-8"  cellspacing="1">
	<thead>
	<tr>
		<th class="sortable" style="width:200px" align="center">Initiating Event</th>
		<th class="sortable" style="width:30px" align="center">%</th>
	</tr>
	</thead>
	<tr>
		<td style="width:200px" align="center">External interference</td>
		<td style="width:30px" align="center">50</td>
	</tr>
	<tr class="alt">
		<td style="width:200px" align="center">Construction defect</td>
		<td style="width:30px" align="center">17</td>
	</tr>
	<tr>
		<td style="width:200px" align="center">Corossion</td>
		<td style="width:30px" align="center">15</td>
	</tr>
	<tr class="alt">
		<td style="width:200px" align="center">Ground movement</td>
		<td style="width:30px" align="center">7</td>
	</tr>
	<tr>
		<td style="width:200px" align="center">Hot-tap error</td>
		<td style="width:30px" align="center">5</td>
	</tr>
	<tr class="alt">
		<td style="width:200px" align="center">Others</td>
		<td style="width:30px" align="center">6</td>
	</tr>
</table><p>
</strong></p>
<p>Of the corrosion incidents reported, 79% are caused by external corrosion. Furthermore, 74% of the external corrosion incidents were due to pitting.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=1P3L5NtnqzU:9V-zEFY2cSk:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=1P3L5NtnqzU:9V-zEFY2cSk:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=1P3L5NtnqzU:9V-zEFY2cSk:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/1P3L5NtnqzU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/external-interferencedamage-the-number-1-cause-of-natural-gas-pipeline-incidents/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/external-interferencedamage-the-number-1-cause-of-natural-gas-pipeline-incidents/</feedburner:origLink></item>
		<item>
		<title>Fires and Explosions in Biodiesel and Ethanol Facilities</title>
		<link>http://feedproxy.google.com/~r/RiskAndSafety/~3/PWq5-vfl-mQ/</link>
		<comments>http://risk-safety.com/fires-and-explosions-in-biodiesel-and-ethanol-facilities/#comments</comments>
		<pubDate>Sun, 03 May 2009 20:27:34 +0000</pubDate>
		<dc:creator>Dr. Saraf</dc:creator>
		
		<category><![CDATA[Biofuels]]></category>

		<category><![CDATA[Fires and explosions]]></category>

		<category><![CDATA[alcohol]]></category>

		<category><![CDATA[biodiesel]]></category>

		<category><![CDATA[dust explosion]]></category>

		<category><![CDATA[ethanol]]></category>

		<category><![CDATA[Explosion]]></category>

		<category><![CDATA[Fire]]></category>

		<category><![CDATA[incidents]]></category>

		<guid isPermaLink="false">http://risk-safety.com/fires-and-explosions-in-biodiesel-and-ethanol-facilities/</guid>
		<description><![CDATA[In an earlier post, I talked about safety in biofuel plants. Today, I would like to share couple of Google Maps (Source: John Astad of Combustible Dust Policy Institute) that graphically display incidents in biodiesel and ethanol plants.
Biodiesel Fires and Explosions Map (click to view)

According to the map, there were  8 fires and 6 explosions [...]]]></description>
			<content:encoded><![CDATA[<p>In an <a href="http://risk-safety.com/biofuel-safety-is-it-time-for-bio-psm/" title="Biofuel Safety: Is it time for Bio-PSM?">earlier post</a>, I talked about safety in biofuel plants. Today, I would like to share couple of Google Maps (Source: John Astad of <a href="http://dustexplosions.blogspot.com/" title="Combustible Dust Institute">Combustible Dust Policy Institute</a>) that graphically display incidents in biodiesel and ethanol plants.</p>
<p><a href="http://tinyurl.com/o6kor3" target="_blank" title="Biodiesel Fires and Explosions Map"><strong>Biodiesel Fires and Explosions Map (click to view)<br />
</strong></a></p>
<p>According to the map, there were  8 fires and 6 explosions in biodiesel facilities in the U.S in 3-year period (2006-2009). This translates to approx. 5 incidents per year.</p>
<p><a href="http://tinyurl.com/qndau2" title="Ethanol Fires and Explosions Map" target="_blank"><strong>Ethanol Fires and Explosions Map (click to view)<br />
</strong></a></p>
<p><a href="http://tinyurl.com/qndau2" title="Ethanol Fires and Explosions Map" target="_blank"></a>Based on the map, there were  22 fires and 11 explosions in biodiesel facilities in the U.S. in 10-year period (1998-2009). This translates to approx. 3 incidents per year.</p>
<div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=PWq5-vfl-mQ:oAioZ85sjtQ:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/RiskAndSafety?a=PWq5-vfl-mQ:oAioZ85sjtQ:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/RiskAndSafety?i=PWq5-vfl-mQ:oAioZ85sjtQ:V_sGLiPBpWU" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/RiskAndSafety/~4/PWq5-vfl-mQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://risk-safety.com/fires-and-explosions-in-biodiesel-and-ethanol-facilities/feed/</wfw:commentRss>
		<feedburner:origLink>http://risk-safety.com/fires-and-explosions-in-biodiesel-and-ethanol-facilities/</feedburner:origLink></item>
	</channel>
</rss>
