What is our primary use case?
We use OpenText MBPM for business process management and vendor invoice management. There are a lot of other variations as well. So we don't just use it for automation.
Primarily, we get information, and we deal with it in terms of business process management.
What is most valuable?
Not just the solution's automation capabilities, but we like everything about it since we are more of a system integrator. So, in whatever we would want to do, there is a greater level of detail in terms of access control mechanisms and in terms of how we initiate or terminate the workflow while also considering how quick the access and retrieval part of it is. The information, I mean, information in terms of documents, unstructured data, and so on and so forth, it's an overall solution that looks pretty formidable.
What needs improvement?
There are shortcomings in the solution's support and documentation part. However, support is a major area that needs improvement. In general, the technical documentation isn't available to start with, but then they kind of bring it together over time. So documentation is nice for the solution considering that I have been using it longer. Still, having some control structures around the product roadmap where the documentation is unavailable is good.
For how long have I used the solution?
I have been using OpenText MBPM for about 15 years. My company has a partnership with OpenText. We are also resellers.
What do I think about the stability of the solution?
Stability-wise, I rate the solution between six and seven out of ten. The stability of the product is okay.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution between six and seven out of ten since there's a lot of room for improvement, and it's quite a heavy solution.
We deal generally with enterprises, especially large and very large enterprises. Also, since the cost of the solution is quite high, it is probably supposed to be meant for large enterprise-sized businesses.
How are customer service and support?
I think the solution's support could do a better job. I rate the support somewhere around four and five out of ten. There is a hoard of people that they get in touch with while contacting them. So we've done some work with them in the past. I mean, we've been a support partner for a while. But apart from that, in terms of understanding the issues for a particular technology, I think there is a lack of people at their end. So they don't really have many people with them. And by the time we could get hold of the right person, especially for production issues, it's a little too late.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We work on SAP and OpenText together in our organization.
How was the initial setup?
On a scale of one to ten, where one is difficult, and ten is easy, I rate the setup between eight and nine since it is not difficult. Also, it could be because we have been doing it for a long time. We deploy it for our customers, and these days, the trend is to have the solution on the cloud, while before that, it used to be on-prem. The deployment probably takes a few weeks, but it all depends on what product we are talking about since OpenText has multiple products, so it's not just one product.
What's my experience with pricing, setup cost, and licensing?
On a scale of one to ten, where one is cost-efficient, and ten is expensive, I rate the pricing somewhere between nine and ten since it is a costly solution.
What other advice do I have?
I'm not an experienced user, but I can tell you how people do it today. So, POC is okay. In POC, there is a lot of content that you can read and figure out how it really works. But then what's more important is to understand, you know, what's the goal they would want to attain in implementing an MBPM solution like OpenText because it's a heavy tool in the first place. At the same time, the users or the organization which is looking to implement it should do a feasibility study in terms of technicalities, operational, and economic standpoint in terms of what they are trying to achieve. So if that is sorted out, they would really have an endpoint in mind, meaning when and what they would want to look at, what they would want to do, and how the solution should look for them. So, potentially, they would do all of this in advance. It is all done in advance so that they face no surprises when the implementation is done. But then what's also important is for an individual to ensure that the organization, which is going to use it in the near future, needs to expose it to all the users well in advance so that they understand the solution's capabilities, limitations, and how it's how it really works. So that there are no wrong expectations set in the overall tone at the later stage.
OpenText MBPM is point solutions for a specific set of activities or a specific set of businesses. Now, just like what we do in terms of MBPM, there are industry verticals that are very specific. Some of them are PnP devices, and some of them are not compatible with certain industry practices. There are point-based solutions that cater to various requirements. So I can't just have the same scale for all of them because some of them are specific for engineering-based businesses while some of them are specific for consulting, and some of them are for various other applications. Now OpenText, as such, comes with a tight integration of many of these products. So that way, it might have an edge, but there are other products that also have integration, but point-based solutions satisfy or help businesses.
Overall, I rate the product somewhere around seven out of ten.