Blueworks Live is cloud-based business process management software that provides users with a collaborative environment for documenting, analyzing, and building business process mapping.
N/A
Nintex
Score 7.9 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
Pricing
IBM Blueworks Live
Nintex
Editions & Modules
No answers on this topic
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
Offerings
Pricing Offerings
IBM Blueworks Live
Nintex
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
IBM Blueworks Live
Nintex
Features
IBM Blueworks Live
Nintex
Reporting & Analytics
Comparison of Reporting & Analytics features of Product A and Product B
IBM Blueworks Live
8.3
Ratings
1% above category average
Nintex
8.5
Ratings
4% above category average
Dashboards
8.00 Ratings
8.80 Ratings
Standard reports
9.10 Ratings
8.80 Ratings
Custom reports
7.90 Ratings
7.80 Ratings
Process Engine
Comparison of Process Engine features of Product A and Product B
IBM Blueworks Live
7.7
Ratings
8% below category average
Nintex
7.4
Ratings
12% below category average
Process designer
8.40 Ratings
8.40 Ratings
Process simulation
8.50 Ratings
5.00 Ratings
Business rules engine
5.80 Ratings
7.80 Ratings
SOA support
7.80 Ratings
6.90 Ratings
Process player
8.20 Ratings
8.40 Ratings
Support for modeling languages
7.20 Ratings
6.00 Ratings
Form builder
8.00 Ratings
9.10 Ratings
Model execution
7.70 Ratings
7.70 Ratings
Collaboration
Comparison of Collaboration features of Product A and Product B
IBM Blueworks Live
8.5
Ratings
1% above category average
Nintex
9.0
Ratings
7% above category average
Social collaboration tools
8.50 Ratings
9.00 Ratings
Content Management Capabilties
Comparison of Content Management Capabilties features of Product A and Product B
Pharmacies are subject to several regulatory obligations, including FDA and HIPAA rules. Pharmacy teams may record and view compliance-related procedures in a uniform format with IBM BLueworks Live. This facilitates Audit tracking, ensures process compliance at every stage, and keeps audits running smoothly.
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.
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.
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.
Blueworks Live was part of a project deal. We did not keep it after the project. We found there are many solutions offering similar or superior capabilities - the fact that Blueworks does not fully support the universal BPMN standard was a big letdown for us. The pricing also did not make sense as a standalone solution.
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.)
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.
It has helped us reduce miscommunication between our departments, such as production, inventory, and shipping, thus reducing delays.
Now, most things are automated; we can quickly know when a product will be in low stock.
With the help of custom charts, we are easily able to determine our best-selling product of the month and week, which helps us market according to stats.
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.