# Traffic Analysis

This section describes how to interpret the traffic reports in order to obtain numerical data which can be related to equipment provisioning and trunk routing efficiency. Some processing of the data is required in order to evaluate trunk routing efficiency; however, in general, the data is readily interpreted from the traffic reports.

The following topics are discussed here:

- Trunk Reports

- Common Equipment and Data Station Groups Reports

- Attendant Report

- Channels Report

- Evaluating Trunk Routing Efficiency

## Trunk Reports

Trunk Reports include Route Plan, Route List, and Route reports as well as reports of Trunks and Trunk Groups.

The Route Plan report covers all Route Plans programmed in the Automatic Route Selection (ARS) form; the Route List report covers all Route Lists programmed in the ARS; and the Route report covers all Routes programmed in the ARS. In the Route report, a Busy Peg is counted every time a busy condition occurs and also whenever an Overflow peg is registered.

The Trunk Groups report covers all Outgoing Trunk Groups and the Trunk report covers all individual trunks that are programmed. The 'Maximum in Use/ Avl' data field in the Trunk Groups report includes only outgoing trunks in the Maximum in Use count, while the Maximum Available ( Avl) count includes all trunks programmed in the Trunk Group. Trunks that may be in use as incoming trunks, or that may have gone into Maintenance states of Out of Service, Manbusy or Suspect are included in the Maximum Available count, but not in the Maximum in Use count. Therefore, it is possible to have a Busy Peg for a Trunk Group even though the Maximum Available field appears to indicate that there were trunks available.

Sample Traffic Report - Route Related
TRAFFIC REPORT system NAME 1988-DEC-02 13:16 TO 13:31
TRUNKS Route Plan | Route Plan Number | Peg | Usage (CCS) | Busy Peg |  | Busy Peg | Hour Time
| 5 6 7 8 | 91 0 43 58 ---- 192 | 13.09 0.00 5.76 7.92 ----- 26.77 | 32 75 58 50 ---- 215 |  | 506 162 480 441 ----- 1589 | 02:16 13:31 05:46 13:31
Route List | Route List Number | Peg | Usage (CCS) | Busy Peg |  | Busy Peg | Hour Time
| 5 6 7 8 2 3 | 91 0 43 58 0 0 --- 192 | 13.09 0.00 5.76 7.92 0.00 0.00 ----- 26.77 | 32 75 58 50 0 0 --- 215 |  | 506 162 480 441 ----- 1589 | 02:16 13:31 05:46 13:31
Routes | Route Number | Peg | Usage (CCS) | Busy Peg | Overflow | Busy Peg | Hour Time
Routes | 3 6 20 46 1 2 | 84 0 20 0 0 0 --- 104 | 22.91 0.00 3.20 0.00 0.00 0.00 ----- 26.11 | 61 0 70 0 0 0 --- 131 | 0 0 70 0 --- 70 | 311 750 508 2 ----- 1571 | 13:31 05:01 07:31 10:01

Route Definitions
Parameter | Definition
Route Plan Number | This column numerically lists all route plans in two categories; plans which were implemented during the period recorded are listed first, followed by a numerical list of the remainder of the route plans.
Peg | This number represents the total number of times the plan was successfully accessed during the period indicated on the report.
Usage | This number (either in Erlangs or CCS) reflects the usage during the current period.
Busy Peg | This number represents the number of times this choice could not be selected due to a busy condition.
Busy Hour - Peg | The busiest hour during traffic collection times is recorded in this field. If the current hour count exceeds the Busy Hour Peg, the Busy Hour Peg would be replaced by the higher count when the report is generated.
Busy Hour - Time | The 60 consecutive minutes within the recorded times during each day in which the traffic load is the highest. The time printed is the ending time of the busy hour.
Route List Number | This numerical record of Route Lists has active lists at the beginning of the report, followed by inactive lists.
Route Number | All routes used during the traffic period will precede the list of available routes which were not selected.
Overflow | The overflow count represents the total number of times during the measurement period a route could not be accessed due to busy conditions, but another route was taken.

Sample Traffic Report - Trunk Related
Trunk Groups
Outgoing Trk Group Number | Trunk Group Label | Peg | Usage (CCS) | Busy Peg | Maximum In Use/ Avl.
20 22 24 28 1 2 4 | E&M TRUN CEPT T1/D4 E& LOOP TRU CO TRUNK | 85 53 0 26 51 0 0 0 | 23.07 7.11 0.00 3.17 7.15 0.00 0.00 0.00 | 61 70 75 75 81 0 0 0 | 3/ 4 1/ 1 0/ 1 0/ 1 1/ 0
|  | 215 | 40.50 | 362 |
Trunks Trunk Number | Trunk Label | Peg in | Usage in (CCS) | Peg Out | Usage Out (CCS)
1 6 XXXX 14 32 BBBB 60 123 200 3 4 7 | E&M TRU E&M TRU E&M TRU E&M TRU LOOP TR CEPT CO TRUN | 1 0 31 0 65 0 0 0 0 0 | 0.33 0.00 8.92 9.03 8.34 0.00 0.00 0.00 0.00 0.00 | 32 45 0 0 0 53 51 0 0 0 | 7.74 0.02 0.00 0.00 0.00 7.12 7.16 0.00 0.00 0.00
|  | 97 | 26.32 | 181 | 22.04

Trunk Definitions
Parameter | Definition
Outgoing Trk Group Number | This column lists the Outgoing Trunk Group numbers in numerical order. Trunk Groups which were active are listed first, followed by Trunk Groups which were not accessed.
Trunk Group Label | This field lists the name of the first trunk in the trunk group.
Peg | This number represents the total number of times this field was successfully accessed during the period indicated on the report.
Usage | This number (either in Erlangs or CCS) reflects the usage during the report period.
Busy Peg | This number represents the number of times a call could not seize a trunk in the group due to a busy condition. If the trunk group is part of an ARS Route List, the busy peg will reflect a count which applies to busy conditions encountered while scanning the Route List.
Maximum In Use/ Avl. | This value represents the greatest number of trunks busy at any one time during the measurement period out of the total number available. Each trunk group has a maximum number of trunks assigned through Customer Data Entry. The maximum number represents the number of available trunks.
Trunk Number | This column lists in numerical order all trunks which were accessed during the measurement period, followed by all trunks which were not accessed.
Trunk Label | Trunk label corresponding to this trunk's TS (Trunk Service) Number.
Peg In | Represents the total number of times the trunk was seized by an incoming call during the measurement period.
Killer Trunk | Term used to define a problem trunk. The trunk is highlighted in traffic reports as a possible Killer Trunk if it registers a high peg number and a low usage (suggesting there could be a problem accessing the trunk), or if the trunk registers a low peg number and a high usage (suggesting the trunk is not releasing properly). A warning ( XXXX or BBBB) is printed on the reports to indicate a suspected Killer Trunk.
BBBB | Printed in the traffic reports, this display highlights a possible Killer Trunk. The trunk has a low peg number and a high usage.
XXXX | Printed in the traffic reports, this display highlights a possible Killer Trunk because of a high peg number but low usage.
Usage In | Represents the usage (in Erlangs or CCS) for incoming calls on the trunk during the measurement period.
Peg Out | Represents the total number of times the trunk was seized by an outgoing call during the measurement period.
Usage Out | Represents the usage (in Erlangs or CCS) for outgoing calls on the trunk during the measurement period.

## Common Equipment and Data Station Groups Reports

Common Equipment and Data Station Groups Reports include reports on DTMF Receivers,.

Sample Traffic Report - Common Equipment Related
COMMON EQUIPMENT
DTMF Receivers
DTMF Group Number 1 | Peg 1101 | Usage (CCS) 181.05 | Busy Peg 0 | Maximum In Use/ Avl. 28/ 96

Common Equipment Definitions
Parameter | Definition
DTMF Group Number | Indicates the Group Number of the DTMF receivers.
Peg | Represents the total number of times that the DTMF receivers were accessed during the measurement period.
Usage | Represents the total usage (Erlangs or CCS) for the DTMF receivers during the measurement period.
Busy Peg | Represents the number of times a call could not be allocated a DTMF receiver, or modem due to a busy condition.
Maximum In Use/ Avl. | This value represents the greatest number of DTMF receivers busy at any one time during the measurement period, out of the total number available.
DTRX Group Number | Indicates the Group Number of the data transceivers.
Data Station Group | Lists the data station hunt groups active during the measurement period by name, if possible, or by pilot number.

## Attendant Report

The Attendant Report includes reports on Attendant Groups, Attendant Consoles, and Attendants. Because all Attendant data is cleared at midnight, every night, attendants logged on at midnight will have their Login Time set to midnight and their Logged in Time set back to zero. As well the Busy Hour data is cleared at midnight. If a traffic period ends at midnight, it will contain the data for that period with the last Busy Hour Time being midnight.

Sample Traffic Report - Attendant Related
ATTENDANT
Attendant Group
Attendant Group 3000 Karen Judy 0 | Calls Answered 45 58 48 40 |  | Calls Abandoned 6 12 7 9 |  | Avg. Waiting Time ( secs.) 12.47 10.10 12.35 9.67 |  | Busy Hour Peg Time 109 13:31 128 13:31 92 13:31 175 13:31
Attendant Consoles
Attendant Console 3000 Karen Judy | Calls Answered 174 5 12 |  | Occupancy (CCS) 2.43 0.09 3.45 |  | Avg. Service Time ( secs.) 1.40 1.83 1.78 |  | Busy Hour Peg Time 288 13:31 16 13:31 20 13:31
Attendants
Attendant Name | Calls Answered | Login Time | Logout Time | Logged In Time | Occupancy (CCS) |  | Busy Hour Peg Time
Karen | 5 | 12:30 |  | 00:45 | 0.09 |  | 16 13:31
Judy | 12 | 12:50 | 13:10 | 00:20 | 3.45 |  | 20 13:31

