SAP PowerDesigner Reviews

As part of my consultancy business I provide training for PowerDesigner users, face-to-face and online. Working directly with clients or as part of subcontracted project work, I provide mentoring for users and customise the tool to fit the client's needs.

The majority of my clients use PowerDesigner for various types of Data Modelling and Database activities, along with Data Governance, Process Governance and Enterprise Architecture.

I use PowerDesigner myself for managing my own workload. For example, I use a Requirements Model to manage the tips and tricks I plan to include in my blog, and a customised Enterprise Architecture Model to manage my training portfolio. PowerDesigner includes a 'Free Model', which I use to manage and generate my library of PowerDesigner scripts.

The architecture of PowerDesigner is designed with extensibility in mind, supporting comprehensive customisation and automation features which allow customers to make the tool fit the way they want to work, embedding those new features directly into the tool itself. For example, the built-in Template Language enabled me to add a feature to export the structure of a Data Model as a JSON-format file for ingestion by a Data Governance tool.

Even if you don't customise or extend PowerDesigner, the tool is still the easiest modelling tool to use, with spreadsheet-like editing capabilities, the ability to link to or replicate (in a managed fashion) objects from a different model. The bi-directional traceability between objects and models is also a key differentiator - whenever you connect two objects together, that connection is visible from both objects (this may sound obvious but, believe me, other tool vendors don't seem to think it's important enough).

SAP have invested a lot of time and effort into improving and extending the capabilities of the PowerDesigner Web Portal. Following the most recent release, users can create and edit Conceptual, Physical, Requirements, Business Process, and Enterprise Architecture models using a standard web browser as well using the client software.

I'm looking forward to the day when the Web Portal supports every type of model, including Logical Data Models. I also would like to see better support for NoSQL databases.

I have been using SAP PowerDesigner for fourteen years. 

There are organisations with hundreds of users, very large models, and very large repository databases. It works.

The documentation is excellent, and more comprehensive than that supplied by the competition. However, even the best software documentation doesn't support you through your day-to-day modelling activities, which is why I wrote a book "Data Modelling Made Simple with PowerDesigner".

The technical support is very good, utilising SAP' standard customer support portal. I have interacted with technical support at another vendor, where everything is done by email, making it very difficult to keep up-to-date on a case.

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.

It's very easy to install. If you want to install a simple repository database, that's really easy as well - SAP provides a licenced copy of SQL Anywhere, which you can deploy anywhere (as the name suggests).

The list price for PowerDesigner is competitive for the base Data Architecture features when compared with the major competitors, especially when you consider the features that SAP don't charge for such as the Repository, Web Portal and 'Viewer' software. However, the pricing for small consultancies needs to be improved. The competing vendors often have special offers that make the tool more affordable, which is vital for data management consultancies that have to buy the tools that their clients use.

A powerful modelling solution has to be selected, implemented and managed in the same way as any other enterprise software - before you evaluate tools make sure you've documented your modelling process and the metadata you need to manage. Run a 'Proof of Concept' first - so you actually know what you're letting yourself in for and how much work you may or may not have to do to get it to work the way you want.

We are using SAP PowerDesigner to design physical and logical data models for new releases of software.

The solution has the basic features for creating entities.

SAP PowerDesigner could improve by being more intuitive and user-friendly. It does not enforce some of the integrity of the model that we would like it to retain.

There are many areas of this solution that needs to be changed.

I have been using SAP PowerDesigner for approximately two and a half years.

SAP PowerDesigner is fairly stable.

There are five people in my organization using this solution.

We have used technical support but was it was difficult to get in touch with the right person. It was not very clear who the responsible person was. They do not seem to have centralized support, making it difficult to get the person in the right region to help us. However, once we found the right person we had our issues resolved.

The installation is in the average difficulty range.

The price of the solution is too expensive. When we asked for certain licenses in different countries it was unattainable.

We have had some issues with being able to procure licenses for specific countries. We were not able to receive licenses for every location we wanted.

We intend to switch solutions and we have been evaluating others.

I would not recommend this solution to others.

I rate SAP PowerDesigner a six out of ten.

I am working for the partner of the vendor of PD. My jobs include implementing, training, customizing, and extending PowerDesigner.

One of my tasks is to develop automation that makes end users more efficient in their work.

It can automate many routine tasks and save human resources to focus on real problems.

The most valuable features are its user-friendly extensibility, impact & lineage analysis, and source/target mappings. It can be configured to display only relevant objects across all models, of any type. It has a public meta-model and the ability to automate many features so that the users can focus on what really matters, as opposed to the formal requirements of the modeling work.

I would like to see better team collaboration in PD. Passing models (or objects in it) from one role to another. Today, we have to solve it by custom extensions and modelling rules just written on paper (and not enforced automatically).

Support for ArchiMate would be an improvement.

There should be a better usage of current hardware including multicore CPUs, higher resolutions (UHD, 4K), and multiple displays.

