Namespace Migration – Pre-Engagement Checklist

The purpose of this memo is to gather key information use for pricing related to namespace migration. This document is the initial in-take document that serves as a means of clarification and to set client expectations.

BackgroundFor clients with Cognos 8 or 10, moving off of the Series 7 namespace to another target namespace generally involves conversion in three areas: migrating users and groups from one namespace to another, converting security in existing models, and converting security in the Content Store.

The high level work breakdown structure is shown below.

The remainder of this document specifies questions that are relevant for pricing of a namespace migration effort.

Motio Namespace Migration Checklist Page 1 of 11

Environments to be convertedEnvironment type Environment must be convertedDevelopment Yes No

UAT Yes No

Production Yes No

Are there any other environments that need to be converted?

If yes, please specify

Motio Namespace Migration Checklist Page 2 of 11

NamespaceThis section requests information about the Source namespace, Target namespace, and mapping method to be used.

Source Manager Namespace – Access ManagerWhich architectural diagram best characterizes your current environment?

Current ArchitectureType I -- A single Access Manager namespace exists that supports multiple Cognos environments.

Type II -- Each environment has its own Access Manager Namespace.

Type III -- If neither of the above diagrams describes your environment, please attach a separate architecture diagram.

Motio Namespace Migration Checklist Page 3 of 11

Additional QuestionsUsers – How many users exist in the Access Manager namespace?

User Classes – Approximately how many user classes exist in the Access Manager namespace?

OS Signons – Are OS Signons used for single signon into Active Directory?

Yes

User classes in target environment.Have User Classes been created in the target environment?

Yes NoIf no, will FirstQuarter perform this as part of the migration? Yes

Memberships in target environmentHave memberships be created in the target environment?

Yes NoIf no, will FirstQuarter perform this as part of the migration? YES

Motio Namespace Migration Checklist Page 4 of 11

Target NamespacePlease indicate the architecture that will be in place following the migration.

Future ArchitectureType I -- A single Target namespace will exist that supports multiple Cognos environments.

Type II – Multiple target namespaces will exist that supports multiple Cognos environments.

Type III -- If neither of the above diagrams describes your environment, please attach a separate architecture diagram.

Motio Namespace Migration Checklist Page 5 of 11

Namespace Mapping MethodPlease indicate which mapping method you will use following the migration.

Direct Yes NoParallel Yes NoOther Yes No

Mapping Method DescriptionsDirect Mapping – In a direct mapping scenario the following applies:

1. Series 7 user classes are converted into roles in the Cognos namespace2. User memberships from the new, target namespace are mapped directly into the related

Cognos namespace groups.3. This approach provides the BI team with a high degree of control/autonomy that they have

been used to with Series7 Access Manager.

Parallel Mapping – In a parallel mapping scenario the following applies:1. Series 7 user classes are converted into groups in the target namespace2. For each group created in the target namespace, a corresponding group is created in the Cognos

namespace.3. Group-to-group mappings are created.4. User memberships are performed in target namespace.5. This approach typical provides the BI team with less control because the corporate LDAP team

usually controls access and memberships to the target namespace.

Motio Namespace Migration Checklist Page 6 of 11

Other -- If neither of the above diagrams describes your environment, please attach a separate diagram that describes the approach that you will use.

Models

Key Questions Please indicate answer belowTransformer

Do Transformer models exist that have Series7 user class views (Transformer 7)?

Do Transformer models exist that have existing Custom Views with Series 7 security attachments (Transformer 8/10)?

Yes NoIf yes, how many models will be converted?

Yes NoIf yes, how many models will be converted?

Framework Manager

Do Framework Manager models exist that have existing security with Series 7 security attachments?

Yes NoIf yes, how many models will be converted?

PlanningDo Planning models exist that have existing security with Series 7 security attachments?

Yes NoIf yes, how many models will be converted?

Metrics

Do Metrics models exist that have existing security with Series 7 security attachments?

Yes NoIf yes, how many models will be converted?

Motio Namespace Migration Checklist Page 7 of 11

Cognos Connection

Key Questions Please indicate answer belowMachine to be used for migrationWindows XP, 2003, 20084Gb RAM1Gb free Hard Drive Space

Yes NoYes NoYes No

Intranet Access to Cognos Dispatcher (preferably the same Dispatcher listed in Cognos GatewayURI list)

Yes No

Cognos version □ 8.1 □ 8.2 □ 8.3 □ 8.4 □ 10

Cognos Operating System □ Windows □ SUSE Linux □ Red Hat Linux □ Solaris □ HP Unix

Security system(s) □ LDAP □ Active Directory □ NTLM □ Site Minder □ Custom □ Other____________

Bandwidth between the Cognos server and the Namespace Migration workstation

□ 10 Mb□ 100 Mb□ 1 GB □ 54 MB□ 11 MB□ Other____________

Both source and target namespaces configured and tested in Cognos?

□ yes □ no □ don’t know

A user account with System Administrator rights exists in both the source and target namespace?

□ yes □ no □ don’t know

Motio Namespace Migration Checklist Page 8 of 11

The estimated user count:

Motio Namespace Migration Checklist Page 9 of 11

Key Questions Please indicate answer belowUsers have considerable content in their My Folders

□ yes □ no □ don’t know

Users typically create their own schedules □ yes □ no □ don’t know

Users have extra Portal Tabs other than “Public Folder” and “My Folders”

□ yes □ no □ don’t know

Users personal preferences are important □ yes □ no □ don’t know

Security is setup via membership in Cognos groups/roles

□ yes □ no □ don’t know

Security setup via security system’s groups/roles □ yes □ no □ don’t know

There are account-level policies throughout the content store

If yes to above, Is this the norm? Is this the exception?

□ yes □ no □ don’t know

□ yes □ no □ don’t know□ yes □ no □ don’t know

Are there any known performance or stability issues with the content store?

□ yes □ no □ don’t know

The number of environments that will be migrated?

3 -4

Key personnel available for migration (as off-peak hours are best)

□ yes □ no □ don’t know

Key Security/Database/Network resources □ yes

Motio Namespace Migration Checklist Page 10 of 11

available for the duration of the migration process □ no □ don’t know

Key resources been identified to test the results of the migration

□ yes We will have folks identified□ no □ don’t know

Key success criteria been identified □ yes We will have this defined□ no □ don’t know

Dedicated Cognos instance identified for the migration (Sandbox, or Development box)

□ yes □ no □ don’t know

The Dispatcher port is open to the workstation that the migration will be run from

□ yes □ no □ don’t know

The content store database backup is this large (MB): Prod : Dev : Test :

Customer Representative: Name:

Motio Namespace Migration Checklist Page 11 of 11