Robotic Process Automation (RPA) Architecture Reviews

Showing reviews of the top ranking products in Robotic Process Automation (RPA), containing the term Architecture
Automation Anywhere (AA): Architecture
Pratyush Kumar says in an Automation Anywhere (AA) review
Delivery Manager, Robotics Process Automation at a retailer with 10,001+ employees

In version 11.3, the setup changed. So far, it has been simpler. Also, in version 11, they have changed the design into a Java Jetty architecture, which is more stable. However, we were not familiar with it, so we had some issues with it. Thankfully, Automation Anywhere diligently answered our calls and helped us through the installation. It wasn't easy to install on our own using the guide. We needed support from a technical entity from the support site to be able to do it.

It needs a lot of coordination between the DBAs, which is a separate team within our organization, the infrastructure team, our team, and the Automation Anywhere teams to execute the deployment. Getting them all together was a good three hours exercise just to install.

Two people from my team worked on the deployment, one of them being a DBA.

View full review »
Sharad Soni says in an Automation Anywhere (AA) review
Director Of Innovation at Quantum AI

It's a very dynamic market and everyday new tricks are being discovered. My advice would be: Look at your process. If your process is screen-based, doesn't have a lot of things to do with APIs, go for Automation Anywhere. If somebody's looking specifically to implement Automation Anywhere, irrespective of what process they're automating, I would probably call it a bad move.

Role-wise, we follow our own system. We have a solution designer and we have an architect. These two guys work hand-in-hand, from solution design to a technical architecture of the Automation Anywhere bot. Then we have developers who develop the system. And we have the leads, of course, who are managers. They are senior staff who understand how the bot code is to be published and released into the Control Room. Most of the time, it's the solution designer and the architects who are critical for us, rather than the developers. The development part is easier than the design part. Designing automation takes a lot out of us.

In our organization we have 42 people, and most of these are multi-skilled on multiple tools. We do only specialized stuff, so some 20 of them would have been working on Automation Anywhere at some point. We use multiple tools. We are tool agnostic. We figure out which tool to use and go with that tool.

We don't have plans to push future usage of Automation Anywhere, most importantly because of extensibility of the tool: I can't extend it. So we created a workflow tool for ourselves similar to UiPath, but it's open to extensions. I don't see a lot of projects happening on Automation Anywhere for us unless the customer asks for it. In the Asia-Pacific market, it's either UiPath or Automation Anywhere. If they don't have a tool then, of course, we'll have to look at the type of project and recommend a tool.

I would rate Automation Anywhere at seven out of ten. The architecture is great. It's only the way they have tried to protect their own bots that is causing them to cannibalize themselves. Otherwise, it is great software. It works on a domain-specific language. You really don't need to understand .NET or Visual Basic or C# to work with it. The domain-specific language is more like English. They have done a great job making something, but there is a big scope for improvement if they want to really unsettle the other guys.

In my opinion, instead of sitting in their offices and not conversing with people out there, there are a lot of things Automation Anywhere can do if it listens to the people who are actually evaluating it, using it, and are happy or unhappy with it. I don't really see a mechanism where Automation Anywhere can be seen listening to this feedback. Secondly, they should be more open about their roadmap and where they are going with Automation Anywhere. What I want them to do is to make some more noise about their plans, rather than their current situation, because customers are not looking to buy Automation Anywhere for the next three years. They're looking to buy it so that if their processes change or if Automation Anywhere changes, it can still be usable for their organizations.

I can't keep on changing tools. Let's say I use Automation Anywhere where it's obvious and then it becomes unsuitable, so I have to change to another tool. That rarely happens because the users are familiar with it and change is the biggest barrier. People don't want to change. And the cost of training is actually more than the cost of the Automation Anywhere tool itself. You need to train different people with different skills, not only in Automation Anywhere but for every tool. You need different skills and different people to actually make the whole thing work.

View full review »
ShripadMhaddalkar says in an Automation Anywhere (AA) review
Director of Operations at XLNC Technologies

Other tools tend to give me exceptions when I am scaling them on the cloud. While the infrastructure might be available, systems won't be able to talk to each other. The codes tend to miss paths, and sometimes codes are not getting applied in the application. However, with Automation Anywhere, we haven't seen any such issues until now, wherein large scale developments are being found to be unstable. 

The good thing about Automation Anywhere is the website has a detailed architecture which talks about having a load balancer and how you can scale up. 

Currently, I have been working with clients in the US and Dubai through remote support. I have been developing bots remotely where I have been able to access their virtual machines. The virtual machines are separate for creators and runners. I have around six creators on virtual machines, which is good enough to start off. There are around 25 runners which are deployed on 25 VMs. This is in US. That's how we are operating them, and it's the largest setup that we work on.

In India, clients start small. They start with a starter pack, which is only allowed to be issued by an implementation partner. If you go onto the Automation Anywhere website, there is nothing called a starter pack. So, organizations will tend to start small with a starter pack, which may come in a bundle of two or three creators, one runner, and one controller. They want to test how it is functions in their organization. If they can pick up low hanging fruit, which means if they're picking processes which are smaller but high in volume, then they will have higher ROI. Then, these organizations tend to jump onto an enterprise level deployment in a maximum of six months. That is the trend that we have seen. 

However, the moment the client starts going big and is not able to get the right ROI in place, that's where they tend to start dropping the ball. Then, they start looking for another RPA software or decide RPA is not for them.

View full review »
Brian Walling says in an Automation Anywhere (AA) review
Global IT Director at a logistics company with 501-1,000 employees

We didn't use Automation Anywhere's technical support, even for deployment. We read and learned what we needed to know. We got on their support site, got their documentation, took the requirements, how to deploy, and what the right architecture was. We scaled based on what we thought we would use it for. My guys like to learn, they like to try, and I allow them to dig a hole and fall into it and then fix it later. They just didn't fall into a hole.

The documentation was good enough for us to read. Granted we're technical people, but it was good enough to read and take actions based on the content. It was really good.

View full review »
BPM Analyst at a financial services firm with 1,001-5,000 employees

The technical support is great. I have worked with a couple of different people who have been absolutely phenomenal, helpful, and have solved so many of our problems.

When I have a serious production support issue, if I need to escalate it, I usually receive a lot of good help from some great people to get our problem resolved. Sometimes, it takes a while, but I get it. Everyone's environment is different, and it's hard to know everything about how everyone has their architecture setup.

They've started up a user community recently. I haven't investigated that much. I really want to do that, but I always thought that a user community where the users of the product always get together, talk, sort of brainstorm, and come up with other suggestions for the tool would be great. However, I believe that has just been started. I just haven't had a chance to go look at it yet.

View full review »
Will Haskell says in an Automation Anywhere (AA) review
Supervisor at a energy/utilities company with 5,001-10,000 employees

The initial setup was complex. However, Automation Anywhere came onsite and helped us with our architecture, then it was fine.

View full review »
Solution1ddf says in an Automation Anywhere (AA) review
Solution Manager at a financial services firm with 10,001+ employees

The installation of version 11 is fairly straightforward. I do like the new server architecture based on Java, as it is very straightforward.

View full review »
ProcessAb41f says in an Automation Anywhere (AA) review
Process Architect at a media company with 5,001-10,000 employees

My current and previous companies have had stability issues. 

I started on version 11 of Automation Anywhere, then when I joined a new company, they used version 10. Therefore, I have seen both versions. With version 11, some of the development stuff was a bit clunky in terms of the tasks that we were performing. They didn't perform as expected, or perform properly, when we were developing the bot. Then, once we deployed it into production, the bot would run for a specific process and work properly about 10 times, but on the eleventh time, it would break. It was always random. Nothing had changed at all, in regards to our system, architecture, or infrastructure.

On version 10, things had been a bit more stable. We made sure that we build code which effectively captures all use cases and exceptions, but stability is key. When you're building automated solutions using bots, people are already skeptical and hesitant to adopt them. Anything you can do to improve the stability is definitely helpful. Ultimately, it depends on what your goal with RPA is. If you're using RPA as a stop-gap to build large-scale system integrations, then it's very helpful. If you're using it as a be all, end all, then stability is your number one concern. 

View full review »
vphead09866 says in an Automation Anywhere (AA) review
Vice President & Head of HR - L&T Defence at a tech services company with 10,001+ employees

The stability has increased a lot. When we started with version 10.2, there was a lot of instability. There was no way we could keep the bots active, there were scenarios where it became disconnected. There is also the code deployment perspective and a lot of other angles. People are always only thinking from the business perspective, but as a technical architect, I think about operational effectiveness and how they can improve the product's maturity.

The stability has improved a lot.

However, when upgrading, they changed their internal architecture. They moved it to a JT Java platform. When moving, some of the existing features did not work in the new version. It might be that they have to improve their regression testing to improve clients' satisfaction. It can happen that what is running in production currently, if I move to a new version, suddenly is not working tomorrow. People are not happy with that and say, "I want to roll back to the older version." They are not able to use the new features.

When moving to a new version, they have to think about what features people are using and what kind of impact there will be. Small business users will be fine, those who have ten bots or 15 bots. But there are organizations like mine that have around 700 to 1,000 bots, and that makes changes very difficult to handle. It could be that 10,000 tasks are using something and if that thing is changed it will be hard to update. I might have to spend a year on that. People will never accept that.

View full review »
ITDirect5fd0 says in an Automation Anywhere (AA) review
IT Director at a tech services company with 1,001-5,000 employees

