<?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"?><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:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>OHSAS 18001 EXPERT</title>
	
	<link>http://ohsas18001expert.com</link>
	<description>Operational Health and Safety</description>
	<lastBuildDate>Tue, 20 Apr 2010 18:48:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/OHSAS18001Expert" /><feedburner:info uri="ohsas18001expert" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>OHSAS18001Expert</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Safety Matters?</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/7K0g1SXzQP4/</link>
		<comments>http://ohsas18001expert.com/2010/02/24/safety-matters/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 19:34:54 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHS Metrics & Measurements]]></category>
		<category><![CDATA[OHS performance]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=349</guid>
		<description><![CDATA[A blog on the website The Hill caught my eye this morning.  It is entitled “More than 70 percent of Congressional offices violate OSHA worker safety standards.”  This is an alarming finding. What was even more disturbing is that the blog went on to say that this result – 70% of office areas in violation of OSHA standards [...]]]></description>
			<content:encoded><![CDATA[<p>A blog on the website <a href="http://thehill.com/" target="_blank">The Hill</a> caught my eye this morning.  It is entitled <a href="http://thehill.com/homenews/house/83311-over-70-percent-of-offices-violate-osha-standards" target="_blank">“More than 70 percent of Congressional offices violate OSHA worker safety standards.”</a>  This is an alarming finding.</p>
<p>What was even more disturbing is that the blog went on to say that this result – 70% of office areas in violation of OSHA standards &#8211; was seen as an improvement because the number of violations found during previous inspections was even higher. </p>
<p>Wow!</p>
<p>Having piqued my interest, I headed over to the website for the <a href="http://www.compliance.gov/" target="_blank">Office of Compliance</a> to take a look at the report myself. </p>
<p>What I found was the <a href="http://www.compliance.gov/reports-studies/osha/osha_rpt_june2009.pdf" target="_blank">Biennial Report on Occupational Safety and Health Inspections</a> dated June 2009. </p>
<p>There are some interesting things in this report –</p>
<ul>
<li>Although details about the inspection criteria and protocols used for the Office of Compliance inspections was not provided, the inspections seemed to be heavily focused on the OSHA electrical and fire regulations.  As a result, the primary types of hazards identified appeared to be electrical and fire hazards.</li>
<li>Clearly missing from the report was any discussion of ergonomic hazards associated with office work.  It is difficult to accept that simply because there is no OSHA ergonomics standard, no ergonomics hazards exist in these offices.  The irony being that the reason there is no OSHA ergonomics standard is that Congress blocked OSHA from developing one.</li>
<li>The inspections conducted did NOT include assessment of written safety and health programs – even though this report acknowledges that “agencies can reduce considerably the incident and severity of on-the-job injuries by implementing effective safety programs.”  </li>
</ul>
<p>This is a significant omission given that the most frequently issued OSHA citations are associated with the lack of safety programs such as hazard communication programs. </p>
<p>The reason given for this omission? </p>
<p>The employing offices (i.e. Congressional members) were concerned about the time required to develop safety programs, their lack of readiness for inspection as well as “legal issues.” (see page 19 of the report).</p>
<p>Given the results reported and, more importantly, the omissions from the inspections actually conducted, it makes one wonder about the wisdom of giving awards to members of Congress for “office safety”.  The results to date do not appear to demonstrate a commitment to safety that should be commended.</p>
<h6>© ENLAR® Compliance Services, Inc. (2010)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/7K0g1SXzQP4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/02/24/safety-matters/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2010/02/24/safety-matters/</feedburner:origLink></item>
		<item>
		<title>Olympic Death – Lessons for an OHSMS</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/64k4rywn_PM/</link>
		<comments>http://ohsas18001expert.com/2010/02/18/olympic-death-lessons-for-an-ohsms/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 19:13:18 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[competency]]></category>
		<category><![CDATA[human factors]]></category>
		<category><![CDATA[risk assessment]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=340</guid>
		<description><![CDATA[The death of Georgian luger Nodar Kumaritashvili at the beginning the 2010 Olympic Games was tragic.  Even though most workplaces are clearly not the same as an Olympic sports facility, there are &#8220;lessons to be learned&#8221; from this tragedy for occupational health and safety professionals.   Arguing whether the individual hurt was at fault is not productive.  As the Georgian President Mikheil [...]]]></description>
			<content:encoded><![CDATA[<p>The death of Georgian luger Nodar Kumaritashvili at the beginning the 2010 Olympic Games was tragic. </p>
<p>Even though most workplaces are clearly not the same as an Olympic sports facility, there are &#8220;lessons to be learned&#8221; from this tragedy for occupational health and safety professionals.  </p>
<ul>
<li>Arguing whether the individual hurt was at fault is not productive.  As the Georgian President Mikheil Saakashvili stated &#8211; &#8220;&#8230;no sports mistake is supposed to lead to a death.&#8221;  When individuals die as a result of workplace incidents, the sentiment is the same.  Blaming the worker is just as counterproductive as blaming an athlete.</li>
<li>Consideration of &#8221;human factors&#8221; is both critical to preventing injury and more difficult and complex than it initially seems. </li>
</ul>
<p>What are those complexities?</p>
<p><span id="more-340"></span>First, consideration of human factors must consider each person as an individual.  Unlike machines, humans are not identical.  Each person is unique in size and statue, physical capabilities and emotional responses.  Protecting all workers means protecting each individual.</p>
<p>Second, there is a relationship between the consideration of human factors associated with a task and the development of the competency needed to perform that task.  Much of the disagreement expressed about the luge crash has focused on the skill and experience of Nodar.  The same issue is often a factor in industrial accidents &#8211; inexperienced workers have a higher accident rate.</p>
<p>Finally, our view of what is an acceptable risk evolves over time.  In a recent <a href="http://motorsport.com/news/article.asp?ID=357919&amp;FS=F1" target="_blank">blog post</a> on <a href="http://www.motorsport.com">www.motorsport.com</a>, Max Mosley, the former president of Formula One&#8217;s governing body, is quoted as saying &#8220;The International Luge Federation is where Formula One was 40 years ago &#8211; the whole mindset is wrong.&#8221; </p>
<h6>© ENLAR® Compliance Services, Inc. (2010)</h6>
<p> </p>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/64k4rywn_PM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/02/18/olympic-death-lessons-for-an-ohsms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2010/02/18/olympic-death-lessons-for-an-ohsms/</feedburner:origLink></item>
		<item>
		<title>“HELP – I’m out of RAM”</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/Mi5Zc_tPL7U/</link>
		<comments>http://ohsas18001expert.com/2010/02/12/help-im-out-of-ram/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 21:18:39 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[risk assessment]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=331</guid>
		<description><![CDATA[OHSAS 18001 requires that your organization’s procedure for hazard identification and risk assessment take into account “human behavior, capabilities and other human factors”.  Many organizations partially address this requirement by establishing an ergonomics program in order to address physical human factors.  Only a few organizations explicitly address mental human factors as a part of their [...]]]></description>
			<content:encoded><![CDATA[<p>OHSAS 18001 requires that your organization’s procedure for hazard identification and risk assessment take into account “human behavior, capabilities and other human factors”. </p>
<p>Many organizations partially address this requirement by establishing an ergonomics program in order to address physical human factors.  Only a few organizations explicitly address mental human factors as a part of their hazard identification and risk assessment. </p>
<p>Yet, <em><span style="text-decoration: underline;">mental</span></em> human factors are very real and can be just as important as <em><span style="text-decoration: underline;">physical</span></em> human factors.  In some cases, they are even more important.  For example, when one is driving a car, factors that reduce mental acuity – such as talking on a cell phone – are typically much more significant than physical capabilities.  The dangers of being distracted while driving is important enough that the first Distracted Driving Summit was held last fall and the U.S. Department of Transportation has set up a <a href="http://www.distraction.gov/" target="_blank">Distracted Driving website</a>. </p>
<p>The human brain has been described as having “a very large hard drive but limited random access memory (RAM).”  As demonstrated by our proficiency at trivia games and success in answering questions on quiz shows like Jeopardy, the human brain is capable of storing a great deal of information.  On the other hand, studies show that most people have difficulty remembering more than 7±2 items at a time in <a href="http://en.wikipedia.org/wiki/Short-term_memory" target="_blank">short term memory</a>.  Our mental processes were developed for a very different environment than we find ourselves in today.  In the past, our modes of information delivery moved much, much slower with significantly fewer “inputs per minute.”  </p>
<p>Yet we design work environments as if this mental limitation does not exist. </p>
<p>We expect individuals to work at full capacity in environments with multiple stimuli.  We set up equipment lines so they are efficient for the machines but terrible environments for the people who have to work there.  We design work processes and work shifts as if mental limitations do not exist.</p>
<p>Unfortunately, when accidents do occur – which they inevitably will – we blame the individuals involved and tell them how “bad” they are. </p>
<p>I’m not sure if this is silly, sad or tragic but it sure is NOT a sound management system approach.</p>
<h6>© ENLAR® Compliance Services, Inc. (2010)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/Mi5Zc_tPL7U" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/02/12/help-im-out-of-ram/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2010/02/12/help-im-out-of-ram/</feedburner:origLink></item>
		<item>
		<title>Strategy vs. Implementation – Which is Important?</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/itElSnDFrR0/</link>
		<comments>http://ohsas18001expert.com/2010/01/26/strategy-vs-implementation-which-is-important/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 21:59:54 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[strategic planning]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=327</guid>
		<description><![CDATA[I have been working for over a year with a project team developing a strategy for improving a management system process that is of great importance to that organization.  It was a major effort that culminated in a presentation to the executive management team. They loved it. That should be great – right? Well&#8230; The problem with [...]]]></description>
			<content:encoded><![CDATA[<p>I have been working for over a year with a project team developing a strategy for improving a management system process that is of great importance to that organization.  It was a major effort that culminated in a presentation to the executive management team.</p>
<p>They loved it.</p>
<p>That should be great – right?</p>
<p>Well&#8230; The problem with an “approved strategy” is that now someone has to implement it.</p>
<p>This is a common issue that arises when an organization establishes an occupational safety and health management system.  The company tasks a team that sets up the framework for the OHSMS, someone writes up the procedures to match the conceptual framework and objectives are established for the various improvement initiatives that have been envisioned.</p>
<p>Then comes implementation &#8211; “doing what you say you are going to do.”  This is often the hard part.</p>
<p>For success – you need BOTH strategy and implementation.  </p>
<ul>
<li>If you have strategy without implementation, you may have great plans but the organization will get no benefits from the strategic planning (the “dusty manuals” syndrome).</li>
<li>If you have implementation without strategy, you will have action but are likely to miss the mark and end up doing the wrong things well (the “ready, fire, aim” syndrome).</li>
</ul>
<p>For a good discussion of the important of getting it right and doing it right – check out the following blog post – <a href="http://blog.smartdraw.com/archive/2009/09/22/strategy-is-execution-don-t-shoot-yourself-in-the-foot.aspx " target="_blank">Strategy IS Execution.</a></p>
<h6>© ENLAR® Compliance Services, Inc. (2010)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/itElSnDFrR0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/01/26/strategy-vs-implementation-which-is-important/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2010/01/26/strategy-vs-implementation-which-is-important/</feedburner:origLink></item>
		<item>
		<title>Lessons from Haiti</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/yZE2APTQ7TI/</link>
		<comments>http://ohsas18001expert.com/2010/01/22/lessons-from-haiti/#comments</comments>
		<pubDate>Fri, 22 Jan 2010 20:26:00 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[Emergency Preparedness]]></category>
		<category><![CDATA[disaster preparedness]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=323</guid>
		<description><![CDATA[The on-going crisis in Haiti is a stark reminder of the importance of disaster preparedness.  Both OHSAS 18001 and ISO 14001 require that an organization establish, implement and maintain procedures to &#8221;identify the potential for emergency situations&#8221; in order to be ready and prepared to respond to these situations when they arise (section 4.4.7). I have been working [...]]]></description>
			<content:encoded><![CDATA[<p>The on-going crisis in Haiti is a stark reminder of the importance of disaster preparedness.  Both OHSAS 18001 and ISO 14001 require that an organization establish, implement and maintain procedures to &#8221;identify the potential for emergency situations&#8221; in order to be ready and prepared to respond to these situations when they arise (section 4.4.7).</p>
<p>I have been working for several years with the <a href="http://www.tbrpc.org/tampabaydisaster/" target="_blank">Tampa Bay Regional Planning Council </a>to help local businesses prepare for disasters.  In our area, the Florida west coast, the disaster we fear is a major hurricane.  As part of these efforts, we developed and presented a series of interactive workshops covering emergency planning, risk assessment and disaster preparedness. </p>
<p>If you want to be prepared, the following points are key -<span id="more-323"></span></p>
<ul>
<li><strong>Prioritization of Efforts</strong> &#8211; It is impossible to address every need at the same time.  Before a disaster strikes, you need to define your risks and establish what your recovery priorities are going to be and then, when disaster strikes, act accordingly.</li>
<li><strong>Clearly Defined Roles and Responsibilities</strong> &#8211; To repurpose an adage from cooking (i.e. &#8220;Too many cooks spoil the pudding.&#8221;) &#8211; too many bosses creates chaos.  Someone must be in charge and that has to be clear to everyone.</li>
<li><strong>Communication is Key</strong> &#8211; Without clear communication, you are likely to have incomplete response actions, wasted duplication of efforts and run the risk of festering anger, outrage and violence in those who are impacted by the disaster event.</li>
<li><strong>Protecting Your Responders</strong> - Heroics look good for TV but should be discouraged. Having responders taking unnecessary risks adds to the ultimate &#8220;body count&#8221; of those impacted by the disaster.</li>
</ul>
<p>If you haven&#8217;t reviewed your emergency preparedness plans yet this year, pull them out and review them now.  While you are at it, update those emergency contact lists, chances are they are out of date.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
<p> </p>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/yZE2APTQ7TI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/01/22/lessons-from-haiti/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2010/01/22/lessons-from-haiti/</feedburner:origLink></item>
		<item>
		<title>Out with the Old – In with the New</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/3CBDc9Fj8CA/</link>
		<comments>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 15:07:03 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[record control]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=317</guid>
		<description><![CDATA[The start of the New Year is good time to pause, reflect and clean out. Many organizations use the start of the year as a time to review their OH&#38;S management system objectives and set new ones.  If their OH&#38;S programs are lagging in their implementation, new approaches or new assignments are considered.  This is [...]]]></description>
			<content:encoded><![CDATA[<p>The start of the New Year is good time to pause, reflect and clean out.</p>
<p>Many organizations use the start of the year as a time to review their OH&amp;S management system objectives and set new ones.  If their OH&amp;S programs are lagging in their implementation, new approaches or new assignments are considered. </p>
<p>This is also a good time to address all that PAPER – either physical paper or electronic paper.  This includes all those completed hazard evaluation forms, inspection checklists, excel spreadsheets, meeting notices and minutes, e-mails with various interested parties, incident investigations, corrective action reports,….</p>
<p>When I help develop record control processes and procedures for an organization, one of the concepts I try to incorporate is the inclusion of record schedules with record breaks and scheduled clean-out days. <span id="more-317"></span></p>
<p>A record schedule is a document that defines how a record is to be kept, how long it needs to be maintained in an active storage location and when it should be destroyed.  <a href="http://www.epa.gov/records/faqs/schedules.htm" target="_self">U.S. EPA has an informative discussion of the purpose and use of record schedules on its web site. </a></p>
<p>The first key to using a record schedule is organizing your records in a way that makes complying with your record retention requirements as easy as possible.  This usually means using record breaks – usually defined points in time when you start a new file. For example, rather than filing all of your records pertaining to a particular topic randomly in one file folder (physical or electronic), you file them by year so you can move an entire year’s worth of records to a different location (off-site storage or electronic archive) at one time. </p>
<p>The second key to using a record schedule is actually setting aside a time for moving old records out of active storage locations and getting rid of unnecessary records in accordance with your organization’s record retention policies. </p>
<p>Although this often appears to be an unimportant mundane task to “put off to another day” it is important to the smooth functioning of your OHSMS. </p>
<p>So, schedule your record clean-out day today.  By the way, wear comfortable clothes and order a pizza.  It will make the job easier.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/3CBDc9Fj8CA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/</feedburner:origLink></item>
		<item>
		<title>Ban the Blame</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/S5p0xkLwru0/</link>
		<comments>http://ohsas18001expert.com/2009/12/15/ban-the-blame/#comments</comments>
		<pubDate>Tue, 15 Dec 2009 13:29:20 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[corrective action]]></category>
		<category><![CDATA[incident investigation]]></category>
		<category><![CDATA[preventive action]]></category>
		<category><![CDATA[root causes]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=314</guid>
		<description><![CDATA[One of the key requirements of the OHSAS 18001 standard is establishing a procedure for taking corrective and preventive action (section 4.5.3.2).  Both corrective and preventive action need to include identifying the underlying causes – often called root causes – of whatever it is that is or went wrong.  This is not easy.  Often, the [...]]]></description>
			<content:encoded><![CDATA[<p>One of the key requirements of the OHSAS 18001 standard is establishing a procedure for taking corrective and preventive action (section 4.5.3.2).  Both corrective and preventive action need to include identifying the underlying causes – often called root causes – of whatever it is that is or went wrong. </p>
<p>This is not easy.  Often, the root cause investigation ends with a determination along the lines of “Joe screwed up.”  We play the blame game.</p>
<p>Why?</p>
<p><span id="more-314"></span>There have been a number of reasons advanced for this and most of them are probably true – at least in part.</p>
<p>Last week, a colleague lent me his copy of Dan Gano’s book – <a href="http://www.amazon.com/Apollo-Root-Cause-Analysis-Thinking/dp/1883677114/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1260882984&amp;sr=1-1" target="_blank">Apollo Root Cause Analysis.</a>  This book sets out a different way of approaching root cause analysis by focusing on defining a problem in terms of both the action and the conditions that caused the particular effect you are analyzing.  For example, you don’t get a fire (an effect) unless you have an ignition source (an action) as well as two conditions (fuel and oxygen at the right concentrations).  Remove either condition (fuel/oxygen) or the action (ignition) and the effect (fire) does not occur.</p>
<p>What I liked most about the book, however, was not the root cause methodology advanced in the book but the explanation of why we so often fall into the blame game.</p>
<p>In a word &#8211; storytelling.</p>
<p>As humans, we have a long tradition of storytelling.  It comes naturally to us.  It is how we have transmitted information for generations.  Everyone likes a good story.</p>
<p>Integral to storytelling is identifying your actors – answering the question “who” is central to telling a good story.  As Gano points out in his book, most incident reports provide a prime example of storytelling.  The initial focus is typically on who did what.  Unfortunately, for purposes of root cause analysis, storytelling sets us up for failure because it keeps us focused on the story &#8211; who, what, where and when &#8211; rather than focusing our attention on identifying the causes of an incident. </p>
<p>So when you are investigating an incident or nonconformity, tell your story.  It is, after all, human nature and likely irresistible.  But when you start your root cause analysis, put the story aside and take the “who” completely out of the analysis.  Remove the names and strike the identifiers.  Instead, focus your attention on the actions and conditions that lead to the situation (effect) that you are investigating.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/S5p0xkLwru0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/12/15/ban-the-blame/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2009/12/15/ban-the-blame/</feedburner:origLink></item>
		<item>
		<title>OHSAS 18001 “Governing Body”</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/DMfzQ54gkvk/</link>
		<comments>http://ohsas18001expert.com/2009/11/24/ohsas-18001-governing-body/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 12:48:48 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[Standards & Certification]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=309</guid>
		<description><![CDATA[A reader recently posted the following question – I am dealing with an organization that claims it is certified to OHSAS 18001… Does anyone know if there is an accreditation board or other governing body which administrates OHSAS 18001 who would be responsible for auditing conformance with these practices? Or does this system rely solely [...]]]></description>
			<content:encoded><![CDATA[<p>A reader recently posted the following question –</p>
<p><em>I am dealing with an organization that claims it is certified to OHSAS 18001… Does anyone know if there is an accreditation board or other governing body which administrates OHSAS 18001 who would be responsible for auditing conformance with these practices? Or does this system rely solely on internal audits only? (<a href="http://ohsas18001expert.com/2009/11/13/trust-but-verify/" target="_self">click here to read the entire comment</a>)</em></p>
<p>There is no one OHSAS 18001 governing body or accreditation board.</p>
<p>As a voluntary international standard, OHSAS 18001 is utilized by organizations in several different ways.<span id="more-309"></span></p>
<p>Some companies use OSHAS 18001 as a guidance document to develop their OH&amp;S management system.  In that case, conformance is discretionary and there is no “certification” or “accreditation”.  In this case, verification of conformance relies solely upon the adequacy and effectiveness of the internal audit program.</p>
<p>OHSAS 18001 is also used for purposes of third-party certification. </p>
<p>Many of the registrars who provide ISO 9001 and ISO 14001 certification also offer OHSAS 18001 certification to their customers.  Because of how OHSAS 18001 was developed (independent of ISO), there are two types of certification being offered by registrars – accredited and unaccredited.   The majority of OHSAS 18001 certifications are unaccredited.</p>
<p>In order to determine the type of certification an organization has, you will need to carefully review the actual certificate.  This can be easier said than done.  Since there is no public access to registration certificates, or any master database of OHSAS 18001 certified companies, you have to get a copy of the certificate from the company that is claiming to be OHSAS 18001 certified.  It is often posted on the wall somewhere.</p>
<p>You would also want to confirm the validity of this certification with the registrar identified on the certificate.  There have been problems with “sham” or fake certificates.  The certificate should also indicate whether or not it is an “accredited” certification and the scope of the certification (what it covers).  In some cases, the actual scope of the certification is narrower than the public relations representations made by the company (certain operations, locations or workers are excluded).</p>
<p>For either accredited or unaccredited certification, the registrar who issued the certificate to the company does periodic audits to determine whether or not the organization has a management system in place that conforms to OSHAS 18001.  Typically, these audits are done either once or twice a year. </p>
<p>If it is an accredited certification, the registrar’s overall certification program is also periodically reviewed by an independent accreditation body.  This review would<span style="text-decoration: underline;"> not</span> include an in-depth review of each of the certificates issued by the registrar.  The focus of accreditation is primarily on the processes used – not the results achieved.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/DMfzQ54gkvk" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/11/24/ohsas-18001-governing-body/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2009/11/24/ohsas-18001-governing-body/</feedburner:origLink></item>
		<item>
		<title>“Timely” Incident Investigation</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/ACtJ_Q0sQOU/</link>
		<comments>http://ohsas18001expert.com/2009/11/18/timely-incident-investigation/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 17:52:09 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=290</guid>
		<description><![CDATA[Section 4.5.3.1 of OHSAS 18001 requires that OH&#38;S incident investigations “be performed in a timely manner”. So &#8211; What is Timely? Neither OHSAS 18002 nor the dictionary (my primary sources for interpreting the OHSAS 18001 requirements) provides much help.  OHSAS 18002 does not explicitly discuss this particular requirement of the OHSAS 18001 standard. The dictionary [...]]]></description>
			<content:encoded><![CDATA[<p>Section 4.5.3.1 of OHSAS 18001 requires that OH&amp;S incident investigations “be performed in a timely manner”.</p>
<p><em><strong>So &#8211; What is Timely?</strong></em></p>
<p>Neither OHSAS 18002 nor the dictionary (my primary sources for interpreting the OHSAS 18001 requirements) provides much help. </p>
<p>OHSAS 18002 does not explicitly discuss this particular requirement of the OHSAS 18001 standard.</p>
<p>The dictionary isn’t particularly helpful either. It defines timely as – “well-timed, in time, occurring at a suitable time, opportunely“. The legal dictionary definition is “falling within a prescribed or reasonable time.”<span id="more-290"></span></p>
<p>As a practical matter, there are several components to a “timely” incident investigation –</p>
<ul>
<li> “The CSI Factor” – As in the TV show CSI, you will want to do your immediate investigation of an incident (who, what, when and where) while the facts are fresh – before memories fade and “the evidence” disappears.</li>
<li>Dealing with Imminent Risks – Hazards that are imminent risks (e.g. defective ladders, broken guards on operating equipment) need to be addressed immediately.</li>
<li>Preventing Future Injuries – Since the primary purpose of incident investigation is prevention of injuries, the root causes of an incident (why and how) need to be determined and addressed before another similar incident occurs.</li>
</ul>
<p>An investigation does not need to be completed all at once in order to be timely.</p>
<p>An incident investigation is often done in two stages:</p>
<ol>
<li>Initial information collection – preserving the evidence</li>
<li>Root cause analysis – determining what the evidence means</li>
</ol>
<p>The initial of collection of information about the incident usually needs to be done quickly. The root cause analysis typically takes more time.</p>
<p>So what do you think? Let me know by completing the survey below or posting a comment.<br />
<!-- Altering or removing this link is a breach of the Vizu Terms and Conditions -->
<div style="font-family:Arial, Helvetica, sans-serif; font-size:9px;height:20px;text-align:center;width:320px;margin:0;padding:0;letter-spacing:-.5px"><a href="http://www.vizu.com" target="_blank"><span style="color:#999;text-decoration:underline;font-size:9px;">Online Surveys</span></a><span style="color:#999;">&nbsp;&amp;&nbsp;</span><a href="http://answers.vizu.com/market-research.htm" target="_blank"><span style="color:#999;text-decoration:underline;font-size:9px;">Market Research</span></a></div>
<p><embed src="http://wp.vizu.com/vizu_poll.swf" quality="high" scale="noscale" wmode="transparent" bgcolor="#ffffff" width="320" height="432" name="vizu_poll" align="middle" allowScriptAccess="always" type="application/x-shockwave-flash" FlashVars="js=false&#038;pid=189829&#038;ad=false&#038;vizu=true&#038;links=true&#038;mainBG=eeeeee&#038;questionText=000000&#038;answerZoneBG=EEEEEE&#038;answerItemBG=cc9966&#038;answerText=000000&#038;voteBG=C8C8C8&#038;voteText=000000"></embed> </p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/ACtJ_Q0sQOU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/11/18/timely-incident-investigation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2009/11/18/timely-incident-investigation/</feedburner:origLink></item>
		<item>
		<title>Trust – but Verify</title>
		<link>http://feedproxy.google.com/~r/OHSAS18001Expert/~3/luhm_y0eXLc/</link>
		<comments>http://ohsas18001expert.com/2009/11/13/trust-but-verify/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 13:31:57 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Auditing]]></category>
		<category><![CDATA[auditing]]></category>
		<category><![CDATA[trust]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=233</guid>
		<description><![CDATA[In previous posts, I discussed the relative importance of management system standards and company culture on OH&#38;S performance.  This discussion was based on the paper entitled The Limits of Management Based Regulation by Neil Gunningham and Darren Sinclair.  One of the conclusions set out in this paper is that the “accountability mechanisms” common to management [...]]]></description>
			<content:encoded><![CDATA[<p>In previous posts, I discussed the relative importance of management system standards and company culture on OH&amp;S performance.  This discussion was based on the paper entitled The <em>Limits of Management Based Regulation</em> by Neil Gunningham and Darren Sinclair.</p>
<p> One of the conclusions set out in this paper is that the “accountability mechanisms” common to management system standards can have a negative impact on OH&amp;S performance.</p>
<p>The authors suggest that many of the fundamental requirements of management system standards – establishing accountability, performance tracking and internal auditing – are “antithetical to measures that our findings suggested had a positive impact on OHS.”  They go on to discuss social science research that finds that accountability mechanisms can decrease trust and, as a result, negatively impact performance. </p>
<p><strong>What does this mean for OHSMS internal audit programs?</strong></p>
<p> First, it is important to recognize that internal audit programs have a purpose.  That purpose is best summed up by the phrase &#8211; “Trust – but Verify.” That is why OHSAS 18001 includes an internal audit program requirement.</p>
<p><span id="more-233"></span> As Steve Covey states in his book - <em>Nothing is as Fast as the Speed of Trust</em> there is a difference between Judgment – what he calls “Smart Trust” and Gullibility.  Extending trust can bring great dividends; however, it can also create significant risks.  The goal is to find the appropriate balance of trust and scrutiny to manage risk appropriately while avoiding both gullibility and excessive suspicion.</p>
<p> With that in mind, let’s examine the goal of an internal management system audit. </p>
<p> In an effective OH&amp;S management system, the goal of your audits should be to find evidence of conformance – to verify that processes are being done right.  This means that the focus should be on documenting conformance NOT on finding nonconformities. </p>
<p>It is human to resent being audited – very few people like having their work questioned.  Simply shifting the focus of the audit process away from a negative intent (finding problems) to positive (celebrate what you are doing right) will go a long way to improving the process and increasing trust.  So will treating the identification of any nonconformities as opportunities for improvement rather than occasions to assign blame.</p>
<p>Recognize the negative impact audits can have on “trust” and take steps to mitigate them.</p>
<p>Avoid using internal audits as “buck passing” or “institutional feel good” exercises. Make sure that top management is as invested in providing the resources needed to fix problems as they are in identifying them in the first place.  Here&#8217;s a thought &#8211; perhaps you can put a positive spin on your audit program by having a set amount of “safety bonus” dollars that are <span style="text-decoration: underline;">immediately</span> available to fund one or more &#8220;opportunities for improvement&#8221; identified during the audit.  Every safety program has potential improvements that aren&#8217;t being pursued becaue of lack of funding.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
<img src="http://feeds.feedburner.com/~r/OHSAS18001Expert/~4/luhm_y0eXLc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/11/13/trust-but-verify/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://ohsas18001expert.com/2009/11/13/trust-but-verify/</feedburner:origLink></item>
	</channel>
</rss>
