SAP PowerDesigner Reviews

I used SAP PowerDesigner as a tool for document folder flow charts and other features.

SAP PowerDesigner is helpful because you can create any type of document.

The most valuable features of SAP PowerDesigner are the creation the flow charts and folders. It is a powerful tool.

SAP PowerDesigner can improve the ease of use. It is not the best tool on the market because it is tough to navigate and use. A beginner would not be able to use it well, it requires some experience. If the solution was more user-friendly it would be able to be used by more audiences. I do not think many people are aware of this solution and they should use it.

In a future release, more features should be added. Other solutions have more features.

I have been using SAP PowerDesigner for approximately two years.

I rate the stability of SAP PowerDesigner a seven out of ten.

I rate the scalability of SAP PowerDesigner a six out of ten.

We have approximately 200 to 300 in the company but not everyone uses it. We will increase usage depending on the company's requirements.

The support from SAP PowerDesigner is great.

I rate the support from SAP PowerDesigner an eight out of ten.

Positive

I did not use other solutions similar to SAP PowerDesigner.

The initial setup of SAP PowerDesigner requires some training before they can work on it. It would be beneficial for those who want to work with the took to take a one month or 20-day training course.

The price of the solution is low. 

I rate the price of SAP PowerDesigner an eight out of ten.

I have not evaluated other solutions before using them. I use whatever the client specifies.

We use 10 to 20 experienced people for the maintenance of the solution. However, the amount of people needed depends on what needs to be worked on. We have other teams that work on the tool, such as developers.

My advice to others is they should try out the solution, it's a good tool. This solution is priced low and if it works for their use case then it is better than paying for a more expensive solution. If your requirements are too high, you can't expect this tool to meet all of your needs, it does not have all the features. You have to go for other options if your requirement needs more features.

I rate SAP PowerDesigner a seven out of ten.

We use the solution for LDM, PDM and scripts implemented in the database. 

When it comes to doing logical or physical Data Modeling, you can do that in other tools as well, or you can do that in Excel. What's best about this tool is that it is easy to use and productive, and it supports a number of databases like Oracle, Informant,  Db2, and many more. This is a stable tool.

PowerDesigner is the market's best tool for Data Modeling. It provides a number of features like multiple team members can work using the repository function. They can work and submit the change into the repository and pull from it. Therefore, you do not need to maintain manual files and do not need to make any comparisons manually. The tool is pretty good at handling that stuff.

It provides you with the capability of having dynamic licenses that you install on the server, and every user borrows the license at each login and returns it after use. This helps maintain the efficient use of the service and is cost-effective.

We are able to work seamlessly with PowerDesigner.

All the features are in working condition, and the product is in good shape. You can easily compare two databases, and you can easily compare two models. You can easily take out data dictionaries and re-import models. You can work on existing models too. ..

The only restriction comes when you have to work on the NoSQL databases and typically when you have to work on any JSON structures. There are some limitations. For example, it cannot work on NoSQL databases, and there is no update on that as well. However, you can still do the Logical Modeling for NoSQL applications. You can do logical models - just not physical ones. The tool should support NoSQL databases, like MongoDB, etc. 

When you implement PowerDesigner, and you do implementation on the server, you also set up a portal. The portal is a web browser link you set up, where a person can use the browser and easily see what models were submitted to the repository. If you want to manage access and edit a file from the browser, you can easily do so without installing Client.exe. However, that portal is very slow. The portal takes a lot of time to respond if you have a number of tables in the schema it will take minutes to populate these tables. Portal performance needs improvement. Everything else is good and it's really a good tool, however, if these things can be improved, it can be even better.

I started using the solution in 2015 and have about seven years of experience with it. 

It's a stable system. It never crashes. The only thing to look out for is if you're using low-end machines for repository services. However, that's the problem on your end. That's not the fault of the product. We do not recommend a low-configuration machine. There needs to be a minimum configuration of two CPUs, which is the machine they recommend. Depending on the load, you have to increase that. When you purchase the product, you will get a technical assessment for the installation. At that time, you can mention the requirements, and they will give you guidance on what machine type you can use.

I'd rate the general stability an eight out of ten. 

It's a scalable product. PowerDesigner does come with a Load Balancer to support multiple license servers. Adding new licenses for users is also a bit easy.

It is very scalable. I'd rate the ability to expand a ten out of ten.

Technical support needs improvement. 

I implemented the product about three years ago and got help from support when I was implementing this for my company. I just kept on raising the request and not getting a response for five or six days. When you are buying technical support, it needs to be solved much faster and shouldn't take five or six days. Make sure you agree on SLAs.

Negative

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. 

