The tool's deployment is easy; I rate it nine out of ten. You need one resource with the basic knowledge to run the scripts to deploy it. We document the process. It has a few variations from customer to customer. 

The project begins with an architect who assesses the customer's needs and the environment, whether on-premise, in the cloud, or SaaS-based. The architect then plans the installation and configuration of the environment. Following this, a system engineer or technical expert handles the installation process. Two resources will be involved in the maintenance. 

Along with the architect and system engineer, a developer must be present for the installation process. Additionally, another technical expert with knowledge of operating systems is required. This individual should understand how to manage certificates, particularly as they may expire over time. They should also have a basic understanding of Java to navigate the key stores and configure the product during installation.

It really depends on the use cases of the client, and what they want to accomplish with the solution. Standing it up and putting it into production is pretty straightforward. Addressing the use cases is where the rubber meets the road. That's where companies like GCA bring value. Standing it up is just the beginning. Actually implementing it to serve the needs of the business and use cases is what makes the solution effective, so it just depends on what the business is trying to accomplish. Identity governance and administration is never ever done. You implement it, and it touches every aspect of the business. If someone changes from SAP to Workday or something like that, it touches identity, and if a source of truth changes, then that affects the identity governance policy. It's the source of truth for all identity and provisioning to provisioning of access and services to an employee or a contractor or a customer, so it's never done.

Standing up the solution can probably be done in a matter of weeks. Effectively implementing it and integrating it with all the sources of truth that a company has, the applications that it touches, and if it needs to provision identities and connect them with access to applications could take years. It just depends on what the company's trying to accomplish, how much money they have to spend, and how quickly they want to act.

The initial setup is a five out of ten.

The solution was very easy to set up. 

If you are installing it for the first time and have no prior experience, then the initial setup may be hard. Once you have more experience, you will be fine.

In initial implementation is very easy. It's not too difficult. 

We usually deliver this kind of project with a team of three people. One project manager is typically involved just in the project management task and then one functional guy, as we have to interact sometimes with the business side and the access certification, et cetera. You have to tell them about the purpose and the interface and how we expect them to respond. Then, there are one or two technical people needed that implement the software at the beginning and then integrate each application of the customer. We usually have a mix of compromise and cloud applications and different flavors and types of architectures. Each project depends on how many applications the customer wants to integrate. Sometimes you need two or three technical people working in parallel just to achieve on the timeline of the project.

Was a bit complex, the Installation process can be definitely improved and re-designed. There is no installation wizard. Instead, lots of manual third party software installations and configurations.

The initial setup is very straightforward. It’s simple.