Installation was quite difficult, requiring specialized expertise.

The initial setup was pretty easy. There were not any complications involved in that.

I rate the initial setup a six to eight out of ten. It is not very easy to set up. If you have business analytics, there'll be some notifications, and if your new developer knows some technology stacks, it is not difficult.

The initial setup is not difficult, but it's not a stack commonly used by developers, which is a big minus because it is difficult to hire developers for this product.

IBM BPM is easy to deploy. We used the CI/CD method for the product implementation. It enabled automated processes.

The initial setup is complex, but once we have a mature framework in place, it has been working well. When deployed properly and as expected, customers are happy to use the solution. However, there is still a lot of configuration and installation taking time. IBM BPM provides a cloud-fast model, where it is possible to integrate automation of the process and where manual interaction is only necessary if automation is not available. We have implemented an ultimate installation that includes both capabilities, but some features were not enabled in the process access station. For example, I could not open KFC documents, they all uploaded, and saved the data, but could not do a profile page without manual interaction. IBM is still working on a permanent solution for this.

The deployment time depends on the requirements, which can be critical, low, or medium-high. If the requirements are critical, it will take six to eight months. For medium requirements, it will take five months, and for low requirements, it will take only one month. Eight people were part of the deployment team.

Its deployment was good and easy, but the problem was that we were not able to get the people with the right skills. It is not like Java technology for which you get a lot of people with skills. It requires very specific skills, which was another challenge that the client was facing. That's why they asked us. 

We don't own the entire application. We have just done a small part of it. They are now looking at what needs to be done and how they can modernize it.

The product's installation was easy.

When my company gets involved with the implementation phase of IBM BPM, we need to install it in three environments, which are the development environment, test environment, and production environment. In order to install IBM BPM successfully in three environments, my company needs a week.

In the past, my company had IBM BPM deployed on an on-premises model. Recently, my company used IBM Cloud Pak for Business Automation (CP4BA) and deployed IBM BPM on the cloud.

The initial setup depends on if the solution is deployed on the cloud or on-prem. The cloud version is easy because we just have to deploy the containers. The on-prem setup requires a lot of work before we can even begin because we need to masterpiece all the layers from the operations system to the database, and the middleware at the front and back end. I give the initial setup an eight out of ten. The deployment takes a full business day.

An experienced person can do the complete deployment on their own however we usually use three people, one for the beginning, middle, and end.

The initial setup of IBM BPM is complex. 

The initial setup is straightforward and easy. I would give it a nine out of ten.

The deployment can take one to two months depending on the company. We have a deployment team of four people including an engineer, an architect, a technical support person, and a project manager. For maintenance of the solution, we have two staff members.

Its installation is complex for the new version.

The initial setup is definitely complex compared to other market comparatives.

The setup is straightforward. However, the debugging was not straightforward.

Deployment was also quick and not complicated. I was not part of the deployment team, but I believe we used an integrator for deployment.

The level of complexity involved in setting up the system depends on whether the business processes are simple or highly complex. Based on our experiences, we deal with the complex setup required for complex business processes. Our team has gained valuable experience in implementing the product and handling complexities with the help of our customer support.

The tool's deployment model depends on the country where customers are located.

The product itself has a feature to take care of the deployment process.

During the deployment process, the first stage involves development, distinction, and protection. In the second stage, servers are deployed on nodes. As someone from the development side, I do not handle the deployment myself. Instead, we install the solutions and configure the environment on our customers' dashboards. After that, we can deploy our solutions or applications on top of it.

We only need a few people to carry out the deployment process.

The maintenance and deployment of the solution are very easy. Also, installation of the latest release is an easy process.

We didn't have any big issues with the network deployment.

We needed two people for the deployment.

Having used lots of software over my life, I would say this one is pretty much on the complex side. Before the cloud version, it was challenging to make sure you've got the right versions downloaded. They had so many different variants with different licensing agreements, and then the patching has to be done in a particular order. The installation has always felt like a homebrew scripting system rather than a really robust installer. It always felt like if you made one mistake, it might take you an hour to back out of it. It was not a very forgiving and intuitive installation.

It was straightforward from our perspective. It was in the cloud, they provisioned the instance for us. However, I think there were some things that we didn't know about that needed to be fixed, and those incidents happened early on. We were a little bit caught off guard. 

We thought there might have been a little more discussion early on about, "Hey, if you're doing this, set it up this way," or some best practices or some guidance that we didn't get. But we fixed the issues and were able to work through that. From that point on, it's been good.

We worked with IBM to implement. I think we implemented it at the right time. I don't think we needed to have started earlier. The business unit that's using it had some overarching projects to look at, in terms of efficiency and improving speed to market. As they were looking at different technologies or process improvements, one of the options was to try to clean up this process. In working with them and working with IT, we landed on using BPM for that. It was actually good timing for their overarching goals. They have other projects in flight that will work in parallel with this to hopefully reduce the time to market.

The initial setup is kind of a pain when compared with other solutions like Comunda, which is more or less like plug-and-play and quite easy. The solution is quite quick in terms of IBM, and it's a bit more complex. Especially if you're talking about having a more enterprise environment, it becomes a bit complex. You have to configure a lot of additional components from that infrastructure to make sure it's running okay, and sometimes it becomes a bit complex.

The initial setup was complex and can be made simpler by starting with better documentation.

The configuration and installation are easy. The deployment took around one to two days. 

The tool's deployment is complex. 

I rate the setup a seven on a scale of one to ten, where one is difficult, and ten is easy. If you are using the UI to do the installation or setup, the rating would be nine. But if you're using shell commands on AIX or Linux, I think it should be almost two or three since I did the shell commands for the services. It also included some server performance tuning and stuff, like, database connections for BPM databases and all such things. It's not easy.

Since I am working in the banking industry, the tool is deployed on-premises.

The deployment takes around two days since there is a need to prepare a development environment.

One person can do deployment with help from a database person. Some database scripts should be deployed on Oracle or Db2.

The initial setup and deployment are really easy.

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.

The initial setup is of medium complexity.

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.

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

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.

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.

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.

The initial setup was very complex. This was back on IBM BPM 7.5, so they had just converted from calling it Lombardi to IBM BPM. It was new infrastructure for us. We had some security and infrastructure constraints unique to the product that we had to work in. We did not previously have a huge WebSphere or Linux presence. We had some custom code at the beginning, but we have mainly moved away from that, and are pretty much out-of-the-box IBM BPM at this point.

It wasn't complex. Putting an app on is quite easy.

The initial setup is challenging. However, once it is done, it's done. It's not hard in the sense that you don't have a lot of other things to do. 

Right now, we are integrating from Cloud Pak. The cloud makes it easy to handle, and we have the help of IBM engineers. Once again, you do it once, and it is done. After that, you are just using it.

I'd rate the initial setup a two out of ten in terms of ease of use. That's in terms of IBM in general, as we have a lot of IBM products. This product has a generally much easier process, however, IBM is hard. 

The initial setup of IBM BPM is easy to do. The implementation time depends on the business that the solution is being put into. It typically takes six months to one year to complete the process. For a deployment that is easy, the process could take only a few hours.

The setup was quite complex because the solution was cutting-edge at that time and IBM invested considerably in the implementation, likely at a loss to themselves.

It is easy to install. It only took 10 to 15 minutes to complete the installation.

The guides are available on social websites.

IBM BPM is one of the several BPM tools that we are working with. Currently, our technical team is working on 50 to 70.

While the installation of the solution itself was straightforward, the customization wasn't straightforward for us. It was too complex, and the training we received did not help us understand the solution. We needed to be experts and we weren't.

The initial setup was quite straightforward.

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.

I was not involved in the initial setup. It was done in-house.

It is straightforward.

Everything is complex. There's no easy-peasy. Intelligent process automation becomes a complex matter. Most people are terrified of moving from their on-prem into the automation and digital transformation. 

We often times will map out according to what we've done in the industry. There is nothing simple, everything is very focused on a true partnership with our customer base.

It has improved a lot. They built some tooling for the BPM platform in particular, in the releases that started about three years ago; they streamlined that quite a bit, it is quite a bit better.

It is still a massive installer compared to some of the heritage software that it was built from. It's quite large and it can take quite a bit of time to install. So that definitely could be better, but it is what it is, it's an IBM product.

Regarding working directly with IBM in the setup, if it's not an IBM project, usually I don't, because I'd have to pay. If it's actually an IBM customer then I would. And I do, sometimes, informally talk to some of the people that I know about what is the current latest and greatest way to handle certain things, but not so much in formal channels if it's not an IBM-direct engagement.

I would say it's medium-complex. It's not highly complex but, yes, since there are a lot of integrations, it's kind of complex.

The tool's setup is neither easy nor difficult. I would rate it a five out of ten. However, it is difficult only in the traditional environment. Set up is easy if you move to the cloud and containerize. One person is enough to handle the tool's maintenance. 

From a user-friendliness perspective, I would rate it as a six out of ten. There was definitely a learning curve to adopt the tool and understand all of its features, but once learned, it was a very good tool for that period of time - about four or five years ago.

The initial setup was easy but using it after became a bit challenging. Deployment took about one day, and we are a big organization.

The initial setup takes three days. It can be a bit complex. 

I was not personally involved in the initial setup because I am in operations. The initial setup was driven by our architects. However, the environment, as the first shot, was completely done under the guidance of IBM.

In terms of timing of the implementation of BPM, I would have liked to have had it 10 years earlier.