I would also like to see better troubleshooting options for repository issues. In case of problems during check-in of the model to the repository, the error message just says "checkin was cancelled", but id doesn`t give you any details or hints where to look, what to repair.

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

PowerDesigner is not the cheapest solution on the market, so make sure that you are using it up to its full potential.

Our customers often choose PowerDesigner because of its wide possibilities for data modeling, together with the huge potential to automate frequent and routine tasks. This enables them to implement their own modeling methods within the tool. 

Sparx Systems Enterprise Architect is an option in terms of price, but not in terms of the number supported DBs, source-target mappings, possibilities of impact & lineage analysis, and the ease of customizability of the tool.

Before deploying PowerDesigner, do not underestimate the initial analysis of WHAT will be modeled, as well as HOW and BY WHOM. Are your users prepared well enough for the transition to PD (training, potential changes in the modeling process, ...)?

My advice for anybody implementing this solution is not to deploy PowerDesigner fully by yourself. Allow an experienced vendor consultant to explain all of the features and possibilities of the tool to you, and then just decide what and how you want or need to use.

• Improving retail company operations on ERP migration

• The report wizard is extensive and useful.

• You can import BPMN from Bizagi.

It has helped me to develop the as-is state, design its to-be state, and track the capital investment according to gap analysis.

• The wizard report links directly to MS Word and is very useful.

• The matrix processes and capabilities are good tools.

• It is easy and fast to use.

• The UML simulation should be improved to avoid designing other tools out of the application. 
• The data governance should be improved, like ER/Studio.

Switched because SAP PowerDesigner is easy to use.

The ROI has been 43%.

• ERwin

• Sparx System Enterprise Architect

• ER/Studio.

I use SAP PowerDesigner for data modeling, documentation, and it interacts with the other tools. Additionally, we use it for all of the business requirements, such as CDM and PDM.

The most valuable feature of SAP PowerDesigner is the testing of the models, it has the best function. Reverse engineering is very helpful too.

The solution itself does not need to be improved. However, they could add support for different languages.

I have been using SAP PowerDesigner for approximately 22 years.

The solution is stable.

The scalability of SAP PowerDesigner is good. However, I have not had the chance to test it in a large environment. For my environment, it works well.

The online support from SAP I have used has been good.

The setup is very simple. 

I would like SAP to prove free licenses to professionals that are using the solution. The free version is limited.

I rate SAP PowerDesigner a ten out of ten.

I like the connectivity or the lineage between the models and usability.

Technical support could be better and more human.

I have been using PowerDesigner for three years.

PowerDesigner is a stable solution. 

PowerDesigner is a scalable solution. I worked in a client site where there was a repository, and there were dozens of data modelers. There wasn't a problem.

It would be better if they had a more human IT support system. They are really chuffed with their support desk, they got the dashboards, and you can log your problems.

With another vendor, you log a problem, and they call straight away. You can tell somebody about the problem. They're very nice and personable, and they know you. For SAP, you're just lost somewhere in the queue, and for me, it's not a decent response.

On a scale from one to ten, I would give PowerDesigner a nine.

Reverse engineering a database in order to produce documentation for client to understand their database in order to support their application, perform data migration, perform system analysis, perform impact analysis, and write interfaces.

This product is very useful when starting a new project. It helped the consultant to understand the database.

No issues encountered.

I've been using it for about 15 years, starting with v5.0

No issues encountered.

The product is very stable, even with no maintenance updates to purchase. There were a few bugs I have found, which I just learned to work around.

It's very good.

It was implemented in-house.

We also looked at what is now CA ERwin Data Modeler.

It is a great product to use, but the client does not really need to purchase the software, as the consultant can reverse engineer the database, and then create the data model and documentation in order to deliver to client. The client can use the read-only version of PowerDesigner.

Often, a customer will want to migrate from another solution onto PowerDesigner. That's how I primarily use the solution: migrating things over to this solution.

We use it to set up the conceptual model. From there, we will take the physical model, where we can start the different DDLs. We will use it to generate the DDLs for the database teams to implement it.

The generational DDLs and the graphics are the solution's most valuable aspects.

The solution is a very pragmatic tool. It's quite easy to use.

The solution is very good for data modeling on a conceptual and physical level.

There are a lot of design tools that are very complicated to use, and customers will not use them in detail. I find the solution to be one of the best tools in the range.

I don't know of any features the solution is lacking.

It would be helpful if there were glossary, catalog and governance tools. It would help make it a true end-to-end product.

I've been using the solution for a while. When I use the solution, the need to use it is driven more from the customer's own needs and not from my own. 

I haven't had any feedback from clients that would make me believe that there are stability issues.

I don't have any direct experience with scaling the solution. It's not something that I handle.

We've never contacted SAP's technical support. I don't have any direct experience with them.

We occasionally do migrations from MEGA HOPEX to PowerDesigner.

The initial setup was straightforward. It's not complex at all.

However, it depends on how big your environment is. It's difficult, but approximately in one week, you can start creating the capabilities and then it depends on what you want to achieve. 

The problem for the migration part is the setup of the conceptual models and the physical models. If you do the modeling between the conceptual and the physical from a migration point of view, then it becomes more complex because you have the generation of internal keys.

We don't have a business relationship with SAP. We prefer to keep our relationship independent and have no direct relationships with them at the moment.

It's certainly a good strategy to migrate to this solution from another tool, but I wouldn't recommend anyone start using it by trying out a trial-and-error strategy. An organization must think first about the migration strategy if they already have a tool and want to migrate before they start. A trial and error approach will waste a lot of time. 

I'd rate the solution eight out of ten. It's easy to use and you can get good pictures out of it.