© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.11-1 Determining Customer Requirements Cisco Unity Design ProcessPresales.

Slides:



Advertisements
Similar presentations
© Copyright 2006 FPT Software 1 © FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 How to work in Fsoft project Authors: KienNT.
Advertisements

Motorola Confidential Proprietary MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names.
Copyright The Info-Tech Research Group Inc. All Rights Reserved. D1-1 by James M. Dutcher Strategic IT Planning & Governance Creation H I G H.
©2011 Check Point Software Technologies Ltd. [PROTECTED] All rights reserved. 3D Security Analysis Report Tool.
Project Scope Management
© 2003, Cisco Systems, Inc. All rights reserved..
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v Understanding Cisco Unity Bridge and Avaya Interoperability Migrating Voice Mail to Unified.
© 2008 Cisco Systems, Inc. All rights reserved.CIPT1 v6.0—1 Implementing Cisco Unified Communications IP Telephony Part 1.
© Tally Solutions Pvt. Ltd. All Rights Reserved 1 Shoper 9 POS Single Store Implementation October 2009.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Providing Cutover Support and Optimization Final Design and Implementation.
© Tally Solutions Pvt. Ltd. All Rights Reserved 1 Shoper 9 Implementation in Chain Store March 2010.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding Cisco Unity Configurations and Messaging Models Cisco Unity Design Process—Presales.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-1 Designing Cisco Unity Bridge and Avaya Migrating Voice Mail to Unified Messaging and Interoperability.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Understanding the Role of Telephony Components in Cisco Unity Design Cisco Unity Design Process—Presales.
IT Administrator Lifecycle Lifecycle Services Dashboard & CustomerSource Roles Developer Business Analyst Information Tools/Service s Project.
Cisco Confidential 1 © 2012 Cisco and/or its affiliates. All rights reserved. Collaborative Professional Services (CPS) Smart Talk Series 303.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Messaging Product Overview Cisco Unity Design Process—Presales.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Using Active Directory and Exchange 2000 or 2003 in Cisco Unity Design Cisco Unity Design.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Developing an Implementation Plan Final Design and Implementation.
Final Design and Implementation
Adding New Services making a difference! Lars Ahlgren Sales Lead Dynamics Services Microsoft Dynamics.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—4-1 Designing VPIM Solutions Migrating Voice Mail to Unified Messaging and Interoperability.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialUnity Briefing 1 Cisco Unity & Unity Connection Q3/Q4 FY08 Pricing Promotion.
1 © 2002, Cisco Systems, Inc. All rights reserved. The Business Case and ROI Analysis for IP Telephony at Cisco Systems Cisco Account Team Date.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—1-1 Designing with the Directory and Mailstore in Domino Cisco Unity Design Process—Presales.
Unified Communications as a Managed Service DIR Telecom Forum, October 7, 2014 ROY ALBRECHT, Director, Sales and Marketing Globalscope Communications.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Characterizing the Existing Network Designing and Supporting Computer Networks.
WP3 Semivirtual Campus Progress Report Petr Grygarek VSB-CZ.
IT Project Management Cheng Li, Ph.D. August 2003.
1 Session Number Presentation_ID © 2001, Cisco Systems, Inc. All rights reserved. Using the Cisco TAC Website for IP Routing Issues Cisco TAC Web Seminar.
11 SECURITY TEMPLATES AND PLANNING Chapter 7. Chapter 7: SECURITY TEMPLATES AND PLANNING2 OVERVIEW  Understand the uses of security templates  Explain.
1 © 2005 Cisco Systems, Inc. All rights reserved. Session Number 11911_11_2005 Managing Cisco Unified Communications Reducing costs and improving resilience.
OFC 200 Microsoft Solution Accelerator for Intranets Scott Fynn Microsoft Consulting Services National Practices.
Satzinger Chp. 2 Part Part 4 of 4 2 Object-Oriented Analysis and Design with the Unified Process Testing Testing is critical discipline Testing activities.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Identifying Application Impacts on Network Design Designing and Supporting Computer.
Presentation_ID 1 © 2007 Cisco Systems, Inc. All rights reserved.Cisco Confidential Networking Academy Maintenance US/Canada Theater Pilot Overview Nov.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Microsoft ® Exchange Server 2010 with Service Pack 1 Infrastructure Planning and Design Published: December 2010 Updated: July 2011.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco PublicITE I Chapter 6 1 Identifying Application Impacts on Network Design Designing and Supporting.
Monitoring and Evaluation Management of a Training Program.
WebEx Cloud Connected Audio Enterprise
BBSM-LRE-Cable-Aironet Total Implementation Package (TIP) Network Design Samples Solution Deployment Methodologies Building Broadband Solutions Unit Document.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—2-1 Understanding Capacity-Planning Considerations The Design Process—Planning.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
© 2006 Cisco Systems, Inc. All rights reserved CUDN v1.1—1 Cisco Unity Design and Networking.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—1-1 Planning Routing Services Creating an Implementation Plan and Documenting the Implementation.
I Copyright © 2007, Oracle. All rights reserved. Module i: Siebel 8.0 Essentials Training Siebel 8.0 Essentials.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Rob Davidson, Partner Technology Specialist Microsoft Management Servers: Using management to stay secure.
© 2007 – 2010, Cisco Systems, Inc. All rights reserved. Cisco Public Course v6 Chapter # 1 Chapter 2: Troubleshooting Processes for Complex Enterprise.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Preparing the Proposal Designing and Supporting Computer Networks – Chapter 9.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
© 2006 Cisco Systems, Inc. All rights reserved. CUDN v1.1—3-1 Developing a High-Level Design Final Design and Implementation.
ESSRT In-Process Review September 10, Agenda 1.Work Completed Till Date 2.Scope of future activities and deliverables 2.
1 © 2005 Cisco Systems, Inc. All rights reserved. Cisco Unity 4.1 Documentation What you need to know.
1 © 2000, Cisco Systems, Inc. CDN iTrack A Mobile Internet Platform for Defence and Emergency Services Phillip Yialeloglou
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—1-1 Planning Routing Services Lab 1-1 Debrief.
OUTCOMES OBJECTIVES FUNCTIONS ACTIONS TERRITORIES LOCATIONS MARKET SEGMENTS TIME LINESCHALLENGE IMPACT RESOURCESACTIVITIESCHANNELS RELATIONS PARTNERS CUSTOMERS.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
© 2003, Cisco Systems, Inc. All rights reserved. 2-1 Campus Network Design.
RSA Professional Services RSA SecurID Solution Design and Implementation (D&I) Services.
Planning Engagement Kickoff
InGenius Connector Enterprise Microsoft Dynamics CRM
Office 365 FastTrack Planning Engagement Kickoff
Development Projects / Analysis Projects / On-site Service Projects
<Name of Product>Pilot Closeout Meeting <Customer Name>
CORPORATE PROFILE JUNE 2016
The Design Process—Planning
The Design Process—Planning
Presentation transcript:

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v Determining Customer Requirements Cisco Unity Design ProcessPresales

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v Cisco Unity Design Process 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. What is it?

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v 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 v Design Process Project Tracking Worksheet for CUSTOMERNAME.xls Item numberPhase/TaskDate StartedDate 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 v Internal Customer Requirements Worksheet Internal Customer Requirements Worksheet has three general goals: –Gather the customers high-level requirements –Define the customers ultimate goals –Obtain a general understanding of the customers infrastructure

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v 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 v Building Blocks 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 functionalityexample: the Audio Text Manager Cisco Unity features and functionality

© 2006 Cisco Systems, Inc. All rights reserved. CUDN v Customer Requirements Verification The Customer Requirements Verification: –Summarizes the customer's initial technical requirements –Defines feature mappings between the customers 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 v 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 v 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 v 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 projects final goal. It is essential to know Cisco Unitys 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 v