It's a simple setup.

The solution is complex to set up. However, you expect this going in. It is a huge application. It is running on a WebSphere Application Server. The WebSphere Application Server is an application server, and therefore, you need to set up this application server first and then to set up the BPM solution. After that, you need to create profiles and so on. There are multiple and sizable parts to the implementation that have some very problematic steps. On top of that, if some error is happening with these steps, we will have a problem. 

On the other hand, you really have a huge and powerful tool at the end. Therefore, you cannot expect the tool will have a simple setup or simple installation and to have all this functionality that you get with IBM BPM, especially with IBM Business Automation Workflow that you ultimately have.

Basically, for first installation and customization of one small dev, test and prod environment  you will not need more than a week.

If you have old version of BPM and olready finished some appps, and you need to upgrade it, then it is a bit more complex, due to the fact that you will probably have problems with the application if these applications are developed in an older version of BPM. Instead of only upgrading software, you will need to convert the application and sometimes it could need some time.

The initial setup is fairly complex. Luckily, we have a few people in our company that know how to do it. It is just a question of having the right resources.

We implemented the solution at the right time for our company and customers.

Setup is a little more complex. But with the support of platforms on cloud, we love that, our customers love it. This becomes so much easier. We provision an environment and now we start building business processes or the application immediately. We don't worry about configuration.

Installation for on-prem used to be a one-time activity for engagement. And we may not even mentor a customer on that, because all they really care about is building processes. With the cloud, it becomes just a push of a button to provision it.

I think we had some assistance from IBM, for a few months. After that, in-house, we pretty much took care of handling it.

The initial set up was easy. The challenge was in adopting it into the release and deployment processes that we have in-house, what we have to follow for the healthcare industry. There was a little bit of a challenge trying to figure out how to take the process and put the appropriate release management processes in place to follow our auditing compliance.

We have ironed that out now and we are able to develop and showcase the product much faster when we compare it with something like Pega. Pega has a process engine that we use. Our development times are much faster in IBM BPM, as well as the pricing is even better than Pega.

The initial setup is very quick. 

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

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 worked with IBM for the initial setup.

We have a team who worked initially on defining the solutions, getting the business needs, and getting all the technical documentation for it to be implemented. I personally managed the development team to develop these workflows and put them into production.

It was not hard to set up. It was more tweaking and optimization going forward, but the initial setup was not an issue.

With these workflows, there are people like the data steward who work on them, so it is not really initiating new workflows. There were workflows that already existed, but maybe in an old fashioned way.

This tool fits within the data strategy at the bank. It was part of our roadmap that we worked on for the last couple of years. It was at the right time. It was for the right context as you need a sponsorship from the business and from the Chief Data Officer, so all those things came together to move forward with BPM, MDM, and different platforms.

Like I said, IBM BPM installation and configuration, migration, and upgrading can be a bit complex because you need to deal with a large set of data that involves databases. And product metadata always needs to be in good shape.

The solution's initial process is straightforward for professionals. It is complex for basic users.

With the business process tool, it needs to be customized according to what the clients want. So, complexities will be there.

The initial setup was straightforward, especially on the cloud.

The initial setup was a combination of straightforward and complex.

I have never installed the solution and am not aware of the process involved. 

The initial setup is complex. It takes several months, and it requires expertise from IBM technicians most of the time.

Its initial setup could be improved. If there was a way to set it up in two or three clicks or there was a way to create a space or cloud infrastructure that can be available in several clicks, it would be a product gain. It would be nice to have something available as platform-as-a-service (PaaS) in cloud infrastructure. I don't know whether this functionality is currently available because we have stopped investing in this technology. 

The initial setup depends on your environment. If it's a standard implementation, it is out-of-the-box and could be done in a two hours. A more complex environment could be more difficult to set up.

The initial setup was complex.

We have several customers with different companies, like banks and hospitals, so it depends on the target, the project, and what features they want to implement. A typical project might need three to nine men per year to deploy.

The initial is not complicated, and it's not easy; It's medium.

Very complex. Too many steps need to be done at the database and server levels, and complex configurations. From what I see, a lot of these steps can be and should be automated.

Sometimes, after updates, the modules did not work and we had to remove the application and deploy as new.

It was a little complex.

The initial setup was straightforward.

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.

As I recall, the initial setup was pretty straightforward. We found it to be rather easy.

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

The initial setup is quite simple and user-friendly to perform.

The configuration is not that easy, and the initial deployment took three months. I'd give my experience with setting up a rating of three out of five.

The initial setup was straightforward. It's automatic, then you compress it.

It took us around one day to install it. 

IBM BPM's deployment is not complex; I rate it a six out of ten. It takes a day to complete. One admin helps to maintain the product. Our server count is between 25 and 30.