IT Service Management Blog
Follow information regarding IT Service Management via this blog.

Act now! Share your HP Release Control best practices.

If you could set up Release Control all over again, is there anything you wished you would have known before you started?  Take a look at these questions from a Global 500 Release Control customer.  They have Release Control in production but are still in the process of setting it up for their users.   If you have any experience with Release Control respond to this blog.  I know they would appreciate the input.


  1. Do you have an official Release Management Process?
  2. Did you do much tailoring of Service Manager’s out-of-box Change Process? 
  3. Did you find it easy to map your data into the release screens?  Did you have trouble matching fields between Service Manager and Release Control?  Did you have to add fields?
  4. Do you have centralized roles other than Change Managers and Release Managers that validate and publish an Enterprise Calendar?  If so are they part of the Admin team or Change/Release teams(s)?
  5. Do your Director’s and VP’s utilize the Calendar?
  6. Does your Change Advisory Board (CAB) utilize the Calendar to vote? If so, what is the process that is followed?
  7. How many ‘generally available’ views do you have setup for your organization?
  8. What is the biggest value you get out of your calendar?
  9. Do you have any measures of success around your calendar? For example:  ‘You decreased the number of backed out changes by x% based on collision detection data’.
  10.  What filters do you use?
  11.  Do you export your calendar?  We would like to export the RC calendar, in a calendar view, for high level managers that don’t access RC directly.
  12.   Approximately how many changes / releases do you do in a year?
  13.   How many users have access to the Calendar and what are their roles? 

| ‎04-01-2011 12:58 PM

Regarding your question #10:


a)  Some companies have multiple CABs and they create a filter specifically for each CAB.  If a CAB is focused on a particular group of applications or services, you can create a filter specifically for changes that affect those applications or services. 


b)  Another type of filter is the Time Period filter.  The use case for this is to define a filter for all changes that affect a particular group of applications or services and save it as a time period filter (the same filter can be saved as both  a public and time period filter type).  Then you configure the time period that represents the allowed changes window for that group of applications and specify its Matching Changes to be defined by the previously defined filter.  Then when viewing the Time Period conflict tab for the change, you will see only the specific time period conflicts that apply to the services or applications that are affected by the change.

Richard Molenaar | ‎03-13-2012 02:40 AM

I have done several implementation of the Release Control application at large enterprise customers.

The application offers a lot of needed functionality and usability that Service Manager lacks.


The most importent feature is the impact analysis based on the uCMDB value chain information ( or technical chain information ).


The application also has some flaws which causes serieus issues for enterprise companies.


# The chang que from Service Manager ( or other import ) is very buggy. If the que gets stuk you have some serieus challenges in getting RC completely synced with the source again without manipulating the data.

# You have little to no control over the "extra" features of impact analysis that is done in RC. I donot know how to manage the history information that is used in the impact analysis. The history outcome of the changes for example ( succesvol by implementor etc ).

# Standard integration does not support the closure codes and text from Service Manager to Release Control.

# The impact analysis done by RC is not synced to SM, so in SM you donot have the information. Only in change tickets you can federate the information from RC.

# The screen layout of the integration for SM and RC require a very high resolution, normal VP users with laptops need to scroll all over the place to see the compleet information of 1 change.


And there are more issues that can cause pain.


I do see the benefit of a tool like RC. There is no other solution in the market at the moment that offers the same functionality that RC does. It has a lot of potential !


Please keep developing it and keep in mind that we like to have control over all aspects of the impact analysis. We donot like black boxes to depend on.

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.
Showing results for 
Search instead for 
Do you mean 
About the Author
Ann Keffer is a Product Marketing Manager for the HP Business Technology Optimization Business (BTO). She is responsible for out-bound mark...

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.