Powered by Temper

Location Incident Cycle Time Report

STOP: Is the Incident module active for your organization?

 

This Report allows you to monitor the Incident cycle time - how long Incidents are spending in each status - on a per Location basis.

Location_Incident_Cycle_Time.jpg

 

Working with the Report

  • Only information about items that originated in each Location is included by default, but selecting or deselecting "Originating" and "Responsible" will add or remove the relevant data from the Report.

  • The date range options are listed along the top of the page. Choose between 1 week, 1 month, 3 months, 6 months, 9 months, 12 months, all time, or a custom range by clicking on the corresponding option.

  • Beneath the date ranges are three additional options:

    • Click "All" to include all Incidents that meet the rest of the filter requirements.

    • Click "Project-Based" to include only Incidents that meet the rest of the requirements and are nested under a Project.

    • Click "Stand-Alone" to include only Incidents that meet the rest of the requirements and are not nested under a Project.

  • Pick a Level Type (or Types) in the "Level Type" field to list only Locations of a certain type on the Report.

  • The Network diagram can be found along the left side of the page. Use this to filter the Report by Location - only items tied to the selected Locations will be included in the Report.

You can also:

  • Click any of the data points or status bars on this Report to open the list of Incidents it is counting. If you don't have the adequate permissions to view them, some items will be excluded from the list.

  • Export the Report to an Excel spreadsheet by clicking 2018-04-25_1238.png near the bottom left corner of the page. 

 

Things to look for:

  • Locations within your organization that are taking significantly longer to implement Incidents than other Locations. People in these Locations may need additional coaching about the importance of timely Incidents and Lean in general.

Bottleneck Alert:

When Incidents are spending a long time in the New status, leadership may be failing to respond quickly and assign New Incidents. Incidents spending a long time in the Resolution Submitted status indicates that leaders are not promptly reviewing submitted Resolutions. Lastly, Incidents spending a long time in the Overdue status indicates that people are not implementing Incidents in a timely manner.

Solutions:

  • Coach leaders to promptly assign new Incidents so that work can commence.

  • Coach leaders to quickly respond to submitted Resolutions.

  • Make sure people are completing the Incidents they’ve been assigned.

 

Have more questions? Submit a request