A little more than a week after Hurricane Sandy barreled through the Eastern seaboard, I wanted to take a moment and share some of my thoughts on business technology resiliency* and how we fared during this significant weather event. While there are still over a million people without electricity and significant recovery efforts underway, I'm overall impressed with the level of resiliency and preparedness many organizations exhibited during (and since) Sandy. I stress resiliency over recovery here because I believe that is the future of disaster recovery and business continuity. Our official definition is: “The ability for business technology to absorb
Service support functions have many names. Some of them are called a help desk, and others have moved on to be a service desk. But there is more out there to tackle! Is your service desk ready for a new identity? I am a huge fan of the IT support organization, as they help us when we need them . . . but to call them a help desk or a service desk . . . Really? Think about all the things we want and need them to do for us — I think this important function should get a new name!
Here are some new functional names that we (Forrester) came up with. Please tell us which one you like! Or tell us a name you like! As Victor Hugo said, “The future has many names: For the weak, it means the unattainable. For the fearful, it means the unknown. For the courageous, it means opportunity.” Looking forward to hear from you.
My customer experience with T-Mobile UK (or was it EE — Everything Everywhere, the joint venture between Deutsche Telekom and France Télécom in the UK?) last Friday was so shocking — and in some cases ridiculous — that I had to share it and highlight the potential customer experience parallels with IT service desks.
For balance: I’ve been a T-Mobile customer since February 2011 and its actual mobile service has been pretty good to date. I might whinge a little that availability seems to have dipped post–transition to EE (and I have no idea why) but that is probably just me imagining things. However, I didn’t imagine this . . .
So what happened?
I bought a second-hand phone and when I put my partner’s SIM in it (to test it), it registered on the EE network but I couldn’t send or receive calls or text; however, I could use mobile Internet. So I thought: is this a service provider, software, or hardware issue? After a quick but unsuccessful “Google” — always my first port of call for support these days — I realized that I needed some expert advice. As the SIM was “nearly working” I decided that I would call EE first.
It started well-ish, taking three minutes to get through the interactive options to a point where I could hear the now mandatory “we are really busy so you might be wasting your time on hold for a while” message. Thankfully I think it was only a minute or so. Then the “helpful” Patrick was available to help. And this is where the relationship started to break down . . .
Why is the system of record, not the customer, always in the right?
Earlier this week, in conjunction with ARM Holdings plc’s announcement of the upcoming Cortex A53 and A57, full 64-bit CPU implementations based on the ARM V8 specification, AMD also announced that it would be designing and selling SOC (System On a Chip) products based on this technology in 2014, roughly coinciding with availability of 64-bit parts from ARM and other partners.
This is a major event in the ARM ecosystem. AMD, while much smaller than Intel, is still a multi-billion-dollar enterprise, and for the second largest vendor of x86 chips to also throw its hat into the ARM ecosystem and potentially compete with its own mainstream server and desktop CPU business is an aggressive move on the part of AMD management that carries some risk and much potential advantage.
Reduced to its essentials, what AMD announced (and in some cases hinted at):
Intention to produce A53/A57 SOC modules for multiple server segments. There was no formal statement of intentions regarding tablet/mobile devices, but it doesn’t take a rocket scientist to figure out that AMD wants a piece of this market, and ARM is a way to participate.
The announcement is wider that just the SOC silicon. AMD also hinted at making a range of IP, including its fabric architecture from the SeaMicro architecture, available in the form of “reusable IP blocks.” My interpretation is that it intends to make the fabric, reference architectures, and various SOCs available to its hardware system partners.