Difference between revisions of "PEC-REP/Current/RPRT/HRCXIiWDResPerf"

From Genesys Documentation
Jump to: navigation, search
(Published)
(Published)
Line 57: Line 57:
 
{{!}}Resource ID
 
{{!}}Resource ID
 
{{!}}Optionally, select a resource (usually an agent) on which to focus the report.
 
{{!}}Optionally, select a resource (usually an agent) on which to focus the report.
{{!}}-
 
{{!}}Tenant<!--(was Not present in GI2)-->
 
{{!}}'''Note: This field is reserved for future use.''' Optionally, select a tenant on which to focus the report.
 
 
{{!}}-
 
{{!}}-
 
{{!}}}
 
{{!}}}
Line 74: Line 71:
 
!'''Attribute'''
 
!'''Attribute'''
 
!'''Description'''
 
!'''Description'''
!'''Data Mart Table.Column'''
 
{{!}}-
 
{{!}}Tenant<!--(was not present in GI2)-->
 
{{!}}'''Note: This field is reserved for future use.''' Enables data within the reporting interval to be organized by tenant.<!--For multi-tenant environments, the universe connection that you define points to only one tenant schema in the Info Mart. New connections are required for access to other tenant schemas.-->
 
{{!}}TENANT.TENANT_NAME
 
 
{{!}}-
 
{{!}}-
 
{{!}}Department<!--(was Not present in GI2)-->
 
{{!}}Department<!--(was Not present in GI2)-->
 
{{!}}Enables data to be organized by the name of the department for which iWD prioritizes and routes tasks.
 
{{!}}Enables data to be organized by the name of the department for which iWD prioritizes and routes tasks.
{{!}}DEPARTMENT.DEPARTMENT_NAME
 
 
{{!}}-
 
{{!}}-
 
{{!}}Process
 
{{!}}Process
 
{{!}}Enables data to be organized by the name of the business process. The business process name is a core attribute that is used to define strategies for how to route tasks and work items.
 
{{!}}Enables data to be organized by the name of the business process. The business process name is a core attribute that is used to define strategies for how to route tasks and work items.
{{!}}PROCESS.PROCESS_NAME
 
 
{{!}}-
 
{{!}}-
 
{{!}}Resource ID
 
{{!}}Resource ID
 
{{!}}Enables data to be organized by the unique identifier of each resource (usually an agent).
 
{{!}}Enables data to be organized by the unique identifier of each resource (usually an agent).
{{!}}AGENT.AGENT_ID
 
 
{{!}}-
 
{{!}}-
 
{{!}}Day
 
{{!}}Day
 
{{!}}Enables data within the reporting interval to be organized by a particular day within a month and year. Day values are presented in YYYY-MM-DD format.
 
{{!}}Enables data within the reporting interval to be organized by a particular day within a month and year. Day values are presented in YYYY-MM-DD format.
{{!}}DATE_TIME.LABEL_YYYY_MM_DD
 
 
{{!}}-
 
{{!}}-
 
{{!}}}
 
{{!}}}
Line 109: Line 97:
 
!'''Metric'''
 
!'''Metric'''
 
!'''Description'''
 
!'''Description'''
!'''Source or Calculation'''
 
 
{{!}}-
 
{{!}}-
 
{{!}}Accepted
 
{{!}}Accepted
 
{{!}}For completed tasks, the total number of tasks that were assigned to this resource during the reporting interval.
 
{{!}}For completed tasks, the total number of tasks that were assigned to this resource during the reporting interval.
{{!}}IWD_AGG_TASK_AGENT_[Y,Q,M,W,D,H,15].TASK_WORK_COUNT
 
 
{{!}}-
 
{{!}}-
 
{{!}}Finished
 
{{!}}Finished
 
{{!}}The total number of tasks that were completed during the reporting interval.
 
{{!}}The total number of tasks that were completed during the reporting interval.
{{!}}IWD_AGG_TASK_AGENT_[Y,Q,M,W,D,H,15].CMPL_TASK_COUNT
 
 
{{!}}-
 
{{!}}-
 
{{!}}Handle Time (Fmt)
 
{{!}}Handle Time (Fmt)
 
{{!}}The total amount of time, in seconds, that this resource worked on tasks before finishing them. This duration is measured as the difference between the time when the resource is assigned to a task, and the time when the task is finished.
 
{{!}}The total amount of time, in seconds, that this resource worked on tasks before finishing them. This duration is measured as the difference between the time when the resource is assigned to a task, and the time when the task is finished.
 
Note that the act of a resource finishing a task within the iWD system does not, in and of itself, mark the task Completed—one of three states that indicate task finalization. A task can  have multiple work items. This metric considers active as well as completed tasks in its computation.
 
Note that the act of a resource finishing a task within the iWD system does not, in and of itself, mark the task Completed—one of three states that indicate task finalization. A task can  have multiple work items. This metric considers active as well as completed tasks in its computation.
{{!}}IWD_AGG_TASK_AGENT_[Y,Q,M,W,D,H,15].WORK_TIME
 
 
{{!}}-
 
{{!}}-
 
{{!}}Avg Handle Time (Fmt)
 
{{!}}Avg Handle Time (Fmt)
 
{{!}}The average amount of time that this resource (for example, an agent) worked on tasks before finishing them. Note that the act of a resource finishing a task within the iWD system does not, in and of itself, mark the task Completed—one of three states that indicate task finalization. This metric considers active as well as completed tasks in its computation.
 
{{!}}The average amount of time that this resource (for example, an agent) worked on tasks before finishing them. Note that the act of a resource finishing a task within the iWD system does not, in and of itself, mark the task Completed—one of three states that indicate task finalization. This metric considers active as well as completed tasks in its computation.
{{!}}Calculated based on the value of the Handle Time and Accepted metrics, where:
 
 
*Handle Time is: IWD_AGG_TASK_AGENT_[Y,Q,M,W,D,H,15].WORK_TIME
 
*Accepted is: IWD_AGG_TASK_AGENT_[Y,Q,M,W,D,H,15].TASK_WORK_COUNT
 
 
{{!}}-
 
{{!}}-
 
{{!}}Min Handle Time (Fmt)
 
{{!}}Min Handle Time (Fmt)
 
{{!}}The shortest amount of time that this resource worked a task before finishing it. Finishing a task within the iWD system does not necessarily imply that the task was Completed—one of three states that indicate task finalization. This metric considers active as well as completed tasks in its computation.
 
{{!}}The shortest amount of time that this resource worked a task before finishing it. Finishing a task within the iWD system does not necessarily imply that the task was Completed—one of three states that indicate task finalization. This metric considers active as well as completed tasks in its computation.
{{!}}IWD_AGG_TASK_AGENT_[Y,Q,M,W,D,H,15].MIN_WORK_TIME
 
 
{{!}}-
 
{{!}}-
 
{{!}}Max Handle Time (Fmt)
 
{{!}}Max Handle Time (Fmt)
 
{{!}}The longest amount of time that this resource worked on a task before finishing it. Finishing a task within the iWD system does not necessarily imply that the task was Completed—one of three states that indicate task finalization. This measure considers active as well as completed tasks in its computation.
 
{{!}}The longest amount of time that this resource worked on a task before finishing it. Finishing a task within the iWD system does not necessarily imply that the task was Completed—one of three states that indicate task finalization. This measure considers active as well as completed tasks in its computation.
{{!}}IWD_AGG_TASK_AGENT_[Y,Q,M,W,D,H,15].MAX_WORK_TIME
 
 
{{!}}-
 
{{!}}-
 
{{!}}}
 
{{!}}}
</onlyinclude>
+
To view more detailed information about the metrics and attributes in this report, and other metrics and attributes that can be used to customize reports, see the [https://docs.genesys.com/Documentation/GCXI/9.0.0/PG/Welcome ''Genesys CX Insights Projects Reference Guide''].</onlyinclude>
 
|structuredtextwide=
 
|structuredtextwide=
 
|FAQHeading=
 
|FAQHeading=
Line 146: Line 124:
 
}}
 
}}
 
}}
 
}}
The following tables explain the prompts you can select when you generate the report, and the metrics and attributes that are represented in the report:
 

Revision as of 14:10, June 12, 2020

This topic is part of the manual Work with Genesys CX Insights Reports for version Current of Reporting.

This page describes how you (as a team leader, manager, or business user) can use the (CX Insights for iWD folder) > Resource Performance Report to understand how resources handle tasks over specific time periods. Gaining insights and the variability of performance for each process, department, and days the resource worked.

Understanding the Resource Performance Report

This report summarizes a resource’s handling of tasks by process over a specified time interval. It provides the total number of tasks that the resource accepted, as well as the shortest, longest, and average amounts of time that it took the resource to handle them.

To get a better idea of what this report looks like, view sample output from the report:

SampleResourcePerformanceReport.pdf

Prompts in the Resource Performance Report

Prompt Description
Pre-set Date Filter Choose from the convenient list of predefined rolling time ranges, spanning one day or more, over which to run the report.
Start Time Choose the first day and time from which to gather report data.
End Time Choose the last day and time from which to gather report data.
Department Optionally, select a department on which to focus the report.
Process Optionally, select a business process on which to focus the report.
Resource ID Optionally, select a resource (usually an agent) on which to focus the report.

Attributes in the Resource Performance Report

Attribute Description
Department Enables data to be organized by the name of the department for which iWD prioritizes and routes tasks.
Process Enables data to be organized by the name of the business process. The business process name is a core attribute that is used to define strategies for how to route tasks and work items.
Resource ID Enables data to be organized by the unique identifier of each resource (usually an agent).
Day Enables data within the reporting interval to be organized by a particular day within a month and year. Day values are presented in YYYY-MM-DD format.

Metrics in the Resource Performance Report

Metric Description
Accepted For completed tasks, the total number of tasks that were assigned to this resource during the reporting interval.
Finished The total number of tasks that were completed during the reporting interval.
Handle Time (Fmt) The total amount of time, in seconds, that this resource worked on tasks before finishing them. This duration is measured as the difference between the time when the resource is assigned to a task, and the time when the task is finished.

Note that the act of a resource finishing a task within the iWD system does not, in and of itself, mark the task Completed—one of three states that indicate task finalization. A task can have multiple work items. This metric considers active as well as completed tasks in its computation.

Avg Handle Time (Fmt) The average amount of time that this resource (for example, an agent) worked on tasks before finishing them. Note that the act of a resource finishing a task within the iWD system does not, in and of itself, mark the task Completed—one of three states that indicate task finalization. This metric considers active as well as completed tasks in its computation.
Min Handle Time (Fmt) The shortest amount of time that this resource worked a task before finishing it. Finishing a task within the iWD system does not necessarily imply that the task was Completed—one of three states that indicate task finalization. This metric considers active as well as completed tasks in its computation.
Max Handle Time (Fmt) The longest amount of time that this resource worked on a task before finishing it. Finishing a task within the iWD system does not necessarily imply that the task was Completed—one of three states that indicate task finalization. This measure considers active as well as completed tasks in its computation.

To view more detailed information about the metrics and attributes in this report, and other metrics and attributes that can be used to customize reports, see the Genesys CX Insights Projects Reference Guide.

Comments or questions about this documentation? Contact us for support!