Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Use the case analytics data model to analyze case performance, service-level agreement (SLA) performance, and active backlog. Fact tables provide individual case and SLA execution details. Aggregate tables summarize results, and related dimensions let you filter and group the data.
The model differs from the legacy case analytics model described in Data models and report mappings for historical analytics reports.
Aggregate tables
Choose the aggregate that matches your reporting question: case outcomes, SLA KPI executions, or captured backlog.
| Table | Description |
|---|---|
| AggCaseAnalytics | Aggregates case data for volume, response and resolution outcomes, feedback, reopens, and case-level SLA performance. |
| AggCaseSLA | Aggregates SLA KPI executions for SLA performance and attainment analysis across cases. |
| AggCaseSnapshot | Provides a point-in-time view of active cases for analyzing backlog, response status, assignment coverage, case age, and staleness. |
All three aggregates use 15-minute case-creation intervals in DateTimeKey. Queue, owner, worker, status, and other classifications reflect the latest known state or the state observed at snapshot capture. They don't show assignment at resolution time.
Fact tables
Use fact tables to explore the individual records behind case and SLA results.
| Table | Description |
|---|---|
| FactCase | One row per case, with assignment, status, resolution, tracked time, customer feedback, and support entitlement details. |
| FactSLAKPIInstance | One row per SLA key performance indicator (KPI) execution, with the associated case, SLA policy, KPI, and execution status. |
The tables are linked by CaseId. One case can have multiple SLA executions, so count distinct cases when combining the tables to avoid counting the same case more than once.
For example, use FactCase with DimCaseEntitlement to analyze cases by support entitlement. Use FactSLAKPIInstance with DimCaseSLAKPI to compare individual SLA results by measure. Available details depend on the source data.
Case dimensions
Use dimensions to filter, group, and analyze cases by descriptive attributes. The default semantic model includes some dimensions; others are available for detail or custom analysis.
| Dimension | Description |
|---|---|
| DimCaseOwner | Users or teams that own cases, including a category for cases without an assigned owner. |
| DimCaseWorker | Current or last known workers assigned to cases, who might differ from case owners. |
| DimCaseOrigin | Channels through which cases are received. |
| DimCasePriority | Priority levels that indicate how urgently cases need attention. |
| DimCaseType | Categories used to classify cases by the type of customer request. |
| DimCaseStatus | Current case status and the reason for that status. |
| DimCaseProduct | Products associated with cases. |
| DimCaseSLAKPI | Measures tracked by service-level agreements (SLAs), such as first response or resolution. |
| DimCaseAgeBand | Age ranges that group active cases by how long they've been open. |
| DimCaseSeverity | Severity levels that describe the impact of cases. |
| DimSubject | Topics and subtopics used to organize cases by subject. |
| DimCaseSLA | SLA policies associated with cases. |
| DimCaseEntitlement | Support entitlements associated with cases, including the customer and support terms. |
Shared dimensions and relationships
The model also uses these shared dimensions:
DimDateprovides date information for time-based analysis.DimTimeZonesupports time-zone-based reporting.DimQueueprovides queue information.DimBusinessUnitprovides business unit information.
DimDate has one row per 15-minute interval. Don't use Date as a unique relationship key: its value repeats across intervals.
Creation-time filters follow this relationship path:
DimDate.DateTimeKey
-> DimTimeZone.LocalDateTimeKey
-> DimTimeZone.UtcDateTimeKey
-> ProxyUtcDateId.UtcDateTimeKey
-> aggregate.DateTimeKey