What is our primary use case?
We are a partner for OpenText and BMC, and this is our main professional service delivery. We are the professional service delivery arm for both of them.
I am responsible for the ITSM products, such as OpenText SMAX, Helix ITSM, and others.
It is not only ITSM, it is an ESM as well.
It is mainly the DWP. And the ITSM modules, IAM, incident, request, change, and others. Mainly for the ESM, the most beneficial layer is the interfacing layer of the DWP, the Digital Workplace. And actually the advanced service catalog.
The underlying work orders and workflows of the service catalog are a mainly critical point for the ESM and even the interface for the ITSM tool as well.
What is most valuable?
Recently, it is good. It is promising. It is still not totally amazing. Even for BMC, for OpenText, for ServiceNow, for all the vendors, it is a booming technology. And all vendors are trying to integrate it inside their ITSM tools. Still, there are some limitations, especially related to the Arabic language, especially for the Middle East. The LLM language model and LLM models are not supporting Arabic for most of the tools. So this is a weakness. However, I can see some vendors are still working on this point right now because there are LLM models in the market supporting Arabic.
For automation, you have multiple tools depending on the vendor. For example, for OpenText, we have an OO integration, Operation Orchestration with SMAX. For BMC, we have Control-M as well, and can automate some items. All vendors as well inside their portfolio are considering the automation. It is not a native function inside the tool, but actually within the portfolio with seamless integration. It fits for purpose.
What needs improvement?
It is perfect, unless there is the support of the Arabic language. Supporting the Arabic language is the critical point, especially for ESM more than ITSM. Because for the ITSM, most of the IT staff can handle the English or any language besides Arabic. But when you are targeting the ESM, you are targeting the HR team, the finance team, the maintenance team. Not all these teams treat with English terminologies or report their cases with English. At this moment, the Arabic language or their native Arabic language should be considered and it will be more important inside the chatbots. I would prefer to chat with my own language.
Enhancing AI support for the Arabic languages, enhancing the automation of the ticket, and automation of the ticket workflows would make it simpler for implementation and simpler for enhancements. Adding more capabilities for adding more flexibility of the customization is important. This is not only for BMC, even for OpenText, even for ServiceNow. As long as you are moving to a low-code platform, you are limiting my capability to customize. The solution will be fit for purpose perfectly for a low-customization environment. However, it is a limitation for the low-code environments. All low-code environments have limitations when customizing. When you compare, for example, in OpenText, when you compare SMAX to the legacy Service Manager, Service Manager has more capabilities for customization, more than SMAX. This is the same between Helix and Remedy. Overall, BMC still has a very powerful way to customize. It still has a very good customization capability.
For how long have I used the solution?
How are customer service and support?
All vendors have several plans for support, for supporting models. From premium to standard, advanced. It depends on the supporting package you purchased. For example, if you are talking about premier support in OpenText or BMC or whatever, and you have a dedicated resource, the response time will be much better. The initial phases of investigation will be very short because you have a dedicated, assigned resource who is understanding your environment, already knows your environment, already knows your understanding and your needs, so it will be much better.
Also, for the support of BMC, especially for BMC Helix on cloud as a software-as-a-service, the support will be faster than the response in investigating an on-prem solution. This is crucial for the troubleshooting of the infrastructure or a bug. For example, if a system is down totally, I am not talking about software enhancements or an issue inside the tool itself, but talking about if a system is down or if you have a critical ticket, BMC Helix SaaS is very good for support, more than support for on-prem. This is the same for ServiceNow, same for OpenText, same for everything. It is about the SaaS supporting model because the resource is already understanding or well-understanding the infrastructure deployment that happened on the cloud, on their cloud.
Which other solutions did I evaluate?
All vendors can compete with their pricing. All vendors for the same class, for example, if you are talking about the world-class such as BMC, ServiceNow, OpenText, all of them can compete in front of each other. I am not talking about the same price for medium-scale such as ManageEngine or smaller tools. But for the same scale of the vendors, almost all of them are near to each other.
What other advice do I have?
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner