Identity Management Consulting
• Business Requirements & ROI assessment
• Identification & Solution Specification
• Identity Management Business Cases
• Meta Directory Strategies
• eProvisioning Architecture and Design
• Implementation Services
• Directory Solutions, Architecture & Topology, Design and Pilots, deployment & install

Messaging Consulting
• Messaging Integration
• Miltary Messaging Design & Architectures

Training
• Identity Management & Provisioning Strategies
• Directory Scheme Design & Directory Architecutres
• Tailored Security & Identity management courses to specific requirements
• Individual courses with overseas partners who are specialists in their fields

At eB2Bcom Consultancy group we are always happy to negotiate commercial terms and structure on a per-customer or per-project basis in the interests of finding the most appropriate pricing model for both parties. In practice however, many of our projects are performed on either a time and materials basis, or fixed-price, fixed-timescale basis.

For time and materials contracts, or for deployment of individual contractors, eB2Bcom simply charge per man-day for time spent working on the project. An estimate of the total cost can be given in advance, though this may change if the requirements change, and is subject to a certain margin of error - predicting the size of software developments is unfortunately not an exact science! Daily rates vary depending on seniority of staff required and the size of the development (we offer a discount for larger projects). Typical figures are available on request.

For fixed-price, fixed-timescale contracts, eB2Bcom take on the development risk associated with the project and quote a price and delivery date to which we commit in advance. Such contracts are practical only where there is a well-defined specification of the work to be performed. A common way to proceed therefore is through a combination of time and materials work to produce a detailed specification, followed by a corresponding fixed-price quote for the development.

Further Information
If you want to become a eB2Bcom reseller, an eB2Bcom agent, or an eB2Bcom systems integration partner then please request our Channel Partner Requestion form

SAP Netweaver Identity Manager Consultancy

Identity Management has been a core business of eB2Bcom’s since the inception of the company, and we are acknowledged in the Asia Pacific region as a leading independent specialist in this field. We have an in-depth understanding that managing a person’s identity, and their access to company resources, is not a singular activity, and that to deploy the facilities for maintaining a person’s complete set of identity information, and associate access control, across multiple business contexts, needs specialized skills and expertise. eB2Bcom has this expertise.

Successful identity and access management sees the confluence of technologies such as directories, provisioning systems, single-sign-on system and administration systems, and the coordination of business process that collect, publish and archive identity information.
Identity management and access control requires a program that follows a defined path deploying the multiple facilities that in total, unifies a person’s disparate data so as to increase accuracy, reduce administration and improve consistency across the enterprise.

As a SAP Netweaver Identity Management (NIC) Partner, eB2Bcom has a 7 step process for undertaking IAM projects as follows:

Our standard approach, tailored to the particular customer requirements are:
1. Project Preparation, Sponsorship and Commitment
2. Discovery and Assessment and Initial Scope
      a. Environmental Scan
      b. Key Person Interviews
      c. Report & Presentation
3. Design
4. Planning and Resources.
5. Delivery and Implementation
6. Production System Handover and Acceptance
7. 90 day Support and Warranty

The SAP NIC Discovery Stage is a three-step process that identifies the scope of the NIC implementation requirements. The activity documents the current identity repository infrastructure, the current provisioning processes and the synchronisation between directory instances. The output is a report that clearly describes the current identity management services, provisioning processes and synchronisation services, and provides recommendations for the implementation of NIMIC to provide an enterprise-wide Identity Management system that reduces costs, improves data accuracy and raise efficiencies and productivity across the user community.

The three steps are:

Environmental Scan
The initial activity is an environment scan of the main identity management repositories used in the organisation. This will be based on direction from IT management and a review of pertinent documentation provided to the Consultant.
The findings are documented in a high-level inventory of the identity management environment within the customer’s organisation.

Key Person interviews and workshop
Key persons will be interviewed to understand their use of identity information and the current processes used to provision identity stores and resolve inconsistencies. The main identity stores in the company and their schemas are identified. The attributes that comprise the identity stores or directories and ownership of the main attributes will be identified and documented.
Representatives from HR will assist in the identification of the major provisioning processes for staff and contractors within the company.
The “to be” scenario will be developed via workshops with key personnel in the company. Workshops with at least two groups will be conducted:
• user groups with the organisation who can advise on enterprise wide identity management requirements. Areas covered will include user provisioning and de-provisioning processes, identity data management, access management and auditing.
• representatives from the Information services function who will consolidate the findings of the previous workshop(s) into policy and procedures for the company. A process mapping exercise is undertaken to map the identity provisioning process clearly indicating the interaction between applications that populate the identity store records.
The output of this step is a high-level design of the identity data model. It identifies the location of the main identity data repositories and the synchronisation required between them as well as clearly indicating the main provisioning and de-provisioning processes.
A standard mapping methodology such as IDEF0 or BPMn is employed to describe the defined processes.

Report and presentation
The output is a project report that documents the inventory defined by the Environmental Scan, the data repositories and synchronisation methodology identified in the key person interviews and the “to be” processes documented as part of the workshops.
The report also addresses the recommended policy for such issues as authoritative source for names and addresses, evidence of identify requirements for the SAP HRIS module, username nomenclature, provisioning procedures and synchronisation of identity repositories. Implementation project activities and recommended tools to be used for the identity management task are identified as well as any gaps in capability.

Discovery Outcomes
At the end of the Discovery Stage the following will be known:
• the schemas of the main identity management repositories (HRIS, authentication directory, email name & address book, white-pages service etc.) identifying redundant data and recommending authoritative sources for the main identity attributes
• the processes and rules governing the synchronisation of the main identity stores including the periodicity and direction of both automated and manual updates
• process maps for the current provisioning processes, showing the interaction between the various groups that participate in staff engagement and staff exiting
• the options available for process improvement, including recommendations for policy administration and directory management processes.
• design and architecture issues
• the recommended approach to the implementation of NIMIC.

Architecture Issues
We adhere to SAP’s requirements and guidelines for design and deployment of NIC systems. Key elements of this are:
• Defining the Role Model
• Workflow processes – identifying & defining
• Portal (i.e. User Interface) – Self Service Requirements. The NIC user interface integrates into the NetWeaver portal. It provides things such as user self service, and needs to be investigated and scoped out for each deployment.
• Password Management, such as where the passwords come from; are default password values going to be used; how can a user change their password; how can a user reset their own password. For example: a user that forgets his/her password cannot log into the Portal. However, the only way for a user to reset their password is to connect to the portal. Is this an acceptable strategy, or does another need to be employed?