Skip to main content

From IBM to MADGE - ROBECO Investment Bank – Rotterdam

For several years it was impossible to convince the IT guys, buyers or directors from ROBECO to try and buy our Smart Bridges. Despite all the brilliant arguments form the best consultant I ever met in my life, Andre Mooij, it was their firm opinion that it could not be as good, and certainly not better than the ones they used from IBM. Until…….

On that Friday night, around 17.30 local time, I had the call form a very nervous IT manager. His first question was if my last offer to test a MADGE Smart Bridge was still valid. The truth unveiled after a couple of extra questions, all IBM Bridges were down and nobody had a clue what happened and how to solve it. So one Bridge for testing would not be enough. Based on the 6 floor building, consisting of 2 towers each, at least 12 were necessary to have the rings in both towers up and running again.

The solution was one of a kind, based on the hard work of brave people in the warehouse in the UK who shipped the bridges, arranged the flight, a colleague that took the time to fly from Heathrow to Rotterdam and back, having the seat next to the 12 bridges and a poor guy form Robeco who had to pick up the stuff at the airport later that night. I guess it was around 23.00 that I had the call from the same guy who asked me to do this miracle that all bridges were up and running. He is probably still a Madge Superfan. The bank changed policy from IBM to MADGE almost instantly.

For those of you who were with Madge that period, you all remember I was punished for this action on stage during one of the international meetings, based on the fact that all logistic, technical and financial principles, guidelines and rules were broken to have this fixed. The risks were obvious but I choose to go for the opportunity to make Robeco a happy customer. I promised to never do it again and that is the real end of this story.

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi