IBM BPM Reviews

The most valuable feature for the organization is the Document Store. It helps us for storing documents for the organization.

The product and environment are very easy to use. With a single click, we can move from the environment into the product.

The issue that we have is with archiving and housekeeping. They don't have a mechanism to achieve processes, data sources, and data. We are currently struggling in this way and would like to get a solution for it.

Having a document viewer would be helpful. As it is now, the system requirements are such that reviewing documents is on a single page. The problem is that with business nowadays is that there are too many requirements.

We have been using IBM BPM for about four years, since 2016.

This is a stable product.

It is a bit difficult to scale.

Sometimes, we face unknown issues. It's our goal to gather information and logs that we need to take. There should be a solution where we can easily monitor what is happening in the system. The system should provide us with a way to implement things such that it is scalable.

We have more than 7,000 users.

Our experience with technical support varies depending on the issue. Sometimes, we get an answer immediately, whereas other times, it takes a while for things to be resolved. For example, recently we had some issues that took seven or eight days to resolve.

The initial setup and deployment are really easy.

This is a good product and I definitely recommend it.

We will be updating to the most recent version next month.

I would rate this solution a seven out of ten.

We are doing a lot of transaction processing for 401ks, moving processes out of a legacy workflow system into IBM BPM.

Our workflow processes are initiated from the web. They will start a process on the back-end, and move throughout all the steps necessary to process distributions, loans, and relevant transactional work. 

We started with Process Server, even before IBM BPM, so it was 2006 to 2007. When IBM bought Lombardi, we converted over. So, it has been quite a while.

It has improved my organization quite a bit. It brought awareness to what our business processes are, even to the business side, who did not necessarily know what they are.

There are a lot of things that you get out-of-the-box: Timers and so on, which took a lot of effort and code before.

It is being able to see the process, and understanding what the process is versus having to bury it in code somewhere. 

Better reporting. I do not think that we are fully taking advantage of what it already has yet.

I have an interest around the robotic piece, and integrating that with the processes. I think that is certainly a good direction to be going. 

So far, it is stable. We do not have a ton of processes moved over yet, but the ones we do have seem to be working pretty well.

We still have a lot to move to figure it out.

I have not had to deal with that side of things. We do not have anything that is down, so I am guessing technical support must be doing okay.

We have a different area that works with getting everything built up and installed. The migration process sometimes is a little bit hairy going from one version of a progress to another. Other people take care of it, so I do not have to worry about it.

It is a pretty good product. It does everything we need it to do.

BPM is an internal workload tool, so I use it to move the funds between different accounts for client onboarding.

The most valuable features are the integration capabilities - BPM can connect with almost any legacy or advanced system - and that you can design and implement UIs.

BPM could be improved with more flexibility in integration and by decreasing the learning curve, which keeps increasing with each new version.

I've worked with this solution for ten years.

The stability varies because it involves a lot of other components like databases, so sometimes if something goes wrong there, it can't recover from the fatal errors.

BPM is scalable, though not automatically.

IBM's technical support is pretty good.

The initial setup is of medium complexity.

As long as you have clear use cases, you can do pretty much whatever you want with this tool. I would rate BPM as eight out of ten.

I am a Solution Architect and I support both cloud and on-premise versions of IBM BPM. I use the solution for banking applications, such as account opening, fund transfers, corporate and credit limit approval process. In the insurance sector, digitalization, underwriting, life insurance claim settlement process, and vehicle claim settlement process. 

This solution has always been lacking in the user interface (UI), it needed to be improved a lot. However, from the acquisition of Spark UI, the UI is much better. Overall the solution is robust and has the ability to integrate with any product for complex workflows.

IBM BPM integrated with Spark UI and the UI is now much better, but they still need to improve the UI because competitors have predefined templates and other additional features. In these competitor's solutions, you are able to use the templates, map your data, and the form is ready to use. With this solution, you need to write a lot of code to have the same quality as the competitor's templates. It would be a benefit to make this platform more towards low-code or no-code. 

The REST web service integration needs to improve by providing other features, such as different security options.

In an upcoming release, they should add video calling capabilities to the solution. I work mainly in the Middle Eastern market and many of the bank companies use video Know-Your-Customer (KYC) to call the customer directly from the BPM tool. They do this for customer verification, such as document and identity authentications. Additionally, every organization at some point would like to send out letters to their customers, for example, welcome letters, but there is no easy way to do it with this IBM BPM. There needs to be a template available or an attachable generated PDF document that can be made easily within this solution.

I have been using this solution for approximately 10 years.

