Transcript About This Template

Cisco Unity Design Process—Presales
Determining Customer Requirements
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-1
Cisco Unity Design Process
What is it?
A repeatable design methodology that focuses on developing a
sustainable design. A sustainable design is maintainable and
seeks to minimize the impact of deployment, administration,
and maintenance when deployed (day two).
It is a series of documents and templates to be bundled as deployment
kits for anyone to use. Partners can use it to streamline the design of
any Cisco Unity solution and to identify services opportunities to sell
to customers.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-2
Cisco Unity Design Process Templates
• Internal Customer Requirements Worksheet
• Customer Requirements Verification
• Cisco Unity Preliminary High-Level Design
• Bill of Materials
• Cisco Unity Usage Analysis
• Cisco Unity Physical Site Survey
• Cisco Unity Logical Survey
• Cisco Unity High-Level Design Definition
• Cisco Unity Low-Level Design Definition
• Cisco Unity Implementation Plan
• Cisco Unity Low-Level Installation Guide
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-3
Design Process Project Tracking Worksheet for
CUSTOMERNAME.xls
Item number
Phase/Task
Date Started
Date Completed
Presales Phase
Presales/Requirements Gathering
Presales/Requirements Development
Presales/Preliminary High Level Design
Presales/BOM for HW, SW and Services
Planning phase
Planning/Usage Analysis
Planning/Feature-Functionality Evaluation of Unity
Planning/Lab Trails-Piloting-Proof of Concept
Planning/Site Survey-Physical
Planning/Site Survey-Logical
Design Phase
Design/High-Level Design Summary
Design/Low-Level Design Detail
Implementation Phase
Implementation/ Implementation Plan
Implementation/Installation
Operations Phase
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-4
Internal Customer Requirements Worksheet
• Internal Customer Requirements Worksheet has three
general goals:
– Gather the customer’s high-level requirements
– Define the customer’s ultimate goals
– Obtain a general understanding of the customer’s
infrastructure
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-5
What Is a High-Level Requirement?
High-level requirement: A broad requirement that
gives general guidance
• Examples:
– Eliminate a circuit-switched system
– Install IP telephony and Cisco Unity to gain unified
messaging capabilities
• Internal Customer Requirements Worksheet
• Customer Requirements Verification
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-6
Building Blocks
Cisco Unity features and functionality
• Know the product; install it in a lab or create a demonstration
build for a laptop.
Cisco Unity product documentation
• Cisco Unity system requirements and release notes
• Cisco Unity tools that help you use Cisco Unity features and
functionality—example: the Audio Text Manager
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-7
Customer Requirements Verification
• The Customer Requirements Verification:
– Summarizes the customer's initial technical requirements
– Defines feature mappings between the customer’s current
system and goals to Cisco Unity system features
• Used to state the requirements back to the customer to
qualify expectations and make sure everyone agrees on the
scope of the project
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-8
Cisco Unity Preliminary High-Level Design
• The Cisco Unity preliminary high-level design is developed
from the Internal Customer Requirements Worksheet.
• This is a high-altitude View of what you plan on implementing
for the customer.
• You will use this to define to your customer:
– Your plans on how to integrate with the PBX infrastructure
– Which deployment model you plan to use
– Which, if any, Interop Gateway you will use
– Overview of the Cisco Unity solution
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-9
Bill of Materials
• Through the process of collecting the customer data and filling out
the templates, you develop estimates:
– Necessary hardware
• Which platforms and how many?
– DC/GCs, Cisco Unity servers, mailstores
– System license
• 32 ports or 72 ports?
– User license
• UM or VM?
– Interoperability license
• AMIS, Bridge, or VPIM ?
– Services
– SMARTnet
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-10
Summary
• Unity Design Process Templates are resources to be used during
the design process.
• A high-level requirement is a high-altitude view of the project’s final
goal.
• It is essential to know Cisco Unity’s features and capabilities to
build a workable design.
• The Internal Customer Requirements worksheet, the Customer
Requirements Verification, the Cisco Unity Preliminary High-Level
Design, and the Bill of Materials are the templates to use in the
Presales phase.
• The Customer Requirements Verification Template can be used to
gather customer requirements.
• Cisco Unity servers, user licenses, networking licenses, and
network infrastructure requirements are examples to be considered
in creation of a Bill of Materials.
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-11
© 2006 Cisco Systems, Inc. All rights reserved.
CUDN v1.1—1-12