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: RChisolm
New Today: 48
New Yesterday: 66
Overall: 142267

People Online:
Visitors: 54
Members: 0
Total: 54

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 - Recording Known Error for Service Desk usage
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Recording Known Error for Service Desk usage

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


Joined: Jan 21, 2010
Posts: 9

PostPosted: Thu May 05, 2011 11:44 pm    Post subject: Recording Known Error for Service Desk usage Reply with quote

Our organization isn't very mature in terms of the ITIL processes. I've been tasked with creating the KEDB within the tool that the Service Desk utlizes (it has appropriate Problem functionality).

One of my biggest challenges is as a Problem manager, I record the Known error with the title description of the actual known error thrown as oppose to a generic description.

Service Desk lacks the maturity to understand this importance and when they receive incidents they do not search the KEDB, they create an incident (I consider this a maturity/training issue). Additionally, in those rare instances when they do search the KEDB they search the generic description.

The question, is it best to use a hybrid approach in creating the KEDB or keep with best practice and log known errors by the actual error message and not generic title?

I want to encourage Service Desk to search KEDB first, but not make it so challenging that they abandon searching long strings of errors.

Thanks,

PS. Our tool is not optimally configured which is another problem, but management focus is not on fixing this despite the obvious.
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Fri May 06, 2011 3:00 am    Post subject: Reply with quote

May I suggest:

1. the language (terminology) used has to be familiar to the service desk staff.

2. incidents can be reported in many different ways by users even when they are about exactly the same thing.

3. the terminology used has to accommodate this as well.

4. It is dangerous to impose specialist jargon beyond the normal experience of those you want to use the system.

5. I'm not aware that it is "best practice and log known errors by the actual error message" although it would certainly be a good idea to record the actual error message somewhere in the system.

6. perhaps the key is to be able to search on symptoms.

I hesitate to offer anything more specific since I am ignorant of the capabilities of your software, but could I point out that users can report, e.g., "printer not working" when the actual issue is a network failure, and they are correct because that is the problem (sorry Twisted Evil ) they see.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Back to top
View user's profile Send e-mail
baloutang
Newbie
Newbie


Joined: Jan 21, 2010
Posts: 9

PostPosted: Fri May 06, 2011 4:04 am    Post subject: Reply with quote

Thank you for clarifying those points. I agree it surrounds terminology.
There may be an opportunity for the tool to have a generic error message that is related to the actual known error.
Either way, you've given me additional things to think about. I appreciate you quick reply!!
Back to top
View user's profile
BorisBear
Senior Itiler


Joined: Mar 10, 2008
Posts: 403
Location: Sunderland

PostPosted: Mon May 09, 2011 6:01 pm    Post subject: Reply with quote

Whenever you have a new Known Error why not issue a briefing to the Service Desk advising them what it is, symptoms, etc, etc, and get some buy in from the Service Desk Management to keep the team appraised of Known Errors......Maybe make it one of their job objectives.
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Problem 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.