The main differences between the products we evaluated and erwin would be the ease of use, between logical and physical transformed models. We experimented with SAP PowerDesigner, but that was not as robust in performing what we wanted it to do. We've experimented with other solutions, such as ER/Studio, which has had different names. That's probably one of the biggest issues: Everybody has to be on the exact same version and release to be able to work together, if you're using the Model Mart repository. After we do those upgrades, we can then deploy the software on the machines.
So, we have to QA the whole process of upgrading our Windows Server and upgrading our database server. Once everybody was comfortable with the features of it, we then had to upgrade our Model Mart repository, which is where we store all of the erwin models. We all got to try the tool to see that we wanted to use it and to understand its features. We tested it on that person's box, one that everybody had access to. That could take longer, depending on what the user's roles are.Īs for our implementation strategy for Data Modeler, we just deployed it on someone's computer. There are other features, such as setting up users in Model Mart, which take longer because you have to analyze the user's needs and set up appropriate permissions. In terms of deployment, just the install of the product on somebody's machine takes about 10 minutes. We've worked with erwin and they have tried to help mitigate that, but we still do encounter issues with licensing. So when a license is locked, even though the person is no longer using the product, because that person is not connected through the cloud, erwin's system doesn't know to release the license. So, we have had some issues with licensing. People can't connect to the license server, because it's done over the cloud, so they have to do an off-line license, which locks the license. Access to servers outside of our firewall causes issues for people who work in certain regions around the world because we restrict access to the cloud for governance purposes. That's probably related to the fact that they're doing more things on the cloud, such as licensing, which has caused problems because we have very tight security here. So, I've done many deployments of erwin, as different releases have come out. I was there for the initial deployment of that as well. After being owned by CA, it then was spun off to its own, standalone company, as erwin. It was then sold to CA and I was involved when CA produced its first rollout.
The product was sold by a company called Platinum when I first started using it.
0 kommentar(er)
