Paying the price for forgetting rule #1
Feb. 4th, 2010 06:55 pmRule #1 of course being "users lie".
I'm installing a printer in the Endoscopy Dept. at the local hospital, and having a hard time finding the right port. Most of the rooms aren't signposted, and the ones that are marked aren't numbered in any logical order, so I stick my head through a door that doesn't have any medical equipment inside and ask for directions.
"I know exactly where that's going!" bellows the helpful user joyfully. "$BOSS_LADY told me to expect you!"
She shows me to the room, making small talk the whole way, and I switch out the old printer for the shiny new one I brought with me. Get in my van and drive back to base where the old printer goes on a pallet. Hospital policy says *all* equipment removed from site gets junked, not just drives.
The following day I come in and find the hospital has been leaving messages for me since the wee hours — they've been having trouble printing, which is weird because I tested the printer before leaving and it didn't have any trouble.
This is where rule #1 comes into it. I hustle back over there and find that the helpful user who showed me where I was going decided on the spot that was *her* printer I was carrying, and got me to replace the one she'd been using, which was supposed to remain in the environment for another two years. Now they have two devices with the same IP on the network, and when the nurses turn on the second one (which is only used during procedures so doctors can print colour photos of a patient's intestinal tract) there's a conflict. Serves me right for not checking the port number and asset sticker against my work order?
I call the dispatcher to have him pull the old device off the pallet in the yard and see if it's still good to go. He pours three inches of water out of it and tells me probably not.
$MY_BOSS talks to $THEIR_BOSS about it, and the result of the discussions is that the Queen of Lies gets to keep her nice new printer, the doctors make do with the old one for the rest of the replacement cycle, and I have to go back to the Endoscopy room to correct the IPs. While it's in use.
Happy days, gritted teeth, *so* nice to see you again.
And the whole time I was working (testing that PC after PC after PC could print to the right machine because the users were nervous) there was a guy face down on an operating table ten feet away getting a camera shoved up his ass.
I'm installing a printer in the Endoscopy Dept. at the local hospital, and having a hard time finding the right port. Most of the rooms aren't signposted, and the ones that are marked aren't numbered in any logical order, so I stick my head through a door that doesn't have any medical equipment inside and ask for directions.
"I know exactly where that's going!" bellows the helpful user joyfully. "$BOSS_LADY told me to expect you!"
She shows me to the room, making small talk the whole way, and I switch out the old printer for the shiny new one I brought with me. Get in my van and drive back to base where the old printer goes on a pallet. Hospital policy says *all* equipment removed from site gets junked, not just drives.
The following day I come in and find the hospital has been leaving messages for me since the wee hours — they've been having trouble printing, which is weird because I tested the printer before leaving and it didn't have any trouble.
This is where rule #1 comes into it. I hustle back over there and find that the helpful user who showed me where I was going decided on the spot that was *her* printer I was carrying, and got me to replace the one she'd been using, which was supposed to remain in the environment for another two years. Now they have two devices with the same IP on the network, and when the nurses turn on the second one (which is only used during procedures so doctors can print colour photos of a patient's intestinal tract) there's a conflict. Serves me right for not checking the port number and asset sticker against my work order?
I call the dispatcher to have him pull the old device off the pallet in the yard and see if it's still good to go. He pours three inches of water out of it and tells me probably not.
$MY_BOSS talks to $THEIR_BOSS about it, and the result of the discussions is that the Queen of Lies gets to keep her nice new printer, the doctors make do with the old one for the rest of the replacement cycle, and I have to go back to the Endoscopy room to correct the IPs. While it's in use.
Happy days, gritted teeth, *so* nice to see you again.
And the whole time I was working (testing that PC after PC after PC could print to the right machine because the users were nervous) there was a guy face down on an operating table ten feet away getting a camera shoved up his ass.
no subject
Date: 2010-02-04 06:08 am (UTC)Well, it wasn't really that bad, I guess...at least they were sedated and not trying to chat or whatnot while I was in there. Talk about awkward...
no subject
Date: 2010-02-04 06:34 am (UTC)(At least you weren't trying to give birth while the window-washers were looking in...)
no subject
Date: 2010-02-04 07:35 am (UTC)no subject
Date: 2010-02-04 01:44 pm (UTC)no subject
Date: 2010-02-04 02:37 pm (UTC)no subject
Date: 2010-02-05 04:57 am (UTC)no subject
Date: 2010-02-05 06:48 pm (UTC)no subject
Date: 2010-02-05 07:11 am (UTC)no subject
Date: 2010-02-04 01:29 pm (UTC)no subject
Date: 2010-02-04 03:54 pm (UTC)no subject
Date: 2010-02-05 05:03 am (UTC)no subject
Date: 2010-02-05 07:09 am (UTC)Sometimes, consequences can come from all kinds of sources... *clickky*
no subject
Date: 2010-02-04 02:37 pm (UTC)--H
no subject
Date: 2010-02-04 08:34 pm (UTC)I don't let them sedate me, and I get violent when my privacy's invaded.
no subject
Date: 2010-02-06 08:53 am (UTC)