The architecture allows us to scale. We are still working to get it to a right level of scalability for our environment.

View full review »
BIManagec9cf says in an Automation Anywhere (AA) review
Business Transformation Manager at a maritime company with 10,001+ employees

We have had some difficulty with ease of use. As far as getting the overall architecture setup, we had a lot of difficulties ensuring the control room was installed correctly and that we were setting up our runner machines correctly, as well. Some of that was due to our own IT not being fully up-to-date on the process and being properly informed. We also just found the install procedures somewhat cumbersome to use. In addition, we have had some difficulties getting it to interact in predictable ways with our in-house software.

We would like a smoother process for moving bots and tasks between the different development environments, from development to testing to production. We find this to be pretty cumbersome to work through.

View full review »
Alexandre Dusseault says in an Automation Anywhere (AA) review
Technical Lead at a financial services firm with 10,001+ employees

The person who is working on our architecture is not always available.

View full review »
BPM Analyst at a financial services firm with 1,001-5,000 employees

The stability is pretty good. In all fairness, I know we went from version 10.5, where we thought we were fairly stable, and we did have some issues. Then, we migrated to version 11.2 and encountered some other stability issues around scheduling things. But, after talking with some Automation Anywhere techs who were extremely helpful, we have recently, as of last week, upgraded to version 11.3.2.1, and that seems to have solved some of our problems.

We are still testing it. I still need to do some checkups. Obviously, I'm here this week, so I'm not doing it right now. Generally speaking, it is stable. Knowing what it's trying to do, I think 100 percent stability with everybody will be different. Architecture and environment are going to be pretty difficult, but they do a good job.

View full review »
Bill Weathersby says in an Automation Anywhere (AA) review
Board member at Transform AI

If you write them correctly and have good architectures internally, then scalability is relatively straightforward. This also applies to reliability. However, you sort of need to write a few before you get to this point. As more of these go to production, these are going to be the two big drivers.

Probably one of the faster scales that we have done is we did a prototype with IQ Bot that had about 500 invoices and a 1000 vendors. In about two and a half to three months time, start to finish, we went from the original amount to 15,000 invoices and 2500 vendors. I would suggest in that 90 to 120 day time frame, if you have done things properly and your architecture is good, that you should be able to scale at any pace that you care to.

View full review »
Kalyan Bitra says in an Automation Anywhere (AA) review
CTO at Sage IT

The ease of use is one of great assets for Automation Anywhere. I would want it to be continued in this fashion. Of course, there is still always room for improvement for any product, but we do that as well.

On the tools' side of it, when I look at it, a lot of commands have ease of use with every task, whether it is Excel or PDF, each are commonly used tasks and automatically available to you. Again, there are some that we may to develop.

I went through most of the Automation Anywhere courses: Architecture courses and even RPA for the business user courses. The courses are very good. It also gave me a very good perspective. The only thing that I would recommend on top of it: Getting the community to grade how much better each course is. At the end of the day, when we publish courses, what's the impact of that to the customer? It's not there. If that comes up, that would be good, so some the more popular courses get more time than other courses, which are really important, but do not get that much visibility.

The bot creation process: They said we should not look at it as a technology as the first thing. I would say technology the least problem that we have. I would first look at common sense: 

  • What is the bot actually doing? 
  • What is the task or workflow which you are trying to automate and is it actually doing it? 
  • What is the value that is actually getting to the customer? Or the impact that it is having on the customer? 

That's very important to identify. That is what it gets you the ROI, etc. You have to look at those aspects of it. 

The second aspect of it, how can you make it ease the pain? For example, if some customers are using the process, and I know to whom to talk about process, then I can determine when it is a bot, system, or mission. We have to make sure the bots and humans are working together and smarter. The second aspect that you look at is the design of it, which is very critical. 

The third aspect of it is adoption. That is what I always come back to, whether the customer has adopted it, and whether those in the chain management are communicating to the underlying teams and are right or not. We need to help all of those things. Then, developing the bot with Automation Anywhere is actually a cakewalk. I would call it very straightforward.

View full review »
Sunil Ranka says in an Automation Anywhere (AA) review
Founder at Predikly

People are now trying to automate many different kinds of technology. They have use cases related to ARP, invoicing, and three-way matching, for example.

We are seeing an incremental need for legacy systems which do not have an architecture in place or API integrations. Our customers are doing things like simple website scraping, bringing the data into Excel, taking that data and then putting it into their legacy systems. We are seeing customers that read a lot of invoices.

Our customers have been using Automation Anywhere for a lot of integration purposes. They've been using it not only for process integration but for application integration as well.

View full review »
Assistan620c says in an Automation Anywhere (AA) review
Assistant Project Manager at a tech services company with 201-500 employees

