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: LatashiaDA
New Today: 15
New Yesterday: 37
Overall: 231700

People Online:
Visitors: 127
Members: 0
Total: 127



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 - One or multiple Requests
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

One or multiple Requests

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

Joined: Mar 27, 2008
Posts: 1

PostPosted: Thu Mar 27, 2008 6:34 pm    Post subject: One or multiple Requests Reply with quote

When I had my first ITIL training, there was not clear definition what is Request Management. With my little experience of ITIL, I would like to hear some comments, how you work on Request Management and especially on this situation.

Service Desk receives a request for a new user account creation. SD's tasks include creation of many service accounts, so should there be only one request where all service accounts are logged in for one user OR should SD create request per service account needed for one user?

one request which has information that network account has been created, mail has been created, internet access has been created


multiple request for one person; one request for network account, second for mail creation, third for internet access etc.
Back to top
View user's profile
Senior Itiler

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

PostPosted: Thu Mar 27, 2008 7:35 pm    Post subject: Reply with quote

Hi sarkku,

the answer lies in what you want to do with the data you record.

For example, if you need to know the frequency of requests for a particular service, then it might be easier to have that if you have set up separate requests for each service.

On the other hand you could collect that level of detail in records generated by the setup process.

I would suggest that you do not want to confuse your users with a myriad of discrete responses for the separate services; if you do break it up into multiple requests, you should keep them clearly linked so that you can talk to the users about their whole request at once.

"Mr. Smith, I'm calling about your request for internet access. It is now set up for you."
"But I asked for email as well?"
"I'm sure someone is dealing with it also" -No! No!
"That's right, I see it here. You will get a call as soon as it is ready" - better
"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
Senior Itiler

Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Thu Mar 27, 2008 7:48 pm    Post subject: Reply with quote


yuo need to think about workflow and how to use a workflow that is consistent with what you want.

I have seen an organisation use 1 ticket for requestion multiple accounts - the user jusy has to check one ticket for updates and the desk have less admin - however the SLA was always blown on these as the ticket passed from resolver group to resolver group to get done - imagine the time ti takes to get 4 accounts set up from one ticket.

Another org recognised this issue and were aboe to spawn seperate tickets from the master call the the user logged so each of the 4 requests hit each resolver group straight away without delay and had a better chance of being in SLA.

Sit down and work out the various workflows, identify the pros and cons - decide one and then test it out with your SM tool.
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile

Joined: Apr 04, 2008
Posts: 30

PostPosted: Sat Apr 05, 2008 2:49 am    Post subject: Reply with quote

This is why I like tools with "work orders" or "task" functionality.

However you cut it, on the IT side, to the client its ONE request. To that end I like to keep the quantity of whatever record interfaces with the client to one. Hopefully your tool is flexible and advanced enough at that point to easily break the work down into its distinct "chunks" and forward to the appropriate work groups.
Back to top
View user's profile
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.