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.
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.
You can use Helix IPaaS.
In order to build smooth data flows and automate business operations, Helix iPaaS enables organizations to link diverse systems, apps, and data sources, whether they are cloud-based or on-premises. It has a number of features, such as:
In order to connect to well-known programmes, databases, APIs, and protocols, Helix iPaaS enables pre-built connectors and adapters. It makes it simple for you to connect to and communicate with various systems.
Event-Driven Architecture: It provides event-based integrations, enabling you to start processes and activities in response to particular circumstances or occurrences.