BMC Helix ITSM vs. Drupal

BMC Helix ITSM fits our environment particularly well, where standardized, auditable processes are already in place: Incident and Problem Management can be structured cleanly, with clear ownership, escalations, and fully traceable documentation—crucial in a highly regulated banking context. Through the customer platform/portal, users can log incidents and requests consistently, track their status transparently, and use a single central communication channel across service boundaries. This supports a service-oriented setup spanning multiple business services and locations. It becomes less suitable—or at least more effort-intensive—when core foundation data is not yet stable: an immature CMDB, insufficient ITAM data quality, and an unstructured knowledge base limit the value of automation and self-service. In addition, heterogeneous integrations and strict authorization models can increase implementation and ongoing maintenance efforts, especially when SLAs are not harmonized across different customer environments.

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

• AI drive incident correlation leading to identifying problems and major incidents quickly.
• Digital Workplace gives end-users a modern and personalized UI to submit requests, monitor service health, and receive self-help.
• As an enterprise ITSM, it is critical that Request, Incident, Problem, Asset, and Change Management are integrated and flow together. BMC Helix is built on this principle.

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• Service Level management configs can be lengthy, and when changes are needed to specific SLA, it does take a long time to configure. Templates work but only for certain things, lots of manual work is still required.
• The Online product documentation can be confusing or in same cases not correct.
• BMC products are sometimes expensive. When partners try to resell licenses or increase their own allotment, it becomes very expensive.

Incentivized

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

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.

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

Overall the product enhances the capability of incident management, problem management and change management. The AI based framework helps generated better visibility and reports. The effectiveness of enhanced service desk suuport improves end user experience as the incidents are handled well in time and aged incidents are highlighted at the right time.

Incentivized

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

for now we are satisfied. first two months 😉

Incentivized

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

could be faster. db is slower from introducing postgresql

Incentivized

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

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.

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

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

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

Satisfied because I didn't have to do it!

Incentivized

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

I believe Remedy's performance and market share exceeds its competitors. But it is worth mentioning that Microsoft's SCCM has excellent integration with Microsoft enterprise solutions and has is less expensive and not efficient. The IBM solution has better analytics but lacks the wide features and capabilities of Remedy. HP & CA are the real competitors for Remedy but lacks the stability, maturity, and effectiveness in Remedy

Incentivized

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

unclear. lot of for less

Incentivized

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

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

• Positive: an introduction to ITIL and viewing Asset, User Management from the perspective of ITIL, and how BMC has implemented those processes
• Negative: The development team needs to communicate better with the sales and support side, and they need offer an open API
• Negative: Currently the Asset Management side has little security and validation of Asset input: anyone can make API (mostly), at any item, which is a problem that I am apart of solving.
• The UX needs updating, badly. Its quality is poor: it functions, but it is cumbersome, click-heavy and requires several hours to understand how to function with it. Also, it needs to ditch IE11 support, altogether.

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs