Our proven Methodology for successful Identity Governance and Administration Projects

1. Omada IdentityPROJECT+
The Proven Methodology for Successful
Identity Governance and Administration Projects
DO MORE WITH IDENTITY

2. Copyright © 2001-2019 Omada® A/S. All rights reserved.
Due to continued product development, this information may change without notice. The information remains the
exclusive property of Omada A/S. If you find any problems in the documentation, please report them to us in writing.
Omada A/S does not warrant that this document is error-free.
The information in this book is true and complete to the best of Omada’s knowledge. All recommendations are provided “as is”
and Omada makes no representations or warranties of any kind as to the correctness and/or usefulness for a specific purpose of
these recommendations or other information contained herein. To clarify, Omada disclaims any warranty, including but not limited to,
warranties of merchantability, satisfactory quality, accuracy, usefulness for a particular purpose or completeness and will not accept
liability for any such warranty, whether express or implied, in connection with the use of this information.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means,
electronic, mechanical, photocopying, recording, or otherwise without the prior written permission of Omada A/S.
IdentityPROCESS+™, IdentityPROJECT+™ and Omada™ are trademarks of the Omada group of companies.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Omada A/S | Østerbrogade 135 | DK-2100 Copenhagen | Denmark
Omada Solutions Ltd.| 120 Pall Mall | London SW1Y 5EA | United Kingdom
Omada GmbH | Bad Nauheimer Straße 4 | D-64289 Darmstadt | Germany
Omada Solutions Inc. | Lytton Avenue | Palo Alto, CA 94301 | USA
Omada Solutions Inc | 413 Stuart Circle | Richmond, VA 23220 | USA
Omada | Postępu 17A | 02-676 Warszawa | Poland
www.omada.net | info@omada.net

3. Content
IdentityPROJECT+
IGA Business Challenges....................................... 4
Omada IGA Building Blocks................................... 5
IdentityPROJECT+................................................... 6
The Core Principles................................................. 8
The Three Phases................................................... 9
The Structure of Project Phases ........................... 10
The Explore Phase............................................ 11
Fit-Gap Analysis................................................ 13
The Build Phase................................................. 16
The Operate Phase ........................................... 18
Project Organization and Roles............................. 22
Project Plan........................................................... 25
Appendix................................................................ 27

4. 4DO MORE WITH IDENTITY
Introduction
IGA Business Challenges
The Growing Need for IGA
All organizations, across industries and governments, have a number of IT-related
challenges in common. Complying with legislative or industry-specific regulatory
requirements is increasingly time- and resource-intensive. Cyber security threats
are diversifying and becoming more severe. Digital transformations are
accelerating, whether driven by market forces or internal priorities. And, above
all, these and other pressures need to be addressed with limited budgets.
Compared to other potential solutions to these challenges, identity governance and
administration (IGA), also referred to as identity and access management (IAM),
is uniquely capable of simultaneously strengthening compliance, reducing security
risk, and improving efficiency through automation of processes.
At the heart of digital transformation
IGA is central to digital transformation, from empowering employees to enabling
secure and efficient collaboration with contractors or partners. Thus, implementing
or upgrading to the latest IGA solutions has become a top priority for many
organizations. However, projects can be incredibly complex, and success is not
guaranteed. IGA’s ability to address many core business challenges means
balancing diverse interests. IGA solutions also span multiple constituencies,
including employees, contractors, business partners, and even the identities of
machines, adding to the complexity.
IGA success depends not only on selecting the right technical solutions, but on
adopting the right project methodology. This Omada guidebook outlines the project
methodology that has built Omada’s reputation for having the highest project
success rate and the most satisfied customers in IGA. It starts with a recognition
that success relies on excellence in technology, people, and processes to deliver
the targeted business value.
PEOPLE
PROCESSES TECHNOLOGY

5. 5 IdentityPROJECT+
The methodology described in this guide covers one element of the four fundamental building blocks in the Omada IGA value proposition.
Each block plays an important part in helping customers and partners achieve excellence in managing
technology, people, and processes.
A Complete Solution for Successful IGA Projects
Omada IGA Building Blocks
Omada Identity Suite
IGA software and
as-a-Service
IdentityPROJECT+
Implementation
and Operations
Methodology
IdentityPROCESS+
Best Practice IGA
Process Framework
Omada
Academy
E-Learning
and Training
Omada’s Four IGA Building Blocks:
• Omada Identity Suite (OIS): IGA as-a-Service or on-premises software
installation with feature parity
• Omada Academy: IGA e-learning and in-person courses for partners and
customers
• IdentityPROCESS+: The leading IGA best practice process framework
• IdentityPROJECT+: The proven project methodology for IGA success
(described in this eBook)
These four building blocks reflect our focus on not only providing leading
technology, but equally important on ensuring the success of our customers and
partners. Together, these building blocks deliver rapid and reliable results that give
organizations the maximum value from their Omada IGA solutions.
Fig. 1: Omada’s four IGA building blocks

