IBM BPM Reviews

We use it for the approval of mortgage insurance. 

It has reduced a lot of manual errors and processes. 

The process flow. The BPM workflow that we use goes through the underwriting, approval from the managers, then it needs the loan approval.

We would like better performance and more visibility on each step of the tool.

It is pretty stable. Sometimes we have performance issues. Otherwise, it is good.

We have two nodes in the cluster environment. This is the scalability that we do have. If we need to increase it, we can add a node to the cluster.

The technical support was helpful when I used them.

In the beginning, we had an IBM BP3.

The initial setup was straightforward.

We worked with a business partner to implement.

It gives us a good return on investment.

It is a good product. I would recommend it.

Most important criteria when selecting a vendor: 

• Support
• Pricing
• Licensing issues.

We are changing the major database in our financial sector. We moving to a paperless process and added a risk engine to make the decision for each loan. 

We use it to evaluate each loan. We have people doing the evaluation of each loan and use BPM to accelerate the process by having metrics between tracking points. We are use validation on the screens to avoid errors. 

We are also using ODM and Avast Enterprise Business services. 

• It controls the risk. 
• We reduced the PCL (credit losses).
• Its efficiency in reducing costs. 
• We are going from a paper to a paperless process.

In the future, we would like to reduce the resources used to manage the process. 

Controlling the operation. We have metrics about fraud, risks, etc. 

We like that it does not require a lot of hours to train our people. 

More customization. We like to customize the screens to show more things related to our company. Customization is very important for us; the complexity to build a solution. We need to make changes quickly, and sometimes the IBM team is very slow with the product evolution or changes to the tool. 

It is performing very well. We are building the solution right now and launching in August.

We are moving to this tool because we have more than 40,000 transactions a month, and we would like to triple this amount. 

Our next step is to scale and change the repayment process.

The technical support is very good. We are with an IBM partner.

We contact technical support because sometimes we have problems with our IBM servers failing. The support is always responsive in fixing the issue.

We did not have a previous solution.

The initial setup was complex. It is not always easy to launch a new platform and it needed better coordination with IBM.

We worked with a business partner to implement the solution. We worked with a business partner because they know how to implement solutions in each market. I am from Latin America, and this partner knows our market. Four years ago, I worked with IBM New York and it was difficult to apply these market solutions in Latin American. However, with this partner, they are aware of our market in Peru. 

Start with a PoC. Do small changes, then take a step back and grow with the platform.

Most important criteria when selecting a vendor: Experience, teamwork, and resolution, because any project has its complications. We want a partner who will resolve these problems quickly. 

We use it for human resources and insurance companies, who use it for their recruitment processes. It has been performing well.

Our clients use it for recruitment. There is a big recruitment process for each department. When they recruit somebody, the IBM BPM solution has a work process:

• If he is commercial, rent him a car or a phone.

• If he is only technical, there is a process to have a desk or a laptop.

We use BPM in conjunction with IIB, IBM Integration Process.

• It provides value. 
• Reduces time.
• Simplifies processes.
• Names are correct during the recruitment process.

We need process monitoring. It is somewhat complex to monitor all the processes which work.

Stability is perfect.

Scalability is perfect.

We have not used IBM technical support.

Our clients were previously using Excel sheets for processes. It has changed their whole life as now the processes are all automated.

It is easier than WPS, which used to be the BPM product. IBM BPM is easier to implement, easier to deploy, and easier for the business people in the company to use the processes. 

We implement the solution on behalf of our clients.

Previously, there were human errors when they entered names. Sometimes, when they ordered a laptop for somebody, they ordered it two times because the first time the system did not acknowledge the order under the incorrect name. Then, they did not know it when through and received two laptops. They ended up having to return one of them, and this had a cost. 

This is why the product's ROI is so quick. 

We help our clients select three products, then afterwards we work with them to select a solution. Other than IBM, our clients often choose Bonitasoft, which is an open source product, and TIBCO BPM.

Most important criteria when selecting a vendor:

• A proof of concept
• Our certification of IBM products
• Our added value on these solutions
• Other customers' recommendations.

The product causes all the processes in the company to be centralized. It helps with process efficiency.

It makes the company business processes work more efficiently.

All our clients are changing to microservice and cloud service. However, BPM does not have a solution for microservice and cloud service.

It needs more integration for API management and cloud services. Also, it could maybe use a connection with microservices. 

BPM is very stable.

It is scalable.

I have not worked with IBM technical support for BPM.

