BMC Helix ITSM Reviews

The primary use case was basic ITIL/ITSM.

It replaced an older system, called ManageNow. It had no major impact on the way we operated. We more or less continued, we had a well-performing organization, so it really didn't change much. Everything we had in ManageNow, we had in BMC Remedy, including basic incident management, event management, based on monitors spread around our environment.

It was a full-featured product. Based on my experience where I was responsible for Remedy, and for a later project where I worked on a very sophisticated implementation of BMC Remedy, it is full-featured and could do almost anything that you can think of in the ITIL portfolio.

BMC Remedy has more features now than I know about and have used, so it would be presumptuous for me to try to suggest improvements for a future release.

What I do find is that, compared to ServiceNow, BMC Remedy is somewhat "closed." I can go to the ServiceNow website and learn everything there is to know about the product, and training is available. That really wasn't available with BMC Remedy.

However, if I'm working with a client who wants to expand and move into other areas - they want to expand their workflow and other parts of the organization, they want to do some work with project management, they want to do some work with HR - I'm not sure that BMC Remedy is doing that. And it's because of their platform. Any software has a lifecycle. To me, BMC is a dated architecture. I wish them well but I don't see how they're going to keep going, long-term, without a total rewrite and coming out with a new system.

BMC Remedy is good. It's solid. I don't remember ever having any stability problems with it.

I didn't see any limits. I worked with one client who had, to me, what seemed like a lot of servers. They had some 25,000 servers. They had a lot of BMC workflows. They had a lot of users on the system. I never really got a full feel for how many, based on what I was doing, but I saw no scalability issues. ServiceNow and BMC Remedy scale about equally.

There were times when we needed to talk with BMC service support, and we got good response. It was something that we paid for, but we got good response.

The old system was at the end of its lifecycle, it was being phased out. The name of it was ManageNow, and I don't know that it exists anymore. It was very old and BMC Remedy was a step up, in the right direction, to a modern system.

When selecting a vendor it depends on the client. In my case, I was selecting for a client and BMC Remedy was the best available at the time. We did an evaluation of all the vendors, and BMC Remedy was the best. That was eight years ago.

Initial setup was like any other similar implementation. There are certain things that you have to do, tables that you have to build, configurations that you have to work with. There are a few modifications that you have to make so that it fits into your environment. We tried to stay as close as we could to the out-of-the-box solution. So it was fairly straightforward.

There are portions of BMC Remedy that are proprietary. One of those was attachments. If I attached an image, if I attached a project plan, if I attached a screen print, getting those out was very difficult when we moved servers to ServiceNow. So if you're not planning on moving, it's not an issue. It's when you move it the issue.

ServiceNow is expanding. If I were just choosing an ITSM system right now, it would be hard to choose, if you ignored the underlying platform. BMC Remedy is very old. It has a very old infrastructure. So if I ignored that, and the "openness" issue, it would be very hard to choose between BMC and Service Now.

I would rate at nine out of 10. It did what we wanted it to do. We had some issues, but we caused those issues by the way we implemented it. I found that BMC training and BMC availability for learning how the system worked and for answering questions - if it wasn't in their manual, it was very difficult to get that information. You had to pay, it wasn't open. It was a "closed" environment. If it had been much more open, so I could get into understanding everything, that would have been better.

In terms of advice, if you're working for a large company on an ITSM solution, where you're talking about incidents, problems, change, knowledge, there are three, maybe four vendors. I would say look at those very hard, learn what you can, and make the best decision for your organization. It's a limited market.

The solution supports our supporting processes. My responsibilities include reporting on the services we offer to end-users, primarily through channels like email. I focus on coordinating arrangements for the services we provide.

The valuable feature for me is that it's a tool that allows me to track processes right from the initial user request. It helps in updating the solution throughout the workflow. I use it to gather information about the people involved, track time, and more.

Working with numerous processes can be complex, and the processes are not always transparent in the solution. At times, users may not be aware of the meaning behind various processes when receiving certain information. The most frequently requested change for the solution is integrating the latest technology to facilitate interactive resolution.

I have been using the solution for the past 20 years.

The solution is stable. I have several servers working together in a cluster.

The solution is scalable.

We haven't needed customer support extensively. However, we did encounter some delays, waiting for several hours to receive a satisfactory answer. Fortunately, there have been no issues with the technical components.

I have worked with SentinelOne and ServiceNow.

The solution is best-suited for medium-sized companies. I rate the solution a nine out of ten.

This tool is used for ticketing purposes, to track down daily issues and requests as part of business requirements.

It includes ITIL practices such as incident management, problem management, change management, asset management, and configuration management. We are able to link tickets to one another.

It is used to create, modify, update, and resolve tickets. Parent/child tickets are possible to create. It can also create problem tickets and change requests. It will easily calculate SLAs and can create and customize reports as per user requirement. 

This product has helped us to maintain our OLAs (Organisation level Agreements) and SLAs (Service Level Agreements) by tracking incidents, requests, problem records, and change requests, all in the form of tickets.

We can easily check the progress of these tickets and follow up with the respective teams.

It provides us the facility to maintain a KEDB (Knowledge database), which is indeed very beneficial for day to day activities.

It can easily add notes to every ticket with the status update.

For us, this tool is essential for ticketing purposes.