We partnered with a consultant from a company in Sri Lanka and they are assisting us with the implementation. This includes development and scaling. We give them the strategic plan according to what we want, then they evaluate the process and let us know the architecture. We may also get involved with the architecture in cases where they might not have the in-depth knowledge of our systems.

Our long term plan is to have a COE where we will have our in-house developers. This will help in development, as well as post-production.

View full review »
Businessa5e1 says in an Automation Anywhere (AA) review
Business Technology Analyst at a consultancy with 5,001-10,000 employees

The initial setup is a little difficult in the beginning to develop an entire infrastructure that the IT will support, but as you grow, you find a way to develop the whole architecture.

View full review »
AjayPatel says in an Automation Anywhere (AA) review
Consultant at a financial services firm with 10,001+ employees

The initial setup was really straightforward. We spoke with AA about what kind of architecture it needs, and they have created it in a way that is very robust.

View full review »
Vinod-Kumar says in an Automation Anywhere (AA) review
RPA Developer at a financial services firm with 10,001+ employees

I was not involved in the initial setup.

For the bot creation process, we have a solution architecture team. They will analyze the process and check for feasibility before proceeding to next level. They'll check whether the process can be automated, then prepare a document which will come to me. Then, I'll try to make the SDLC. I'll check whether the process is possible, then we'll go for development. This is the structure:

  1. Analysis and feasibility study.
  2. Documents preparation.
  3. Development.
  4. UAT.
  5. Deployment.

There's a process requirement. If I get request today, it will take some two to three months to develop and close the incident.

View full review »
RpaLead259a says in an Automation Anywhere (AA) review
RPA Lead at Juniper Networks

I would rate the solution as a six out of 10 due to the resolution issue. It is a major issue that we are facing with the tool.

Get the approvals done before investing. We wasted the license for six months. The licenses were unused because we didn't have the approvals for the application. We procured it and kept it for six months. Therefore, before investing, get the approvals internally, then go for it.

We have integrated Automation Anywhere with SAP (ERP system) and BlackLine (reconciliation tool). For integrating, we are using web scaping tools and object cloning.

I am certified Automation Anywhere RPA professional with Automation Anywhere University. I am looking for courses on solution architecture and would like to have something for this in the University.

We don't use Citrix automation.

View full review »
SystemsAecf6 says in an Automation Anywhere (AA) review
Systems Analyst at a manufacturing company with 10,001+ employees

When we started, we were not aware of the entire architecture of Automation Anywhere. It was like a new technology. I have a partial technical background, so I could easily understand the tool and its architecture. However, I observed that non-technical team members could also easily understand Automation Anywhere's commands. They way that the bots are built makes it very easy for non-technical people to understand the logic pieces if they have logic skills. They can develop bots. Compared to other tools, where users should have some technical knowledge, this is an excellent differentiator for Automation Anywhere.

View full review »
Mithun Kumar says in an Automation Anywhere (AA) review
Advisory Council Member at a tech services company with 1,001-5,000 employees

We would like a better coding interface for developers. We would also like to have a user interface which reduces the time to learn the product so more people in the organization can use software, like Automation Anywhere, quickly automating processes.

As an organization, we feel the exception and error handling could be way better.

We would like the software not to change as often. Architectures were radically reinvented without informing the customer. This wasn't something we appreciated. 

Some of the stuff being used internally in the product, like Elasticsearch or open source, did not pass vulnerability ability assessment. This is another issue. 

We hope Automation Anywhere takes internal component security seriously as we are looking forward to the Automation Anyway A2019 launch. We hope it addresses some of these issues with error handling as well as component security.

View full review »
Abhineet Sood says in an Automation Anywhere (AA) review
Consultant at Zs

Initially, because we started everything in-house (did not partner with a consulting firm or the typical technology integrators), it was difficult. Then, we started learning the architecture and environment. Automation Anywhere gave us a dedicated support to set up the whole journey for us in the initial few years. It went from strength to strength after that.

View full review »
Harish Bennalli says in an Automation Anywhere (AA) review
Senior App Developer at a financial services firm with 1,001-5,000 employees

The latest version is more stable. We have mostly legacy applications. We do interact with Automation Anywhere support for patches and DLLs which are compatible with our legacy applications. Maybe after our upgrade, we can expect more stability.

In couple of months, we are looking to upgrade. We have set up our environment for integrating in AWS into our architecture. We are setting this up now and planning to install Automation Anywhere 11.3 to see how it is.

View full review »
Gopalkrishna Baskarabhatla says in an Automation Anywhere (AA) review
Architect at Cisco

