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: paulojorgelima
New Today: 28
New Yesterday: 106
Overall: 149904

People Online:
Visitors: 44
Members: 3
Total: 47 .

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 - Problem Management Documentation
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Problem Management Documentation

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


Joined: Jan 10, 2007
Posts: 4

PostPosted: Tue Jan 16, 2007 10:46 pm    Post subject: Problem Management Documentation Reply with quote

Our problem management Severity One documentation is currently over 20 pages. I have been requested to create an Executive Summary in hopes that we can get people to read and use the documentation. In the currently documentation there is alot of duplication. We will have information in verbal and graphical. Which is more effective in this type of document?

Question
Back to top
View user's profile
m_croon
Senior Itiler


Joined: Aug 11, 2006
Posts: 262
Location: Netherlands

PostPosted: Tue Jan 16, 2007 11:35 pm    Post subject: Reply with quote

Hi Curby,

Allow me to make a little guess: have you made a distinction in sev1 events regarding different platforms (Wintel/Ux) / services / clients? Is there any possibility you can decrease the number of pages by going for a more generic approach?

In my experience, a combination of graphs and text works best. Graphs never extending the size of 1 page.


Michiel
Back to top
View user's profile Visit poster's website
Fabien
Senior Itiler


Joined: Sep 27, 2005
Posts: 207

PostPosted: Wed Jan 17, 2007 7:40 am    Post subject: Reply with quote

Michiel is pointing out an important thing here. Your Sev1 doc is something that should be digested by anyone who could come across one, which means it must be lean, efficient, and take into account that people hate reading... Reduce to bullet points only, use graphs and diagrams, make it one 4' by 3' poster if necessary.
_________________
BR,
Fabien Papleux

Accenture
Technology Consulting | Service Excellence
Red Badge Certified

Twitter @itilgeek
Back to top
View user's profile Send e-mail Visit poster's website MSN Messenger
Globis
Itiler


Joined: Apr 17, 2007
Posts: 36
Location: Cape Town

PostPosted: Thu May 03, 2007 1:16 am    Post subject: Reply with quote

I'm a little unsure of what you're refering to. Do you mean the severity (priority) rating applied to an incident in incident management, or do you mean the severity rating of a problem after carrying out e.g. Pain Value Analysis?

If you did mean problem severities, then mirror the way you define incident severities. After all the way you handle a problem is driven in the same way as you handle an incident, i.e. the effect on the business.

If you meant incident severities, and if Michiel is correct, i.e. your incident severities are differently defined per service, you are on the road to disaster. Your service desk will never cope effectively at supporting more than a few services. Documentation will become too detailed to be useful (as you've found out), and therefore redundant. Processes will be confusing and hard to carry out accurately, especially in a pressured environment such as the Service Desk.

Define one set of Severities (or priorities according to ITIL, although personally I think severity is a much better description), and apply them to all services.

These should be described in terms of impact to the service (business), and describe things like handling process, target resolution time, escalation path, reporting required etc.

No more than one A4 page should be required per severity, and there is no need for more than 4, maybe 5 severities.

For example:

    Severity: One (aka Critical)
    Impact: Total loss of service, business severely affected
    Target Resolution time: 1 hour
    Escalation path: Service Manager -> CIO -> CEO
    Reporting: Update every 30 minutes to requestor
    Process: ** short generic description of handling process + flow chart**

Each service will be restored differently, but those details do not need to be reflected in the documentation for severities.

This is equally valid for problem severities, certainly the rating and impact should be the same. Resolution time, Reporting, escalation path and process will be different as the driver here is to find the root causes and fix them, rather than get the service restored ASAP.

Dave
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.