Attendant Definitions
Parameter | Definition
Attendant Group | Lists the Attendant groups active during the measurement period by name, if possible, or by directory number.
Calls Answered | Represents the total number of calls, both internal and external, processed by the attendant consoles in the Attendant group during the measurement period.
Avg. Waiting Time | The average time (in seconds) an incoming call was waiting before being processed by the attendant or cleared by the calling party. This value is measured from the point where the call initially appears at the console and when the call is actually answered, or cleared.
Busy Hour - Peg | This is the number of calls received during the busiest hour of the day. If the current hour count exceeds the Busy Hour Peg total, the Busy Hour Peg would reflect the higher count when the report is generated. NOTE: For attendant groups, this number equals: calls answered + calls abandoned. For attendant consoles, this number includes only the calls answered.
Busy Hour - Time | The 60 consecutive minutes within the day in which the traffic load is the highest. The time printed is the ending time of the busy hour for an individual attendant, a console or a group.
Attendant Console | This field reports the activity on a per-console basis, regardless of the number of attendants who may have manned it during a report period.
Occupancy | This field reflects the total time during a report period that the console spent processing calls.
Avg. Service Time | Average time the attendant spends processing a call.
Attendant Name | Attendants are identified by the user id entered by the attendants when they log in.
Login and Logout | These fields are independent of the traffic schedules. Traffic periods containing numerous login and logout times will report only the last activity, but reflect the total logged in time in the Logged In Time counter. Logout fields are blank if no logout has occurred during a traffic period.
Logged In Time | This field records the total time the attendant was logged on and available for service.

## Channels Report

The Channels Report includes reports on Transmit Links, Receive Links, Group of Links, and Channels maximum usage.

Sample Traffic Report - Channel Related
CHANNELS |  |  |  |
Transmit Links Link Number 0 1 2 9 12 24 26 47 | Function PER PER PER MC DS1 ATD DTRX PER | Peg 158 158 158 5 91 5 43 332 | Usage (CCS) 282.23 303.79 322.18 82.11 13.47 0.10 1.43 60.13 | Max. Chann Used/Avail. 34/ 32 37/ 32 39/ 32 11/ 16 2/ 32 1/ 32 2/ 32 14/ 32
Group of Links Grp of Links No. 1 2 9 10 11 | Name of Group PER PER DS1 ATD DTRX MC | Peg 3008 688 364 10 86 10 | Usage (CCS) 4663.84 113.86 52.34 0.20 2.87 164.22 | Max. Chann Used/Avail. 540/ 512 28/ 512 10/ 128 2/ 64 4/ 64 22/ 96
Group of Links Grp of Links No. 1 2 9 10 11 | Name of Group PER PER DS1 ATD DTRX MC | Peg 3008 688 364 10 86 10 | Usage (CCS) 4663.84 113.86 52.34 0.20 2.87 164.22 | Max. Chann Used/Avail. 540/ 512 28/ 512 10/ 128 2/ 64 4/ 64 22/ 96
Channels Max. Usage | 5834.60 | Busy Hour | 278884 Time | 02:31

Channel Definitions
Parameter | Definition
Link Number | This field reflects the link number.
Function | Associated function for link (ATD, DTRX, PER, PRE1, PRT1).
Peg | Number of times a link was accessed during a period.
Usage | This value reflects the total usage on the link.
Max. Chann Used/Avail. | This value represents the greatest number of channels busy at any one time during the measurement period out of the total number available.
Grp Of Links No. | This number identifies a peripheral level controller of the system on which a communications path consisting of a group of circuit switch links is terminated.
Name Of Group | Associated function for Link Group (ATD, DTRX, PRE1, PRT1).
Max. Usage | The total of all channels Maximum Channels Used is shown in this field.
Busy Hour | This peg count reflects the total peg for the busiest hour of the day.
Time | The ending time of the busiest hour during traffic data collection. This reflects the current day.

## Evaluating Trunk Routing Efficiency

The usage data obtained for trunk groups and individual trunks may be used to evaluate, primarily, the performance of the Trunk Routes and Route Lists defined through system programming. If the traffic levels on given routes warrant changes to the Routes and/or Route Lists, changes to the customer database are required. Some investigation is required, however, because inefficient trunk routing may be due to such errors as incorrect programming of the Interconnect Restriction Table, Classes of Restriction, Trunk Circuit Descriptors, etc. The following documents should be consulted at this stage: See Automatic Route Selection (for an overview of ARS), Programming Procedures, ARS Routes, ARS Route Lists, and Trunk forms.

## Use of SMDR Data in Traffic Analysis

In order to analyze the nature and frequency of external calls, it may become necessary to obtain and interpret Station Message Detail Recording data. This data will complement traffic reports and will present a detailed and complete record of calls to and from stations in the system.