Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: JulietU86
New Today: 3
New Yesterday: 67
Overall: 148462

People Online:
Visitors: 52
Members: 1
Total: 53 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

Note: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


The Itil Community Forum: Forums

ITIL :: View topic - Standard Changes in HP OpenView Service Desk
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Standard Changes in HP OpenView Service Desk

 
Post new topic   Reply to topic    ITIL Forum Index -> Change Management
View previous topic :: View next topic  
Author Message
andincan
Newbie
Newbie


Joined: Dec 21, 2006
Posts: 2
Location: British Columbia, Canada

PostPosted: Fri Dec 22, 2006 3:31 pm    Post subject: Standard Changes in HP OpenView Service Desk Reply with quote

Hi All,

What a great forum! Tons of great info Thanks!

So, my second post since joining is an RFI Very Happy

I am currently leading a project to implement ITIL based processes in my organization as well as HP OpenView Service Desk V5.1. I am currently struggling with the configuration of Standard Changes in this system. The templates seem to be the obvious place, but the drop down interface is clumsy when there are a lot of items included. UI rules based on a custom field does not seem to be a great solution either!

Has anyone had any experience on this or would like to offer suggestions?? Comment on how you document and list Standard Changes would be appreciated.

In Service Desk, I am thinking that a combination of a shorter list of more generic templates combined with UI rules based on the CI category may be the way to go.

Any comments??

Thanks for you assistance.
Back to top
View user's profile
m_croon
Senior Itiler


Joined: Aug 11, 2006
Posts: 262
Location: Netherlands

PostPosted: Sat Dec 23, 2006 8:05 am    Post subject: Reply with quote

Hi,

It's been quite a while since I've worked with OVSD, but if I remember correctly, it is also possible to open templates from the file-menu, and there it is possible to place templates in folders. Using a folderstructure should give you enough support to use more templates.
Back to top
View user's profile Visit poster's website
ARoll
Senior Itiler


Joined: Apr 10, 2006
Posts: 86
Location: Boise Idaho

PostPosted: Thu Jan 04, 2007 7:19 am    Post subject: Reply with quote

andincan,

Greetings. Here is an option that we have done with our service desk 4.5 implementation. We found that we were not going to be using what was originally the Project module. What we have done since in our service pack we do not have the ability to relate changes to changes, we have reworked the Project module to become the "change group" module. What we utilize this for is relating multiple rfc's to what may be a project effort or rollout and these in turn have 1 group change created. For standard changes we also create a group change for the standard change. We have setup specific UI rules so that only certain person have the ability to created this Standard Group Change. (We have a status that is Preapproved and a Category of Standard). From there when they need to invoke the standard change again they create a copy of the original change request and update the necessary pertinent information (dates etc) and relate it to the "Standard Group Change". We have UI rules in place that check that newly created standard rfc is related to a standard group change. From there post implementation we in change management will review to ensure that the standard change process was followed. The UI rules in place to not allow the standard change to be related to a non-standard group change or nothing at all.

Again this may seem confusing to those that may not have worked with service desk but this was the solution we came up with. I've heard though that in later service packs(22 i think) and service desk 5.0 you do have the ability to relate an rfc to an rfc with out needing to ustilize the workaround that we did.

Adam
Back to top
View user's profile Send e-mail AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Change Management All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.