BMC Helix ITSM vs. ServiceNow IT Service Management

There are many ITSM platforms available - but only a very select few are true enterprise leaders. BMC Helix is one. When it comes to managing thousands of incidents daily, BMC Helix helps cut through the noise with incident correlation and predictive problem management.

Incentivized

In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.

• The Service Asset and Configuration Management capabilities of Helix ITSM are awesome. It can be used as a central repository for all SACM information and seamlessly integrated with Helix Discovery.
• It has the most certified ITIL process modules of any ITSM system. These modules work seamlessly with each other and give you the power to manage any situation effectively.
• As an Administrator of Helix ITSM you have many tools at your disposal to create customizations, workflows. BMC makes it easy to manage the system, leaving time to develop customizations and workflows.

Incentivized

• When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
• I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
• Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
• To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.

Incentivized

• Customization can be lengthy due to the numerous features included in the software.
• New staff members require some sort of hands-on training to get to know all the use capabilities.
• The analytics can be improved to include forecasts and trend analysis.
• Expensive compared to competitors.

Incentivized

• It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
• The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
• The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!

Incentivized

It provides the tool we need and is able to be customised to meet new requirements. Cost to change in training and integrations would be considerable.

To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.

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.

The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.

for now we are satisfied. first two months 😉

Incentivized

We have never had any issues with ServiceNow's availability that I am aware of in the two years I have been using it.

Incentivized

could be faster. db is slower from introducing postgresql

Incentivized

For a massive system, page loads are reasonably quick, including searches.

Incentivized

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.

I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.

Incentivized

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

Incentivized

To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.

Satisfied because I didn't have to do it!

Incentivized

Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.

Incentivized

I did not select Remedy myself, so I am coming in from someone who is apart of the story, from somewhere in the midway. That being said: Remedy has begun a journey of understanding the problems associated with the implementation of ITIL, and indeed ITIL itself (it is a top-down process for management of an IT department). there are many alternatives out there. One, in particular, I am keen to investigate: Redmine. But in doing so, It will be evaluated via my experience with Remedy.

Incentivized

We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.

Incentivized

unclear. lot of for less

Incentivized

Again, always room for improvement, but a very stable product none-the-less.

Incentivized

ServiceNow works as an enterprise solution.

Incentivized

• The ROI was fine initially as we got what we paid for and it served its purpose
• Over time, we got behind on releases due to limitations with customizations we made to the application. The product then became out of support and completely out of date, and we had to replace
• Overall ROI was minimal and once the product was out of date we found more value in other tools

Incentivized

• Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
• One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
• Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
• Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.

Incentivized