We use it for incident management mostly, though we also try to use it for problem management, but most of the time we use it for managing and resolving incidents.
The most valuable feature for me is the ability to make workflows. We haven't experienced that whole functionality, because I'm based in Lima, Peru, while our headquarters is in Colombia, where the administration of this solution is handled. We have not been customizing this tool here in Lima, but the workflow is very important. Other features that are also important include configuration management (configuration management database) and the knowledge base (recorded solutions function).
I like this solution's interface because it's user-friendly and works well on the cloud.
This solution is good because it's on the cloud, so customers are told ahead of time if there's scheduled maintenance. We receive emails prior to the maintenance period.
The additional feature I'd like to see in the next release is related to self-service on the user side. I have this new environment of users at home and making them independent would be a good point to enforce. Improving the knowledge base also goes along with that.
I've been using it for approximately one year.
I find this solution stable.
The scalability of this solution is good.
I haven't had the chance to contact technical support. Maybe the person in our Colombia headquarters who worked with the reseller was able to contact support, but I'm not sure if the support was from the reseller or from the ManageEngine ServiceDesk Plus support team.
The setup was easy. It's common to have some mistakes for all tools. Loading your users and loading your configuration items were not difficult.
This was managed by our Colombia headquarters, but I can tell by the communication we received that deployment was through a third party: the reseller.
We deployed this solution on the cloud.
For pricing, I'm not on the negotiation team. We only received the product. Our headquarters in Colombia bought all the licenses. I can't tell you whether it's cheap, or whether it's expensive, or the cost-benefit. I have no information about that.
I can't tell you an area or room for improvement, though it's a good question because we only use one or two in asset management and operations management. We haven't tried it in other departments or areas. For example, I don't know if it works well for managing and monitoring service-level agreements. I can't tell you exactly based on my experience with this solution.
Deployment of this solution took no longer than two days.
The number of people using this solution, for our technical operators it's a group of 10, while the users in our database are more than 150. I was only thinking about the number of users in my country, here in Peru, but the total number of users is approximately 400 users, because we use it in Chile and Colombia, aside from Peru. In all of the three countries, all of our users use the same solution. In terms of increasing the usage, maybe in some other models, but in-licenses, I'm sure because we are covering all the users in the three countries.
My advice to people thinking of implementing this product: It's a good product. We found good experiences and reviews about it on the internet, in terms of how easy it is to use and its quality. I will tell people that it's a good product to try. I have also tried other tools, but this product makes a difference. It's a good one. It's the best one for me.
My rating for this solution is a nine out of ten.
Useful review. FEW queries -
a) When you talk about growing to 1000 cases, do you mean 1000 incidents/requests per day?
b) Are you using the CMDB and how are you populating it if yes? What discovery mechanism is being used?
Regards,
Jeevan