We had a team of ten engineers for the deployment process. 

Moreover, the deployment time can vary between a couple of hours and a few days. The only time it might take longer is if there are external dependencies, where another team's deployment needs to happen first. But usually, deployments are a matter of hours, not minutes.

We have our own internal team.

The installation of LoadRunner takes about an hour, and I can start building scripts on the same day. So, it takes less than a day to deliver something.

I've worked with environments ranging from 10 to 10,000 concurrent users, covering everything in between.

Maintaining LoadRunner itself is not difficult. However, the complexity of maintaining scripts depends on their complexity and the user's scripting skills. So, it is not about the tool, but it is about the user. 

We had the Micros Focus team assist us with the initial setup process. 

We did the installation of the solution with our system administrators or a manager who has access. Not everyone has the correct access to install the software.

We used a consultant to deploy the tool.

The entire implementation process was handled in-house. We did not use any consultants or integrators. 

The implementation is completed in-house.

I am involved in the installation and maintenance, including upgrades.

The vendor is an expert and helps with all the setup and installation tasks.

It was with a mix of an in-house team and vendor support. The vendor team is necessary for the initial setup, and upgrades can be done in-house, but major upgrades need vendor support.

In-house.

The deployment could take quite a while, even when I was used to doing it. Getting the software installed and running is pretty quick and that is not a problem. But creating the projects and creating the test scripts can take a little while. To get up and running and doing stuff within it, it is probably just around a week. Doing it professionally with the integrations and with all the correct testing scripts, it can take a month and more. It really all depends on the purpose and how you want to use it.  

We did it in-house.

I did the implementation by myself as part of a project for one of our customers. My advice is to understand the business need that would guide to a proper scope and design guidelines. Performance Center can be implemented in different ways (standalone, distributed, with/without integration with HP-ALM or HP Diagnostics, number of load generators and their location etc.). The implementor should arrange for the best and quickest setup that will fulfill the goals, otherwise the implementation would end up as a trip of trial and error, and probably fail, or exceed the time plan.

We did implement the software using our in-house team, but I would advise engaging HP consultants for larger installations. The complexity of our environment cannot be compared to the needs of a typical enterprise.

Orasi Software does Performance Center implementation. I am not a member of that team. I have been on projects where Performance Center was implemented by the client and then Orasi was called to correct any issues. 

Again, I cannot stress enough how important it is to have an experienced administrator. It may cost more initially but it will save time and money later.

We did it in-house with the help of a consultant.

I was not completely involved in implementation, so I don’t have much information on this.

We used a vendor team.

In-house.

We worked out the complexities ourselves.

HP vendor

We implemented it with our in-house, but we used the help desk during the entire process of implementation. Their help desk needs to know more about their own tools.

We did it in-house with help from tech support.

I've implemented it both ways, and my advice is to get the vendor to help you design a detailed plan and manage that plan.

We used a vendor team.

Through a vendor team.

We implemented through the vendor, who used highly-skilled professionals.