0 service requests

About this visual

Each circle represents a possible state of the service request.

The size represents the percentage of time spent by all service requests in this state. (Larger circles indicate more time.)

The colour represents the time spent by any service requests, on average in this state. (Red circles indicate a higher average processing time.)

The arcs on top represent forward flows, from left to right. Their size and colour again represent the total and average time spent in that transition.

The arcs below represent reverse flows, from right to left. Their size and colour are similarly constructed.

Cause of delay This visual uses TopCause: a Gramener algorithm

Group Count Days spent

* Empty cell implies no impact

Summary of the causes

There are no significant causes of delay that we can infer for this segment from the data.

Service requests status Showing 0 out of 0

Service Request ID SR Audit Create Datetime SR Audit Status Next status Time spent

Process Workflow Optimization

This page shows all required calculations for the workflow POC.

Computations

  1. De-duplicate data by primary keys Service Request ID, SR Audit Create Datetime, and SR Audit Status.
  2. Sort by Service Request ID, and within that, by SR Audit Create Datetime.
  3. Add a Next status column that has the next row's SR Audit Status within a given Service Request ID. (The last row in each Service Request ID will have a NaN Next status.)
  4. Calculate the Time spent as the next row's SR Audit Create Datetime minus the current row's SR Audit Create Datetime. For the last row, this value will be NaN.

Basic statistics

Time spent in each status, on average

count count_transitioned mean_days total_days
SR Audit Status

Time spent on transitions

count mean_days total_days
SR Audit Status Next status