IT service management (ITSM) has a number of definitions from a variety of sources. Starting with the ITIL (the ITSM best practice framework)-espoused definition:
“The implementation and management of quality IT services that meet the needs of the business. IT service management is performed by IT service providers through an appropriate mix of people, process and information technology. See also service management.” Source: ITIL 2011 Glossary http://www.best-management-practice.com/officialsite.asp?DI=575004. Where service management is defined as: “A set of specialized organizational capabilities for providing value to customers in the form of services.”
A more “directly customer-focused” definition is provided on Wikipedia:
“A discipline for managing information technology (IT) systems, philosophically centered on the customer's perspective of IT's contribution to the business. ITSM stands in deliberate contrast to technology-centered approaches to IT management and business interaction.”Source: http://en.wikipedia.org/wiki/IT_service_management
If you're an I&O professional, what comes to mind when you say "end user"? If you're like most of us, your mind has a conjured-up impression of a cosmically clueless person who actually gave you a hard time once, and the picture is now your mind's own avatar for everyone you support. It's not usually a positive image, is it? I used to picture a middle-aged, BMW-driving executive with his hair parted on one side wearing an LL Bean sweater, probably an Ivy-league grad, who couldn't be bothered to actually take responsibility for his own personal computing destiny…he always had servants to take care of trivialities…and hence he was ruining my day with his incompetence. Let's call him Ascot Rothschild III.
An image like that is a powerful thing, and the painful memory of this individual's willful, arrogant ignorance then pervades our future thinking about what we're up against when we set IT policy like BYOC. Ascot becomes the poster child - in our minds anyway - for every garden-variety corporate doofus that we'll have to deal with if we give people any more rope than we already do. They also give us plenty of reasons to take more rope away. In my case, I used to sit on a helpdesk for Remedy customers, and my team had a collection of "special" customers we wondered how they managed to get dressed and find their car keys in the morning. As I later designed Remedy and Peregrine applications, I did so with these "edge cases" in mind.
Amazon Web Services (AWS) is great, but many of our enterprise clients want those cloud services and values delivered on premise, behind their firewall, which may feel more comfortable for protecting their intellectual property (even if it isn't). AWS isn't very interested in providing an on-premise version of its solution (and I don't blame them). Today's partnership announcement with Eucalyptus Systems doesn't address this customer demand but does give some degree of assurance that your private cloud can be AWS compatible.
This partnership is a key value for organizations who have already seen significant adoption of AWS by their developers, as those empowered employees have established programmatic best practices for using these cloud services — procedures that call AWS' APIs directly. Getting them to switch to your private cloud (or use both) would mean a significant change for them. And winning over your developers to use your cloud is key to a successful private cloud strategy. It also could double your work to design and deploy cloud management solutions that span the two environments.
There has been a lot of buzz around using the cloud for disaster recovery lately, and with good reason -- it's a new and compelling approach to fast recovery. However, along with any hype comes a certain amount of confusion, so I set out to get some clarity on what cloud-based disaster recovery really is. The core feature of any cloud-based recovery is that ability to actually recover at the providers' location using their cloud assets. Just copying data there is not true recovery. I also realized that the term "cloud-based disaster recovery" was too broad, and that actually solutions fall into one of three categories:
Do-it-yourself (DIY): Using the public cloud to architect a custom failover solution leveraging the agility and speed of the cloud.
DR-as-a-service (DRaaS): Prepackaged services that provide a standard DR failover to a cloud environment that you can buy on a pay-per-use basis with varying rates based upon your recovery point objective (RPO) and recovery time objective (RTO). Data is either sent using backups or replication.
Cloud-to-cloud disaster recovery (C2C DR): The ability to failover infrastructure from one cloud data center to another, either within a single vendor's environment or across multiple vendors.
I don’t blame you. And here’s why: The scope of mobile management is confusing and expansive, including things like mobile device management (MDM), persona separation technology, enterprise application stores, application management and a slew of other tools. Some vendors focus purely on one mobile management category, like device management, while plenty of others tackle two or three different enterprise challenges. At the same time, this market is evolving so fast that any assessment of the technologies and their vendors is out of date within 2-3 months.
But before I explain why Symantec’s acquisition is so important, let me give some more context. Mobile management has three main components which I&O professionals are thinking about, the device, the apps, and the data. Today, most first firms follow a very similar path: devices first – get an MDM solution to provide some control over the environment, set a mobile policy for employees, and start trying to figure out what to do about applications and data. Realistically, MDM only solves your challenge around device control – probably the least important of the three. That’s the path that many vendors are following today. As the MDM market becomes more commoditized, most vendors are turning their engineers towards data protection and sharing tools and application management technology. Had a conversation about Dropbox or Box.net lately? That’s a conversation about both apps and the data.
OK ITIL, the IT service management (ITSM) best practice framework, is neither a cult nor a religion, but hopefully I grabbed your attention.
The point of this short, but hopefully interesting, blog is that when we usually think about ITIL we normally focus on the IT service management and IT operations organizational domains as its playground. And, while we appreciate that other IT roles might have an interest in ITIL (especially enterprise architects or those looking at DevOps), I imagine most will be surprised at the following percentage readership demographic for my recent “Adopting ITIL” report.
Percentage split of Adopting ITIL readers across Forrester “role types”
Last week I had the pleasure of attending ManageEngine’s first user conference and training event in the Middle East (Dubai to be specific); with event attendees not only from the UAE, but also Bahrain, Egypt, Kuwait, Oman, Qatar, Saudi Arabia, and Russia.
The one-day user conference element of the two-day event, offered me both fresh insight into how IT service management, ITIL, and enabling tools are being adopted in the Middle East, and first-hand experience of ManageEngine’s customers within the region.
This quick blog is intended to capture my views, thoughts, and opinions for the benefit of all.
The current state of IT service management in the Middle East?
My previous experiences of IT service management and ITIL in particular in the Middle East had been somewhat limited; but as with most things I had drawn my own opinions and conclusions based on the exposure (the proverbial joining of dots). So before last week I believed:
ITIL was talked about but with “implementations” driven from the higher echelons, or even outside, of the IT organization; adoption was slow and susceptible to resistance. It was a “good thing to do” rather than a business-focused means to an end.
That while customers (end users) are important the focus was still very much on the IT – the creation of IT rather than the consumption of IT services.
Middle Eastern companies value “prestige” and as such were most likely to buy Big 4 solutions for IT service management.
Next up in the 2012 lineup for the Intel E5 refresh cycle of its infrastructure offerings is Cisco, with its announcement last week of what it refers to as its third generation of fabric computing. Cisco announced a combination of tangible improvements to both the servers and the accompanying fabric components, as well as some commitments for additional hardware and a major enhancement of its UCS Manager software immediately and later in 2012. Highlights include:
New servers – No surprise here, Cisco is upgrading its servers to the new Intel CPU offerings, leading with its high-volume B200 blade server and two C-Series rack-mount servers, one a general-purpose platform and the other targeted at storage-intensive requirements. On paper, the basic components of these servers sound similar to competitors – new E5 COUs, faster I/O, and more memory. In addition to the servers announced for March availability, Cisco stated that it would be delivering additional models for ultra-dense computing and mission-critical enterprise workloads later in the year.
Fabric improvements – Because Cisco has a relatively unique architecture, it also focused on upgrades to the UCS fabric in three areas: server, enclosure, and top-level interconnect. The servers now have an optional improved virtual NIC card with support for up to 128 VLANs per adapter and two 20 GB ports per adapter. One in on the motherboard and another can be plugged in as a mezzanine card, giving up to 80 GB bandwidth to each server. The Fabric Interconnect, the component that connects each enclosure to the top-level Fabric Interconnect, has seen its bandwidth doubled to a maximum of 160 GB. The Fabric Interconnect, the top of the UCS management hierarchy and interface to the rest of the enterprise network, has been up graded to a maximum of 96 universal 10Gb ports (divided between downlinks to the blade enclosures and uplinks to the enterprise fabric.
My colleague Benjamin Gray and I have been looking closely at Windows 8 for the past several months to make sure we have a clear understanding of what it means for I&O organizations, leaders, and professionals. We have been briefed in depth by Microsoft executives, program managers, and engineers. We have downloaded, installed, and used the Windows 8 Consumer Preview, and we have had hundreds of conversations with I&O professionals in the past year on Windows 7 (and now Windows 8) adoption — from those looking for guidance, as well as those with strong opinions already formed. As you might expect, we have formed some opinions of our own.
For those who haven't talked with Ben Gray, he is a fantastic authority on Windows adoption trends with complete mastery of the data. He has closely watched Windows Vista, Windows 7, and now Windows 8 go through the cycles of preparation, migration, adoption, and operation. Ben was the first at Forrester to point out that Windows 8 is an "off-cycle release," coming too soon on the heels of Windows 7 for companies to be ready to adopt it. He and I authored a document on Windows adoption trends for 2012, which will be published shortly and provides additional data and context. Ben has also dissected the Forrsights Workforce Employee survey data in dozens of ways, and he delivers a fantastic presentation for Forrester customers on what he's learned.
Apple launched its next-gen tablet, the new iPad, yesterday at a San Francisco event. Among the standout features includes a Retina display with 2048×1536 resolution, meaning that the new iPad has 1 million more pixels than a 1080p HDTV. Further, the device packs a dual-core CPU, a quad-core A5X graphics processor, LTE support, worldwide 3G support, and 10-hour battery life (nine hours on 4G). I expect that these upgrades will undoubtedly be enough to attract consumers and enterprises alike and further consolidate Apple’s resounding tablet market leadership globally.
So what will be the impact of the new iPad on the rapidly evolving telecom industry? I believe it will disrupt the market due to the following:
The As will rule the tablet market. The tablet market is moving towards a likely duopoly between Apple and Amazon due to their aggressive pricing strategies. Through Kindle Fire, Amazon has wiped out the competition in the sub-$199 price range while with the new iPad, Apple will knock out competitors starting from $499 upwards. Moreover, as iPad 2 will coexist alongside the latest incarnation and Apple will slash iPad 2 prices to $399, it reduces the market play of other OEMs such as Samsung even further.