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 (discontinued)
Score 4.4 out of 10
N/A
Cherwell Software was a full suite of service management tools competing with BMC Remedy, ServiceNow, and IBM SmartCloud. It was acquired by Ivanti, and has reached EOL.
BMC is the obvious choice for medium—to large companies. With all the functionality included, most of it will be used by more prominent companies. The cost vs. use makes sense for them. For smaller companies, the high cost of license implementation and running costs usually make BMC too expensive. Having a light version for them could increase BMC's market share.
Cherwell [Service Management] is the perfect tool for any organization big or small that needs a solution to handle inter-departmental and customer facing business processes and services. Cherwell offers a complete suite of tools that allow you to maintain a robust service catalog, publicize those services through a web portal, and gives your end users a way to engage with self-help and self-service. In addition, Cherwell's low code architecture makes configuration and customization a breeze without a concern of rendering the system unusable and un-upgradeable. Cherwell is designed for change and we find that we are able to easily manage ever changing workflows with ease. If you are a small organization, you can set up and maintain Cherwell with minimal staff. If you are a large organization with complex business needs, you can leverage Cherwell to solve a wide variety of business problems rapidly.
Remedy is great for housing much of the ITIL process in one System: if you want a complete package with every bell and every whistle, Remedy is for you
Remedy breaks down the functions of ITIL into "consoles": separate areas of the System, that allow one to focus on Changes, Incidents, Assets, etc
The interface is VERY compatible with legacy web browser tech: The last surviving member of the browser wars is still the favorite for remedy users: IE 11
After proper training on setting up the views and servers, Cherwell did a good job separating various department ownership of tickets. Our work views weren't cluttered with irrelevant information.
There is a lot of information that can be embedded into tickets. Such as sub-task assignments that could contain almost the same information as a ticket itself. Lot of customization options.
Custom personal dashboards were nice, once I figured out how to do it. Not everyone wants to see things the same way as other people, and being able to move touch points where you want is always a plus.
Sometimes comments made on a ticket do not generate emails to the technician who owns it, and they will not know there is an update from the customer without checking it
Sometimes I will see an error pop up when copying text but it can easily be closed
Sometimes the time-out window for staying logged in does not appear on top of other applications so I will not know it's logging me out
There has been little experience of downtime. It is well received by end users. The ability to customise it to integrate into existing systems is good. The organisation is realising cost savings through the information it provides. There is continued investment to develop the product by our own staff. In most instances there is not a requirement for client software to run it as a simple web browser will do.
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
Their tech support is top notch. They respond and get back to us, even on lower level incidents and issues, very quickly. It is rare that we deal with a support technician who does not know what they are doing.
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.
We had a 'train-the-trainer' session from Cherwell to some of our users who were unfamiliar with the product, and we had an individual who 'championed' training internally and provided several training classes over the period of a few weeks for new Cherwell users. We also had a team who traveled to remote sites to conduct in-person training there too.
the trainers dont have so much practical experiences. its mostly follow up and reading existing documentation withou own input. of course experiences people are on shore or have no free time. sad truth
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
As I mentioned, as an MSP we are exposed to most ITSM products on the marketplace. On completeness of offering, we find BMC ahead of the rest. The only other comparable product is ServiceNow, and functionality is neck and neck with BMC ahead in ITOM, and with ServiceNow pricing is premium for the branding and marketing
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 development into the product. It was an aging platform with no real future growth.
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
Cherwell is more expensive (of course) compared to the home-grown ITSM solution that we previously used, so it has cost us more in capital outlay and it will continue to do so. But it has drastically reduced the number of end-user issues that have "fallen through the cracks". It makes assistance triage easy because you can customize the prioritizing of tickets by both urgency and priority of your tickets as well as by VIP status of the user.
Our internal end-user satisfaction with the IT department has drastically improved since implementation of CSM. Our technicians don't forget to finish up a task with many tiny details and that's because Cherwell's workflows provide the technician with a list of the steps needed to finish up the task. We've become a much more popular IT department and leadership has noticed. I can't put an ROI number on that but it's priceless to me.
Technician errors in user onboarding and offboarding have virtually disappeared, saving us hours and hours of technician time. Again, I haven't calculated the ROI but it's probably a good 20% or more of our tier 1 technicians' time that has been saved. Higher-tier technicians are obviously not as affected since they weren't usually the ones who were neglecting the details, but even they have enjoyed more efficiency and better prioritization of their time.
