Feb 24th

I won’t be a law breaker soon!

By Lynda Peggs
  1. It seems that the Government intend to raise the speed limit on motorways to 80mph in 2013. Their rationale is what you’d expect: the current limit has been untouched for years and vehicle safety has improved dramatically in that time and driving on motorways is ‘safer’ than on other roads.
    But in an interview with The Times, Philip Hammond (the Transport Secretary) said that he believes we operate in a ‘democracy of policing by consent’. He reckons that if 50% of the population are breaking the law then it’s the law that needs looking at and not necessarily the law-breakers. He’s probably got a point because few people stick to 70 or below on a motorway in my experience.
    Predictably road safety campaigns are up in arms about it, but there again they won’t be happy until we’re all pedestrians in any case. I have to say that I’m with you Phil! You’re a refreshing change! Stupid rules, or rules that are perceived to be stupid, just don’t get followed and frankly we (as a country) don’t enforce this particular law very well anyway do we? So why have it?
    Phil’s argument got me thinking too. You see at the moment one of my key strategic priorities at work is to do with getting people to work safely because they want to and not because they think if they don’t they’ll get told off by the boss.
    Although we’ve been making progress on this (which is just as well as part of my bonus is riding on it!), I wonder now whether we’ve been coming at it from the wrong angle. Maybe the biggest lever for change is really in understanding what safety rules and processes need to be changed.
    Arguably if people choose not to the follow some rules and there hasn’t been an accident surely the rule is a waste of time. I mean, if the rule was to wear eye protection when doing X, and people don’t wear the protection when they should you’d expect there to be more incidents involving stuff getting into peoples eyes when they do it, right?
    If the rule is really important, why hasn’t it been enforced harder either by the line manager or organisationally? After all, organisations don’t make up rules for the sake of it, most consider them very carefully. So if it’s that important it should be enforced.
    Just like if the 70mph speed limit on a motorway is that important there should be more tickets given out but there isn’t. Why? Because the police are too busy dealing with other more serious issues like murder, scum mugging old ladies and drug dealers.
    To help me get my bonus (I have a new drive to pay for) we’ve set up some focus groups with front line employees to talk about some of these things (not mugging and drug dealing, I mean safety rules!), and hopefully we’ll come up with some stuff that we can ‘police by consent’. In other words the rules we’re left with are the really important ones rather than what we might have now: really important ones and a whole heap of other non-important stuff that we get upset about when people don’t follow them! And of course, fewer rules the more chance you’ve got of people remembering them.
    So my challenge to anyone reading this blog is to have a think of things from a different perspective: are you too worried about getting people to conform to a rule when what you should be wondering is, is that the right rule is in place? Only when, you’ve confirmed that it is, should you try to change people’s behaviours.
    Now I’ve got my head round that, I just need to work out if Phil is Conservative or a Liberal Democrat – after all I don’t want to give credit to the wrong party do I, you only get one vote!
    Ah, thank the Lord for Google, he’s a blue!
Sep 28th

Managing HSE Data

By Steve Krile
I have been designing systems to manage incident information for 10 years now (you may have noticed those ads for CoreHSE.com - yeah, that's me!), and if there is one lesson I have learned, it is this: make sure you know what you know. Often times, when we are dealing with the very real and raw emotions of an accident our perceptions about what really happened becomes somewhat clouded. We are focused on getting the best possible treatment for our friend and co-worker, securing the area, making sure no one else gets hurt, and all the other immediate response activities that come as second nature to most of us.

However, if we are ever going to truly prevent this from happening again we need to do a proper and thorough investigation. And for most of us, this comes as second-nature as well. But, let me pull the camera back a bit, and let’s look at the landscape from a little further out. What if we want to optimize our analysis of critical incident management? What if we want to know the most dangerous machine in our building? What if a product engineer asks us, “What is the history of injuries for this part we manufacture?”
What if we want to know the 5-year trend of upper extremity burns across our 20 oil platforms?

 

There is only one way to really know what you know and that is through codes. You should code as much as you can to enhance your incident management. There are many things we could code about an incident – injury type, body part, body location, lost time, medical treatment, machine, location, and on and on. However I suggest there is one code more important than all of those other items. This code will determine whether you “count” this incident. This code will set a precedent for long-term trend analysis. This code was the basis for our HS&E Management system we started 10 years ago. That code is : Most Serious Result.

The problem we were trying to solve was being able to compare the injury rates from  plant in Kentucky, USA to the rates from a plant in Plymouth, England. With such vastly different governments mandating completely different standards for injury reporting, it was not possible to harmonize the two systems based on government requirements. And that’s just those two countries. What about France, Germany, the Czech Republic, India, and the rest of our operations all over the world? How were we supposed to get everyone reporting similar critical incidents in a similar (or to be more precise – exact) manner? 

What we developed was a coding system for result that would be applied across all of our operations regardless of jurisdiction or government. It would be *our* reporting standard. This standard became the corner-stone for our corporate Incident Management system. No longer were we forced to parse the local laws of Wuhu, China to decide if an injury was reportable to the Chinese government and therefore should be counted.  

In the next article I will show you the codes we came up with and some of the challenges we had implementing this coding system.

Jul 15th

Protect Your Workers from Heat Related Illness and Death.

By Trey Greene
The summer temperature is rising by the day and so are the rates of heat-induced illness and death. The first report of heat-induced illness took place in Memphis, TN on June 24, 2009, but deaths have been occurring all season and are sure to continue. These incidents remind us to provide employees with the proper training to ensure their safety when working in these conditions.

“Working in extreme temperatures is not only uncomfortable, it can be life-threatening,” said acting Assistant Secretary of Labor for OSHA Jordan Barab. “It is important for workers and their employers to minimize the chances of heat-induced illnesses, and imperative that they recognize the signs of heat stress and take the proper precautions to reduce the chances of illness or death.”

Many employers who spend the majority of their time indoors tend to lose sight of the risks that dramatic weather conditions can have on their outdoor workers. By simply taking the time to administer safety training on this issue can save everyone involved from getting burned.

“This heat is taking a toll on everyone, but especially to those who have to work in it day in and day out. We wanted to help these employees stay safe by creating a SafetySkills™ Heat Stress course that tackles this issue and what preventative measures should be taken,” said Trey Greene, CEO of noodleStream.com.
Jun 9th

Lessons Learned

By Kevin Site Owner
With the site coming along at such a great rate I think we now have enough members to add a Lessons Learned section to the site.  If all HSE People would like to send me any lessons Learned from Incidents / Accidents throughout the month I will put together a collation of the month's lessons learned and post it to the publications page at the end of each month.

Lessons learned can be in any common format and should be no more than 2 pages and preferably include some pictures of the Incident / Accident

Please send all contributions to kevin@oilandgaspeople.com cc forbez@gmail.com