We performed a comparison between erwin Data Modeler by Quest and SAP Signavio Process Manager 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."It has centralized storage so that a data model can be shared by different teams."
"It's a safeguard for me because I'm always concerned that somebody is free handing it and will forget a key coming from the parent. The migrating keys are a great feature. Identifying relationships, non-identifying relationships, and being visually right there to understand the differences are great features. erwin is key to being able to visually understand whatever the customer is requesting. They'll give you words on a paper, but once they can actually view it as a picture, it really comes to life. The data comes to life to where they understand exactly what they're asking for."
"We had some data integration projects, where we needed to integrate it for about 100 databases. Doing that manually is crazy; we can't do that. With erwin, it was much easier to identify which tables and columns could be used for the integration. That means a lot in terms of time and effort as well as my image to the customer, because they can see that we are providing value in a very short time."
"Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."
"The visual data models for helping to overcome data source complexity and enabling understanding and collaboration around maintenance and usage are excellent. A picture speaks 1,000 words. Seeing a picture that shows you how the data relates to each other helps you better understand what the data is and how to use it. Pairing that information with a dictionary, which has the definitions of the tables and columns or the entities and attributes, ensures that the users understand what the data is so that they can use it best and most successfully."
"What has been useful, I have been able to reverse engineer our existing data models to document explicitly referential integrity relationships, primary/foreign keys in the model, and create ERDs that are subject area-based which our clients can use when working with our databases. The reality is that our databases are not explicitly documented in the DDL with primary/foreign key relationships. You can't look at the DDL and explicitly understand the primary/foreign key relationships that exist between our tables, so the referential integrity is not easily understood. erwin has allowed me to explicitly document that and create ERDs. This has made it easier for our clients to consume our databases for their own purposes."
"It allows us to create logical data models. We can represent a database model in business terms, which is very useful for us."
"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."
"In my opinion, the most valuable feature is the editor and its ease of use, and when people are looking at it, they can make comments about changes that need to be made."
"The benefit of this application is that I can immediately describe processes and form normative documents for these processes. For me, this is definitely a plus. Сurrently, I work in a company that is not involved in the structural alignment of business processes. They have huge gaps in this. Nothing is described and there are no norms. Therefore, the formation of regulatory documents, rules, and descriptions of processes, not only in graphic form, but also in documentary form is an absolute plus. I have not found this in other process programs."
"The GUI is very easy to use, where you can sit together with your colleagues, discuss the process, and during these discussions you can build up the model."
"Process management/Process governance is what we think Signavio is very good at."
"The most valuable feature for me is usability."
"I really like the Collaboration Hub because it's so easy to communicate. And what is really important is that you can use it asynchronously. It doesn't matter if you're working in Italy or in America. You are using the same process and you can speak about the same process."
"All in all, Signavio usability is excellent. Anyone can learn to use the tool quickly. This increases acceptance as employees are not facing a high learning curve. With the offered usability it is easy to model processes also live in workshops."
"The collaboration function in the project views is valuable because people can comment on the processes and we can respond."
"The erwin Data Modeler is quite complex to use."
"The solution's reporting side needs to be improved."
"It would be nice to have it on the Linux platform, not just Windows. If they can support Linux, there would be a huge market for it."
"It does not have a cloud application."
"I still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."
"I love the product. I love the ability to get into the code, make it automated, and make it do what I want. I would like to see them put some kind of governance over the ability to make changes to the mart tables with the API, so that instead of just using the modeler's rights to a table -- it has a separate set of rights for API access. That would give us the ability to put governance around API applications. Right now a person with erwin and Excel/VBA has the ability to make changes to models with the API if they also have rights to make changes to the model from erwin. It's a risk."
"I find the UI very clunky and very difficult to use. If I add columns to a table the whole workflow could be so much easier. I get frustrated using it. I've tried other tools. I've tried to get off of erwin a few times. I always come back to it because every tool has its own set of problems, and it seems like if I have to pick my poison, I stay with erwin. But so many things that are clunky with it."
"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 think the intuitive handling is an issue which they should be more focused on, especially as we have issues with the glossary. If you want to implement Signavio within procedures in contact with other software, it's quite difficult to integrate and you will have several points where you have to double and triple the work, because you cannot maintain the data centrally. With other solutions, we can integrate it and have only one data transfer, to import and export with other solutions. A glossary is still limiting us."
"Being able to integrate the Workflow Accelerator with more products would be good."
"I find it difficult to figure out how I can better align this solution with my KPIs."
"The product's pricing could be improved."
"The collaboration and commenting are great. However, I think it would be more useful for people to get notifications of comments straight-away so we can react even quicker to them than we already can."
"Technical support has been somewhat challenging; there hasn't been much visibility on how to create a ticket or integrate with SAP."
"I think the biggest selling point that Signavio talks about is its collaborative aspect. However, there's still a lot more improvement in terms of what they can do, how they receive comments, address comments, whether they actually provide feedback, etc. There is still a little bit more improvement to be made on those areas."
"It's very user-orientated, which is why I gave it a high rating, even if it is not perfect in every corner."
erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews while SAP Signavio Process Manager is ranked 6th in Business Process Design with 57 reviews. erwin Data Modeler by Quest is rated 8.6, while SAP Signavio Process Manager 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 SAP Signavio Process Manager writes "Has many functionalities and is used to model processes to the former operating model". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Visio, Lucidchart and Sparx Systems Enterprise Architect, whereas SAP Signavio Process Manager is most compared with Celonis, ARIS BPA, Camunda, Visio and ADONIS. See our SAP Signavio Process Manager 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.
