BMC Helix ITSM replaces Remedy. It is a broad suite of ITSM, tools with strong integrations to other BMC tools and in-built ITAM. The product is used mainly by global brands and is offered in on-premise and SaaS configurations.
N/A
Cherwell Service Management
Score 7.2 out of 10
N/A
Cherwell Software was founded by the former CEO of FrontRage Solutions and is a full suite of service management tools competing with BMC Remedy, ServiceNow, and IBM SmartCloud.
The licensing was favorable for our company. The setup and development made it easy to implement. We did have a 3rd party assist with requirements gathering and implementation. This allowed us to meet out targets and deliverables. Performance is very seldom an issue. The uptime …
Verified User
Engineer
Chose Cherwell Service Management
Both Remedy & CA were far more complex to implement, enhance and support. The architecture and framework each solution was developed on didn't lend itself to be no-code or low-code like Cherwell, and therefore the ability to expand and utilize either tool on an enterprise-level …
ServiceNow was administrative heavy and required more than one admin. Also expensive for smaller customers. Remedy was scaled more for enterprise customers where we are small to mid-sized. FootPrints - we replaced FootPrints with Cherwell due to a lack of BMC putting any further …
Much more customizable than other products, especially when ran in a self-hosted environment. Cherwell [Service Management] allows for greater flexibility of custom development and integrations to allow for automating tasks that traditional ITSM apps are not well suited for. …
Though there are other competitive products that are more powerful and faster than Cherwell Service Management - we've been using CSM due to the price point.
When I did the shopping for an ITSM solution, I found that ITSM solutions seemed to (at the time, anyway) fall into two rough categories and a small third category. In the first larger category, there were a group of the "out of the box", quick to implement but immature and …
We evaluated numerous applications for our ITSM tool. There are specific reasons why each was eliminated but in a nutshell it mostly came down to the application's ability to meet our current and future support needs and 10-year cost. Cherwell was really the most flexible and …
Large complex organisation, with complex technology that needs to manage Technology Services. It is very flexible and able to manage a large complex environment but the knowledge required to set this up correctly (foundation data and configuration) is the key factor for success. It can integrate with many other systems and tools and integrate data from many sources - whether that be AWS cloud, or an on premises bespoke system. I would not recommend for a Small Organisation without the resources to set up and maintain the underlying foundation data and configuration.
Well suited in an IT environment where you have limited staff. It can be managed by one administrator. Reliability of the SaaS environment has been excellent. Flexibility in developing automated workflows to open, manage, and close Incidents. Change Management due to ability to modify OOB to meet the needs of our staff. Contract Management allowing us to be notified when a contract or license is up for renewal and setting reminders. Integrations are not easy to create and manage.
Integration with monitoring software like SolarWinds. where Remedy can transform notifications to work orders and assign to respective teams.
Detailed Customization capability to fit the exact needs of the organization.
Change management calendar, which integrates change orders from all organization departments and facilitates the scheduling process of project managers.
It can be offered as a cloud-based service, where you don't need to worry about server maintenance or database backup.
Cherwell's email handling automation works flawlessly. The only time that I have ever needed to reset the automation service that drives it is when my own server that houses the small connecting agent has some kind of problem and disconnects us from our hosted Cherwell instance. It just works. Emails to a certain address always result in a new ticket or update to an existing ticket.
Cherwell is literally 100% customization in so many ways that it would be pointless to try to enumerate them. There is a very sizable list of already-created customizations (called "mApps") that you can download and apply to your instance. If you don't like them you can roll them back in seconds. But you can add and configure entire modules using one of these pre-defined, completely free, add-on packages. It's so easy to add features this way that I check the list of available mApps every month or so just to see what functionality I can add.
The interface (ironically). My company has made an attempt to replace the "classic" Remedy interface with some more functional, modern, but Remedy set to a particular look and feel (and consequently, functionality)
The API is hidden from the user: There exists an API for Remedy, that would make my job TONS easier, as I like to perform actions on Remedy in bulk (and therefore - programmatically). Exposing a user API is very much mainstream these days, so Remedy relying on its interface to perform ITIL is very limiting
By extension- the result of Remedy's interface is that it becomes very "click-happy": little buttons, and links stuffed into every corner of the screen, with options API logically together. API is old, but it still feels very rushed.
The primary tool for most of my ITIL operations is: searching. API of searching goes into finding assets, checking in equipment, finding users, tickets, etc. What Remedy could very much benefit from a "Google" -like interface
Cherwell is still the best tool for the job in the market. Even though Ivanti bought them and are trying to convince everyone to move over to Neurons for ITSM, they have stated Cherwell will remain supported indefinitely and have a roadmap for future Cherwell development. Unfortunately, ISM is not as flexible as Cherwell (and the UX is atrocious), hence why many people are sticking with Cherwell (and why many Cherwell customers never purchased ISM originally)
At least Remedy is all contained in a single platform, so the interface is consistent. Also, the most heavily performed functions are generally usable. However, to use some of the more advanced modules can be a bit more cumbersome (such as Change Management and CMDB (Not Including ADDM)). So, overall BMC Remedy ITSM is better than some applications like CA SDM or HP SM, but not quite on par with ServiceNow.
I enjoy the layout and configuration of our Cherwell Service Management instance. It did take me a bit to get used to, as with any new ticketing system, but now that I understand the system more, I thoroughly enjoy it! There are just so many options and the UI is very intuitive.
The browser client is mostly acceptable in terms of performance, but still lacks parity with the rich client. The rich client is not very performant at all. It's built on old architecture and relies heavily on a fast internet connection, good caching and database indexing. There are several unwritten rules with form design (and form arrangement) which most users are not aware of, but can severely impact performance in the rich client. This is where the flexibility of Cherwell can come back to bite you if you step outside the boundaries of these unwritten rules
The support is good in overall resolving the issues and even in the deployment phase. We are able to use it in production without any trained in-house engineer as the support team gets the job done. We can say that experts completed the deployment for us, and now it is functional.
We generally have a good time with Cherwell support, however, there are the few niche cases where I have to explain how Cherwell works to the customer support agent on the other end. A little more product education for tier 1 support could go a long way in helping expedite support requests from SaaS customers.
I didn't partake in the in-person training, but it was available. I preferred the online method instead, which was a great experience. It was nice to have someone available to bounce questions off of and demonstrate how certain functions worked.
The training was great! We got together to review the system, its UI, and how to perform basic functions. Then there was plenty of time to ask questions and test out the system while there was someone available to assist.
Implementation is a breeze. Each time I've implemented it, we had an outsourced vendor overseeing it & assisting where needed. However, Cherwell OOTB is ready to go, and configuring it for LDAP/SAML, etc. for authentication and user-imports is really straight forward. The infrastructure needed for Cherwell is extremely simple too - and installing the server & database takes no more than 20 mins
The decision to select BMC Remedy was made prior to my employment. We did conduct an RFC process for a new ITSM platform and BMC was considered but not selected. We looked at several platforms and ended up choosing Ivanti Service Desk (previously LANDESK) due to the features, ease of customization and price.
Much more customizable than other products, especially when ran in a self-hosted environment. Cherwell [Service Management] allows for greater flexibility of custom development and integrations to allow for automating tasks that traditional ITSM apps are not well suited for. Cherwell [Service Management] gives you the freedom to develop your own objects with minimal licensing costs.
We have never had any major show-stopper issues with Cherwell itself - more so with the infrastructure it sits on. Moving from in-house cloud (on Cherwell's side), to AWS then to Azure has caused multiple problems over the years (some still on-going), however the product has remained fairly stable
As mentioned, they were always great to work with (minus the project management side). My only feedback would be to push back on requirements that don't make sense
When I was in Management discussion calls, and all the team is happy while using BMC Remedy so I don't find any specific negative impact on our organization.
I really enjoy Smart IT as the tool of choice for our incident management team.
Visibility of tickets is key. All support staff users can see tickets in consoles they have access to.
As with any standard ticketing system, it helped decrease the time before first contact with clients.
Our department was always concerned with keeping a low budget, and it was cheaper than most.
My supervisor could easily tell how many resources were being put into each employee, so we had more visibility of our team's capabilities at a given time if we needed to take on something complex.
