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: HErlikily
New Today: 120
New Yesterday: 176
Overall: 131365

People Online:
Visitors: 58
Members: 3
Total: 61 .

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

Categories of Change

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


Joined: Nov 01, 2007
Posts: 1

PostPosted: Fri Nov 02, 2007 12:50 am    Post subject: Categories of Change Reply with quote

Does anyone have a list/description for categories of change currently used at your place of employment. Also, is there another term to used besides 'Normal Change' .
Back to top
View user's profile
JoePearson
Senior Itiler


Joined: Oct 13, 2006
Posts: 116
Location: South Africa

PostPosted: Fri Nov 02, 2007 5:01 am    Post subject: Reply with quote

Normal Change, Standard Change and Emergency Change. Any other categories I've seen used generally serve different purposes like differentiating the origin or the organisational approval level. The category should only be used to identify the process the change will follow.

But you could have good reasons for a different set.
Back to top
View user's profile Visit poster's website
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Mon Nov 19, 2007 10:29 pm    Post subject: Reply with quote

We use Basic Change instead of Normal Change, with the rest as is, but it is the same in the end.

Regards

Ed
Back to top
View user's profile
Mark-OLoughlin
Senior Itiler


Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Mon Nov 19, 2007 11:02 pm    Post subject: Reply with quote

Hi,

I keep it simple and use Nomal or Emergency. Thi sallows me to quickly get the metric normal vs emergency changes which is an important metric to report.

I do add a provision for pre-approved changes with the following logic. preapproved changes are classed as normal changes and are approved in the Normal count. However it is importat to report and track preapproved changes so they can be catagorised under a sub catrgoty or by using a checkbox or similar field on the CR form.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
asrilrm
Senior Itiler


Joined: Oct 07, 2007
Posts: 441
Location: Jakarta, INA

PostPosted: Tue Nov 20, 2007 10:47 am    Post subject: Reply with quote

Sorry I'm a little bit lost.

Is there any difference between change type and change category?
From one reference I've read
- Emergency, RFC that has to be served immediately
- Basic, RFC that was never been done before
- Standard (or pre-approved?), RFC that has happened before

From another reference I've also read
- Urgent (probably the same as emergency)
- Major
- Significant
- Minor

In a sample IT Change Management Policies and Procedures Guide from Evergreen Systems, Inc. the change category is completely different and it's categorized (and sub-categorized) as
- hardware
- software
- configuration
- etc.
See [Edited: No links pleasse]
Back to top
View user's profile
Ed
Senior Itiler


Joined: Feb 28, 2006
Posts: 411
Location: Coventry, England

PostPosted: Tue Nov 20, 2007 6:13 pm    Post subject: Reply with quote

asrilrm wrote:
Sorry I'm a little bit lost.

Is there any difference between change type and change category?
From one reference I've read
- Emergency, RFC that has to be served immediately
- Basic, RFC that was never been done before
- Standard (or pre-approved?), RFC that has happened before

From another reference I've also read
- Urgent (probably the same as emergency)
- Major
- Significant
- Minor

In a sample IT Change Management Policies and Procedures Guide from Evergreen Systems, Inc. the change category is completely different and it's categorized (and sub-categorized) as
- hardware
- software
- configuration
- etc.


Hi Asrilrm

In the Blue Book (V2)

Example types are given as Basic (interchangable with Normal), Standard & Emergency - Basic is an ad-hoc change (a one-off), Standard Changes are repeatable (able to be proceduralised) and are pre-approved, and an Emergency change needs to be done now

Example categories are based on impact - Minor , Significant & Major

Example priorities are low, medium high, Immediate(interchangable with urgent)

So a Change with minor impact, with a need to be done now, that has never been done before and is an ad-hoc change is a basic-minor, whereas a change with significant impact, without any great urgency, that has never been done before and is an ad-hoc change is a basic-significant.

Many people mix impact and priority and forget that urgent is a priority, not an impact.

I hope this helps

Regards

Ed
Back to top
View user's profile
UKVIKING
Senior Itiler


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

PostPosted: Tue Nov 20, 2007 6:52 pm    Post subject: Reply with quote

Folks,

I find that the following helps me when I see categories fo change

Non Time Based change or Fault Fixes

Emergency Changes

These changes need to be done now so that service is restored. The approval process is streamlined and so is the creation process

There may be little chance of testing and change has no guarentee of success

Time based changes

everything else

from the urgent, immediate to the standard and planned

Time is required to assess the impact and risk of the change
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter
Back to top
View user's profile
Skinnera
Senior Itiler


Joined: May 07, 2005
Posts: 121
Location: UK

PostPosted: Fri Jan 04, 2008 7:15 pm    Post subject: Reply with quote

Fault = to resolve an ongoing Incident Case
Problem = to resolve an outstanding Problem Case
Emergency = to prevent an imminent service outage where no Incident Case currently exists (ie a threshold has been breached but service is as yet unaffecetd)
Planned = normal Change
Standard = Low Risk, Low Impact, agreed implementation methodology, descriptions, etc, history of success, does not conflict with anything
Templated = as above but not necessarily Low Risk or Impact, and may conflict with other work (which of cousre is detailed).
Back to top
View user's profile Send e-mail
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.