:: ::
 
Our Methodology ...
Objectives

Based on our experience, we focus our services on the following principles, as our customers have ranked them the strongest contributors to a successful deployment.
Achieving a successful deployment
Delivering value quickly, on average within 90 days – this highlights the benefits of focusing in well-defined phases in order to show progress and mitigate risk
Working collaboratively with your resources, to transfer knowledge needed to own and operate the system
Focusing on open communications and customer satisfaction, starting on the first day of the project.
Project Phases
The methodology we have successfully used in previous deployments breaks down each project into one or more threads. With the project threads defined, the methodology next suggests a path to take the project from kickoff to production deployment
Project Approach
As appropriate, some customers choose to take different paths to reach the same end goal
Project Timeline
Using a medium complexity production deployment as an example, the following Gantt chart illustrates the main phases for a 12-week project.

Part of the methodology includes several risk mitigation options, which are highly recommended to our customers:
Product Training – Training is provided to ensure that end users can effectively use the products when the transition to operations occurs. Training should occur prior to the implementation phase of the project.
Architecture Review – As an option to customers, a third-party architecture review process is available, which allows the project team onsite to validate and verify the design prior to entering implementation. This allows for early detection of potential issues and a validation of other best practices followed in previous projects. This review process typically occurs towards the end of the design phase.
Production Readiness Assessment – Prior to the final production rollout customers can engage a team of senior architects to conduct a production readiness on their implementation to get final validation of their deployment and correct any detail in order to assure successful production operation.
Staffing
The table below summarizes a typical staffing roster of Otecia International resources.
Role
Allocation
Description
Senior Technical Architect
Full time
This resource will serve as a senior technical advisor to the team and to the Customer, and as a single point of contact for all project-related issues.  The senior technical architect will be responsible for setting the overall technical direction for the project, assisting in the design of the technical architecture, resolving integration challenges, and bringing Otecia International best practices to bear.  This manager will track and escalate all issues to resolution, plan project tasks, and ensure that the project meets budget objectives.
Senior Identity Management Consultant
Full time
This consultant will serve in the role of full time technical architect, initially responsible for designing and implementing the foundation technical architecture, serving as the day-to-day technical interface to the Enterprise Services and Security teams.  As the project progresses, this resource will be become more responsible for designing and implementing application integrations with the architecture.  This consultant will be the lead resource responsible for development of any API integrations, if/where required.
Directory Architect
Directory Architect
This consultant will be responsible for the design and implementation of the directory, including schema, namespace, topology and data synchronization plan.  This consultant will serve as the lead architect responsible for assisting the customer with the implementation of the LDAP directory to support the IDM application.  During design, this architect will primarily interface with the Security groups within the customer to define schema, DIT, etc. and later with the Enterprise Services team when building the LDAP infrastructure.
Copyright 2006-2007 Otecia International, Inc.; All Rights Reserved