Our finance organization needed to transform itself to meet the changing business models. We established the finance transformation office to meet the entire organization's financing transformation needs. As part of that, we identified a couple of quarters ago that RPA was one of the software solutions which could help us automate several of our business processes. This is apart from the re-engineering and re-architecture that we do to transform our entire business process. Now, there can be some use cases within finance which can be transformed through usage of automation software, like Automation Anywhere.

We have streamlined several activities, cutting down on manual activities. This has happened over the last six to seven years.

View full review »
Mahaan Pai says in an Automation Anywhere (AA) review
IT Analyst at a computer software company with 10,001+ employees

My day-to-day activity was to take data from invoices and put it into an Oracle DB. I have already automated banking uses, which deal with some of the invoices. The second case solution which I had worked with was multi-bot architecture.

We have certain kinds of applications spread across our organization and the data coming into that organization is common. We made a solution as a multiBot: one Bot is working on one application and we have hundreds of applications. So a hundred Bots work together on the same set of data to integrate it.

The applications are different. Say one is Oracle, one is SAP (System Analysis and Program Development) and one is Salesforce. In the way we implemented this, we segregated the workload into parts: part as a master Bot, part as a worker Bot and part as the closure Bot. The master Bot will work on the input part of the data set, the worker Bot will work with the individual (designated) applications, and the closure Bot will consolidate all the data and feed it back to the designated user. This was the plan for our architecture.

View full review »
VisheshNigam says in an Automation Anywhere (AA) review
Associate Director at Concentrix

The product is quite stable. I don't know how to code the the other products which we have used. One thing with the bot that we are always with struggling is the memory management. The Automation Anywhere product is quite stable in that perspective. Security and other things are very well managed by Automation Anywhere. The third piece is the architecture is very much centrally governed. This makes this product more robust.

View full review »
ApurvaBoradia says in an Automation Anywhere (AA) review
CEO at Nine A Business Connect

A good thing about Automation Anywhere are three important things: scalability, durability, and the entire stability of the environment. So, I can start the journey with one, two, five, or 10 bots, then just look at the very comparable enterprise organization where I could apply hundreds of the bots.

Now, in any other situation, when I deploy the bot from our development to UAT to a production environment, and bots are running in a production environment, what I should not be worried about is: Are those bots running? Are the tasks getting completed on time? All that stuff. 

Stability of Automation Anywhere bots is very high. So, a one side deploys these bots successfully. I don't have to worry much whether the bot is stable. Is the bot performing? Even after deploying the bot, do I have to go back and check ii the bot is having some problems? Or, are there some errors being induced?

In the Control Room, I am able to see the complete dashboard of all the bots: 

  • Which bots I have deployed (hundreds of them)?
  • How many bots are in progress? 
  • How many bots are running? 
  • How many bots have thrown some error because of incorrect jobs or processes?

That gives me very quick access to the entire deployment of my bots. I can access that dashboard, even from my mobile. Even if I'm not in office and I'm head of the enterprise or a COE architecture, I can just log into my mobile and see how many bots are performing well, how many bots have done the job in time, etc.

The stability of the whole architecture is the essence of Automation Anywhere, if you ask me.

View full review »
Soumyadeep Paul says in an Automation Anywhere (AA) review
Manager - FP&A at Sterlite Power

A Cloud-based version of this solution would reduce dependence on architecture.

Better use case management to prevent each development from scratch would be an improvement.

View full review »
Prakasha S says in an Automation Anywhere (AA) review
Solution Architect at Accenture

The solution is pretty stable, we didn't face many issues. Once the instalation is done the control room core architecture wont face many issues.there are quick fixes like service restart if anything goes off. but most of the time we hear AA support suggesting us to reinstall with the new version of software for performance issues, but with my experiance i hardly see that making huge differnce in fixing the actual issue.

 Monitoring can be done through email alerts for the core infrastructure. Issues mainly in HA(High Availability) with cluster sync issues still not monitored at the dashboard level, which might be a concern if the cluster goes out of sync. At the bot implementation lot of things are dependent on the way we code so it's additional work for the developer to get the code keeping in mind all the events which might happen. I would have been impressed if the solution had framework at the control room level to keep track of the overal execution and transactions, hope they can bring that feature in future releases

View full review »
reviewer1390506 says in an Automation Anywhere (AA) review
Delivery Manager (RPA : Robotics Process Automation) & Automation Architect at Accenture

Using Automation Anywhere we have built/supported 200+ automation around operations and automated different Sharepoint, Outlook, ServiceNow, and contract processing related use cases. It offers a lot of features, flexibility whether it is through Meta bot, IQBot, etc. 

It offers :

a. Zero-install, Web-ready platform: Deploy RPA across the entire organization and scale bots on-demand in a few clicks.                                                                                                  b. Use the pluggable API architecture to maximize extensibility and customize RPA to meet unique business automation requirements.
c. Integrated machine learning: Streamline your document-centric processes with drag-and-drop IQ Bot integration.
d. Self-learning automation engine: Create a smarter automation engine by infusing third-party AI technology.