This solution is very stable. When looking at all the features reliability is one of the strongest points of this solution. It has greater scalability and stability compared to the other competitors, such as Appian.

The scalability is really good. The scalability of IBM BPM is one of the best in the market because you can scale seamlessly. You can add any number of user licenses, CPU cores, or other components.

Most of the customers I have are enterprise companies using this solution.

The support is not very good. When we raise the Problem Management Report (PMR) for any support, they usually take a long time to respond. They tend to ask a lot of questions instead of evaluating the system themselves by doing screen sharing sessions or other troubleshooting evaluations. There are times when we finally get a response from support but the solution they gave is not helpful and the issue remains.

I rate IBM BPM customer support as seven out of ten.

I have been using this solution for a long time and for me the setup is not difficult. However, it is a little complex if it is your first time or when you compare it to competitors. The length of time it takes to do the setup depends on the hardware environment, but it typically does not take very long.

The price of the solution is fair for an enterprise solution that has both cloud and on-premise deployments and when comparing to competitors. Recently IBM has introduced Cloud Pak which allows for more flexible licensing options for automation and other features.

I have evaluated Appian.

I rate IBM BPM a nine out of ten.

We do claims processing and BPM is the product that we use to have the member ID's and codes added to it.

Process Portal is where most of our business users log in and complete their work, that's the main use of interface. 

We don't use it in conjunction with IBM Case Manager or any other IBM information product.

It is helpful in processing at least 200K claims, so during open enrollment it's huge for our company.

It saves a lot of manual work, a lot of data entry work. That's how it has positively impacted our processes.

The workflows, and using them to process the claims and send files back.

It will be good to have the RPA. I learned that that's coming up, the workflows are going to have RPA in them, so I'm looking forward to that.

Except for the Lucene the index - we had a couple of issues in the Process Portal where the Lucene index went out of sync, and we had to work at least 15 - 20 hours to have it back in sync with the database. So that was big for us last year. 

If that's improved, or if that's removed, or if there is a workaround for the Lucene index issue, that would be great. 

Scalability is good. We are looking into rolling out BPM for newer projects as well. I can't say we are seeing an ROI from being able to scale with it.

I wasn't involved in the initial setup. We worked directly with IBM.

I rate it a nine out of 10. It's not a 10 because of the Lucene index issue. That cost us a lot of efforts in the production environment.

It's a good solution in terms of stability and processing and response. We haven't ventured much on the other features that IBM BPM gives, like Business Space and Business Process Choreographer. I think other than the Process Portal issue, the other things are good.

We do use not the BPM alone; we use the BPM with the ODM and the BPM with the RPI from IBM too, which is Automation Anywhere. So we have a lot of pieces connect to accelerate the process. We have a business process to open accounts and a workflow from open accounts to transfers. The transfers include internal transfers and international transfers.  We have a business process to open accounts and a workflow from open accounts to transfers. The transfers include internal transfers and international transfers. We have about 60 processes, including nine complex processes implemented. We also have 20 ad-hoc processes. We created these processes in about a month.

The process is important. The processing functionality makes it easy to change processes and workflows easily. This is useful as our business is in constant transformation and is constantly changing. We have an internal team that knows the product well regarding BMP, and we do not often need the intervention or further support of IBM.

This is one of the best tools to support the business and the way we work, and the numerous processes we need to implement.

IBM could improve the price. It is far too expensive. It would also be useful to be able to implement the product more quickly. The front end is not customised for a good user experience. It does not have an amicable interface.

We started using IBM BPM seven years ago.

IBM BPM can be scaled up and down to various layers. At the highest level, the solution is implemented quickly and suits our purpose. Lower levels provide more functions but take longer to implement.

When there are issues with the product, we need to raise a case with IBM, but the turnaround time for support requests is very long. However, generally, we don't have that many issues with the product.

We improved the setup process, but it can still take between 2 to 6 months to complete an implementation. If there are any issues, it can take up to a year to complete. It is a complex process.

It would be best if you chose the correct partner for implementation. If you don't use a partner with the correct knowledge and the implementation goes wrong, you need to re-implement, and it is a very time-consuming process. The implementation should ideally not be used as a learning process. We found this out by experience as we once had a partner with little experience, and as a result, a lot of errors occurred within the implementation. This cost a lot of time to resolve. We use an experienced integrator now to assist with the process.

It is a very expensive product.

It's a robust technology, able to support a lot of processes so that users can use it in a large group processing environment. I don't customers use the latest version. The latest version, 6.0, has been out for 2 to 3 months, but there have been many problems with it. It is best to use a mature version in the market, which is well established.  

