...
Over time, an increasing number of services will rely on the provisioning functions of your IAM System. When selecting provisioning products (software or service, open source or commercial, on-prem , SaaS or IaaS) for use in your IAM System, as well as the services you are provisioning, it is important to consider the eventual end of life of that product, as well as how you will integrate that product initially.
...
Is it a flat fee? Does it increase with population growth, number of "seats," storage requirements, etc.? Does it consider alumni, or other internal or external users? Does it use a standard size-ranking structure, such as IPEDS?
Consider: Whether and how the product can be customized, and who can do the customization.
IAM system requirements are often very unique to each institution, requiring unique customization. This issue is particularly important for SaaS IAM services, where the vendor has control over the deployment, as well as the software implementation.
Do: Consider all other technology acquisition issues that are not specifically related to IAM.
This includes ongoing maintenance, vendor stability, ease of deployment, etc.
Product Offboarding
When selecting and onboarding a new product, consider your eventual exit strategy.
...