User Guide

Table Of Contents
DescriptionHistorical Data
In all, therefore, there are eight Interval tables that support fteen-minute reporting
if the system is congured for it. The equivalent Interval tables are populated by
either half-hour or fteen-minute data, based on conguration.
Note: By default, data is captured in 30-minute intervals.
Fields in the Interval tables are no longer appended by ToHalf. For example, the
Agent_Half_Hour table has a eld named AvailTimeToHalf. In the Agent_Interval
table, that eld is named AvailTime.
Interval tables are :
Agent_Interval
Agent_Skill_Group_Interval
Peripheral_Interval
Service_Interval
Skill_Group_Interval
Call_Type_Interval
Call_Type_Skill_Group_Interval
Campaign_Query_Rule_Interval
Note: There is no interval conguration for the Campaign_Query_Rule_Interval
table. Both the Campaign_Query_Interva; table and
theCampaign_Query_Rule_Half_Hour table contain 30-minute data.
Those Half_Hour tables that do not have new Interval tables are populated only
for completed half-hour intervals, and the data elds are stored in the database
Half Hour
with the extension "ToHalf" (for example,
Application_Gateway_Half_Hour.ErrorsToHalf).
These elements contain a value for a completed half-hour interval. The completed
interval is the time period falling between xx:00:00 and xx:29:59, or xx:30:00
and xx:59:59.
For example, if an error occurred at 15:47:00, it will be counted in the 15:30:00
to 15:59:59 half-hour interval. Data for this interval is not written to the database
until the interval is complete (for example 16:00:00). Therefore, the latest error
half-hour data is available for the previous completed interval (that is, the 15:00:00
to 15:29:59).
Report Template Reference Guide For Cisco Unified Intelligence Center Release 8.0(4)
210
Chapter 12: Unified ICM/CCE Reporting Concepts
Historical and Interval Data