IBM Robotic Process Automation with Automation Anywhere is a robotic process automation solution combining business process management tools from IBM with Automation Anywhere's bots and automation capabilities.
$840
per month
Nintex
Score 8.0 out of 10
N/A
Nintex offers a platform that helps companies discover, automate, and optimize business processes.
$480
Minimum 1,000 users per user
Oracle BPM Suite
Score 8.5 out of 10
N/A
The Oracle Business Process Management Suite is an integrated environment for developing, administering, and using business applications centered around business processes.
N/A
Pricing
IBM Robotic Process Automation
Nintex
Oracle BPM Suite
Editions & Modules
IBM RPA On premises
Platform starter pack, starting at USD 840.00 per month
per month
IBM RPA Software as a service (SaaS)
Platform starter pack, starting at USD 840.00 per month
While it can be applied to various scenarios, its suitability can depend on the specific requirements of a given task or process. Here are some scenarios where IBM RPA is well-suited and scenarios where it may be less appropriate: Well suited: 1.Data Entry and Data Migration: RPA can efficiently automate data entry tasks, such as copying information from one system to another or migrating data between databases, reducing the risk of human error 2. Report Generation: RPA can generate routine reports by extracting data from various sources, formatting it, and delivering the reports to the relevant stakeholders, saving time and effort. 3. Email and Message Handling: RPA can help manage and categorize emails and messages, such as routing customer inquiries to the right department or processing routine email requests.Less suited for: 1. Cases where there is High Variability: RPA may struggle with tasks that have a high degree of variability, where each case is unique and difficult to standardize. 2. For Complex Decision-Making: RPA is rule-based and not designed for complex decision-making processes. It cannot replace the judgment and decision-making capabilities of humans. 3.Tasks Requiring Creativity: RPA is not suitable for tasks that require creativity, innovation, or problem-solving skills, as it operates based on predefined rules and logic.
We use Nintex to automate fundraising outreach at scale. It helps us send personalized emails to a large contact list, and we’d also like to automate follow-ups when there’s no reply. If you need highly customized solutions or clean, fully controllable code, I wouldn’t recommend Nintex. It has many features, but it’s not the same as building your own system from scratch. That said, it can save a lot of time for standard automation workflows.
Oracle BPM is well suited to organizations and environments that have a good understanding of their business processes and organizational structures. Trying to introduce a tool such as Oracle BPM into the organization without a good grasp on how the business operates is a recipe for disaster as the implementation will uncover all of the dirty secrets of an organizations business processes and bring them to light. BPM is not to be utilized for smaller service orchestrations or technical service implementations, these should be handled by the Oracle SOA Suite using the BPEL process manager, leaving BPM to handle the organizational business processes, referring to and including lower level services and BPEL processes as needed.
It was programmed to navigate to the web page requiring reCAPTCHA verification, locate the reCAPTCHA challenge, and generate a screenshot or other data to present to a user for manual input.
It was programmed to extract employee data from emails or forms, update the employee record in Workday, and send automated notifications.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
Security and data privacy: IBM RPA may not have the strongest security features, which can leave sensitive data vulnerable to breaches or hacking.
Scalability: IBM RPA may not scale well to accommodate larger businesses and more complex processes, which can lead to performance issues and increased costs.
Customization: IBM RPA may not provide as much customization options as some users would like, making it difficult to tailor the software to specific business needs.
If you are creating a process with parallel subprocesses, there's no way to see, in a single view in Nintex, all the steps for the subprocesses. You have to view each sub-process in its own view, so it's hard to see what's going on at a high level.
There isn't an easy way to filter the processes by another user (not yourself) in Nintex. There is a report that shows processes and objects by user, but that's not as convenient. This is something that I've seen in other tools (OpenPages by IBM) so I am surprised that it is missing.
Nintex doesn't really have a way to capture iterative processes (which we have a lot of). It's designed for linear processes.
Oracle BPM is left behind by other tools more modern in terms of user experience, usability and ability to integrate with everything else.
To really harvest the potential of Oracle BPM you need to do it in JDeveloper and with ADF. This restricts its usage to very technical people.
The administration of the Oracle BPM tools has really put a burden on our team. It is running on Weblogic and we experience issues very often either with performance or with a bad configuration of the system.
As with all Oracle products, the price can be an issue for smaller shops.
By implementing IBM Robotic Process Automation, we realized that they are digital robots with a great impact on our manual tasks, generating good automation capabilities that are beneficial to the entire company.
We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
IBM RPA is a very powerful tool, it has almost all the features that are necessary to build, implement and manage highly functional robots. The learning curve is very fast, so excellent skills are acquired. It is not necessary to have strong programming knowledge because its use is very easy. It is just drag and drop commands. By adding rules and logic, wonderful robots can be achieved.
Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
IBM has done a great job with enablement for the product. There is documentation for use-cases, development videos for beginners, and a community forum that has proven useful for getting started with the application. Although the resources cannot solve every problem a developer comes across, they have been very beneficial to our technical team.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
I am main developer of the this implementation. I have faced many chanllenges in implementation as IBM RPA not provided direct commands to automate Excel. I enjoyed in finding solution and best approach for the implementation
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
I've always had excellent service and had no trouble communicating. It has aided in my understanding of how I can continue to use the bots. Reading peer assessments reveals that while IBM RPA demands a substantial initial financial commitment, it justifies its cost, unlike Blue Prism RPA, which does not.
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
We evaluated Bonita and found that it might fit a smaller-sized company better; we found that Oracle BPM Suite scaled much more evenly. We almost went with one of the competitors, but in the end chose Oracle BPM Suite after we factored in the cost of VMware licensing. There are literally tons of analytics on the back end which are great for upper management, but not so much for average users, but this fits our business model quite well.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
IBM Robotic Process Automation has helped save on cost and time as it is able to automate tasks that are repetitive and routine tasks.
IBM Robotic Process Automation has helped us increase productivity. This is because it is able to perform tasks with a high degree of accuracy and speed.
It has enhanced compliance as it is able to automate compliance-related tasks. This has helped us improve our reputation.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
You'll most certainly need a deep dive and extensive training before your users can even think of using the product and they are very expensive.
Lack of documentation makes it very difficult to manage the application if any error is encountered which will result in you ending up hiring a dedicated person to look into the application once it's deployed.
For a very large org., if properly implemented and used, it can help identify the cost-intensive and inefficient processes.
