We performed a comparison between erwin Data Modeler by Quest and IBM Blueworks Live based on real PeerSpot user reviews.
Find out in this report how the two Business Process Design solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features are the ability to reverse engineer and do model comparison. With the reverse engineering, I can understand the databases from third-party products. With the model comparison, I can track the differences between two versions of the same database."
"Another feature of erwin is that it can help you enforce your naming standards. It has little modules that you can set up and, as you're building the data model, it's ensuring that they conform to the naming standards that you've developed."
"When you're getting down to the database level, where you're building a design and you're creating DDL out of it, or you're going in the other direction where you're reaching into system catalogs and bringing things back, that starts to really require specialization. Visio isn't going to reverse-engineer that for you. Those features in erwin are valuable."
"The product lets us import different types of models from various databases."
"The generation of DDL saved us having to write the steps by hand. You still had to go in and make some minor modifications to make it deployable to the database system. However, for the data lineage, it is very valuable for tracing our use of data, especially personal confidential data through different systems."
"We find that its ability to generate database code from a model for a wide array of data sources cuts development time. The ability to create one model in your design phase and then have it generate DDL code for Oracle or Teradata, or whichever environment you need is really nice. It's not only nice but it also saves man-hours of time. You would have to take your design and just type in manually. It has to take days off out of the work."
"It supports a wide variety of databases, including the latest ones. We have chosen to go for a cloud-based database, and it supports that, which is very useful."
"It allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"The solution is easy to operate. Also, there is an automatic mode to make the business flow. You don't have to put any lines or arrows in a decision point in IBM Blueworks Live; it's very automatic."
"Business users understand it really well, which means we can then help them automate their business processes."
"I like the two-tiered approach, that is, discover and then drill down to the main steps. You can right click and attach risk, policies, and much more. It is a user-friendly solution."
"It has the ability to document in different formats. It is not tied to a specific model. You can look at it from different angles and see the intuitive nature of it. It always generates a valid diagram. You cannot create something that is not BPMN compliant."
"This solution is good at utilizing standards rules for connectivity."
"It is a stable solution since there has not been any downtime. Everything loads fast."
"The ease of documenting and digitizing the processes was valuable to us."
"It's very easy, very quick to create a process map. It has templates. The look and feel is very nice. What we want to achieve out of the process map, we can achieve it using Blueworks."
"The Bulk Editor needs improvement. If you had something that was a local model to your local machine, you could connect to the API, then it would write directly into the repository. However, when you have something that is on the centralized server, that functionality did not work. Then, you had to export out to a CSV and upload up to the repository. It would have been nice to be able to do the direct API without having that whole download and upload thing. Maybe I didn't figure it out, but I'm pretty sure that didn't work when it was a model that sat on a centralized repository."
"In terms of improvements, support could have been better in terms of installation, especially of workgroups. We struggled quite a bit to get it up and running. Collaboration could have been better from an installation perspective, but it is trivial as compared to what we use it for. Other than that, I don't have much feedback. It works pretty well, and the fact that we've been using it for more than a decade shows that it is quite solid."
"The navigation is a little bit of a challenge. It's painful. For example, if you've got a view open and you want to try to move from side to side, the standard today is being able to drag and drop left and right. You can't really do that in the model. Moving around the model is painful because it doesn't follow the Windows model today."
"One of the things I've been talking to the erwin team about through the years is that every data model should have the ability to be multi-language... When I was working at Honda, it became very difficult to work with the Japanese teams using just one model. You can have two models, one in English and one in Japanese, but that means you have to keep the updates back and forth, and that always increases the risk of something not being updated."
"I would like to see more support for working with the big-data world. There are so many new databases evolving and it's very hard for them to keep up with all of the new technologies. It would be good if they were able to dynamically support big-data platforms, other than Hive and Teradata."
"We are planning to move, in 2021, into their server version, where multiple data modelers can work at the same time and share their models. It has become a pain point to merge the models from individual desktops and get them into a single data model, when multiple data modelers are working on a particular project. It becomes a nightmare for the senior data modeler to bring them together, especially when it comes to recreating them when you want to merge them."
"I would like to see improved reporting and, potentially, dashboards built on top of that. Right now, it's a little manual. More automated reporting and dashboard views would help because currently you have to push things out to a spreadsheet, or to HTML, and there aren't many other options that I know of. I would like to be able to produce graphs and additional things right in the tool, instead of having to export the data somewhere else."
"There is a lack of local support in the China region."
"The ability to create a very structured rule. With the capability that we have right now, Blueworks Live is more process focused. We should be able to enhance it to include a lot more of decisions as well."
"I can't insert any images. For example, within the process map, if I want to put it in the box or rectangle, or circle. If I have to use one image or icon, that's not possible."
"I would like to see integration with ERP systems. This would help us to simulate the process and see where the problems are. Though IBM Blueworks Live is a good tool for documenting, it is not good for simulating."
"The user interface is quite easy at first but process analysts soon run into roadblocks of limited functionality, which is disappointing."
"The font size is really, really small and it's really not useful to print out process models because you cannot read what's written in different boxes. This makes it necessary for people to have access to the tool. We view licenses to see how the printing or output is. It's not very good."
"The APIs are great, except the normal business user doesn't know how to create APIs. So it's hard because IBM comes to us as the business users and tell us to create reporting with APIs, except we don't know that, so we have to turn around and flip it to our IT people."
"There should be an option to import from and export to Microsoft Visio. Being able to move files back and forth between Blueworks Live and Visio would be good."
"Sometimes, the tool is automatic, which can complicate it, but once you're accustomed to manipulating it, you can use it very effectively."
erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews while IBM Blueworks Live is ranked 12th in Business Process Design with 20 reviews. erwin Data Modeler by Quest is rated 8.6, while IBM Blueworks Live is rated 8.2. The top reviewer of erwin Data Modeler by Quest writes "The product lets users import different types of models, but it is expensive, and the interface must be improved". On the other hand, the top reviewer of IBM Blueworks Live writes "An easily scalable and affordable solution that enables users to document and digitize processes with ease". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Visio, Lucidchart and Sparx Systems Enterprise Architect, whereas IBM Blueworks Live is most compared with Visio, SAP Signavio Process Manager, Lucidchart, ARIS Cloud and Camunda. See our IBM Blueworks Live vs. erwin Data Modeler by Quest report.
See our list of best Business Process Design vendors.
We monitor all Business Process Design reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
