BMC Helix ITSM Reviews

I was responsible for three implementations with BMC. All of these implementations are related to ITSM, with the IT Service Management implementation, where we manage all the processes like incident management, request fulfillment, problem management, change management, and configuration management. All three projects were of the same scope, with only ITSM managing all these processes in each one.

The most important feature in the BMC is the users' and technical teams' front end. They are good for the front end, simple front end. For the first line of support and for the end users, it's a good front end. It's very simple to register, to follow the cases or incidents. 

It is a stable product if set up correctly.

The solution can scale. 

In the back office, for the expertise technicians, it's more complex to manage the layout. The back office for the expertise needs work. It's too specialized for technicians. Sorry, they need to simplify this background and back office more. For this level of support, it's very complex, and for the customers, it's an issue. The biggest issue for our customers is the back office for the specializations through the second and third lines of support.

The management of the solution, the maintenance of the solution is based on this back office, so it's very complex for the teams to manage the solution.

It's very difficult to implement.

Support could be better.

I'd like to see the globalization of the solution. The solution has varied models needed to make a simple implementation. BMC needs to look to a centralized solution, an all-in-one solution. To implement ITSM, I need to have a model for change management, I need to have a model for orchestration, I need to have a model for workflow design, and all suites of BMC have this problem. With ServiceNow, all are included in the ITSM solution. For example, however, for BMC, we need varied models to implement. 

The customers also need to maintain the solution after the implementation. It is very difficult for them to give that support.

I've used the solution for about five years. 

If the configuration was well performed, yes, it's a stable solution. However, this is the same problem for all the other solutions in the market. If we don't have a good implementation, we don't have a good illustration of the solution. That said, if we follow the best practice to implementation, it's very stable.

The solution scales well. 

Technical support can be improved. They are fast in response, yet they pass the buck to other people. It is not easy to follow the register of support. It's not the worst support in the world. However, it could be better.

Neutral

I also have knowledge of ServiceNow. 

It's very difficult to set up the product. It's one of the most difficult solutions in the market to implement. It's time-consuming. It will take more than two months compared to something like ServiceNow, which is faster and easier. 

The number of people you need for deployment and maintenance is minimal, maybe four or five people. We can separate that into one project management, one architect, and three developers or analysts to implement the solution.

I was a partner of BMC in my last job function. 

The best support is defending the requirements of the company. This is the same advice I would give in ServiceNow. It's very important for any solution to define the requirements very well. Based on that, it's easier to implement the solution. 

I'd rate the solution eight out of ten. Compared with other solutions in the market, for example, Manage Engine, which has technical limitations, BMC is robust. We can do everything with BMC. We can do a lot with ServiceNow too. BMC does have complexity in the implementation, however. 

We are using BMC Helix ITSM mainly for incident and change management.

The most valuable features of BMC Helix ITSM are the service level management, configuration, and reporting tool.

When BMC Helix ITSM did some upgrades it caused some issues. They have fixed some of the problems but more improvement is needed.

BMC solutions are now multiple solutions, they are not one comprehensive solution. It would be beneficial if there was one installation that could be done for all the solutions together. It would make it a lot easier to upgrade.

They should improve the reporting and dashboard. However, we have seen the smart report and dashboard, it was very good and I know they have enhanced it with Grafana. They are using Grafana with the latest version, but we did not try it yet.

I have been using BMC Helix ITSM for approximately 25 years.

BMC Helix ITSM is a highly stable solution.

The scalability of BMC Helix ITSM is good. We are able to scale to solution up and down.

I rate the scalability of BMC Helix ITSM a nine out of ten.

I have had a bad experience with the support. Their knowledge was lacking, the response times were not always good for the reported case. Depending on the reporting case the support could be better or worse. 10 to 20 percent of the reported cases are not handled in a timely manner.

I rate the support from BMC Helix ITSM a four out of ten.

Neutral

The initial setup of BMC Helix ITSM is straightforward.

I rate the initial setup of BMC Helix ITSM a nine out of ten.

We used a third-party consultant for the implementation of the solution.

We did not compare the price of BMC Helix ITSM to other vendors. However, it has a mid-range price.

I rate the price of BMC Helix ITSM a six out of ten.

I rate BMC Helix ITSM an eight out of ten.

It has complete coverage of ITIL processes and a rich functionality. Plus, it provides a strong customisation platform in AR System which is quite flexible.

