I used ER/Studio before using SAP PowerDesigner.

In my current organization, we are not using this solution, however, if I was asked to change solutions, I would change back to this product. 

When comparing with Bizagi, PowerDesigner excels in BPMM standards and follows a strict relation model in data modeling. However, Bizagi surpasses in application organization, form creation, and process testing.

I would say that the Linux and MEGA are intuitive, but not complete. Linux cannot track down the data model inside the databases, but it's very intuitive and user-friendly. So PowerDesigner is complete, but it's for experts and cannot be used by junior teams.

I have used Erwin Data Modeler and it was not as intuitive as SAP PowerDesigner. I was attempting to use Erwin Data Modeler by myself and it was difficult to learn.

The main advantage of SAP PowerDesigner compared to other solutions is the various sources of database it can connect and deliver data models, and do reverse engineering. Not every modeler tool can do reverse engineering, forward engineering, versioning, version control, and additional properties on the objects, such as core physical options. I'm using Oracle connectors. You have everything you want to have and you can deliver every object code in SAP PowerDesigner.

My company hasn't used a different solution apart from SAP PowerDesigner. It's been the company's solution for the last twenty years. Though my company recently thought of bringing erwin Data Modeler on board, the initiation process was put on hold.

The interface is way better with SAP PowerDesigner. Other solutions are limited in their designs. They simply focus on the database, for example, and not on the different types of models.

I did not use other solutions similar to SAP PowerDesigner.

I used to use ER/Studio and Techwin for modeling. In my previous job, the focus was more on the modeling and data modeling as a stand-alone kit. We selected PowerDesigner here because of the repository setup it caters to. SAP has the function to be able to establish the repositories, work in teams and then consolidate and present to a larger audience through a web browser. That was the main consideration for switching. The usability of how to model is pretty similar and there's no big difference in terms of the functionalities. But from a whole enterprise setup; the repositories, the check in, check out of those things into a central repository, are the key reasons we switched. 

One key difference is the connectivity. Besides the modeling we also do reverse engineering. We will try to connect to different data sources to extract information rather than building a model from scratch. That is one advantage because this is actually the SAP program so it has a good connection with the SAP product. We use quite a lot of SAP modules in our organization, so it's a good fit in a way that we can actually link it to some of our SAP servers and database and just reverse engineer the models. This is a main benefit over the other solutions which  are more neutral and more stand-alone products.

I have used other tools like erwin Data Modeler and they have versioning repositories also, but it seems like their check-in and check-out processes are much simpler and much cleaner. The central repository seems to be a little more stable.

The other advantage to erwin is that you can model right in the diagram, which means less clicking. In PowerDesigner, sometimes there are so many property sheets that we are constantly clicking.

The two other products that I have used are erwin Data Modeler and Enterprise Architect. I switched because of the scope and the user-friendliness of the tool. PowerDesigner used in conjunction with SQL Server is quite amazing. They work well together.

I worked with erwin for maybe a year or two. Then we switched to SAP PowerDesigner because of the quality of the product and the price. The cost of the product is cheaper, and the bank was very sensitive to the price. I am happy with the switch to PowerDesigner.

If our suppliers want us to use other tools, we of course will, however, we've been using this solution since 1994. I do not recall if we used anything before that, or what it might have been.

Before PowerDesigner we were using IDERA and erwin. PowerDesigner was better than IDERA, but it's obviously a lot more expensive, so IDERA could be a better value.

With PowerDesigner, I had the whole studio. I had the business process solution. With IDERA there are separate downloads and everything so I only used the data modeling studio.

I have used many modelling tools (possibly more than 10) over the years; when I set up my own consultancy I had a choice of tools to focus on, choosing PowerDesigner. I do also provide some consultancy and customisation for Idera ER/Studio Data Architect.

I started with IBM Rational Rose and then switched to PowerDesigner. I have some experience with Sparx Systems Enterprise Architect, too.

We occasionally do migrations from MEGA HOPEX to PowerDesigner.

Switched because SAP PowerDesigner is easy to use.

No.

I previously used Erwin and I switched because PowerDesigner is a more powerful tool. PowerDesigner is more powerful than Erwin in many ways, but to highlight one, the capability mentioned about the Data Modeling is non-existent on Erwin and in my opinion, it is very important.

I have used Sparx Enterprise Architect that provides more functions for a fraction of the costs.