Cisco Cisco Unified Provisioning Manager 8.5 Libro bianco
White Paper
© 2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 1 of 5
Modeling Provisioning Return on Investment
Overview
Enterprises deploying Cisco
®
Unified Communications at scale frequently want to optimize the ongoing management
costs for moves, adds, changes, and deletions (often referred to as MACD). The scale at which this optimization
becomes a necessity varies, but often enterprises that have deployed 1000 or more phones can achieve significant
benefits by using applications such as Cisco Unified Provisioning Manager to accelerate, simplify, and delegate
repetitive tasks to less-technical staff. The addition of multiple services such as voicemail, unified messaging, and
single number reach, supported by Cisco Unified Communications applications such as Cisco Unity
™
meeting
applications, Cisco Unity Connection, and Cisco Mobility Manager, significantly increases the value of a provisioning
application.
This document describes the business case and associated return-on-investment (ROI) calculator spreadsheet
(EDCS-691144), which enterprises can use to get an idea of potential savings by deploying Cisco Unified
Provisioning Manager.
Approach
The ROI calculator spreadsheet provides a simple way to parameterize a deployment, and get some initial views on
multiyear savings and payback.
The calculator has numerous sections that can—and in most cases should—be tailored to match a specific
deployment. Initial sections allow entering some basic input parameters, such as size of deployment and growth
rates. Latter sections calculate investment required, savings potential, payback, and multiyear cumulative benefits.
Primary Inputs
The Initial Number of Phones is the factor that affects most of the spreadsheet. This factor scales the costing, as
well as the number of changes expected, and hence potential cost savings. Annual Growth represents the increase
in the number of phones deployed year over year. The calculator assumes the same growth rate each year. If your
growth rate is different, you can modify the formulas to specify the specific growth rate for each year.
The number of clusters indicates the general complexity of the deployment. It acts as a scaling factor for
implementation services work, if that is selected as “Yes” in the primary inputs.
Customer Discount is the discount applied against standard Cisco pricing for this particular customer.
Secondary Inputs
You can also change secondary inputs, but defaults are meant to represent typical deployment scenarios.
Service Parameters indicate complexity of the service. Thus enterprises with 24 lines on a phone will have a
potentially different ROI than ones with 2 lines on a phone.
You should set Service Parameters to include voicemail or unified messaging (on Cisco Unity or Cisco Unity
Connection applications), and whether you use Cisco Mobility Manager for single-number-reach activation.
Typical values for error rates and times to provision services before and after deployment of Cisco Unified
Provisioning Manager are included. You should verify these values with specific data and use cases from the
specific enterprise. Specifically, the default values show a 10:1 acceleration when using Cisco Unified Provisioning