The five ITIL books can be obtained directly from the publisher's website: HERE
Or as downloadable PDFs:
Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
Service related resources
Service Level Agreement
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.
Select Interface Language:
Please contact us via the feedback page to discuss advertising rates.
The Itil Community Forum: Forums
ITIL :: View topic - Incident Classification, Notifications Quandry
wireed Newbie Joined: Jun 10, 2006 Posts: 6
Posted: Tue Dec 19, 2006 4:20 am Post subject: Incident Classification, Notifications Quandry
Issue is we are struggling to revampour ticketing systems towards ITIL. Issue becomes complicated as you ave to have a base and you can't totally cstomize for every device in a network
1) classifying the incidents, notifications and escalations. This get complicated when you are an outsourcer. We want to propely alert of an issue, but what is reasonable when notifying?
2) What is a reasonable timeline for querying the client on what's going on, i.e., status, closing info etc.
Especially difficult when the end user does not respond, do you keep ping away, quit, close the ticket?
Seems like a never ending battle that no one wins!!
UKVIKING Senior Itiler Joined: Sep 16, 2006 Posts: 3544 Location: London, UK
Posted: Tue Dec 19, 2006 6:46 am Post subject:
If you are a outsource bidy providing support for one of the processes, you should hodl regular meetings to discuss ticket flow
to get a policy/process set up for dealing with the unanswerable _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
Sen Newbie Joined: Dec 18, 2006 Posts: 2
Posted: Tue Dec 19, 2006 6:56 am Post subject:
1) You need to 1st have proper monitoring in place and with knowledge of kind of alters set you can define the sev of an issue /alert. you can always notify based on critical ones and cover them in SLA's
If the environment is supported or handled by a Vendor, Have frequent meetings
2) The resonable time you be based on the business requirements, The thing I follow is wait for 2 days with 3-4 times reminder to user, if user not responding close the ticket.
All times are GMT + 10 Hours
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
Logos/trademarks property of respective owner. Comments property of poster. Rest © 2004 Itil Community for Service Management & Foundation Certification. SV Site source (c)2003, and is Free Software under the GNU / GPL . All Rights Are Reserved.