For the deployment process, you need a minimum of one server or you can have three servers at a maximum. You need two CPUs and a four GB machine at a minimum. However, if you wanted to do all the installation on a single machine, you can use the eight GB machine instead of a four or six GB. 

For the distribution of the license, you can install the license server and do a dynamic distribution of the license where a person opens the .exe on their local system. They can use the license and return after use by closing the .exe. This feature can only be achieved by implementing the license server.

Another .exe needs to be installed on the server to store the model in repository services. You can do your work on your local server and after you are done, you submit the model to the repository. When the model submitted to repository services is saved on the server, other users can connect to the repo and take the latest copy when required to refer to and work.

Portal services can also be installed and used for model sharing. For example, If you have 50 people, you wouldn't want to buy a license for everyone, and therefore, you can create 50 accounts in PowerDesigner's portal instead of passing out 50 licenses. 

One person is sufficient in terms of handling deployment. It takes two to three days to set up everything. The ideal process takes three to four hours only, however, before that, you have to set up the server, and you have to do other activities on the server, including first-time logins and Java updates. Those things sometimes take time. If you don't have anyone from IT helping you on the server part and if you're doing everything yourself and the server is available, it takes only three hours. On the cloud, it is a little easier. On-premises you also have to open the firewall ports and everything. On the high end, it might take three days, however, not more than that.

The licensing is manageable. Earlier, they had multiple license styles, and they used to charge differently. Nowadays, they have only two categories, an enterprise version, and a data architect version. It is around 5,000 euros.

If you compare it to the market and other tools and look at the functionality, it's pretty good. For a big organization, the cost would not be a big concern.

If you decide to pay for support, you get one year free when you buy a license. After that, they charge 30% of the license every year for support coverage.

The documentation, however, is pretty good, making it feasible to go without support since you can likely troubleshoot on your own.  

I'd advise others that, when you are considering licensing if you need bulk licenses, you can easily get a deal from PowerDesigner. You can easily negotiate with them since they do like to negotiate if you are buying in bulk. 

When you are doing this negotiation, at that time, you can negotiate a contract in which they will be responsible for implementing it in your environment. If you are doing the installation on your own, you can ask for technical support that will provide quick responses during the implementation to avoid waiting on tickets during setup.

SAP PowerDesigner is an excellent tool that does what I need it to do. What I like most about it is that it's stable, fast, and easy to understand.

I also found the SAP PowerDesigner repository very good. The tool is flexible, too.

The portal of SAP PowerDesigner could be better.

The tool also needs more features and integration with other products, such as Collibra. It would be interesting for SAP PowerDesigner to have more integration.

SAP PowerDesigner is a stable tool, so it's an eight out of ten.

SAP PowerDesigner is a nine, scalability-wise.

I used ER/Studio before using SAP PowerDesigner.

The initial setup for SAP PowerDesigner is difficult, so it's a six out of ten for me.

Deploying SAP PowerDesigner took eight to sixteen hours.

You need to be a database administrator to deploy SAP PowerDesigner because you need to configure the database and repository. For example, you need to be a Windows administrator to do some network configurations. Three people would be enough to install the SAP PowerDesigner, and then two people simultaneously for DA and Windows administration.

We deployed SAP PowerDesigner in-house.

When you purchase the license for SAP PowerDesigner, you have to buy one year of support. The tool is worth the money.

I work with both SAP PowerDesigner and ER/Studio.

I'm a user of SAP PowerDesigner, but in the past, I've worked for an SAP partner.

I'm working with the latest version of the solution.

I'm a personal user and not a corporate user of the tool, so I have no plans to increase the usage of SAP PowerDesigner.

I advise anyone planning to use the tool to undergo training first. SAP PowerDesigner is not challenging to use as long as you do the training for at least one week, which helps you understand how to use the tool better and all its features.

My rating for SAP PowerDesigner is eight out of ten because it's a great tool. It's stable. You only need to understand one aspect to understand all its features. My clients and I find SAP PowerDesigner great to use.

I mainly use it to create application maps and to connect other applications to IOS platforms. Usually, we use PowerDesigner in order to study the impact of modifying columns and the cut-offs in order to deploy a new data model. I also use it to handle change requests on IS, for example, pushing data models or applying the follow-up on changes done directly on other IOS.

I think that the user experience could use a lot of improvement. 

It would also be good to have a connection with CMDB. In particular, the gap analysis. Usually, when we work on a project, on enterprise architect tools, we start with a paper version and then connect the CMDB. PowerDesigner cannot analyze the gap between reality and the theoretical schema we build.

I have been using SAP PowerDesigner for about four to five years.

