CA Community






This Blog
Syndication

April 2008 - Posts

CSI: Crime Scene Investigation or Continual Service Improvement – You decide

Published: April 14 2008, 08:11 AM | no comments
by Marvin Waschke

 

Most of the country thinks CSI stands for "Crime Scene Investigation," as popularized on TV. In a convoluted sort of way, the acronym means something similar in ITIL® v3. This is a stretch, but bear with me.   

 

In v3, CSI stands for Continual Service Improvement and it is the fifth volume of the v3 publication. In the v3 scheme of things, CSI is the culmination of Strategy, Design, Transition, and Operation and is the phase in the service lifecycle that actually is part of all of the previous four phases. But too often, CSI becomes Crime Scene Investigation when we in IT mess up.

 

On TV, the ensuing activity takes place in Las Vegas, Miami and New York. In this blog, we visit Washington DC...

 

Recently, the Census Bureau announced that they are abandoning a plan to replace paper and pencil with wireless handheld computers for the 2010 census, a move that will add 3 billion dollars to the cost of conducting the census according to the New York Times in an article entitled "Dust Off the Pencils: Plans for High-Tech Census Collapse." The Washington Post article is entitled Census Back to Pen and Paper. I'm not sure what bothers me more, overlooking industry best practices, the $3 billion, or sharpening all those pencils. 

 

As a student of ITIL, the phase "crime scene" might come to mind when reading the details. I don't want to point fingers or try to second guess the participants based only on a couple of news items, but this is an example of a failure in service management that ITIL good practices are designed to prevent.

 

Apparently, the problem began in the strategy phase when the requirements for a projected service are formulated based on the strategic goals. I infer from the news reports that the strategic goal of this service was to increase the accuracy and decrease the cost of the census. The strategic plan was a reasonable, even modest, extension of commonly used inventory technology: use GPS enabled handheld computers to record the exact location of each canvassed household and wirelessly transmit the collected data to regional accumulation centers. According to the reports, the requirements for implementing this plan were not thoroughly understood or communicated to the partner who was to supply the devices. As the project proceeded, more and more requirements were added, under-estimates were revealed, and costs ballooned, eventually resulting in the cancellation of plans to implement the service.

 

It is not clear whether the service ever got beyond the design phase and into transition where it would have been tested and deployed into the production environment, and it certainly never reached the operation.

 

In the ITIL v3 service lifecycle, CSI plays a role in every phase. Experience with the service in each phase is collected and analyzed to discover ways to improve the service. In the case of a failed service, this is a lot like Crime Scene Investigation, looking for the mistakes made and tracing flaws so that the service can be improved in the future.

 

Census takers may still use pen and paper in 2010, but if the Census Bureau applies CSI properly, there is a good chance that the 2020 census will be automated.

 

 

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:  
Leave a comment

 

By: Marvin Waschke
Marv Waschke is a senior principal architect at CA Technologies. He has represented CA Technologies in several standards groups including the Cloud Management Working Group and Configuration Management Database Federation working groups of the Distributed Management Task Force (DMTF). He is also a member...
Read More..

ITIL v3 – You’re doing it whether you know it or not

Published: April 08 2008, 02:36 PM | 5 Comment(s)
by Robert Stroud

 

I'd like to make a quick point. There are times when I find the discussions surrounding ITIL® v3 popularity to be superfluous. That's because whether or not people are "for" ITIL v3, if they want to work for successful organizations, they have probably already put several aspects of ITIL v3 into practice -- whether they realize it or not.  

 

I recently visited several European ITIL practitioners who are in process of transforming their ITSM implementations to support their dynamic business environments -- the objective, to innovate as the market demands. As the head of the ITSM team at a large manufacturer commented, "any ITIL implementation that is service aligned is doing much of v3 already." I concur.

 

In his case, Knowledge Management, Self Help and Access Management have been part of his culture for the last 12 months and pre-date the launch of v3.  

 

So please. There is no "for" or "against." You are going to adopt some practices that are suspiciously reminiscent of ITIL v3. If you choose not to label them as such, so be it. Or, to paraphrase Chelsea Clinton, "that's absolutely none of my business."

 

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:  
Tags: , ,
Leave a comment

 

By: Robert Stroud
Robert Stroud serves as VP and as Service Management, Cloud Computing and Governance Evangelist at CA Technologies. Robert also serves as an International vice president of ISACA, is part of the Framework committee and was the former chair of the COBIT Steering Committee. Robert also serves on the itSMF...
Read More..

COBIT and ITIL – Better Together

Published: April 01 2008, 09:25 AM | 2 Comment(s)
by Robert Stroud

 

Those of you struggling with bringing IT and business alignment to life through your ITIL® initiative may be surprised to learn that your salvation may lie in a free download.

 

Even with the improved use of organizational charts and metrics in ITIL v3, some practitioners have commented that the linkage to a sound maturity process is still lacking. This is where COBIT, which is available for free from http://www.isaca.org/, can assist.

 

Many companies that I work with have been using COBIT's Key Performance Indicators, Maturity Models and RACI Charts (which track  Responsible, Accountable, Consulted and Informed persons for every process) to provide metrics and structure for their ITIL processes.

 

