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
Nintex
Oracle BPM Suite
Editions & Modules
Enterprise - Process Platform
$480
Minimum 1,000 users per user
Professional - Process Platform
150,000
per year
Expert - Process Platform
185,000
per year
Custom
Personalized Quote
No answers on this topic
Offerings
Pricing Offerings
Nintex
Oracle BPM Suite
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Nintex
Oracle BPM Suite
Features
Nintex
Oracle BPM Suite
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
Nintex
8.5
Ratings
4% above category average
Oracle BPM Suite
6.0
Ratings
31% below category average
Dashboards
8.80 Ratings
6.00 Ratings
Standard reports
8.80 Ratings
6.00 Ratings
Custom reports
7.80 Ratings
6.00 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
Nintex
7.4
Ratings
12% below category average
Oracle BPM Suite
7.4
Ratings
12% below category average
Process designer
8.40 Ratings
8.00 Ratings
Process simulation
5.00 Ratings
7.00 Ratings
Business rules engine
7.80 Ratings
9.00 Ratings
SOA support
6.90 Ratings
8.00 Ratings
Process player
8.40 Ratings
8.00 Ratings
Support for modeling languages
6.00 Ratings
7.00 Ratings
Form builder
9.10 Ratings
4.00 Ratings
Model execution
7.70 Ratings
8.00 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
Nintex
9.0
Ratings
7% above category average
Oracle BPM Suite
6.0
Ratings
33% below category average
Social collaboration tools
9.00 Ratings
6.00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
The Nintex K2 platform is not only efficient and developer-friendly, but the support provided by the vendor is also highly commendable. The platform's ease of use and robust functionality make it a preferred choice for developers, while the vendor's exceptional support ensures smooth implementation and ongoing assistance, enhancing overall user satisfaction.
Oracle BPM is part of [the] Middleware SOA suite. Hence Oracle BPM can be directly installed with Oracle WebLogic. Oracle BPM comes with [a] standard out of the box portal. Recently Oracle has introduced another Web based portal to design processes. Standard Oracle BPM workflows can be created using the Jdeveloper. Deploying BPM apps are easy to deploy over Weblogic. All features with Weblogic can be utilized with Oracle BPM. Oracle BPM is [a] standard Middleware product and can make excellent front end applications.
Difficult to fix flows that are in process (such as re-assigning a task for someone that is OOO or has left the company).
Nintex support team does not have resolution SLAs (only acknowledgment SLAs). Occasionally this has led to key issues taking weeks to resolve.
The number of integrations available is impressive, however, sometimes key methods are not available within an integration. This has been improving significantly in the past 2 years as the platform has matured.
Extremely complicated to work with. The WYSIWYG is of no help either since it very buggy and poorly designed. If you are a business or functional user, you will have a hard time using the application.
The Oracle's "Using" and "Implementing" guides are nearly useless with no examples and case studies and there is no documentation available to learn or understand the process.
Very few skilled developers are available in market who really understand how to implement Oracle BPM suite.
Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs. Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.
Nintex Workflow does exactly what it is advertised to do: make workflow development fast and easy. It doesn't provide very much new functionality, but it isn't really supposed to. When I am working with a client on a SharePoint project, I am always happy if I hear that they use Nintex Workflow, as it makes workflows much easier.
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.
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.
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 was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. because it is less automated and more flexible.)
All are fairly similar in capabilities, but the Oracle BPM Suite has good support for BPMN 2.0, integrates well with open standards and has an excellent design/development platform when compared to the other BPM vendors. The Oracle BPM Suite integrates well with the complimentary Oracle Fusion Middleware products that typically accompany a BPM implementation, making it a part of an overall well integrated solution set. Oracle BPM also has very good monitoring, reporting and analytics support built-in.
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.
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.
When we moved to Oracle BPM many years ago, it was a huge uplift for our business processes because we didn't have any tool to model flows except Outlook and Excel.
We established and streamlined the manufacturing workflows that were needed with the growth of the business.
We discovered after a while that the ROI was not great since along with the cost of the tools, we had to account the cost of development from the software team too. It took a lot of time to deliver our first automations due to the big learning curve needed for Oracle BPM.