To register for an Internet.com membership to receive newsletters and white papers, use the Register button ABOVE.
To participate in the message forums BELOW, click here
The other day I was asked to research what properties a Service Management Tool (SMT) should have. Sad to say, I'm new in this area. I only have some experience as a Service Desk worker. But that is long past.
I can imagine that with the SMT it should be easy to:
- add a new customer with it's particular Service Level Agreement (SLA).
- track a problem of that customer where the SMT will control the problem against the SLA.
As each customer probably will have its particular brand of SLA you can imagine that it is important to be flexible in entering the SLA in the SMT. Depending on the type of problem you might not want to solve the problem directly in favour for more pressing problems. But at the same time you do not want to wait past the agreed upon time frame to solve the problem.
This is one scenario you can use to look at the capabilities of a SMT. What would you consider important in a SMT?
Define a SMT better. "Service Management" is a very broad term. Do they mean a Service Support tool? If so then my checklist would start with
- service desk functionality
- incident, request, problem, change, release, config, knowledge and service level management functionality
- incident, request, problem and change "tickets"
- users, customers, SLAs, assets and services in same database as the tickets, all linked. This is as near as you need to get to "CMDB"
- uses ITIL terminology
Last edited by The Skeptic; 06-19-2008 at 04:51 AM.
My company is implementing BMC Remedy which includes all kinds of IT service management modules such as incident management, problem management, change management, release management, asset management, etc.
It must be able to support your Service Management process, be supportable, be easily customizable, and fit within your company's budget.
It seems to me that you either aren't sure of your processes, or perhaps they aren't yet defined by your company. That should be done first before investing in a tool that may or may not fit your processes.
"you either aren't sure of your processes, or perhaps they aren't yet defined by your company. That should be done first before investing in a tool that may or may not fit your processes" Amen brother. People Process Technology (or Things), in that order. And not the reverse: technology does not fix process
It must be able to support your Service Management process, be supportable, be easily customizable, and fit within your company's budget.
It seems to me that you either aren't sure of your processes, or perhaps they aren't yet defined by your company. That should be done first before investing in a tool that may or may not fit your processes.
Excuse me, can you throw in any names which comply the characteristics?
And what is the least expensive product that is trustworthy?
The price goes with features.
If want all the features listed below you might try ManageEngine ServiceDesk Plus
Quote:
Originally Posted by The Skeptic
- service desk functionality
- incident, request, problem, change, release, config, knowledge and service level management functionality
- incident, request, problem and change "tickets"
- users, customers, SLAs, assets and services in same database as the tickets, all linked. This is as near as you need to get to "CMDB"
- uses ITIL terminology
If it is too fancy you might try Hardware Inspector or ipi.helpdesk which have a little features and less expensive.
Help with choosing Service Management Tool
Linear Mode