View full review »
reviewer1442205 says in an Automation Anywhere (AA) review
Sr. software engineer at Accenture

One area where I can see room for improvement is the training material that is available. I am aware that the Automation Anywhere university has a lot of training content, and even better, all of it is categorized with respect to the user's role in development. I took the training course related to architecture. This course and content were nice but the videos had a digital voice over, which made it non-engaging for me. After certain videos, you cannot concentrate much.

The other point that is relative to my experience is that for a completely new person to RPA, Automation Anywhere may come with a small learning curve.

View full review »
UiPath: Architecture
Agenor Roris Filho says in an UiPath review
Business Analyst and Process Consultant, Test Lead at a tech services company

The solution architecture should be reviewed to offer more opportunities to small companies or small entry level projects. For example, they could accept SQL Server Express Edition or other open software database engine; and allow all components installed in only one server, at least up to 10 robots.

View full review »
reviewer1019496 says in an UiPath review
User
  • Citrix recorder
  • UI Explorer
  • I used to connect using remote desktop and automated it using image automation. 
  • The cloud deployment option is particularly attractive to some customers for its flexibility and scalability, along with customary thin client advantages. 

Those customers should determine if the RA provider offers a cloud service that scales automatically. The customer should go beyond that minimum and look for a provider whose architecture provides a proven integration track record with Citrix (including Xen) and other virtualization technologies, enterprise applications such as SAP (GUI and web), Oracle, Siebel, PeopleSoft, Salesforce.com.

View full review »
Jose Antonio Flores says in an UiPath review
Manager of IT and Development at Gecu

I haven't had any issues with the architecture at all.

View full review »
Zachary Rubenfeld says in an UiPath review
RPA Developer at Guidehouse

The differentiation between unattended and attended bots is valuable, as well as being able to do portions of a process that are unattended coupled with portions that are attended. We can get human interaction, all within the same product.

The product is easy to use and definitely exceeded my expectations in that context. I have an IT enterprise architecture background with some computer programming experience. This was very easy to grasp.

The additional plugins and different partner programs have been a huge help.

View full review »
Thomas McEvoy says in an UiPath review
Lead Associate at Booz Allen Hamilton Holding

The Academy Live that I took was only a half a day course. There needs to be diverse set of courses for those introduced to RPA for the first time. There are different people who show up to this course: 

  • The developer who is interested in automation and automating different facets of the tasks that they have, either at work or for their clients. 
  • Business managers who want to know more about what RPA can do for my business or company. They want the operational and strategic level versus the tactical level of how do I get automation to do the thing I want it to do?

The course was only a half a day, and although we were able to provide two automations and build two bots, it would be helpful if that was extended to include the RPA story and pitch. E.g., What's the story that we need to tell in order to get people to say, "How do I get into the pilot phase now."

I would like to have the course do an introduction, "Welcome to the course. This is what RPA is. Now, let us build your first bot." 

The sales elements of why RPA should be there too:

  • What is the value proposition that RPA brings to the table.
  • Here is the expected ROI for a menial task, saving an hour a week equals this in the long term. Even if you can cut a 25 minute task out of somebody's daily routine, this is the benefit in the long term.

That wasn't there as much. I wasn't really expecting it to be there, but in the long term, if there are a number of different types of training courses which are offered, people will have different breadths of understandings of RPA can really do, e.g., it needs a hardcore developing training and a capture manager. It needs to explain what sort of things a capture manager needs to know. Maybe not necessarily how to develop the architecture for it, but what does that even mean? For example, how easy is it for me to get Orchestrator onto a server? How do I become a reseller of the software? These are the capture manager responsibilities, and it would be helpful if they were explained. While this is probably more of a day two of a training rather than day one. 

I would like to see a UiPath user group to discuss issues. I am unaware of all the activities and features, and this would help. Right now, there is just the user's guide and UiPath GO! It would be great if this feedback went back to the UiPath development team. We should also be notified of new features through an alerting system on UiPath GO!

View full review »
Jeremy Gilliland says in an UiPath review
Chief Automation Officer at JOLT

If I was going to give any advice to someone who was just about to utilize the software, I would say that the most successful organizations that apply this technology make it an entire team effort. It's not started in one business unit. And if it is, it's socialized across the enterprise. That's the quickest way to scale: getting everybody onboard. The second-biggest thing is that the most impactful projects you will get will come from your people, your internal workers. And until you get them to understand what the software can do and its capabilities, it's going to take you longer to scale your program. So make sure everybody's socialized, and make sure everybody truly understands what the software can truly do. They're going to give you the best opportunities to benefit from it.

