It's my understanding the initial setup isn't very difficult. However, I don't do the setup in the PoC. 

I have only with the phone connection and I don't think it's very difficult.

The initial setup is pretty simple and a straightforward mechanism. It does require some knowledge on how to set up and a basic understanding of networking protocols and other things, which is pretty complex. It's not something that's easy to learn and I think SailPoint could look at bringing out intuitive-based migration> There are 10 people in my team who deal with implementation and deployment and the time it takes generally depends on the scale of the setup. One of our larger projects took around three months. 

The solution was easy to install for me but might not be for someone who is not used to the
methodology.

On a scale of one to ten, I would rate the initial setup of SailPoint as a two. It's rarely an easy process, and the ease of setup depends on the resources allocated. However, compared to my experiences with other enterprise systems, SailPoint's setup was relatively better. Its out-of-the-box integration with Broadcom and Active Directory was particularly advantageous, addressing around thirty-five to forty percent of our challenges without requiring additional customization.

The platform deployment was pretty easy. But when you start to onboard the applications, it becomes more complex. The whole configuration depends on the application architecture and how you should set it up. All the cases are different, and that can be quite challenging.

The initial setup is not straightforward and takes around a month to complete. Two persons are required to deploy the solution. An experienced person is needed to use IdentityIQ.

The implementation involves installing the application and the database on different machines. Then, we will proceed with the integration based on the data we receive from SailPoint. After that, we will discuss with the customer the connections they need to close accounts and the rules for creating accounts. 

Once this process is complete, we will check for related accounts and generate a report accordingly. This report will be sent to the responsible owner, who will be identified through SailPoint. We will assist the customer in assigning those accounts to the correct owner. Following that, we'll assist in setting up the business decision template and help the customer launch their subscription, guiding them through each step and aiding the manager in signing off on certifications.

The deployment requires someone specialized in the solution. It can be expensive to set up, however, once it's deployed and properly up and running, it's very easy to use. 

That said, the initial setup is not straightforward. Any IAM project takes some expertise to deploy, as it's not an easy technology to get going. it's the same as a SIEM solution. You need to have a good understanding of the technology and spend some time with the customer in order to completely understand his requirements. After that, you will be able to do a proper deployment.

The amount of personnel you need depends on the size of the environment, however, the bigger the environment, the more technical team you need. You need at least one expert on the site to handle the project, just one expert, who will put in the guidelines. After that, you can have, two or three junior people to do the repetitive tasks.

The product's initial setup phase was satisfactory for our company.

I rate the product's deployment phase a nine on a scale of one to ten points, where one is difficult, and ten means it is easy to deploy.

Depending on the infrastructure where the product is required to be deployed, the deployment process, along with the updates, can take a week's time.

I rate the initial setup process a seven out of ten. It takes a couple of days to complete.

Initially, I had difficulties, but with time, I gained experience. Especially integrating legacy applications like ARPAQ. Over time, it became easier, but integrating legacy apps remains a typical issue.

In terms of user experience, I don't have any complaints.  We are planning to migrate to the cloud.

Installation requires knowledge of application servers and relational databases; a high availability environment can be setup in a matter of hours-days once infrastructure is in place. IdentityIQ requires a relational database and supports all the main flavors, Oracle, IBM, Microsoft, MySQL; IdentityIQ runs on a Java application server, again the common platforms are supported, Oracle, IBM, Apache Tomcat and Red Hat JBoss.

The initial setup is straightforward. This took one week. 

The solution’s initial setup is complex.

SailPoint IdentityIQ has a straightforward setup. I'd rate its setup a five out of five.

The initial setup was straightforward. We knew our requirements, and we've got all the infrastructure required for the system. We didn't have a lot of issues with the product itself. There were some vulnerabilities in the product, but they addressed them in the next version. They were able to address them in version 7.3.

Our deployment took us about, I would say a week. We had to do it in different phases. 

