Sign in | Join United States - English [Change]
 Home > Insights 

To ITIL® V3 and Beyond: Travels with Rob Stroud

Travel around the world with this IT best practices evangelist as he speaks on IT Service Management, IT Governance and ITIL trends

November 2007 - Posts

  • Bringing ITIL Home for the Holidays

    I've decided to use the upcoming holiday season to launch an ITIL initiative in my home. With all the time I spend evangelizing on ITIL, it is only natural that it has crossed over from my business life to my personal life.  

     

    My idea was prompted by a conversation I had with an energy sector executive. Our discussion covered the increasing reliance of business on technology. This was exemplified by the exec's energy company, which is in the middle of replacing their out-dated meter reading process. The current process necessitates bi-monthly visits to clients' backyards, and in-between estimates of power usage, which I can tell you from experience are never close. The new system is made up of smart meters that automatically send actual usage information back to the company. The system also allows customers to view their power consumption online. This got me thinking.   

     

    With winter in the northeast of the US fast approaching, steps to leverage this new system to manage my power consumption would yield real value. I began to think like a business--a business that has adopted ITIL best practices of course.

     

    I am going to set up a process to monitor and manage power consumption remotely. I'll use alerts to notify me when my threshold of acceptable power consumption is exceeded.  I'll send automatic and electronic change requests to the thermostats controlling my heating to lower the setting. I'll verify the change is correctly implemented by checking the power consumption (which should immediately decrease) online.

     

    Managing all of this in my head will be complicated, so I'll document the event management and change management processes involved. 

     

    What maturity level do I attempt? How do I know I am done? As currently planned, my total expenditure for this project is conveniently just under $1000 (I say conveniently because in my house, projects over $1,000 require a business case). I will need to consider the impact on resources: I will not be available for the annual backyard cleanup process (well documented in the annual work list) and I may have to miss a play or two of football.  Still, I think it will be a weekend well spent.  

     

    Back to the energy company discussion for a moment. One of the points made by the exec was that the line between IT and business processes are increasingly blurred. The Technology Service Desk is handling more questions every day as more business is transacted via the web and customers have greater freedom to manage their own power consumption. The smart meter proactively sends data to the billing process which interfaces with clients' bill payment services. Electronic alerts notify customers that their bills have been automatically paid. The value to the energy company is a more constant cash flow, which leads to a reduction in the number of days that receipts are outstanding.  With less overhead, the price of energy declines.

     

    If the focus was on departmental silos instead of on the overall business solution, we would have lost sight of the primary business driver, which is to provide energy with less overhead, allowing delivery to be at a lower cost and ultimately playing a role in the greening of IT and the business.

     

    So what is the business driver for my household ITIL implementation? I travel so much that I need to control the human manual override within my house--my wife and children who continue to believe that holiday lights should be on all night and 80 degrees is the optimal temperature indoors--even during a New York winter.  

     

    ITIL® is a Registered Trade Mark, and a Registered Community Trade Mark of the Office of Government Commerce, and is Registered in the U.S. Patent and Trademark Office.

    Share this post: Email it! | bookmark it! | digg it! | reddit!
  • Proving CMDB Value through “Scenario Planning”

    I recently spoke at a number of very well attended CMDB seminars. Without fail, I was asked the following question, either during my talk, or afterwards during the accompanying networking events: How can I implement a CMDB and show value quickly?

     

    I subscribe to a notion that my blogging colleague Marv Waschke recently wrote about in his Iterating on IT Service blog posting entitled "ITIL v3: Simplifying Complexity."  That is that implying that something inherently complex is simple raises all kinds of suspicions and red flags. That being said, happily there is a proven way to implement a CMDB and show value quickly. I'll explain.        

     

    A large manufacturing client I spoke with at a recent event completed their initial CMDB implementation in 60 days. In a future blog posting, I'll cover how they managed to implement so quickly. For now, I'd like to delve into how they managed to deliver value so quickly, using a technique they dubbed "scenario planning."

     

    Scenario planning involves developing a number of business scenarios through which the CMDB would add value, leveraging "high value CIs." (A high value CI is a parent CI, usually a business service or critical asset in the organization.) These scenarios are used to support the business case for funding the CMDB. By limiting the scenario scope, work is focused on delivering benefits most important to the business. For this client, recent outages reinforced the premise that the efficient running of the production line should form the central focus of the CMDB implementation and the service levels that related to it. 

     

    Their selected scenarios included the following:

     

    1. Identifying major incidents affecting the production line (one of our high value CIs); identifying the IT systems and processes involved; finding the root cause; and fixing the CI with a change.
    2. Resolving an error identified late in the release cycle of a change and using the relationships stored in the CMDB to determine the critical components to be tested prior to releasing the change to the production environment.
    3. Identifying critical components and ensuring that they are identified appropriately so that the change process ensures that all changes to technology affecting the production line are scheduled during downtime.

    The scenarios were carefully selected to meet the clear objectives of ensuring compliance with service levels, and ensuring that unscheduled changes do not affect the production process. With well-defined scenarios purposefully designed to address important organizational issues, the initial CMDB implementation was able to proceed with a laser-like focus on processes that the organization already acknowledged it needed. The value of the CMDB was quickly evident.

     

    To ensure that value is quickly realized, the initial CMDB implementation must not be sidetracked into superfluous CMDB muscle flexing. Rather, the success of the scenario planning technique is dependent on IT's ability to concentrate solely on the CMDB benefits that can address specific business priorities. I suggest those of you facing a CMDB implementation give this technique serious consideration.

     

    For more CMDB implementation advice, I recommend reading the eBook entitled Delivering Better Service with a CMDB, written by Shirley Lacy, industry expert and ITIL® V2 and V3 author. Chapter 1 introduces you to Configuration Management and covers the critical success factors in implementing a CMDB. You can read it for free by registering here.

     

     

    ITIL® is a Registered Trade Mark, and a Registered Community Trade Mark of the Office of Government Commerce, and is Registered in the U.S. Patent and Trademark Office.

    Share this post: Email it! | bookmark it! | digg it! | reddit!
 
 
Page Tools