I do the installation, configuration, and integration for my clients. It is usually a little complex.

As a bank, any business processes which run on it:

• A treasury application
• A lost and stolen credit card application
• New accounts, etc.

There are many use cases that are now administrated through one BPM processor.

It has performed pretty well. One of the concerns, which is a question of our processes more than the product, we like to do a monthly release cycle and that is not fast enough for some people. Therefore, we have created a separate BPM that we call our DevOps box, which allows them to update it anytime they want. This is in production.

We use it as a combination of machine processes and human processes. There is a workflow, then somebody kicks it off and enters the data. Some decisions are made automatically, and other decisions are made by human beings. Just the mix of these two makes it a good combination.

We are incorporating ODM to some degree.

We are creating a new box because we have all these forms. They have to be signed, therefore we have not been able to take advantage of the ease of deployment. However, we now have separate boxes, which do not need all the same approvals in order to get something into production. You can just put it in whenever you need to.

I like the Process Center. I can go to one place and view what all the environments are doing, the ease of deployment, etc.

Stability is good. We have had a few problems, but IBM has helped us to resolve them.

We had a weird problem that whenever the database would go down, even for a few seconds, it broke the connection. It would not come back up as it was supposed to. However, working with IBM, we were able to figure out a fix, then it came back up, even after an interruption of the database.

Scalability is good. In the time that I have been there, we have added more JVMs to help with the increased workload, so it does scale.

Technical support is good. They are very responsive. It is usually me who takes more time to get back to them than they take to get back to me, which is good.

We did use Oracle for a little while, but we did not like the Oracle BPM product.

IBM BPM allow us to streamline manually processes.

I have been involved in the setup of this new box (DevOps). I installed and configured it, but I did not do the original install. I did the new install, which was complex. However, the documentation is good, and we did it pretty much without incident.

We did the implementation directly with IBM.

Try it out on a small scale. Do one project which is relatively simple, then work out the bugs this way. Do not try to put too much in it at one time.

Most important criteria when selecting a vendor: We are a bank, so security is extremely important. We are looking for someone who is going to be here a year from now, and someone who will support us. 

The number one thing is support. If we are down, we want somebody helping us now, because we can't be down.

Implementing and automating business workflows.

We use it for automating certain processes which previously took a lot of time for agents to set up different products for customers. They would have to enter a lot of different systems. This has now mostly been automated.

It is running okay, though we have experienced a little instability lately.

We have been experiencing bad performance and instability. 

We can scale by increasing the infrastructure which is currently running. 

We are receiving good assistance from the technical support.

We previously used the very early workflow engine from IBM. 

IBM BPM is a more modern tool than what we used before. 

The initial setup was a combination of straightforward and complex.

We implemented with IBM's help.

Contact IBM and let them help with the process.

Automating business processes to reduce the amount of people in the business.

For example, when policy participants go on pension, then we automate the process by sending letters automatically, setting reminders, etc.

By automating several tasks, we have already reduced a lot of work for the business.

We made the transformation to agile. Altogether with BPM, it is the total package.

Ease of use.

Consider an admin console during deployment. I would like to migrate single instances, not the whole bunch at once. 

Stability is mostly good.

Scalability is pretty good.

Technical support is pleasant to work with and always available.

We already had a bunch of WebSphere applications running, and have competence in it. BPM running on WebSphere allowed us not to have to build a completely new support team.

The initial setup was complex.

It was setup mostly by IBM.

At the moment, due to a takeover, we are evaluating between TIPCO and BPM (which we love).

Build in phases, then extend afterwards, piece by piece.

We use it for an insurance process. IBM BPM automates the processes. We use it for handling all the human tasks, people who were doing repetitive tasks, the tasks are now done by BPM.

We don't use it in conjunction with IBM Case Manager or any other IBM automation products, yet. But we're looking at the RPA stuff.

For our company, it's cost reduction.

What they're doing right now with RPA is a a good move.

There are some things, but nothing off the top of my head. I would have to think about it.

Stability is good. We've never had any downtime.

The scalability is good for us.

We have seen ROI from it, I don't know the numbers.

Tech support is satisfactory. There is good competence in IBM Lab. 

It was complex, but fair, since it is a complex thing. We worked both directly with IBM and with a business partner to implement it.

I think we implemented it at the right time. I don't think we needed to start earlier.

When looking at a vendor we, of course, look at the price, but also for technology, since we are one of the few customers in the Netherlands using IBM BPM.

I would recommend it.