Deployment should definitely be done using the support of experts. Even when I owned my own RPA program, and I wasn't in a consulting capacity, I still reached out to a third-party to get support. While setting it up is something that you can do internally, given that most objectives include speed-to-market and quick scaling - wanting to see results in 60 days instead of six months - it's going to be very difficult to do alone, especially if your goal is to have 100 bots in a year. If your goal is ten, you can probably manage it. It's important to use experts if you are looking to rapidly scale.

I have implemented UiPath in virtual environments, including on-prem, Azure VMs and servers, SQL-based data storage, as well as AWS. I've never had any issues with the responsiveness or the application having any problems operating. The biggest consideration that you have when trying to deploy robots in a virtual environment is making sure that your architecture is sound. You have to integrate through severs and you have to take into consideration firewall updates. And then there's interacting from the cloud if your applications are on-prem. You have to make sure that the bot doesn't have any issues. But if your architecture is solid and your infrastructure is set to support the applications in a cloud environment, there shouldn't be any issues. You wouldn't notice any difference compared to having them on a desktop on-premise.

I would agree that UiPath eliminates human error, but I would add the caveat that good code eliminates human error. I've been doing this for a while and I've seen bots that mess up. It's in your delivery methodology. If you have a sound delivery methodology - you're going through a rigorous UAT cycle and are having outputs audited by the subject matter experts - you should literally get to zero errors. Maybe you will have five percent exception cases, but your error percentage should be zero.

Having worked with all the tools, they all have little niche components. As long as UiPath continues to focus on knowing what the next wave of technology is that businesses really need to use to be efficient, and they start embedding that skillset in their software, that's all you could ask for. They need to stay in front of the power curve of technology, which is impossible, but they're trying.

I've never had a bad issue with UiPath. My experience with them has always been pleasant and engaging. They're never stuck at just giving you software, showing you how to use it, and then walking out. They're always focused on improving your business. If you focus on that, and focus on generating value, you can't lose.

Automation technology is the number-one driver across an organization now. Trying to find ways to do more with less has been the going mantra for organizations for years now. It's no longer feasible to simply run operational efficiency or Six Sigma projects to try to get gains. The only way that you're going to get significant gains is going with an automation-first approach. That's where I see a lot of organizations headed, even spending more on RPA software than on cloud implementation. It's a very big focus, and I don't see that slowing down any time soon.

On a scale from one to ten, I would you rate UiPath as an eleven. It's excellent software.

View full review »
Camilo Gutierrez says in an UiPath review
RPA Leader and Business Analyst at Ecopetrol

When we started we started with UiPath and Blue Prism. We made 14 processes with each and we decided to stay with UiPath. Mostly because of the IT architecture. We really like the Orchestrator, for example. It was like a huge consideration we had because Blue Prism is like a closed book and we didn't like it too much.

View full review »
Vikram Modgil says in an UiPath review
Founder at Pi Square

We have tremendous support from UiPath. We can say that from our perspective, we are very fortunate to be in the Pacific Northwest and that team is one of the best. It doesn't matter if we are big or small, they help everyone. So every time we have an issue or a challenge, whether it's engineering, presales, architecture, or development, we get all the support.

View full review »
MichaelSanders says in an UiPath review
Principal Engineer at Salt River Project

The most valuable feature is the ability to stop the process after it has been started by an individual user. This allows for some dynamic events, but still gain the automation. The underlying architecture (i.e. Elastic stack) is decent, but there probably needs to be better ties there to maintain at least an n-1 version on the Elastic stack.

View full review »
Barry Rodick says in an UiPath review
Lead Consultant at Konexo UK

The initial setup was really straightforward. In such a large law firm that has high data security obligations, we set these things up, appoint the orchestrator, and it just works. I have not encountered too many problems. 

It doesn't feel like a heavyweight ERP system or some larger workflow tool. These things are deployed onto a desktop and they speak to a server. It's not heavy. It doesn't feel like a piece of software with a heavy footprint.

The deployment took a week. It took us longer to end-to-end to get the invoice approved.

We've taken advantage of the architecture. Our IT team set some ground rules about where the virtual machines need to be hosted and deployed, but it's not that heavyweight. We increase some standards with IT and then install the software on those machines. We're using the Cloud version so there's not a lot to worry about.

View full review »
WorkFusion: Architecture
Ranjan-Prasad says in a WorkFusion review
Senior Software Engineer at a computer software company with 10,001+ employees

Before implementing it would be good to go through the design points.

On a scale of 1 - 10 I would rate them a 6. That's not low - that 60%. But as I said, it needs to be upgraded and modified. On-prem solution software needs to be in a stack that is much more accessible around the architecture of your plant. It should be fast-acting and accessed over the internet. That's the most important part and most companies require it.

View full review »
BarryBao says in a WorkFusion review
IT Manager at a recreational facilities and services company with 11-50 employees