The implementation strategy we had was to start with first, deploying development and QA systems. Then gather lessons learned from these systems, then go to production. That helped us a lot because we found out that we have a lot of concerns with our infrastructure. There were a lot of firewalls that we had to open to communicate with the external system, with the Cloud system that we needed to connect to. So, a lot of that was more like ad-hoc testing. Because we weren't sure how many of the firewall ports we needed to open and which ones we needed. That took a lot of our time. It was just the infrastructure from our end. In terms of the installation of the product and the implementation of it, that was very quick.

We have a big staff because we are integrating with so many other systems from HR to Active Directory to SAP. So the core team is about twelve to twenty people, but the extended team, I would say, if you combine them all together with all the work we've done, is probably more than thirty or forty. They are not all technical. Some of them were just there for governance or requirement gathering.

The implementation is straightforward. It depends on the environment and customers’ needs. However, it is easy.

The initial setup of SailPoint IdentityIQ was very easy, and I rate it a ten out of ten. We have an automatic deployment engine, so the deployment takes around an hour, not long.

The setup is very, very easy. Identity IQ is the on-premises software for the solution and it is easy to setup. There are modules to install so the only thing you need is time to complete them. 

The initial setup is easy.

IdentityIQ is difficult to begin with, but compared to its competitors, it'd be an eight out of ten in terms of ease of setup.

The deployment duration varies. They've got examples of people being up and running in a month. For massive companies with hundreds or thousands of employees, it takes a couple of years to get fully implemented, but they've got ways where you can implement it almost by a business unit, so you can be up and running and then slowly, you add the rest of the company to the implementation.

In terms of the number of people required, the actual SailPoint team would be three to four people, and then they use the business analysts in the company to help onboard the application. That's a really nice methodology where I can spread the workload over a bunch of people instead of having to rely on one person and get those backlogs and lineups form. For example, I can have a business analyst from the business units I'm working with help me onboard applications. That really speeds it up.

In terms of the deployment model, they have a SaaS version, but you can do it on-prem, and you can also do it with the hybrid model.

While the setup is very easy, the real difficulty lies in creating the connectors for work service.

The deployment time varies with the project and client and can last anywhere from three months to a year or two. We have a smaller project involving 100 employees and a larger, more difficult, one involving 10,000. The latter requires a longer deployment period and more connectors. 

SailPoint IdentityIQ's usability depends on how well it is implemented. To set up the product, you must configure it like a web application. This involves setting up a web server and determining the number of servers needed based on the site's requirements. The setup process can vary in complexity depending on the client's environment. It can take a day to complete. 

The initial setup for SailPoint IdentityIQ was straightforward.

Its installation is easy, but it depends on how many and what types of identity sources you have. If you have well-defined sources, such as active directory, LDAP directory, or some other application directories, it is very easy, but if you have only databases with identities, it could be challenging. It is not always easy to deploy identity management solutions in organizations because there are too many identity sources that have to be integrated.

The deployment duration depends on the scale, complexity, and number of sources. Typically, in enterprise organizations, it could take from six to nine months to cover the whole organization. It can even take a year. For customers with less than 20,000 or 30,000 active users, you can deploy it in less than three months.

The initial setup is very easy. There are no challenges with the implementation.  The deployment strategy depends upon the kind of applications you want to integrate. Implementation time is based purely on your number of connectors, the kinds of applications, and the user environment. 

The setup was pretty good. We have five people that can handle deployment and maintenance. 

The initial setup is very straight forward and it takes around 30 minutes end to end. It is a Java app on a web server so you can do it locally and very quickly.

The initial setup is easy.

The initial setup is complex due to the handling of identity and access management. If you have the expertise and if you are trained well, then it is not difficult. Deployment takes between three and twelve months.

This solution takes a long tome to deploy, but it is not complex to setup. A medium-scale deployment will take you about one year.

The system requires about ten to fifteen people to maintain from various teams i.e. active directory, access management, security etc.

The initial setup of SailPoint IdentityIQ is easy. The time of deployment can take approximately two days.

