The initial setup is not so difficult to use.

It's at the medium level. For on-premises, we have to install a server separately and the bot environment separately. When it comes to the server, we have to configure a database in MS SQL Server, and we have to create five to six databases on the server side, and the bots and the servers communicate using the Microsoft Messaging Queuing system. 

The initial configuration took about two to three days because I had to enable a few ports. In the client environment, every port was closed, so we had to open a few ports for the API and other layers. They have an inbuilt OCR tool, and for that one, we need to expose the APIs.

The setup process for IBM RPA is very easy and clear. The documentation is clear and concise, and our customers can easily budget for the costs without any surprises.

The initial setup was straightforward.

The initial setup was straightforward. It takes one hour to deploy.

The initial setup is very easy. Sometimes our customers experience a high setup time during database creation. It takes only one hour to set up if you're prepared with databases, rows, and access to the database.

I would say that the initial setup process was super simple. Our model of deployment is on-premises.

It was pretty straightforward. The packaging of the solution was pretty straightforward to just deploy. We're running it actually on Azure, on our cloud services, so we were able to get it up and running, I think literally, within less than half a day. It's also a PoC environment, but just getting that up and running was simple.

The initial setup is very simple. The learning curve is easy.

We work with the presales teams and have not had much experience with the setup.

The length of time required for deployment will be two or three months, depending on the infrastructure. When you have an on-premises deployment, you need to prepare the infrastructure to perform the implementation. There are times where the initial setup takes longer than you first imagine when the project begins.

For example, having availability with the client's infrastructure in order to start working on an RPA project is sometimes a problem.

The cloud is the best way to deploy RPA. However, we face the dilemma that we cannot use the cloud. So, I think that the solution to this type of problem is to try and set up a private cloud for our clients. Unfortunately, I have found that it is not a simple process to set up a private cloud. The number of resources required is not necessarily reachable for many entities.

I think it's complex, and not straightforward.

The initial setup is straightforward. The setup can be done in an hour.

I did not find the initial setup complex. I would describe it as easy. It's very straightforward.

The initial setup is straightforward. I don't think there are any issues with the product usability.

I think it is more about the features: How we leverage them, then how we apply them at scale in our enterprise. There is a lot more focus on change management when you are bringing robots in, e.g., people start getting concerned about losing their jobs. 

The setup is a little complex as compared to Blueworks Live but it is not as complex as IBM BPM or IBM ODM. From a structure perspective, you still go through creating your three layers - your Bot Creator, Bot Runner, and your Control Room - along with the database. So from a structure perspective, you're still going through the same stages, but the tool itself is so small compared to the size of IBM BPM that it's not very difficult to install. Typically, we allocate two days for installation, which is about 16 hours of effort to do the installation in a test environment.

The initial setup was not complex at all. It took less than an hour to set up the solution. 

We were able to put up a solution, like set up a port or create an application, in such a short time from the ground up. We are able to run this and put it in production with minimal effort required, and that is a big deal for us.

The product was easy to deploy.

The initial setup is complex. You need to first find out where and how it can provide real value to the company. Without doing that first, without understanding the main objective you are pursuing, it can take a lot of time to show a company that this product delivers real value. 

Once you understand the final objective, you can design and implement it. The implementation really isn't a big problem once you have well-defined objectives that you need to achieve.

The setup is generally straightforward but can become complex based on your execution plan.  

The initial setup is straightforward. We have used various versions of automation solutions in the past, so we understand the whole setup process.

I have found some of the deployments of IBM Robotic Process Automation are more difficult than others. Some deployments can take a few months.

It's a client terminal solution, so the desktop solution doesn't require much time to install and deploy.