There were a lot of acronyms and keywords being bandied about at
Gartner ITxpo this year. A Google search on the minds of the attendees would have generated a lot of hits on SOA, Globalization, Sourcing, Enterprise [Web] 2.0, “Free” Software, SaaS, and Cloud Computing. Social Networking was also an interesting thread that passed through all the other topics that attendees were abuzz about.
A large majority of the exhibiting vendors of course tagged their displays, demonstrations, and 30 second pitches with these terms to ensure that they too garnered as much attention as possible. I had a number of discussions with existing Managed Objects customers as well as parties interested in BSM about these trends and how to incorporate them into a cohesive strategy.
The BSM approach to dealing with these varied (and sometimes opposing) technologies is to focus on the service as a whole vs. individual moving parts and silos. As a customer of the power company, I expect that a flip of a light switch produces a predictable outcome every time – the lights come on. If they don’t, I don’t expect to hear details from the power company about all the potential issues that they are looking into ranging from failures in relay stations, downed power lines, problems with grids in neighboring states, etc. I count on them knowing the scope and source of the problem very quickly and getting it resolved. Electricity is an essential service and that level of understanding of what’s going on in the various moving parts of the power business is crucial.
Translating this type of operational model to IT management is what produces an effective BSM strategy. With IT becoming more complex (SOA, Enterprise 2.0, open source) and diffuse (Globalized, xSourced, SaaS, Cloud Computing) simultaneously, it is crucial to provide the best-of-breed management solutions for SMEs in each of these areas. Stopping here, however, leads to the all too common trap of too many tools and not enough answers. The key ingredient is a federated system that combines KPIs from each of the specialized solutions and allows a business level view to be constructed from it, that is, a true Manager of
Managers with customizable dashboards for all parties with a vested interest in service availability and performance.
Implementation of this BSM strategy requires access to data connectors that span multiple vendors’ management solutions, expansion opportunities for the next generation of platforms, and most importantly – an analysis engine that can handle the complexity of the combined data feeds and make it available to a flexible presentation layer for the users of the system.
Although there were many different solutions to these challenges presented at ITxpo, a successful BSM deployment should offer a simple and personalized iGoogle-like experience for managing and viewing content of underlying IT infrastructure and the applications that run on top of it, and that’s one thing that everyone agreed on.
-- Abbas
Nice write up Abbas. How do we get clients to focus on creating a BSM strategy? How do we get them to eventually elevate the BSM solutions above the tactical quick wins they're often initially deployed for? How do we establish an equal seat at the secret council for BSM alongside the other cool initiatives like SOA, BI, Governance and Risk, etc.?
I see far too many clients who continue to treat the BSM solution as just another tool they hope will save the day but don't create and adopt a strategy that guides them for the long run.
Doug
BSM/ITSM Blog: http://dougmcclure.net
Posted by: Doug McClure | April 17, 2008 4:41 AM
Your questions are exactly what the champions for a BSM solution at an organization should think through before pulling the trigger on any deployment. On the BSM strategy front, I strongly believe that there should always be a showcase deployment initially that addresses the initial pain that started them down the road. Stretching my light switch analogy a little bit – everyone has had a situation where flipping the switch resulted in either nothing happening, the bulb blowing up, flickering, or a dim light coming on. It’s important to pilot or have a phase one implementation that actually delivers on the promise of either preventing the situation from occurring in the first place, or allowing it to be fixed much more effectively and quickly.
Internally, this deployment now becomes a showcase which can be used to expand the deployment. When one LOB or service owner has a better way of doing things than the others, the news quickly spreads and starts a “Me Too!” rush. I have personally observed this taking place at a number of BSM deployed sites including the financial sector and the federal government.
To be on the “cool council” you either have to be cool on your own merit which I think the Me Too rush enables, or add something unique to other projects sitting at the table. In most cases, cool is also new, unknown, groundbreaking, game changing and BSM can be a key piece in the deployment strategy to make sure that it can deliver. For example, SOA adds so many moving parts to the picture that unless you do track it holistically as service, troubleshooting and monitoring are going to be a nightmare. Governance and Risk on the service side require some element of prediction/modeling capabilities in a BSM solution, which a complete one should include.
In my experience, the people who see the most value from a BSM deployment are also the ones that view it as a lot more than a tool, but rather think of it as a platform on which to base process and knowledge sharing enterprise wide.
Abbas Haider Ali.
Posted by: Abbas Haider Ali | April 30, 2008 9:19 PM