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


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: Scottnup
New Today: 10
New Yesterday: 27
Overall: 231722

People Online:
Visitors: 128
Members: 1
Total: 129 .



Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

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.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Change Management: Classification
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Change Management: Classification

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

Joined: Aug 26, 2004
Posts: 1

PostPosted: Thu Dec 09, 2004 7:35 pm    Post subject: Change Management: Classification Reply with quote

I'm having troubles in the classification of a Request for Change. In ITIL there are 2 points of attention:
1. priority which is made of urgence and impact
2. category which is made of impact of resources.

1. Is that the same method on incidentmanagement? Urgence: if a employee could work or not and impact what impact on IT-network?

2. Category: what kind of categorys are we talking about?

Can somebody give samples of how a RfC could be classified with a simple example?

Sorry for my poor english BTW!
Back to top
View user's profile
Senior Itiler

Joined: Oct 06, 2004
Posts: 77
Location: Bloomington, IL

PostPosted: Fri Dec 10, 2004 1:29 am    Post subject: Reply with quote

Buenos Dias!

Yes, the impact, priortiy and urgency definitions should be used consistently across all processes to facilitate communications and increased quality.

Impact=effect on the business (sometimes stated by # of users/customers affected)
Urgency=the necessity of getting the service restored (single network printer down vs entire network segment down)

Impact + Urgency=Priority (overall speed at which the service needs to be restored or the RFC needs to be implemented)

RFC Categories=amount of resources needed to implement the change (minor, major, significant, extreme are all terms that might be used here)

Priority(Impact +Urgency)+Category(Resources)=part of the calculation of the risk of implementing the RFC

Much of this can be found in the Service Support book, but some of this is my interpretation of Best Practices.

Hope this gives you a start!

Back to top
View user's profile Send e-mail MSN 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

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.