Scope:
Tickets assigned to DSDS
Only two sites to be considered for the reporting. For that, we need to consider tickets that are raised by the users based on the corresponding site.
What are the applications included in the scope?
| Indicators | Description | Source table technical name | Source field technical name | Calculations/Flow |
|---|---|---|---|---|
| Backlog incidents | Number of ongoing (status: open and in progress) incidents. Excluding the one resolved, closed,...per site. | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents Master data to link user ID to the site Joint: User ID | customer_login_id | Filters: Status=1, 2... Based on the user ID login to the dashboard, apply the filter to count only incidents that are created in the same site as the user |
| Incident daily growth rate | Number of ongoing incidents at the reporting time divided by the number of open incidents reported in the mid night of the day before. For that, real time refresh and daily snapshots from the source are required. | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Incident weekly growth rate | Number of ongoing incidents at the reporting time divided by the number of ongoing incidents reported in the mid night of the 7 day before. For that, real time refresh and daily snapshots from the source are required. | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Unassigned backlog | Number of ongoing incidents at the reporting time with no assignee | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Unassigned incident weekly growth rate | Number of ongoing incidents without assignee at the reporting time divided by the number of ongoing incidents without assignment in the mid night of the 7 day before. For that, real time refresh and daily snapshots from the source are required. | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Critical incidents | Number of ongoing incidents with priority as critical | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Critical incidents weekly growth rate | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | |||
| Oldest critical incidents (Time) | The time window between the creation date of the latest ongoing incidents with priority as critical and the current time | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Opened ticket last 48 hrs | The tickets with creation date in the last 2 days (How to show a trend ? number per day, per hrs? | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Resolved incidents | The number of Resolved tickets in what time period? Resolved today? | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| Resolved incident daily | The number of incidents for which the status turned to resolved in each day (the last seven days to be displayed in the dashboard) | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| MRTT of resolved incident | ? | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| MRTT daily growth rate | ? | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents | ||
| MRTT weekly growth rate | ? | prj-data-dm-dt-dev.ODS.ODS_HLX_0000_F001_I_H_incidents |