For us, there are two main features that are most valuable:
- IT Service Management, and
- Service Support
For us, there are two main features that are most valuable:
It holds us accountable for IT services, leading to a reduction in IT service outages.
It's also given us a tight and streamlined management of services and reduction in resource utilization.
It could be improved in the areas of cloud management, documentation, and training.
I've been using it for 10+ years.
We didn't encounter any issues with deployment.
It's been stable for us.
It's scaled for us as needed.
Customer service is good.
Technical Support:Technical support is good.
We didn't use a previous solution.
The initial setup was straightforward.
We used a vendor team for implementation. There was a significant time frame for analysis and design in implementing the solution.
We didn't look at other solutions.
I highly recommend this solution.
We use Remedy as our ITIL solution for our IT department. Currently, we have a few projects starting up, which will also utilize it as a ticket intake system for non-IT as well.
Our Change Management and Incident Management processes have been greatly improved by using Remedy. It has allowed us to standardize and streamline both processes immensely.
Currently, the Service Catalog has the most value to it. Mainly, because we are able to offer IT functionality to non-IT people. This also helps to cut down calls and emails to the Service Desk by routing things automatically via the catalog.
We found that there was numerous issues upgrading from 8.1 to 9.1 in that all our licenses were broken for almost a year and a half. We chased down a total of 14 hotfixes, patches, and service packs before things were finally resolved. During that time, said "fixes" also broke other things, so it was quite the sore spot with management for some time.
We understand this occurred mainly because the Dev team rewrote the entire code from scratch to remove the spaghetti code. However, in doing so, they really broke quite a few things which left not only us, but numerous companies, in dire straights for quite some time.
I highly recommend that more QA be done on a product like this, especially after a complete rewrite, to make sure things are working properly. I can't imagine what it was like in version 9.0.
Call logging and escalation features are the most valuable for us because they are easy to use and with them, we can assign a request to a specific person or department.
It made the organization better. We have been able to improve our SLAs because previously no one was assigned to a job and we could ignore it.
It doesn't allow a person logging a call to assign the ticket to a specific department, but only to update it.
I've been using it for seven months in the IT service desk.
No issues with deployment.
There have been no stability issues.
No scalability issue.
The ability to utilise CMDB information is the most valuable feature for us as it helps us to see interlinkages between CIs.
It has improved our issue resolution and change management process.
Desktop client should be an option for heavy users.
We had no issues during the deployment.
We've not experienced any stability issues.
We've had no problem scaling it to our needs.
I've not had to contact technical support.
The initial set-up was straightforward.
We performed the implementation in-house.
Have your business requirements confirmed prior to selecting a vendor.
The ease of installation and configuration is valuable. It's quick to build prototypes and full-fledged, database-based applications.
Product consultants who assist and maintain the product for customers.
It needs to be web based. The product also needs a client native (non web) version re-introduced.
I've been using the AR System for 20 years.
I've had no issues deploying it.
There have been no issues with the stability.
There have been no issues with the scalability.
It's excellent.
Technical Support:It's excellent.
There was no previous solution in place.
The initial setup is partially complex, but reading the install manual ahead of time is recommended to offset the complexity.
We are a consulting firm that assist our customer based in this area.
It has seamless integration with third-party products.
Improved IT service desk and change management functions within the organization.
On the Administration activity to be more user friendly in terms of capturing logs also more features to be included in development activity.
It's been 11 years now.
We had some issues but we have overcome all those.
We had some issues but we have overcome all those.
We had some issues but we have overcome all those.
It's very good.
Technical Support:It's very good.
I've never used any other solution in my career.
The implementation. was easy.
We did it in-house.
Yes.
Yes.
They are quick to respond, but could be a bit more helpful.
BMC Remedy ITSM suite solution was chosen to replace the existing ITSM tool. The existing tool was lagging in functionality and not addressing our business requirements. The Remedy tool was very much aligned to ITIL and had the industry experience for significant number of years. BMC also has very other products which help in achieving better service management.
It takes a long-time to plan and deploy the on-premise solution.
Information Technology Service Management (ITSM) as a service level process use. I use the reporting console to make reports for managers.
Reports have helped us to improve our IT processes. The main benefit is providing the right information to our decision-makers.
From a business point of view, it is important to have a tool that is scalable and has the possibility to modify reports of different indicators. This functionality has improved significantly.
Maybe it could be more simplified and easier to change the reporting point of view, like from a different vendor to another.