Identity Management System

The Vendor is required to provide identity management system, which will reach end of support in January 2029.
- The new identity management solution must address these gaps, support for complex user relationships and integrating a broader range of users, including external and community members.
- Requirement:
1. Environment setup
•    Establishment of minimum required environments: testing, development, and production.
•    Integration of representative systems across multiple areas and contexts.
2. Data migration and system integration
•    Like-for-like replication of user and attribute data from PeopleSoft, modern campus MIM, active
•    Directory and Entra id, including unique identifiers and namespaces
•    Support for systems as they build out new design, ensuring integration with sources of truth and systems of record.
•    Integration with ad and Entra id in applicable environments.
3. Solution design and use case analysis
•    Develop a solution design document outlining the proposed architecture.
•    Collaborate on architectural design.
•    Analyze primary and necessary use cases for version 1.0, including those currently supported by MIM (Microsoft identity manager). and map to the recommended solution
•    Deconstruct existing MIM functionalities to align with new governance and administration (IGA) requirements.
•    Define the functional scope of integration and capabilities required.
4. Access management and lifecycle events
•    Catalog the default set of access, accounts, and privileges automatically granted to a user based on their primary affiliation access, for all user types.
•    Analyze lifecycle events for all user types and map them to MIM capabilities.
•    Design identity management use cases for the new solution.
5. Documentation and planning
•    Solution design document
•    User manual
•    Resource plan
•    Proposed project team structure
•    Implementation plan
•    Test documents to support testing activities
6. Training and knowledge transfer
•    Deliver configuration and administration training.
•    Conduct technical training.
•    Implement shadow training for key university resources during design and deployment phases.
7. Data migration and business continuity
•    Develop a data migration plan covering both legacy and new environments.
•    Prepare business continuity and disaster recovery (DR) plans.
•    Provide it security and business continuity plans.
8. Support model
•    Propose a support model, including service level agreements (SLAs), support plans, and disaster recovery plans.