Omada Identity

I find several aspects of Omada highly valuable, particularly its core capabilities and flexibility: User Life Cycle Management: Omada's user life cycle management is exceptionally robust, providing a very good grip on the process. Its core capabilities are very refined and granular. Connectivity Options: The tool offers excellent connectivity, enabling connections to numerous systems like SuccessFactors and Microsoft HR via API-based connections. It provides dedicated connectors for established tools, and for others, APIs are available for integration. Controls on Role Management and Request Access: Omada provides strong controls in these areas. It effectively manages roles for various personas, including technical accounts. A significant benefit is its multi-account management and segregation of duties capability, ensuring that when a main identity is deactivated, all related access is also removed. We manage all our SAP ECC roles through Omada, ensuring segregation of finance and HR roles and overall control. The tool offers flexibility to customize role management beyond out-of-the-box offerings, useful for unique use cases like country-specific or co-location role assignments. Flexibility and Customization: A key selection factor was Omada's flexibility to create custom solutions through coding when functionality isn't readily available. This was crucial as our first IGA tool required matching cluttered processes to business needs. Omada's control and customization capabilities were strong from the outset. A notable example is a custom solution developed for retaining access and carrying forward user details for consultants converting to employees, which was not out-of-the-box and ran for a very long time. Omada also allows creation of custom fields on the Graphical User Interface (GUI). The customization aspect is highly rated.

- the product itself has smart ideas/implementations which are not available in other products - if an urgent support case arises, the manufacturer assist in solving the problem.

Omada comes with a wide range of capabilities. The most beneficial feature is its 'user life cycle management' which has always been robust and flexible. In the recent release, they have improvised the connectivity part by giving access to a range of connectors/collectors. Access based on role and assignment is top notch

Several aspects stand out as areas for improvement: Poor Reporting Section: The reporting functionality on the on-premise version is poor and has been a pain. While Omada indicates improvements in the cloud, we have not yet tested this. On-Premise Performance Degradation: Performance tends to degrade as data volumes increase. This is due to Omada's heavy dependency on SQL; when data becomes complex with multiple tables to be queried, multiple views to be analysed, performance suffers. Recommendations involve changing SQL for fine-tuning. This has led to significant impacts: role provisioning, expected in 4-6 hours, sometimes took 24-48 hours. Sink delays occurred, preventing new hires from logging in because their accounts weren't ready in the IT system. While these issues were off and on for last few years, they have improved after a health check program and Omada's recommendations. Complex Architecture and Troubleshooting: The architecture is quite complex, with so many components in between integrated. This makes troubleshooting a big challenge, making it difficult to pinpoint where the problem is and which component has the problem. Troubleshooting becomes kind of a challenging part. Steep Learning Curve: Omada is a bit complex tool to set up, presenting a very much steep learning curve. We struggled a lot with the tool to understand it and get control of it during initial years. We needed to be specific to the detail level for requirements. Past Deployment Challenges: Our initial onboarding and deployment experience was not so great at the start. Committed timelines always were missed due to complexities on the tool side to develop new things, as a lot of customizations were required and they could not come up on time. Lot of issues that were identified during the testing in UAT necessitated redo things, causing delays. Our initial deployment extended from one year to 2 years plus. However, the deployment experience has evolved and is quite different now for recent projects.

- poor availability of implementation partners - closed user group with, with less answers to questions - in public internet there are no groups or entries in stackoverflow etc, you can find solution for requirements

Omada reporting is always a nightmare, but it looks better in the cloud version. Need to do more work on real time provisioning. need a dedicated SQL developer to avoid performance issues at the data level. Deliverables from the Omada dev team never meet timeline.