6. 6DO MORE WITH IDENTITY
Introduction
IdentityPROJECT+
IdentityPROJECT+ supports the execution of short iterative projects that always
follow a three-phased sequence: EXPLORE – BUILD - OPERATE. This phased
approach supports the complete lifecycle for IGA – from implementation to
operations. IdentityPROJECT+ strives to deliver business value incrementally in
2-3 months releases. The project team is guided to implement the most valuable
and important functionality first. Priorities vary across organizations, and the right
balance between business priorities must be determined.
Determining what is most valuable and important from a business perspective
creates clarity. From the outset of the project it is imperative to set clear,
measurable goals and to balance compliance, risk, efficiency, and cost. An
unbalanced focus on these parameters, may lead to lack of alignment between
stakeholders and undesirable outcomes lacking transparency or benefits. With
the business priorities clearly defined, IdentityPROJECT+ will lead to an optimally
balanced IGA solution.
Explore - Build - Operate
Omada has developed the IdentityPROJECT+ methodology based on 20 years of
experience in IGA projects. We are committed to continuously refining and further
developing the methodology based on our ongoing experience and in line with the
changing needs of our customers and partners.
This guide describes the methodology in some detail, but it also refers to related
documents, templates, and tools. These are continuously made available on the
Omada Hub - our knowledge sharing portal for Omada partners and customer
organizations (Referred to as The Organization in the eBook). IdentityPROJECT+
uses standards targeting the specific needs that IGA projects require. While it
has a strong focus on delivering according to best practices, it also provides the
required flexibility to support an organization’s unique requirements.
Fig. 2: It is imperative to set clear, measurable project goals and to balance compliance, risk, efficiency, and cost

7. 7 IdentityPROJECT+
BENEFITS OF THE METHODOLOGY
The overall benefit of IdentityPROJECT+ is that it enables organizations to
implement IGA with the IdentityPROCESS+ framework and create business value
in a proven, systematic way.
IdentityPROJECT+ enables organizations to:
+ Get measurable and valuable results faster through streamlined projects
+ Guide the implementation team through all project phases to be completed on
time
+ Adopt standardized, well-documented, extensible best-practices that ensure
delivery of future-proof IGA solutions
+ Exploit best-practices and offer automation options
+ Improve project progress monitoring and keep stakeholders informed
+ Reduce total cost and risk of implementation through an iterative
implementation roadmap
+ Discover the power of unique features and tools built into Omada solutions
+ Incorporate organization and partner teams
+ Seamlessly integrate IGA in your existing environment in terms of adaptation
of tools, reporting, technical platforms, and deployment requirements
+ Utilize Omada-certified project managers, architects, and consultants to design
lean IGA solutions in the most optimal way
I started reading this eBook
wondering what I would get out of
it. By the end, I had a very clear
idea how successful projects
should be run. Combined with the
templates and other tools on the
Omada Hub, it is another great
example of how Omada cares
about creating business value!”
Jesper Stener - Sales Director, ICY Security
“

8. 8DO MORE WITH IDENTITY
IdentityPROJECT+
The Core Principles
Omada has developed many of the best practices in use throughout IGA today and Omada project managers and architects have been involved in hundreds of
projects in a wide range of industries. This experience is reflected in the core principles of IdentityPROJECT+.
Utilize short iterative cycles
IdentityPROJECT+ supports short iterative cycles
focused on measurable value. A core focus of each
cycle is that the most valuable and important
functionality is prioritized and implemented first.
Map deliverables directly to the
business value
Each IdentityPROJECT+ deliverable is mapped
to a clear, objective description of the value it is
expected to provide.
Apply only proven tools, methods, and
processes
The IdentityPROJECT+ methodology relies on
proven OIS supported architectural building blocks,
standard interfaces like REST APIs, workshop
templates that ensure productive stakeholder
engagement, and well-defined processes.
Implement best practice processes
Avoid reinventing the wheel and maximize ROI.
IdentityPROJECT+ encourages the use of Omada’s
IdentityPROCESS+ best practice framework as the
basis for implementing IGA processes.
Evaluate value fulfillment continuously
IdentityPROJECT+ takes into consideration that
IGA projects are business projects. Therefore, it
is important to measure the success of the project
on an ongoing basis using relevant business
metrics.
Utilize continuous feedback to improve
and extend the methodology
IdentityPROJECT+ projects are a series of short
cycles, each providing feedback for the next. In the
same way, Omada is continuously learning from
feedback from our partners and customers, and
incorporating improvements into the
IdentityPROJECT+ methodology.
+

9. 9 IdentityPROJECT+
IdentityPROJECT+
The Three Phases
EXPLORE BUILD OPERATE
The IdentityPROJECT+ methodology is structured around projects that consist of three phases – Explore, Build and Operate. All IGA projects are recommended to
move through these three standard phases iteratively. The IdentityPROJECT+ methodology is tailored so that the phases Explore-Build-Operate can also be
partially run in parallel to adjust to different organizational requirements. In fact, several projects can run in parallel in a program.
For example, an ‘Explore’ phase and a ‘Build’ phase can run in parallel across two projects in a program.
However, two phases can never run in parallel within one single project.
Fig. 3: The three IdentityPROJECT+ phases

10. 10DO MORE WITH IDENTITY
Each phase consists of a set of activity groups and deliverables. Deliverables are outcomes of a phase and serve as the input to the following phase.
Each deliverable is defined by clear and objectively measurable output. Each phase is supported by tools and accelerators that are utilized to
produce the deliverable in the most effective manner. Activity groups contain a number of activities related to reaching a successful deliverable.
The Structure of
Project Phases
Fig. 4: The relationship between a program, projects, phases, activity groups, activities, deliverables, and milestones
IGA Program
Activity
IGA Project
Phase
Milestone
Deliverable
Activity Group
Work Breakdown
Structure
Deliverable

