Durchschnittliche Bewertung85 Bewertungen
- Gesamt 4 / 5
- Benutzerfreundlichkeit 4 / 5
- Kundenservice 4 / 5
- Funktionen 4 / 5
- Preis-Leistungs-Verhältnis 4 / 5
Angaben zum Hersteller
- Gegründet 1999
Über Remedy ITSM
Comprehensive ITSM solution that helps to simplify the connection between people and information.
Die hilfreichsten Reviews für Remedy ITSM
Bewertet am 26.8.2015
Used it for 3 years in our corporation now and it has been great for tracking change and incidents
Kommentare: Enterprise level, very powerful software which is very easy to use. As of Remedy 7.6x, you can make your own customizations to the application or even create applications of your own with their customized Eclipse tool. While a lot of OOTB features worked very well for us, we still needed the ability to customize and create our own forms and processes or even the ability to perform automation and self-service with other applications. Some items the learning curve is not bad at all and customizations can be added with little to no effort. Whereas others have taken quite a long time to develop and troubleshoot. One such customization which we developed was the ability to have placeholder templates for Change, Incident, Work Order and Tasks where we pass through variables via the SRM and it dynamically generates and populates the ticket with this information. We have full date automation, dynamic Task generation and the ability to dynamically modify the template on the fly based on the answers that the user passes through via SRM. So instead of multiple templates which are served based on "if-then" answers in the Process Definition, we have a single template which then gets massaged based on the user's answers. This customization took a decent amount of time to complete, but it reduced the amount of time of SRM and template rework to almost nothing. Of course with such customization, there are always risks of breaking existing workflow or failure during an upgrade. So when we upgraded fro 7.6.04 to 8.1, it took a solid month of work to check each and every form, active link, filter, etc to make sure that things worked with the new upgrade. But BMC's tools helped reduce both the time and work it took to get the kinks worked out and we had all of our environments upgraded and without the need to call in expensive consultants to assist with it. As with any piece of software, there are always going to be issues. However, we have found that 9.5 out of 10 times we contact BMC for support, their staff is more than knowledgeable and have us up and running again in short order. BMC's Remedy ITSM Suite is a great piece of software and VERY flexible to meet the most demanding of situations. After being a Remedy Administrator for 3 years, I can say without hesitation that it is well worth the price and would be a welcomed addition to any I.T. department.
Bewertet am 2.7.2015
Love Remedy ITSM 8.1.01
Kommentare: I have been a Remedy developer since 1998. I was an early deplorer of 7.6 and 8.0 AND love ITSM 81.01. I deployed 8.1.01 in January 2015. Installing email to use Outlook was missed because the install was not clearly understood. The same happened with Web Services. Correcting these deficits caused an outage shortly after Go Live. Incident, Change, Knowledge, Asset & Release Management are deployed. DMT worked well for the foundation data with one exception - it is no longer possible to import Categorizations as Global; all categorizations are Company specific. SRM deployed quickly using the export/import method; painless and a big win for my customer. Incident, Work Order & Change Templates were created using data mining were included in IOC deployment. I love the People Management Console; it too, was a standard customization I added to previous apps. Multi-tenancy was simple to configure and deploy. While Work Orders are now a stand-alone form, the app is not as well structured as Incident or Change Management, i.e. there is no "Print" button on the WOI:Work Order form. With the ITSM Email Engine & Rules of 8.x, Remedy has nailed it! This used to be a huge development effort that took several months to complete, often delaying application deployment. The incoming email rules are well written and meet most customer needs. We have all of our tickets create Service Requests. We had to add some customizations because when the "Requested For" user is changed, all of the new customer info does not write to the SR completely. This is a big deal when the customer has access to the Request Entry Console because the new customer does not have access to the REQ. The Survey is confined to tickets created using SRDs which does not work for my customer. A custom Survey is in the works because the customer for every resolved Incident must receive a survey solicitation. The TMS:Task form still uses the "Classic" view. It would be nice to have this view updated to match the "Best Practice" view of other ITSM forms. The same for CTM:People. It would be great to have the option of having the last Task close a Work Order or Change Request part of application rules. This is a big issue with customers who always get caught unaware of the behavior.