DEFINITY® ECS Release 7 Basic Call Management System (BCMS) Operations PDF Definity 8 2 BCMS

Definity Enterprise R 8-2 BCMS Operations Definity Enterprise R 8-2 BCMS Operations

User Manual: PDF T E X T F I L E S

Open the PDF directly: View PDF PDF.
Page Count: 190 [warning: Documents this large are best viewed by clicking the View PDF Link!]

555-230-706
Comcode 108485087
Issue 2
June 1999
DEFINITY®
Enterprise Communications Server
Release 7
Basic Call Management System (BCMS)
Operations
Copyright 1999, Lucent Technologies
All Rights Reserved
Printed in U.S.A.
Notice
Every effort was made to ensure that the information in this book was
complete and accurate at the time of printing. However, information is
subject to change.
Your Responsibility for Your System’s Security
Toll fraud is the unauthorized use of your telecommunications system
by an unauthorized party, for example, persons other than your com-
pany’s employees, agents, subcontractors, or persons working on your
company’s behalf. Note that there may be a risk of toll fraud associated
with your telecommunications system and, if toll fraud occurs, it can
result in substantial additional charges for your telecommunications
services.
You and your system manager are responsible for the security of your
system, such as programming and configuring your equipment to pre-
vent unauthorized use. The system manager is also responsible for
reading all installation, instruction, and system administration docu-
ments provided with this product in order to fully understand the fea-
tures that can introduce risk of toll fraud and the steps that can be taken
to reduce that risk. Lucent Technologies does not warrant that this
product is immune from or will prevent unauthorized use of com-
mon-carrier telecommunication services or facilities accessed through
or connected to it. Lucent Technologies will not be responsible for any
charges that result from such unauthorized use.
Lucent Technologies Fraud Intervention
If you suspect that you are being victimized by toll fraud and you need
technical support or assistance, call Technical Service Center Toll
Fraud Intervention Hotline at 1 800 643-2353.
Federal Communications Commission Statement
Part 15: Class A Statement. This equipment has been tested and
found to comply with the limits for a Class A digital device, pursuant
to Part 15 of the FCC Rules. These limits are designed to provide rea-
sonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates,
uses, and can radiate radio-frequency energy and, if not installed and
used in accordance with the instructions, may cause harmful interfer-
ence to radio communications. Operation of this equipment in a resi-
dential area is likely to cause harmful interference, in which case the
user will be required to correct the interference at his own expense.
Part 68: Network Registration Number. This equipment is registered
with the FCC in accordance with Part 68 of the FCC Rules. It is identi-
fied by FCC registration number xxx.
Canadian Department of Communications (DOC)
Interference Information
This digital apparatus does not exceed the Class A limits for radio
noise emissions set out in the radio interference regulations of the
Canadian Department of Communications.
Le Présent Appareil Nomérique n’émet pas de bruits radioélectriques
dépassant les limites applicables aux appareils numériques de la class
A préscrites dans le reglement sur le brouillage radioélectrique édicté
par le ministére des Communications du Canada.
Trademarks
CentreVu, DEFINITY, and GuestWorks are registered trademarks of
Lucent Technologies.
Prologix is a trademark of Lucent Technologies.
Ordering Information
Call: Lucent Technologies Publications Center
Voice 1-800-457-1235 International Voice 317-361-5353
Fax 1-800-457-1764 International Fax 317-361-5355
Write: Lucent Technologies Publications Center
P.O. Box 4100
Crawfordsville, IN 47933
Order: Document No. 555-230-706
Comcode 108485087
Issue 2, June 1999
For additional documents, refer to Appendix B, ‘‘References.’’
You can be placed on a standing order list for this and other documents
you may need. Standing order will enable you to automatically receive
updated versions of individual documents or document sets, billed to
account information that you provide. For more information on stand-
ing orders, or to be put on a list to receive future issues of this docu-
ment, contact the Lucent Technologies Publications Center.
Product Support
To receive support on your product, call 1-800-242-2121. Outside of
the continental United States, contact your local Lucent Technologies
authorized representative.
European Union Declaration of Conformity
The “CE” mark affixed to the equipment described in this book indi-
cates that the equipment conforms to the following European Union
(EU) Directives:
• Electromagnetic Compatibility (89/336/EEC)
• Low Voltage (73/23/EEC)
• Telecommunications Terminal Equipment (TTE) i-CTR3
BRI and i-CTR4 PRI
For more information on standards compliance, contact your local dis-
tributor.
Comments
To comment on this document, return the comment form located at the
back of this book.
Lucent Technologies Web Page
The World Wide Web home page for Lucent Technologies is
http://www.lucent.com
Acknowledgment
This document was prepared jointly by the Customer Training and
Information Products Organization and the Information Development
Organization for Global Learning Solutions
Lucent Technologies Bell Laboratories,
Denver, CO 80234-2703.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706
Issue 2
June 1999
Contents
iii
Contents
Contents iii
About this Book ix
■Overview ix
■Reasons for reissue ix
Offer Category A Versus Offer Category B ix
■Organization x
■Conventions used in this document x
■Where to find related documents xi
■How to order related documents xi
■How to comment on this document xi
1 BCMS Description 1-1
■Overview 1-1
■BCMS Reports 1-2
■Printing and Storing Reports 1-3
■Acceptable Service Level 1-4
Percent within Service Level 1-4
Acceptable Service Level Administration 1-5
■System Capacities1-6
■Interactions 1-7
Offer Category A Versus Offer Category B 1-7
Interactions With External CentreVu CMS 1-8
Interactions with VuStats 1-8
2 System Access 2-1
■Logging In and Logging Off 2-1
BCMS Login 2-2
Logging In 2-2
Logging In from a Local Terminal 2-2
Logging In from a Remote Terminal 2-3
Logging Off 2-4
■How to Change the BCMS Password 2-5
3 Generating BCMS Reports 3-1
■Overview 3-1
■Displaying and Printing Real-Time Reports 3-1
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706
Issue 2
June 1999
Contents
iv
Displaying Real-Time Reports 3-2
Printing Real-Time Reports 3-2
■Displaying, Printing, and Scheduling Historical Reports 3-3
Displaying Historical Reports 3-4
Printing Historical Reports 3-8
Scheduling Historical Reports 3-11
4 BCMS Report Reference 4-1
■Overview 4-1
■Real-Time Reports 4-3
BCMS Split Status Report 4-3
Command 4-3
Description 4-3
Sample Report 4-4
Header Definition 4-5
BCMS System Status Report 4-8
Command 4-8
Description 4-8
Sample Report 4-9
Header Definitions 4-9
BCMS VDN Status Report 4-12
Command 4-12
Description 4-12
Sample Report 4-12
Header Definition 4-13
■Historical Reports 4-16
BCMS Agent Report 4-17
Command 4-17
Description 4-17
Sample Reports 4-18
Header Definitions 4-19
BCMS Agent Summary Report 4-22
Command 4-22
Description 4-22
Sample Reports 4-22
Header Definitions 4-23
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706
Issue 2
June 1999
Contents
v
BCMS Split Report 4-27
Command 4-27
Description 4-27
Sample Reports 4-28
Header Definitions 4-29
BCMS Split Summary Report 4-35
Command 4-35
Description 4-35
Sample Reports 4-36
Header Definitions 4-37
BCMS Trunk Group Report 4-42
Command 4-42
Description 4-42
Sample Reports 4-43
Header Definitions 4-44
BCMS Trunk Group Summary Report 4-47
Command 4-47
Description 4-47
Sample Reports 4-48
Header Definitions 4-49
BCMS VDN Report 4-52
Command 4-52
Description 4-52
Sample Reports 4-53
Header Definition 4-54
BCMS VDN Summary Report 4-58
Command 4-58
Description 4-58
Sample Reports 4-58
Header Definitions 4-59
5 System Printer and Report Scheduler 5-1
■Overview 5-1
■System Printer 5-1
System Printer Administration 5-2
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706
Issue 2
June 1999
Contents
vi
System Printer Data Link Operation
and Maintenance 5-3
■Report Scheduler 5-3
Print Intervals 5-4
Adding a Report to the Report Scheduler 5-4
Summary of the Steps for Printing Reports
on the System Printer 5-6
Listing Scheduled Reports 5-7
Change Command 5-9
Remove Command 5-10
6 Use of BCMS Reports for ACD Planning 6-1
■Planning/Engineering Objectives 6-1
BCMS System Status Report 6-2
BCMS Split Status Report 6-3
BCMS VDN Status Report 6-3
BCMS Trunk Group Report 6-4
BCMS Agent Report 6-4
BCMS Split or Skill Report 6-5
BCMS VDN Report 6-5
■Engineering ACD Applications with Data Obtained
from the BCMS Reports 6-5
Agent Engineering/Optimizing Guidelines 6-6
Trunk Engineering Guidelines 6-34
A BCMS/CentreVu CMS Report
Heading Comparison A-1
■Summary of Differences A-1
B References B-1
■Basic DEFINITY ECS documents B-1
Administration B-1
Installation and maintenance B-3
Call center documents B-5
DEFINITY B-5
CentreVu CMS B-6
Application-specific documents B-7
ASAI B-7
ACD B-8
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706
Issue 2
June 1999
Contents
vii
Console operations B-8
Hospitality B-9
Non-U.S. audiences B-9
GL Glossary and Abbreviations GL-1
IN Index IN-1
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706
Issue 2
June 1999
Contents
viii
About this Book
ixOverview
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
About this Book
Overview
This document provides a comprehensive description of the Basic Call
Management System (BCMS) feature, which is available with the DEFINITY®
Enterprise Communications Server (Offer Category A). This document also
describes the Report Scheduler feature, which is often used with BCMS.
Although intended primarily for the BCMS administrator, this document may prove
useful to the system administrator, the Automatic Call Distribution (ACD) split
supervisor, the ACD administrator, and ACD agents.
Reasons for reissue
This document is being reissued to define BCMS attributes that are not used with
the offer category B products, DEFINITY Business Communications System
(BCS) and GuestWorks®.
Offer Category A Versus Offer Category B
Offer Category A products (DEFINITY ECS and Prologix™) supports more
features and feature capacities than the Offer Category B products (DEFINITY
BCS and GuestWorks). In relation to the BCMS feature, the following features are
not supported with Offer Category B:
■Expert Agent Selection (EAS) and skills
■
CentreVu
® Call Management System (CMS)
■VuStats.
When using this BCMS Operations document with an Offer Category B product,
you should ignore references to these features.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
About this Book
xOrganization
Organization
This guide is divided into the following chapters and appendices:
■Chapter , "About this Book", is an introduction to this document.
■Chapter 1, "BCMS Description", provides a brief overview of the BCMS
feature and lists the BCMS reports.
■Chapter 2, "System Access" ,provides procedures on how to log in and
log off BCMS. This chapter also provides the procedures for changing the
BCMS password.
■Chapter 3, "Generating BCMS Reports", describes the procedures for
displaying, printing, and scheduling BCMS reports.
■Chapter 4, "BCMS Report Reference", gives a detailed description of
each BCMS report.
■Chapter 5, "System Printer and Report Scheduler", describes the
optional Report Scheduler feature. This chapter also includes a description
of the report scheduler commands and a display of the reports.
■Chapter 6, "Use of BCMS Reports for ACD Planning", describes
desirable objectives and how the BCMS reports can be used to plan,
engineer, and optimize ACD splits and trunk groups.
■Appendix A, ‘‘BCMS/CentreVu CMS Report Heading Comparison’’,
compares reports and report headings between BCMS and CentreVu Call
Management System (CMS).
■Appendix B, ‘‘References’’, lists other documents that may be used for
reference.
■‘‘Glossary and Abbreviations’’, contains a list of frequently used terms
and their definitions as well as a list of abbreviations and acronyms.
■‘‘Index’’, contains a cross-referenced index.
Conventions used in this document
This document uses the following conventions:
■The names of commands are shown in the following typeface:
change system-parameters feature
■Information you type is shown in the following typeface: EIA
■Information displayed on the screen is shown in the following typeface:
login:
■Keyboard keys are shown as follows: RETURN
■Function keys are shown as follows: CANCEL
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
About this Book
xiWhere to find related documents
Where to find related documents
See Appendix B, ‘‘References’’, for a detailed list of documents related to
DEFINITY ECS. Use these documents to help administer, maintain, and operate
the system.
With each system that is shipped from the factory, you will receive a compact disc
(CD-ROM) that contains most of the supporting documents listed in Appendix B,
‘‘References’’. These documents can be viewed and printed from a personal
computer. The order number for the CD-ROM is 555-230-833.
How to order related documents
To obtain support documentation, contact:
BCS Publications Center
PO Box 4100
Crawfordsville, Indiana 47933-3126
U. S. A.
In North America: Outside of North America:
1-800-457-1235 or 1-317-322-6791 +1-317-361-5353
FAX 1-800-457-1764 or 1-317-322-6849 FAX +1-317-364-5355
How to comment on this document
Lucent Technologies welcomes your feedback. Please fill out the reader comment
form and return it. Your comments are of great value and help improve our
documentation.
If the reader comment form is missing, FAX your comments to +1-303-538-1741,
and mention this document’s name and number,
DEFINITY ECS R7 BCMS
Operations
, (555-230-706, Issue 2).
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
About this Book
xiiHow to comment on this document
BCMS Description
1-1Overview
1
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
1
BCMS Description
Overview
BCMS helps you monitor the operations of your ACD application. BCMS collects
data regarding the calls on the switch and organizes the data into reports that help
you manage ACD facilities and personnel. The BCMS reports allow you to
manage the hourly and/or daily operations of the ACD by:
■Monitoring trunk group usage
■Monitoring the calling volume for each split
■Monitoring VDNs
■Monitoring the work load of each agent
■Comparing agents’ performances.
These reports can be displayed on a video display terminal in real time, printed
immediately, scheduled to print at a later time, or scheduled to print periodically at
times you specify.
NOTE:
All references to splits in this book also apply to skills as used with the
Expert Agent Selection (EAS) feature. However, Offer Category B products
DEFINITY BCS and GuestWorks do not support the EAS feature. Therefore,
if you are using the BCMS feature with DEFINITY BCS or GuestWorks, only
use the term “splits” to define agent groups. See ‘‘Interactions’’ on Page 1-7
for more information.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Description
1-2BCMS Reports
1
BCMS Reports
The BCMS feature provides the following reports:
1. Real-time reports that present data on:
■All splits, on a system basis, that are administered for internal
measurements or for both internal and external adjunct
measurement
NOTE:
DEFINITY BCS and GuestWorks does not support an external
adjunct (for example,
CentreVu
®
Call Managmenet System).
■Individual splits and the agents staffing them that have been
administered for internal or both measurements
■VDNs that are administered for internal measurement or for both
internal and external measurement.
2. Historical reports that present historical information and can be printed
immediately or scheduled for subsequent printing. These reports present
data on:
■Individual agents or a group of agents, based on the time of day
■Individual agents or a group of agents, based on the day of the week
■Individual splits or a group of splits, based on the time of day
■Individual splits or a group of splits, based on the day of the week
■Individual trunk groups or a group of trunk groups, based on the time
of day
■Individual trunk groups or a group of trunk groups, based on the day
of the week
■Individual Vector Directory Numbers (VDNs) based on the time of
day
■Individual VDNs based on the day of the week.
NOTE:
Agents can be measured by their physical extension (that is, the phone
extension they use), or they can be measured by their Login IDs when either
EAS or BCMS/VuStats Login IDs is optioned (EAS, VuStats, and Login IDs
are not supported with DEFINITY BCS and GuestWorks).
Chapter 4, ‘‘BCMS Report Reference’’ describes each BCMS report in detail while
Chapter 6, ‘‘Use of BCMS Reports for ACD Planning’’ describes how to plan and
maintain an ACD based on the information provided by these reports.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Description
1-3Printing and Storing Reports
1
Printing and Storing Reports
The BCMS reports may be displayed on the Management Terminal or printed on
its associated printer. The reports also can be scheduled to print at a later time
with the Report Scheduler.
As an option, a personal computer (PC) or host computer may be used to store
the reports and provide additional data manipulation capabilities.
NOTE:
The BCMS software resides completely on the switch and does not include
any special software or unique communications protocol for the PC/host
computer application. Although Lucent Technologies does propose the use
of a PC to collect, store, and print the reports, Lucent Technologies does not
recommend an applications software package for the PC. Since Lucent
Technologies does not install, administer, or control the PC application,
Lucent Technologies does not guarantee correct operation of this
arrangement. Customers using a PC to collect report data will need the
following report output information for each report:
1. Begin with one-half page of line feeds.
2. Print a four-line banner containing the following information:
■Print job ID
■Command
■Time of day
■User.
3. Provide a form feed.
4. Begin report data using 80 characters per line. Use spaces where there are
no data, and a newline character at the end of each line.
5. Provide a form feed after each page of data. (The page length is defined in
system parameters.)
6. Provide a form feed when the report is finished printing.
BCMS data is stored in volatile switch memory; it cannot be saved to or retrieved
from tape. The switch preserves historical data if a Reset System 1, Reset
System 2, or Reset System Interchange (in a duplicated system) occurs.
Real-time data is preserved if a Reset System 1 or Reset System Interchange
occurs.
The switch loses all data (historical and real-time) during software upgrades.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Description
1-4Acceptable Service Level
1
Acceptable Service Level
Before using BCMS, you should understand the concept of Acceptable Service
Level and then set the acceptable service level field on various forms.
NOTE:
Acceptable Service Level is not supported on the DEFINITY BCS and
GuestWorks offers.
Acceptable Service Level is the desired time for an agent to answer a call for a
given VDN or hunt group. Timing for a call begins when the call encounters a VDN
or enters a hunt group queue. If the number of seconds to answer the call is equal
to or less than the administered acceptable service level for the VDN or hunt
group, the call is recorded as acceptable.
Percent within Service Level
A service level can be administered for each hunt group or VDN, if the
BCMS/VuStats Service Level? customer option has been set to
y
and if the hunt
group or VDN is measured by BCMS.
To calculate the percentage of calls within the acceptable service level, BCMS
divides the number of acceptable calls by the calls offered.
For hunt groups, BCMS calculates the Percent Within Service Level as follows:
where
accepted — Is the number of calls answered for which the queue time was less
than or equal to the administered service level for the split.
dequeued — Is the number of calls that encountered the split’s queue, but were
NOT answered, abandoned, or outflowed. This occurs with multiple split queuing.
For VDNs, BCMS calculates the Percent Within Service Level as follows:
where
accepted — Is the number of answered calls (
num ans
) for which the time to
answer was less than or equal to the administered service level for the VDN.
num
ans
here refers to the data item on the form of the same name.
% IN SERV LEVL accepted * 100
ACDcalls + abandons + outflows + dequeued
------------------------------------------------------------------------------------------------------------------------=
% IN SERV LEVL accepted * 100
calls offered
----------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Description
1-5Acceptable Service Level
1
calls offered — Is the total number of completed calls that accessed the VDN
during the current interval.
Acceptable Service Level Administration
The
Acceptable Service Level
is administered on the System-Parameters
Customer-Options, VDN, and Hunt Group forms. On the System-Parameters
Customer-Options form (only changeable by a Lucent Technologies technician),
verify that the field BCMS/VuStats Service Level? is set to y.
On the Hunt Group Form, set the Acceptable Service Level field to a
number between 0 and 9999 seconds. Set the Measured field to either internal
or both.
On the Vector Directory Number form, set the Acceptable Service Level field to a
number between 0 and 9999 seconds. Set the Measured field to either internal
or both.
NOTE:
The column % IN SERV LEVL on a report will be blank if:
■The BCMS/VuStats Service Level? field on the Customer Options form is
set to n.
■No service level is defined for the split or VDN (it cannot be set if BCMS
Service Level is set to n).
■No call ended in the interval.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Description
1-6System Capacities
1
System Capacities
The following tables illustrates the feature capacities for BCMS and ACD based
on the different switch types and different offer categories. If the capacity differs
between Category A and B, the values in the table are shown as A/B. For
example, the BCMS capacity for Measured splits on an R7csi Category A system
is 99, but the capacity is only 5 for a Category B system.
Maintenance commands and BCMS monitoring sessions compete for the same
access resources: in fact, DEFINITY counts the monitoring session as a
maintenance command. So, for example, you cannot execute a maintenance
command and run a monitoring session simultaneously on a G3si. (The limit for
active maintenance commands is higher on the G3r because this model reserves
two command slots for the Initialization and Administraiton System [INADS] and
System Access Terminal [SAT] logins.)
Table 1-1. BCMS Feature Capacities
Item
DEFINITY
ECS
R6vs/csi/si
DEFINITY
ECS
R6r
DEFINITY
ECS
R7csi/si
DEFINITY
ECS
R7r
(BCS/GuestWorks
Issue 4)
(BCS/GuestWorks
Issue 5)
Maximum active maintenance
commands for the system 151 5
Maximum agents displayed by
monitor BCMS split command1
1. The Monitor Split command only displays status for the first 100 agents logged into the split
regardless of how many additional agents log into the split.
100 100 100 100
Maximum BCMS terminals 3 4 3 4
Maximum simultaneous BCMS
terminals in monitor mode 131 3
Measured agents or login IDs 400/20 2000/20 400/25 2000/25
Measured agents per split 200/20 999/20 200/25 999/25
Measured splits 99/5 600/5 99/5 600/5
Measured trunk groups 32 32 32 32
Measured VDNs 99/4 512/8 99/10 512/20
Reporting periods
Intervals 25 25 25 25
Days 7 7 7 7
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Description
1-7Interactions
1
Table 1-2. ACD Feature Capacities
Interactions
Offer Category A Versus Offer Category B
Offer Category A products (DEFINITY ECS and Prologix™) supports more
features and feature capacities than the Offer Category B products (DEFINITY
BCS and GuestWorks). In relation to the BCMS feature, the following features are
not supported with Offer Category B:
■Expert Agent Selection (EAS) and skills
■CentreVu® Call Management System (CMS)
■VuStats.
When using this BCMS Operations document with an Offer Category B product,
you should ignore references to these features.
Item
R6vs/csi/si R6r R7csi/si R7r
BCS/GuestWorks Issue 4 BCS/GuestWorks Issue 5
Logged-in ACD agents 150 150 150 150
Logged-in splits per agent 4 4 4 4
Announcements per split 2 2 2 2
Announcements per system 128 256 128 256
Queue slots per group 200 999 200 999
Queue slots per system 1500 15000 1500 15000
Splits 99 600 99 600
ACD members per split 200 999 200 999
Split members per system 150 150 150 150
Measured agents 20 20 25 25
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Description
1-8Interactions
1
Interactions With External CentreVu CMS
From the administration perspective, the ACD parameters associated with trunk
groups, hunt groups, and VDNs are any of the following:
■Not measured
■Internally measured by BCMS
■Externally measured by
CentreVu
CMS
■Measured both internally by BCMS and externally by
CentreVu
CMS.
Note that using BCMS in conjunction with
CentreVu
CMS increases the maximum
number of agents and trunk groups that can be measured for a particular ACD
application. In other words, the capacities for BCMS are additive to those of
CentreVu
CMS.
NOTE:
If both BCMS and
CentreVu
CMS are used simultaneously, switch
performance may be degraded.
Interactions with VuStats
VuStats enables agents and supervisors with telephone displays to view data
about agents, splits, and VDNs. Much of this information is the same as that
provided by BCMS.
System Access
2-1Logging In and Logging Off
2
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
2
System Access
Logging In and Logging Off
A BCMS terminal is considered to be a remote Management Terminal. You can
access BCMS reports either from a Management Terminal (local) or on a dial-up
(remote) basis. When dial-up access is used, the following constraints affect the
number of terminals that can access BCMS data simultaneously:
■The number of dial-up (Netcon) channels. (vs/si only)
■The number of Terminal User IDs (TUIs). A TUI is a switch resource used
by:
— the Lucent Technologies Technical Service Center (TSC) when
logged in
— the Management Terminal when powered up
— a remote Management Terminal when logged in
— a BCMS terminal when logged in
— the system printer while printing
— journal/log printer.
When the switch is configured with more than one Management Terminal, you
may use one of the following terminal types to access the BCMS feature:
■4410
■4425
■513
■610
■615
■715 BCT
■terminal emulation.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Access
2-2Logging In and Logging Off
2
Typically, one terminal is dedicated to the administration and/or maintenance
tasks, while the others are used for the ACD/BCMS features.
BCMS Login
The switch provides several different categories of login names. The login name
identifies the user and his or her permitted capabilities to the system. Generally,
each category permits unique capabilities (and restrictions). You must create a
login for each supervisor or other user that you want to view BCMS reports. A
BCMS login can allow you to display, print, and schedule BCMS reports.
Logging In
There are two types of terminal configurations for logging into BCMS: a remote
and a local. Although both configurations use the same types of terminals, the
remote terminal requires a data module for dialing up the system.
!CAUTION:
If you change your BCMS log-in, all scheduled reports must be rescheduled
under the new login in order to run.
Logging In from a Local Terminal
To log into BCMS from a local terminal, perform the following steps:
1. Turn on the terminal (if required) and press BREAK (if no prompt is
displayed).
— The screen displays the following prompt:
Login:
2. Enter the appropriate login and press RETURN.
— The screen displays the following prompt:
Password:
3. Enter your password and press RETURN. For security reasons, the
password is not displayed as you type it. The system verifies that the login
and password you entered are valid.
— If you entered an invalid login or password, the system displays the
following message and prompt:
INCORRECT LOGIN
Login:
Repeat Steps 2 and 3.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Access
2-3Logging In and Logging Off
2
— If you entered the correct login and associated password, the screen
displays the following prompt:
Terminal Type (Enter 513, 715, 4410, 4425, VT220):
[513]
Proceed to Step 4.
4. Enter the appropriate terminal type:
■If you are using a 513 terminal, just press RETURN. 513 (which is
displayed in brackets on the screen) is the default.
■If you are using a 4410 terminal, enter 4410 and press RETURN.
■If you are using a 4425 terminal, enter 4425 and press RETURN.
■If you are using a 610 or 615 MT terminal that has a 513 emulation
cartridge, just press RETURN.
■If you are using a 610 or 615 MT that does not have the 513
emulation cartridge, enter 4410 and press RETURN.
■If you are using a 715 BCT terminal, enter 715 and press RETURN.
After you enter the appropriate terminal type, the system displays the
following prompt:
enter command:
The system is now ready for you to enter a command to generate a BCMS
report.
Logging In from a Remote Terminal
To log into BCMS from a remote terminal, perform the following steps:
1. Turn on the terminal and press BREAK (if no prompt is displayed).
— The screen displays the following prompt:
Dial:
2. Enter the hunt group extension number for the Netcon channels and press
RETURN.
— The screen displays the following prompt:
Login:
3. Enter the appropriate login and press RETURN.
— The screen displays the following prompt:
Password:
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Access
2-4Logging In and Logging Off
2
4. Enter your password and press RETURN.
For security reasons, the password is not displayed as you type it. The
system verifies that the login and password you entered are valid.
— If you entered an invalid login or password, the system displays the
following message and prompt:
INCORRECT LOGIN
"Login:
Repeat Steps 3 and 4.
— If you entered the correct login and associated password, the screen
displays the following prompt:
Terminal Type (Enter 513, 715, 4410, 4425, VT220):
[513]
Proceed to Step 5.
5. Enter the appropriate terminal type:
■If you are using a 513 terminal, just press RETURN. 513 (which is
displayed in brackets on the screen) is the default.
■If you are using a 4410 terminal, enter 4410 and press RETURN.
■If you are using a 4425 terminal, enter 4425 and press RETURN.
■If you are using a 610 or 615 MT terminal that has a 513 emulation
cartridge, just press RETURN.
■If you are using a 610 or 615 MT that does not have the 513
emulation cartridge, enter 4410 and press RETURN.
■If you are using a 715 BCT, enter 715 and press RETURN.
After you enter the appropriate terminal type, the system displays the
following prompt:
enter command:
The system is now ready for you to enter a command to generate a BCMS
report.
Logging Off
Whenever you are not using the terminal, log off the system. To log off the system,
perform the following steps:
1. Type logoff.
2. Press RETURN.
The switch automatically disconnects the terminal.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Access
2-5How to Change the BCMS Password
2
How to Change the BCMS Password
Any user can change the password for the login they have been assigned to view
BCMS reports. The System Manager (or any user with special privileges) can
change the password for other users.
The password should be changed at regular intervals and:
■Each time a new person takes over a login name
■If an unauthorized person has discovered the password
Once a password is assigned or changed, keep the following in mind:
■Do not give the password to anyone
■Keep the written password in a locked place
To change a password, perform the following steps:
1. At the enter command: prompt, enter change password <login name>
and press RETURN.
— The system displays the Password Administration screen (Screen
2-1). The cursor is positioned on the Password of Login
Making Change: field.
Screen 2-1. Password Change Screen
2. Enter your current password and press RETURN.
— The cursor is positioned on the Login’s Password: field.
change password bcms Page 1 of 1
LOGIN ADMINISTRATION
Password of Login Making Change:
LOGIN BEING ADMINISTERED
Login’s Name:
Login Type:
Service Level:
LOGIN’S PASSWORD INFORMATION
Login’s Password:
Reenter Login’s Password:
Password Aging Cycle Length (Days): 120
LOGOFF NOTIFICATION
Facility Test Call Notification? y Acknowledgment Required? y
Remote Access Notification? y Acknowledgment Required? y
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Access
2-6How to Change the BCMS Password
2
3. Enter your new password and press RETURN.
NOTE:
Valid passwords contain four to seven alphabetic or numeric
characters, or a combination of alphabetic and numeric characters.
— The cursor is positioned on the Reenter Login’s Password:
field.
4. Re-enter your new password and press ENTER.
— The system displays the following prompt:
command completed successfully
command:
Generating BCMS Reports
3-1Overview
3
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
3
Generating BCMS Reports
Overview
This chapter describes the procedures for displaying and printing real-time reports
and for displaying, printing, and scheduling historical reports. It is assumed that a
system printer has been connected and administered before attempting to print
these reports.
Displaying and Printing Real-Time
Reports
The monitor command is used to display and print real-time status reports. These
reports display data accrued since the last interval boundary. Data is based on
hourly or half-hourly intervals as administered in the “BCMS/VuStats
Measurement Interval” field on the Feature-Related System Parameters screen.
There are three monitor commands, one to display or print each real-time report:
■bcms split
■bcms system
■bcms vdn.
Whenever a status report is displayed on the Management Terminal, it updates
automatically approximately every 30 seconds. You can immediately update the
on-screen status report by pressing UPDATE. To cancel the monitor command and
return to the command prompt, press CANCEL. If the status report consists of more
than one page, press NEXTPAGE to display any subsequent pages and PREVPAGE
to display any previous pages.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-2Displaying and Printing Real-Time Reports
3
If you incorrectly enter the command, or if the qualifier is not applicable or is not
measured, an error message appears on the message line, located on the bottom
of the screen. If you require more information about the error message, press
HELP.
Complete the steps in the following sections to display or print real-time reports.
Displaying Real-Time Reports
To display a real-time report, complete the following procedures.
1. Type the monitor command that will display the report you want to view.
See Table 3-1.
2. Press RETURN. The report appears on your screen.
3. Press the NEXTPAGE key to display subsequent pages and the PREVPAGE
key to display previous pages if appropriate.
4. To immediately update the report data, press UPDATE.
5. To exit the report, press CANCEL.
:
Printing Real-Time Reports
To print a real-time report, complete the following procedures.
1. Type the monitor command that will print the report. See Table 3-2.
2. Press RETURN. The report prints on the printer that is attached to your
terminal.
Table 3-1. Commands for Displaying Real-Time Reports
To Vie w t he Typ e Whe r e
Split Status Report monitor bcms split ## ## is an administered split
measured by BCMS.
System Status Report monitor bcms system ## ## is an administered split or
range of splits measured by
BCMS. ## is optional. If not
included, the report shows all
splits.
VDN Status Report monitor bcms vdn ## ## is an administered VDN
extension measured by BCMS.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-3Displaying, Printing, and Scheduling Historical Reports
3
Displaying, Printing, and Scheduling
Historical Reports
The list commands are used to display historical information for agents, splits,
trunk groups, and VDNs. There are eight secondary list commands:
■bcms agent
■bcms summary agent
■bcms split
■bcms summary split
■bcms trunk
■bcms summary trunk
■bcms vdn
■bcms summary vdn.
With these commands, you can specify:
■Whether you want data that is collected during a specified range of dates
or during a specified period of time. Data collected during a specified
period of time is based on hourly or half-hourly intervals as administered in
the “BCMS/VuStats Measurement Interval” field on the Feature-Related
System Parameters screen.
!CAUTION:
The switch stores time interval data in a time database that holds a
maximum of 25 intervals. Data for the 26th interval overwrites the first
interval in the time database (and so on). Therefore, if the half-hour
option is selected, care should be exercised to ensure that time
Table 3-2. Commands for Printing Real-Time Reports
To Vie w t he Typ e Whe r e
Split Status Report monitor bcms split ## print ## is an administered split
measured by BCMS.
System Status Report monitor bcms system ##
print ## is an administered split or
range of splits measured by
BCMS. ## is optional. If not
included, the report shows all
splits.
VDN Status Report monitor bcms vdn ## print ## is an administered VDN
extension measured by BCMS.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-4Displaying, Printing, and Scheduling Historical Reports
3
interval reports are run while the data for the desired interval is still
available in the time database. For example, if you select the
half-hour option, print the report twice daily to ensure that you do not
lose information.
■The times or days for which you wish to see data.
■The system to immediately display the report on your terminal.
■The system to print the report. If you include print at the end of the
command, the system will immediately print the report to the printer
attached to the management terminal. If you include schedule at the end
of the command, the system will allow you to schedule the report to print to
the system printer immediately (immediate), at a later time (deferred), or
routinely at specified times (scheduled).
Complete the steps in the following sections to display, print, or schedule historical
reports.
Displaying Historical Reports
To display an historical report, complete the following procedures.
1. Type the list command that will display the report you want to view. See
Table 3-3.
2. Press RETURN. The report appears on your screen.
3. Press the NEXTPAGE key to display subsequent pages and the PREVPAGE
key to display previous pages if appropriate.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-5Displaying, Printing, and Scheduling Historical Reports
3
Table 3-3. Commands for Displaying Historical Reports
To Vie w t he Ty pe Whe r e
Agent Report
(hourly/half-hourly) list bcms agent ## time
staffed xx:xx xx:xx ## is a valid agent extension or
login ID measured by BCMS.
staffed lists data only for the
intervals that the agent has
staffed time.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Agent Report (daily) list bcms agent ## day
staffed xx/xx xx/xx ## is a valid agent extension or
login ID measured by BCMS.
staffed lists data only for the days
that the agent has staffed time.
The first xx/xx is the start day.
The second xx/xx is the stop day.
Agent Summary Report
(hourly/half-hourly) list bcms summary agent
## time staffed xx:xx xx:xx ## is a valid agent extension or
login ID or range of extensions/
login IDs measured by BCMS.
staffed lists data only for agents
with staffed time.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Agent Summary Report
(daily) list bcms summary agent
## day staffed xx/xx xx/xx ## is a valid agent extension or
login ID or range of extensions/
login IDs measured by BCMS.
staffed lists data only for agents
with staffed time.
The first xx/xx is the start day.
The second xx/xx is the stop day.
Split Report
(hourly/half-hourly) list bcms split ## time xx:xx
xx:xx ## is an administered split
measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-6Displaying, Printing, and Scheduling Historical Reports
3
Split Report (daily) list bcms split ## day xx/xx
xx/xx ## is an administered split
measured by BCMS.
The first xx/xx is the start day.
The second xx/xx is the stop day.
Split Summary Report
(hourly/half-hourly) list bcms summary split ##
time xx:xx xx:xx ## is an administered split or
range of splits measured by
BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Split Summary Report
(daily) list bcms summary split ##
day xx/xx xx/xx ## is an administered split or
range of splits measured by
BCMS.
The first xx/xx is the start day.
The second xx/xx is the stop day.
Trunk Group Report
(hourly/half-hourly) list bcms trunk ## time
xx:xx xx:xx ## is a trunk group measured by
BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Trunk Group Report
(daily) list bcms trunk ## day xx/xx
xx/xx ## is a trunk group measured by
BCMS.
The first xx/xx is the start day.
The second xx/xx is the stop day.
Trunk Group Summary
Report
(hourly/half-hourly)
list bcms summary trunk ##
time xx:xx xx:xx ## is a trunk group or range of
trunk groups measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Trunk Group Summary
Report (daily) list bcms summary trunk ##
day xx/xx xx/xx ## is a trunk group or range of
trunk groups measured by BCMS.
The first xx/xx is the start day.
The second xx/xx is the stop day.
Table 3-3. Commands for Displaying Historical Reports — Continued
To Vie w t he Ty pe Whe r e
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-7Displaying, Printing, and Scheduling Historical Reports
3
VDN Report
(hourly/half-hourly) list bcms vdn ##### time
xx:xx xx:xx ## is an administered VDN
extension measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
VDN Report (daily) list bcms vdn ##### day
xx/xx xx/xx ## is an administered VDN
extension measured by BCMS.
The first xx/xx is the start day.
The second xx/xx is the stop day.
VDN Summary Report
(hourly/half-hourly) list bcms summary vdn
##### time xx:xx xx:xx ## is an administered VDN
extension or range of extensions
measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
VDN Summary Report
(daily) list bcms summary vdn
##### day xx/xx xx/xx ## is an administered VDN
extension or range of extensions
measured by BCMS.
The first xx/xx is the start day.
The second xx/xx is the stop day.
Table 3-3. Commands for Displaying Historical Reports — Continued
To Vie w t he Ty pe Whe r e
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-8Displaying, Printing, and Scheduling Historical Reports
3
Printing Historical Reports
If you do not have a printer directly connected to your terminal, see ‘‘Scheduling
Historical Reports’’ on page 3-11.
To print an historical report, complete the following procedures.
1. Type the list command for the report that you want to print. See Table 3-4.
2. Press RETURN. The report prints on the printer that is attached to your
terminal.
Table 3-4. Commands for Printing Historical Reports
To Print the Type Where
Agent Report
(hourly/half-hourly) list bcms agent ## time
staffed xx:xx xx:xx print ## is a valid agent extension or
login ID measured by BCMS.
staffed prints data only for the
intervals that the agent has staffed
time.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
Agent Report (daily) list bcms agent ## day
staffed xx/xx xx/xx print ## is a valid agent extension or
login ID measured by BCMS.
staffed prints data only for the days
that the agent has staffed time.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Agent Summary
Report
(hourly/half-hourly)
list bcms summary agent
## time staffed xx:xx
xx:xx print
## is a valid agent extension or
login ID or range of extensions/
login IDs measured by BCMS.
staffed prints data only for agents
with staffed time.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-9Displaying, Printing, and Scheduling Historical Reports
3
Agent Summary
Report (daily) list bcms summary agent
## day staffed xx/xx xx/xx
print
## is a valid agent extension or
login ID or range of extensions/
login IDs measured by BCMS.
staffed prints data only for agents
with staffed time.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Split Report
(hourly/half-hourly) list bcms split ## time
xx:xx xx:xx print ## is an administered split
measured by BCMS.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
Split Report (daily) list bcms split ## day
xx/xx xx/xx print ## is an administered split
measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Split Summary Report
(hourly/half-hourly) list bcms summary split
## time xx:xx xx:xx print ## is an administered split or range
of splits measured by BCMS.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
Split Summary Report
(daily) list bcms summary split
## day xx/xx xx/xx print ## is an administered split or range
of splits measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Trunk Group Report
(hourly/half-hourly) list bcms trunk ## time
xx:xx xx:xx print ## is a trunk group measured by
BCMS.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
Trunk Group Report
(daily) list bcms trunk ## day
xx/xx xx/xx print ## is a trunk group measured by
BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Table 3-4. Commands for Printing Historical Reports — Continued
To Print the Type Where
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-10Displaying, Printing, and Scheduling Historical Reports
3
Trunk Group
Summary Report
(hourly/half-hourly)
list bcms summary trunk
## time xx:xx xx:xx print ## is a trunk group or range of
trunk groups measured by BCMS.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
Trunk Group
Summary Report
(daily)
list bcms summary trunk
## day xx/xx xx/xx print ## is a trunk group or range of
trunk groups measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
VDN Report
(hourly/half-hourly) list bcms vdn ##### time
xx:xx xx:xx print ## is an administered VDN
extension measured by BCMS.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
VDN Report (daily) list bcms vdn ##### day
xx/xx xx/xx print ## is an administered VDN
extension measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
VDN Summary Report
(hourly/half-hourly) list bcms summary vdn
##### time xx:xx xx:xx
print
## is an administered VDN
extension or range of extensions
measured by BCMS.
The first xx:xx is the start time. The
second xx:xx is the stop time. Both
are in military time.
VDN Summary Report
(daily) list bcms summary vdn
##### day xx/xx xx/xx
print
## is an administered VDN
extension or range of extensions
measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Table 3-4. Commands for Printing Historical Reports — Continued
To Print the Type Where
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-11Displaying, Printing, and Scheduling Historical Reports
3
Scheduling Historical Reports
The Report Scheduler allows you to schedule the day or days for the system to
print the report. If you do not have a printer directly connected to your terminal,
you can use the Report Scheduler feature to print the report immediately to the
system printer. For more detailed information about the Report Scheduler, see
Chapter 5, ‘‘System Printer and Report Scheduler’’.
To schedule an historical report, complete the following procedures.
1. Type the list command that will schedule the report. See Table 3-5.
2. Press RETURN.
— The Report Scheduler form appears on your screen. The cursor is
located in the Print Interval: field.
Screen 3-1. Report Scheduler Form
NOTE:
If you do not have a printer directly connected to your terminal, you
can immediately print the report to the system printer by pressing
ENTER.
3. Enter schedule and press RETURN.
—The Print Time: field appears beneath the Print
Interval: field, and fields for each day of the week appear at the
bottom of the form. The cursor is located in the Print Time:
field.
list bcms agent ## time xx:xx xx:xx
Page 1
REPORT SCHEDULER
Date: 11:00 pm MON APR 23, 1990
Job Id: 1 Job Status: none
Command: list bcms agent ## time xx:xx xx:xx
Print Interval: immediate
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-12Displaying, Printing, and Scheduling Historical Reports
3
Screen 3-2. Report Scheduler Form with the Print Interval Set to
scheduled
4. Enter the time you want the report printed and press RETURN.
— The cursor moves to the Sun: field.
5. Enter y for the day(s) you want the report printed. Use RETURN to move the
cursor to the next field.
6. When you are finished, press ENTER.
— The report has been scheduled, and the system presents the enter
command: prompt.
!CAUTION:
If you change your BCMS log-in, all scheduled reports must be rescheduled
under the new login in order to run.
NOTE:
The commands for scheduling historical reports also can be used to defer
printing of a report to a later time. See ‘‘Report Scheduler’’ on page 5-3 for
more information.
list bcms agent ## time xx:xx xx:xx
Page 1
REPORT SCHEDULER
Date: 11:00 pm MON APR 23, 1990
Job Id: 1 Job Status: none
Command: list bcms agent ## time xx:xx xx:xx
Print Interval: scheduled
Print Time: xx:xx
Sun: n Mon: n Tue: n Wed: n Thu: n Fri: n Sat: n
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-13Displaying, Printing, and Scheduling Historical Reports
3
Table 3-5. Commands for Scheduling Historical Reports
To Print the Type Where
Agent Report
(hourly/half-hourly) list bcms agent ## time
staffed xx:xx xx:xx
schedule
## is a valid agent extension or
login ID measured by BCMS.
staffed prints data only for the
intervals that the agent has staffed
time.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Agent Report (daily) list bcms agent ## day
staffed xx/xx xx/xx
schedule
## is a valid agent extension or
login ID measured by BCMS.
staffed prints data only for the
days that the agent has staffed
time.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Agent Summary
Report
(hourly/half-hourly)
list bcms summary agent
## time staffed xx:xx xx:xx
schedule
## is a valid agent extension or
login ID or range of extensions/
login IDs measured by BCMS.
staffed prints data only for agents
with staffed time.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Agent Summary
Report (daily) list bcms summary agent
## day staffed xx/xx xx/xx
schedule
## is a valid agent extension or
login ID or range of extensions/
login IDs measured by BCMS.
staffed prints data only for agents
with staffed time.
The first xx:xx is the start day. The
second xx:xx is the stop day.
Split Report
(hourly/half-hourly) list bcms split ## time
xx:xx xx:xx schedule ## is an administered split
measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-14Displaying, Printing, and Scheduling Historical Reports
3
Split Report (daily) list bcms split ## day
xx/xx xx/xx schedule ## is an administered split
measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Split Summary Report
(hourly/half-hourly) list bcms summary split
## time xx:xx xx:xx
schedule
## is an administered split or
range of splits measured by
BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Split Summary Report
(daily) list bcms summary split
## day xx/xx xx/xx
schedule
## is an administered split or
range of splits measured by
BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Trunk Group Report
(hourly/half-hourly) list bcms trunk ## time
xx:xx xx:xx schedule ## is a trunk group measured by
BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Trunk Group Report
(daily) list bcms trunk ## day
xx/xx xx/xx schedule ## is a trunk group measured by
BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Trunk Group Summary
Report
(hourly/half-hourly)
list bcms summary trunk
## time xx:xx xx:xx
schedule
## is a trunk group or range of
trunk groups measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
Trunk Group Summary
Report (daily) list bcms summary trunk
## day xx/xx xx/xx
schedule
## is a trunk group or range of
trunk groups measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Table 3-5. Commands for Scheduling Historical Reports — Continued
To Print the Type Where
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-15Displaying, Printing, and Scheduling Historical Reports
3
VDN Report
(hourly/half-hourly) list bcms vdn ##### time
xx:xx xx:xx schedule ## is an administered VDN
extension measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
VDN Report (daily) list bcms vdn ##### day
xx/xx xx/xx schedule ## is an administered VDN
extension measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
VDN Summary Report
(hourly/half-hourly) list bcms summary vdn
##### time xx:xx xx:xx
schedule
## is an administered VDN
extension or range of extensions
measured by BCMS.
The first xx:xx is the start time.
The second xx:xx is the stop time.
Both are in military time.
VDN Summary Report
(daily) list bcms summary vdn
##### day xx/xx xx/xx
schedule
## is an administered VDN
extension or range of extensions
measured by BCMS.
The first xx/xx is the start day. The
second xx/xx is the stop day.
Table 3-5. Commands for Scheduling Historical Reports — Continued
To Print the Type Where
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Generating BCMS Reports
3-16Displaying, Printing, and Scheduling Historical Reports
3
BCMS Report Reference
4-1Overview
4
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
4
BCMS Report Reference
Overview
Table 4-1 is a quick reference to the commands that you can use to display, print,
and schedule BCMS reports. See Chapter 3, ‘‘Generating BCMS Reports’’ for
more detailed instructions for displaying, printing, and scheduling reports.
The remainder of this chapter describes each report in detail, providing a brief
description of each report, sample reports, and a description of the information
contained in each report.
NOTE:
Most BCMS measurement data is collected at the end of a call, whereas
hunt group measurements count calls as soon as they begin. Therefore,
calls spanning across a time interval boundary will be counted differently by
the two. If comparing the measurements from BCMS with those from the
hunt groups, there may be slight differences. However, both hunt group and
BCMS measurements should indicate the same trends.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-2Overview
4
.
Table 4-1. BCMS Administration Commands
BCMS Administration Commands1
1. Items depicted within brackets, such as [print], are optional.
Action Object Qualifiers
monitor bcms split split number [print]
bcms system [split number]2 [print]
2. Whenever the command line qualifier [schedule] is initially executed, the system defaults the
report for immediate printing (unless a day/time of day is scheduled) and generates a Job Id.
The Job Id is required by the Report Scheduler feature for updating and deleting the
schedule of reports.
bcms vdn extension2 [print]
list bcms agent ext.|loginID3 [time] [staffed] [start time] [stop time] [print|schedule]2
3. If “BCMS/VuStats Login IDs” is enabled on the System-Parameters Customer-Options form,
then you must enter an agent’s login ID or a range of login IDs in place of the physical
extension or range of extensions. (VuStats is not supported with DEFINITY BCS and
GuestWorks; however, BCMS Login IDs are supported.)
bcms agent ext.|loginID3 [day] [staffed] [start day] [stop day] [print|schedule]
bcms summary agent ext.|loginID2 3 [time] [staffed] [start time] [stop time]
[print|schedule]
bcms summary agent ext.|loginID2 3 [day] [staffed] [start day] [stop day] [print|schedule]
bcms split split number [time] [start time] [stop time] [print|schedule]
bcms split split number [day] [start day] [stop day] [print|schedule]
bcms summary split split number2 [time] [start time] [stop time] [print|schedule]
bcms summary split split number2 [day] [start day] [stop day] [print|schedule]
bcms trunk group number [time] [start time] [stop time] [print|schedule]
bcms trunk group number [day] [start day] [stop day] [print|schedule]
bcms summary trunk group number2 [time] [start time] [stop time] [print|schedule]
bcms summary trunk group number2 [day] [start day] [stop day] [print|schedule]
bcms vdn extension [time] [start time] [stop time] [print|schedule]
bcms vdn extension [day] [start day] [stop day] [print|schedule]
bcms summary vdn extension2 [time] [start time] [stop time] [print|schedule]
bcms summary vdn extension2 [day] [start day] [stop day] [print|schedule]
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-3Real-Time Reports
4
Real-Time Reports
BCMS provides three real-time reports:
■BCMS Split Status
■BCMS System Status
■BCMS VDN Status.
The BCMS Split Status report provides the current (real-time) status and
cumulative measurement data for those agents assigned to the split you specify.
The BCMS System Status report provides current (real-time) status information
for either all BCMS splits or selected splits. The BCMS VDN Status report
provides the current (real-time) status and cumulative measurement data for
VDNs monitored by BCMS.
BCMS Split Status Report
Command
Use the following command to generate the BCMS Split Status report:
monitor bcms split (split number) [print]
Description
The BCMS Split Status report provides the current (real-time) status and
cumulative measurement data for those agents assigned to the split you specify.
This report displays data accrued since the last interval boundary. For example, if
the interval is set for hourly, and you issue the command to display the BCMS
Split Status report at 11:10 a.m., the report displays the data accrued since 11:00
a.m. Although this report is updated approximately every 30 seconds, you can
immediately update the information on the screen by pressing UPDATE. At the
beginning of the next interval, the report resets.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-4Real-Time Reports
4
Sample Report
Screen 4-1. BCMS Split Status Report Screen
*An asterisk precedes the
Calls Waiting
field if any of the calls are
Direct Agent calls.
&The
LOGIN ID
column is empty if the BCMS login system
parameter is set to
no.
$ If name is not administered, this column is blank for the agent.
Split is displayed as “Skill” when EAS is optioned (EAS and skills are not
supported with DEFINITY BCS and GuestWorks).
monitor bcms split 30
BCMS SPLIT (AGENT) STATUS
Split: 30 Date: 12:13 pm MON MAY 15, 1995
Split Name: headquarters
Calls Waiting: 5 Acceptable Service Level: xxx
Oldest Call: 1:39 % Within Service Level: xxx
Staffed: 7 Avail: 1 ACD: 1 ACW: 2 AUX: 2 Extn Calls: 2 Other: 1
ACD EXT IN EXT OUT
AGENT NAME LOGIN ID EXT STATE TIME CALLS CALLS CALLS
Agent 1 32191 12345 Avail 12:00 0 0 0
Agent 2 32192 12346 ACD 12:04 1 0 0
Agent 3 32193 12347 ACW 12:12 3 0 0
Agent 4 32194 12348 AUX 11:30 0 0 0
Agent 5 32195 12349 Ext In 12:08 1 2 0
Agent 6 32196 12350 Ext Out 12:10 0 0 1
Agent 7 32197 12351 Other 11:58 0 0 0
$ 32198 12352 INIT 00:00 0 0 0
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-5Real-Time Reports
4
Header Definition
Table 4-2. Split Status Report Header Definitions
Header Definition
Split The split number specified with the command line.
Split Name The administered name of the split. This name usually describes the
purpose or service of the split (for example, sales, service, or help line). If
no name exists, BCMS displays the split extension (for example,
EXT 65222).
The split name is limited to a maximum of 11 characters. If you enter
more than 11 characters, the additional characters are not printed on the
System Printer.
Calls Waiting The number of calls currently queued and calls ringing at an agent’s
phone. If any of the calls in the queue are Direct Agent calls, an asterisk
appears before the value in this field.
Oldest Call The number of minutes and seconds that the oldest call in queue has
been waiting to be answered. This includes calls ringing at an agent’s
phone.
Acceptable
Service Level The desired time for an agent to answer a call for a given hunt group or
VDN. Timing for a call begins when the call enters the hunt group queue.
% Within
Service Level The percentage of calls answered within the administered service level.
This field is blank if no calls have been recorded for this time interval or if
there is no
Acceptable Service Level
administered on the Hunt Group
form.
NOTE:
Not available with DEFINTY BCS and Guestworks.
Staffed The number of agents currently logged into the split. Staffed equals
available agents, agents on ACD calls and agents in ACW, AUX, and
Other.
Avail The number of agents in this split currently available to receive an ACD
call. In order to be counted as being available, agents must either be in
the Auto-In (AI) or Manual-In (MI) work mode. Refer to the Glossary for a
description of work modes. If the agent is on another split’s call or is
performing After Call Work for another split, the agent is not considered
available and is not recorded here. If a call is ringing at the agent’s phone
or a call is on hold, the agent is not considered available unless Multiple
Call Handling is active and the agent selects AI/MI with a call on hold.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-6Real-Time Reports
4
ACD The number of agents who are currently on an ACD call for this split. This
value also includes Direct Agent calls and those agents who are currently
on ACD calls that flowed in from another split.
ACW The number of agents in this split who are currently in ACW mode for this
split. Refer to the Glossary for a description of After Call Work (ACW)
mode. If an agent is in ACW mode for another split, the agent is included
in the Other state count for this split. ACW includes agents who are on
extension-in and extension-out calls while in ACW.
AUX The number of agents in this split who are currently in the AUX work
mode for this split. If an agent is answering a call from another split or is
in ACW work mode for another split, that agent is not considered in AUX
work mode for this split and is not included in this number. The agent is
included in the Other state count. AUX includes agents who are on
extension-in and extension-out calls while in AUX, Auto-In and
Manual-In.
Extn The number of agents in this split who are currently on non-ACD calls.
These non-ACD calls may be either incoming (direct to the extension) or
outgoing (direct from the extension). Those agents receiving or making
extension calls while available, or while in the ACW or AUX work mode
are recorded as being on extension calls.
Other The number of agents in this split who:
■Are on a call from another split
■Are in ACW work mode for another split
■Have placed a call on HOLD and made no other state selections
■Have a call ringing at their telephones
■Are dialing a number (to place a call or activate a feature)
All of the agents in the Other state are unavailable for ACD calls.
AGENT NAME The name of the agent. Generally, this is the agent’s first or last name.
However, if no name is administered on the station form, this field is left
blank. When the field is blank, the data can be identified by the extension.
LOGIN ID The BCMS login ID(s) (taken from the BCMS/VuStatus Login ID form or
EAS Login form) for which you requested the report. This column is
empty if BCMS logins are not optioned. (VuStats are not supported on
DEFINITY BCS and GuestWorks: however, BCMS Login IDs are
supported.)
EXT The 1-, 2-, 3-, 4-, or 5-digit extension number for the agent.
Table 4-2. Split Status Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-7Real-Time Reports
4
STATE The current work state for the agent. Possible work states are Avail,
ACD, ACW, AUX, Extn, and Other. Unstaffed agents do not appear on
the report. When the system time is changed, agents are in the INIT
state. Each agent remains in the INIT state until he or she takes a call or
pushes a work mode button.
TIME The 24-hour clock time at which the agent entered this work state.
ACD CALLS The number of ACD calls that the agent has completed since the
beginning of the current interval. This value includes any calls that flowed
in from other splits. (Calls in process are not counted until they are
completed.)
EXT IN CALLS The number of non-ACD calls that the agent has received (incoming)
since the beginning of the current interval. (Calls in process are not
counted until they are completed.) The maximum value is 255.
If an extension-in call is active for less than the time set for the Abandon
Call Timer, the call will not be counted in this field. The duration of such
calls is counted as AUX/OTHER time.
EXT OUT
CALLS The number of non-ACD calls that the agent has made (outgoing) since
the beginning of the current interval. (Calls in process are not counted
until they are completed.) The maximum value is 255.
Table 4-2. Split Status Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-8Real-Time Reports
4
BCMS System Status Report
Command
Use the following command to generate the BCMS System Status report:
monitor bcms system [split number] [print]
Description
The BCMS System Status report provides current (real-time) status information
for either all BCMS splits or selected BCMS splits. This report displays data
accrued since the last interval boundary. For example, if the interval is set to hour,
and you issue the command to display the BCMS System Status report at 11:10
a.m., the report displays the data accrued since 11:00 a.m. Although this report is
updated approximately every 30 seconds, you can immediately update the
information on the screen by pressing UPDATE. This report is reset at the beginning
of the time interval (for example, hour or half-hour).
NOTE:
When analyzing this report, keep the following things in mind:
■All averages are for completed calls only.
■A completed call may span more than one time interval. ACD calls that are
in process (have not terminated) are counted in the time interval in which
they terminate. For example, if an ACD call begins in the 10:00 to 11:00
time interval, but terminates in the 11:00 to 12:00 time interval, the data for
this call is counted in the 11:00 to 12:00 time interval.
■Asterisks indicate that the maximum for the associated field has been
exceeded.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-9Real-Time Reports
4
Sample Report
Screen 4-2. BCMS System Status Report Screen
Header Definitions
&Split name is not administered — default is EXT xxxx, where
xxxx is the extension administered for the split.
Split is displayed as “Skill” when EAS is optioned (EAS and skills
are not supported with DEFINITY BCS and GuestWorks).
Table 4-3. System Status Report Header Definitions
Header Definition
SPLIT NAME The name of the split (for example, sales, service, or help line). If no
name exists, the split extension (for example, EXT 12345) is
displayed.
CALLS WAIT The number of calls in the split’s queue that are currently waiting to be
answered and calls ringing at an agent’s phone. If any of the calls in
the queue are Direct Agent calls, an asterisk appears before this field.
Consult the Glossary for a description of the Direct Agent feature.
OLDEST CALL The number of minutes and seconds the oldest call in queue has been
waiting to be answered. This includes calls ringing at an agent’s
phone.
Continued on next page
monitor bcms system
BCMS SYSTEM STATUS
Date: 12:53 MON MAY 15, 1995
AVG AVG AVG AVG % IN
CALLS OLDEST SPEED AVAIL ABAND ABAND ACD TALK AFTER SERV
SPLIT NAME WAIT CALL ANS AGENT CALLS TIME CALLS TIME CALL LEVL
Service 3 1:03 :45 0 3 :30 20 2:30 1:25 85
EXT 4000 5 :33 :15 0 11 :45 36 1:32 :35 91
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-10Real-Time Reports
4
AVG SPEED
ANS The average amount of time it takes before the calls are answered by
agents. This value includes time waiting in the queue and time ringing
at the agent’s telephone. The calculation is:
Keep the following things in mind:
■Calls that flow in from other split(s) do not include
time in queue
from the other splits in this calculation. Also, the AVG SPEED
ANS does not include time spent listening to a forced first
announcement.
■A completed call may span more than one time period. ACD
calls that are in process (have not terminated) are counted in
the time period in which they terminate. For example, if an ACD
call begins in the 10:00 to 11:00 time period, but terminates in
the 11:00 to 12:00 time period, the data for this call is counted in
the 11:00 to 12:00 time period.
■Asterisks indicate that the maximum for the associated field has
been exceeded.
AVAIL AGENT The number of agents in this split who are currently available to
receive an ACD call directed to this split.
ABAND CALLS The total number of ACD calls that have hung up while waiting to be
answered. This includes those calls that have abandoned while in
queue or while ringing. Calls that are not queued (for example,
because the queue is full, the caller receives a forced first
announcement and abandons during the announcement, or no agents
are staffed) are not counted as abandoned for the hunt group.
AVG ABAND
TIME The average time before an ACD call abandons. This does not include
any time spent in another split’s queue before intraflowing to this split.
The calculation is:
This value does not include time spent listening to a forced first
announcement or calls that
abandon
while listening to a forced first
announcement.
Table 4-3. System Status Report Header Definitions — Continued
Header Definition
Continued on next page
AVG SPEED ANS =
Sum of Each Completed Call’s Time In Queue + Time Ringing
Total Number of ACD Calls Answered
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
AVG ABAND TIME Total Abandon Time
Total Number of Abandoned Calls
------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-11Real-Time Reports
4
ACD CALLS The number of ACD calls completed during the current interval. This
number also includes those calls that flow in from other splits.
AVG TALK
TIME The average duration of ACD calls for each split. This calculation
includes the time each agent spent talking but does not include ring
time at an agent’s telephone. The calculation is:
AVG AFTER
CALL The average ACW time for call-related ACW time completed by agents
in this split during this time interval. Call-related ACW is the time that
occurs immediately after an ACD call (that is, when an agent was in
Manual mode and an ACD call ended, or when the agent presses the
ACW button during an ACD call). AVG AFTER CALL does not include
time spent on direct incoming or outgoing calls while in ACW or time
that immediately follows an EXTN call. The calculation is:
The average is for ACW sessions, which may not correspond to the
number of ACD calls either because some ACD calls did not have
ACW time or because the call was recorded in another interval.
% IN SERV
LEVL The percentage of calls answered within the administered service level
for this split. Calculation is based on the following
where
accepted is calls answered whose queue time was less than or equal
to the administered service level for the split.
dequeued is a call that encountered the split’s queue, but which was
NOT answered, abandoned, or outflowed. This occurs with multiple
split queuing.
NOTE:
Not available with DEFINTY BCS and Guestworks.
Table 4-3. System Status Report Header Definitions — Continued
Header Definition
Continued on next page
AVG TALK TIME Total ACD Talk Time
Total Number of ACD Calls Answered
----------------------------------------------------------------------------------------------------=
AVG AFTER CALL Total Call-Related ACW Time
Number of Call-Related ACW Sessions
--------------------------------------------------------------------------------------------------------=
% IN SERV LEVL accepted * 100
ACDcalls + abandons + outflows + dequeued
------------------------------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-12Real-Time Reports
4
BCMS VDN Status Report
Command
Use the following command to generate the BCMS VDN Status report:
monitor bcms vdn extension [print]
Description
The VDN Status report gives real-time status information for internally measured
VDNs. (See the BCMS Feature Capacity table in Chapter 1, ‘‘BCMS
Description’’.) You must specify the extensions of the VDNs you want the system
to monitor. You can specify the extensions in a list or in a range format. For
example, monitor bcms vdn 12345 12346 12350-12359
.
Sample Report
Screen 4-3. BCMS VDN Status Report Screen
* Indicates that the VDN name is not administered for the VDN;
default extension is as shown.
monitor bcms vdn 12345-12349
BCMS VECTOR DIRECTORY NUMBER STATUS
Date: 15:30 Mon May 15, 1995
AVG AVG AVG CALLS % IN
CALLS OLDEST ACD SPEED ABAND ABAND TALK/ CONN FLOW BUSY/ SERV
VDN NAME WAIT CALL CALLS ANS CALLS TIME HOLD CALLS OUT DISC LEVL
knives 5 :25 50 :39 5 :45 2:30 0 0 24 91
EXT 12346* 0 :00 0 :00 0 :00 :00 0 0 0 0
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-13Real-Time Reports
4
Header Definition
Table 4-4. VDN Status Report Header Definitions
Header Definition
Date The current date and time (updated every 30 seconds or when the update
key is pressed).
VDN NAME The name of the VDN being reported. If the VDN does not have a name
administered, this field displays
EXT XXXXX
where “
XXXXX”
is the
VDN’s extension.
CALLS WAIT The number of calls that encountered this VDN and have not been
answered, abandoned, outflowed, or forced busy/disc. Includes calls in
queues, in vector processing, and ringing at an agent’s station.
OLDEST CALL The time the oldest call currently waiting has waited in the VDN. Timing
starts when the call enters the VDN.
ACD CALLS The number of completed ACD calls answered in a BCMS-measured
split. The split may have been reached via the queue-to-main, check
backup, route-to, messaging split, or adjunct routing commands. Includes
Direct Agent calls (EAS only).
AVG SPEED
ANS The average speed of answer for ACD and connect calls (see CONN
CALLS below) that have completed for this VDN during the current
period. This includes the time in vector processing, in a split’s queue, and
time ringing. The calculation is:
Answer time for a call is recorded when the call ends. If a call originates
in interval x, is answered in interval y, and ends in interval z, the
associated answer and talk times are recorded in interval z.
ABAND CALLS The number of calls to this VDN that have abandoned before being
answered during the current period. This includes VDN calls that were
routed to an attendant, station, or announcement, and abandoned before
being answered.
Continued on next page
AVG SPEED ANS Total Answer Time
Total ACD Calls + Total CONNect CALLS
--------------------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-14Real-Time Reports
4
AVG ABAND
TIME The average time abandoned calls waited before abandoning during the
current period. The calculation is:
AVG
TALK/HOLD The average talk time for ACD calls completed by this VDN during the
current period. This does not include ring time, but it does include any
time the caller spent on Hold. The calculation is:
CONN CALLS The number of completed calls that were routed to a station, attendant,
announcement, messaging skill, or call pickup and were answered there.
Table 4-4. VDN Status Report Header Definitions — Continued
Header Definition
Continued on next page
AVG ABAND TIME Total Abandon Time
Total Calls Abandoned
------------------------------------------------------------=
AVG TALK/HOLD Total Talk Time
ACD Calls
-----------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-15Real-Time Reports
4
FLOW OUT The number of calls that were routed to another VDN or to a trunk,
including successful look-ahead attempts.
CALLS
BUSY/DISC The number of calls that were forced busy or forced disconnect during the
current interval. This value includes:
■calls that encountered a busy or disconnect vector step
■calls disconnected by a stop vector step
■calls forwarded to a split or skill with a full queue
■calls forwarded to a split or skill with no available agents and no
queue
This value does not include abandoned calls.
% IN SERV
LEVL The percent of calls offered that completed and were answered within the
acceptable service level defined on the VDN form. The calculation is:
call offered is defined as:
acdcalls + flowout calls + abandoned + connect + busy/disc
Accepted is the number of ACD and CONNect calls that were answered
within the administered service level. This field is blank if no calls were
recorded for this time interval. This field is also blank if no
Acceptable
Service Level
has been administered on the VDN form.
NOTE:
Not available with DEFINTY BCS and Guestworks.
Table 4-4. VDN Status Report Header Definitions — Continued
Header Definition
Continued on next page
% IN SERV LEVL accepted * 100
calls offered
----------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-16Historical Reports
4
Historical Reports
BCMS provides eight historical reports. These reports give you information for an
interval of time. You can print the reports for a period of time measured in minutes
or hours, or a period of time measured in days. The BCMS historical reports are
as follows:
■Agent
■Agent Summary
■Split
■Split Summary
■Trunk Group
■Trunk Group Summary
■VDN
■VDN Summary.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-17Historical Reports
4
BCMS Agent Report
Command
Use one of the following commands to generate the BCMS Agent Report:
list bcms agent extension/loginID [time] [staffed] [start time] [stop
time][print/schedule]
list bcms agent extension/loginID [day] [staffed] [start day] [stop day]
[print/schedule]
Description
The BCMS Agent Report provides traffic information for the specified agent.
Depending on specifics from the command line, the information may be displayed
as either a time interval or a daily summary. If neither
time
nor
day
is specified,
time
is the default. In this case, the report displays data accrued for the
previous 24 time intervals (hour or half-hour), including data from the most
recently completed time interval. To get information on the current time interval,
you must use a monitor bcms command.
When analyzing this report, keep the following in mind:
■All averages are for completed calls only.
■A completed call may span more than one time interval. ACD calls that are
in process (have not terminated) are counted in the time interval in which
they terminate. For example, if an ACD call begins in the 10:00 to 11:00
time interval, but terminates in the 11:00 to 12:00 time interval, the data for
this call is counted in the 11:00 to 12:00 time interval.
■Asterisks indicate that the maximum for the associated field has been
exceeded.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-18Historical Reports
4
Sample Reports
Screen 4-4. BCMS Agent Report — Hourly
Screen 4-5. BCMS Agent Report — Daily
list bcms agent 4222 8:00
BCMS AGENT REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Agent: 4222
Agent Name: s-jones
AVG TOTAL TOTAL TOTAL AVG TOTAL TOTAL
ACD TALK AFTER AVAIL AUX/ EXTN EXTN TIME HOLD
TIME CALLS TIME CALL TIME OTHER CALLS TIME STAFFED TIME
8:00- 9:00 10 1:15 7:30 25:00 10:40 1 4:00 60:00 :20
9:00-10:00 18 1:40 18:00 4:20 :00 2 3:20 60:00 1:00
10:00-11:00 10 1:20 8:20 16:10 :00 0 :00 38:00 :10
----------- ----- ------ ------- ------- ------- ----- ----- -------- ------
SUMMARY 38 1:28 33:50 45:30 10:40 3 3:33 158:00 1:30
list bcms agent 4222 day 5/13
BCMS AGENT REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Agent: 4222
Agent Name: s-jones
AVG TOTAL TOTAL TOTAL AVG TOTAL TOTAL
ACD TALK AFTER AVAIL AUX/ EXTN EXTN TIME HOLD
DAY CALLS TIME CALL TIME OTHER CALLS TIME STAFFED TIME
5/14/95 200 1:30 100:00 35:00 80:00 10 2:00 540:00 5:00
5/13/95 38 1:28 34:12 45:30 10:40 3 3:33 158:00 1:30
----------- ----- ------ ------- ------- ------- ----- ----- -------- ------
SUMMARY 238 1:30 134:12 80:30 90:40 13 2:22 698:00 6:30
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-19Historical Reports
4
Header Definitions
Table 4-5. Agent Report Header Definitions
Header Definition
Agent The extension or login ID of the agent.
Agent Name The name of the agent. If no name is administered, the agent’s extension
is displayed in the form
EXT 65432.
TIME/DAY The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the earliest time interval (either hour or
half-hour). If no start time is given, the oldest time interval is the default. A
stop time requires an associated start time. If no stop time is given, the
last completed time interval (hour or half-hour) is the default. If no start
time or stop time is given, the report displays data accrued for the
previous 24 time intervals. If you specify
day
in the command and do not
include a start day or stop day, the report displays data accrued for the
previous 6 days and data accrued through the most recently completed
interval (hour or half-hour) for the current day.
ACD CALLS The number of ACD calls answered by this agent for all splits during the
reporting interval. This value includes calls that flowed in from other splits
and Direct Agent calls.
AVG TALK
TIME The average duration of ACD calls for all splits the agent was logged into.
This value includes time spent talking but does not include the amount of
time the agent was holding an ACD call or ring time at the agent’s
telephone. The calculation is:
TOTAL
AFTER CALL The total amount of time that the agent spent in call-related or
non-call-related ACW work states for all splits during the reporting
interval. This includes time agents spent on extension-in and
extension-out calls while in the ACW work mode. If an agent entered
ACW in one interval, but ended ACW in another interval, the appropriate
amount of ACW time is credited to each of the intervals.
Continued on next page
AVG TALK TIME Total ACD Talk Time
Total Number of ACD Calls Answered
----------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-20Historical Reports
4
TOTAL AVAIL
TIME The sum of the time that the agent was available to receive ACD calls
during the reporting interval. During this time, the agent:
■Was in Auto-In or Manual-In work mode for at least one split.
■Was not in ACW in any split.
■Was not on any call or placing any call (unless Multiple Call
Handling [MCH] is active).
■Did not have ringing calls.
TOTAL
AUX/OTHER The total time that this agent was unavailable to receive calls in any split
during the reporting interval.
A split totals AUX TIME whenever any agent is logged into the split and:
■Receives an EXTN call while in AUX or AVAIL state.
■Makes an EXTN call while in AUX or AVAIL state.
■Hits his/her AUX button.
Note that if the agent was in Other for all logged-in splits, that time is
reflected here. For example, ringing calls can cause several seconds of
AUX/OTHER time to accrue.
For the agent report, any non-ACD call time is also totaled in the AVG
EXTN TIME column. Two points of contrast are:
1. The measurement TOTAL AUX/OTHER is time-interval based, rather
than being call-related. For example, assuming that the previously
identified stipulations are met, then if the agent is in AUX from 9:55 to
10:05, 5 minutes is recorded in the 9:00 to 10:00 time interval and 5
minutes is recorded in the 10:00 to 11:00 time interval.
2. The measurement AVG EXTN TIME is call related. For example, if an
agent is on a non-ACD call from 9:55 to 10:05, the call and 10
minutes of EXTN time is recorded in the 10:00 to 11:00 time interval.
Because the agent report includes some call-related items, the sum of all
items for a given hour may not exactly equal 60 minutes.
EXTN CALLS The total number of non-ACD incoming and outgoing calls for this agent
during the reporting interval. Only those non-ACD calls that are originated
and/or received while the agent is logged into at least one split are
counted.
If an extension-in call is active for less than the time set for the Abandon
Call Timer, the call will not be counted in this field.
Table 4-5. Agent Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-21Historical Reports
4
AVG EXTN
TIME The average amount of time that the agent spent on non-ACD calls while
logged into at least one split during the reporting interval. This average
does not include time when the agent was holding the EXTN call. The
calculation is:
If an extension-in call is active for less than the time set for the Abandon
Call Timer, the call will not be counted and the duration of the call will be
counted as AUX/OTHER time.
TOTAL TIME
STAFFED The total time that the agent spent logged into at least one split during the
reporting interval. Staff time is clocked for an agent who is in multiple
splits as long as the agent is logged into any split. Concurrent times for
each split are not totaled.
TOTAL HOLD
TIME The total time that the agent placed ACD calls on hold. This time is the
caller’s hold time
and is independent of the state of the agent. TOTAL
HOLD TIME does not include the hold time for non-ACD calls.
SUMMARY The total of each of the columns that do not contain averages. Columns
that do contain averages are the total time divided by the total number of
calls.
Table 4-5. Agent Report Header Definitions — Continued
Header Definition
Continued on next page
AVG EXTN TIME Total Ext Time
Total Number of Ext Calls
--------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-22Historical Reports
4
BCMS Agent Summary Report
Command
Use one of the following commands to generate the BCMS Agent Summary
report:
list bcms summary agent extension|loginID [time] [staffed] [start time] [stop
time][print/schedule]
list bcms summary agent extension|loginID [day] [staffed] [start day] [stop
day] [print/schedule]
Description
This report is similar to the BCMS Agent report except that this report provides
one line of data for each agent. You can specify one or more agents by entering
agent IDs or extensions. An agent does not appear on the report if there is no
data for that agent. If you specify that you want the report to include more than
one time period, and the data exists for one or more, but not all of the specified
times, the system uses the available data to calculate and display the one-line
summary; the system does not identify which times are not included in the
calculations.
Sample Reports
Screen 4-6. BCMS Agent Summary Report — Hourly Summary
list bcms summary agent 4222-4224 4869 time 8:00-12:00
BCMS AGENT SUMMARY REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Time: 8:00-12:00
AVG TOTAL TOTAL TOTAL AVG TOTAL TOTAL
ACD TALK AFTER AVAIL AUX/ EXTN EXTN TIME HOLD
AGENT NAME CALLS TIME CALL TIME OTHER CALLS TIME STAFFED TIME
s-jones 10 1:15 7:30 25:00 10:40 1 4:00 60:00 :20
t-anderson 18 1:40 18:00 4:20 :00 2 3:20 60:00 1:00
j-jacobsen 10 1:20 8:20 16:10 :00 0 :0 38:00 :10
----------- ----- ------ ------- ------- ------- ----- ----- -------- ------
SUMMARY 38 1:28 33:50 45:30 10:40 3 3:33 158:00 1:30
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-23Historical Reports
4
Screen 4-7. BCMS Agent Summary Report — Daily Summary
Header Definitions
Table 4-6. Agent Summary Report Header Definitions
Header Definition
Time/Day The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the earliest time interval (either hour or
half-hour). If no start time is given, the most recent time interval is the
default. A stop time requires an associated start time. If no stop time is
given, only the start interval/day is used. If no start time or stop time is
given, the most current interval/day is used. If you specify
day
in the
command and do not include a start day or stop day, the report displays
data for the current day accrued through the most recently completed
interval (hour or half-hour).
Agent Name The name of the agent. If no name is administered, the agent’s extension is
displayed in the form
EXT 65432.
ACD CALLS The number of ACD calls answered by this agent for all splits during the
reporting interval. This value includes calls that flowed in from other splits
and Direct Agent calls.
Continued on next page
list bcms sum agent 4222-4223 4869 day 5/14
BCMS AGENT SUMMARY REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Day: 5/14
AVG TOTAL TOTAL TOTAL AVG TOTAL TOTAL
ACD TALK AFTER AVAIL AUX/ EXTN EXTN TIME HOLD
AGENT NAME CALLS TIME CALL TIME OTHER CALLS TIME STAFFED TIME
s-jones 10 1:15 7:30 25:00 10:40 1 4:00 60:00 :20
t-anderson 18 1:40 18:00 4:20 :00 2 3:20 60:00 1:00
j-jacobsen 10 1:20 8:20 16:10 :00 0 :0 38:00 :10
----------- ----- ------ ------- ------- ------- ----- ----- -------- ------
SUMMARY 38 1:28 33:50 45:30 10:40 3 3:33 158:00 1:30
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-24Historical Reports
4
AVG TALK
TIME The average duration of ACD calls for all splits the agent was logged into.
This value includes time spent talking but does not include the amount of
time the agent was holding an ACD call or ring time at the agent’s
telephone. The calculation is:
TOTAL
AFTER CALL The total amount of time that the agent spent in call-related or
non-call-related ACW work states for all splits during the reporting interval.
This includes time agents spent on extension-in and extension-out calls
while in the ACW work mode. If an agent entered ACW in one interval, but
ended ACW in another interval, the appropriate amount of ACW time is
credited to each of the intervals.
TOTAL
AVAIL TIME The sum of the time that the agent was available to receive ACD calls
during the current interval. During this time, the agent:
■Was in Auto-In or Manual-In work mode for at least one split.
■Was not in ACW in any split.
■Was not on any call or placing any call (unless Multiple Call Handling
[MCH] is active).
■Did not have ringing calls.
Table 4-6. Agent Summary Report Header Definitions — Continued
Header Definition
Continued on next page
AVG TALK TIME Total ACD Talk Time
Total Number of ACD Calls Answered
----------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-25Historical Reports
4
TOTAL
AUX/OTHER The total time that each agent was unavailable to receive calls in any split
during the reporting interval.
A split totals AUX TIME whenever any agent is logged into the split and:
■Receives an EXTN call while in AUX or AVAIL state.
■Makes an EXTN call while in AUX or AVAIL state.
■Hits his/her AUX button.
Note that if the agent was in Other for all logged-in splits, that time is
reflected here. For example, ringing calls can cause several seconds of
AUX/OTHER time to accrue.
For the agent report, any non-ACD call time is also totaled in the AVG
EXTN TIME column. Two points of contrast are:
1. The measurement TOTAL AUX/OTHER is time-interval based, rather
than being call-related. For example, assuming that the previously
identified stipulations are met, then if the agent is in AUX from 9:55 to
10:05, 5 minutes is recorded in the 9:00 to 10:00 time interval and 5
minutes is recorded in the 10:00 to 11:00 time interval.
2. The measurement AVG EXTN TIME is call related. For example, if an
agent is on a non-ACD call from 9:55 to 10:05, the call and 10 minutes
of EXTN time is recorded in the 10:00 to 11:00 time interval.
Because the agent report includes some call-related items, the sum of all
items for a given hour may not exactly equal 60 minutes.
EXTN CALLS The total number of non-ACD incoming and outgoing calls for this agent
during the reporting interval. Only those non-ACD calls that are originated
and/or received while the agent is logged into at least one split are counted.
If an extension-in call is active for less than the time set for the Abandon
Call Timer, the call will not be counted in this field.
Table 4-6. Agent Summary Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-26Historical Reports
4
AVG EXTN
TIME The average amount of time that the agent spent on non-ACD calls while
logged into at least one split during the reporting interval. This average
does not include time when the agent was holding the EXTN call. The
calculation is:
If an extension-in call is active for less than the time set for the Abandon
Call Timer, the call will not be counted and the duration of the call will be
counted as AUX/OTHER time.
TOTAL TIME
STAFFED The total time that the agent spent logged into at least one split during the
reporting interval. Staff time is clocked for an agent who is in multiple splits
as long as the agent is logged into any split. Concurrent times for each split
are not totaled.
TOTAL HOLD
TIME The total time that the agent placed ACD calls on hold. This time is the
caller’s hold time
and is independent of the state of the agent. TOTAL
HOLD TIME does not include the hold time for non-ACD calls.
SUMMARY The total of each of the columns that do not contain averages. Columns
that do contain averages are the total time divided by the total number of
calls.
Table 4-6. Agent Summary Report Header Definitions — Continued
Header Definition
Continued on next page
AVG EXTN TIME Total Ext Time
Total Number of Ext Calls
--------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-27Historical Reports
4
BCMS Split Report
Command
Use one of the following commands to generate the BCMS Split report:
list bcms split (split number) [time] [start time] [stop time][print/schedule]
list bcms split (split number) [day] [start day] [stop day] [print/schedule]
Description
The BCMS Split report provides traffic information for the specified split number.
Depending on specifics from the command line, the information may be displayed
as either a time interval or a daily summary. If neither
time
nor
day
is specified,
time
is the default. In this case, the report displays data accrued for the
previous 24 time intervals (hour or half-hour), including data from the most
recently completed time interval. To get information on the current time interval,
you must use a monitor bcms command.
When analyzing this report, keep the following in mind:
■All averages are for completed calls only.
■A completed call may span more than one time interval. ACD calls that are
in process (have not terminated) are counted in the time interval in which
they terminate. For example, if an ACD call begins in the 10:00 to 11:00
time interval, but terminates in the 11:00 to 12:00 time interval, the data for
this call is counted in the 11:00 to 12:00 time interval.
■Asterisks within a field indicate that the maximum for that field has been
exceeded.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-28Historical Reports
4
Sample Reports
Screen 4-8. BCMS Split or Skill Report — Hourly
Screen 4-9. BCMS Split or Skill Report — Daily
* Acceptable service level changed.
Split is displayed as “Skill” when EAS is optioned (EAS and skills
are not supported with DEFINITY BCS and GuestWorks).
Split is displayed as “Skill” when EAS is optioned (EAS and skills
are not supported with DEFINITY BCS and GuestWorks).
list bcms split 3 time 8:00-10:00
BCMS SPLIT REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Split: 03
Split Name: services Acceptable Service Level: 17
AVG AVG AVG TOTAL TOTAL % IN
ACD SPEED ABAND ABAND TALK AFTER FLOW FLOW AUX/ AVG SERV
TIME CALLS ANS CALLS TIME TIME CALL IN OUT OTHER STAFF LEVL
8:00- 9:00 32 :25 4 :32 5:15 16:00 3 5 3:30 4.0 80*
9:00-10:0 8 :07 1 :03 3:20 :00 0 0 9:30 2.2 85
----------- ----- ----- ----- ----- ----- ------- ---- ---- ------ ----- ---
SUMMARY 40 :21 5 :26 4:52 :26 3 5 13:00 3.1 81
list bcms split 3 day 5/14/95
BCMS SPLIT REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Split: 03
Split Name: services Acceptable Service Level: 17
AVG AVG AVG TOTAL TOTAL % IN
ACD SPEED ABAND ABAND TALK AFTER FLOW FLOW AUX/ AVG SERV
DAY CALLS ANS CALLS TIME TIME CALL IN OUT OTHER STAFF LEVL
5/14/95 40 :21 5 :26 4:52 17:20 3 5 13:00 3.1 81
-------- ----- ----- ---- ----- ----- ------- ---- ---- ------- ----- ---
SUMMARY 40 :21 5 :26 4:52 17:20 3 5 13:00 3.1 81
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-29Historical Reports
4
Header Definitions
Table 4-7. Split Report Header Definitions
Header Definition
Split The split number specified with the command line.
Split Name Displays the name that is administered for this split number. If no name
exists, BCMS displays the split extension (for example, EXT 65432).
Acceptable
Service Level The desired time for an agent to answer a call for a given hunt group.
Timing for a call begins when the call enters the hunt group queue.
TIME/DAY The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the earliest time interval (either hour or
half-hour). If no start time is given, the oldest time interval is the default. A
stop time requires an associated start time. If no stop time is given, the
last completed time interval (hour or half-hour) is the default. If no start or
stop time is given, the report displays data accrued for the previous 24
time intervals. If you specify
day
in the command and do not include a
start day or stop day, the report displays data accrued for the previous 6
days and data accrued through the most recently completed interval
(hour or half-hour).
ACD CALLS The number of ACD calls completed for this split during the current
interval. This number also includes calls that flowed in from other splits
and Direct Agent (EAS only) calls.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-30Historical Reports
4
AVG SPEED
ANS The average amount of time answered ACD calls (split and Direct Agent)
spent in queue and ringing at an agent’s station before being answered
during the reporting interval. Calls that flowed in do not have queue time
from the previous split included in this average. This calculation is:
Keep the following things in mind:
■This value does not include time listening to a forced first
announcement.
■A completed call may span more than one time period. ACD calls
that are in process (have not terminated) are counted in the time
period in which they terminate. For example, if an ACD call begins
in the 10:00 to 11:00 time period, but terminates in the 11:00 to
12:00 time period, the data for this call is counted in the 11:00 to
12:00 time period.
ABAND
CALLS The total number of ACD calls that have hung up while waiting to be
answered during this time interval. This value includes those calls that
have abandoned while in queue or while ringing. Calls that are not
queued (because the queue is full, the caller receives a forced first
announcement and abandons during the announcement, or no agents
are staffed) are not counted as abandoned. Also, calls that abandon
while on hold are not counted as abandoned.
AVG ABAND
TIME The average time before an ACD call abandons. This value does not
include any time spent in another split’s queue before flowing into this
split. The calculation is:
This value does not include time listening to a forced first announcement
or calls that
abandon
while listening to a forced first announcement.
Table 4-7. Split Report Header Definitions — Continued
Header Definition
Continued on next page
AVG SPEED ANS =
Sum of Each Completed Call’s Time In Queue + Time Ringing
Total Number of ACD Calls Answered
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
AVG ABAND TIME Total Abandon Time
Total Number of Abandoned Calls
------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-31Historical Reports
4
AVG TALK
TIME The average amount of time agents are active on ACD calls (split and
direct agent) for each split. This includes time spent talking. The
calculation does not include ring time at an agent’s telephone or time
spent on hold. The calculation is:
TOTAL
AFTER CALL The amount of time that the agents in this split spent in call-related or
noncall-related ACW mode during the reporting interval. This value
includes time spent on direct incoming or outgoing calls while in ACW. If
an agent entered ACW in one interval, but left ACW in another interval,
each interval is credited with ACW time.
FLOW IN The total number of completed calls that this split received as a coverage
point (intraflowed) from another BCMS-measured split, or are call
forwarded (interflowed) to this split and completed during the reporting
interval. This total does not include calls that are interflowed from a
remote switch by means of the Look Ahead Interflow feature. FLOW INs
are recorded when a call ends.
Table 4-7. Split Report Header Definitions — Continued
Header Definition
Continued on next page
AVG TALK TIME Total ACD Talk Time
Total Number of ACD Calls Answered
----------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-32Historical Reports
4
FLOW OUT The total number of calls queued to this split that were:
■Successfully sent to the split’s coverage point after queuing for the
specified
don’t answer
interval. (This does not include calls that
went to coverage based on any other criterion.)
■Forwarded-out via call forwarding
■Forwarded-out via a route to station extension vector step
■Answered via the Call Pickup feature
■Forwarded-out via Look Ahead Interflow
■First queued to this split and then were answered by the second or
third split
■Were redirected back to this split or its coverage path due to
Redirect On No Answer timing
FLOW OUTs are recorded when a call ends.
In a multiple split-queuing environment, inflows and outflows become a
bit more complicated. Consider the following scenarios:
If a multiple queued call is answered in a nonprimary split (that is, a
second or third split), an outflow is recorded in the statistics for the first
split, and an inflow and an answer are recorded to the statistics for the
answering split. For example, suppose there are three splits numbered 1
through 3. A call comes in for split 1, but all agents are busy in this split.
The call then goes into queue for splits 2 and 3. An agent in split 3
answers the call. In this example, an outflow is recorded in the statistics
for split 1, and an inflow and an answer are recorded in the statistics for
split 3. A dequeued call is counted for split 2.
If the call is answered in the primary split, no inflows or outflows are
recorded for any split. Splits 2 and 3 record the call as dequeued.
If a call is queued to three splits (for example, splits 1, 2, and 3, with split
1 being the primary split), then encounters a
route-to command that
sends the call to another VDN, that queues to different splits (for
example, splits 4 and 5), an outflow is recorded in the statistics for split 1.
If the call is answered in split 4, an answer is recorded in the statistics for
split 4. However, no inflow is recorded to the statistics for split 4.
Table 4-7. Split Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-33Historical Reports
4
FLOW OUT
(cont.) If the call is answered in split 5, an outflow is recorded for the statistics for
split 4, and both an inflow and an answer are recorded in the statistics for
split 5.
Similarly, if a multiple queued call routes to another split, an outflow is
recorded to the statistics for the primary split, but no inflow is recorded to
the statistics for the routed-to split.
TOTAL
AUX/OTHER The total time that logged-in agents in this split were unavailable to
receive calls during the reporting interval. This value includes time spent
on non-ACD calls while in AUX for this split. This value does not include
the time agents spent on another split’s calls or in ACW for another split.
For example, a split totals AUX TIME whenever any agent logs into the
split and:
■Receives an EXTN call while in AUX or AVAIL state
■Makes an EXTN call while in AUX or AVAIL state
■Hits his/her AUX button
Furthermore, the split report measurement AUX TIME is time-interval
based, since it is not directly related to a call. For example, if an agent is
in AUX for any of the previously identified reasons from 9:55 to 10:05,
then 5 minutes is recorded in the 9:00 to 10:00 time interval and 5
minutes is recorded in the 10:00 to 11:00 time interval.
Table 4-7. Split Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-34Historical Reports
4
AVG STAFF The average number of agents who were logged into this split (staffed)
during the reporting interval.
% IN SERV
LEVL The percentage of calls answered within the administered service level.
where:
accepted is calls answered whose queue time was less than or equal to
the administered service level for the split
dequeued is a call that encountered the split’s queue, but that was NOT
answered, abandoned, or outflowed. This occurs with multiple split
queuing.
NOTE:
Not available with DEFINTY BCS and Guestworks.
SUMMARY For those columns that specify averages, the summary is an average for
the entire reporting interval. For the ACD CALLS, ABAND CALLS,
TOTAL AFTER CALL, FLOW IN, FLOW OUT, AUX TIME, and TOTAL
HOLD TIME columns, the summary is the sum of individual time intervals
or specified days.
Table 4-7. Split Report Header Definitions — Continued
Header Definition
Continued on next page
AVG STAFF Total Staff Time
Time Interval
------------------------------------------=
% IN SERV LEVL accepted * 100
ACDcalls + abandons + outflows + dequeued
------------------------------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-35Historical Reports
4
BCMS Split Summary Report
Command
Use one of the following commands to generate the BCMS Split Summary report:
list bcms summary split (split number) [time] [start time] [stop time]
[print/schedule]
list bcms summary split (split number) [day] [start day] [stop day]
[print/schedule]
Description
The BCMS Split Summary report provides traffic measurement information for a
specified group of BCMS splits. Depending on specifics from the command line,
the information may be displayed as either a time interval or daily summary. If
neither
time
nor
day
is specified,
time
is the default. In this case, the report
displays data accrued for the previous 24 time intervals (hour or half-hour),
including data from the most recently completed time interval. To get information
on the current time interval, you must use a monitor bcms command.
This report is similar to the Split Report except that this report provides one line of
data for each split, which includes all data for the specified times. A split does not
appear on the report if there is no data for that split. If you specify more than one
time period, and data exists for one or more, but not all, of the specified times, the
system uses the available data to calculate and display the one-line summary; the
system does not identify which times are not included in the calculations.
When analyzing this report, keep the following in mind:
■All averages are for completed calls only.
■Asterisks indicate that the maximum for the associated field has been
exceeded.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-36Historical Reports
4
Sample Reports
Screen 4-10. BCMS Split or Skill Summary Report — Hourly Summary
Screen 4-11. BCMS Split or Skill Summary Report — Daily Summary
Split is displayed as “Skill” when EAS is optioned (EAS and skills
are not supported with DEFINITY BCS and GuestWorks).
Split is displayed as “Skill” when EAS is optioned (EAS and skills are
not supported with DEFINITY BCS and GuestWorks).
list bcms summary split 5 3 time 9:00-16:00
BCMS SPLIT SUMMARY REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Time: 9:00-16:00
AVG AVG AVG TOTAL TOTAL % IN
ACD SPEED ABAND ABAND TALK AFTER FLOW FLOW AUX/ AVG SERV
SPLIT NAME CALLS ANS CALLS TIME TIME CALL IN OUT OTHER STAFF LEVL
Sales 32 :25 4 :32 5:15 16:00 3 5 3:30 4.0 75
Service 8 :07 1 :03 3:20 :00 0 0 9:30 2.2 83*
-------- ----- ----- ---- ----- ----- ------- ---- ---- ------- ----- ---
SUMMARY 40 :21 5 :26 4:52 16:00 3 5 13:00 3.1 76
list bcms summary split 5 3 day
BCMS SPLIT SUMMARY REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Day: 5/15/95
AVG AVG AVG TOTAL TOTAL % IN
ACD SPEED ABAND ABAND TALK AFTER FLOW FLOW AUX/ AVG SERV
SPLIT NAME CALLS ANS CALLS TIME TIME CALL IN OUT OTHER STAFF LEVL
Sales 32 :25 4 :32 5:15 16:00 3 5 3:30 4.0 75
Service 8 :07 1 :03 3:20 :00 0 0 9:30 2.2 83*
-------- ----- ----- ---- ----- ----- ------- ---- ---- ------- ----- ---
SUMMARY 40 :21 5 :26 4:52 16:00 3 5 13:00 3.1 76
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-37Historical Reports
4
Header Definitions
Table 4-8. Split Summary Report Header Definitions
Header Definition
TIME/DAY The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the earliest time interval (either hour or
half-hour). If no start time is given, the oldest time interval is the default. A
stop time requires an associated start time. If no stop time is given, the
last completed time interval (hour or half-hour) is the default. If no start or
stop time is given, the report displays data accrued for the previous 24
time intervals. If you specify
day
in the command and do not include a
start day or stop day, the report displays data accrued for the previous 6
days and data accrued through the most recently completed interval
(hour or half-hour).
Split Name Displays the name that is administered for this split number. If no name
exists, BCMS displays the split extension (for example, EXT 65432).
ACD CALLS The number of ACD calls completed for this split during the current
interval. This number also includes calls that flowed in from other splits
and Direct Agent calls.
AVG SPEED
ANS The average amount of time answered ACD calls (split and Direct Agent)
spent in queue and ringing at an agent’s station before being answered
during the reporting interval. Calls that flowed in do not have queue time
from the previous split included in this average. This calculation is:
Keep the following in mind:
■This value does not include time listening to a forced first
announcement.
■Asterisks indicate that the maximum for the associated field has
been exceeded.
Continued on next page
AVG SPEED ANS =
Sum of Each Completed Call's Time In Queue + Time Ringing
Total Number of ACD Calls Answered
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-38Historical Reports
4
ABAND
CALLS The total number of ACD calls that have hung up while waiting to be
answered during this time interval. This value includes those calls that
have abandoned while in queue or while ringing. It also includes calls with
a talk time that is less than the value administered for the BCMS/VuStats
Abandon Call Timer. Calls that are not queued (because the queue is full,
the caller receives a forced first announcement and abandons during the
announcement, or no agents are staffed) are not counted as abandoned.
Also, calls that abandon while on hold are not counted as abandoned.
AVG ABAND
TIME The average time before an ACD call abandons. This value does not
include any time spent in another split’s queue before flowing into this
split. The calculation is:
This value does not include time listening to a forced first announcement
or calls that
abandon
while listening to a forced first announcement.
AVG TALK
TIME The average duration of ACD calls (split and direct agent) for each split.
This includes time spent talking. The calculation does not include ring
time at an agent’s telephone or time spent on hold. The calculation is:
TOTAL
AFTER CALL The amount of time that the agents in this split spent in call-related or
noncall-related ACW mode during the reporting interval. This value
includes time spent on direct incoming or outgoing calls while in ACW. If
an agent entered ACW in one interval, but left ACW in another interval,
each interval is credited with ACW time.
FLOW IN The total number of completed calls that this split received as a coverage
point (intraflowed) from another BCMS-measured split, or are call
forwarded (interflowed) to this split and completed during the reporting
interval. This total does not include calls that are interflowed from a
remote switch by means of the Look Ahead Interflow feature. FLOW INs
are recorded as they occur.
Table 4-8. Split Summary Report Header Definitions — Continued
Header Definition
Continued on next page
AVG ABAND TIME Total Abandon Time
Total Number of Abandoned Calls
------------------------------------------------------------------------------------------=
AVG TALK TIME Total ACD Talk Time
Total Number of ACD Calls Answered
----------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-39Historical Reports
4
FLOW OUT The total number of calls queued to this split that were:
■Successfully sent to the split’s coverage point after queuing for the
specified
don’t answer
interval. (This does not include calls that
went to coverage based on any other criterion.)
■Forwarded-out via call forwarding
■Forwarded-out via a route to station extension vector step
■Answered via the Call Pickup feature
■Forwarded-out via Look Ahead Interflow
■First queued to this split and then were answered by the second or
third split
■Were redirected back to this split or its coverage path due to
Redirect On No Answer timing
FLOW OUTs are recorded when a call ends.
In a multiple split-queuing environment, inflows and outflows become a
bit more complicated. Consider the following scenarios:
If a multiple queued call is answered in a nonprimary split (that is, a
second or third split), an outflow is recorded in the statistics for the first
split, and an inflow and an answer are recorded to the statistics for the
answering split. For example, suppose there are three splits numbered 1
through 3. A call comes in for split 1, but all agents are busy in this split.
The call then goes into queue for splits 2 and 3. An agent in split 3
answers the call. In this example, an outflow is recorded in the statistics
for split 1, and an inflow and an answer are recorded in the statistics for
split 3. A dequeued call is counted for split 2.
If the call is answered in the primary split, no inflows or outflows are
recorded for any split. Splits 2 and 3 record the call as dequeued.
If a call is queued to three splits (for example, splits 1, 2, and 3, with split
1 being the primary split), then encounters a
route-to
command that
sends the call to another VDN, that queues to different splits (for
example, splits 4 and 5), an outflow is recorded in the statistics for split 1.
If the call is answered in split 4, an answer is recorded in the statistics for
split 4. However, no inflow is recorded to the statistics for split 4.
Table 4-8. Split Summary Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-40Historical Reports
4
FLOW OUT
(cont.) If the call is answered in split 5, an outflow is recorded for the statistics for
split 4, and both an inflow and an answer are recorded in the statistics for
split 5.
Similarly, if a multiple queued call routes to another split, an outflow is
recorded to the statistics for the primary split, but no inflow is recorded to
the statistics for the routed-to split.
TOTAL
AUX/OTHER The total time that logged-in agents in this split were unavailable to
receive calls during the reporting interval. This value includes time spent
on non-ACD calls while in AUX for this split. This value does not include
the time agents spent on another split’s calls or in ACW for another split.
For example, a split totals AUX TIME whenever any agent is logged into
the split and:
■Receives an EXTN call while in AUX or AVAIL state
■Makes an EXTN call while in AUX or AVAIL state
■Hits his/her AUX button
Furthermore, the split report measurement AUX TIME is time-interval
based, since it is not directly related to a call. For example, if an agent is
in AUX for any of the previously identified reasons from 9:55 to 10:05,
then 5 minutes is recorded in the 9:00 to 10:00 time interval and 5
minutes is recorded in the 10:00 to 11:00 time interval.
Table 4-8. Split Summary Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-41Historical Reports
4
AVG STAFF The average number of agents who were logged into this split (staffed)
during the reporting interval.
% IN SERV
LEVL The percentage of calls answered within the administered service level.
where:
accepted is calls answered whose queue time was less than or equal to
the administered service level for the split
dequeued is a call that encountered the split’s queue, but that was NOT
answered, abandoned, or outflowed. This occurs with multiple split
queuing.
NOTE:
Not available with DEFINTY BCS and Guestworks.
SUMMARY For those columns that specify averages, the summary is an average for
the entire reporting interval. For the ACD CALLS, ABAND CALLS,
TOTAL AFTER CALL, FLOW IN, FLOW OUT, AUX TIME, and TOTAL
HOLD TIME columns, the summary is the sum of individual time intervals
or specified days.
Table 4-8. Split Summary Report Header Definitions — Continued
Header Definition
Continued on next page
AVG STAFF Total Staff Time
Time Interval
------------------------------------------=
% IN SERV LEVL accepted * 100
ACDcalls + abandons + outflows + dequeued
------------------------------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-42Historical Reports
4
BCMS Trunk Group Report
Command
Use one of the following commands to generate the BCMS Trunk Group report:
list bcms trunk (group number) [time] [start time] [stop time][print/schedule]
list bcms trunk (group number) [day] [start day] [stop day] [print/schedule]
Description
The BCMS Trunk Group report gives statistical information for all BCMS
measured trunk groups. The BCMS Trunk Group report may be used by the ACD
administrator and/or manager to monitor use of the trunk group and to determine
the optimal number of trunks for the trunk group. Depending on specifics from the
command line, the information may be displayed as either a time interval or a daily
summary. If neither
time
nor
day
is specified,
time
is the default. In this case, the
report displays data accrued for the previous 24 time intervals (hour or half-hour),
including data from the most recently completed time interval.
When analyzing this report, keep the following in mind:
■All averages are for completed calls only.
■A completed call may span more than one time interval. ACD calls
that are in process (have not terminated) are counted in the time
interval in which they terminate. For example, if an ACD call begins
in the 10:00 to 11:00 time interval, but terminates in the 11:00
to 12:00 time interval, the data for this call is counted in the 11:00
to 12:00 time interval.
■Asterisks in a field indicate that the maximum for that field has been
exceeded.
■A single asterisk at the end of a time or date field indicates that
during the interval, trunk group administration occurred which
changed the number of trunks.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-43Historical Reports
4
Sample Reports
Screen 4-12. BCMS Trunk Group Time Interval Report
Screen 4-13. BCMS Trunk Group Daily Report
list bcms trunk 1 time 8:00 11:00
BCMS TRUNK GROUP REPORT
Switch Name: Lab Model Date: 12:59 pm THU APR 20, 1995
Group: 1
Group Name: TG 1 Number of Trunks: 11
| INCOMING | OUTGOING |%ALL %TIME
TIME |CALLS ABAND TIME CCS | CALLS COMP TIME CCS|BUSY MAINT
8:00- 9:00* 23 2 2:15 31.02 1 1 1:36 .96 0 0
9:00-10:00 35 2 1:48 35.74 4 4 1:42 4.08 0 0
10:00-11:00 24 1 1:40 22.93 0 0 :00 .00 0 0
----------- ----- ---- ------ -------- ----- ---- ------ ------ --- ---
SUMMARY 82 5 1:54 29.89 5 5 1:39 2.52 0 0
list bcms trunk 1 day 4/17
BCMS TRUNK GROUP REPORT
Switch Name: Lab Model Date: 12:59 pm THU APR 20, 1995
Group: 1
Group Name: TG 1 Number of Trunks: 11
| INCOMING | OUTGOING |%ALL %TIME
DAY |CALLS ABAND TIME CCS | CALLS COMP TIME CCS|BUSY MAINT
4/17/95* 82 5 1:54 29.89 5 5 1:39 2.52 0 0
----------- ----- ---- ------ -------- ----- ---- ------ ------ --- ---
SUMMARY 82 5 1:54 29.89 5 5 1:39 2.52 0 0
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-44Historical Reports
4
Header Definitions
Table 4-9. Trunk Group Report Header Definitions
Header Definition
Group The trunk group number specified with the command line.
Group Name The name that is administered for this trunk group. If no name is
administered, then this field is displayed as blank.
Number of
Trunks The number of individual trunks in the trunk group at the end of the first
interval being reported.
TIME/DAY The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the top of the time interval (either hour or
half-hour). If no start time is given, the report displays data accrued for
the previous 24 time intervals. A stop time requires an associated start
time. If no stop time is given, the last completed time interval (hour or
half-hour) is the default. If no start time or stop time is given, the report
displays data accrued for the previous 24 time intervals. If you specify
day
in the command and do not include a start day or stop day, the report
displays data accrued for the previous six days and data accrued through
the most recently completed interval (hour or half-hour).
If switch administration causes the number of trunks in a
BCMS-measured trunk group to change during a day or a time interval,
an asterisk appears in the
DAY/TIME
field.
INCOMING
CALLS The total number of incoming calls carried by this trunk group.
INCOMING
ABAND The number of incoming calls that queued to ACD splits, then abandoned
(without being answered by a staffed agent within this split) during the
reporting interval. It also includes calls with a talk time that is less than the
value administered for the BCMS/VuStats Abandon Call Timer (not
supported with the DEFINITY BCS and GuestWorks offer). Calls that
cannot queue (for example, queue full, or calls that receive a busy signal
from the Central Office because there aren’t any available trunks) are not
included in the INCOMING ABAND number. Also included are calls
directly to staffed ACD agents that are unanswered.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-45Historical Reports
4
INCOMING
TIME The average holding time for incoming calls to this trunk group during the
specified reporting interval. Holding time is defined as the length of time
in minutes and seconds that a facility is used during a call. The
calculation for incoming time is:
INCOMING
CCS The total holding time (usage) for incoming calls to the trunk group during
the specified reporting interval. The units are expressed in hundred call
seconds (CCS).
OUTGOING
CALLS The total number of outgoing calls for this trunk group during the specified
reporting interval.
OUTGOING
COMP The total number of outgoing calls that were placed over this trunk group
and answered during the specified reporting interval.
Completion is determined by either return of network answer supervision,
or a call that lasts longer than the answer supervision time-out parameter;
whichever occurs first.
OUTGOING
TIME The average holding time for outgoing calls during the specified reporting
interval. The calculation is:
Table 4-9. Trunk Group Report Header Definitions — Continued
Header Definition
Continued on next page
INCOMING TIME Total Holding Time for all Incoming Calls
Total Number of Incoming Calls
-----------------------------------------------------------------------------------------------------------=
OUTGOING TIME Total Holding Time for Outgoing Calls
Total Number of Outgoing Calls
----------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-46Historical Reports
4
OUTGOING
CCS The total holding time (usage) for outgoing calls from this trunk group.
The units are expressed in CCS.
% ALL BUSY The percentage of time that all the trunks in this trunk group were busy.
This value includes trunks that are maintenance busy. The calculation is:
where Busy Times is expressed in minutes and is the sum of all times
when all trunks were simultaneously busy.
% TIME
MAINT The percentage of time that one or more trunks have been busied-out for
maintenance purposes. The calculation is:
where:
■Total Maintenance Busy Time is the sum of Maintenance Busy
Time (in minutes) for all trunks (individually) in this trunk group
during this interval
■Time Interval is expressed in minutes (for example,
30
if using a
half-hour interval,
60
if using a one-hour interval, and
1440
if using
a daily summary)
For reporting purposes, call data is stored during the time interval
(hour or half-hour) that the trunk goes idle, not when the station
releases. Also, changing the number of trunks in a trunk group can
cause unexpected results for that interval.
Table 4-9. Trunk Group Report Header Definitions — Continued
Header Definition
Continued on next page
% ALL BUSY Total of all Busy Times
Time Interval
------------------------------------------------------------ X100()=
% TIME MAINTENANCE Total Maintenance Busy Time x 100
Time Interval x Number of Trunks in Group
-----------------------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-47Historical Reports
4
BCMS Trunk Group Summary Report
Command
Use one of the following commands to generate the BCMS Trunk Group
Summary report:
list bcms summary trunk (group number) [time] [start time] [stop
time][print/schedule]
list bcms summary trunk (group number) [day] [start day] [stop day]
[print/schedule]
Description
The BCMS Trunk Group Summary report provides information about
BCMS-measured trunk groups. You can specify the trunk groups you want
included in the report. The BCMS Trunk Group report can be used by the ACD
administrator and/or manager to monitor use of one or more trunk groups and to
determine the optimal number of trunks for the trunk groups. Note that this applies
only to trunk groups measured by BCMS.
This report is similar to the BCMS Trunk Group report except that the information
for a trunk group appears on separate lines of the report, with totals of activity for
all trunks in the trunk group for the specified time. You can print the report for a
certain time period specified in either hours or days (up to 7 days).
The report displays only the information that exists and does not identify absent
data. If data does not exist for a specified trunk group, the trunk group does not
appear on the report. Also, if information does not exist for a portion of the
specified time period, the report displays all existing information but does not
identify where there is no data.
When analyzing this report, keep the following in mind:
■All averages are for completed calls only.
■Asterisks in a field indicate that the maximum for that field is
exceeded.
■A single asterisk at the end of a time or date field indicates that
during the interval, trunk group administration occurred which
changed the number of trunks.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-48Historical Reports
4
Sample Reports
Screen 4-14. BCMS Trunk Group Summary Report — Hourly
Screen 4-15. BCMS Trunk Group Summary Report — Daily
list bcms trunk sum 23-25 time 8:00
BCMS TRUNK GROUP SUMMARY REPORT
Switch Name: Lab Model Date: 12:59 pm THU APR 20, 1995
Time: 8:00-13:00
| INCOMING | OUTGOING |%ALL %TIME
GROUP NAME |CALLS ABAND TIME CCS | CALLS COMP TIME CCS|BUSY MAINT
IN-800 23 2 2:15 31.02 1 1 1:36 0.96 0 0
OUT-WATTS* 35 2 1:48 35.74 4 4 1:42 4.08 0 0
TIE-GROUP 24 1 1:40 22.93 0 0 :00 0.00 0 0
----------- ----- ---- ------ -------- ----- ----- ------ ------ --- ---
SUMMARY 82 5 1:54 29.89 5 5 1:39 2.52 0 0
list bcms trunk sum 23 day 5/17/92
BCMS TRUNK GROUP SUMMARY REPORT
Switch Name: Lab Model Date: 12:59 pm THU APR 20, 1995
Day: 5/17/95
| INCOMING | OUTGOING |%ALL %TIME
GROUP NAME |CALLS ABAND TIME CCS | CALLS COMP TIME CCS|BUSY MAINT
IN-800* 82 5 1:54 29.89 5 5 1:39 2.52 0 0
----------- ----- ---- ------ -------- ----- ----- ------ ------ --- ---
SUMMARY 82 5 1:54 29.89 5 5 1:39 2.52 0 0
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-49Historical Reports
4
Header Definitions
Table 4-10. Trunk Group Summary Report Header Definitions
Header Definition
TIME/DAY The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the top of the time interval (either hour or
half-hour). If no start time is given, the report displays data accrued for
the previous 24 time intervals. A stop time requires an associated start
time. If no stop time is given, the last completed time interval (hour or
half-hour) is the default. If no start time or stop time is given, the report
displays data accrued for the previous 24 time intervals. If you specify
day
in the command and do not include a start day or stop day, the report
displays data accrued for the previous six days and data accrued through
the most recently completed interval (hour or half-hour).
If switch administration causes the number of trunks in a
BCMS-measured trunk group to change during a day or a time interval,
an asterisk appears in the
DAY/TIME
field.
Group Name The name that is administered for this trunk group. If no name is
administered, then this field is displayed as blank.
INCOMING
CALLS The total number of incoming calls carried by this trunk group.
INCOMING
ABAND The number of incoming calls that queued to ACD splits, then abandoned
(without being answered by a staffed agent within this split) during the
reporting interval. Calls that cannot queue (for example, queue full, or
calls that receive a busy signal from the Central Office because there are
no available trunks) are not included in the INCOMING ABAND number.
Also included are calls directly to staffed ACD agents that are
unanswered.
INCOMING
TIME The average holding time for incoming calls to this trunk group during the
specified reporting interval. Holding time is defined as the length of time
in minutes and seconds that a facility is used during a call. The
calculation for incoming time is:
Continued on next page
INCOMING TIME Total Holding Time for all Incoming Calls
Total Number of Incoming Calls
-----------------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-50Historical Reports
4
INCOMING
CCS The total holding time (usage) for incoming calls to the trunk group during
the specified reporting interval. The units are expressed in hundred call
seconds (CCS).
OUTGOING
CALLS The total number of outgoing calls for this trunk group during the
specified reporting interval.
OUTGOING
COMP The total number of outgoing calls that were placed over this trunk group
and answered during the specified reporting interval.
Completion is determined by either return of network answer supervision,
or a call that lasts longer than the answer supervision time-out parameter;
whichever occurs first.
OUTGOING
TIME The average holding time for outgoing calls during the specified reporting
interval. The calculation is:
Table 4-10. Trunk Group Summary Report Header Definitions — Continued
Header Definition
Continued on next page
OUTGOING TIME Total Holding Time for Outgoing Calls
Total Number of Outgoing Calls
----------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-51Historical Reports
4
OUTGOING
CCS The total holding time (usage) for outgoing calls from this trunk group.
The units are expressed in CCS.
% ALL BUSY The percentage of time that all the trunks in this trunk group were busy.
This value includes trunks that are maintenance busy. The calculation is:
where Busy Times is expressed in minutes and is the sum of all times
when all trunks were simultaneously busy.
% TIME
MAINT The percentage of time that one or more trunks have been busied-out for
maintenance purposes. The calculation is:
where:
■Total Maintenance Busy Time is the sum of Maintenance Busy
Time (in minutes) for all trunks (individually) in this trunk group
during this interval
■Time Interval is expressed in minutes (for example,
30
if using a
half-hour interval,
60
if using a one-hour interval, and
1440
if using
a daily summary)
For reporting purposes, call data is stored during the time interval
(hour or half-hour) that the trunk goes idle, not when the station
releases. Also, changing the number of trunks in a trunk group can
cause unexpected results for that interval.
Table 4-10. Trunk Group Summary Report Header Definitions — Continued
Header Definition
Continued on next page
% ALL BUSY Total of all Busy Times
Time Interval
------------------------------------------------------------ X100()=
% TIME MAINTENANCE Total Maintenance Busy Time x 100
Time Interval x Number of Trunks in Group
-----------------------------------------------------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-52Historical Reports
4
BCMS VDN Report
Command
Use one of the following commands to generate the BCMS VDN report:
list bcms vdn extension [time] [start time] [stop time][print/schedule]
list bcms vdn extension [day] [start day] [stop day] [print/schedule]
Description
The BCMS VDN report provides statistical information for the specified VDN.
Depending on specifics from the command line, the information may be displayed
as either a time interval or a daily summary. If neither
time
nor
day
is specified,
time
is the default. In this case, the report displays data accrued for the
previous 24 time intervals (hour or half-hour), including data from the most
recently completed interval.
When analyzing this report, keep the following in mind:
■All averages are for completed calls only.
■A completed call may span more than one time period. ACD calls
that are in process (have not terminated) are counted in the time
period in which they terminate. For example, if an ACD call begins in
the 10:00 to 11:00 time period, but terminates in the 11:00 to 12:00
time period, the data for this call is counted in the 11:00 to 12:00
time period.
■Asterisks indicate that the maximum for the associated field has
been exceeded.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-53Historical Reports
4
Sample Reports
Screen 4-16. BCMS VDN Report — Hourly
Screen 4-17. BCMS VDN Report — Daily
list bcms vdn 12345 time 8:00 12:00
BCMS VECTOR DIRECTORY NUMBER REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
VDN: 12345
VDN Name: Ginsu Knives Acceptable Service Level: 17
AVG AVG AVG CALLS % IN
CALLS ACD SPEED ABAND ABAND TALK/ CONN FLOW BUSY/ SERV
TIME OFFERED CALLS ANSW CALLS TIME HOLD CALLS OUT DISC LEVL
08:00-09:00 79 50 :39 5 :45 2:30 0 0 24 85*
----------- ----- ----- ----- ----- ----- ----- ----- ---- ---- ---
SUMMARY 79 50 :39 5 :45 2:30 0 0 24 85
list bcms vdn 12345 day 5/14
BCMS VECTOR DIRECTORY NUMBER REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
VDN: 12345
VDN Name: Ginsu Knives Acceptable Service Level: 17
AVG AVG AVG CALLS % IN
CALLS ACD SPEED ABAND ABAND TALK/ CONN FLOW BUSY/ SERV
DAY OFFERED CALLS ANSW CALLS TIME HOLD CALLS OUT DISC LEVL
5/14/95 79 50 :39 5 :45 2:30 0 0 24 85*
----------- ----- ----- ----- ----- ----- ----- ----- ---- ---- ---
SUMMARY 79 50 :39 5 :45 2:30 0 0 24 85
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-54Historical Reports
4
Header Definition
Table 4-11. VDN Report Header Definitions
Header Definition
VDN The VDN specified with the command line.
VDN Name The name that is administered for this VDN. If no name exists, the VDN
extension (for example EXT 64532) is displayed.
Acceptable
Service Level The desired time to answer calls to the VDN. Timing for a call begins
when the VDN is encountered.
TIME/DAY The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the top of the time interval (either hour or
half-hour). If no start time is given, the report displays data accrued for
the previous 24 time intervals. A stop time requires an associated start
time. If no stop time is given, the last completed time interval (hour or
half-hour) is the default. If no start time or stop time is given, the report
displays data accrued for the previous 24 time intervals. If you specify
day
in the command and do not include a start day or stop day, the report
displays data accrued for the previous 6 days and data accrued through
the most recently completed interval (hour or half-hour).
CALLS
OFFERED The total number of completed calls that accessed the VDN during the
current interval. This calculation is:
CALLS OFFERED=
ACD CALLS + FLOW OUT + CALLS BUSY/DISC + ABAND CALLS
ACD CALLS The total number of calls to the VDN that ended in the specified interval
and were answered by an agent in a BCMS-measured hunt group. ACD
calls include calls that reached the split via the queue-to-main, check
backup, route-to, messaging split, or adjunct routing commands.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-55Historical Reports
4
AVG SPEED
ANS The average speed of answer for answered ACD and CONNect calls that
have ended for this VDN during the current period. This includes time in
vector processing, time in a split’s queue, and time ringing. This
calculation is:
A completed call can span more than one time period. ACD calls that are
in process (have not terminated) are counted in the time period in which
they terminate. For example, if an ACD call begins in the 10:00 to 11:00
time period, but terminates in the 11:00 to 12:00 time period, the data for
this call is counted in the 11:00 to 12:00 time period.
ABAND
CALLS The total number of calls that have abandoned from the VDN before
being answered or outflowed to another position during the current
interval. This value includes calls that abandoned while in vector
processing or while ringing an agent. It also includes calls with a talk time
that is less than the value administered for the BCMS/VuStats Abandon
Call Timer (not supported with the DEFINITY BCS and GuestWorks offer.
AVG ABAND
TIME The average time calls spent waiting in this VDN before being abandoned
by the caller during the current interval. The calculation is:
AVG
TALK/HOLD
TIME
The average duration of calls (from answer to disconnect) for this VDN
during the current interval. This includes time spent talking and on hold.
The calculation does not include ring time at an agent’s telephone. The
calculation is:
CONN CALLS The number of completed calls that were routed to a station, attendant,
announcement, messaging skill, or call pickup and were answered there.
Table 4-11. VDN Report Header Definitions — Continued
Header Definition
Continued on next page
AVG SPEED ANS Total Answer Time
Total ACD Calls + Total CONNect CALLS
--------------------------------------------------------------------------------------------------------------=
AVG ABAND TIME Total VDN Abandon Time
Total Number of Abandoned VDN Calls
--------------------------------------------------------------------------------------------------------=
AVG TALK TIME Total VDN Talk/Hold Time
NUM ANS
---------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-56Historical Reports
4
FLOW OUT The total number of completed calls that were routed to another VDN or
to a trunk, including successful lookahead attempts.
FLOW OUT does not include calls that encounter a
goto vector
command.
Once a call outflows, the system does not take further measurements on
the call for this VDN. As a result, if an outflowed call later abandons, it is
not recorded in ABAND CALLS for this VDN.
CALLS
BUSY/DISC The total number of calls that were forced busy or forced disconnect
during the current interval. This value includes:
■calls that encountered a busy or disconnect vector step
■calls disconnected by a stop vector step
■calls forwarded to a split or skill with a full queue
■calls forwarded to a split or skill with no available agents and no
queue
This value does not include abandoned calls.
Table 4-11. VDN Report Header Definitions — Continued
Header Definition
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-57Historical Reports
4
% IN SERV
LEVL The percentage of calls that were answered with the administered service
level for this VDN. Calculate as the following:
where
accepted is the number of answered calls whose answer time was less
than or equal to the administered service level for the VDN.
calls offered is the total number of completed calls that accessed the
VDN and completed during the current interval.
This field is blank if no calls have been recorded for this time interval. This
field is also blank if no
Acceptable Service Level
is administered on the
VDN form.
NOTE:
Not available with DEFINTY BCS and Guestworks.
SUMMARY For those columns that specify averages, the summary is also an
average for the entire reporting interval. For the TOTAL ATTEMPTS,
ACD CALLS, ABAND CALLS, FLOW OUT, and OTHER CALLS columns,
the summary is the sum of individual time intervals or specified days.
Table 4-11. VDN Report Header Definitions — Continued
Header Definition
Continued on next page
% IN SERV LEVL accepted * 100
calls offered
----------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-58Historical Reports
4
BCMS VDN Summary Report
Command
Use one of the following commands to generate the BCMS VDN Summary report:
list bcms summary vdn extension [time] [start time] [stop time]
[print/schedule]
list bcms summary vdn extension [day] [start day] [stop day]
[print/schedule]
Description
This report is similar to the VDN report except that it provides one line of data for
each VDN included in the report, and the one line includes all data for the
specified times. If no data exists for a VDN, the VDN does not appear on the
report.
Sample Reports
Screen 4-18. BCMS VDN Summary Report — Hourly Summary
list bcms summary vdn 12345, 13443-13448 time 8:00-12:00
BCMS VECTOR DIRECTORY NUMBER SUMMARY REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Time: 8:00-12:00
AVG AVG AVG CALLS % IN
CALLS ACD SPEED ABAND ABAND TALK/ CONN FLOW BUSY/ SERV
VDN NAME OFFERED CALLS ANSW CALLS TIME HOLD CALLS OUT DISC LEVL
EXT 13443 0 0 :00 0 :00 :00 0 0 0
EXT 13444 0 0 :00 0 :00 :00 0 0 0
EXT 13445 0 0 :00 0 :00 :00 0 0 0
EXT 13446 0 0 :00 0 :00 :00 0 0 0
EXT 13447 0 0 :00 0 :00 :00 0 0 0
EXT 13448 0 0 :00 0 :00 :00 0 0 0
Ginsu Knive 79 50 :39 5 :45 2:30 0 0 24 85*
----------- ----- ----- ----- ---- ----- ----- ----- ---- ---- ---
SUMMARY 79 50 :39 5 :45 2:30 0 0 24 85
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-59Historical Reports
4
Screen 4-19. BCMS VDN Summary Report — Daily Summary
Header Definitions
Table 4-12. VDN Summary Report Header Definitions
Header Definition
TIME/DAY The time or day interval specified in the command line.
Time is always expressed in 24-hour format. Start and stop times are
optional. Reports always start at the top of the time interval (either hour or
half-hour). If no start time is given, the report displays data accrued for
the previous 24 time intervals. A stop time requires an associated start
time. If no stop time is given, the last completed time interval (hour or
half-hour) is the default. If no start time or stop time is given, the report
displays data accrued for the previous 24 time intervals. If you specify
day
in the command and do not include a start day or stop day, the report
displays data accrued for the previous 6 days and data accrued through
the most recently completed interval (hour or half-hour).
VDN Name The name that is administered for this VDN. If no name exists, the VDN
extension (for example EXT 64532) is displayed.
CALLS
OFFERED The total number of completed calls that accessed the VDN during the
current interval. This calculation is:
CALLS OFFERED=
ACD CALLS + FLOW OUT + OTHER CALLS + ABAND CALLS
ACD CALLS The total number of calls to the VDN that ended in the specified interval
and were answered by an agent as a result of a
queue-to-main or
check-backup split
step.
Continued on next page
list bcms summary vdn 12345 day 5/14
BCMS VECTOR DIRECTORY NUMBER SUMMARY REPORT
Switch Name: Lab Model Date: 11:05 am MON MAY 15, 1995
Day: 5/14/95
AVG AVG AVG CALLS % IN
CALLS ACD SPEED ABAND ABAND TALK/ CONN FLOW BUSY/ SERV
VDN NAME OFFERED CALLS ANSW CALLS TIME HOLD CALLS OUT DISC LEVL
Ginsu Knives 79 50 :39 5 :45 2:30 0 0 24 85*
----------- ----- ----- ----- ---- ----- ----- ----- ---- ---- ---
SUMMARY 79 50 :39 5 :45 2:30 0 0 24 85
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-60Historical Reports
4
AVG SPEED
ANS The average speed of answer for answered ACD and CONNect calls that
have ended for this VDN during the current period. This includes time in
vector processing, time in a split’s queue, and time ringing. This
calculation is:
A completed call can span more than one time period. ACD calls that are
in process (have not terminated) are counted in the time period in which
they terminate. For example, if an ACD call begins in the 10:00 to 11:00
time period, but terminates in the 11:00 to 12:00 time period, the data for
this call is counted in the 11:00 to 12:00 time period.
ABAND
CALLS The total number of calls that have abandoned from the VDN before
being answered or outflowed to another position during the current
interval. This value includes calls that abandoned while in vector
processing or while ringing an agent. Calls that abandoned immediately
after the agent answered are recorded as ACD CALLS.
AVG ABAND
TIME The average time calls spent waiting in this VDN before being abandoned
by the caller during the current interval. The calculation is:
AVG
TALK/HOLD
TIME
The average duration of calls (from answer to disconnect) for this VDN
during the current interval. This includes time spent talking and on hold.
The calculation does not include ring time at an agent’s telephone. The
calculation is:
CONN CALLS The number of completed calls that were routed to a station, attendant,
announcement, messaging skill, or call pickup and were answered there.
Table 4-12. VDN Summary Report Header Definitions — Continued
Header Definition
Continued on next page
AVG SPEED ANS Total Answer Time
Total ACD Calls + Total CONNect CALLS
--------------------------------------------------------------------------------------------------------------=
AVG ABAND TIME Total VDN Abandon Time
Total Number of Abandoned VDN Calls
--------------------------------------------------------------------------------------------------------=
AVG TALK TIME Total VDN Talk/Hold Time
NUM ANS
---------------------------------------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-61Historical Reports
4
FLOW OUT The total number of completed calls that were routed to another VDN or
to a trunk.
FLOW OUT does not include calls that encounter a
goto vector
command
or calls that forward to another extension (which are tracked as
CONNected CALLS).
Once a call outflows, the system does not take further measurements on
the call for this VDN. As a result, if an outflowed call later abandons, it is
not recorded in ABAND CALLS for this VDN.
CALLS
BUSY/DISC The total number of calls that were forced busy or forced disconnect
during the current interval. This value includes:
■calls that encountered a busy or disconnect vector step
■calls disconnected by a stop vector step
■calls forwarded to a split or skill with a full queue
■calls forwarded to a split or skill with no available agents and no
queue.
This value does not include abandoned calls.
% IN SERV
LEVL The percentage of calls that were answered with the administered service
level for this VDN. Calculate as the following:
where
accepted is the number of answered calls whose answer time was less
than or equal to the administered service level for the VDN.
calls offered is the total number of completed calls that accessed the
VDN and completed during the current interval.
NOTE:
Not available with DEFINTY BCS and Guestworks.
SUMMARY For those columns that specify averages, the summary is also an
average for the entire reporting interval. For the TOTAL ATTEMPTS,
ACD CALLS, ABAND CALLS, FLOW OUT, and OTHER CALLS columns,
the summary is the sum of individual time intervals or specified days.
Table 4-12. VDN Summary Report Header Definitions — Continued
Header Definition
Continued on next page
% IN SERV LEVL accepted * 100
calls offered
----------------------------------------=
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS Report Reference
4-62Historical Reports
4
System Printer and Report Scheduler
5-1Overview
5
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
5
System Printer and Report Scheduler
Overview
The Report Scheduler is enabled on the System-Parameters Features form. Only
an authorized Lucent Technologies representative can access and make changes
to the System-Parameters Customer-Options form. The parameters of the system
printer, which are used by the Report Scheduler feature, are administered on the
Feature-Related System Parameters form. If the parameters for the system
printer are not administered, scheduled reports cannot be printed. The system
administrator login may access this screen by entering the change
system-parameters features command. This command and the requirements
for using the Feature-Related System Parameters to set up the Report Scheduler
are covered in this chapter.
System Printer
The system printer, rather than the printer that is attached directly to the
Management Terminal is used to print scheduled reports. Scheduled reports
cannot be sent to the Management Terminal or to its printer.
NOTE:
The system printer should not be confused with and does not replace the
journal, Call Detail Records (CDR), or Property Management System (PMS)
dedicated printers. The Report Scheduler is intended to print all DEFINITY
System reports and the output of virtually all list, display, and test
commands.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-2System Printer
5
System Printer Administration
Use the Feature-Related System Parameters screen to administer the hardware
parameters of the system printer. The system administrator login may access this
screen form by entering the change system-parameters features command.
Screen 5-1 shows the Feature-Related System Parameters screen and Table 5-1
describes the data fields for this screen.
Screen 5-1. System Printer Hardware Administration Screen
NOTE:
For complete installation instructions for the System Printer, see the
installation documents as referenced in Appendix B.
Table 5-1. System Printer Hardware Administration
Field Description
System Printer
Extension: Enter either the data module extension number associated with
the System printer or enter “eia” if the DCE jack is used to
interface the printer. The “eia” option is not available for G3r.
EIA Device Bit Rate: This field is not displayed for R5r configurations. Enter “1200”,
“2400”, “4800”, or “9600” per the required printer speed setting.
Default is “9600”.
Lines Per Page: Enter the number of lines per page required for the report. Valid
entries are 24 through 132. Default is “60”.
Page 4 of 9
FEATURE-RELATED SYSTEM PARAMETERS
SYSTEM PRINTER PARAMETERS
System Printer Extension: ____ Lines Per Page: 60
EIA Device Bit Rate: 9600
SYSTEM-WIDE PARAMETERS
Switch Name: ________________
MALICIOUS CALL TRACE PARAMETERS
Apply MCT Warning Tone? n MCT Voice Recorder Trunk Group: ___
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-3Report Scheduler
5
System Printer Data Link Operation
and Maintenance
Operation and maintenance of the system printer data link is significantly different
from the CDR and journal printer data links. For example, the CDR and journal
printer data links are maintained in a constant link up state, while the system
printer data link is only brought up once every 15 minutes provided there are
reports to be printed, or when an immediate report is scheduled.
The system printer data link has three states that identify its operational condition.
The states are: (1) link up, (2) link down, and (3) maintenance busyout. Whenever
the communication path (including software processes, hardware cabling, and
printer) functions properly and data is exchanged successfully between them, the
data link is defined as being in the link up state. The link down state refers to all
times except (1) whenever reports are being printed and (2) whenever
maintenance personnel have disabled the link. The maintenance busyout state is
the result of executing the busyout sp-link command from the Manager I
terminal. While in the maintenance busyout state, the switch software processes
are disabled and the link retry operation is disabled.
Monitor the operating status of the system printer and, as necessary, refill the
paper bin, relieve any paper jams, verify that the printer is receiving power, etc.
NOTE:
Only personnel with maintenance permissions can execute the busyout
sp-link command. This is normally only performed via the maintenance
login. Therefore, as necessary, all nonmaintenance personnel should simply
flip the printer power switch to the OFF position to refill the paper bin and
remove jammed paper. Subsequently, the system printer can be restored
on-line by turning the power switch ON.
If the system printer link generates either a Warning alarm or a Minor alarm, the
problem should be referred to the proper maintenance personnel.
Report Scheduler
The Report Scheduler may be used with many switch features. Specifically,
virtually all list, display, or test commands may be executed with the schedule
qualifier. Therefore, the system administrator login, maintenance login, and other
logins, may schedule reports.
Whenever a command containing the schedule option is executed, it results in
generating a Job Id. A maximum of 50 different Job Ids (50 different reports) can
be scheduled for printing. The Report Scheduler feature is used to specify the
actual day(s) and time of day that each report will be printed.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-4Report Scheduler
5
Print Intervals
For purposes of printing reports, three print intervals are available:
■immediate — If you select this option, the report will be printed
immediately.
■scheduled — If you select this option, the date, time, and day(s)
parameters for the report are set administratively. To change them,
readministration is required.
■deferred — If you select this option, the report will be generated once for
the date, time, and day specified.
Adding a Report to the Report Scheduler
To add a report to the Report Scheduler, enter a list, test, display, or other
command followed by the schedule option. Whenever a report is initially
scheduled, the print interval of immediate is automatically assigned as the
default. Therefore, if immediate is not desired, the print interval must be changed
to deferred or scheduled and a day and print time must still be added to the
Report Scheduler. Table 5-2 describes the data fields for this screen.
Screen 5-2. Adding a Report with the List Measurements Attendant-Group Schedule
Command
list measurements attendant-group Page 1
REPORT SCHEDULER
Job Id: 1 Job Status: none
Command: list measurements attendant-group
Print Interval: immediate
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-5Report Scheduler
5
Table 5-2. Report Scheduler Field Descriptions
Field Description
Job Id: This is a display-only field. Whenever a command is executed with the
qualifier schedule, the system responds by generating a unique Job Id
number. The Job Id assigned by the system is the lowest number within
the range of 1 through 50 that is not in use.
Job Status: This is a display-only field. It identifies the print status of the report. Since
the job is not yet on the Report Scheduler, this field displays none.
Command: This is a display-only field. It displays the command line parameters
ACTION, OBJECT, and QUALIFIER, of the command being scheduled.
Print Interval: This field has three options: immediate, deferred, and scheduled. The
immediate option is initially assigned as a default. Thereafter this option
is used whenever the administrator would like to print the report
immediately. Whenever the Print Interval: field is changed from
immediate to deferred, or scheduled, the system responds as
appropriate with the word deferred or scheduled. Furthermore, the
screen changes to the format shown in Screen 5-6 and the administrator
is prompted to enter values for the Print Time: and the days of the week
fields.
NOTE:
The deferred option is only used when you want to schedule the
report for a single printing. Thereafter, the Job Id is automatically
removed from the Report Scheduler. Those reports that are
administered as scheduled are printed on a week after week basis.
Print Time: Within a given hour, reports may be scheduled at 15-minute intervals
(that is, xx:00, xx:15, xx:30, or xx:45). The system printer requires
significant switch processor resources. Therefore, it is important that the
reports be scheduled for off-peak hours. Furthermore, the reports should
not all be scheduled for the same hour and time interval, but should be
staggered across multiple off-peak time intervals. If, because of printing
volume or other problems, a report is not printed within four hours of its
scheduled time interval, it will not be printed until its next scheduled time
interval. This is a 4-hour (non-administrable) limit. Immediate and
deferred jobs would be removed from the Report Scheduler under this
scenario and would require reentry to print.
Days of Week For each day of the week that the report is to be printed, enter y (yes).
Alternatively, enter n (no) for those days when the report should not be
printed. Selecting an n for all seven days of the week will effectively
disable a report from being printed. Days are defaulted to n.
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-6Report Scheduler
5
Screen 5-3. Administering a Time/Date When Adding a Scheduled Report
Other commands are added to the Report Scheduler in a similar manner. Simply
append the schedule qualifier to the command and, whenever the first screen
appears, change the Print Interval: field from immediate to scheduled
and subsequently administer the Print Time: and days of the week fields.
Summary of the Steps for Printing Reports
on the System Printer
Procedure:
Execute a command with the schedule qualifier.
Response:
The first screen of the Report Scheduler (for example, Screen 5-4 with the
appropriate command) is displayed. It indicates that the print interval is
immediate.
Procedure:
Either (a) press ENTER — to print the report (immediately) on the system printer, or
(b) since the cursor is on the word immediate just type the word scheduled, or
deferred, and then press ENTER.
NOTE:
If you are using a PC running the 513 terminal emulation package, your
keyboard will not have an ENTER. You must map a function key to serve in
this capacity (pressing RETURN will not achieve the desired results).
Response:
When the print interval is changed to scheduled or deferred, the Print Time:
and the days of the week fields are displayed (for example, Screen 5-3 with the
appropriate command).
list report scheduler Page 1
REPORT SCHEDULER
Job Id: 1 Job Status: none
Command: list report scheduler
Print Interval: scheduled
Print Time: xx:xx
Sun: n Mon: n Tue: n Wed: n Thu: n Fri: n Sat: n
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-7Report Scheduler
5
Procedure:
Type in the desired print time and press ENTER. The cursor is now on the days of
the week field. For those days that you desire to print the report, type in a y.
Response:
Press ENTER to execute the command. The system responds with a prompt for the
next command.
Listing Scheduled Reports
To display a list of all reports that are on the Report Scheduler, enter the list
report-scheduler command. This command displays a list of all reports in the
Report Scheduler. The order of the list is according to scheduled print time.
Reports will be printed according to this list (for example, first report on the list is
the first report printed). Screen 5-4 shows the screen for the list
report-scheduler command. Table 5-3 describes the data fields for this screen.
Screen 5-4. Report Scheduler Screen Form — Typical
NOTE:
In instances such as those for Job Id 4, if an immediate report is scheduled,
the Days field is completed with one y for the current day and n for the
others.
All fields are display-only. If, after reviewing this report, it is determined that
change needs to be made, the change report-scheduler command may be used
to make the desired changes.
list report-scheduler
Page 1 of x
REPORT SCHEDULER
Job Id Days (smtwtfs) Time User Status Type
Command
4 nynnnnn 18:45 bcms printing immediate
list measurements attendant-group time 14:15
2 nynynyn 19:00 bcms waiting scheduled
list measurements call-rate time 07:00
7 nnnnnyn 19:15 bcms waiting deferred
list bcms agent 5000 time 08:00 12:00
23 nnynnnn 19:15 bcms waiting scheduled
list bcms agent 4000 day 09/11 09/15
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-8Report Scheduler
5
Table 5-3. Report Scheduler Screen Form
Field Description
Job Id Whenever a command is executed with the schedule qualifier, the
system responds by generating a unique Job Id number. The Job Id
assigned by the system is the lowest number within the range of 1
through 50 that is not in use.
Days (smtwtfs) On a per-day basis, an n indicates that the report will not be printed
that day; a y indicates that the report will be printed that day.
Selecting an n for all seven days of the week will effectively disable
a report from being printed.
Time The time interval that the report is scheduled to be printed.
User The user login that scheduled the identified report.
Status Same as “Job Status” which was described previously. The four
possible states are:
■Waiting—means that the report is not scheduled for any activity
during the current 15-minute time interval.
■Print-Next—means that the report is scheduled to be printed
within the current 15-minute time interval.
■Printing—means that the report is currently being printed.
■Printed—means that the report has been successfully printed
during the current 15-minute time interval.
Type Indicates the type of print interval that is scheduled for the report.
Command This field displays the complete command line (excluding the
schedule option) that the user entered to produce the identified
report.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-9Report Scheduler
5
Change Command
The change report-scheduler command is used to change the schedule of a
report. To display this screen form, enter the change report-scheduler xx
command. The xx corresponds to the Job Id. Screen 5-5 shows the Change
Report-Scheduler screen. Table 5-4 describes the data fields for this screen.
Screen 5-5. Change Report-Scheduler Screen
Table 5-4. Change Report-Scheduler Screen Form
Field Description
Job Id: This is a display-only field. It is the unique identifier for the report. The Job
Id assigned by the system is the lowest number within the range of 1
through 50 that is not in use.
Job Status: This is a display-only field. It identifies the print status of the report. The
four possible states are:
■Waiting—means that the report is not scheduled for any activity during
the current 15-minute time interval.
■Print-Next—means that the report is scheduled to be printed within
the current 15-minute time interval.
■Printing—means that the report is currently being printed.
■Printed—means that the report has been successfully printed during
the current 15-minute interval.
Command: This is a display-only field. It is the command that is to be executed.
Continued on next page
change report-scheduler 23 Page 1
REPORT SCHEDULER
Job Id: 23 Job Status: printed
Command: list bcms agent 4000 time start 08:00 stop 12:00
Print Interval: scheduled
Print Time: 19:15
Sun: n Mon: y Tue: n Wed: y Thu: n Fri: y Sat: n
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-10Report Scheduler
5
Remove Command
The remove report-scheduler command is used to remove a report from the
Report Scheduler. To display this screen form, enter the remove
report-scheduler xx command. The xx corresponds to the Job Id. Screen 5-6
shows this screen. Table 5-5 describes the data fields for the screen.
Screen 5-6. Remove Report Scheduler Command Screen
Print Interval: The three possible options are immediate, scheduled, and deferred. If the
print time of a report is changed so that its scheduled time now falls inside
the current 15-minute time interval (that is, the Job Status: field changes
from waiting to print-next), the report will not be printed in the current
interval.
Print Time: Within a given hour, reports may be scheduled at 15-minute intervals (that
is xx:00, xx:15, xx:30, xx:45). This field may be changed as desired. The
system printer requires significant switch processor resources. Therefore,
it is important that the reports be scheduled for off-peak hours.
Furthermore, the reports should not all be scheduled for the same hour
and time interval, but should be staggered across multiple off-peak time
intervals. If, because of printing volume or other problems, a report is not
printed within four hours of its scheduled time interval, it will not be printed
until its next scheduled time interval. This is a 4-hour (nonadministrable)
limit. Immediate and deferred jobs would be removed from the Report
Scheduler under this scenario and would require reentry to print.
Days of
Week On a per-day basis, an n indicates that the report will not be printed for
that day; a y indicates that the report will be printed for that day. This field
may be changed as desired. Selecting an n for all seven days of the week
will effectively disable a report.
Table 5-4. Change Report-Scheduler Screen Form — Continued
Field Description
Continued on next page
remove report-scheduler 23 Page 1
REPORT SCHEDULER
Job Id: 23 Job Status: printed
Command: list bcms agent 7000 time start 08:00 stop 12:00
Print Interval: scheduled
Print Time: 19:15
Sun: n Mon: y Tue: n Wed: y Thu: n Fri: y Sat: n
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-11Report Scheduler
5
NOTE:
All fields are display-only. Once the user has verified that the identified
report is the one to be removed, it is then necessary to press RETURN.
Following this action, the system waits for the next command.
Table 5-5. Remove Report Scheduler Command Screen
Field Description
Job Id: The unique identifier for the report. The Job Id assigned by the system
is the lowest number within the range of 1 through 50 that is not in use.
Job Status: Identifies the print status of the report. The four possible states are:
■Waiting—Means that the report is not scheduled for any activity
during the current 15-minute time interval.
■Print-Next—Means that the report is scheduled to be printed within
the current 15-minute time interval.
■Printing—Means that the report is currently being printed.
■Printed—Means that the report has been successfully printed during
the current 15-minute interval.
Command: The command associated with the Job Id that is being removed.
Print Interval: The three possible options are immediate, scheduled, and deferred.
Print Time: Within a given hour, reports may be scheduled at 15-minute intervals
(for example, xx:00, xx:15, xx:30, xx:45).
Days of Week On a per-day basis, an n indicates that the report will not be printed for
that day; a y indicates that the report will be printed that day. Selecting
an n for all seven days of the week will effectively disable a report from
being printed.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
System Printer and Report Scheduler
5-12Report Scheduler
5
Use of BCMS Reports for ACD Planning
6-1Planning/Engineering Objectives
6
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
6
Use of BCMS Reports for ACD
Planning
Planning/Engineering Objectives
Before presenting examples of how you can use the BCMS reports to optimize the
operations of an ACD application, this chapter reviews certain relevant points.
First, recall that the ACD hunt groups and trunk groups may be administered for:
■Internal measurements (DEFINITY BCS and GuestWorks supports internal
measurements only)
■External measurements (
CentreVu
Call Management System)
■Both internal and external
■None (no measurements)
Second, the ACD feature can support a maximum number of agents, splits, and
trunk groups. Since the BCMS feature may measure fewer agents, splits, and
trunk groups, those agents, splits, and trunk groups that are not measured with
the BCMS feature either are measured with external
CentreVu
CMS or are not
measured at all (
CentreVu
CMS is not supported with DEFINITY BCS or
GuestWorks).
If you are planning to implement BCMS and you do not have accurate traffic
information, then the ACD splits are initially designed based on an estimated
number of trunks and agents according to the particular needs of each ACD split.
The number of trunks and agents is based on an estimated volume of incoming
traffic. The primary purpose of the BCMS reports is to monitor the ACD
application and provide information detailing how the splits, agents, and trunk
groups are being used. By analyzing these reports, you can determine the
optimum number of agents and trunks needed to support a given ACD
application.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-2Planning/Engineering Objectives
6
The overall design of an ACD should be based on how a business values a lost or
blocked call. For example, if the ACD split handles sales and each blocked or
dropped call represents potential lost revenue, it will probably be desirable to
provide more trunks than agents to minimize the lost calls. As a contrast, if the
ACD split handles calls from a captive customer base and each agent performs a
significant amount of “After Call Work” that results in an expense to the
organization, it will probably be desirable to provide fewer trunks than agents.
Finally, remember that the report scheduler allows only 50 reports each night. If
you do not need to view historical data on an hour-by-hour basis, or if you prefer
to see data sorted by entity (such as agents, splits, or VDNs) rather than sorted by
time, then you should utilize the summary reports. These reports can include up to
30 entities at one time, and thus can allow you to make better use of the 50
available scheduler slots.
BCMS System Status Report
You should use the BCMS System Status Report (monitor bcms system) as the
first step toward determining how the ACD is functioning. This report displays data
that details how each split’s queue is currently functioning. Specifically, the report
lists:
■The number of CALLS WAITING in the queue (this includes calls ringing)
■The length of time that the OLDEST CALL has been queued
■The number of ACD calls that have been answered
■The number of agents that are available to receive ACD calls
■The number of calls that have abandoned
■The average length of time before a call abandons the queue
■The average length of time it is taking before the ACD calls are answered
■The average length of time the agents spend talking
■The average length of time the agents spend in ACW mode.
■The percentage of calls answered within service level.
If any of the numbers are not within their desired range, the individual
split(s) should be observed more closely with the Monitor Split Status
Report. Some of the more obvious indications of a problem are:
— An excessive number of calls waiting in the queue, or a very old
“oldest call.”
— An excessive number of calls that have abandoned the queue
— A large number of agents that are available to receive ACD calls
— If only a small number of ACD calls have been answered, but the
split is still staffed with a large number of agents
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-3Planning/Engineering Objectives
6
— An excessive amount of time is spent in ACW mode, AUX work, or
ExtnIn/ExtnOut calls.
BCMS Split Status Report
You can use the Split Status Report (monitor bcms split) to determine:
■Whether there are enough “staffed” agents for the current level of incoming
calls.
— If after monitoring the Avail field for several minutes and no agents
are indicated as being available to receive calls, you will probably
want to “staff” some of the “unstaffed” positions, especially if this
loss of business represents a loss in revenue.
— If all agent positions are “staffed,” it may be appropriate to add more
agents to the split.
— If an excessive amount of time is being spent answering ACD calls
for another split, then it may be appropriate to determine the reason
and possibly to assign more agents to the other split.
■Whether any particular agent or agents are spending too much time on
ExtnCalls.
— If an agent is suspected of spending too much time on ExtIn/ExtOut
calls, the BCMS Agent Report should be used to investigate further.
■Whether, based on a comparison of agents within this split, any particular
agent is taking more time to handle calls than appropriate. More
specifically, this would be referred to as excessive ACD talk time.
— If an agent is suspected of taking more time than appropriate, the
BCMS Agent Report should be used to investigate further.
BCMS VDN Status Report
You can use the BCMS VDN Status Report (monitor bcms vdn) to determine
how one or more internally-measured VDNs and vectors are functioning. This
report can help you to determine whether you need to change a VDN instead of
moving agents between splits when ACD traffic changes. Specifically, some
information this report indicates is:
■How many calls have encountered a VDN but have not been answered
■The time the oldest call has been waiting in the VDN
■The average length of time for a call to be completed in the VDN during the
current period
■The average length of time a call waited before abandoning during the
current period
■The average length of talk time for calls to the VDN completed during the
current period
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-4Planning/Engineering Objectives
6
■The percent of calls being answered in the VDN within the acceptable
service level during the current period
BCMS Trunk Group Report
You can use the BCMS Trunk Group Report (list bcms trunk) to determine:
■The number of incoming and outgoing calls
■The average amount of time for incoming calls
■The average amount of time for outgoing calls
■The number of incoming calls that abandoned. This may be an indication
that there are not enough “staffed” agent positions rather than not enough
trunks
■The number of outgoing calls that were placed over this trunk group and
answered during the specified reporting period
■The CCS traffic load for incoming calls
■The CCS traffic load for outgoing calls
■The percent of time that one or more trunks have been busied-out for
maintenance purposes
■The percent of time that all trunks within this group are busy. This field
should serve as an indication of whether additional trunks may be needed.
If the designated trunk group serves a split that provides a revenue-producing
function, it will generally be desirable for the trunk group to contain enough trunks
to accommodate the peak level of traffic. After identifying when peak traffic
occurs, it is then necessary to schedule a trunk report for that time of day.
Subsequently, the information from this report and other reports may be used with
the “Trunk Engineering Guidelines” (described later) to determine the correct
number of trunks for the trunk group.
BCMS Agent Report
You can use the BCMS Agent Report (list bcms agent) to determine exactly how
the specified agent uses his or her time. Subsequently, and depending on the
specifics of the data, you may observe that certain changes are in order. For
example, if the TOTAL AVAIL TIME field shows a high number, you may find it
desirable to:
1. Change this agent’s work schedule
2. Place this agent into multiple splits via an administration change. You can
identify those splits that may be in need of additional agents by analyzing
the individual BCMS Split Reports.
If the AVG TALK TIME field shows high numbers, this may indicate that the agent
needs additional instruction and training.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-5Engineering ACD Applications with Data Obtained from the BCMS Reports
6
BCMS Split or Skill Report
You can use the BCMS Split Report (list bcms split) to identify the time of day
and days of the week when the split is most and least busy. Again, the type of
actions that should be taken will be determined by the business function provided
by the split (for example, whether the split provides a revenue-producing function
such as sales or a revenue-draining function such as warranty service). If the split
is revenue-producing, it may be desirable to identify the time and day when peak
traffic occurs and provide enough trunks and agents to keep the number of
blocked calls low and the service level is high. Furthermore, you can determine
the appropriate number of agents that should be staffed for other times.
BCMS VDN Report
You can use the BCMS VDN Report (list bcms vdn) to determine if your calls are
being handled in a timely manner. For example, the AVG ABAND TIME indicates
how long callers will wait for an agent before hanging up. If the AVG ABAND TIME
is less than the AVG SPEED ANS, you may assume that callers are not being
serviced fast enough by an agent. As a result, this VDN may need more staffing.
If the percentage in service level (% IN SERV LEVL) is not high enough, you may
need more agents or it may be appropriate to provide “backup” splits when the
primary split is under heavy load.
The FLOW OUT and CALLS BUSY/DISC values help you determine the
performance of your vectors. A high FLOW OUT value indicates that the VDN
cannot handle the calls in time. A high CALLS BUSY/DISC value may indicate
that your vectors are written incorrectly.
You should use the “Agent Engineering/Optimizing Guidelines” (described later) to
determine the correct number of agents for each ACD split.
Engineering ACD Applications with
Data Obtained
from the BCMS Reports
When engineering and/or optimizing an ACD, Table 6-1 through Table 6-12 should
be used to determine how many agents and trunks will be required to handle a
given number of incoming calls. Each split should be designed individually for the
number of agents and trunks required, subject to any pertinent system limitations.
You should include for any planned future growth, but do not exceed the
maximum values of the ACD parameters supported by the BCMS feature.
Interpolation is a method of estimating tabular values of a function between two
known values of that function. When using Table 6-1 through Table 6-11 to
determine the number of agents required and Table 6-12 to determine the number
of trunks required for a given ACD, you may find that the expected number of call
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-6Engineering ACD Applications with Data Obtained from the BCMS Reports
6
arrivals or the carried load lies somewhere between two entries in the tables.
Therefore, the number of agents or trunks required will also lie somewhere
between the two entries.
If this is the case, the number of agents required or number of trunks needed can
only be found by interpolation. Use the following equation to interpolate between
tabular values:
Where:
Agent Engineering/Optimizing Guidelines
Table 6-1 through Table 6-11 list the number of ACD agents required to handle a
given incoming call load. The top rows on each of these tables show the possible
delay times for a given incoming call load (calls per hour or busy hour calls), and
the left-most column lists the agents required to handle the incoming call load
such that 90 percent the incoming calls will be answered by the agents before the
specified delay has occurred.
NOTE:
The entries in Table 6-1 through Table 6-11 are in busy-hour calls, which are
the number of calls received by the ACD during peak levels of caller activity.
x
Is the independent variable in terms of calls per hour
y
Is the dependent or functional variable in terms of agents or
trunks needed
x
0Is the tabular value of the independent variable that immediately
precedes
x
x
1Is the tabular value of the independent variable that immediately
succeeds
x
y
0Is the tabular value of the dependent variable that immediately
precedes
y
y
1Is the tabular value of the dependent variable that immediately
succeeds
y
y
=y0+(y1−y0)x1−x0
x−x0
_
_______
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-7Engineering ACD Applications with Data Obtained from the BCMS Reports
6
To determine how many agents will be required to handle the incoming call load of
an ACD split, use Table 6-1 through Table 6-11 as follows:
■Use the BCMS Split Report (list bcms split) to determine the AVG TALK
TIME (the time an agent spends processing a call, or talking to a caller).
Table 6-1 through Table 6-11 contain data that describes the following
service times: 7, 15, 30, 45, 60, 90, 120, 180, 240, 300, and 600 seconds.
Choose the appropriate table for the AVG TALK TIME of the ACD split.
NOTE:
For purposes within this document the term “AVG Talk Time” is
equivalent to the term “AVG Service Time.”
■At the top of the table, choose the closest possible AVG SPEED ANS in
seconds. AVG SPEED ANS is actually a delay time that is defined as the
elapsed time from when a call is routed to the ACD split until it is answered
by an agent. The delay criterion states that 90 percent of the incoming calls
will be answered by the agents before the specified delay has occurred.
■If the calling volume, otherwise referred to as the busy-hour calls, is known,
then use the number indicated on the report. Otherwise, you must estimate
this number. Busy-hour calls denotes the number of calls received by the
ACD during peak levels of caller activity. A typical busy-hour calling rate
might be 120, 130, or 160 calls per hour.
NOTE:
The actual busy-hour calling rate depends on agent staffing and the
particular application. Obviously, the numbers that are identified here
as being typical would be much too high for five agent positions and
too low for 30 agent positions. The numbers given are only for
illustration purposes.
■After choosing the appropriate table and delay column, find the entry in the
table for busy-hour calls that is greater than or equal to the number of
busy-hour calls chosen.
■The number of agent positions required is then found in the left-most
column of the respective table.
■You can interpolate between the tables (for different call service times),
between the columns (for different delay times), and between the rows (for
different number of calls per hour).
Table 6-1 through Table 6-11 were prepared by using a range of 1 to 1000 agents.
For small service times, this yields high traffic rates, even for a small number of
agents. The high traffic rates are presented in the tables for completeness only.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-8Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Example 1:
The classified ads department of a newspaper receives 160 calls per hour. The
average time an agent spends on each call is three minutes. If most of the calls
should be answered in less than 30 seconds, how many agents should be
employed in this department?
Table 6-8 provides data for 180-second (3-minute) call durations. Under
the 30-second column heading (AVG SPEED ANS), find the first entry greater
than 160 calls per hour (175). Follow this row left to the agents column and find 12
agents. The number of agents required to answer 160 calls (of 3-minute duration)
per hour with 90 percent of the callers waiting less than 30 seconds is 12 agents.
For this example, consider the efficiency of the agents and the sensitivity of the
parameters to changes in the call arrival rate. The efficiency of the agents is the
ratio of the number of agent hours spent on the phone to the number of agent
hours in an hour. The number of agent hours spent on the phone is 160 calls per
hour times .05 hours (3 minutes) which equals 8 agent hours. Therefore, the
efficiency is 8/12 (12 agents for 1 hour) and equals .67 or 67 percent.
Suppose the calls per hour increased to 185 calls per hour. The efficiency is now
(185 X 0.05)/12 = 0.77 or 77 percent. The efficiency has increased, but this added
efficiency is not free of charge. The delay criterion has changed significantly from
about 1.6 percent of all calls taking longer than 30 seconds for an agent to answer
to about 15.0 percent (175 calls per hour yield 10.0 percent, but 160 calls per hour
were stated). To get the delay criterion back to 1.6 percent would require a delay
time of about 55 seconds.
Another measure of what is happening with the queue is the average time spent
waiting for service in the queue. With 160 calls per hour, the mean time spent in
the queue is 7.53 seconds. With 185 calls per hour, the mean time in the queue
is 16.14 seconds. The point of this example is to emphasize the sensitivity of the
time in the queue to the arrival rate. In other words, increasing the agent efficiency
from 67 percent to 77 percent nearly doubles the various measures of queuing
time.
NOTE:
For Examples 2 and 3, the “?s” in the tables represent the unknown values
you are looking for. The italicized numbers in the tables represent numbers
that are not included in Table 6-1 through Table 6-11.
Example 2:
The reservations department for a hotel chain knows that the average call
duration is five minutes and that most of the potential customers will not wait more
than one minute for their call to be answered. How many agents are required to
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-9Engineering ACD Applications with Data Obtained from the BCMS Reports
6
handle 150 calls per hour? Under the 60-second column of Table 6-10, you will
find the following information:
Therefore, 16 agents are needed to support the reservations department.
Example 3:
The manager of a split in an ACD knows that calls average 75 seconds and that
the split receives 200 calls per hour. The manager wants most of the calls to be
answered in less than 40 seconds. How many agents are required? To answer
this question, you must interpolate between all parameters—first, between delay
time and calls per hour to obtain the number of calls per hour for a 40-second
delay time. Under the 30- and 45-second columns of Table 6-5 and Table 6-6 you
will find:
agents 60
14 129
? 150
16 151
60 Seconds Average Service Time 75 Seconds 90 Seconds Average Service Time
AVG ANSWER SPEED AVG ANSWER SPEED
agents 30 40 45 agents 30 40 45
5 186 ? 202 7 194 ? 205
?
200
?
200
6 238 ? 257 8 231 ? 242
y
=number o f agents needed
y
=y0+(y1−y0)x1−x0
x−x0
_
_______
y
=14 +( 16 −14 ) 151 −129
150 −129
_
_________
y
=14 +( 2 ×.955 )
y
=15.9
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-10Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Now interpolate between delay time and calls per hour in both tables to obtain
calls per hour for a 40-second delay time.
Now you can fill in the first blank: 197 calls per hour under the 40-second delay
time heading. Repeat the interpolation process three more times to come up with
the figures 251, 190, and 226.
60 Seconds Average Service Time 75 Seconds 90 Seconds Average Service Time
AVG ANSWER SPEED AVG ANSWER SPEED
agents 30 40 45 agents 30 40 45
5 186
197
202 7 194
201
205
?
200
?
200
6 238
251
257 8 231
226
242
y
=number o f calls per hour
y
=y0+(y1−y0)x1−x0
x−x0
_
_______
y
=186 +( 202 −186 ) 45 −30
40 −30
_
_______
y
=186 +( 16 ×0. 666 )
y
=196. 66
y
=number o f agents needed when a 60 −second service time is desirable
y
=y0+(y1−y0)x1−x0
x−x0
_
_______
y
=5+( 6 −5 ) 251 −197
200 −197
_
_________
y
=5+( 1 ×0. 055 )
y
=5. 05
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-11Engineering ACD Applications with Data Obtained from the BCMS Reports
6
So now we know that 5.05 agents would be needed when a 60-second service
time is desirable. Repeat the above interpolation process once (for a 90-second
service time) to come up with the result:
y
(number of agents) = 7
From exact calculations, the use of six agents implies that 1 percent of the
incoming calls will wait more than 40 seconds.
60 Seconds Average Service Time 75 Seconds
90 Seconds Average
Service Time
AVG ANSWER SPEED AVG ANSWER SPEED
agents 30 40 45 agents 30 40 45
5 186
197
202 7 194
201
205
5.05 200 7.27 200
6 238
251
257 198 8 217
226
231
y
=number o f agents needed when a 75 −second service time is desirable
y
=y0+(y1−y0)x1−x0
x−x0
_
_______
y
=5. 05 +( 7 −5. 05 ) 90 −60
75 −60
_
_______
y
=5. 05 +( 1. 95 ×0. 50 )
y
=6. 02 ( or 6 )
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-12Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-1. 7 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1 154 195 253 302 359 392 429 449 470
2 575 648 736 799 865 902 942 962 984
3 1044 1135 1237 1305 1376 1415 1455 1476 1498
4 1531 1633 1743 1815 1888 1928 1969 1990 2012
5 2025 2136 2251 2326 2401 2441 2483 2504 2526
6 2525 2641 2761 2838 2914 2955 2997 3018 3040
7 3027 3149 3272 3350 3428 3469 3511 3533 3555
8 3532 3657 3783 3863 3941 3983 4025 4047 4069
9 4038 4167 4295 4376 4455 4496 4539 4561 4583
10 4545 4677 4808 4889 4969 5010 5053 5075 5097
12 5562 5699 5833 5916 5997 6039 6082 6104 6126
14 6581 6722 6859 6943 7025 7067 7110 7132 7155
16 7602 7746 7885 7971 8053 8095 8139 8161 8183
18 8625 8771 8912 8998 9081 9123 9167 9189 9212
20 9648 9797 9939 10026 10109 10152 10195 10218 10240
25 12208 12362 12508 12596 12680 12723 12767 12789 12812
30 14772 14929 15077 15166 15251 15294 15338 15360 15383
35 17337 17497 17647 17736 17822 17865 17909 17932 17954
40 19903 20065 20217 20307 20393 20436 20481 20503 20526
45 22470 22634 22787 22878 22964 23008 23052 23074 23097
50 25037 25204 25357 25449 25535 25579 25623 25646 25669
60 30174 30343 30499 30591 30677 30721 30766 30789 30811
70 35312 35483 35640 35733 35820 35864 35909 35932 35954
80 40451 40624 40782 40875 40963 41007 41052 41074 41097
90 45591 45765 45924 46018 46105 46150 46195 46217 46240
100 50731 50906 51066 51160 51248 51292 51337 51360 51383
125 63582 63760 63922 64016 64105 64149 64194 64217 64240
150 76435 76615 76778 76873 76961 77006 77051 77074 77097
175 89289 89471 89634 89730 89818 89863 89909 89931 89954
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-13Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 102144 102326 102491 102586 102675 102720 102766 102788 102811
225 114999 115182 115347 115443 115532 115577 115623 115646 115668
250 127854 128038 128204 128300 128389 128435 128480 128503 128526
275 140710 140895 141061 141157 141246 141292 141337 141360 141383
300 153565 153751 153917 154014 154104 154149 154194 154217 154240
350 179277 179464 179631 179728 179818 179863 179908 179931 179954
400 204990 205177 205345 205442 205532 205577 205623 205645 205668
450 230702 230891 231059 231156 231246 231291 231337 231360 231383
500 256415 256604 256773 256870 256960 257006 257051 257074 257097
550 282128 282318 282487 282584 282674 282720 282765 282788 282811
600 307842 308032 308201 308298 308389 308434 308480 308503 308525
650 333555 333745 333915 334013 334103 334148 334194 334217 334240
700 359268 359459 359629 359727 359817 359863 359908 359931 359954
750 384982 385173 385343 385441 385531 385577 385623 385645 385668
800 410696 410887 411057 411155 411246 411291 411337 411360 411383
850 436409 436601 436771 436869 436960 437005 437051 437074 437097
900 462123 462315 462485 462583 462674 462720 462765 462788 462811
950 487837 488029 488199 488298 488388 488434 488480 488503 488525
1000 513551 513743 513914 514012 514103 514148 514194 514217 514240
Table 6-1. 7 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-14Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-2. 15 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1 44526886115136163180198
2 196 222 261 295 339 367 399 417 437
3 386 425 478 521 572 603 637 656 676
4 592 640 703 752 808 840 876 896 916
5 806 862 933 986 1045 1078 1115 1135 1156
6 1025 1089 1165 1221 1282 1317 1355 1375 1396
7 1248 1317 1399 1457 1521 1556 1594 1615 1636
8 1474 1548 1634 1694 1759 1795 1834 1854 1875
9 1702 1780 1869 1932 1998 2035 2074 2094 2115
10 1931 2013 2106 2170 2237 2274 2313 2334 2355
12 2393 2482 2580 2646 2715 2753 2793 2814 2835
14 2858 2953 3055 3124 3194 3232 3273 3294 3315
16 3326 3425 3531 3601 3673 3712 3752 3773 3795
18 3796 3899 4008 4079 4152 4191 4232 4253 4275
20 4266 4373 4485 4558 4631 4671 4712 4733 4755
25 5448 5562 5679 5754 5830 5870 5911 5933 5955
30 6634 6753 6875 6952 7029 7069 7111 7133 7155
35 7823 7947 8071 8150 8228 8269 8311 8333 8355
40 9013 9141 9268 9349 9427 9468 9511 9533 9555
45 10205 10336 10466 10547 10626 10668 10711 10732 10755
50 11399 11532 11664 11746 11826 11868 11910 11932 11955
60 13787 13926 14061 14144 14225 14267 14310 14332 14355
70 16178 16321 16458 16543 16624 16667 16710 16732 16755
80 18571 18716 18856 18942 19024 19066 19110 19132 19154
90 20965 21113 21254 21341 21423 21466 21510 21532 21554
100 23359 23510 23653 23740 23823 23866 23910 23932 23954
125 29349 29504 29650 29738 29822 29866 29910 29932 29954
150 35341 35499 35648 35737 35822 35865 35909 35932 35954
175 41334 41496 41646 41736 41821 41865 41909 41932 41954
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-15Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 47329 47493 47645 47735 47821 47865 47909 47932 47954
225 53325 53490 53644 53735 53821 53865 53909 53932 53954
250 59321 59488 59643 59734 59821 59865 59909 59932 59954
275 65318 65487 65642 65734 65820 65864 65909 65932 65954
300 71315 71485 71641 71733 71820 71864 71909 71932 71954
350 83310 83482 83640 83733 83820 83864 83909 83931 83954
400 95307 95480 95639 95732 95820 95864 95909 95931 95954
450 107303 107478 107638 107732 107819 107864 107909 107931 107954
500 119301 119477 119637 119731 119819 119864 119909 119931 119954
550 131298 131476 131636 131731 131819 131864 131909 131931 131954
600 143296 143474 143636 143731 143819 143864 143909 143931 143954
650 155294 155473 155635 155730 155819 155864 155909 155931 155954
700 167293 167473 167635 167730 167819 167863 167909 167931 167954
750 179291 179472 179635 179730 179819 179863 179909 179931 179954
800 191290 191471 191634 191730 191818 191863 191909 191931 191954
850 203289 203470 203634 203729 203818 203863 203909 203931 203954
900 215287 215470 215634 215729 215818 215863 215909 215931 215954
950 227286 227469 227633 227729 227818 227863 227909 227931 227954
1000 239285 239469 239633 239729 239818 239863 239908 239931 239954
Table 6-2. 15 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-16Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-3. 30 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1 161822263543576882
2 798698111132147169183200
3 161 173 193 212 240 260 286 301 319
4 252 270 296 320 353 376 404 420 438
5 349 371 403 431 468 493 522 539 558
6 450 476 513 544 585 611 641 659 677
7 554 583 624 659 702 729 760 778 797
8 660 692 737 774 819 847 880 898 917
9 767 803 851 890 937 966 999 1017 1037
10 875 914 965 1007 1055 1085 1118 1137 1157
12 1096 1140 1196 1241 1292 1323 1358 1376 1396
14 1319 1368 1429 1476 1530 1562 1597 1616 1636
16 1544 1597 1663 1712 1768 1801 1836 1856 1876
18 1772 1829 1898 1949 2007 2040 2076 2096 2116
20 2001 2061 2133 2186 2245 2279 2316 2335 2356
25 2577 2645 2724 2781 2843 2877 2915 2935 2956
30 3159 3232 3317 3377 3440 3476 3514 3535 3556
35 3743 3822 3911 3973 4039 4075 4114 4134 4155
40 4330 4414 4507 4571 4637 4674 4714 4734 4755
45 4919 5006 5103 5168 5236 5274 5313 5334 5355
50 5509 5600 5699 5766 5835 5873 5913 5934 5955
60 6692 6789 6894 6963 7034 7072 7113 7134 7155
70 7879 7981 8089 8160 8233 8271 8312 8333 8355
80 9067 9174 9285 9358 9432 9471 9512 9533 9555
90 10257 10368 10482 10556 10631 10670 10712 10733 10755
100 11449 11563 11680 11755 11830 11870 11912 11933 11955
125 14432 14552 14674 14752 14829 14869 14911 14933 14955
150 17419 17545 17670 17750 17828 17869 17911 17933 17955
175 20408 20538 20667 20748 20827 20868 20911 20933 20955
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-17Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 23399 23533 23665 23746 23826 23868 23911 23932 23955
225 26392 26529 26662 26745 26826 26867 26910 26932 26955
250 29386 29525 29661 29744 29825 29867 29910 29932 29955
275 32380 32522 32659 32743 32825 32867 32910 32932 32955
300 35375 35519 35658 35742 35824 35867 35910 35932 35954
350 41367 41514 41655 41741 41824 41866 41910 41932 41954
400 47360 47510 47653 47740 47823 47866 47910 47932 47954
450 53354 53507 53652 53739 53823 53866 53910 53932 53954
500 59349 59504 59650 59738 59822 59866 59910 59932 59954
550 65345 65502 65649 65738 65822 65865 65910 65932 65954
600 71341 71500 71648 71737 71822 71865 71909 71932 71954
650 77338 77498 77647 77737 77822 77865 77909 77932 77954
700 83335 83496 83646 83736 83821 83865 83909 83932 83954
750 89332 89495 89646 89736 89821 89865 89909 89932 89954
800 95330 95493 95645 95735 95821 95865 95909 95932 95954
850 101327 101492 101644 101735 101821 101865 101909 101932 101954
900 107325 107491 107644 107735 107821 107865 107909 107932 107954
950 113323 113490 113643 113735 113821 113865 113909 113932 113954
1000 119322 119489 119643 119734 119821 119865 119909 119932 119954
Table 6-3. 30 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-18Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-4. 45 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1 101112141721293545
2 48525763748398109122
3 99 105 115 125 142 155 174 186 201
4 157 165 179 193 213 229 251 264 280
5 218 229 246 263 287 305 329 343 359
6 282 296 316 335 363 382 407 422 439
7 348 364 387 409 439 460 486 501 519
8 416 434 460 484 516 538 565 581 598
9 485 504 533 559 593 616 644 660 678
10 555 576 607 635 671 695 723 740 758
12 697 722 758 788 827 852 882 899 918
14 841 870 909 943 984 1010 1041 1059 1077
16 988 1019 1062 1098 1142 1169 1200 1218 1237
18 1135 1170 1216 1254 1300 1327 1360 1378 1397
20 1284 1322 1371 1410 1458 1486 1519 1537 1557
25 1661 1704 1760 1803 1854 1884 1918 1937 1957
30 2042 2090 2151 2198 2251 2282 2317 2336 2356
35 2426 2479 2544 2594 2649 2681 2717 2736 2756
40 2812 2869 2938 2990 3047 3080 3116 3136 3156
45 3199 3260 3333 3387 3445 3479 3516 3535 3556
50 3589 3653 3729 3784 3844 3878 3915 3935 3956
60 4370 4440 4522 4580 4642 4677 4715 4735 4756
70 5154 5230 5316 5376 5440 5476 5514 5535 5556
80 5941 6021 6111 6173 6239 6275 6314 6334 6355
90 6730 6814 6907 6971 7038 7074 7114 7134 7155
100 7520 7607 7703 7769 7837 7874 7913 7934 7955
125 9499 9594 9696 9765 9835 9873 9913 9934 9955
150 11483 11584 11691 11761 11833 11872 11912 11933 11955
175 13470 13576 13686 13759 13832 13871 13912 13933 13955
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-19Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 15459 15569 15683 15757 15831 15870 15912 15933 15955
225 17449 17563 17680 17755 17830 17870 17912 17933 17955
250 19441 19558 19677 19754 19829 19870 19911 19933 19955
275 21434 21554 21675 21752 21829 21869 21911 21933 21955
300 23428 23550 23673 23751 23828 23869 23911 23933 23955
350 27417 27543 27670 27749 27827 27868 27911 27933 27955
400 31408 31538 31667 31748 31827 31868 31911 31933 31955
450 35400 35533 35665 35747 35826 35868 35911 35932 35955
500 39393 39530 39663 39745 39826 39867 39910 39932 39955
550 43387 43526 43661 43744 43825 43867 43910 43932 43955
600 47382 47523 47660 47744 47825 47867 47910 47932 47955
650 51378 51521 51658 51743 51824 51867 51910 51932 51955
700 55374 55518 55657 55742 55824 55867 55910 55932 55954
750 59370 59516 59656 59742 59824 59866 59910 59932 59954
800 63366 63514 63655 63741 63824 63866 63910 63932 63954
850 67363 67512 67654 67741 67823 67866 67910 67932 67954
900 71360 71511 71653 71740 71823 71866 71910 71932 71954
950 75358 75509 75653 75740 75823 75866 75910 75932 75954
1000 79355 79508 79652 79739 79823 79866 79910 79932 79954
Table 6-4. 45 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-20Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-5. 60 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
177891113172229
2 353640435056667485
3 7275818797106120130143
4 113 118 126 135 149 160 177 188 202
5 158 164 175 186 202 216 234 246 261
6 204 212 225 238 257 272 292 305 321
7 253 262 277 292 313 329 351 364 380
8 302 313 330 346 370 387 410 424 440
9 352 365 383 401 427 445 469 483 500
10 403 417 438 457 484 503 528 542 559
12 508 524 548 570 600 620 646 662 679
14 614 632 659 684 716 738 765 781 799
16 721 742 772 799 833 856 884 900 918
18 830 853 886 914 951 975 1003 1020 1038
20 940 965 1000 1030 1069 1093 1123 1139 1158
25 1218 1248 1289 1322 1364 1390 1421 1439 1457
30 1500 1534 1579 1616 1661 1688 1720 1738 1757
35 1784 1822 1872 1911 1958 1987 2019 2038 2057
40 2071 2112 2165 2207 2256 2285 2319 2337 2357
45 2358 2403 2459 2503 2554 2584 2618 2637 2657
50 2648 2695 2754 2800 2852 2883 2918 2937 2956
60 3229 3281 3346 3395 3450 3481 3517 3536 3556
70 3813 3870 3939 3990 4047 4080 4116 4136 4156
80 4399 4460 4534 4587 4646 4679 4716 4735 4756
90 4987 5052 5129 5184 5244 5278 5315 5335 5356
100 5576 5645 5725 5781 5843 5877 5915 5935 5956
125 7054 7130 7216 7276 7340 7376 7414 7435 7456
150 8536 8618 8709 8772 8838 8875 8914 8934 8955
175 10021 10108 10204 10269 10337 10374 10413 10434 10455
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-21Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 11509 11600 11700 11767 11836 11873 11913 11934 11955
225 12998 13094 13196 13264 13335 13373 13413 13434 13455
250 14489 14588 14693 14763 14834 14872 14913 14934 14955
275 15980 16082 16190 16261 16333 16372 16412 16433 16455
300 17473 17578 17688 17760 17832 17871 17912 17933 17955
350 20460 20570 20683 20757 20831 20871 20912 20933 20955
400 23450 23563 23680 23755 23830 23870 23912 23933 23955
450 26440 26558 26677 26754 26829 26870 26911 26933 26955
500 29432 29553 29675 29752 29829 29869 29911 29933 29955
550 32426 32549 32673 32751 32828 32869 32911 32933 32955
600 35419 35545 35671 35750 35828 35869 35911 35933 35955
650 38414 38542 38669 38749 38827 38868 38911 38933 38955
700 41409 41539 41667 41748 41827 41868 41911 41933 41955
750 44404 44536 44666 44747 44826 44868 44911 44932 44955
800 47400 47534 47665 47747 47826 47868 47911 47932 47955
850 50396 50531 50664 50746 50826 50868 50910 50932 50955
900 53393 53529 53663 53745 53826 53867 53910 53932 53955
950 56389 56527 56662 56745 56825 56867 56910 56932 56955
1000 59386 59526 59661 59744 59825 59867 59910 59932 59955
Table 6-5. 60 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-22Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-6. 90 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1555679111418
2 232426293237424954
3 475053586371778793
4 7578839096107115125132
5 104 109 115 124 131 144 153 164 171
6 135 141 148 159 168 181 191 204 211
7 167 174 182 194 205 220 230 243 251
8 199 208 217 231 242 258 269 282 290
9 233 242 252 268 280 297 308 322 330
10 267 277 288 305 318 336 347 362 370
12 336 348 361 380 394 414 426 441 450
14 406 421 435 456 471 492 505 521 529
16 477 494 510 532 549 571 584 600 609
18 549 568 585 610 627 650 664 680 689
20 622 642 661 687 705 729 743 760 769
25 807 831 852 882 902 927 942 959 968
30 994 1021 1045 1077 1099 1126 1141 1159 1168
35 1182 1213 1239 1274 1297 1324 1341 1358 1368
40 1373 1406 1435 1471 1495 1524 1540 1558 1568
45 1564 1600 1630 1669 1693 1723 1740 1758 1768
50 1756 1794 1826 1867 1892 1922 1939 1958 1968
60 2142 2185 2220 2263 2290 2321 2338 2357 2367
70 2530 2577 2615 2660 2688 2720 2738 2757 2767
80 2920 2971 3011 3058 3087 3119 3138 3157 3167
90 3311 3365 3407 3456 3485 3519 3537 3557 3567
100 3703 3760 3804 3854 3884 3918 3937 3957 3967
125 4687 4750 4797 4851 4882 4917 4936 4956 4967
150 5673 5742 5792 5848 5881 5917 5936 5956 5967
175 6662 6735 6788 6846 6879 6916 6936 6956 6967
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-23Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 7653 7729 7784 7844 7878 7915 7935 7956 7967
225 8645 8725 8782 8843 8878 8915 8935 8956 8967
250 9638 9721 9779 9842 9877 9915 9935 9956 9966
275 10631 10717 10777 10841 10876 10914 10935 10956 10966
300 11626 11714 11775 11840 11876 11914 11934 11956 11966
350 13616 13708 13772 13838 13875 13914 13934 13955 13966
400 15608 15704 15769 15837 15874 15913 15934 15955 15966
450 17601 17700 17767 17836 17873 17913 17934 17955 17966
500 19594 19697 19765 19835 19873 19913 19934 19955 19966
550 21589 21694 21763 21834 21872 21913 21934 21955 21966
600 23584 23691 23762 23833 23872 23912 23933 23955 23966
650 25580 25689 25760 25833 25871 25912 25933 25955 25966
700 27576 27687 27759 27832 27871 27912 27933 27955 27966
750 29573 29685 29758 29832 29871 29912 29933 29955 29966
800 31569 31683 31757 31831 31871 31912 31933 31955 31966
850 33566 33682 33756 33831 33870 33912 33933 33955 33966
900 35563 35680 35755 35830 35870 35912 35933 35955 35966
950 37561 37679 37755 37830 37870 37912 37933 37955 37966
1000 39559 39678 39754 39830 39870 39911 39933 39955 39966
Table 6-6. 90 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-24Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-7. 120 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
13444567911
2 171718202225283337
3 343637404349536065
4 545759636774808894
5 7679828893101108117123
6 99 102 106 113 119 129 136 146 153
7 122 126 131 139 146 157 165 175 182
8 146 151 156 165 173 185 193 205 212
9 170 176 182 192 201 213 223 234 241
10 195 202 209 220 229 242 252 264 271
12 246 254 262 275 285 300 310 323 331
14 298 307 316 331 342 358 369 383 390
16 350 361 371 387 399 417 428 442 450
18 404 415 427 444 457 475 487 502 510
20 457 470 483 501 515 534 547 561 570
25 594 609 624 646 661 682 695 711 719
30 732 750 767 791 808 830 844 860 869
35 872 892 911 937 956 979 993 1010 1019
40 1013 1035 1056 1084 1103 1128 1143 1159 1169
45 1155 1179 1201 1231 1252 1277 1292 1309 1318
50 1297 1324 1347 1379 1400 1426 1442 1459 1468
60 1584 1614 1641 1675 1697 1725 1741 1758 1768
70 1873 1906 1935 1972 1995 2024 2040 2058 2068
80 2163 2199 2230 2269 2293 2323 2340 2358 2368
90 2454 2493 2526 2566 2592 2622 2639 2658 2668
100 2746 2788 2822 2864 2891 2921 2939 2958 2967
125 3480 3527 3565 3610 3638 3670 3688 3707 3717
150 4216 4268 4309 4357 4386 4419 4437 4457 4467
175 4954 5011 5054 5105 5135 5168 5187 5207 5217
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-25Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 5694 5754 5800 5853 5883 5918 5937 5957 5967
225 6436 6499 6547 6601 6632 6667 6686 6706 6717
250 7178 7244 7294 7349 7381 7417 7436 7456 7467
275 7921 7990 8041 8098 8130 8166 8186 8206 8217
300 8665 8737 8789 8847 8880 8916 8936 8956 8967
350 10154 10230 10285 10345 10379 10416 10435 10456 10467
400 11645 11725 11782 11843 11878 11915 11935 11956 11967
450 13137 13220 13279 13342 13377 13415 13435 13456 13466
500 14630 14716 14776 14840 14876 14914 14935 14956 14966
550 16124 16213 16274 16339 16375 16414 16434 16456 16466
600 17618 17710 17773 17839 17875 17914 17934 17955 17966
650 19113 19207 19271 19338 19374 19414 19434 19455 19466
700 20609 20704 20769 20837 20874 20913 20934 20955 20966
750 22105 22202 22268 22336 22374 22413 22434 22455 22466
800 23601 23700 23767 23836 23873 23913 23934 23955 23966
850 25097 25198 25266 25335 25373 25413 25434 25455 25466
900 26594 26696 26765 26835 26873 26913 26934 26955 26966
950 28091 28195 28264 28334 28372 28413 28434 28455 28466
1000 29588 29693 29763 29834 29872 29913 29934 29955 29966
Table 6-7. 120 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-26Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-8. 180 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1222233345
2 111111121314161921
3 222324252629313539
4 353637394145485357
5 495152555762667276
6 646667717479849196
7 798183879197102110115
8 95 97 100 104 108 115 121 129 134
9 111 113 116 122 126 134 140 148 154
10 127 130 133 139 144 152 159 168 174
12 160 164 168 175 180 190 197 207 213
14 194 198 203 211 217 228 236 246 253
16 228 233 239 247 255 266 274 285 292
18 263 269 275 284 292 305 313 325 332
20 298 304 311 322 330 343 353 364 372
25 387 395 403 416 426 441 451 463 471
30 478 487 497 511 523 539 549 563 571
35 570 581 591 607 620 637 648 662 670
40 662 674 686 704 717 736 747 762 770
45 755 769 782 801 815 834 847 861 870
50 849 864 878 898 913 933 946 961 970
60 1038 1055 1071 1094 1110 1132 1145 1160 1169
70 1228 1247 1265 1290 1307 1330 1344 1360 1369
80 1419 1441 1460 1487 1505 1529 1543 1560 1569
90 1612 1635 1656 1684 1703 1728 1743 1759 1769
100 1804 1829 1852 1882 1902 1927 1942 1959 1968
125 2289 2318 2343 2377 2399 2425 2441 2459 2468
150 2776 2809 2837 2873 2896 2924 2940 2958 2968
175 3264 3301 3331 3369 3394 3423 3440 3458 3468
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-27Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 3755 3794 3826 3867 3892 3922 3939 3958 3968
225 4246 4288 4322 4365 4391 4421 4439 4458 4468
250 4738 4783 4819 4863 4890 4921 4938 4957 4967
275 5231 5278 5316 5361 5388 5420 5438 5457 5467
300 5724 5774 5813 5859 5887 5920 5938 5957 5967
350 6713 6766 6808 6857 6886 6919 6937 6957 6967
400 7703 7760 7804 7854 7885 7918 7937 7957 7967
450 8694 8754 8800 8853 8883 8918 8937 8957 8967
500 9686 9750 9797 9851 9882 9917 9936 9956 9967
550 10680 10745 10795 10850 10882 10917 10936 10956 10967
600 11673 11742 11792 11848 11881 11917 11936 11956 11967
650 12668 12738 12790 12847 12880 12916 12936 12956 12967
700 13662 13735 13788 13846 13880 13916 13936 13956 13967
750 14657 14732 14786 14845 14879 14916 14935 14956 14967
800 15653 15730 15785 15845 15879 15916 15935 15956 15967
850 16649 16727 16783 16844 16878 16915 16935 16956 16967
900 17645 17725 17782 17843 17878 17915 17935 17956 17967
950 18641 18723 18780 18842 18877 18915 18935 18956 18966
1000 19638 19721 19779 19842 19877 19915 19935 19956 19966
Table 6-8. 180 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-28Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-9. 240 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1222222233
28889910111214
3 161717181920222427
4 262727283032343740
5 363738404144465154
6 474849515357596468
7 586061636669737882
8 707173767883879297
9 828385889196100107111
10 94 96 98 101 104 110 114 121 126
12 118 121 123 127 131 137 142 150 155
14 143 146 149 154 158 165 171 179 185
16 169 172 175 181 186 194 200 208 214
18 195 198 202 208 213 222 229 238 244
20 221 225 229 235 241 251 258 267 273
25 287 292 297 305 312 323 331 341 348
30 354 360 366 376 383 395 404 415 422
35 422 429 436 447 456 469 478 490 497
40 491 499 506 518 528 542 552 564 571
45 561 569 577 590 601 616 626 638 646
50 630 639 649 663 674 689 700 713 721
60 771 781 792 808 820 837 849 862 870
70 912 924 936 954 967 986 998 1012 1020
80 1055 1068 1081 1101 1115 1134 1147 1161 1170
90 1198 1213 1227 1248 1263 1283 1296 1311 1320
100 1341 1358 1373 1395 1411 1432 1445 1461 1469
125 1702 1722 1740 1765 1782 1805 1819 1835 1844
150 2065 2088 2108 2136 2155 2179 2193 2210 2219
175 2430 2455 2477 2507 2527 2552 2567 2584 2593
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-29Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 2796 2823 2847 2879 2900 2926 2942 2959 2968
225 3162 3192 3218 3251 3273 3300 3316 3334 3343
250 3530 3562 3589 3624 3647 3675 3691 3708 3718
275 3898 3932 3961 3997 4021 4049 4065 4083 4093
300 4267 4302 4332 4370 4394 4423 4440 4458 4468
350 5005 5045 5077 5117 5142 5172 5189 5208 5218
400 5746 5788 5822 5865 5891 5922 5939 5958 5968
450 6487 6532 6568 6612 6639 6671 6688 6707 6717
500 7229 7277 7315 7360 7388 7420 7438 7457 7467
550 7972 8022 8062 8109 8137 8170 8188 8207 8217
600 8715 8768 8809 8857 8886 8919 8937 8957 8967
650 9459 9514 9557 9606 9635 9669 9687 9707 9717
700 10204 10261 10304 10355 10385 10418 10437 10457 10467
750 10949 11007 11052 11104 11134 11168 11187 11207 11217
800 11694 11754 11800 11853 11883 11918 11937 11957 11967
850 12440 12502 12549 12602 12633 12668 12686 12706 12717
900 13186 13249 13297 13351 13382 13417 13436 13456 13467
950 13932 13997 14045 14100 14132 14167 14186 14206 14217
1000 14678 14744 14794 14849 14881 14917 14936 14956 14967
Table 6-9. 240 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-30Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-10. 300 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1111112222
26677788910
3 131313141415161820
4 212121222324262830
5 292930313234363941
6 373839404144464952
7 464748505154566063
8 565657596164677175
9 656667697175788386
10 74 76 77 79 81 85 89 94 98
12 94 95 97 100 102 107 111 117 121
14 114 116 117 121 124 129 133 140 144
16 134 136 138 142 145 151 156 163 168
18 155 157 159 164 167 174 179 186 191
20 175 178 181 185 189 196 202 210 215
25 228 231 235 240 245 253 260 268 274
30 281 285 289 296 302 311 318 327 333
35 336 340 345 352 359 369 377 387 393
40 390 395 401 409 416 427 435 446 453
45 445 451 457 466 474 486 494 505 512
50 501 507 513 524 532 545 554 565 572
60 612 620 627 639 649 662 672 684 691
70 725 734 742 755 766 781 791 804 811
80 838 848 857 872 883 899 910 923 931
90 952 963 973 989 1001 1018 1029 1043 1050
100 1067 1078 1089 1106 1119 1137 1148 1162 1170
125 1354 1368 1381 1401 1415 1434 1447 1461 1470
150 1643 1659 1675 1696 1712 1733 1746 1761 1769
175 1934 1952 1969 1992 2009 2031 2045 2060 2069
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-31Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 2225 2245 2264 2289 2307 2330 2344 2360 2369
225 2518 2539 2559 2586 2605 2629 2643 2660 2669
250 2811 2834 2855 2884 2904 2928 2943 2959 2969
275 3104 3129 3152 3182 3202 3227 3242 3259 3268
300 3398 3425 3449 3480 3501 3527 3542 3559 3568
350 3987 4017 4043 4076 4098 4125 4141 4159 4168
400 4578 4610 4638 4674 4697 4724 4741 4758 4768
450 5170 5204 5234 5271 5295 5324 5340 5358 5368
500 5762 5799 5830 5869 5894 5923 5940 5958 5968
550 6355 6394 6427 6467 6492 6522 6539 6558 6568
600 6948 6990 7024 7065 7091 7122 7139 7158 7168
650 7543 7586 7621 7664 7690 7721 7739 7757 7767
700 8137 8182 8219 8262 8290 8321 8338 8357 8367
750 8732 8779 8816 8861 8889 8920 8938 8957 8967
800 9327 9376 9414 9460 9488 9520 9538 9557 9567
850 9923 9973 10012 10059 10087 10120 10138 10157 10167
900 10518 10570 10610 10658 10687 10719 10738 10757 10767
950 11114 11167 11209 11257 11286 11319 11337 11357 11367
1000 11711 11765 11807 11856 11886 11919 11937 11957 11967
Table 6-10. 300 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-32Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-11. 600 Seconds Average Service Time
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
1111111111
2333334445
3667777889
4 101011111111121314
5 141415151516171819
6 191919192021222325
7 232324242526272830
8 282828293030323336
9 323233343536373941
10 37 37 38 38 40 41 43 44 47
12 47 47 48 48 50 51 53 55 58
14 56 57 58 59 60 62 64 67 70
16 66 67 68 69 71 73 76 78 81
18 77 77 78 80 82 84 87 89 93
20 87 88 89 90 93 95 98 101 105
25 113 114 116 117 120 123 127 130 134
30 140 141 143 145 148 151 156 159 164
35 166 168 170 172 176 179 185 188 193
40 194 195 198 200 205 208 214 218 223
45 221 223 226 228 233 237 243 247 253
50 248 250 254 257 262 266 272 277 282
60 304 306 310 314 320 324 331 336 342
70 360 363 367 371 378 383 390 395 402
80 416 419 424 429 436 442 450 455 461
90 473 476 482 487 495 501 509 514 521
100 530 533 539 545 553 560 568 574 581
125 672 677 684 691 700 708 717 723 731
150 816 822 830 837 848 856 866 873 880
175 961 967 977 984 996 1005 1016 1022 1030
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-33Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 1106 1113 1123 1132 1145 1154 1165 1172 1180
225 1251 1259 1270 1280 1293 1303 1314 1322 1330
250 1397 1405 1418 1428 1442 1452 1464 1471 1480
275 1543 1552 1565 1576 1591 1601 1614 1621 1630
300 1690 1699 1713 1724 1740 1750 1763 1771 1780
350 1983 1994 2010 2021 2038 2049 2063 2071 2079
400 2277 2289 2306 2319 2337 2348 2362 2370 2379
450 2572 2585 2603 2617 2636 2648 2662 2670 2679
500 2867 2881 2901 2915 2934 2947 2961 2970 2979
550 3163 3177 3198 3213 3234 3246 3261 3270 3279
600 3459 3474 3496 3512 3533 3546 3561 3569 3579
650 3755 3771 3794 3811 3832 3845 3861 3869 3879
700 4051 4069 4092 4109 4131 4145 4160 4169 4179
750 4348 4366 4391 4408 4431 4444 4460 4469 4479
800 4645 4664 4689 4707 4730 4744 4760 4769 4779
850 4942 4961 4988 5006 5029 5044 5060 5069 5079
900 5239 5259 5286 5305 5329 5343 5360 5369 5378
950 5536 5557 5585 5604 5629 5643 5660 5669 5678
1000 5834 5855 5884 5904 5928 5943 5959 5969 5978
Table 6-11. 600 Seconds Average Service Time — Continued
AVG SPEED ANS
agents 11 15 22 30 45 60 90 120 180
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-34Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Trunk Engineering Guidelines
The number of trunks required for a typical ACD ranges from 1.1 to 1.7 times the
number of agents (whenever a blocked call represents potential lost revenue). As
in the case of agents, the number of trunks required for an ACD is based on the
incoming traffic to each split, not the ACD as a whole.
The left-most column in Table 6-12 lists the number of trunks required to service a
split depending on the carried load in
Erlangs
and the blocking probability. Erlang
is a unit of traffic intensity, or load, used to express the amount of traffic it takes to
keep one facility busy for one hour. Blocking probability relates to the desired
grade of service. The possible blocking probabilities are shown across the top of
Table 6-12, and the entries under the blocking probabilities are carried loads in
Erlangs.
To determine the number of trunks needed for a given split, use Table 6-12 as
follows:
■You will need a split report for the peak busy-hour (for example, list
bcms split ## time xx:xx xx:xx) for the busiest day of the week.
NOTE:
If the time interval is sufficiently long to cover the busiest hours of the
day (such as 8:00 to 18:00) you need only scan the report to
determine which hour is the busy hour. If you have this report for a
time other than the peak busy hour then you will need to estimate
values for the busy hour.
■For the identified peak busy hour, you will need to determine the AVG TALK
TIME and the AVG SPEED ANS. Otherwise, you must estimate the
average call duration: the total time a caller spends waiting for an answer,
plus any time on hold (in queue), and plus the service time (the time the
caller spends talking to an agent).
■If you know the calling volume, otherwise referred to as the busy-hour calls,
then use that value. As an alternative, you must estimate the number of
busy hour calls received by the ACD split during peak levels of caller
activity.
NOTE:
The calling volume is simply the sum of the two fields (# ACD and #
ABAND) for the identified busy hour. This does not include:
■calls never queued
■calls given Central Office (CO) busy
■Multiply the call duration (in fractions of an hour) by the rate of busy-hour
calls (in calls per hour). This number is the carried load in Erlangs.
Abandoned calls should be multiplied by the AVG ABAND time.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-35Engineering ACD Applications with Data Obtained from the BCMS Reports
6
■Determine the desired grade of service (the blocking probability). The
blocking probability for each split is defined as the ratio of blocked calls to
the total number of incoming calls.
■In the column corresponding to the desired grade of service, (for
example, 1 percent blocking probability) choose the nearest higher carried
load. The number of trunks required is then read from the left-most column.
NOTE:
The entries in Table 6-12 are offered loads in Erlangs.
Example 4:
An insurance agency has an ACD that queues calls incoming from the public
switched network. The agency knows that the average caller spends 30 seconds
on hold (in queue), and requires 6 minutes and 20 seconds to service. The
busy-hour call arrival rate is 70 per hour. How many trunks does the agency need
to provide a service level of 99 percent (1 percent blocking probability)?
The average call duration is:
Therefore, the carried load in Erlangs is:
Under the 1 percent column, you will find that 14 trunks can service a carried load
of 7.278 Erlangs while 16 trunks can service 8.786 Erlangs. Interpolate as follows:
Therefore, the agency will need 15 trunks to satisfy its customers.
average call duration =30 +380 =410 seconds or 0. 11389 hours
carried load =0. 11389 ×70 =7. 972
y
=number o f trunks
y
=y0+(y1−y0)x1−x0
x−x0
_
_______
y
=14 +( 16 −14 ) 8. 786 −7. 278
7. 972 −7. 278
_____________
y
=14 +( 2 ×0. 460 )
y
=14. 92
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-36Engineering ACD Applications with Data Obtained from the BCMS Reports
6
Table 6-12. ACD Trunk Engineering
Blocking Probability
trunks 0.01% 0.02% 0.05% 0.10% 0.20% 0.50% 1.00% 2.00% 5.00%
1 0.0002 0.0003 0.0006 0.0011 0.0021 0.0050 0.0100 0.0200 0.0500
2 0.0142 0.0202 0.0321 0.0457 0.0652 0.1049 0.1511 0.2190 0.3622
3 0.0868 0.1102 0.1516 0.1936 0.2482 0.3473 0.4509 0.5902 0.8544
4 0.2347 0.2824 0.3622 0.4388 0.5340 0.6977 0.8607 1.070 1.448
5 0.4519 0.5269 0.6482 0.7614 0.8981 1.126 1.347 1.624 2.108
6 0.7282 0.8314 0.9952 1.145 1.323 1.614 1.890 2.230 2.812
7 1.054 1.186 1.392 1.577 1.795 2.147 2.476 2.877 3.551
8 1.422 1.582 1.829 2.049 2.306 2.716 3.096 3.555 4.316
9 1.825 2.013 2.300 2.555 2.849 3.316 3.745 4.258 5.102
10 2.260 2.474 2.801 3.089 3.420 3.941 4.417 4.982 5.905
12 3.207 3.473 3.876 4.227 4.628 5.253 5.817 6.482 7.553
14 4.238 4.555 5.030 5.441 5.907 6.630 7.278 8.036 9.243
16 5.338 5.703 6.246 6.715 7.244 8.059 8.786 9.632 10.97
18 6.495 6.905 7.515 8.038 8.626 9.530 10.33 11.26 12.72
20 7.700 8.154 8.827 9.402 10.05 11.04 11.91 12.92 14.49
25 10.88 11.44 12.26 12.96 13.74 14.92 15.96 17.15 18.99
30 14.24 14.90 15.86 16.67 17.57 18.94 20.13 21.49 23.56
35 17.75 18.49 19.58 20.50 21.52 23.05 24.39 25.91 28.19
40 21.37 22.19 23.40 24.42 25.55 27.24 28.72 30.38 32.87
45 25.08 25.98 27.31 28.42 29.65 31.50 33.10 34.89 37.57
50 28.86 29.85 31.28 32.48 33.81 35.80 37.52 39.45 42.31
60 36.62 37.75 39.38 40.75 42.27 44.53 46.48 48.65 51.84
70 44.57 45.83 47.66 49.19 50.88 53.39 55.55 57.95 61.43
80 52.68 54.07 56.07 57.75 59.60 62.35 64.71 67.31 71.08
90 60.92 62.42 64.60 66.42 68.42 71.40 73.94 76.74 80.76
100 69.26 70.87 73.21 75.17 77.31 80.51 83.22 86.21 90.48
125 90.47 92.35 95.07 97.33 99.82 103.5 106.6 110.1 114.9
150 112.1 114.2 117.3 119.8 122.6 126.8 130.3 134.1 139.4
175 134.0 136.3 139.7 142.5 145.6 150.2 154.0 158.2 163.9
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-37Engineering ACD Applications with Data Obtained from the BCMS Reports
6
200 156.2 158.7 162.4 165.5 168.8 173.8 177.9 182.4 188.6
225 178.5 181.3 185.2 188.5 192.1 197.5 201.9 206.7 213.3
250 201.0 203.9 208.2 211.7 215.6 221.3 226.0 231.1 238.0
275 223.7 226.8 231.3 235.0 239.1 245.1 250.2 255.5 262.7
300 246.4 249.7 254.4 258.4 262.7 269.1 274.4 280.0 287.5
400 338.4 342.3 347.9 352.6 357.8 365.3 371.6 378.2 386.7
500 431.4 435.9 442.3 447.7 453.6 462.2 469.3 476.7 486.2
600 525.1 530.1 537.3 543.4 549.9 559.5 567.3 575.5 585.7
700 619.4 624.9 632.8 639.4 646.6 657.1 665.6 674.5 685.4
800 714.2 720.1 728.7 735.8 743.6 754.9 764.1 773.5 785.1
900 809.3 815.7 824.9 832.5 840.8 852.9 862.7 872.7 884.8
1000 904.7 911.5 921.3 929.4 938.2 951.1 961.5 972.0 984.6
1100 1000 1008 1018 1026 1036 1049 1060 1071 1084
1200 1096 1104 1115 1124 1134 1148 1159 1171 1184
1300 1192 1200 1212 1221 1231 1246 1258 1270 1284
1400 1289 1297 1309 1319 1329 1345 1357 1370 1384
1500 1385 1394 1406 1416 1427 1444 1456 1469 1484
1600 1482 1490 1503 1514 1526 1542 1556 1569 1584
1700 1578 1587 1601 1612 1624 1641 1655 1668 1684
Table 6-12. ACD Trunk Engineering — Continued
Blocking Probability
trunks 0.01% 0.02% 0.05% 0.10% 0.20% 0.50% 1.00% 2.00% 5.00%
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Use of BCMS Reports for ACD Planning
6-38Engineering ACD Applications with Data Obtained from the BCMS Reports
6
BCMS/CentreVu CMS Report Heading Comparison
A-1Summary of Differences
A
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
A
BCMS/CentreVu CMS Report
Heading Comparison
The following is a comparison of reports and report headings for BCMS and
CentreVu
Call Management System (CMS). The attachments detail each column
from each BCMS report, its corresponding column from a standard
CentreVu
CMS report (or a database item in the
CentreVu
CMS database or a calculation, if
no corresponding column appears in a standard
CentreVu
CMS report) and
present notes on any differences between the two.
NOTE:
CentreVu
CMS is not supported on the DEFINITY BCS or GuestWorks
offers.
Summary of Differences
The following are the primary differences between the BCMS report items and
those in
CentreVu
CMS:
1. Names of measured entities on the switch are limited to 27 characters. On
CentreVu
CMS, they are limited to 20 characters. (Note that both systems
may truncate names to fit on some reports.)
2. Almost all database items in
CentreVu
CMS are call-based rather than
interval-based. This means that almost all data for a call is recorded in the
interval in which the call and any associated after call work completed. In
BCMS, most items are recorded when the call itself completes (not
following after call work), except for transfers, which are recorded when the
transfer takes place, i.e., when the agent pushes the transfer button for the
second time. In fact, half of the call ends with the transfer and is recorded
at that point (since one of the facilities goes away on a transfer).
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-2Summary of Differences
A
3. The system supports “ring” state when reporting on ACD calls to the
CentreVu
CMS.
CentreVu
CMS tracks the time that calls spend ringing and
will show an agent with a call ringing as being in the “ring” state, on
real-time reports. BCMS receives notification when a call is ringing at the
agent’s terminal and puts the agent into the “Other” state in real-time
reports. It does not have a “ring” state nor does it explicitly track the time
calls spend ringing at agents’ terminals.
4.
CentreVu
CMS collects both interval-based and call-based after call work
time. The interval-based ACW time includes any time in ACW not
associated with a call (The agent pushed the ACW button while not on an
ACD call.), as well as call-related ACW time. The call-based ACW time
includes only ACW time associated with a call.
CentreVu
CMS agent
reports that show the time agents spent in the various work states display
interval-based ACW time.
CentreVu
CMS split and VDN reports that show
average after call work time use the call-based ACW time to calculate the
average.
BCMS historical reports display the equivalent of interval-based ACW time,
i.e., the ACW time reported includes both call-related and non-call related
ACW time. The “monitor system” (BCMS System Status) report displays
only call-related ACW time.
5. The BCMS real-time agent report shows the
clock time
at which the agent
entered the current work state.
CentreVu
CMS real-time agent reports
show the
elapsed time
the agent has spent in the current work state.
6.
CentreVu
CMS does not include direct agent ACD calls with split ACD calls
on split reports. BCMS does include direct agent ACD calls in ACD CALLS
on split reports.
7.
CentreVu
CMS records dequeues for calls that dequeue from non-primary
splits in a VDN. BCMS does not display a count of dequeued calls in any
reports, however dequeued calls do count as calls offered to the split and
thus have an effect on the percent within service level calculation for the
split.
8. BCMS reports hold time only for ACD calls.
CentreVu
CMS reports hold
time for ACD calls on split reports, but reports hold time for ACD and
extension calls in agent reports.
NOTE:
If you are viewing CMS reports using CentreVu Supervisor, the report
headings may be slightly different.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-3Summary of Differences
A
Table A-1. BCMS Agent Status (Real-Time) Report
BCMS
Column Description CMS Report
CMS Column/DB
Item CMS Notes
Split Split number Split Status Split name or number
Split Name Split name Split Status Split name or number
Calls Waiting ACD/DA calls
waiting Split Status Calls Waiting ACD calls only
Oldest Call time oldest
ACD/DA call
waited
Split Status Oldest Call Waiting time oldest ACD call
waited
Staffed agts logged into
split Split Report Agents Staffed
Avail agts available in
split Split Report Agents Available
ACD agts on ACD/DA
calls for split Split Report Agents ACD Calls ACD calls only
ACW agts in ACW for
ACD/DA calls Split Report Agents After Call
Work
AUX agts in AUX for
split Split Report Agents Aux Work
Extn agents on extn
calls; these
agents are also
counted in ACW
and AUX
ONACWIN
+ONAUXIN
+ONACWOUT
+ONAUXOUT
Not on std CentreVu
CMS RT reports
Other agts on ACD or in
ACW for another
split, with calls
ringing or calls on
hold
Split Report Agents Other includes agents on DA
calls
AGENT name or extn Agent Report Agent Name
LOGIN ID agent login ID Agent Report Login ID
EXT agent extension Agent Report Extn
STATE Avail, ACD, ACW,
AUX, Ext In, Ext
Out, Other,INIT
Agent Report State CMS states: AVAIL,
ACDIN,ACDOUT,
ACW,ACWIN,
ACWOUT,AUX,
AUXIN,AUXOUT,
DACD,DACW,RING,
UNKNOWN,OTHER
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-4Summary of Differences
A
TIME clock time agent
entered state Agent Report Time elapsed time in state
ACD CALLS number in/out
ACD + DA calls
completed
ACDCALLS +
DA-ACD CALLS Not on standard
CentreVu CMS RT
reports
EXT IN
CALLS extension in calls
completed ACWINCALLS+
AUXINCALLS Not on standard
CentreVu CMS RT
reports
EXT OUT
CALLS extension out
calls completed ACWOUTCALLS+
AUXOUTCALLS Not on standard
CentreVu CMS RT
reports
Table A-1. BCMS Agent Status (Real-Time) Report — Continued
BCMS
Column Description CMS Report
CMS Column/DB
Item CMS Notes
Continued on next page
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-5Summary of Differences
A
Table A-2. BCMS System Status (real-time) Report/CentreVu CMS Real-time Split
Report
BCMS Column Description
CMS Column/DB
Item CMS Notes
SPLIT Split name or ext Split
CALLS WAIT ACD and DA calls
waiting Calls Waiting ACD calls only
OLDEST CALL time oldest ACD/DA
call has waited Oldest Call Waiting ACD calls only
AVG SPEED ANS avg speed of ans for
ACD/DA calls Avg Speed of Answer ACD calls only
AVAIL AGENT avail agts Agents Available
ABAND CALLS ACD/DA calls
abandoned from
queue or ringing
Abandoned Calls ACD calls only
AVG ABAND TIME avg time for ACD/DA
calls to abandon Avg Time to Abandon ACD calls only
ACD CALLS ACD/DA calls
completed Split ACD Calls ACD calls only
AVG TALK TIME avg talk time for
ACD/DA calls Avg Split ACD Talk
Time ACD calls only
AVG AFTER CALL avg ACW time for
ACD/DA calls for
call-related ACW
Not on standard
CentreVu CMS RT
reports
% IN SERV LEVL % calls answered
within service level %Within Service
Level on Queue/Agent
Summary and Call
Profile repts
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-6Summary of Differences
A
Table A-3. BCMS VDN Status Report / CentreVu CMS VDN Report
BCMS Column Description CMS Column/DB Item CMS Notes
VDN NAME VDN name or extension VDN name or number
CALLS WAIT calls waiting in VDN Calls Wait
OLDEST CALL time oldest call has
waited Oldest Call
ACD CALLS completed ACD/DA calls ACD Calls
AVG SPEED ANS avg speed of answer for
ACD and connect calls Avg Speed Answer
ABAND CALLS VDN calls that
abandoned Calls Aban
AVG ABAND TIME avg time for VDN calls to
abandon Aban Time
AVG TALK/HOLD avg time ACD caller
spent talking and on hold Avg ACD Talk CMS number does
not contain hold time
CONN CALLS calls routed to station,
attendant or annc and
answered there
CONNECTCALLS not on standard
CentreVu CMS RT
report
FLOW OUT calls routed to another
VDN or to a trunk VDN Flow Out
CALLS
BUSY/DISC calls that executed busy
or disconnect step Busy/Disc
% IN SERV LEVL % ACD and connect calls
answered within service
level
% Within Service Level on VDN Call Profile
rept
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-7Summary of Differences
A
Table A-4. BCMS Agent Report / CentreVu CMS Agent Summary
BCMS Column Description
CMS Column/DB
Item CMS Notes
Agent Agent extn or Login
ID Agent Name login ID if no name
ACD CALLS ACD/DA calls
completed for all
splits
ACD Calls
AVG TALK TIME avg time talking on
ACD/DA calls, all
splits
Avg Talk Time
TOTAL AFTER CALL Total ACW time for
ACD/DA calls and
non-call related ACW;
includes time on extn
calls
I_ACWTIME
TOTAL AVAIL TIME time avail in at least
one split Agent Time Avail
TOTAL AUX/OTHER time in AUX in ALL
splits and time on
AUX extn calls; does
include “Other” time,
ringing time
Agent Time AUX does not include time
ringing, in other
EXTN CALLS in/out extn calls
completed Extn In Calls, Extn
Out Calls CMS has two
columns
AVG EXTN TIME avg time on extn calls Avg Extn In Talk
Time, Avg Extn Out
Talk Time
CMS has two
columns
TOTAL TIME
STAFFED total time staffed in
any split Agent Time Staff
TOTAL HOLD TIME time ACD calls on
hold HOLDTIME ACD and personal
calls
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-8Summary of Differences
A
Table A-5. BCMS Split Summary / CentreVu CMS Split Summary
BCMS Column Description
CMS
Column/DB
Item CMS Notes
Split split number Split name or number
Split Name split name or extn Split name or number
ACD CALLS ACD/DA calls completed by this
split ACD Calls ACD calls only
AVG SPEED ANS avg speed of ans for ACD/DA
calls Avg Speed Ans ACD calls only
ABAND CALLS ACD/DA calls abandoned for
this split Aban Calls ACD calls only
AVG ABAND TIME avg time to abandon for
ACD/DA calls Avg Aban Time ACD calls only
AVG TALK TIME avg talk time for ACD/DA calls Avg Talk Time ACD calls only
TOTAL AFTER
CALL total ACW time for ACD/DA calls
and non-call related ACW I_ACWTIME for ACD calls and
non-call related ACW
FLOW IN calls split accepted as coverage
pt, or call-forwarded
(non-vectoring); calls answered
by non-primary split (vectoring).
Must have outflowed from a
BCMS-measured split.
Flow In
FLOW OUT calls split extends to its
coverage pt, which call-forward
out or are answered via call
pickup (non-vectoring); calls that
dequeue (and are not
answered) from primary split’s
queue (vectoring)
Flow Out
TOTAL
AUX/OTHER time agents spent in AUX,
including “Other” time I_AUXTIME other time not
included
AVG STAFF avg # people staffed during
period Avg Pos Stf
% IN SERV LEVL % calls answered within service
level % Within Service
Level on Split Status report
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-9Summary of Differences
A
Table A-6. BCMS Trunk Group Summary / CentreVu CMS Trunk Group Summary
Report
BCMS Column Description
CMS Column/DB
Item CMS Notes
Group trunk group number Trunk group name or number
Group Name trunk group name Trunk group name or number
Number of Trunks trunks in group Number of trunks
INCOMING CALLS incoming calls carried Inbound Calls Carr
INCOMING ABAND incoming calls
abandoned Inbound Calls Aban
INCOMING TIME avg holding time,
incoming calls Inbound Avg Trk
Holding Time
INCOMING CCS total holding time in CCS,
incoming calls Inbound Total CCS
OUTGOING CALLS outgoing calls carried Outbound Calls Carr
OUTGOING COMP outgoing calls answered Outbound Far End
Comp
OUTGOING TIME avg holding time,
outgoing calls Outbound Avg Trk
Holding Time
OUTGOING CCS total holding time in CCS,
outgoing calls Outbound Total CCS
% ALL BUSY % time all trunks in tk gp
busy % Time All Trunks
Busy
% TIME MAINT % time trunks busied out
for maint % Time Maint Busy
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
BCMS/CentreVu CMS Report Heading Comparison
A-10Summary of Differences
A
Table A-7. BCMS VDN Summary / CentreVu CMS VDN Report
BCMS Column Description CMS Column(s) CMS Notes
VDN Ext VDN extension VDN name or number
VDN Name VDN name or extension VDN name or number
CALLS OFFERED calls that used the VDN Calls Offered
ACD CALLS ACD/DA calls answered by
agent; for “queue to main”
and “check backup” only
Calls Ans includes calls from
“queue to main”, “check
backup”, “route to”
split/skill, “messaging
split/skill” and “adjunct
routing”
AVG SPEED ANS avg speed ans for ACD/DA
calls Avg Speed Ans
ABAND CALLS calls abandoned from VDN
from “queue to main” and
“check backup” only
Calls Aban includes calls from
“queue to main”, “check
backup”, “route to”
split/skill, “messaging
split/skill” and “adjunct
routing”
AVG ABAND TIME avg time in VDN before
abandon Avg Aban Time
AVG TALK/HOLD avg talk time on ACD/DA
calls, including time on
hold
Avg Talk Time excludes time on hold
CONN CALLS calls routed to station,
attendant, annc, call
pickup, or messaging split,
and answered there
Other Calls
Connect
FLOW OUT calls that execute “route
to”, “messaging split” or
“adjunct routing”
successfully
VDN Flow Out calls that route to
external or VDN only
CALLS
BUSY/DISC calls forced busy or
disconnected Calls Forced Busy,
Calls Forced Disc
% IN SERV LEVL % ACD and connect calls
answered within service
level
% Within Service
Level on VDN Status rept
References
B-1Basic DEFINITY ECS documents
B
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
B
References
This chapter contains a list of user documents for the DEFINITY Enterprise
Communications Server (ECS) Release 7. (Most of these documents are
backward compatible with, and can be used with, the DEFINITY ECS Release 6
systems.)
To order these or other DEFINITY documents, contact the Lucent Technologies
Publications Center at the address and phone number on the back of the title
page of this document. A complete catalog of Business Communications Systems
(BCS) documents, including previous issues of the documents listed here, is
available on the World Wide Web. Ask your account team for the web address.
Basic DEFINITY ECS documents
These documents are issued for all new and upgrade DEFINITY ECS Release 7
systems.
Administration
The primary audience for these documents consists of customer administrators.
DEFINITY ECS Release 7 — Overview, 555-230-024, Issue 7
Provides a brief description of the features available with DEFINITY ECS R7. This
book does not provide a general overview of the switch nor of basic telephony.
This book is available in the following languages: English, German (DE), Dutch
(NL), Brazilian Portuguese (PTB), European French (FR), Latin Spanish (SPL),
Italian (IT), Russian (RU), and Japanese (JA). To order, append the language
suffix to the document number; for example, 555-230-024DE for German. No
suffix is needed for the English version.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-2Basic DEFINITY ECS documents
B
DEFINITY ECS Release 7 — Administrator’s Guide, 555-233-502, Issue 1
A task-based document that provides step-by-step procedures for administering
the switch. This book contains information previously found in DEFINITY ECS
Administration and Feature Description, 555-230-522, as well as new information
for this release and procedural sections added in Release 7.
DEFINITY ECS Release 7.1 — Change Description, 555-230-405, Issue 1
Provides a high-level overview of what is new in DEFINITY ECS R7.1. Describes
the hardware and software enhancements and lists the problem corrections for
this release. It also includes any last-minute changes that come in after the
remaining books have gone to production.
DEFINITY ECS Release 7 — System Description Pocket Reference,
555-230-211, Issue 4
Provides hardware descriptions, system parameters, listing of hardware required
to use features, system configurations, and environmental requirements.
DEFINITY System’s Little Instruction Book for basic administration,
555-230-727, Issue 5
Provides step-by-step procedures for performing basic switch administration
tasks. Includes managing phones, managing features, routing outgoing calls, and
enhancing system security.
DEFINITY System’s Little Instruction Book for advanced administration,
555-233-712, Issue 2
Provides step-by-step procedures for managing trunks, managing hunt groups,
setting up night service, writing vectors, recording announcements, using reports,
and understanding call centers.
DEFINITY System’s Little Instruction Book for basic diagnostics,
555-230-713, Issue 2
Provides step-by-step procedures for baselining your system, solving common
problems, reading alarms and errors, using features to troubleshoot your system,
and contacting Lucent.
DEFINITY ECS Release 7 — Reports, 555-230-511, Issue 5
Provides detailed descriptions of the measurement, status, security, and recent
change history reports available in the system and is intended for administrators
who validate traffic reports and evaluation system performance. Includes
corrective actions for potential problems.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-3Basic DEFINITY ECS documents
B
BCS Products Security Handbook, 555-025-600, Issue 6
Provides information about the risks of telecommunications fraud and measures
for addressing those risks and preventing unauthorized use of BCS products. This
document is intended for telecommunications managers, console operators, and
security organizations within companies.
DEFINITY ECS Release 7 — System 75 and System 85 Terminals and
Adjuncts Reference, 555-015-201, Issue 10
Provides drawings and full descriptions for all phones, phone adjuncts, and data
terminals that can be used with System 75, System 85, DEFINITY
Communications System, and DEFINITY ECS. This document is intended for
customers and Lucent Technologies account teams for selecting the correct
equipment.
Guide Builder™ Software for DEFINITY® Telephones, 555-230-755
Provides the ability to produce laser-printed documentation for specific
telephones. A comprehensive user’s guide and on-line help support the software.
This information applies to Release 7 as well as earlier DEFINITY systems. All
customers receive this software.
Installation and maintenance
DEFINITY ECS Release 7 — Administration for Network Connectivity,
555-233-501, Issue 1
Describes the main types of switch-to-switch connections that use OverLAN
hardware and software, and the procedures required to administer these
connections.
DEFINITY ECS Release 7 — Installation and Test for Single-Carrier Cabinets,
555-230-894, Issue 4
Provides procedures and information for hardware installation and initial testing of
single-carrier cabinets. This book is available in the following languages: English,
German (DE), Dutch (NL), Brazilian Portuguese (PTB), European French (FR),
Latin Spanish (SPL), Italian (IT), Russian (RU), and Japanese (JA). To order,
append the language suffix to the document number; for example,
555-230-894DE for German. No suffix is needed for the English version.
DEFINITY ECS Release 7 — Installation and Test for Multi-Carrier Cabinets,
555-230-112, Issue 6
Provides procedures and information for hardware installation and initial testing of
multi-carrier cabinets.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-4Basic DEFINITY ECS documents
B
DEFINITY ECS Release 7 — Installation for Adjuncts and Peripherals,
555-230-125, Issue 5
Provides procedures and information for hardware installation and initial testing of
ECS adjunct and peripheral systems and equipment.
DEFINITY ECS Release 7 — Installation, Upgrades and Additions for
Compact Modular Cabinets, 555-230-128, Issue 4
Provides procedures and information for hardware installation and initial testing of
compact modular cabinets.
DEFINITY ECS Release 7 — ATM Installation, Upgrades, and Administration,
555-233-106, Issue 1
Provides step-by-step instructions for how to install, upgrade, and administer ATM
switches.
DEFINITY ECS Release 7 — Installation and Maintenance for Survivable
Remote EPN, 555-233-102, Issue 2
Describes how to install, cable, test, and perform maintenance on a Survivable
Remote Expansion Port Network (SREPN). Provides power, ground, and fiber
connections.
DEFINITY ECS Release 7 — Upgrades and Additions for R7r, 555-230-121,
Issue 5
Provides procedures for an installation technician to upgrade an existing
DEFINITY Communications System or DEFINITY ECS to DEFINITY ECS
Release 7.
Includes upgrade considerations, lists of required hardware, and step-by-step
upgrade procedures. Also includes procedures to add control carriers, switch
node carriers, port carriers, circuit packs, auxiliary cabinets, and other equipment.
DEFINITY ECS Release 7 — Upgrades and Additions for R7si, 555-233-104,
Issue 1
Provides procedures for an installation technician to upgrade an existing
DEFINITY Communications System or DEFINITY ECS to DEFINITY ECS
Release 7.
Includes upgrade considerations, lists of required hardware, and step-by-step
upgrade procedures. Also includes procedures to add control carriers, switch
node carriers, port carriers, circuit packs, auxiliary cabinets, and other equipment.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-5Basic DEFINITY ECS documents
B
DEFINITY ECS Release 7 — Maintenance for R7r, 555-230-126, Issue 4
Provides detailed descriptions of the procedures for monitoring, testing,
troubleshooting, and maintaining the R7r ECS. Included are maintenance
architecture, craft commands, step-by-step trouble-clearing procedures, the
procedures for using all tests, and explanations of the system’s error codes.
DEFINITY ECS Release 7 — Maintenance for R7si, 555-233-105, Issue 1
Provides detailed descriptions of the procedures for monitoring, testing,
troubleshooting, and maintaining the R7si ECS. Included are maintenance
architecture, craft commands, step-by-step trouble-clearing procedures, the
procedures for using all tests, and explanations of the system’s error codes.
DEFINITY ECS Release 7 — Maintenance for R7csi, 555-230-129, Issue 4
Provides detailed descriptions of the procedures for monitoring, testing,
troubleshooting, and maintaining the R7csi (Compact Modular Cabinet) ECS.
Included are maintenance architecture, craft commands, step-by-step
trouble-clearing procedures, the procedures for using all tests, and explanations
of the system’s error codes.
Call center documents
These documents are issued for DEFINITY ECS Call Center applications. The
intended audience is DEFINITY ECS administrators.
DEFINITY
DEFINITY ECS Release 7 — Guide to ACD Call Centers, 555-233-503, Issue 1
This module contains information about the call center-specific features of the
DEFINITY ECS. This information was previously contained in DEFINITY ECS
Administration and Feature Description.
DEFINITY ECS Release 7 — Call Vectoring/EAS Guide, 555-230-521, Issue 2
Provides information on how to write, use, and troubleshoot vectors, which are
command sequences that process telephone calls in an Automatic Call
Distribution (ACD) environment.
It is provided in two parts: tutorial and reference. The tutorial provides
step-by-step procedures for writing and implementing basic vectors. The
reference includes detailed descriptions of the call vectoring features, vector
management, vector administration, adjunct routing, troubleshooting, and
interactions with management information systems (including the Call
Management System).
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-6Basic DEFINITY ECS documents
B
DEFINITY ECS Release 7 — Basic Call Management System (BCMS)
Operations, 555-230-706, Issue 1
Provides detailed instructions on how to generate reports and manage the
system. It is intended for telecommunications managers who wish to use Basic
Call Management System (BCMS) reports and for system managers responsible
for maintaining the system. This documentation applies to Release 7 as well as
earlier DEFINITY systems.
CentreVu CMS
The following documents provide information about administration and use of the
CentreVu Call Management System.
CentreVu Call Management System Release 3 Version 6— Administration,
Issue 1, 585-215-850
CentreVu Supervisor Version 6 — Reports, 585-215-851, Issue 1
CentreVu Call Management System Release 3 Version 5 — Custom Reports,
585-215-822, Issue 1
CentreVu Call Management System Release 3 Version 6 — Upgrades and
Migrations, 585-215-856, Issue 1
CentreVu Call Management System Release 3 Version 6 — External Call
History Interface, 585-215-854, Issue 1
CentreVu Call Management System Release 3 Version 5 — Forecast,
585-215-825, Issue 1
CentreVu CMS R3V6 — Planning, Configuration, and Implementation,
585-215-879, Issue 1
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-7Basic DEFINITY ECS documents
B
Application-specific documents
These documents support specific DEFINITY documents.
ASAI
DEFINITY Communications System G3 — CallVisor ASAI Planning Guide,
555-230-222, Issue 4
Provides procedures and directions for the account team and customer personnel
for effectively planning and implementing the CallVisor Adjunct/Switch Application
Interface (ASAI) PBX-Host environment. The CallVisor ASAI is a communications
interface that allows adjunct processors to access switch features and to control
switch calls. It is implemented using an Integrated Services Digital Network
(ISDN) Basic Rate Interface (BRI). Hardware and software requirements are
included.
DEFINITY ECS Release 6 — CallVisor ASAI Protocol Reference,
555-230-221, Issue 7
Provides detailed layer 3 protocol information regarding the CallVisor
Adjunct/Switch Application Interface (ASAI) for the systems and is intended for
the library or driver programmer of an adjunct processor to create the library of
commands used by the applications programmers. Describes the ISDN message,
facility information elements, and information elements.
DEFINITY ECS Release 6 — CallVisor ASAI Technical Reference,
555-230-220, Issue 7
Provides detailed information regarding the CallVisor Adjunct/Switch Application
Interface (ASAI) for the systems and is intended for the application designer
responsible for building and/or programming custom applications and features.
DEFINITY ECS — CallVisor ASAI DEFINITY LAN Gateway over MAP-D
Installation, Administration, and Maintenance of, 555-230-113, Issue 2
Provides procedures for installation, administration, and maintenance of the
CallVisor Adjunct/Switch Application Interface (ASAI) Ethernet application over
the DEFINITY LAN Gateway and is intended for system administrators,
telecommunications managers, Management Information System (MIS)
managers, LAN managers, and Lucent personnel. The ASAI-Ethernet application
provides ASAI functionality using 10Base-T Ethernet rather than BRI as a
transport media.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-8Basic DEFINITY ECS documents
B
DEFINITY ECS — CallVisor ASAI PC LAN over MAP-D Installation,
Administration, and Maintenance of, 555-230-114, Issue 1
Provides procedures for installation, administration, and maintenance of the
CallVisor Adjunct/Switch Application Interface (ASAI) Ethernet application over
the PC LAN and is intended for system administrators, telecommunications
managers, Management Information System (MIS) managers, LAN managers,
and Lucent personnel. The ASAI-Ethernet application provides ASAI functionality
using 10Base-T Ethernet rather than BRI as a transport media.
DEFINITY ECS Release 6 — CallVisor ASAI Overview, 555-230-225, Issue 2
Provides a general description of Call Visor ASAI.
This document is available in the following languages: English, German (DE),
Dutch (NL), Brazilian Portuguese (PTB), European French (FR), Colombian
Spanish (SPL), and Japanese (JA). To order, append the language suffix to the
document number; for example, 555-230-894DE for German. No suffix is needed
for the English version.
DEFINITY ECS Release 6 — CallVisor PC ASAI Installation and Reference,
555-230-227, Issue 3
Provides procedural and reference information for installers, Tier 3 support
personnel, and application designers.
ACD
DEFINITY Communications Systems G3 — Automatic Call Distribution
(ACD) Agent Instructions, 555-230-722, Issue 5
Provides information for use by agents after they have completed ACD training.
Includes descriptions of ACD features and the procedures for using them.
DEFINITY Communications Systems G3 — Automatic Call Distribution
(ACD) Supervisor Instructions, 555-230-724, Issue 4
Provides information for use by supervisors after they have completed ACD
training. Includes descriptions of ACD features and the procedures for using
them.
Console operations
The primary audience for these documents consists of attendant console users.
DEFINITY ECS Console Operations, 555-230-700, Issue 4
Provides operating instructions for the attendant console. Included are
descriptions of the console control keys and functions, call-handling procedures,
basic system troubleshooting information, and routine maintenance procedures.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-9Basic DEFINITY ECS documents
B
DEFINITY ECS Release 7 — Console Operations Quick Reference,
555-230-890, Issue 3
Provides operating instructions for the attendant console.Included are
descriptions of the console control keys and functions, call-handling procedures,
basic system troubleshooting information, and routine maintenance procedures.
This book is available in the following languages: English, German (DE), Dutch
(NL), Brazilian Portuguese (PTB), European French (FR), Latin Spanish (SPL),
Italian (IT), Russian (RU), and Japanese (JA). To order, append the language
suffix to the document number; for example, 555-230-890DE for German. No
suffix is needed for the English version.
Hospitality
The primary audience for these documents consists of hotel and health care
administrators, and telephone operators at these locations.
DEFINITY ECS Release 7 — Hospitality Operations, 555-230-723, Issue 5
Provides step-by-step procedures for using the features available for the lodging
and health industries to improve their property management and to provide
assistance to their employees and clients. Includes detailed descriptions of
reports.
Non-U.S. audiences
DEFINITY ECS Release 7 — Application Notes for Type Approval
Describes specific hardware and administration required to operate the DEFINITY
ECS in countries outside the United States. Available on the DEFINITY ECS
Release 7 Library CD only.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
References
B-10Basic DEFINITY ECS documents
B
Glossary and Abbreviations
GL-1
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
GL
Glossary and Abbreviations
A
abandoned call
An incoming call in which the caller hangs up before the call is answered.
ACD
See Automatic Call Distribution (ACD).
ACD agent
See agent.
ACW
See after-call work (ACW) mode.
access code
A 1-, 2-, or 3-digit dial code used to activate or cancel a feature, or access an outgoing trunk.
ACD
See
Automatic Call Distribution (ACD). ACD also refers to a work state in which an agent is on an
ACD call.
ACD work mode
See work mode.
active-notification call
A call for which event reports are sent over an active-notification association (communication
channel) to the adjunct. Sometimes referred to as a monitored call.
active notification domain
VDN or ACD split extension for which event notification has been requested.
adjunct-controlled split
An ACD split that is administered to be under adjunct control. Agents logged into such splits must
do all telephony work, ACD login/ logout, and changes of work mode through the adjunct (except for
auto-available adjunct-controlled splits, whose agents may not log in/out or change work mode).
after-call work (ACW) mode
A mode in which agents are unavailable to receive ACD calls. Agents enter the ACW mode to
perform ACD-related activities such as filling out a form after an ACD call.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Glossary and Abbreviations
GL-2
agent
A person who receives calls directed to a split. A member of an ACD hunt group or ACD split. Also
called an ACD agent.
agent report
A report that provides historical traffic information for internally measured agents.
Auto-In Work mode
One of four agent work modes: the mode in which an agent is ready to process another call as soon
as the current call is completed.
Automatic Call Distribution (ACD)
A feature that answers calls, and then, depending on administered instructions, delivers messages
appropriate for the caller and routes the call to an agent when one becomes available.
Automatic Call Distribution (ACD) split
A method of routing calls of a similar type among agents in a call center. Also, a group of extensions
that are staffed by agents trained to handle a certain type of incoming call.
AUX-Work mode
A work mode in which agents are unavailable to receive ACD calls. Agents enter AUX-Work mode
when involved in non-ACD activities such as taking a break, going to lunch, or placing an outgoing
call.
B
BCMS
Basic Call Management System
C
Call Management System (CMS)
An application, running on an adjunct processor, that collects information from an ACD unit. CMS
enables customers to monitor and manage telemarketing centers by generating reports on the
status of agents, splits, trunks, trunk groups, vectors, and VDNs, and enables customers to partially
administer the ACD feature for a communications system.
call vector
A set of up to 32 vector commands to be performed for an incoming or internal call.
call work code
A number, up to 16 digits, entered by ACD agents to record the occurrence of customer-defined
events (such as account codes, social security numbers, or phone numbers) on ACD calls.
CCS or hundred call seconds
A unit of call traffic. Call traffic for a facility is scanned every 100 seconds. If the facility is busy, it is
assumed to have been busy for the entire scan interval. There are 3600 seconds per hour. The
Roman numeral for 100 is the capital letter C. The abbreviation for call seconds is CS. Therefore,
100 call seconds is abbreviated CCS. If a facility is busy for an entire hour, then it is said to have
been busy for 36 CCS. See also Erlang.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Glossary and Abbreviations
GL-3
CMS
Call Management System
CWC
See call work code.
D
DIVA
Data In/Voice Answer
DNIS
Dialed-Number Identification Service
direct agent calling
An Expert Agent Selection (EAS) capability that makes it possible for a caller to reach the same
agent every time and still include the call in the managment tracking of the call center. This is ideal
for claims processing where a client need to speak with the agent handling the claim. This felxibility
ensures a high level of customer service without reducing management control.
domain
VDNs, ACD splits, and stations. The VDN domain is used for active-notification associations. The
ACD-split domain is for active-notification associations and domain-control associations. The
station domain is used for the domain-control associations.
E
Erlang
A unit of traffic intensity, or load, used to express the amount of traffic needed to keep one facility
busy for one hour. One Erlang is equal to 36 CCS. See also CCS or hundred call seconds.
extension-in
Extension-In (ExtIn) is the work state agents go into when they answer (receive) a non-ACD call. If
the agent is in Manual-In or Auto-In and receives an extension-in call, it is recorded by CMS as an
AUX-In call.
extension-out
The work state that agents go into when they place (originate) a non-ACD call.
external measurements
Those ACD measurements that are made by the External CMS adjunct.
I
ICM
Inbound Call Management
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Glossary and Abbreviations
GL-4
internal measurements
BCMS measurements that are made by the system. ACD measurements that are made external to
the system (via External CMS) are referred to as external measurements.
INADS
Initialization and Administraiton System
L
LDN
Listed directory number
M
Manual-In work mode
One of four agent work modes: the mode in which an agent is ready to process another call
manually.
See
Auto-In Work mode for a contrast.
MMCH
Multimedia call handling
O
OCM
Outbound Call Management
offered load
The traffic that would be generated by all the requests for service occurring within a monitored
interval, usually one hour.
OQT
Oldest queued time
othersplit
The work state that indicates that an agent is currently active on another split’s call, or in ACW for
another split.
P
POE
Processor occupancy evaluation
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Glossary and Abbreviations
GL-5
Q
queue
An ordered sequence of calls waiting to be processed.
queuing
The process of holding calls in order of their arrival to await connection to an attendant, to an
answering group, or to an idle trunk. Calls are automatically connected in first-in, first-out sequence.
R
Redirection on No Answer
An optional feature that redirects an unanswered ringing ACD call after an administered number of
rings. The call is then redirected back to the agent.
report scheduler
Software that is used in conjunction with the system printer to schedule the days of the week and
time of day that the desired reports are to be printed.
S
SAT
System access terminal
split
A group of ACD agents.
split condition
A condition whereby a caller is temporarily separated from a connection with an attendant. A split
condition automatically occurs when the attendant, active on a call, presses the start button.
split number
The split’s identity to the switch and BCMS.
split report
A report that provides historical traffic information for internally measured splits.
split (agent) status report
A report that provides real-time status and measurement data for internally measured agents and
the split to which they are assigned.
staffed
Indicates that an agent position is logged in. A staffed agent functions in one of four work modes:
Auto-In, Manual-In, ACW, or AUX-Work.
stroke counts
A method used by ACD agents to record up to nine customer-defined events per call when CMS is
active.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Glossary and Abbreviations
GL-6
system administrator
The person who maintains overall customer responsibility for system administration. Generally, all
administration functions are performed from the Management Terminal. The switch requires a
special login, referred to as the system administrator login, to gain access to system-administration
capabilities.
system printer
An optional printer that may be used to print scheduled reports via the report scheduler.
system report
A report that provides historical traffic information for internally measured splits.
system-status report
A report that provides real-time status information for internally measured splits.
system manager
A person responsible for specifying and administering features and services for a system.
U
UCD
Uniform call distribution
V
VDN
See vector directory number (VDN).
vector directory number (VDN)
An extension that provides access to the Vectoring feature on the switch. Vectoring allows a
customer to specify the treatment of incoming calls based on the dialed number.
vector-controlled split
A hunt group or ACD split administered with the vector field enabled. Access to such a split is
possible only by dialing a VDN extension.
W
work mode
One of four states (Auto-In, Manual-In, ACW, AUX-Work) that an ACD agent can be in. Upon
logging in, an agent enters AUX-Work mode. To become available to receive ACD calls, the agent
enters Auto-In or Manual-In mode. To do work associated with a completed ACD call, an agent
enters ACW mode.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Glossary and Abbreviations
GL-7
work state
An ACD agent may be a member of up to three different splits. Each ACD agent continuously
exhibits a work state for every split of which it is a member. Valid work states are Avail, Unstaffed,
AUX-Work, ACW, ACD (answering an ACD call), ExtIn, ExtOut, and OtherSpl. An agent’s work
state for a particular split may change for a variety of reasons (example: when a call is answered or
abandoned, or the agent changes work modes). The BCMS feature monitors work states and uses
this information to provide BCMS reports.
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Glossary and Abbreviations
GL-8
Index
IN-1
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
IN
Index
A
acceptable service level
administration of,1-5
definition,1-4
ACD
definition of parameters,1-8
determine how it is functioning,6-2
engineering of
interpolation method,6-5
using BCMS reports,6-5
example application
classified ads department,6-8
insurance agency,6-35
reservations department,6-8
split management,6-9
managing operations with BCMS,1-1
monitoring the operations of an application,1-1
optimization of,6-5
overall design criteria,6-2
planned future growth,6-5
planning,6-1
when excessive time in answering calls,6-3
ACD feature,6-1
ACD planning
agent engineering/optimizing guidelines,6-6
planning/engineering objectives,6-1
ACD trunk engineering
table,6-36
Agent Report
example screen,4-18
Agent Summary Report
example screen,4-22
example summary,4-23
agents
changing their schedule,6-4
determine how time utilized,6-4
determining required number,6-7
determining when to add more to a split,6-3
evaluating time spent answering ExtnCalls,6-3
evaluating when more training needed,6-4
measured by Login IDs,1-2
measured by physical extension,1-2
placing in multiple splits,6-4
when to add more,6-5
average amount of time
for incoming calls,6-4
for outgoing calls,6-4
average length of time
before a call abandons the queue,6-2
taken before the ACD calls are answered,6-2
the agents spend in ACW mode,6-2
the agents spend talking,6-2
average service time
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Index
IN-2
table,6-12, 6-14, 6-16, 6-18, 6-20, 6-22, 6-24, 6-26, 6-28, 6-30, 6-32
AVG ABAND TIME field,6-5
AVG TALK TIME field,6-4, 6-7
B
BCMS
capacities,1-6
changing password,2-5
collection of data,4-1
compare report headings with CMS,A-1
data loss during software upgrades,1-3
description of,1-1
feature,1-2
interactions with external CMS,1-8
interactions with VuStats feature,1-8
login,2-2
password,2-2
changing,2-5
reports,1-2
how to access,2-1
list of primary differences from CMS reports,A-1
storage of data,1-3
terminal configurations for logging in,2-2
type of reports
list,1-2
monitor reports,1-2
BCMS Agent Report
ACD planning,6-4
example screen,4-18
purpose,4-17, 6-4
table of differences with CMS Reports,A-7
BCMS Agent Summary Report
example screen,4-22, 4-23
purpose,4-22
BCMS commands
table of,4-2
BCMS Login IDs,4-2
BCMS Split or Skill Report,6-7
ACD planning,6-5
example screen,4-28
purpose,6-5
BCMS Split or Skill Status Report,4-3
ACD Planning,6-3
example screen,4-4
purpose,4-3, 6-3
BCMS Split or Skill Summary Report,4-35
example screen,4-36
BCMS Split Report
purpose,4-27
BCMS Split Summary Report
purpose,4-35
BCMS System Status Report,4-8
ACD planning,6-2
description,6-2
example screen,4-9
purpose,4-3, 4-8, 6-2
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Index
IN-3
table of differences with CMS Reports,A-5
BCMS Trunk Group Report,4-42
ACD planning,6-4
example screen,4-43
purpose,6-4
BCMs Trunk Group Report
purpose,4-42
BCMS Trunk Group Summary Report
example screen,4-48
purpose,4-47
BCMS VDN Report,4-53
ACD planning,6-5
example screen,4-53
purpose,4-52, 6-5
BCMS VDN Status Report,4-12
ACD planning,6-3
example screen,4-12
purpose,4-3, 6-3
table of differences with CMS Reports,A-6
BCMS VDN Summary Report
example screen,4-58, 4-59
C
call handling
evaluation of,6-5
capacities
BCMS,1-6
CCS traffic load,6-4
change command,5-9
Change Report-Scheduler
example screen,5-9
Change Report-Scheduler screen
field descriptions,5-9
commands
table of,4-2
Comments,xi
comparing agents’ performances,1-1
conventions used in this document,x
Customer Options form,1-5
D
dial-up access
constraints,2-1
displaying real-time status reports,3-1
Documents,xi
E
EAS feature,1-2
error messages,3-2
evaluating a VDN or vector,6-3
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Index
IN-4
excessive ACD talk time,6-3
expert agent selection feature,1-2
external CMS
interactions with BCMS,1-8
F
Feature-Related System Parameters screen,5-2
form
Customer Options,1-5
Hunt Group,1-5
System-Parameters Customer Options,5-1
VDN,1-5
H
historical reports
definition,4-16
hunt group
collection of data,4-1
Hunt Group form,1-5
I
interpolation equation,6-6
L
length of time that the oldest call has been queued,6-2
list commands
purpose,3-3
listing
scheduled reports,5-7
logging in,2-1, 2-2
from remote terminal,2-3
steps
from local terminal,2-2
logging off,2-1
steps,2-4
M
monitor command
purpose,3-1
Monitor Split Status Report.,6-2
monitoring
the calling volume for each split,1-1
the work load of each agent,1-1
trunk group usage,1-1
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Index
IN-5
VDNs,1-1
N
number of agents available to receive ACD calls,6-2
number of calls
that have abandoned,6-2
that have been answered,6-2
waiting in the queue,6-2
number of incoming and outgoing calls,6-4
number of incoming calls that abandoned,6-4
O
Ordering Documents,xi
P
Password Change screen,2-5
password for BCMS
changing,2-5
PC requirements
for collecting report data,1-3
peak traffic,6-4
percent of time that all trunks within this group are busy,6-4
percent within service level
calculation for hunt groups,1-4
calculation for VDNs,1-4
how calculated,1-4
percentage of calls answered with in service level,6-2
performance,1-8
print intervals,5-4, 5-5
printer
hardware administration,5-2
problem indicators concerning splits,6-2
R
real-time status reports
description,3-1
Related Documents,xi
remove command,5-10
Remove Report Scheduler Command
example screen,5-10
Remove Report Scheduler Command screen,5-10
field descriptions,5-11
Report Scheduler feature,ix, 5-3
adding a report,5-4
change command,5-9
enabling,5-1
field descriptions,5-5
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Index
IN-6
print intervals,5-4
purpose,5-3
remove command,5-10
what it prints,5-1
Report Scheduler form
typical example,5-7
Report Scheduler screen
field descriptions,5-8
reports
adding to Report Scheduler,5-4
BCMS,1-2
BCMS Agent Report,4-17
ACD planning,6-4
BCMS Agent Summary Report,4-22
BCMS Split or Skill Report,4-27
ACD planning,6-5
BCMS Split or Skill Status Report,4-3
ACD planning,6-3
BCMS Split or Skill Summary Report,4-35
BCMS System Status Report,4-8
ACD planning,6-2
BCMS Trunk Group Report,4-42
ACD planning,6-4
BCMS Trunk Group Summary Report,4-47
BCMS VDN Report,4-52
ACD planning,6-5
BCMS VDN Status Report,4-12
ACD planning,6-3
BCMS VDN Summary Report,4-58
changing schedule,5-9
CMS VDN Status Report,4-12
displaying list of scheduled reports,5-7
displaying real-time status reports,3-1
listing scheduled,5-7
maximum number for printing,5-3
maximum per night,6-2
on agents,1-2
on splits,1-2
on trunk groups,1-2
on VDNs,1-2
removing from Report Scheduler,5-10
specifying day and time to print,5-3
steps for printing using Report Scheduler feature,5-6
type of
list reports,1-2
monitor reports,1-2
when scheduled reports can’t be printed,5-1
S
scheduled reports
time and date,5-6
service level
acceptable,1-4
percent within,1-4
setting the field,1-4
Split or Skill Report
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Index
IN-7
example screen,4-28
Split or Skill Status Report,4-3
example screen,4-4
purpose,4-3
Split or Skill Summary Report,4-35
example screen,4-36
splits
backup
when to add more,6-5
identifying busy times,6-5
staffed agents
determining if enough for incoming calls,6-3
system printer,5-1
administering hardware parameters,5-2
assumptions about operation,5-3
data link
maintenance,5-3
operation,5-3
operational states,5-3
minor alarm,5-3
operation different from CDR and journal printer,5-3
paper jams,5-3
parameters,5-1
refill paper bin,5-3
warning alarm,5-3
System Printer Hardware Administration
example screen,5-2
example screen for G3i,5-2
System Status Report,4-8
example screen,4-9
System-Parameters Customer-Options form,5-1
form
System-Parameters Customer-Options,1-5
T
terminal types
for accessing BCMS,2-1
Trunk Group Report,4-42
example screen,4-43
trunks
determining the number required,6-34
guidelines for engineering,6-34
range of typical number,6-34
ratio to number of agents,6-34
when to add more,6-5
V
VDN form,1-5
VDN Report,4-53
example screen,4-53
VDN Status Report,4-12
example screen,4-12
purpose,4-12
DEFINITY Enterprise Communications Server Release 7 Basic Call
Management System (BCMS) Operations
555-230-706 Issue 2
June 1999
Index
IN-8
VDN Summary Report
example screen,4-58, 4-59
vectors
evaluation of performance,6-5
VuStats feature,1-2
description of,1-8

Navigation menu