Cause and Resolution Codes

[mitter]

Hi Everyone,

Does anyone have a list of Incident Resolution and Cause codes that they would like to share?

Thanks
Mitter

[UKVIKING]

Sure

Incident closure codes are as follows

AA, AB, AC...

BK01, BJ02...

Incident closure codes can be anything you want them to be .. however, they need to relate to a phrase or condition that is agreed

Causes
User Error
Software error
hardware error
Design flaw
Performance
Fault

Closure code

Closed w/o action
User Requested
User Error
Restart Service
Restart system
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[UrgentJensen]

You can go one further than that too if you want. I have in the past also used 'resolution work type' categories e.g. 'replaced disk', 'update AD for customer' etc.

These can be useful when you're trying to work out what skills you need most and also understand call lengths and so on.

Be warned though, you can get lured into having lots and lots of these codes and they end up frustrating the team and take quite a bit of administration if you define every type of activity, so keep them broad to begin with. Make sure you really need them first!

Cheers,

Urgent.

[Timo]

Start with identifying what aspects of service it is important/required for you to report on. You would get a better picture of what codes will be required then.

[iJohnnyJ]

Here is what our team is using (high level). Like UJ posted, be warned you can have lots and lots of these codes. For instance under the Root Cause Category - Change, I have different sub-categories that give more detail. Just make sure the information you use is useful to your processes and company culture. Let me know if you need more information.

Incident Resolution:
Cancelled by requestor
Document published
Duplicate incident
Fixed problem
Inaccurate information - unable to process
Incomplete information - unable to process
No problem found
Referred to other resource
Request completed
Requested access already exists
Training issue
Unable to duplicate

Root Cause Category:
Change
Environment
Hardware
Link
Network
Process
Software
Vendor/Partner

[mitter]

Thanks for the information..

The type of codes that I was thinking about were..

Cause Code:
Server Unavailable

Resolution Code:
Reboot/Recycled

I was told that there should be lots of examples on the internet, however I have not had much luck in my search

[Mark-OLoughlin]

Hi,

remember as always codes are just a means for you to get information out of the system. Codes should be selected that will provide you with information that you need and is usefull to you.

With this in mind, and some of the examples that are given to you, you should be able to figure out some basic codes to begin with.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant