> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/work-manager/work-manager/reports/operations-performance-review-report/report-visual-and-measure-reference.md).

# Report Visual & Measure Reference

### Visual & Measure Reference

The full list of cards and visuals across all six tabs, with the underlying measure and source tables for each. Use this when you're building or personalising a visual and need to know which field feeds it.

<table><thead><tr><th width="157">Tab</th><th>Visual (Display Name)</th><th width="134">Type</th><th>Underlying Measure(s)</th><th>Source Table(s)</th></tr></thead><tbody><tr><td>Operations Summary</td><td>Work Items Started</td><td>KPI Card</td><td>Work Items Started</td><td>Work Items, Date</td></tr><tr><td>Operations Summary</td><td>Work Items Open</td><td>KPI Card</td><td>Work Items Started, Status &#x3C; 5</td><td>Work Items, Date</td></tr><tr><td>Operations Summary</td><td>Work Items Overdue</td><td>KPI Card</td><td>Work Items Started, _IsOverdue = 1</td><td>Work Items, Date</td></tr><tr><td>Operations Summary</td><td>SLA Compliance</td><td>KPI Card</td><td>SLA % On EndDate</td><td>Work Items, Date</td></tr><tr><td>Operations Summary</td><td>AHT in Hrs</td><td>KPI Card</td><td>Avg Handling Time in Hrs</td><td>Activity, Work Items, Users, Date</td></tr><tr><td>Operations Summary</td><td>Daily Active Users</td><td>KPI Card</td><td>Daily Active Users</td><td>Activity, Date</td></tr><tr><td>Operations Summary</td><td>Monthly Volume — Received vs Closed</td><td>Clustered Column</td><td>Work Items Started; Closed</td><td>Work Items, Date</td></tr><tr><td>Operations Summary</td><td>By Process (Top 10)</td><td>Donut</td><td>Work Items Started</td><td>Work Items, Process, Date</td></tr><tr><td>Operations Summary</td><td>Top 10 Agents — Throughput &#x26; AHT</td><td>Table</td><td>Closed; AHT; SLA %</td><td>Work Items, Activity, Users, Date</td></tr><tr><td>Volume &#x26; Workload</td><td>Work Items On Target</td><td>KPI Card</td><td>Started, _IsOverdue = 0, Status &#x3C; 5</td><td>Work Items, Date</td></tr><tr><td>Volume &#x26; Workload</td><td>Work Items Closed</td><td>KPI Card</td><td>Work Items Closed</td><td>Work Items, Date</td></tr><tr><td>Volume &#x26; Workload</td><td>Daily Volume Trend</td><td>Line</td><td>Work Items Started; Closed</td><td>Work Items, Date</td></tr><tr><td>Volume &#x26; Workload</td><td>Status Breakdown By Customer</td><td>100% Stacked Bar</td><td>Work Items Started by Status</td><td>Work Items, Date</td></tr><tr><td>Volume &#x26; Workload</td><td>Ageing Distribution</td><td>Clustered Column</td><td>Work Items Started by Ageing Category</td><td>Work Items, Date</td></tr><tr><td>Volume &#x26; Workload</td><td>Queue Wise Count</td><td>Bar</td><td>Work Items Started by Queue</td><td>Work Items, Queues, Date</td></tr><tr><td>Quality &#x26; Defects</td><td>Defects Count</td><td>KPI Card</td><td>Defects Count</td><td>Defects, Date</td></tr><tr><td>Quality &#x26; Defects</td><td>Work Items Reopened</td><td>KPI Card</td><td>Started, _IsReOpened = TRUE</td><td>Work Items, Process, Date</td></tr><tr><td>Quality &#x26; Defects</td><td>Work Items Reworked</td><td>KPI Card</td><td>Started, CountOfRework > 0</td><td>Work Items, Date</td></tr><tr><td>Quality &#x26; Defects</td><td>Peer Review Failure Count</td><td>KPI Card</td><td>Peer Review Failure Count</td><td>Work Items, Date</td></tr><tr><td>Quality &#x26; Defects</td><td>Defects Trend</td><td>Area</td><td>Defects Count over time</td><td>Defects, Date</td></tr><tr><td>Quality &#x26; Defects</td><td>Party At Fault</td><td>Clustered Bar</td><td>Defects Count by Party</td><td>Defects, Date</td></tr><tr><td>Quality &#x26; Defects</td><td>Defects By Queue</td><td>Bar</td><td>Defects Count by Queue / Is Resolved</td><td>Defects, Queues, Date</td></tr><tr><td>SLA &#x26; Cycle Time</td><td>SLA Compliance</td><td>KPI Card</td><td>SLA % On EndDate</td><td>Work Items, Date</td></tr><tr><td>SLA &#x26; Cycle Time</td><td>Avg TAT (Days)</td><td>KPI Card</td><td>Avg TAT (Days)</td><td>Work Items, Date</td></tr><tr><td>SLA &#x26; Cycle Time</td><td>SLA Compliance Trend</td><td>Line</td><td>SLA % On EndDate over time</td><td>Work Items, Date</td></tr><tr><td>SLA &#x26; Cycle Time</td><td>Ageing Distribution — Open</td><td>Clustered Bar</td><td>Started (open only) by Ageing</td><td>Work Items, Date</td></tr><tr><td>SLA &#x26; Cycle Time</td><td>Avg TAT (Days) By Queue</td><td>Table</td><td>Avg TAT (Days) by Queue</td><td>Work Items, Queues, Date</td></tr><tr><td>Agent Performance</td><td>Work Items Resolved Per User</td><td>KPI Card</td><td>Resolved Per User (Insights Users)</td><td>Work Items, Users, Date</td></tr><tr><td>Agent Performance</td><td>% Utilisation</td><td>KPI Card</td><td>% Utilisation</td><td>Insights, Date</td></tr><tr><td>Agent Performance</td><td>% Productivity</td><td>KPI Card</td><td>% Productivity</td><td>Insights, Date</td></tr><tr><td>Agent Performance</td><td>Agent Leaderboard</td><td>Table</td><td>Resolved; Util %; Prod %; SLA %; AHT</td><td>Work Items, Activity, Insights, Users, Date</td></tr><tr><td>Agent Performance</td><td>Time Allocation Breakdown</td><td>Stacked Column</td><td>8 duration categories (Hrs)</td><td>Insights, Date</td></tr><tr><td>Agent Performance</td><td>Responsible Agents</td><td>Bar</td><td>Work Items Started (Insights Users)</td><td>Work Items, Users, Date</td></tr><tr><td>Agent Performance</td><td>Active Users Trend</td><td>Area</td><td>Active Users (Insights Users)</td><td>Activity, Users, Date</td></tr><tr><td>Communications</td><td>Incoming / Outgoing / Thank You</td><td>KPI Card</td><td>Email Count by Date (by type)</td><td>Communications, Date</td></tr><tr><td>Communications</td><td>Unprocessed Emails</td><td>KPI Card</td><td>Email Count (Unprocessed)</td><td>Communications, Date</td></tr><tr><td>Communications</td><td>Volume Trend — Incoming vs Outgoing</td><td>Line</td><td>Email Count by type over time</td><td>Communications, Date</td></tr><tr><td>Communications</td><td>By Process</td><td>Bar</td><td>Email Count by Process / type</td><td>Communications, Process, Date</td></tr><tr><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

<table><thead><tr><th width="111">Table</th><th width="205">Fields</th><th width="466.75">Description</th></tr></thead><tbody><tr><td>Context</td><td>Contract</td><td>Name of the Contract</td></tr><tr><td>Context</td><td>Customer</td><td>Name of the Customer</td></tr><tr><td>Context</td><td>Service</td><td>Name of the Service</td></tr><tr><td>Context</td><td>Service Line</td><td>Name of the Service Line</td></tr><tr><td>Context</td><td>Supplier</td><td>Name of the Supplier</td></tr><tr><td>Dates</td><td>Date</td><td>Calendar range of dates for filtering data</td></tr><tr><td>Dates</td><td>Month</td><td>Months of the dates</td></tr><tr><td>Dates</td><td>Year</td><td>Year of the dates</td></tr><tr><td>Process</td><td>Process Name</td><td>Name of the process each Work Item belongs to</td></tr><tr><td>Process</td><td>ProcessGroup</td><td>Process group given for Cases / Tickets</td></tr><tr><td>Process</td><td>Work Item Type</td><td>Type of the Work Item (Ticket, Action or Case)</td></tr><tr><td>Queues</td><td>Queue</td><td>Name of the queue the Work Item was last present in</td></tr><tr><td>Sentiment Scores</td><td>6M Moving Avg</td><td>6 months moving average over the number of emails that have sentiment scores. To be visualised against dates.</td></tr><tr><td>Sentiment Scores</td><td>CaseCount</td><td>Total number of Cases</td></tr><tr><td>Sentiment Scores</td><td>Email Count</td><td>Total number of emails that sentiment score</td></tr><tr><td>Sentiment Scores</td><td>PercentagesOfAllSentiments</td><td>Percentage of emails with positive,negative &#x26; neutral sentiment compared to the total</td></tr><tr><td>Sentiment Scores</td><td>TicketCount</td><td>Total number of Tickets</td></tr><tr><td>Sentiment Scores</td><td>Total Work Items</td><td>Total number of workitems with emails that have sentiment score</td></tr><tr><td>Sentiment Scores</td><td>ImpactZonesSentiment</td><td>Imapct zones based on combination of SLA &#x26; Sentiment Types (High Priority, Neutral, Positive, Success Optimization)</td></tr><tr><td>Sentiment Scores</td><td>Logged</td><td>Email logged date in date time format</td></tr><tr><td>Sentiment Scores</td><td>LoggedDate</td><td>Email logged date in date format</td></tr><tr><td>Sentiment Scores</td><td>Sender</td><td>Email sender's full name or email address (depending on whichever is availible)</td></tr><tr><td>Sentiment Scores</td><td>Sentiment Confidence</td><td>Confidence level of the email classification (or sentiment score) in percentage (0 - 100%)</td></tr><tr><td>Sentiment Scores</td><td>PercentageSentimentConfidence</td><td>Sentiment Confidence shown in percentage</td></tr><tr><td>Sentiment Types</td><td>Sentiment Type</td><td>Types of sentiment (Positve, Negative or Neutral)</td></tr><tr><td>Ticket Categories</td><td>Ticket Category1</td><td>Ticket Category level 1</td></tr><tr><td>Ticket Categories</td><td>Ticket Category2</td><td>Ticket Category level 2</td></tr><tr><td>Ticket Categories</td><td>Ticket Category3</td><td>Ticket Category level 3</td></tr><tr><td>Ticket Categories</td><td>ConcatTicketCategoryLabels</td><td>Combined representation of Ticket Category level 1, 2 &#x26; 3</td></tr><tr><td>Users</td><td>Email Address</td><td>Email address of the user responsible for the work item</td></tr><tr><td>Users</td><td>Team Manager</td><td>Full name of the manager of the users responsible for the work item</td></tr><tr><td>Users</td><td>User Name</td><td>Full name of the user responsible for the work item</td></tr><tr><td>Work Items</td><td>Assigned User Count</td><td>Assigned User Count is the unique number of users assigned to the work item througout it's lifecycle (from start to end).</td></tr><tr><td>Work Items</td><td>Assigned User Count Groups</td><td>Grouping of Assigned User Count into different buckets (e.g., 0, 1-3, 3-5, 5-7 etc.)</td></tr><tr><td>Work Items</td><td>Customer Duration(Hrs)</td><td>Total time (in working hours) taken to complete the work item as per the customer calendar. Value will be blank if the work item is still in progress.</td></tr><tr><td>Work Items</td><td>Customer Duration Groups</td><td>Grouping of Customer Durations into different buckets (e.g., 0-24, 24-48, 48-72, 5-7 etc.)</td></tr><tr><td>Work Items</td><td>DueDate</td><td>Work Item Due Date in date time format</td></tr><tr><td>Work Items</td><td>EndDate</td><td>Work Item End Date in date time format</td></tr><tr><td>Work Items</td><td>Has Defects</td><td>Whether the Work Item has defect or not (Yes or No)</td></tr><tr><td>Work Items</td><td>Is Reopened</td><td>Tickets that got opened after going to resolved status</td></tr><tr><td>Work Items</td><td>Reference</td><td>Reference number of each Work Item</td></tr><tr><td>Work Items</td><td>Reopened Count</td><td>Number of times the work item got reopened throughout it's lifecycle</td></tr><tr><td>Work Items</td><td>Reopened Count Groups</td><td>Grouping of Reopened Count into different buckets (e.g., 1-3, 3-5, 5-7, 7+ etc.)</td></tr><tr><td>Work Items</td><td>ResolvedDate</td><td>Work Items Resolved Date in date time format</td></tr><tr><td>Work Items</td><td>SLA</td><td>Service Level Agreement to indicate where Work Item is Overdue or not</td></tr><tr><td>Work Items</td><td>StartDate</td><td>Work Item Start Date in date time format</td></tr><tr><td>Work Items</td><td>Supplier Duration(Hrs)</td><td>Total time (in working hours) taken to complete the work item as per the supplier calendar. Value will be blank if the work item is still in progress.</td></tr><tr><td>Work Items</td><td>Title</td><td>Title of the Work Item</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.enate.net/enate-help/work-manager/work-manager/reports/operations-performance-review-report/report-visual-and-measure-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