BMC Remedy ITSM has been used both by the customers that I served as well as the software services companies that I actually worked for while serving those customers. In each case that I have seen so far, BMC Remedy has typically been implemented to transform multiple older ticketing systems into a centralised single IT ticketing system. In the case of telecom vendors, largely it is doing the job of network (operations support systems) ticketing and is integrated with variety of non-BMC applications. In each case, it has helped customers transform their applications stack and bring in a uniform, standardised process when compared to the past. This results in savings and streamlining of both people and processes.

The traditional UI of Remedy is somewhat of a weak point from the end user perspective. Also, from a developer perspective, a lack of version of management support unlike traditional programming languages such as Java/C# etc where you can easily create code lines, create branches/merge branches, create automated drops of code etc. One can't do this in Remedy in that manner. In general, Remedy doesn't support very aggressive Agile development and is more conducive to a waterfall kind of SDLC. Also, the debugging of defects or performance issues in Remedy is not well assisted by the Remedy Developer Studio.

I have been using BMC products for around nine years, since 2006. My experience includes older versions such as 7.0.1, and 7.6.03/04.

By itself the product is ok, but frequently people follow incorrect procedures while doing custom coding. BMC does provide guidelines to avoid this, but AR systems as such doesn't prevent you from coding in the incorrect manner, so such bad customisation can cause deployment/upgrade issues later. From versions 7.6.04 and 8.1 onwards, this is largely addressed due to the introduction of the overlay concept, but it is still not too easy to upgrade wherever you have heavy customisation.

Again the stability is frequently related to custom code rather than out of the box code. I don't think it is unusual for any application going live for the first time to be a bit unstable for the first two to three releases, at least after the first ever go-live.

Not much - it is highly scalable.

Customer service can vary wildly. With premier support from BMC, which is very expensive I believe, it can be quite fast and dedicated. But, if you have bronze, a basic service or worse, if you don't have direct service from BMC but only have access to them via some intermediate partner - then it may not always be smooth.

I have experienced service to both extremes - very good and not good at all! Currently I am driving a project that has premier support so it is quite good in this case. They helped a lot in sorting out upgrade related issues and we had a very smooth excellent upgrade from 8.1 patch 002 to SP2.

Typically our customers switched from other products such as Amdocs Clarify or People Soft or home grown ticketing applications to BMC Remedy because the older platforms were not supported by the original vendor anymore OR they found the older solution was not scaling to their needs. Plus, older ticketing functionality was typically fragmented across multiple applications - e.g. for incident management, they may use one application and a completely different application for change management and so on. Now, it is all within one suite which is much easier to handle.

BMC Remedy is set up for a real production environment and can be quite complex depending on what you have. For normal DEV/TEST environments, it is fairly straightforward, but it certainly is nothing like MS Office or something, where you can blindly click next-next and then finish and forget about the installation! It is a complex enterprise application and needs proper administration on an ongoing basis.

In all cases, I have had my own set of people (belonging to a software services company) that did the implementation. In India, we have a pretty good pool of people available for this in general.

I believe there is a strong need to actually compare Remedy, Service Now and couple of open source or free to download products and bring out what really the free products can achieve vis-a-vis established product like Remedy.

As of now, this is more of a perception (Remedy is costly, Free products have less functionality etc - but hardly anyone is going to great lengths to establish point by point, module by module what really is better in which software).

There is no point in listening to such comparison done by one of the vendors (e.g. BMC Remedy communities are having several comments of how Service Now lacks several things and customers coming back to Remedy. Service Now communities are saying exactly opposite. The need is to take out this bias and put down all the facts in a proper shoot-out.

In most situations, we got involved only when customer had already made a decision to go for BMC Remedy so I can't really comment on this. But I think it is more to do with good sales pitch from BMC and the fact that it is an established tool with large enterprises that has typically tilted the scale towards BMC Remedy.

For large organisations, or a medium organisation that is now growing due to new acquisitions etc. (typically several thousand people strong and a large presence in one or more countries) BMC Remedy is surely a very good choice. For smaller organisations, there is the option of BMC Remedy-On-Demand (ROD), but then they may have cheaper alternatives - or at least options that give low starting price.

The main valuable feature is the flexibility of the product -- the ability of being able to make it do almost anything we need it to do to adjust to our business needs and to do it very quickly. The time to deliver a finish product is fast.

We have been able to provide several fairly complex and deeply integrated fully customized applications within the different systems throughout the company in an extremely quick delivery time which is impossible with other products.

It has improved the life cycle of the development making it a lot shorter to go from the concept phase (requirements gathering) to the deployment portion.

We also have been able to provide a lot more applications to the businesses within to service them better. Improve their processes by automating a lot of their sticky notes and spreadsheets and other paper trails that they were using prior to the application being created.

I have been developing on ARS platform since 1998, but on this version since 2013.

Like any product/new versions there are always issues. The main ones are the undocumented features that comes with the customized applications. We are not using the out of the box application (ITSM) therefore we are thinking "out of the box" and BMC did not document all of the changes made in their different upgrades. So each time you upgrade from one version to another, you always run into these issues. You need to always make sure you do thorough testing of all the functionality you have in your different applications especially if you are "outside of the box" type of business.

We did and still have stability issues that we are working on. The issues are all linked to the BIRT reporting tool which was the solution recommended at the time by BMC. But we are now totally disconnecting from this tool. We have identify this as being the 100% culprit and are using other methods for doing what is required within our web applications.

But beside the reporting issue no. This is a solid system. We do however have a weekly scheduled reboot of our servers (Windows farm) just to be safe. But that is just because they are Windows :-)

