Export (0) Print
Expand All

Phase One: Collect Data

 

Topic Last Modified: 2007-04-30

The goal of this initial phase is to collect as much informaton as possible about the Lotus Domino infrastructure, business needs, and applications. Then you can use the information to understand the enviroment and to identify areas that need more in-depth analysis. Tasks in this phase include:

  • Document the current Lotus Domino application infrastructure, including number, version, and location of Lotus Domino servers, replication topology, and backup and disaster recovery plans.

  • Identify the applications that are unlikely candidates for migration, such as mail and administration applications.

  • Discover the applications that can easily be migrated using Microsoft Application Transporter 2006 or the Lotus Migration Suite 2007 for Lotus Domino.

  • Group applications that share a common design so that analysis and recommendations can be performed for these applications. Analysis includes the following activities:

    • Identify and label specific customer templates (in Domino).

    • Look for functionality consolidation opportunities by identifying functionality in Domino that could be consolidated into a single Web-based application.

    • Determine what applications have replicas or are replicas. This task will help you to avoid analyzing the same application more then once.

    • List applications that provide the same functionality (such as training applications) across many different groups in the organization. Identify these applications for consolidation in Lotus Domino prior to migration.

  • Identify the applications that require additional analysis. These applications might include applications with low usage, odd usage patterns, extreme size, or applications that contain many forms and views.

  • Identify applications that are not candidates for migration, such as the following applications:

    • Specific to managing or monitoring the Domino environment, including antivirus and spam-related applications.

    • Domino tips and tricks.

    • Domino Forms Library.

    • Domino logs (specific to applications or servers).

    • Any application that has not been used for an extended period of time. Determine how long to wait before an application is defined as unused.

    • Third-party applications that can be replaced by a Microsoft Exchange Server-based version such as antivirus, anti-spam, unified messaging, and fax.

Microsoft Application Analyzer 2006 for Lotus Domino or the Microsoft Transporter Suite for Lotus Domino perform many of these tasks and generate various reports that provide the information necessary to move to the other analysis phases.

When you begin an assessment, try to obtain pertinent documentation (see the following list). Reviewing this documentation allows you to perform some research before you perform onsite interviews or intensive tools-based data collection. Keep in mind, though, that documentation has a tendency of becoming stale or of not bring implemented at all.

Although the following list is not comprehensive, it does point you in the right direction as to the various types of documentation you should be looking for. Few if any organizations will have all these documents available, but all will have some of the following:

  • Security architecture:

    • Application security

    • Development security

    • End user security

    • Regulatory requirements

    • Remote access architecture

  • Communication plans used in previous projects

  • Logistics documentation:

    • Hardware acquisition process

    • Timing and other hardware guidelines

  • Standards guides for the organization

  • Project plans:

    • Previous design projects

    • Previous migration projects

    • Previous deployment projects

  • Risk documents from previous projects

  • System policy documents:

    • Acceptable use documentation

    • Mailbox and other retention rules

  • Operations guides for solutions

  • Project management standards and guides

  • Legal and regulatory guidance documents

  • List of deployed third-party applications

    • Status of applications today (for example, version(s), if deployed)

    • Upgrade and additional plans for any applications already deployed

  • Organizational documentation standards

  • Helpdesk policies and procedures

    • How are new products moved to the Helpdesk?

    • What are the Helpdesk's service level agreements (SLA)?

  • Training process and procedures

    • Training plans

    • Training requirements

  • Development standards:

    • Development process

    • Code libraries

    • Coding requirements

  • WAN capacity and configuration

  • Any architectural documents:

    • Workflow design

    • Mail routing and design

    • Lotus Domino server design and standards

    • Mobility design

    • DNS and other name space design

    • Directory structure: Users and Groups

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft