R17 CMS Capacities
R17 CMS Capacities
Capacities
Release 17
July 2014
© 2014 Avaya Inc. All Rights Reserved. Concurrent User License (CU). End User may install and use the Software on
multiple Designated Processors or one or more servers, so long as only the
Notice licensed number of Units are accessing and using the Software at any given
While reasonable efforts have been made to ensure that the information in this time. A “Unit” means the unit on which Avaya, at its sole discretion, bases the
document is complete and accurate at the time of printing, Avaya assumes no pricing of its licenses and can be, without limitation, an agent, port or user, an
liability for any errors. Avaya reserves the right to make changes and e-mail or voice mail account in the name of a person or corporate function
corrections to the information in this document without the obligation to notify (e.g., webmaster or helpdesk), or a directory entry in the administrative
any person or organization of such changes. database utilized by the Software that permits one user to interface with the
Software. Units may be linked to a specific, identified Server.
Documentation disclaimer
Named User License (NU). You may: (i) install and use the Software on a
“Documentation” means information published by Avaya in varying mediums single Designated Processor or Server per authorized Named User (defined
which may include product information, operating instructions and performance below); or (ii) install and use the Software on a Server so long as only
specifications that Avaya generally makes available to users of its products. authorized Named Users access and use the Software. “Named User”, means
Documentation does not include marketing materials. Avaya shall not be a user or device that has been expressly authorized by Avaya to access and
responsible for any modifications, additions, or deletions to the original use the Software. At Avaya’s sole discretion, a “Named User” may be, without
published version of documentation unless such modifications, additions, or limitation, designated by name, corporate function (e.g., webmaster or
deletions were performed by Avaya. End User agrees to indemnify and hold helpdesk), an e-mail or voice mail account in the name of a person or corporate
harmless Avaya, Avaya's agents, servants and employees against all claims, function, or a directory entry in the administrative database utilized by the
lawsuits, demands and judgments arising out of, or in connection with, Software that permits one user to interface with the Software.
subsequent modifications, additions or deletions to this documentation, to the
Shrinkwrap License (SR). You may install and use the Software in
extent made by End User.
accordance with the terms and conditions of the applicable license
Link disclaimer agreements, such as “shrinkwrap” or “clickthrough” license accompanying or
applicable to the Software (“Shrinkwrap License”).
Avaya is not responsible for the contents or reliability of any linked websites
referenced within this site or documentation provided by Avaya. Avaya is not Heritage Nortel Software
responsible for the accuracy of any information, statement or content provided
on these sites and does not necessarily endorse the products, services, or “Heritage Nortel Software” means the software that was acquired by Avaya as
information described or offered within them. Avaya does not guarantee that part of its purchase of the Nortel Enterprise Solutions Business in December
these links will work all the time and has no control over the availability of the 2009. The Heritage Nortel Software currently available for license from Avaya
linked pages. is the software contained within the list of Heritage Nortel Products located at
http://support.avaya.com/LicenseInfo/ under the link “Heritage Nortel
Warranty Products”. For Heritage Nortel Software, Avaya grants Customer a license to
Avaya provides a limited warranty on its hardware and Software (“Product(s)”). use Heritage Nortel Software provided hereunder solely to the extent of the
Refer to your sales agreement to establish the terms of the limited warranty. In authorized activation or authorized usage level, solely for the purpose specified
addition, Avaya’s standard warranty language, as well as information regarding in the Documentation, and solely as embedded in, for execution on, or (in the
support for this Product while under warranty is available to Avaya customers event the applicable Documentation permits installation on non-Avaya
and other parties through the Avaya Support website: equipment) for communication with Avaya equipment. Charges for Heritage
http://www.avaya.com/support Nortel Software may be based on extent of activation or use authorized as
Please note that if you acquired the Product(s) from an authorized Avaya specified in an order or invoice.
reseller outside of the United States and Canada, the warranty is provided to
Copyright
you by said Avaya reseller and not by Avaya. “Software” means computer
programs in object code, provided by Avaya or an Avaya Channel Partner, Except where expressly stated otherwise, no use should be made of materials
whether as stand-alone products or pre-installed on hardware products, and on this site, the Documentation, Software, or hardware provided by Avaya. All
any upgrades, updates, bug fixes, or modified versions thereto. content on this site, the documentation and the Product provided by Avaya
including the selection, arrangement and design of the content is owned either
Licenses by Avaya or its licensors and is protected by copyright and other intellectual
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, property laws including the sui generis rights relating to the protection of
http://support.avaya.com/LicenseInfo/ ARE APPLICABLE TO ANYONE WHO databases. You may not modify, copy, reproduce, republish, upload, post,
DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, transmit or distribute in any way any content, in whole or in part, including any
PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN code and software unless expressly authorized by Avaya. Unauthorized
AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A reproduction, transmission, dissemination, storage, and or use without the
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA express written consent of Avaya can be a criminal, as well as a civil offense
RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, under the applicable law.
AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS
Third-party components
OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE
OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT Certain software programs or portions thereof included in the Software may
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR contain software (including open source software) distributed under third party
SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, agreements (“Third Party Components”), which may contain terms that expand
DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS or limit rights to use certain portions of the Software (“Third Party Terms”).
TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR Information regarding distributed Linux OS source code (for those product that
WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE have distributed Linux OS source code) and identifying the copyright holders of
SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS the Third Party Components and the Third Party Terms that apply is available
“YOU” AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS in the Documentation or on Avaya’s website at:
AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR http://support.avaya.com/ThirdPartyLicense/
THE APPLICABLE AVAYA AFFILIATE ( “AVAYA”). You agree to the Third Party Terms for any such Third Party Components.
Downloading documents
For the most current versions of documentation, see the Avaya Support
website:
http://www.avaya.com/support
This document describes the supported hardware platforms and capacities for the Avaya Call
Management System (CMS) Release 17 (R17), Release 17 R2 (R17 R2), and Release 17 R3
(R17 R3) software that can currently be purchased from Avaya.
This document includes the following topics:
● Using the capacity limits on page 7
● Capacity descriptions on page 7
● CMS R17, R17 R2, and R17 R3 Capacities on page 10
● Optimizing CMS reporting efficiency on page 14
Capacity descriptions
The following topics describe the measurements you must use to determine which CMS
hardware platform is required.
Concurrent supervisors
The concurrent supervisors capacity is the total maximum number of CMS supervisors and
CMS terminal emulator logins that exist during the peak busy hour. The concurrent supervisors
capacity is not the number of authorized logins, but the number of logins actually used.
Note:
Note: This capacity limit is the sum of the login count from each client type, CMS
Supervisor Web client and CMS Supervisor PC Client.
Calculate the number of concurrent supervisors by counting the maximum number of supervisor
logins and terminal emulator logins that exist during the busy hour period. Each login counts as
one. Do not count the number of reports. This calculation must be 1600 or less.
Third-party software
The third-party software capacity is the number of external or third party interface applications.
Some examples of third-party interfaces are Blue Pumpkin, ODBC, wallboards, Geotel,
Operational Analyst, TCS, and IEX.
Calculate the amount of third-party software by counting the number of third party applications
used.
! Important:
Important: The one exception to this rule is Geotel, which counts as two applications.
Do not count each instance of the application. If you use wallboards, count the wallboards as
one application. Do not add up the total number of wallboards.
Agent/skill pairs
The agent/skill pairs capacity is the total number of agent/skill pairs.
Calculate this capacity by multiplying the number of agents by the number of skills each agent
can log in to. The number of agents and the number of skills are based on the switch
administration. For example, if there are 20 agents, and each agent is administered with 5 skills,
you would multiply agents by their skills for a value of 100 agent/skill pairs. You must count the
total number of skills administered for the agent, not the number of skills used by the agent.
Report elements
The report elements capacity is the average number of report elements.
A report element is an entity that is monitored by an average real-time report. Report elements
are not the lines of data rendered on the report but the element that is chosen to run the report
against. Some examples of elements are VDNs, skills, and vectors.
Calculate this capacity by counting each element. You would count one element if a report is run
for one skill. It does not matter if the report has lines of data for each agent in the skill.
New shipments
The Dell R720 introduces new CMS system wide capacities. The new CMS system wide
capacities come with restrictions, so review Maximum values with multiple ACD deployment for
specific restrictions when using the higher system wide capacities.
Note:
Note: All per ACD capacities remain unchanged.
New system wide capacities
The following table represents the maximum values with multiple ACD deployment on a Dell
R720 system supporting 800,000 agent skill pairs:
Maximum values with multiple ACD deployment
Note:
Note: There is no impact on daily, weekly, and monthly limits. When the capacity limit of
agent skill pairs crosses 200,000, there is an impact on the interval data storage.
Upgrades
External Call 200,000 200,000 per 20 200,000 per 20 mins 200,000 per 20 mins
History (ECH) per 20 mins
records mins
1. The total capacity of concurrent CMS Supervisors is the combined capacity of CMS Supervisor PC clients and CMS
Supervisor Web clients.
2. CMS supports a system wide limit of 200,000 agent skill pairs, with a per ACD limit of 100,000 agent skill pairs.
- Carefully examine the number of agents, skills, VDNs, trunks, or other elements in one
report. Limit the number of agents or other elements in a single report as much as
possible.
● Custom report design
- In historical reports, there should be no input for multiple dates when running against
the interval database tables. Existing reports that allow multiple dates should be
modified to gain access to the appropriate daily/weekly/monthly table instead of the
interval table.
- Any historical report that takes longer than a few seconds to complete should be
reviewed for modification to improve performance.
- Any real-time report that takes more than a few milliseconds to refresh should be
reviewed or modified to improve performance.