But in all honesty, we need to always keep an eye on the amount of Handles being generated by all the services from the BMC AR System. They do from time to time run out of control and will require you to restart the services. But that is not a regular occurrence.

None. I haven't seen any limitation at all on this product. It is as good as the hardware will allow it to be. you just need to ensure you have the proper hardware/architecture to support what you need.

The Customer service is the same as always. It hasn't changed much. They will always be there to help you find the product to help you grow in your business.

BMC needs to keep improving their support. It is still far from what it was back in the days of Remedy. It is very sad that you still are asked for you logs when the logs are already been provided and that you are asked the same questions when those are already answered in the tickets. It is as if they are reading from a script like drones. They need to learn to be more proactive and less robots. When the tickets being raised already have all the details of the issues, and all the diagnostics have been done by us please send the details to second level or 3rd if necessary instead of asking us to repeat the steps we already repeated. we don't have time to waste, especially when a server is down. That is why we do not use BMC support at the moment.

We have been on BMC AR System platform here since the mid 90s. We keep adding more applications, modifying/updating the old ones.

We have retired some too. It is an easy platform to grow and adapt

I was not at this client site when the implementation was done. But from experience, I would suggest that anyone embarking in this adventure does get at least the basic training

BMC ARS was implemented back in mid 1990's . I was not at this client site when the implementation was done.

BMC ARS was implemented back in mid 1990's . I was not at this client site when the implementation was done.

I keep a close eye on license usage and balance them. The cost of license is always an issue in every company and needs to be evaluate every Quarter/Year.

A report is provided with the recommendation to each business units on what needs to be done.

BMC ARS was implemented back in mid 1990's . I was not at this client site when the implementation was done.

This is based on the older version of the product as we are slowly moving all our thick client apps to the Web. This has been a pain stacking process due to amount of applications we needed to move and to the multiple of "old" code we had to drag along with us. The next move will be the upgrade to version 9 which will be another huge and exciting step. This is an amazing powerful product, but like any product that has so much multi possibilities, it has its "quirkiness" that you need to learn to work with.

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.

• Configuration Management – to track hardware, software, users
• Change Management – manage and maintain the company schedule of activities and resources

This product aided in the management of hardware, software, resources, and implementation schedules. Additionally, it opened the communication barriers for resources and management to communicate one on one or in a group tracking and utilizing the facts

The company has used it for 11 years, and I have used it as an implementer & manager for four and a half years. I have also used is personally as an end-user for a further seven years.

When I was a part of the support and upgrade team, it took 120 constant hours to upgrade. 

The data was slow and the BMC support was lacking. 

After the five day upgrade we then had days of data clean up.

We were using a very old product called PMSD, and excel spreadsheets. It was not robust nor did it provide the endless types of functionality that Remedy offered.

The initial setup for all involved was “discovery” as no one had the experience of the tool.

Our internal team performed the hardware configuration and setup, software process and procedures, documentation and training. Our teams were technically strong and had good technical knowledge. They knew the company and this is what made our implementation successful.

I cannot comment as I was not monitoring the ROI. 

I do know that managing the configuration items aided in the upcoming annual contracts for hardware, software products and other configuration items, the data was extremely helpful.

We evaluated several tools – I cannot remember them as it’s been a while. We had a PRB team and performed site visits and demos.

It’s a great product, I would highly recommend it. My strong advice is to take your time to plan, understand your company, and design your processes with your team members to understand all aspects. You also need to schedule your time and implementation. Finally, understand that it’s teamwork, and without that no-one will be successful.

• 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.