Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
· Home
· Content
· Feedback
· News
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: ogalijid
New Today: 16
New Yesterday: 40
Overall: 231768

People Online:
Visitors: 140
Members: 2
Total: 142 .



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.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

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 - Service Requests - theory vs. reality
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Service Requests - theory vs. reality

Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message
Senior Itiler

Joined: May 25, 2007
Posts: 105
Location: USA

PostPosted: Sat Jul 19, 2008 8:45 am    Post subject: Service Requests - theory vs. reality Reply with quote

In theory ITIL Service Requests are basically any request for service.

I've read the discussion from 2005 regarding Service Requests and came away with some good fodder. However, I'd like to ask a simple question.

In reality, which service requests are really not practical to run through the Service Desk?

Our draft IM plan currently lists the following examples.
Requests for information
Procurement requests
Batch job requests for a specific purpose
Service extension requests
Password resets
Operational queries and processing
Change Requests

Requests for information and password resets and such are obvious service requests - as are requests for standard changes. But I'm a bit leery of running procurement requests and such through our Service Desk.

I'm in a data center. Our customers talk to their end users; we talk to our customers' programmers, application administrators, project managers, etc.

Our customers aren't going to ask, "Can we add a couple more gigs of storage to our application?" because if they needed it, our admins would work out the details and put in the RFC. But our customers have said, "We're streaming live video on our website between 9-10 Monday morning, can the NOC please monitor the webservers more closely than usual."

Thanks! --rpmason
Back to top
View user's profile
Senior Itiler

Joined: Oct 07, 2007
Posts: 441
Location: Jakarta, INA

PostPosted: Sat Jul 19, 2008 6:13 pm    Post subject: Reply with quote


To your list:
- Request for Information: Service Desk
- Procurement requests: Procurement Team internally; SLM or CRM externally
- Batch job requests: Service Desk
- Service extension requests: SLM
- Password resets: Service Desk
- Operational queries and processing: Service Desk
- Change requests: Change Management Team internally; SLM or CRM externally

But those are what apply in my company. Might not be the same for others.

Back to top
View user's profile
Senior Itiler

Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh

PostPosted: Sat Jul 19, 2008 7:49 pm    Post subject: Reply with quote

Hi rpmason,

in reality all of your list is appropriate to go through the service desk - or not depending on how you operate.

First benefit: you have one central point at which to track progress against commitment. Therefore you have a complete picture in one place of what any customer is waiting for or might be agitated about.

Second benefit: having a consistent central record of all requests (and their outcomes) that come from your users and customers, helps with the analysis, e.g., for service improvement or service re-alignment programs.

The way to make it work is by passing the request promptly to the right group (e.g. procurement, server admin.) and let them manage and perform the process. They can close the request on your service desk when it has been delivered.

If you have customers and users talking directly to different support and service units it is much more difficult to manage the overall customer relationships. The danger areas include customer authority, prioritizing of work (resource management), duplication, inconsistent delivery. Rigorous procedures are needed to minimize these risks.
"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
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk 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

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.