The most valuable feature is the linking of parent and child tickets. When there are major issues, through the help desk, multiple tickets are raised for the same issue. This allows us to segregate it by parent or child tickets and link the child tickets to the parent.

It's easy to calculate the SLA as it provides the timing as to when the ticket was raised, and the clock automatically stops when the ticket is on pending status. Thus, at the time of resolution, it provides the SLA, whether the ticket met the SLA or not.

To raise any ticket, there are too many fields to be filled and it makes generating tickets very time-consuming. Some fields should take data automatically; for example, ticket routing to the teams after entering the team's respective CI (Configuration Item). This will save time and creating tickets would be faster. 

The GUI looks a bit complex and can be much better.

When generating reports, there are limited options to customize as per user requirement. It is in need of better customization so that these requirements can be satisfied.

We have been using BMC Helix ITSM for six years.

• CMDB is very useful and it is used to manage client and non-client CI
• Freedom to use your ow way to integrate other systems with BMC Remedy
• Not too difficult to customize workflows

Using Service Request Management creates a Change Request and then sends, via a web service, a request to start a job on VMware to automatically create a server. When the job is finished and server is created it send back the name of the server back to remedy and automatically creates the CI in CMDB and create relationships. In this way we created an automatically way of requesting a server.

In 8.1.02 the Atrium core in the Midtier should be improved. It is using flex technology which is not so reliable. I think in v9 it was changed the technology.

I have been using this product for almost eight years.

There were no major issues with the deployment.

There have been no major issues with the stability.

There have been no issues with the scalability.

The first level is not so skilled . If you manage to go to second level they are good.

There was no previous solution in place.

It was a complex one, because our company was bought by another one and both companies had different versions of remedy installed which needed to be unified. The complexity was from the level of customizations each instance of Remedy needed.

We did it via a vendor. It would be good to create a knowledge in hour which knowledge should be transferred from the vendor side.

I'm not involved in this area.

The BMC Remedy products are reliable and cover all the ITIL processes. An advice would be to try to keep as low as possible the level of customizations.

We use BMC Helix ITSM as a managed ticketing solution for the telecom industry.

The solution is already aligned with the framework, so it is easy for us to proceed with any ISO 27K certification. We should take a certification in terms of Service Assurance and Service Framework.

There are plugins to the solution that have come onto the market, so the solution should also be updated in terms of administration to increase efficiency. That is why we have come up with other products that have a similar use case. BMC needs to come up with a plug-and-play system that requires a minimal partition, it would be highly beneficial.

I have been using the solution for seven years.

I give the stability an eight out of ten.

I give the scalability an eight out of ten.

The initial setup is not simple. We require a skilled administrator to complete the deployment. Depending on the customer's requirements the solution can be deployed on-premises or cloud.

I give the solution a seven out of ten.

The differences between BMC Helix and other ITSM solutions depend on the use case, process alignment, and organizational requirements. We have realigned the entire product to suit telecom operations, so it depends on the organization's strategy regarding ticketing solutions.

I recommend the solution to others.

This is an IT Service Management tool for incident management. 

I use this product as an end-user and not an administrator. This is not a product that I use extensively. We primarily use it for incident tracking and service request tracking.

The interface is nice and it's simple to use.

It provides a good user experience.

Functionality-wise, it falls short of our expectations. This could be the way we have it deployed. Perhaps, the functionalities have not been enabled 100% in our organization. There could be some additional features that our enterprise is not aware of, yet is available.

There is a text editor that we use to enter our incident description or service request description, and it should be richer in terms of features. For example, it would be helpful if we had more formatting options.

We have not faced too many issues with stability. It's fairly okay.

This product is used enterprise-wide, with between 600 and 800 users.

Our administration teams are the ones that have contact with technical support. As such, I have not had any experience with them.

Prior to using BMC Helix, we used CA Service Desk.

I prefer using BMC.

We used a system integrator for the deployment.

I would rate this solution a six out of ten.

I'm a service management specialist and I'm in partnership with BMC.

I like the digital workplace, it's an appealing feature for me. 

One of the issues with the solution is the requirement to provide a lot of information in order to log a request. I'm not talking about end users, technicians or engineers need to provide too much information to initiate a work order or an incident. It doesn't flow; access should require minimal effort. They should consider using ITIL principles and not just IT. 

The initial setup required an engineer for configuration, to load data on the system. The datasheet form isn't user friendly, a client wouldn't be able to fill it in, a tech savvy person is required.

I like the tools BMC offers but it's very expensive.  The pricing model needs to be revisited.

BMC is definitely not for small businesses, especially those in Africa, Eastern Europe, and the Middle East. It's difficult to get small businesses onto BMC because of the cost. For functionality, I would give this solution an eight out of 10 but I have a serious problem with the pricing and that brings my rating down to a six.

To manage the ITSM process in our organization and the organization's infrastructure via CMDB.

I have implemented and worked on this product at many customer sites. The way you can customize this product to adapt to the process the customer is already using is what sets this apart from other ITSM products out there. This helps customers to adapt to the tool pretty quickly.

The versatility and customizability of the product is what I like most. It provides a strong customization platform in the AR System.

The interface is one major complaint about this product. With the recent introduction of Digital Workplace and SmartIT products. I think BMC is finally going in the right direction on that front.