1. SAP Identity Management 7.2 Implementation
Road-map
SAP Identity Management 7.2 Implementation

2. Implementation plan index
Scope
Get to know auditory and stakeholders
Plan your time
Consider current ITSM environment for implementation
Harmonization program for User ID naming Convection
Build
Connections
Testing
Train the users
Go-live

3. What is sap identity management?
Central management of identities throughout system landscape.
Rule-driven workflow and approval process
Extensive audit trail, logging and reporting functionality.
Governance trough centralized and auditable identity data.
Compliance trough integration with SAP Access Control.
Compliant and integrated identity management solution to mitigate segregation-of-duties risks.
SAP Identity Management
SAP applications
SAP SCM
SAP ERP HCM
SAP ERP
JAVA
SAP HANA
Successfactors
Non-SAP applications
Database
Legacy
Web-app OS …
SAP Access Control

4. Identity life-cycle Relationship Start Relationship End
Provisioning
Routine User Management
User Support & Self Service
De-provisioning
Re-engage
Creating accounts
Gaining access
Relationship Start
Relationship End
Turn key
Remove all access

5. IDM Connection approach
SuccessFactors
Integration with SAP Business Suite and Successfactos
SAP Identity Management
SAP Access Control
SAP applications
Non-SAP applications
SAP ERP HCM
Identity virtualization and identity as a service
Compliance checks
Central identity store
Approval workflows
Web-based single sing-on and identity federation
Reporting
Provisioning to SAP and non-SAP systems
Password management

6. 1. Scope
Build a clear strategy of Identity Management – decide which systems needs to be connected. Vision should cover whole landscape which will deliver the implementation of SAP Netweaver Identity Management.
Include into your strategy which and when those systems needs to be included.
Strategy should include as a key point SAP GRC Access Control and SAP Single Sign- On Integration.
Present the vision and strategy to top management. Project Sign-off.

7. 2. Get to know auditory and stakeholders
Get to know which people, from which parts of company needs to be involved in the project.
Early stakeholders involvement.
All stakeholders have to be involved in project planning to be aware and to sign before the implementation starts.
Adjust the system and project to business processes and prepare to roll out to the organization.

8. 3. Plan your time
Be sure that you have enough of resources and people have right skill-set.
Consider your budget, that you have to pay for each phase.
How long will it take to reach each phases in your implementation. Consider buffer in your estimations.
Plan your time in order to current ITIL environment

9. 4. Itsm environment
Use change management tool for each scope phase and changes within
Consider that some change requests will take more time than the other. Make sure that you will prioritize using standard connectors. Custom connectors will take more effort and time. Be sure to take the right approach from change management perspective.
Identity Management is a powerful toolbox, which is able to provide a lot – but not everything.

10. 5. Harmonization program for User ID naming convention
Define and implement consistent user ID naming convention throughout all systems.
Consider SAP HCM, Active Directory, SAP, OIM
Create mapping table for each of a system
Define master system for creating ID’s (master attributes)
Ensure that you will get high quality data from the master system

11. 6. build
At this point all business processes should be clear and well known to the implementer.
Define and create accordingly User Interfaces (like Password reset tool, Security team project tools, user management tools).
According to business processes define which users should maintain which attributes.
Creating first build of IDM system design.
Due to requirements create reporting functionalities.

12. 7. Connections
Creating technical design for attribute mapping between various systems which are in scope.
Adding and creating connections between IDM and scope systems.
Testing the connection.
Do notification extensions for UI workflows.
Testing build version in order to current connections/business processes.

13. 8. Testing
The most important part is to test standard connectors (the ones which will be used most frequently).
Try to reduce the customization of enhanced framework.
Involve Security team in functionality testing.
Get a proper sign-off for this phase.

14. 9. Train the users
First training needs to be delivered for 2 members of IDM administrators who will be able for solution handover.
Deliver a training for each of member of Security team. Make sure that they are able to use all functionality and tools that IDM provides.
World-wide training for end users.
Make sure that everything is documented. Good documentation for end users will reduce the number of incoming incidents significantly.

15. 10. go-live Don’t start go-live with a big bang.
Divide go-live in 3 groups and 3 phases.
Go-live for IDM team members. Phase where all systems in scope and stakeholders of those systems are aware that you are live in current solution. Go- live should take about a week.
Go-live for Security team members. Phase where all functionalities for Security team are being used for project related actions, daily basis management. This go-live is mainly for hyper-care reasons.
Main go-live for Sec. Team and all end users. Main hyper-care takes about 6 months.