It is quite stable. The tool is widely used among big companies here in France and North Africa. It has evolved through the years. When it comes to stability, I would give it a ten out of ten.

It can handle everything. It can reproduce all data models, all connections, all APIs, and so on. I would give it a nine out of ten. 

So far, I have not had any need to contact SAP's technical support. 

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.

The onboarding of the solution is very difficult when we're creating a project from scratch. Even with the new version of the design, it's very difficult to create a new project and start building blocks around it. It is a very efficient tool once the first scheme is created, the first version. Then we create the business view, then the platform view, then the application view, but what could use improvement is the user experience. We cannot start without a very long tutorial, and I would say it's not very user-friendly.

The licensing model is quite expensive. It costs approximately one hundred thousand euros to initially set it up.

I would rate PowerDesigner an eight out of ten.

I was working with Bosch, where I was part of the enterprise data modelling team, and we used SAP PowerDesigner as a data modelling tool. We mainly concentrated on the manufacturing domain, so we followed the data modelling approach using Data Vault 2.0. So the organization told us to use SAP PowerDesigner as a data modelling tool. There are competitors for SAP PowerDesigner tools like Urban and many more, but our organization decided on SAP PowerDesigner. With this tool, a framework was designed by one of the organizations in Germany, and Bosch partnered with them to generate scripts automatically. SAP PowerDesigner also provides the flexibility to create logical and conceptual data models. As a team, we were mainly focused on creating physical data models using SAP PowerDesigner.

Once you create physical data models, you can check out the DDL scripts and implement them on your Oracle databases. We used Oracle databases, but SAP PowerDesigner supports a lot of databases.

It is hard for a new person to learn how to use SAP PowerDesigner, but once they understand and practice, it's pretty simple to use SAP PowerDesigner, and it's easy to take out the DDL scripts.

The user interface could be more user-friendly. We have not worked with other models, but the user interaction or the visualization of the tool should be improved because it looks like an old tool, even though it provides good features. A visualization feature would attract users and make it easier to use.

The automation could be improved because it does not provide the framework or automation but provides data modelling capability. So you have to do it on your own or get a third-party contractor to develop the automation. For us, a company integrated with Bosch and generated a stable framework. Other tools provide automation capability available on cloud.

There was a pain point when we downloaded, configured and installed the software in our local systems. So we thought to put this particular software somewhere in a central system where we can directly access using Citrix workspace because when you install this in your local systems, there is a probability that you will not be able to check in your developments to the central repository.

Organizations that are using SAP PowerDesigner or are thinking of using it may have a big problem if they are moving particular projects to offsite centers or offsite nations. We faced many issues with check-ins of our models where the central server was sitting in Germany. We were located in India, and it was hard or near impossible to check in our models after our developments. We were dependent on our German colleagues to check in our models. We used to send requests via Outlook or Microsoft Teams, and then they would check in the models on our behalf. So we started using Citrix workspace, and there was a central system where SAP PowerDesigner was installed for us. We used it to develop our models and to do the check-ins and checkouts.

We used this solution at my previous employer for about two years.

It is a stable solution, and I rate the stability a seven out of ten. We were initially facing technical issues due to authentication only. Aside from that, there were scenarios where we could not check in because we had to check in our models only using the checked-out models. We could copy our models, create a new copy, and then check in. So there are some technical things that developers should understand because you have to check in the model, but you cannot check in the same model with a different identity.

There will be a different number that the schedule gets generated for each model, and you can rename a new model and try to check in, but it will not. So, developers should know how to use the tool rather than guessing and playing. There were scenarios where other colleagues faced other issues, but I believe most issues we faced were related to authentication. Aside from that, we have not faced any major issues.

It is upon an application, and it is based on licensing. So it is just a tool for developing your data model. So scaling depends on the number of licenses the organization purchases and how many users there are. So if they purchase 20 licenses and 30 people are using them, they will face an issue. I believe about 40 users were using it.

We had no direct connection or contact with the SAP PowerDesigner team. Some of my colleagues have a few connections in Germany, but if we had faced any issues, we would have reached out to my colleagues, and they internally would have reached out to SAP.

I rate the setup a five out of ten. It was difficult to set up because we had to apply a lot of patch files one after the other. In addition, there was an issue with using the SAP PowerDesigner in our local systems and checking in to a central server or a central repository in Germany or some countries. I am unsure if this was an issue with the Bosch team or if other organizations had the same issue. PowerDesigner should work towards fixing this and providing access to the users through Citrix workspace or other version machines.

We completed the setup ourselves. Some guidelines were written by colleagues who had used the solution earlier, so we followed them and implemented them. It takes a long time to install, and you will not be sure whether it works fine. So organizations should prefer to go via virtual machines because if your local system crashes, you must start from scratch to install the software. But if that particular software is installed somewhere on a server, it would be better than installing it in local systems.

