1. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Developing an Implementation Plan Final Design and Implementation

2. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-2 Implementation Plan Overview Implementation Plan document drawn from Low-Level Design Definition document Step-by-step guide on installation of system including: Preinstallation tasks Installation tasks Cutover tasks Go or no-go criteria Fallback readiness Operations acceptance

3. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-3 Preinstallation Tasks Preinstallation tasks include: Telephony integration, PBX reconfiguration, other resources lined up Preparing administrative consoles Creating accounts for Cisco Unity installation Schema extension Loading Lotus DUCs on Domino servers

4. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-4 Installation Tasks Use the Low-Level Design Definition document for: Physical placement of Cisco Unity servers Installation of software on Cisco Unity, Domino servers Installation of client applications—ViewMail for OutLook, Lotus DUCs Configuration and importing of subscribers

5. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-5 Precutover Tasks Configuration testing Conversation test plan Integration test plan Simulated load testing Go or no-go decision Precutover subscriber enrollment

6. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-6 Fallback Readiness Ability to reinstate legacy voice-mail system Severe issues that cannot be resolved in a timely manner: –Continuous fail-safe conversations –Ports timing out constantly due to connectivity issues to PBX –Hardware failures –Software failures—Cisco Unity services terminating unexpectedly –Infrastructure issues—messaging systems, domain controllers, switches or routers

7. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-7 Operations Acceptance No unexpected errors occur. Cisco Unity answers calls and voice ports remain registered or active. The TUI conversation responds normally even during high- traffic periods.

8. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-8 Summary The Implementation Plan document is derived from the Low-Level Design Definition document. Implementation steps include preinstallation, installation, precutover, and acceptance. Preinstallation steps include setting up administration consoles and creating Cisco Unity system accounts. Installation steps include physical placement of Cisco Unity servers, loading of software on servers and clients, and importing subscribers. Tests should be run before cutover to discover any issues.

9. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-9 Summary (Cont.) Criteria should be set and a plan developed should fallback be needed. Postcutover acceptance is the absence of any major issues.

10. © 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-10