11. 11 IdentityPROJECT+
THE EXPLORE PHASE
The EXPLORE phase involves planning and preparation for the project. During the
EXPLORE phase, information is gathered, and decisions that are important for the
subsequent phases are made.
The project plan and the project schedule are prepared during this phase. A
project charter is created that outlines business priorities, requirements, and other
project fundamentals.
One of the main deliverables is the signed-off Business Blueprint, which is a
detailed documentation of the results gathered and conclusions made during
workshops. A fit-gap analysis is used during workshops to secure progress and
adherence to best practices.
Achieve Fast Concrete Results
IdentityPROJECT+ supports a fast approach to align on an initial scope for the
first Business Blueprint, as it leverages the IdentityPROCESS+ best practice
process framework as an accelerator. A subset of the business processes within
IdentityPROCESS+ is pre-described/defined in a solution scope named Omada
Essential, which every IGA project can benefit from starting with, and which by
itself adds business value to the organization.
Although every organization has its special business requirements, objectives,
scope, and priorities, utilizing Essential as an accelerator to get to an initial scope
fast is a tremendous boost. Then, each subsequent phase will build directly on
the Essential solution and provide additional value to the organization. This
recommended iterative approach demonstrates fast, concrete results to the
organization and reduces business risk.
Activities in this phase include:
• Establish project charter
• Establish project communication plan
• Establish team and roles and get commitment to suggested resource allocation
• Conduct kick-off meeting
• Improve / finalize estimations of future releases (in a phased, iterative approach
for the next 1-2 releases)
• Sketch the needed project releases and rollout strategy
• Conduct a fit-gap analysis utilizing IdentityPROCESS+ vs. customer
requirements
• Create and sign-off Business Blueprint
• Create test use-cases with objectively measurable definitions of success
• Establish a common understanding of the future solution support set-up
• Conduct scoping and architecture workshops and finalize prioritization of
requirements
• Determine requirements which cannot be implemented as a standard
• Agree on IGA processes needed based on IdentityPROCESS+
• Agree on overall SoD concept, account concept, naming concept, overall role
model concept and other concepts
• Define data quality requirements and current status
• Agree on overall design of interfaces
• Define Change Request procedure
• Define Issue Handling procedure
• Establish rules for dealing with custom code if needed in BUILD
• Establish high-level design of (potential) custom code and deployment
packages

12. 12DO MORE WITH IDENTITY
The output from this phase includes:
• Project charter created and signed-off
• Project resources allocated and committed
• Kick-off conducted successfully
• Signed-off project plan with key business-centric milestones
• Clear allocation of team members’ role-responsibilities
• High-level estimate of time allocated for the duration of the project or program
• Agreement on Change Request or Issue Management procedure
• Business Blueprint (including solution design) created and signed-off
• Architecture design document created and signed off
• Gaps identified and agreed to, gap resolution created
• Service ‘lights on’ or software installed
Sample tools provided to support this phase:
• Project plan template
• Kick-off agenda template
• Business Blueprint document template
• Business Process Master List template document, following the structure of
IdentityPROCESS+
• Office templates for scoping and running a workshop
• Runbook for how to scope and run workshops
• Guidelines, detailed questionnaires for workshops
• Change Request template
• Quick guide for account model
• Quick guide for survey/recertification concept
• Architecture Design template
• Omada manuals and eBooks for OIS and IdentityPROCESS+
Fig. 5: IdentityPROJECT+ provides a high-level project plan template which is useful, e.g. when preparing for steering committee presentations
Explore
Operate
Build
Build
Build
Explore
Explore Operate
Operate
Project start
Blueprint signed
Essential Solution Scope Live
Super users and
administrator training
Fully automated governance
of access
Legacy IAM
decommisioned
3 months
6 months
9 months
Lights-On

13. 13 IdentityPROJECT+
The IdentityPROJECT+ fit-gap analysis which is performed during the Explore phase is a great way to map an organization’s requirements to best
practices as defined in IdentityProcess+ and to identify potential gaps.
1. Priorities (e.g. based on the organization’s defined use cases) are
mapped into detailed standard process areas and process descriptions
2. Organizations’ fit to best practices and Omada Identity Suite (OIS)
standard capabilities and potential gap areas are identified
3. Organizations’ gap to OIS standard features are analyzed and changes
are defined and estimated
4. Solution design is produced including standard fit configuration and
described solutions for closing the organization’s specific gaps
Fit-Gap
Analysis
Fig. 6: An IdentityPROJECT+ fit-gap analysis is a great way to map an
organization’s requirements to best practices as defined in IdentityPROCESS+
and to identify potential gaps
Business
Needs
EXPLORE
1
4
3
2
Business
Blueprint
Best Practice
Processes

14. 14DO MORE WITH IDENTITY
OMADA ESSENTIAL - FRAMING THE FIRST SOLUTION SCOPE
Essential is the recommended first solution scope to deliver within an IGA project.
Initial solution scope:
Omada Essential
Fig. 7: ‘Essential’ is the recommended first solution scope to deliver in within an IGA project.
Adding additional systems,
automation and processes

15. 15 IdentityPROJECT+
BEST PRACTICE RECOMMENDATIONS FOR
THE EXPLORE PHASE
• Involve all stakeholders (including the project or program sponsor) early in the
project to secure their buy-in
• Build a communication plan to prepare the organization for changes they will
experience when a new IGA system with standard processes is introduced
• Communicate the project progress to relevant stakeholders on a regular basis.
Communicating and aligning expectation within the organization creates
awareness and reduces the resistance to change that exists in all organizations
• Agree on how to measure value and ‘what good looks like’
• Use IdentityPROCESS+ best practice processes as benchmarks. Compare with
those processes and be open to changing existing processes
• Plan to decommission older, not business-critical functionality (legacy) to create
a new lean solution
• Discuss, in detail, the requirements not covered by IdentityPROCESS+ and
separate business-critical use cases from nice-to-have features. Then, do a cost/
benefit evaluation and take into account later maintenance/upgrade costs.
• Establish an overview of all known master data, target systems, processes,
and organizational issues to secure consistent prioritization
• Define the critical interface issues such as whether to use file-based
communication or automated provisioning
• Use stringent and structured reviews of data quality. The improvement of data
quality should be planned for and be an integral part of any IGA project to secure
success. Poor data quality is often neglected or underestimated and has
historically been the single largest cause of project delays and cost overruns.
Communicate the project
progress to relevant
stakeholders on a regular basis.
Communicating and aligning
expectation within the
organization creates awareness
and reduces the resistance to
change that exists in all
organizations
!

16. 16DO MORE WITH IDENTITY
THE BUILD PHASE
During the BUILD phase, the business process requirements are implemented and
configured based on the signed-off Business Blueprint. The first BUILD phase
typically involves establishing an Essential solution. Depending on the rollout
strategy, the BUILD phase can be repeated multiple times in subsequent projects to
achieve multiple valuable releases and solutions deployed into production.
During this phase, the project team configures, tests and documents the solution.
The solution configuration is split into two activity groups: Baseline configuration
(major scope); and Final configuration (remaining scope). Tests are an integrated
part of the BUILD phase. User-centric tests include functional test and end-to-end
integration test.
The go-live must be well planned for an IGA project as IGA solutions interact with
many end-users including employees and managers. Preparation for go-live is also
part of the BUILD phase. This includes completing the cut-over activities such as
load testing, end-user training, system management, and cut-over rehearsal.
During go-live, the transition is made from a project-oriented, pre-production
environment to a live production operation.
Activities in the BUILD phase include (some are only relevant to the
on-premise Essential, some are relevant to subsequent scopes):
• Turn on the light of OIS as-a-service or install the OIS software
• Configure the Essential IGA processes from IdentityPROCESS+
• Configure master data interface and import master data
• Configure provisioning service
• Connect a set of target systems for automated provisioning
• Configure Essential business processes in OIS
• Configure standard reports
• Configure surveys
• Configure SoD rules
• Build custom code and deployment packages
• Perform in-project recertifications as part of data quality management and
improvement
• Perform test data migration from legacy systems
• Prepare documentation
• Test data delivery to other systems
• Define SLA’s for the OPERATE phase
• Train the IGA/IAM team and IT production team to perform solution operations
after go-live
• Prepare for the OPERATE phase by preparing the operating infrastructure incl.
monitoring and back-up routines
• Create a detailed go-live plan
• Perform pre-go-live checks
• Perform the first (partial) rollout
• Support production solution during a short hyper-care period
Output (Initial BUILD Phase):
• Configured Essential scope within OIS software or service
• Master Data/Authoritative Source System connected to OIS software or service
• Live dashboards showing data quality and giving advice to improve quality and
lower risks
• Ready-to-go surveys to perform first recertifications
• Signed-off User Acceptance Test
• Organization is prepared to OPERATE
Output (Following BUILD Phases)
• Enhanced reports and surveys configured
• Automated provisioning to a set of target systems
• Additional critical business applications onboarded and provisioning established
• The organization's stakeholders are trained according to their roles
• Additional IGA processes configured
• Next steps of the overall rollout plan carried out

17. 17 IdentityPROJECT+
Sample IdentityPROJECT+ tools provided to support this phase:
• OIS Configuration Guide following the best practices of IdentityPROCESS+
• Interface contracts templates for implementation of interfaces including SLA’s
• Questionnaires for interfaces
• Questionnaires for account and identity types
• OIS documentation available on the HUB
• Omada Provisioning Service (OPS) readiness questionnaire
BEST PRACTICE RECOMMENDATIONS FOR
THE BUILD PHASE
• Ensure continuous business buy-in for areas such as user experience and IGA
process flow, role concept, SoD policies, automated assignment policies, and
recertification campaign design. This is recommended to be done by demoing
progress iteratively to the stakeholders during workshops
• Use the IdentityPROCESS+ best practices as benchmarks for process design
• Stay as close as possible to the OIS standard features and functionality such as
the account concept and best practice survey flow
• Configure the standard solution to fit your business needs. Avoid custom code
and 3rd-party libraries to the extent possible to enable seamless upgrades to
newer versions
• Be open to postponing certain topics / scope to a following release / project
• Allocate an Omada architect to perform quality checks of the deliverables and to
evaluate the cross-project dependencies on an ongoing basis
• Master data may be enriched in OIS. However, to avoid compliance issues, do
not manipulate authoritative master data already delivered to OIS. Any actions
for improving data quality must reside in the master data source systems
• Stay focused on your iterative rollout strategy as defined during EXPLORE
• Train and educate your internal stakeholders including the solution responsible
and the end-users. Training areas include new processes, operating the solution,
and how to operate in a new and more streamlined governance setup
• Ensure you have a test environment that is as similar as possible to production
Configure the standard solution
to fit your need. Avoid custom
code and 3rd-party libraries to
the extent possible to enable
seamless upgrades
to newer versions
!