I rate this solution a six out of ten.

We use this solution for business analysis and to generate use cases. Each model is developed based on all the requirements that are gathered. There's a small install for the setup on each machine and then we operate through a shared license server that is connected to it.

One of the things that I'm working on right now is improving the health of our models because a number of them are old. We're missing a lot of information that we need as we look towards an enterprise level data lake. This will allow us to better relate ownership of the data to a particular area within ODOT.

I've used the reverse engineering feature a lot. I can take a look at the structure of the database and what relationships it has. Some of the general modeling functions are also really valuable. It's pretty simple to show people how to add objects to model and develop relationships.

I'm trying to find some of the requirements for data cataloging within Power Designer. There are some minor things that could be easier. We're writing up procedures to bring all the modeling back into one group as this reduces delays in production.  

We have experienced one issue with stability which was connected to licensing. For two or three days, nobody could get in and use the tool. Assuming we do not experience a similar incident, I would rate them a seven or eight out of ten for stability. We are no longer signed up for support from Power Designer and so we have needed to determine our own workarounds in these situations which takes some time.

The technical support for this solution is good. When we developed the instructions, we had meetings with them and changed the order of some of the things and added things that they wanted to see. 

I would rate the support for this solution an eight out of ten. 

Positive

The initial setup is straightforward. We had a problem a few years ago when we moved our from a SQL server. Out of 16 installs, we had three failures and that was because people changed from the standard setup.

We have two Power Designer administrators and I am one of them. When anyone checks in, it creates a change list. 

I would rate this solution a seven out of ten. 

We use SAP PowerDesigner for logical data modeling and physical data modeling.

The feature I found valuable in SAP PowerDesigner is extraction.

I also like that my company hasn't faced any issues because of the clear documentation about SAP PowerDesigner.

One disadvantage of SAP PowerDesigner is that you cannot reverse engineer the ALTER statements, so that's an enhancement or area for improvement I'm looking forward to seeing from the SAP team in the future. That should directly reflect on the physical data models my company builds.

I also want SAP PowerDesigner to be able to generate ALTER statements in the future.

I've been using SAP PowerDesigner for over two and a half years.

Stability-wise, SAP PowerDesigner is a seven out of ten.

SAP PowerDesigner is a highly scalable solution.

I haven't contacted the technical support for SAP PowerDesigner. Support only reaches out to me to see if there's any upgrade or patch installation issue.

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.

Setting up SAP PowerDesigner was straightforward, though the technical management team handled that. That team makes the software available for people to use.

My company hasn't disclosed ROI details to me, so I have no information on whether there was ROI from SAP PowerDesigner.

Regarding costs, SAP PowerDesigner is pricey, as I've heard from my team manager, which is why the company has been thinking of bringing another solution on board.

My company has implemented SAP PowerDesigner and no longer requires any other data modeling tool.

I'm using the desktop version of SAP PowerDesigner, version 16.5.7.

In the company, more than one hundred people use SAP PowerDesigner. My company only has twenty-two licenses, so most users rely on mobile licenses.

One person can handle the deployment and maintenance of SAP PowerDesigner.

I advise anyone looking into using SAP PowerDesigner to consider the only constraint that erwin Data Modeler could overcome and SAP PowerDesigner couldn't. erwin Data Modeler can generate the ALTER statements apart from the CREATE statements. In contrast, SAP PowerDesigner only generates the CREATE statements, which is why people prefer to use erwin Data Modeler. You also need to consider your budget. Cost-wise, SAP PowerDesigner is better than erwin Data Modeler.

My rating for SAP PowerDesigner is eight out of ten.

My company is a customer of SAP PowerDesigner.

We are using this solution for architecture management.

I have found the solution not easy to use. When publishing you have to download the HTML, make adjustments against the updated HTML, convert it to HTML, then finally paste the HTML. There is not an on-the-fly function available to bypass the step-by-step converting process that other solutions have.

The versioning system could be improved. We have to identify the connections and there are lots of limits in certain areas, such as the JDBC driver. I do not have a computer able to do the versioning system because we do not have a database to use. We do not have the budget for that. They should use something, such as GitHub, it would be helpful.

I have been using this solution for five years.

Sometimes the server goes down and I am not able to use the tools. The solution could be more stable.

The solution scalability is good.

The initial setup was very easy.

I have evaluated erwin, it has some enhanced features, such as easy publishing.

We plan to migrate to erwin solution in the near future. I would not recommend it.

I rate SAP PowerDesigner a five out of ten.