On Call A warning from the past in today’s On Call. Helpfulness is not always rewarded with a pat on the back and a slap-up meal on expenses. Sometimes the Somebody Else’s Problem field* is best left alone.
Our tale comes from a reader Regomised as Derek and concerns his time working for a multinational with plants at multiple locations in the UK. He was part of the application support team and toiled under a 24/7 call-out arrangement. A cry for help had to be answered within the hour.
One of the plants would start production at 0400 on Monday mornings, but started work four hours earlier to make sure things were up to speed. It had two main buildings. One was an office unit, housing the comms and server rooms. The other had an equipment room, with switches and patch panels as well as an operations room with client PCs and expensively large monitors.
The two buildings were connected by a fibre-optic cable that ran in a culvert beneath the yard, through which large trucks (Derek told us they could weigh as much as 38 tonnes) would rumble.
“The plant required the applications to be running,” Derek told us. “No manual overrides so no system = no production.
You can probably see where this is going.
Sure enough, at 0130 one Monday morning the call came in. Nothing was working.
“I reluctantly dragged myself from my warm bed to drive the 10 miles to the plant,” recalled Derek, “to be greeted by the sombre production team.”
It wasn’t looking good. All the screens were showing “connection error” messages and a simple ping test showed that the network between the two buildings was down. Derek’s heart sank as he pondered the cause. The culvert running under the yard – the one over which those heavy trucks passed over and over again – had probably been stoved in, severing the connection.
Worse, for reasons known only to management, the infrastructure team responsible didn’t provide out-of-hours support. Sure – the applications team was always on the end of the phone. The rest? Only 8 to 5.
What to do? At this point Derek could have played the “Not my job” card and left production hanging. Instead, he decided to see if there was anything he could do to help.
He went to the equipment room where, sure enough, the fibre connection light on the switch was dark. “So I followed the cable from the rack,” he said, “and found it went to a wall-mounted box where it converted from the patch cable to the main multicore cable that ran under the yard…”
Hang on. One of the connectors looked like it was sitting a bit lower than its partner. Derek gave it a push and twist to seat it properly and hey presto! The plant burst into life.
“I suspect the connector had never been fully home since being installed about five years previously,” he told us, “it had been hanging, but had finally dropped to the point where the connection broke.”
Derek was the hero of the hour, and the recipient of many beer tokens from a grateful production team.
His boss, however, was less than impressed. Not with the slipshod connection, but with Derek’s helpful assistance. Instead he found himself receiving a dressing down: “That’s not your job!” snapped the boss.
“Such is life,” said a now-retired Derek.
Derek’s story reminded your correspondent of a fibre connection in a previous life where contractors left a mere 2cm of cable outside of the shielding. 2cm that proved all too attractive for sharp rodent teeth. Sadly, fiddling with the connectors didn’t resolve the rat-induced hardware trauma.
But that’s another story.
Have you ever stepped out of your comfort zone to fix somebody else’s problem? Were you garlanded with praise or berated for your efforts? Let us know, with an email to On Call. ®
*Somebody Else’s Problem (SEP) field: documented in Douglas Adams’ Life, The Universe and Everything and concerns something being invisible because it is, er, somebody’s else’s problem. Not to be confused with the Steve Jobs Reality Distortion Field.