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.

The initial setup was very easy.

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.

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.

The deployment varies, with some projects on Azure and others on Oracle.

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.

It is easy to set up because after you download the installer you click next multiple times and you are finished. You can install every specification test and feature. It has many features, and you can install everything, instead of everything individually, it is easier.

If you want to build logical or physical data models for fun, experience, or studying, it's easy to install and set up.

I rate the initial setup of SAP PowerDesigner a nine out of ten.

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. 

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

The initial setup is straightforward now but initially took some time to get used to. I've been using it as a user, not as an administrator. We connected to a repository and the name and user login was automatically remembered so it took about one minute.

At one point, we observed an error when two users have been doing check-ins of this model at the same time.

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 complexity depends on the client, the firewall, and the company's rules of who can use and view different things. 

I carried out the initial setup myself and would say that it is moderately difficult. There's a lot of reading necessary on the documentation and if you're setting it up for the first time you might require technical support. Implementation took several days but the timing really depends because some of it requires the trust structures, opening up parts, etc.  

The initial setup is straightforward. There's nothing complex about it.

It will take some time to teach yourself how to use the product, but the installation is nothing. It's an hour or two to deploy it.

The initial setup is somewhat complex, although I've seen worse. We work with the vendors to implement this product. Deployment time was around two weeks and the installation took a day. The solution doesn't require any maintenance. We currently have 10 users, and we want to expand that but because the tool is not user-friendly we haven't done that yet. 

The initial set up of SAP PowerDesigner was okay. But it really depends. For example, the initial setup for a startup would be an easy task. If it's a bank, you can't install it by yourself.
In my experience, it took months to set up and deploy SAP PowerDesigner for one of my banking clients. 

The initial setup is very straightforward. It's not complex at all. You just install it. You just click on the install button and go ahead and install everything. 

It will also ask if I want a backend repository database. If you say yes, then they will install the database. It is called a Sybase SQL Anyware. Now it is owned by SAP. I don't know exactly what they call it - maybe SAP SQL Anyware or Sybase SQL Anyware. 

In the end, it doesn't take more than five or ten minutes. it's very quick and efficient.

The setup of this solution is easy, but using it is rather complex.

The initial setup was straightforward. It took around one hour. 

The installation is in the average difficulty range.

The setup is very simple. 

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 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.

Straightforward.

It was easy to install.