18. 18DO MORE WITH IDENTITY
THE OPERATE PHASE
The OPERATE phase covers activities related to the continuous operation of your
OIS solution, whether it is delivered as-a-Service or as software. During this phase,
the solution is operated by the support organization.
During OPERATE end-user support, incident handling, change request
management, and daily monitoring are ongoing following the processes defined in
the BUILD phase. The established support organization utilizes Omada’s support
services per the support agreement.
Activities in this phase include:
• Continuously fine-tune application lifecycle standards, processes, and
procedures
• Run the Incident Process continuously
• Run Change Request Management process and other ITIL like processes
• Plan for continuous upgrades and enhancements
• Provide ongoing support for the end-users
• Monitor and report SLA fulfillment
• Manage releases and upgrades
• Run periodic requirements analysis to proactively be able to react on new
organizational decisions, new legal requirements, or new business requirements
• Add additional (minor) processes or change existing processes
• Add new organizational units, employees, partners, and contractors
• Add new systems and decommission target systems as needed
• Monitor data quality on a continuous basis when new systems are added or new
data is used
• Collect requirements for subsequent projects / EXPLORE phases
• Propose SoW’s and charters for additional rollouts to derive additional value from
your OIS
SUPPORT OFFERING
The organization should evaluate and decide on the required support level.
Omada provides flexible support packages and options in line with the
organization’s needs:
Helpdesk and
documentation
access
Response
times
Incident, issue
and change
request handling
services
Health Check
services
Scheduled
upgrades
Solution
monitoring
services

19. 19 IdentityPROJECT+
INCIDENT FLOW OVERVIEW AND RESPONSIBILITIES
The way incidents and service requests are handled directly impacts how stakeholders experience the IGA solution, and
therefore project success. Below is an example of a three-tier Incident Flow process:
1st
Line
Support
2nd
Line
Support
Omada
3rd
Line Support
Super
Users
OIS Application
Operation
Services
Related
infrastructure
and systems
Logging of incidents
and service requests
into Omada ITSM
Follow your tickets,
responses and
activities
Request for help/
configuration
Remediate
product or
service issues
Fig. 8: An example of an operations process: The Incident Flow process
End Users

20. 20DO MORE WITH IDENTITY
BEST PRACTICE RECOMMENDATIONS FOR
THE OPERATE PHASE
• Agree on desired support services and SLA levels and early on: ‘What does
good look like?’
• Plan for the OPERATE phase already during the EXPLORE phase
• Decide on the preferred operating mode (Service or Software) early on, and
choose your operator
• If you plan to use a third-party operator, it is recommended to involve them early
in the project to secure proper planning of tasks such as monitoring of the
solution and integrating the solution into backup routines
• Decide on who should receive training and plan for operations training and
knowledge transfer early on
• Train your support organization before the initiation of the OPERATE phase by
utilizing the focused learning paths offered by the Omada Academy
• Engage with Omada’s Support organization representative early to ensure a
setup that perfectly fits your organization’s requirements
Agree on SLA’s before going live:
‘What does good look like?’
!

21. 21 IdentityPROJECT+
Accelerators and Other Valuable Tools Included in IdentityPROJECT+
IdentityPROJECT+ includes accelerators such as guides, checklists, standard questionnaires, and deliverable templates. In addition, IdentityPROJECT+ utilizes the
standard OIS documentation and the ‘Tips and Tricks’ available on the Omada HUB. Examples of tools included:
Tool Title Tool Type Purpose/Business Justification
Project Reporting Template Template Transparent reporting of used resources, budget, and status allows efficient project management
Reporting of problems with solution options allows actions to be taken early
Scoping Document Template In a Scoping Excel, the processes, data sources and infrastructure landscapes are defined and checked for quality
and completeness. It gives the gap between standards and special use-cases not covered by a standard
Interface Design Questionnaire Questionnaire Provides an accelerated approach to setting up connectivity to systems
Data Mapping Template Template Helps to define the data mapping from incoming data to the OIS data model
Interface Contract Template Template Formalizes the interfaces by fixing technologies, service levels, and responsibilities
Project Resource Planning
Template
Template Helps project managers plan resources and provide up-to-date overviews to the steering committee
Business Blueprint Template
Document
Template Simplifies and speeds up the creation of a Business Blueprint
System Onboarding Guide Guide Provides guidance for how to onboard new target systems following a standard onboarding process
OPS Readiness Checklist Checklist Provides a structure for validation of OPS readiness before go-live
System Onboarding Guide Guide Makes it easier to onboard target systems
Survey Campaign Guide Guide Makes it easier to design successful survey campaigns
Dependency Matrix Guide Provides an updated overview of dependencies between activities
Functional Design Template Template Lists all important issues which must be decided on when running an IGA initiative
OIS Administration Guide Guide Helps to define a customer-specific administration guide
Technical Design Guide Guide Lists all important issues which must be decided and planned from a technical implementation perspective
Standard Project Plan
Essential Scope
Template Provides a WBS structure of standard deliverables, activity groups, and activities to deliver the ‘Essential’ scope
Use-Case Template Deliverable Template Provides advice on what an IGA use-case must contain
Test-Case Template Deliverable Template Provides advice on what an IGA test-case must contain
Business Case Value
Calculator
Tool Provides a structured approach to calculating the value of your IGA project
Role Mining BI Tool Tool It is possible to enhance the out-of-the-box role features provided by OIS by connecting a standard Power BI Role
Mining tool to OIS. This enables the utilization of the capabilities of Power BI to identify trends related to rules or
exceptions, making it easier to identify and map ‘birthrights’ across organizational units

