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: JKEHV
New Today: 64
New Yesterday: 88
Overall: 139965

People Online:
Visitors: 57
Members: 1
Total: 58 .

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 - Change Management implementation problems
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Change Management implementation problems

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


Joined: Sep 18, 2006
Posts: 9

PostPosted: Mon Sep 18, 2006 6:41 pm    Post subject: Change Management implementation problems Reply with quote

Hello all,
We are currently implementing change managment to our system.
There is a question that we can't find the answer.
Is it possible to create a change from an incident?
If change management covers all the configuration item changes in this case I can open directly a change order. But in the reference the way described like this:
incident-->problem-->change order
I don't understand please help me
thank you
ermanu
Back to top
View user's profile
Fabien
Senior Itiler


Joined: Sep 27, 2005
Posts: 207

PostPosted: Mon Sep 18, 2006 10:05 pm    Post subject: Reply with quote

Hey Ermanu,

The point in ITIL is that by the time you get to raise a Request For Change, you have already analyzed the root cause of your incident, which means you have performed the Problem Control subprocess and you are in the middle of the Error Control subprocess of Problem Management.

There are reasons why ITIL looks at it this way:

1) The goal of Incident Mgt is to restore service ASAP. We are concerned that you may be spending too much time trying to fix an IT problem, and not enough restoring the business service. In other words, we want to make sure, at Incident Mgt level, that you are doing your utmost for speed.

2) We are also concerned that if you go straight from Incident Mgt to an RFC, you may miss the opportunity to document a workaround that could considerably reduce the time to resolution for later incidents of the same type.

3) From the Incident Mgt process, you should be missing the 'big picture' that Problem Management has. Where you would expect Incident Mgt to give more priority to urgency, you would see Problem Management prioritize more on business impact. By going straight from Incident to RFC, you could be working on the wrong priority.

All that is fine and easy but it's theory. If you can make sure that the three above principles are maintained in your implementation, then you have implemented Problem Mgt even though it will not be recognized formally in the overall process.

I always take the side of the structured approach and wonder: why would the Service Desk operator want to raise an RFC? Will it speed up the process? What are the circumstances? What is the trade-off? Am I burning steps? ... and I think you are asking yourself those questions so that's great. Ultimately you need to do what makes sense for your organization.
_________________
BR,
Fabien Papleux

Accenture
Technology Consulting | Service Excellence
Red Badge Certified

Twitter @itilgeek
Back to top
View user's profile Send e-mail Visit poster's website MSN Messenger
UKVIKING
Senior Itiler


Joined: Sep 16, 2006
Posts: 3293
Location: London, UK

PostPosted: Tue Sep 19, 2006 3:21 am    Post subject: Reply with quote

in addition to Fabian's data

Consider Service Requests from your customers/users

Firewall changes - open / close ports, ACL list change
Software Installation, Upgrades, Patching etc

would not really have an Incident but may have a Service Request - Although a Service Request starts as an incident because that is the way ITIL defines an incident and Service request
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Configuration 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.