Where is response concentrated?
Compare open incidents by service, asset, priority and assigned person.
Review incident load, planned work, rack power and event outcomes.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Open | 41 | ||
| Acknowledged | 29 | 71% | |
| Investigating | 17 | 59% | |
| Resolved | 10 | 59% |
Sample counts per stage
Compare open incidents by service, asset, priority and assigned person.
Compare opening and acknowledgment dates for the cases with both recorded.
Read approved changes with their start and end dates and affected service.
Compare request due dates with recorded completion dates.
Read power figures by rack code and linked asset.
Group receipts by provider and processing state.
Count incidents by priority and status for each affected service.
Compare incident opening and acknowledgment dates by service and assignee.
Group open and investigating incidents by service, asset and assigned person.
List approved and implementing changes with their scheduled start and end dates.
Compare requested, due and completed dates by service and request type.
List recorded power by rack code, unit start and linked asset.
Group cable identities and ports under their linked incident.
Compare open, investigating and known-error problems by service and owner.
Count integration receipts by provider and receipt status.
Start free, then use Proto to change fields, steps and approvals before your team goes live.