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.
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.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
Posted: Wed Apr 18, 2007 6:09 pm Post subject: Service Request vs Incident
Hi,
We are in process of creating service catalog. We have a Help Desk tool in production with Incident Type (eg: Hardware, Software, Application etc) and Sub Type (eg: Application/App01, App02 etc..). and then description field to enter the incident details.
new to ITIL, so lil confusion that where do i keep service catalog and how.
For eg: I received a call from user for some desktop problem.. i classfied (Hardware/Desktop PC/Problem desciption)
I received a request for new ip telephone.. how do i classify?.. do i need to use the type/subtype/description? or we maintain separate catalog for Services (service catalog) and Incidents.. When it is service request use service catalog and when it is incident use the other catalog
Joined: Sep 16, 2006 Posts: 3590 Location: London, UK
Posted: Wed Apr 18, 2007 10:46 pm Post subject:
The service catelogue should be the list of services that you provide to your customers/users.
The definitions as to the classifcations with the Service desk tool should link to what kind of services you provide
For example
You provide IP Telephony, Email, Network connectivity, Web (internet and intranet access), Desktop Applications - general, Desktop Application - specialized
For IP Telephony - what are the sub services you provide - software, hardware, configuration etc
When a person who consumes your IP telephony service contacts the SD, treat the IP phone like a PC. so the Incident would be classified asHardware - IP Phone or Software - IP Phone; Connectivity, etc _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
The Service center handles many different types of service requests. all requests, whether for routine service or for problem resolution, are considered service requests. To organize, the service requests are categorized using service catalog
Joined: Sep 16, 2006 Posts: 3590 Location: London, UK
Posted: Fri Apr 20, 2007 8:45 pm Post subject:
You are confusing the Service Catelogue with the service toll fields.
THe Service Catelogue should be the list of services that you provide to your customers/users. This document (for want of a better term) should be created using the SLA creation life cycle and the Service Level Management process to develop it
There shoudl be a definitive SC for the services you provide so that if you get new customers/users/ you can say .. here is our services, hours sla, etc
The Service Desk tool would have fields to identify what kind of ticket is being raised. Most tools have fields for the initial raising of the call, the classification of the call, etc. then a closing field value for the call as well
for ex
A user calls in with an issue, their network connectivity is down because they get to a web site.
The call is raised as either - hardware issue, software issue or network issue. Priority may be medium. There may be a subcategory for the ticket classification related to the h/w s/w etc issue
When the work is assigned to the resolving group, hey determine the site is block and close the call. They would put a closure reason - which would match the result.
If the SD tool can be linked to services, then if the service is Intranet,/Internet, then when you run reports you can see how many h/w , s/w etc issues against what service you are tracking
doe sthis make better sense _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
Joined: Sep 21, 2006 Posts: 20 Location: Great Lakes, North America
Posted: Sat Apr 21, 2007 5:41 am Post subject:
Another way to organize Catalogue vs. Non-Catalogue items is to include standard MACDs (Moves, Adds, Changes, Decommissions) in a Menu/Catalogue that is published/known. These MACDs are processed and provisioned with either a set cost to the Service Requesting organization or are included as part of normalized Service.
Any Service Request that does not align with the MACDs identified in the Catalogue are subsequently non-catalogue requests and may require the engagement of Account/Project/Engineering/etc. management or teams to process a Request for Quotation to be presented to the person or organization requesting the service.
Joined: Jan 01, 2006 Posts: 500 Location: New Jersey
Posted: Thu Apr 26, 2007 11:04 am Post subject:
Hello Mahen,
The answer to this is to classify Service Requests as Service Requests and Incidents as Incidents. ITIL V3 is coming out and has clearly broken the two up into separate and distinct categories.
My Best,
Frank Guerino
CEO & Founder
TraverseIT
On-Demant ITIL _________________ [Edited by Admin to remove link]
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