I work for an insurance company and we use BPM to digitize two of our main claiming processes, to make them paperless.

We use it as a workflow platform and little more than that, because they are interconnected with other platforms of ours: our legacy systems, our customers, our partners, providers, etc. There are two BPM applications we developed with IBM, as a partner, to follow the bottlenecks and those kinds of things. So, I would say that it is more than a workflow software for us.

One of the most notable things is how you can develop use cases with the customers, internal customers, but directly within. The software process model that BPM supports is really exciting in that aspect. The natural interconnection with other IBM products is sure: WebSphere Portal, FileNet. We interconnect all of those.

We haven't discovered what features could be added, yet. We are still in the early phases, and it has more features than we are using now.

The people working on the front desk are having some problem with managing the documentation. For instance, they get a picture, and if the picture comes rotated 90 degrees, together with a picture that is not rotated, they have some problems dealing with that, technically. There are some minor aspects that on the usability side that are still lacking. That has to do with FileNet, too, I'm talking about the suite together.

One of the processes, the one that we developed first, is running okay. The other one is not, but I attribute that to the fact that we are still in the rollout process, and it's still in the early stages of development.

In terms of ROI through scaling, one of the processes we automatated with BPM is running smoothly with fewer people than before, and in fact the size of the demand has scaled, very notably. We haven't calculated it yet, but it's really returning on the investment.

I think it will meet our needs going forward. And they better make sure it does.

Support is good. They had to escalate internally, in order to get some more expert advice internally, but it was okay.

We've been helped by IBM staff, but there was no problem there. We used BPM on Cloud for development, testing, and pre-prod, and we used the on-premises for production, and everything is working properly.

We're looking at automating and digitizing our processes. There are two use cases. One is centralization of account opening. That has been out there for just over a year. 

The second process that we picked is the consumer loans process, the loan approval process, the whole loan application. The loan application process has just been automated, so it's been there for about two or three months.That is what has been put on the BPM tool.

So we use it primarily for managing the workflow of the loan application or of account opening for a new customer who walks into one of the branches.

So far, the tool is fantastic. The challenge has been for our people, I think the ability to realize that the tool is only as good as the thought that you put behind it. So what my team ended up doing was using the existing process and putting it on the tool. Based on that, now they've realized that using the tool means there is an opportunity to rethink the process itself, as well. That's what we're going to go through. But the tool itself, the experience was fantastic.

We're not using it in conjunction with any other IBM products. This is a standalone application that we're using.

In terms of the process automation and the workflow improvement, although, as I said earlier, we did not re-engineer the process, just the fact that there are lots of times when there is back-and-forth between the branch staff and the back office staff. So all of that, now that it is all automated on the workflow, has significantly reduced the turnaround time for the loan application. Previously, if it used to take anywhere between 10 to 12 days on average, now it takes between two to three days on average.

There is a component of this BPM pool - I can't recall the name. What it does is, it allows you to create various scenarios and then run them quickly, before actually putting them onto a tool. So I think that part of the tool is really fantastic, because that enables you to create scenarios, create simulations, before actually going out and putting it into the tool itself.

At this point, we're still going through the process of exploring the features that we have. I think we're far from the stage where we can talk about new features.

So far, we have not put huge volumes onto it, so it's been working fine. I am not sure how it will behave when we put really large volumes onto it.

We will be scaling it up, especially on the account opening side, because we do end up opening about a couple of a million accounts a year. So yes, we will be putting it to scale and we'll be seeing how it goes.

So far, we've been doing it in a couple of hundred branches, we wanted to do it in a controlled manner. But starting in about the second quarter this year is when we're going to put it to test on a mass scale and we'll see how it goes.

In terms of scaling, it's not like you can see the return on investment in hard dollar terms, but just the fact that from a customer experience perspective, if you can turn it around in two days instead of 10 days, by default, that should hopefully translate into more loans that we book, better customer experience, and better word out there in the market. Obviously, you can't put a dollar value to that itself.

The technical team was fully involved in the process, and it was a fantastic experience.

I wasn't involved in the setup personally, but my team members were involved in it. I have seen the tool itself. It wasn't that complex. I think it required a little bit of programming understanding, but by and large it was reasonably easy to use.

We worked directly with IBM itself. They're the ones we deal with. We are the largest client for IBM in Pakistan, so IBM works with us directly.

Regarding when we implemented it, we should have started a few years ago. It's automation, digitization. I think the earlier you do, the better it is.

I think it's worth looking at the IBM BPM solution. Certainly, when it comes in combination with the other tool that I talked about, where you can do a simulation, I think it's worth it. One should certainly look at it.