COBIT is the governance framework that aligns business strategies and objectives with IT deliverables by identifying and analyzing the IT processes and measurements needed to construct processes that deliver desired business results.

 

COBIT provides the missing governance capabilities for your ITIL processes, helping you measure and assure performance and roll up the metrics to business requirements to provide a holistic view of your performance.

 

While ITIL does offer performance measurements and organizational information, in my opinion these don't roll up to the business level to the extent COBIT does.

 

For example, take a look at COBIT process DS1, Define and Manage Service Levels, which is defined as control over the IT processes of defining and managing service levels with the objective of ensuring the alignment of key IT services with business strategy. COBIT identifies requirements, inputs, outputs, report requirements, organizational impact, metrics and the maturity model (every COBIT process has its own maturity model to show you where you are and where you are going ) -- all of which can assist you in your ITIL journey.

 

So go to isaca.org and download COBIT.  It's on me.

 

By the way, check back at isaca.org in the next few weeks for mappings of COBIT 4.1 to ITIL v3.  We'll have two versions to choose from depending on whether you have an existing leaning towards COBIT or ITIL.  

 

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:  
Tags: , ,
Leave a comment

 

By: Robert Stroud
Robert Stroud serves as VP and as Service Management, Cloud Computing and Governance Evangelist at CA Technologies. Robert also serves as an International vice president of ISACA, is part of the Framework committee and was the former chair of the COBIT Steering Committee. Robert also serves on the itSMF...
Read More..

Should Service Users Be Tracked as CIs in the CMDB?

Published: April 01 2008, 09:17 AM | no comments
by Marvin Waschke

 

As CMDB experts go, I have a lot of experience, starting with implementations a decade ago when ITIL was almost unknown in North America. Still, a question posed to me at CA's recent customer-focused Development Buddy Summit sent me to the books -- the ITIL® books that is -- hunting for an answer.

 

In a one-on-one conference, a customer asked me if it was appropriate to use "people CIs" in the CMDB to track subscribers to services.

 

Hmmm. Technically, the CA CMDB can support such a practice. After all, it has a CI family representing people that can be connected with applications such as HR and LDAP (Lightweight Directory Access Protocol that helps you locate individuals and other resources on the Internet or on an intranet) that specialize in information about people. Theoretically, those "people CIs" could have a "subscribes to" relationship with service CIs. But maintaining these "people CIs" would be a predominantly manual process that would not scale easily throughout an enterprise.

 

I suggested that CA Service Catalog could be the solution as it is designed to track and manage subscriptions to services.

 

Though I had provided an answer, the nagging question followed me back to my hotel room and kept me awake that night. When a customer asks for something, I like to examine the need in depth. If one client perceives a need, then others might as well and that could lead to useful product enhancements.

 

This question sent me to the ITIL v3 library for an answer. If ITIL suggested using people CIs to represent service subscribers, then perhaps we should consider putting more support for it into the CA CMDB.

 

After hours of research that took me through several ITIL v3 volumes, I concluded that ITIL does not suggest using people CIs in this manner.

 

The ITIL v3 Service Transition publication does list "people" as potential CIs, but only in two types of CIs. The first type of CI that includes people is the Service Capability CI. This represents the intangible capabilities or expertise that organizations, functions, teams, or people have to design, implement, operate, and maintain services. The second type of CI is the Service Resource CI. Service resources are tangible assets that can be drawn upon for services. A person is a service resource when he or she is employed to design implement, operate, or maintain services.

 

Subscribers, users or customers of a service are neither service resources nor service capabilities. Rather than contributing to a service, they receive value from a service.

 

ITIL talks about services as a way for users to assign costs and risks to a service supplier. In other words, service users are seeking to gain the benefits of service capabilities and service resources without taking on the risk of owning these capabilities or resources. Therefore, although ITIL v3 suggests people be included in the CMDB, it does not suggest service subscribers, users or customers should be CIs.

 

Since ITIL is good practice, not law, I did entertain the notion of including service customers in the CMDB even though this practice was not mentioned by the ITIL authors. Ultimately, I decided against it. SACM (Service Asset and Configuration Management, the processes that own the CMDB) focuses on supporting the implementation of service designs that represent solutions that meet requirements based upon enterprise business strategies. That is a tall order, but it does not include managing the users of services. Loading the CMDB up with subscribers, users and customers is bound to invite confusion and error.

 

The conclusion I came to after several days of research matched the answer I gave during my client meeting: A service subscription catalog, which is designed to support the customer-to-service relationship, is the right place to house service subscriber, user and customer information.

 

I don't regret having invested the time. Researching answers is my favorite way to learn. Plus, I'm sleeping soundly once again.

 

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:  
Leave a comment

 

By: Marvin Waschke
Marv Waschke is a senior principal architect at CA Technologies. He has represented CA Technologies in several standards groups including the Cloud Management Working Group and Configuration Management Database Federation working groups of the Distributed Management Task Force (DMTF). He is also a member...
Read More..

More Posts