22. 22DO MORE WITH IDENTITY
IdentityPROJECT+
Project Organization and Roles
The success of a project is dependent on assigning the right people to the right roles. In IGA projects there is a very close interaction between the business,
compliance department, and IT. In general, all stakeholders need to interact more closely than in many other projects.
Implementation Partner Organization
Project
Sponsor
Project
Manager
Solution
Architect
Consultant
(data)
Consultant
(data model
and workflow)
Project Owner
Project
Manager
Technical
Architect
Data supplier
(target
systems)
HR (identity
data and
processes)
• Assurance of value creation for the Organization
• Monitoring of team and project quality of service
• Executive dialogue (Organization and Omada) and
key escalation point-of-contact
• OIS implementation approach, planning, resource
allocation, stakeholders, procedures, deliverables,
scope, progress, risk and economy (estimation /
re-estimation)
• OIS reference architecture
• OIS implementation approach, installation, use
cases, design, change requests (scope),
re-estimation, quality assurance, deployment
• Environments (development, test and production)
• Data quality assessments (authoritative sources
and target systems)
• Loading data from target systems (SQL Server
Integration Services) and mapping data in OIS
• Participating in relevant design areas
• OIS data modelling towards the organization’s
requirements, transforming use cases into solutions
and building specific workflows as required by the
organization
• Participating in relevant design areas (use cases,
solutions)
• Accountable for benefits realization
• Monitoring of team and project quality of service,
executive dialogue (Implementation Partner and
Omada) and key escalation point-of-contact
• Overall project planning and management of the
customer resources, stakeholders and procedures
• Participation in deliverable approval, scope,
progress, risk and economy (estimation /
re-estimation)
• Close cooperation with Omada’s project manager
• Overall planning and management of resources,
stakeholders and procedures
• Participation in deliverable approval, scope,
progress, risk and economy (estimation /
re- estimation)
• Close cooperation with Implementation Partner’s
Project Manager
• Deliver data for quality assessment and facilitating
automatic data extract from target systems in
relation to user accounts, resources / roles and
account-to-resource relationships (assignments)
• Experience with identity lifecycle (joiner, mover,
leaver) processes from an HR perspective
• Knowledge of identity master data (employees,
consultants, business partners, and more)
Fig. 9: An overview of the project roles recommended for IGA projects

23. 23 IdentityPROJECT+
IdentityPROJECT+ Provides Clear Guidance for who is Responsible for each Deliverable
The Organization’s Responsibilities
The Implementation Partner’s
Responsibilities
Project
agreement
Platforms
for software
ready
Access to inte-
grated systems
made available
Kick-off
meeting
HR data
made
available
AD Data
made
available
Solution
tested by the
organization
Acceptance
provided
Platform
prerequisites
submitted
Platform checklist
submitted
Platforms checked
‘Lights on of OIS Service’ or OIS
software Installed
Essential solution
configured and AD
connected
Solution
tested by
implemen-
tation partner
Handover
meeting
Essential
go-live
Solution
documentation
delivered
Fig. 10: A selection of IGA project deliverables and who is responsible

24. 24DO MORE WITH IDENTITY
Keep your organization
continuously informed by
inviting to short sessions
on a regular basis where
all stakeholders can
experience progress
made and the value it
provides for the business
!
Best Practice Recommendations Related to
Project Organizations and Roles
• Ensure the project owner is informed on a regular basis - not only during steering
committee meetings
• Ensure the project owner is included in the communication plan
• Keep your organization continuously informed by inviting to short sessions on a regular
basis where all stakeholders can experience progress made and the value it provides for
the business
• Think ‘broader organization’ which includes stakeholders outside the core project like
the CISO and compliance officer
• Make one overall architect responsible for the solution architecture and architecture
sign-off
• Empower consultants to make decisions through clear delegation of tasks and
responsibilities
• Utilize architects, senior- and junior consultants in an efficient mix. There are many tasks
where a well-balanced mix of seniority levels and experience can provide results very
cost-efficiently