We moved from Oracle Identity Manager to SailPoint and the initial setup was not straightforward. It took two to three days and was done is small steps. 

It was straightforward to implement, which is an advantage with products deployed on-premises. However, there is minimal documentation around the firewall on SailPoint community sites. For example, sometimes, we want to configure SailPoint IdentityIQ for our developers in a development version, and we don't want it to connect inside a company's firewall. But that is not addressed in the architectural documents. The documentation covers areas like check configuration or DR configuration but does not mention options for different networking structures between a web server and a product and how it works. Deployment is dependent on the project. Sometimes we complete it ourselves, and other times it's done by a third party.

It was straightforward.

The initial setup was easy, and the implementation was completed within four months.

It was a standard installation. It wasn't too complicated or easy. It is a typical out-of-the-box installation. We could do it all ourselves with our in-house engineering capability. We need at least one engineer for deployment and maintenance and 10 people for support. It's a multi-year project for us split into three phases. I was there for phase one and part of the second phase. The third phase is ongoing.

It can be a bit complex and requires training and a strong background in IT systems and some software development, but other than that it can be learned over time.

The initial setup is straightforward. The deployment time depends on the customer's requirements. If we are using our maximum resources, it takes about ten days.

Its initial setup is not straightforward. No identity management solution is straightforward.

The installation consists of two parts, the one for coming up with the rules, for which we go to the input, the other for providing some assistance in the creation of the rules and accesses. Once that part is done, the tooling part is pretty simple.

The installation is straightforward. 

I do not recall how long it took. 

Initial installation is straightforward and takes less than one day, once you have a VM, a database, and a directory available. What takes the most time is the connectivity to each authoritative source and target directory.

Given a person has a background in implementing solutions, site architecture, and infrastructure, I rate the difficulty level of the current solution as an eight out of ten, with one being very difficult and ten being very easy.

The solution is deployed on the cloud, hybrid cloud and on-premises.

The basic deployment of SailPoint over user lifecycle management can depend on a client's use cases. However, for the basic setup of the system, it may take a week or so to get the solution ready with everything configured. One architecture is enough to carry out the deployment process. Also, the number of people required for maintenance depends upon the total number of use cases we have configured, so we can't categorize or quantify it.

The initial setup always was straightforward with shorter implementation times and quick benefits.

The initial setup of the product is relatively straightforward. The complexity really depends on the customer requirements, business rules or processes that influence how difficult the implementation gets. On average, it probably takes a couple of days to install the product. But once it is installed, then you have got to have the product usable and working with other solutions and other systems. For that, it needs to be configured to have that connectivity with those other systems. That is where some of the implementation time starts to add up. To install a base active directory kind of set up takes about two weeks. 

We have configured and setup some basic functionality for a client within these tight timeframes. To do that you will need real business buy in to clear hurdles out of the way for the dependencies for the install, the infrastructure, business requirements etc.

The initial setup isn't really complex, but it is difficult. It could be simplified in many ways. Right now, it's not straightforward. Up to 80% of implementations do not go to plan.

The initial setup is straightforward. Easy installation and configuration.

It was complex. Identity and account management is very heavily dependent on the accuracy, authority, and timing of the source data. As the implementation progressed, we became aware more and more that some of the missing detail (especially around the exceptions of when a central unique Employee number is actually "central" or consistent, or the complexity of some of the attributes - e.g. whether their validity is date dependent, allowing for multiple values, etc) will cause issues in the proposed processes and the timing of providing access when required.

I would say it's simple (compared with OIM 11gR2, but more difficult when compared with MS FIM 2010 R2).
IdentityIQ has very good documentation and you shouldn't face problems with the installation.

It was pretty straightforward, just need to follow installation documentation properly.

The setup was straightforward.

It was straightforward as we have a lot of experience with Sun IDM.

The initial setup is straightforward. The time it takes to deploy depends on the size of the organization but it is reasonable. 

The initial setup was straightforward. The deployment was okay.