--- title: DEX Score metric definitions description: Base system DEX Score metric definitions measure application, device, user sentiment, and service desk experience. locale: en-US canonical_url: https://www.servicenow.com/docs/r/it-operations-management/digital-end-user-experience-dex/dexscr-metric-defs.html release: brazil product: Digital End-User Experience \(DEX\) classification: digital-end-user-experience-dex topic_type: reference last_updated: "2026-09-10" reading_time_minutes: 2 breadcrumb: [Digital Experience Score reference, Reference, Digital End-User Experience, IT Operations Management] --- # DEX Score metric definitions Base system DEX Score metric definitions measure application, device, user sentiment, and service desk experience. The DEX Score metrics are calculated for a specific application or device group within a defined time range and location. |Metric|Application type| |------|----------------| |Application crashes|Installed| |Average DNS lookup|Web| |Average page load time|Web| |Average response time|Web| |CPU usage|Installed| |Failed web requests|Web| |Memory usage|Installed| |Metric| |------| |Battery health| |CPU usage| |Disk usage| |Memory usage| |Wifi receive rate| |Wifi RSSI| |Wifi transmit rate| |Metric| |------| |Application survey| |Device survey|
Metric Description
Customer satisfaction scores for incident resolved The score for customer satisfaction surveys sent to users for resolved incidents. Scores are calculated only for those surveys that have been successfully submitted by users.Normalized values for surveys are considered and surveys with normalized values greater than zero are assigned weights on a scale of 0–100. For more information, see [Normalized value for an assessment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/example-normalized-value-calc.md).
Number of resolved incidents The number of incidents resolved or closed for an application or device group.For example, the number of Chrome application incidents resolved in the first week of July in New York.
Mean time to resolve an incident The average time \(in hours\) taken to resolve incidents. It is calculated by averaging the differences between incident creation and resolution times for resolved incidents.
Number of closed major incidents The number of major incidents resolved or closed for an application or device group.Major incidents are filtered by confirming that the Major Incident Management plugin \(com.snc.incident.mim\) is active and the **Major incident state** field on incident records is set to **Accepted**.
Percentage of first assignment resolution The percentage of incidents resolved on first assignment. Calculated as: \(incidents with **Reassignment count** of zero ÷ total incidents\) × 100.
Percentage of incidents that breached SLA This percentage is calculated by dividing the number of incidents that have breached the SLA time by the total number of incidents, and multiplying the result by 100.The total number of incidents with SLA breach is the sum of incidents with the **Has breached** state marked as **true** in the Task SLA table of the incident records.
Percentage of reopened incidents This percentage is calculated by dividing the number of incidents with **Reopened count** greater than zero in the incident records by the total number of incidents, and multiplying the result by 100.
Total outages due to incidents The total duration of outages or degradation \(in hours\) caused by incidents.It is calculated as the sum of the durations of all outages recorded in the cmdb\_ci\_outage table.
The number of closed major incidents, resolved incidents, and total outages due to incidents are metrics that help evaluate service desk experience but don’t contribute to the experience score. **Parent Topic:**[Digital Experience Score​ reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/it-operations-management/digital-end-user-experience-dex/dexscr-dex-score-reference.md)