25. 25 IdentityPROJECT+
The IdentityPROJECT+ project plan is recommended to be used actively as a tool throughout the project for planning and following-up on progress.
IdentityPROJECT+ provides template Project Plans with Work Breakdown Structures, Deliverables, Activity Groups, Activities and Milestones, and proposed
allocation of responsibilities to project roles. In addition, the IdentityPROJECT+ Project Plan shows the cross-functional dependencies of the deliverables.
The template for the Essentials Project Plan contains detailed descriptions of Activity Groups with link to Deliverables with described measurable outcomes.
IdentityPROJECT+
Project Plan
W-4 W-3 W-2 W-1 W1 W2 W3 W4 W5 W/6 W/7 W/8 W/9 W10 W11 W12
Establish environments
Collect data
Attestation
Essential go-live
Provide platforms and access rights
Lights-on of OIS Service or install software
Collect identity data from authorative source
Collect access data from Active Directory
Basic configuration (incl. join rules)
Set-up reporting
Quality check (account ownership)
Survey configuration
Configuration of deprovisioning
Quality assurance and acceptance
Promote to production
Training
Go-support
Month -1 Month 1 Month 2 Month 3
Sprints in the Essential agile execution
1
2
3
4
1
2
3
4
0 1 2 3 4 5
Contract Signed
Kick-Off (meeting)
Check Join Rules
Accept
Lights-on or
installation
completed
Data join and
reporting
established
Ready for
survey with
deprovisioning
Go-live
Fig. 11: Sample section of the IdentityPROJECT+ Project Plan template – Gantt View

26. 26DO MORE WITH IDENTITY
Best Practice Recommendations for Using
the IdentityPROJECT+ Project Plan
• Build a project plan that focuses on value-adding deliverables and not only
activities
• Ensure that every deliverable is objectively verifiable and that the business value
is understood by the stakeholders
• Plan for the big picture, but schedule for releases every 2-3 months (avoid big-
bang projects). Articulate and document the business value of each planned
release
• Build a work breakdown structure and allocate the responsibilities for
deliverables, activity groups, and activities
• Use the plan as an active tool for communication and follow-up throughout the
program/project
Ensure that every deliverable is
objectively verifiable and that
the business value is
understood by the
stakeholders
!

27. 27 IdentityPROJECT+
Accelerator
Accelerators provided as part of IdentityPROJECT+ include example documents,
questionnaires, checklists, and other tools that help accelerate the completion of
activities while increasing quality.
IdentityPROCESS+ Framework
The IdentityPROCESS+ best practice framework captures two decades of Omada’s
experience working with leading organizations around the globe. It simplifies IGA
decisions, ensures maximum automation of IGA business processes, and helps
organizations optimize business value and ROI – all based on proven best
practices.
IdentityPROJECT+ Workshops
Scoping and architecture workshops are conducted using IdentityPROCESS+ best
practices as the starting point to align with standards and secure a seamless
upgrade path for future versions. A fit-gap analysis is part of these workshops, and
the organization is challenged on any need to deviate from best practices. Potential
gaps are identified, and solutions are defined.
Omada Essential Solution Scope
Omada Essential is the recommended first solution scope for any IGA initiative,
based on experience from hundreds of projects. Essential can be implemented with
OIS delivered as-a-service or as software.
Essential establishes the foundation for future solutions and creates business value
in itself – delivered in a short period. It is based on a well-defined scope,
including cleaning and mapping data from Active Directory and the organization's
HR system. With the Essential scope in place, the organization establishes an
Essential overview of access granted throughout the organization. The Essential
overview is used in validation workshops with business users to confirm the
Essential scope and define the scope of future phases.
Essential benefits:
• Ensures that the organization’s most urgent risk and compliance issues are dealt
with fast
• Reduces organizational risk by disclosing orphan or unused accounts and
remediates wrongful access by shutting it down – e.g., employees or contractors
that should not have access to privacy data, former employees, expired
contractors, unused service-accounts and more
• Creates the foundation for future solution scopes to be added
• Available data can be analyzed, and the first recertification can be run
Appendix
Definition of Terms
• Identities ownership of user accounts (who)
• Identity Lifecycle including terminated identities (Join-Move-Leave)
• Actual state reporting point-in-time and development over time
• Recertification of user accounts and access rights
• Ensuring off-boarding processes (disabling access and removal of privileges)
• Knowledge and control over privileged access to information resources
• Establishing compliance to regulations and standards such as GDPR and ISO27000
• Implementation of best practices and improving information security maturity
(e.g. Least Privileges)
• Continued and efficient documentation for audits, ad hoc queries and security initiatives
Fig. 12: Starting with the Essential Solution that is delivered by utilizing the
IdentityPROJECT+ Methodology provides clear and fast benefits
Insight
Controls
Risk
Mitigation