Previously, I was working with Blue Prism. Blue Prism is highly architectural. It is deployed through a complex architecture. The server control and development and vendor support are very expensive here in China.

View full review »
reviewer1373997 says in a WorkFusion review
Analyst, Intelligent Automation at a financial services firm with 10,001+ employees
  • Simple to use (business user, not IT reliant)
  • Cost-effective
  • Easy to support and integrate with current IT Architecture 
View full review »
reviewer1387212 says in a WorkFusion review
Head of Intelligent Automation - Africa Regions at a financial services firm with 10,001+ employees

I do not think we have ever had issues with stability. It seems to be very good from my personal experience. It is more likely that something in the solution will be affected by the environment changing than it just breaking down. The question becomes can an RPA solution adapt to changing architecture through various upgrades and version changes and remain compatible with the environment.  

The stability of the product itself is something we have not had issues with.  

View full review »
Kryon RPA: Architecture
Adam Staude says in a Kryon RPA review
Manager, Application Support at a consumer goods company with 1,001-5,000 employees

Process Discovery is brand new. We are on 19.1 for it. I know on 19.2 that they change the architecture completely. From talking to some other companies that use this, it sounds like we are missing some pretty big features that we will need. We will be doing an upgrade here in the near term. In general, Kryon's upgrade process is basically uninstall/reinstall at this point. They don't have an easy way to upgrade the software in place, which would be an added benefit. The process is not difficult. We have just a handful of robot machines with high availability enabled, along with a couple of app servers and a couple of database servers. Still, that's 12 machines which all need to be upgraded, and that is no simple effort when you're talking about a full reinstalled software. If we fully utilized our licensing by scaling out, we'd have more than 30 machines. We would have to upgrade on the field. Then, it's a pretty big task if they release new features and things that we want to take advantage of going forward. I see an opportunity for improvement from them here.

We are using it to do some automated reporting, and right now, we can't put images into the HTML formatted body of an email. We can either attach an image or embed a link to an image, but we can't just drop in an image into the HTML. That is feedback that I have given them. It would be nice to be able to have a bot take an image and paste it in as you would in Outlook. Otherwise, we have to provide either those images on a public website. If we want them just to be attached, it just doesn't look as clean. Especially people in our sales force, who are on their mobiles a lot, are not on our network a lot. These are a challenge for them when they just want to be able to glance at the report and go on with their day. It seems like a small problem, but it's limiting for us in some of the areas where we could deploy more of this solution. We have a feature request in for this, and I'm hoping it will be included in the future.

How it delineates file names on email attachments could be better. It is a hard coded comma, and if somebody includes a comment in a file name that messes it up. It is such a ridiculous thing. Who puts commas in file names? But, you would be surprised, and it happens. This is another simple thing they could easily tweak.

Their Tier 1 support is pretty basic. You either have to jump through the same hoops every time or escalate to a different Tier through your rep. 

View full review »
BotFarm: Architecture
reviewer1264746 says in a BotFarm review
Sr. Director at a financial services firm with 10,001+ employees

I am aware of the initial setup process - we set it up ourselves. It's pretty straightforward. I don't think there's any complexity in the architecture from a UI point of view, sometimes there are slight differences but the setup is straightforward.

We carried out the deployment by ourselves. We also had the robotics process monitoring team setup nearby. The assistance we required related more to the documenting and business process flows.

View full review »
Blue Prism Cloud: Architecture
VikasTandon says in a Blue Prism Cloud review
Robotic Process and Test Automation Consultant at OFGEM

We did not ultimately deploy Blue Prism because we chose to use UiPath instead. However, I have detailed knowledge of this solution.

The primary use case is the building of clean, automated processes. These are then easily used and maintained by the architecture.

View full review »
reviewer1227903 says in a Blue Prism Cloud review
Head of Solution Development at a energy/utilities company with 10,001+ employees

Initial setup was not too difficult, the difficult part was our own infrastructure and the cloud set up. We had internal resources and consultants helping. The  whole setup and deployment of the solution took almost three months which included architecture of the infrastructure, installing Blue Prism and starting automation.

View full review »
HelpSystems AutoMate: Architecture
Mangr677 says in a HelpSystems AutoMate review
Manager at a consultancy with 501-1,000 employees

This product is quite easy to install, learn, and use, with our new employees being able to start using it in projects for clients after only two weeks of internal training.

Compared to other products, the pricing model for this solution is much more convenient, flexible, and adaptable to the Portuguese reality.

Key automation features: email, FTP/SFTP, OCR, ODBC, terminal emulation. 

Main benefits: Full Client-Server Architecture, Multi-Machine Execution, Centralized Management Interface, Graphical Workflows, Intuitive Task Development & Debugging.

View full review »