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.
The Itil Community Forum: Forums
ITIL :: View topic - Same Category for multi-departments and self-Service
Posted: Tue May 01, 2007 12:14 am Post subject: Same Category for multi-departments and self-Service
Hi all,
It is logical to keep Category simple for self-service but we have many departments have their own Intranet. If we list all departments then the list will be long for users to identify. What do you think is best?
--------------
Web Application/Intranet
(Service Desk has to assign it to the right department & reporting may not show how many ticket each department has with Intranet issue)
-- or ------
Web Application/Intranet/Payroll Department
Web Application/Intranet/Billing Department
Web Application/Intranet/Porcurment Department
.............
(tickets can be auto-assigned to the appropriate dept directly)
Joined: Jan 12, 2007 Posts: 48 Location: Warsaw, Poland
Posted: Mon May 07, 2007 7:49 pm Post subject:
If every department uses it's own Intranet, then you probably will be able to get information about the department from other source, like the caller's ID linked to HR data. Then additional info in category is redundant.
If you are not able to get this information from other source, then you need to find out if you need this information or not. The answer is in your SLA(s).
If the users use the Intranet of other departments, then you have to ask yourself if every Intranet is a different Service. The answer is in your Service Catalogue. _________________ Krzysztof (Chris) Baczkiewicz
IT Standards Support
Eracent
Perhaps your best option would be to try a pilot study with some "super users" to see what works the best.
Imposing a structure on your user base might well be an unwelcome action, whereas a pilot allows for an inclusive approach which will support user buy-in.
Analyse your contacts to see where the most active users are, both by service and department, build your pilot accordingly. _________________ Helen Morris
ISEB Accredited ITIL Trainer & Consultant
ISO 20K accredited Trainer & Consultant
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