28. 28DO MORE WITH IDENTITY
Omada Hub
Omada’s online knowledge hub and Q&A forum available to partner and customer
organizations.
Omada Identity Suite (OIS)
Omada Identity Suite (OIS) is provided as software or as-a-service with full
feature parity. The service is truly scalable, fully supported, runs on Azure, and
fulfills the highest compliance and security standards. It includes a comprehensive
set of Identity Governance and Administration (IGA) capabilities for the entire
identity lifecycle process, access request processes, policy & risk management,
access recertification, and many others.
Omada IGA Academy
The acclaimed IGA training academy established by Omada to spread best
practices and help partners and customers create business value. Omada
Academy combines e-learning with in-person courses to fit the needs of each
participant.
Project Activity
A project activity represents a specific set of tasks to be performed. There can
always be only one person responsible for an activity.
Project Activity Group
A collection of Project Activities.
Project Deliverable
Project deliverables represent objectively measurable outputs from a project
phase. Deliverables can, for example, be a signed project plan, a test successfully
completed and signed off, or a signed and completed Business Blueprint.
Producing and receiving sign-off on all deliverables relating to a project phase also
defines the completion of the project phase.
Project Milestone
A milestone is a significant intermediate goal in an overall project or project phase
and can segment a project plan or phase into smaller intervals. If a milestone is
constrained by a specific date, it is a scheduled milestone. Such time-restrained
milestones allow project managers to monitor progress and ensure that critical
deadlines are met, e.g., delivery or approval dates. A milestone trend analysis
helps project managers forecast how delays in meeting certain deadlines set by
milestones can delay the whole project.
Project Phase
A project phase consists of a number of activity groups. Each project phase
delivers a set of objectively measurable deliverables. Deliverables link to
milestones with set dates. Reaching these milestones means the project
progresses as planned. Project phases within one project can never overlap.
One phase within a project has to be completed before the next can begin.
However, multiple projects can run in parallel under a program, each being in a
different phase. In such cases, cross-coordination across projects is of utmost
importance.

29. 29 IdentityPROJECT+
Project Plan
The project plan contains project phases, activity groups, activities, deliverables
and milestone and clarifies the interrelated dependency of the activity groups and
activities.
Project Program
A program is a set of multiple projects. Each project runs through the three
standard project phases – EXPLORE, BUILD, OPERATE. Projects under a
program do not have to be in the same phases – for instance one project can
be in the EXPLORE phase, while another project may be in the OPERATE phase.
Project Roadmap
The project roadmap represents a high-level overview of a project’s objectives,
deliverables and milestones. Think of it as a bird’s eye view of the entire project.
While a project plan and related project phases track operational details, a project
roadmap gives an overview of the most important objectives and deliverables. In
short, it provides the big picture. Project roadmaps help the project align around
key milestones over a longer period with its stakeholders.
Solution
A solution solves business needs for the organization. A solution is delivered to
the organization to provide current and future value e.g. by automating a selection
of IGA business processes. The Omada Essential solution scope (which can run
either as software or as-a-service) is a good example.
Work Breakdown Structure
A Work Breakdown Structure (WBS) is a collection of activity groups that organizes
the team’s work into manageable sections. It is a hierarchical decomposition of the
total scope of work as defined by those activity groups to be carried out by the
project team to accomplish the related deliverables.
Provide Platforms
• Infrastructure
• Servers for
environments
• Service Accounts
Install OIS or LIghts-
On of OIS Service
• Test environment
• Production environment
Collect Authoritative
Source
• Identities
• Organization
• Managers
Collect from Active
Directory
• Accounts
• Group memberships
• Join rules
Connect to Active
Directory
• Deprovisioning
Set-up Basic Reports
• Orphaned accounts
• Account ownership
• Basic entitlements
Configure Surveys
• System owner
• Manager
• Resource owner
Fig. 13: IdentityPROJECT+ provides detailed descriptions of standard activity packages – WBS view

30. DO MORE WITH
IDENTITY
Omada is a market leading provider of IT security solutions for identity management and access
governance. Omada delivers services within identity and access governance, risk management,
compliance, role-based access management, and process governance. Omada enables organizations
to achieve compliance, reduce risk exposure, and maximize efficiency – providing policies, processes,
and solutions for fulfillment of governance demands. Established in 2000, Omada has operations in
Europe and North America, delivering its solution via a network of skilled partners and system
integrators
www.omada.net | info@omada.net
DO MORE WITH IDENTITY
Contact Omada
Headquartered in Copenhagen, we have a widespread partner network across Europe, North America
and Africa, and sales offices in the following cities:
Omada A/S | Østerbrogade 135 | DK-2100 Copenhagen | Denmark
Omada Solutions Ltd.| 120 Pall Mall | London SW1Y 5EA | United Kingdom
Omada GmbH | Bad Nauheimer Straße 4 | D-64289 Darmstadt | Germany
Omada Solutions Inc. | Lytton Avenue | Palo Alto, CA 94301 | USA
Omada Solutions Inc | 413 Stuart Circle | Richmond, VA 23220 | USA
Omada | Postępu 17A | 02-676 Warszawa | Poland
Copyright © 2019 Omada® A/S. All rights reserved.
Since 2000, Omada has focused on using identity to create business value – measurable value,
from IT and HR to marketing and sales. Identity, managed the Omada way, simultaneously
improves security, efficiency, cost control and regulatory compliance throughout any
organization. And, it can do even more. Identity can accelerate digital transformations,
smooth M&A integration, and enable deeper relationships with suppliers and customers.
Few technologies have the potential to impact so much. Belief in this essential role of identity
unites our organization, fuels our innovation, and strengthens our collaboration with partners.
We have pioneered many of the best practices in use today and are passionate about taking
identity management even further. We are committed to using identity to create business value.
Omada is a ‘Leader’ in the 2019 Gartner Magic Quadrant
for Identity Governance and Administration.