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: AHoman
New Today: 2
New Yesterday: 161
Overall: 131061

People Online:
Visitors: 61
Members: 5
Total: 66 .

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 - Incident fix/closure codes
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Incident fix/closure codes

 
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message
fandango
Newbie
Newbie


Joined: Mar 21, 2006
Posts: 3

PostPosted: Wed Mar 22, 2006 12:11 am    Post subject: Incident fix/closure codes Reply with quote

Incident fix/closure codes

I suspect that the answer to this question may read something like "depends on the information requirements of your organisation". From my ITIL novice perspective, a given incident may have a symptom, a root cause and a fix. Is there a hard and fast ITIL guideline for whether a closure code reflects a root cause or fix? In my organisation closure codes can reflect either. For example, let us imagine the following incident:

Symptom: Slow responses from server
Root Cause: File System 98% full. Archive file housekeeping not up to date
Fix: Perform housekeeping on archived files

Now, there exists the following two combinations of closure codes:

Combination 1

Code 1: Server
Code 2: Operating System
Code 3: File system full

Combination 2

Code 1: Server
Code 2: Operating System
Code 3: Housekeeping

Combination 1 reflects the root cause and Combination 2 refelcts the fix. Now, which combination will be provide the most useful management information? I suppose it may be useful to know how many File System Full instances there have been and how many issues have been solved by housekeeping.

To summarise my questions are:

1) Is there a rigid ITIL guideline for whether a closure code reflects a root cause or fix?
2) Or, is there a model or set of guidelines that can offer guideance to those designing closure codes and/or for service desk analysts closing off incidents?
Back to top
View user's profile
itilimp
Senior Itiler


Joined: Jan 20, 2006
Posts: 172
Location: England

PostPosted: Wed Mar 22, 2006 4:50 am    Post subject: Reply with quote

Welcome to the black art that is categorisation. Although there is a little guidance in the ITIL books on this (and I mean a little!) I think most people on this forum would agree that it isn't quite right and needs to be services based. There are some other threads on this forum if you have a search, although they mainly deal with opening call categories rather than closure.

As for root or fix, it depends on what is most important to you and whether you are doing this to feed into problem management or not. Do you want to be able to say we had x number of calls where the root cause was y or we performed x number of fixes of type z? Personally I'd imagine the former as this would help inform problem management which root cause needs time allocated to eliminating it.
Back to top
View user's profile Visit poster's website
Oz
Newbie
Newbie


Joined: Dec 09, 2005
Posts: 8

PostPosted: Sat Mar 25, 2006 1:34 pm    Post subject: Reply with quote

Hopefully one can eliminate the root cause after all isn't that the idea ???
But that would not eliminate the house keeping.
So the answer would be root cause and once the root cause is eliminated you wont get any more calls because the house keeping is being done.
_________________
Oz
Back to top
View user's profile Visit poster's website
ITILbit
Newbie
Newbie


Joined: Mar 14, 2008
Posts: 6

PostPosted: Thu Mar 20, 2008 8:33 pm    Post subject: Reply with quote

Is there a comon list of possible closure or resolution codes that can be used?

Surely a generic list for a general IT infrstructure should exist somewhere?
Back to top
View user's profile
UKVIKING
Senior Itiler


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

PostPosted: Thu Mar 20, 2008 9:14 pm    Post subject: Reply with quote

no and dont call us shirley

we are surly, surely you knew that
_________________
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 -> The ITIL Service Desk 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.