This phase can also last several weeks. High level architectural decisions are made during this phase: how many Cisco Unity servers? what is the general arrangement? how will it fit into the customer's current environment?
GOAL: Produce a Why Create a High Level Design.
T2.1 Hold a projectWhy Do Planning Kick Off.
T2.2 Create the Why Create a High Level Design -- a summary of everything that you plan to do, including your migration strategy and how you expect the design to look after Cisco Unity is deployed. If you have a phased-migration strategy, show how your voice messaging/unified messaging and electronic messaging infrastructure will look at the end of each phase.
T2.3 CreateWhy Create Site Specific Diagrams.
T2.4 Conduct a Why Do a Gap Analysis between requirements and the customer's existing network hardware and software to determine which core infrastructure and technologies may be necessary to implement Cisco Unity.
T2.5 Perform a Why Do a Security Analysis.
T2.6 Perform a Why Do a Budget Analysis.
T2.7 Perform Why Do Lab Trials as part of your feature evaluation of Cisco Unity. The important part of this effort is to put Cisco Unity in a semiproduction environment and test it under load or in different ways.
GOAL: Begin the subscriber training process.
S2.1 Create your Why Create a Communication Strategy for how you will communicate this change to your subscribers.
S2.2 Review the Why Review Planning Outcomes, and adjust the project timeline accordingly.
S2.3 Perform an Why Do an Operational Readiness Assessment.
S2.4 Compile the data needed for Why Prepare for Design Phase from your preparation and planning activities.