• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Being asked to deactivate a fire suppression system - yikes"

Collapse

  • unixman
    replied
    Interesting from these replies that it does happen now and again, and my experience was not unique (unless we all worked at the same place!).

    On the subject of insurance, if the client lost the DC to fire, they would presumably make an insurance claim. However, it is hard to imagine even their weighty policy paying out one it becomes known that the fire suppression system was disabled. I hope the client realizes that.

    Leave a comment:


  • unixman
    replied
    Originally posted by vwdan View Post
    ...As a contractor I really wouldn't want to be touching those buttons, to be honest.
    Exactly my feelings on the matter.

    Leave a comment:


  • gables
    replied
    Originally posted by vwdan View Post
    I have a vague memory of doing this back in ~2006, but certainly not recently. As a contractor I really wouldn't want to be touching those buttons, to be honest.
    Indeed, I was a permie when I last did this.

    Leave a comment:


  • vwdan
    replied
    I have a vague memory of doing this back in ~2006, but certainly not recently. As a contractor I really wouldn't want to be touching those buttons, to be honest.

    Leave a comment:


  • gables
    replied
    Yep, where I worked (2008-2014) we disabled the fire suppression system which was Halon, didn't want to be gassed.

    Leave a comment:


  • Lance
    replied
    a couple of years ago. yes.
    It was a brand new DC. I'm not really that interested in that side of data centres so just did what was asked.

    Althoguh I did point out that they needed someone to do double check it had been re-armed as people kept forgetting.

    Leave a comment:


  • DaveB
    replied
    It's possibly historic. If they had a Co2 or Halon system in place then this would be good practice. If it's been replaced by a foam or water based system, as many have nowadays, then it may be that the SOP's for the data center weren't updated at the same time, hence still disabling the fire system when the room is occupied.

    Leave a comment:


  • dx4100
    replied
    Yes years ago during my early days...

    As a contractor I would want the practice in writing and that the client accepted all associated risks. I would imagine my PII would expect me to have mitigated their exposure.

    Leave a comment:


  • unixman
    replied
    Originally posted by CheeseSlice View Post
    Yes, during a permie job when I was a lot younger.
    Thought it was a bit odd, but figured it must be OK since my older colleague showed me how
    I guess if you are permy, you are on slightly safer ground, insurance wise.

    Leave a comment:


  • CheeseSlice
    replied
    Yes, during a permie job when I was a lot younger.
    Thought it was a bit odd, but figured it must be OK since my older colleague showed me how

    Looking at it another way, it was a choice... Either deactivate it and risk a fire spreading,... or risk being gassed to death by Halon.
    With literally no other human beings about, I preferred not being gassed. If the whole server room went up in flames I could probably make it out first and wait for the fire brigade to arrive

    Leave a comment:


  • malvolio
    replied
    Nor me, but ive been in a datacentre when the Halon was triggered by a sensor fault. Its not an experience i would want to repeat.

    Its also why i prefer water rather than gas to put fires out. It doesnt risk killing people.

    Leave a comment:


  • Old Greg
    replied
    I've never been asked to.

    Leave a comment:


  • Being asked to deactivate a fire suppression system - yikes

    Howdy,

    Summary: have you ever been asked to de-activate the fire suppression system in a client data centre ?

    Long version:
    This is for anyone whose role takes them into client data centres. Systems administrators (like me) and perhaps hardware people.

    Over the years, I have regularly worked in physical data centres. For example when building servers, doing small hardware changes or escorting third party engineers. Sometimes, entering a data centre involves extra security procedures, such as entering a PIN or similar. All very reasonable. However, a recent client expected me to do something else, in addition. That is: to disable the fire suppression system before entering the DC, and to re-enable it after leaving. The staff showed me how to do it, and it was a routine procedure for them. (By "fire suppression system", I mean the in-built sprinklers or gas flood system that actually puts out the fire).

    How odd. I cannot guess why staff were deactivating the fire protection. It isn't something I have come across before, and isn't a widespread practice, according to Google. I think their motivation was personal safety but when I asked, nobody could explain why they were doing it, including staff engineers, my manager and even the manager in charge of the data centre.

    It seems to carry several serious risks, not least being that if you forget to re-enable it, and the DC later burned down, your insurer is unlikely to pay out after they learn that you de-activated the sprinklers. Even if they did pay, a £10 million policy from QDOS (like mine) is not going to cover the cost of a whole DC. I politely told the client that, for these and other reasons, I would not be deactivating their fire suppression system.

    I'm not looking to start a discussion on flood/sprinkler systems. I know they come in many forms, and can be dangerous for humans. I'm just asking if you have come across this practice ? And if so, did you consider the risks?

Working...
X