UCMDB and increasing customer ROI

In Greek mythology Sisyphus (pronounced /ˈsɪsəfəs/; Greek Σίσυφος sísypʰos [ˈsisifos] was a king punished by being compelled to roll a huge boulder up a hill, only to watch it roll back down, and to repeat this throughout eternity. http://en.wikipedia.org/wiki/Sisyphus

 

Increasing customer ROI is something I have been focusing on furiously since receiving responsibility of the UCMDB functional architecture about three years ago. It was clear to me right from the outset that we were handing customers with a great piece of machinery but expecting them to unnecessarily perform Sisyphean work. If you wanted to map a service then TQL was a great way of doing so. However, what do you do when you have 1000 services? And what do you do when you wish to leverage impact analysis capabilities and also monitor the same service? In that case, you had to generate a unique view for every occasion. We could do better than that. We had to.

 

Enter the 8.0 modeling studio with the ability to separate service models from views. What we realized was that customers were building hundreds of views that were based essentially on an almost identical query, except for a core part that changed from view to view. We then looked further into this core and discovered that it consisted of the basic elements of services i.e.. the infrastructure elements that were dedicated to the service. The rest of the view was the information related to these elements (network, databases, software, etc'). We decided to allow customers to define this core as the model of the service and then apply what we call perspectives to these service models. Perspectives bring this related information so now you could model your billing service once and then have different people consume this service based on their needs e.g.. "show me the network that supports this service" or " show me the storage this service uses". Perspectives are essentially parameterized queries and the parameter values are the CI instances that are in the service models.

 

So what does this mean? Once you model your services you can start consuming these models in various HP BTO applications. The service models you define are consumed by Release control for its impact analysis. The same service models are consumed by the BSM dashboard. This means that we also ensure that what Release control predicts will happen if a server is down will actually show on the BSM dashboard if the server actually does go down. Model once - Consume everywhere!

 

"But Ahi" you will say to me, "How can I keep maintaining 1000 service models manually? It is untenable". To that claim I can now answer with "Pattern based modeling". Starting with the 9.0 release, even the content of your service models can be based on query results. So now the content of the service model is dynamic and so is the part that gets the related information (perspective). Think of the power you get at your fingertips. 9.0 also allows combining perspectives in various ways as they are applied to the service model. And oh, let's not forget that the resulting views can be consumed at various places of the portfolio and for your reporting purposes as stated above. Model once - Consume everywhere!

 

I encourage you to look into the modeling studio and pattern based modeling. Once you get it you'll realize that we regard this increased return on UCMDB investment as one of the topics most near and dear to our hearts. Going forward you can expect to see these capabilities continue to evolve. We will continue ensuring that the time you have to spend modeling your services will decrease by adding productivity features. At the same time, the value you get out of service models will continue to increase by adding more and more ways in which these service models are consumed across the portfolio.

 

So check us out at an IT outlet store near you and find out just how much value you can get out of our products. I'll say it one more time folks: Model once - Consume everywhere!

Comments
Parasuram Anantharam | ‎09-09-2010 10:09 AM

Ahi,  This is a great article.  I'd like to suggest that HP or one of the power users of UCMDB give detailed worked out examples on how we could fully leverage the power of UCMDB, especially along the lines of this article.   It'd be a great enhancement to the documentation and would do a better job of transferring the vision of the designers of UCMDB into real uses in the customer world.

Ahi Gvirtsman | ‎09-14-2010 05:37 AM

We have numerous customers using the modeling studio concepts and it shouldn't be difficult to get some reference screenshots. What medium do you think would be appropriate for this? I'm not sure that this blog would be the right one. Usually we arrange a session where customers show each other what they do with the product.

Parasuram Anantharam | ‎09-15-2010 09:24 AM

Ahi,  Thank you.  I was just on the Practitioner's forum with Jody Roberts and they're putting together a running exemplar to capture this kind of information and create case studies.  One thing that would be very beneficial, in my opinion, is to include step-by-step bow-to information and not stay too high-level.

A great medium would be to post it as a paper / examples on the CMS Community Website (HP LiveNet Forum).

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
Showing results for 
Search instead for 
Do you mean 
About the Author
I'm a 20 year veteran in the software industry with experience ranging from control systems, communications systems, RAD systems and for the...
Featured


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.