We haven't really tested it for high scalability. The max number of people who will be on it in our company at one time is four or five dozen. I would think it would scale but I don't have any practical experience with it. In our company, about 20 to 30 percent of users touch the content of the solution as part of their daily roles. 

It has easily scaled to what we want. If you buy a license, you get full access. You can have as many users as you wish. I have no issues or concerns with scalability.

It seems scalable. They have fixed the main issue which was the indexing process for the search engine. It had some bugs and was causing a lot of trouble. That was the main scalability problem but they have fixed these points and isolated the indexing process. So now everything seems to be to be working and scalable.

We have created a lot of projects, so we have really used it a lot. We are going to migrate to a change-management phase where we are going to work on keeping our data fresh. It's really a day-to-day tool now for all the service managers and our project teams.

Looking to the future, I expect we will use it as we are using it today.

Anybody from the company has access to the information; it is free internally. There are 1,000 users from IT in our group. So, everyone is not accessing the tool on a daily basis. Approximately 60 percent of the staff is getting onto the tool on a weekly basis in order to dig into the information. 

I think it scales well. We've done some looking into the licensing and how many people can use it. It has good scalability features. It can support multiple users with different levels of access, from "full access," to "some access," to "read-only access," so it gets to a wide user community.

We have between 50 to 100 users. They include administrators, enterprise architects, systems architects, and we have project management, executives, and business stakeholders who are looking at the read-only portions of the data. We build the enterprise systems architectures and those stakeholders have the ability, with read-only, to look into the latest, up-to-date diagrams.

Our use is corporate-wide — and we're a big company with around 90,000 employees. We don't use it extensively throughout the corporation; it's used in a couple of domain areas. We are trying to expand the usage of it a bit.

For deployment of the solution and its maintenance, the people involved are not full-time on those tasks, but there are somewhere between two and four people who have a hand in the actual deployment of the system.

We have multiple web servers haven't had any issues with the scalability.

It has already been rolled out to everybody in the company, so I don't know if we will be increasing usage. About 2,500 users touch the content of the solution as part of their daily roles in our organization. We have one person responsible for maintenance of the solution, the solution's architect.

No issues.

Evolve is scalable with multi-user ability, so multiple designers and engineers can work on the same data model simultaneously. 

- Prior to a major upgrade to the underlying graphics engine in about 2010, we occasionally experienced slow performance when moving large numbers of objects (e.g. several hundred entities at a time) in very large models, but we worked with the Erwin technical team and the issue was resolved and has not been a problem in over 5 years of working daily with very large data models since then.

- We and our customers regularly use the "Complete Compare" function to compare and manage multiple large related models with no problems.

- We also use Erwin's metadata API to programmatically synchronize enhancements across as many as 100 large data models at a time with no problems.

I didn't see a problem with it being scalable.

We were a team of about three consistently using it at a time. If we could have gotten it deployed, we were a department of maybe 20 to 30 data architects. Of that, probably our operational architects would have used it first, and that would have been about eight or 10 people. Then, we would have roll it out to the others because we were organized into operational architects, data warehouse architects, and data vault architects. We saw that the operations folks probably would have been the first in line to work with it.

You could scale Evolve. 

The scalability is quite good, and it's normally given from the support team in India. 

We've had no issues surrounding the scalability of the solution. We have about eight users on it right now. We don't plan to increase usage at this time.

None

The scalability is good, but so far we haven't used the shared version. We use the single stand-alone version. We have only three users, and they are all data architects. We don't use any other staff for maintenance. We also don't plan to increase our usage soon.

No issues.