Entity Breakdown Page - Revision history

Hendry.mwamburi: /* Filters */

2026-01-27T12:41:49Z

Filters

← Older revision		Revision as of 14:41, 27 January 2026
Line 14:		Line 14:
	\|Entity slicer		\|Entity slicer
	\|Enables users to filter the report by entity ( Business unit)		\|Enables users to filter the report by entity ( Business unit)
			\|-
			\|Region slicer
			\|Enables users to filter the report by Region
	\|-		\|-
	\|User		\|User

2025-08-15T09:46:11Z

← Older revision		Revision as of 11:46, 15 August 2025
Line 1:		Line 1:
	== Summary ==		== Summary ==

			The '''Non-Conformance Dashboard''' provides an interactive and consolidated view of service and operational non-conformance tickets. It supports performance monitoring, trend analysis, and root cause identification across multiple business entities.

	== Filters ==		== Filters ==

2025-08-15T09:42:22Z

← Older revision		Revision as of 11:42, 15 August 2025
Line 86:		Line 86:
	\|This visual presents the total number of non-conformance cases categorized by the '''Corrective Action''' taken, using a '''stacked bar chart'''. Each bar represents a grouping (such as entity, month, or category depending on filters), with each segment showing a specific corrective action classification.		\|This visual presents the total number of non-conformance cases categorized by the '''Corrective Action''' taken, using a '''stacked bar chart'''. Each bar represents a grouping (such as entity, month, or category depending on filters), with each segment showing a specific corrective action classification.
	\|-		\|-
	\|10. Total		\|10. Total Non-Conformance by Action
	\|		\|Total Non-Conformance = DISTINCTCOUNT('Performance and Root Cause'[id])
	\|		\|This visual presents the '''total number of non-conformance cases''' categorized by the '''Action taken against employee''' taken to resolve them, using a '''stacked bar chart'''. Each bar corresponds to a grouping (such as entity, month, or category, depending on active filters), and each colored segment within the bar represents a specific Action taken.
	\|}		\|}

2025-08-15T09:39:28Z

@@ Line 74: / Line 74: @@
 |MoM Variance = [Total Non-Conformance]-[Last Month Tickets]
 MoM Growth% = DIVIDE([MoM Variance],[Last Month Tickets])
 Total Non-Conformance = DISTINCTCOUNT('Performance and Root Cause'[id])
 |This visual combines a '''clustered bar chart''' (showing total non-conformance counts per month) with a '''line chart''' (showing Month-over-Month growth percentage). It provides both absolute ticket volumes and their relative change over time in a single view.
 |}

2025-08-15T09:30:46Z

← Older revision		Revision as of 11:30, 15 August 2025
Line 70:		Line 70:
	\|Total Non-Conformance = DISTINCTCOUNT('Performance and Root Cause'[id])		\|Total Non-Conformance = DISTINCTCOUNT('Performance and Root Cause'[id])
	\|This visual displays the total count of non-conformance tickets grouped by their '''Category Name'''. Each bar represents a category, and the bar’s length corresponds to the number of tickets in that category.		\|This visual displays the total count of non-conformance tickets grouped by their '''Category Name'''. Each bar represents a category, and the bar’s length corresponds to the number of tickets in that category.
			\|-
			\|7. Total Non-conformance and MOM Growth% by Month Name
			\|MoM Variance = [Total Non-Conformance]-[Last Month Tickets]
			MoM Growth% = DIVIDE([MoM Variance],[Last Month Tickets])
			Total Non-Conformance = DISTINCTCOUNT('Performance and Root Cause'[id])
			\|This visual combines a '''clustered bar chart''' (showing total non-conformance counts per month) with a '''line chart''' (showing Month-over-Month growth percentage). It provides both absolute ticket volumes and their relative change over time in a single view.
	\|}		\|}

2025-08-15T09:24:43Z

← Older revision		Revision as of 11:24, 15 August 2025
Line 67:		Line 67:
	\|This measure calculates the mean number of days taken to resolve non-conformance tickets, based on the difference between the ticket’s creation date and resolution date.		\|This measure calculates the mean number of days taken to resolve non-conformance tickets, based on the difference between the ticket’s creation date and resolution date.
	\|-		\|-
	\|6. Total ~~Non_conformance~~		\|6. Total Non-conformance by Category Name
	\|		\|Total Non-Conformance = DISTINCTCOUNT('Performance and Root Cause'[id])
	\|		\|This visual displays the total count of non-conformance tickets grouped by their '''Category Name'''. Each bar represents a category, and the bar’s length corresponds to the number of tickets in that category.
	\|}		\|}

2025-08-15T09:22:04Z

← Older revision		Revision as of 11:22, 15 August 2025
Line 66:		Line 66:
	AVERAGE ( 'Performance and Root Cause'[Days] )		AVERAGE ( 'Performance and Root Cause'[Days] )
	\|This measure calculates the mean number of days taken to resolve non-conformance tickets, based on the difference between the ticket’s creation date and resolution date.		\|This measure calculates the mean number of days taken to resolve non-conformance tickets, based on the difference between the ticket’s creation date and resolution date.
			\|-
			\|6. Total Non_conformance
			\|
			\|
	\|}		\|}

2025-08-15T09:17:28Z

@@ Line 46: / Line 46: @@
 !Description
 |-
-|Total Non-Conformance Raise
+|1. Total Non-Conformance Raised
+|Total Non-Conformance = DISTINCTCOUNT('Performance and Root Cause'[id])
+|This measure calculates the total number of unique non-conformance records in the dataset by counting distinct ticket IDs.
 |}

2025-08-15T09:04:33Z

2025-08-15T08:56:52Z

← Older revision		Revision as of 10:56, 15 August 2025
Line 24:		Line 24:
	!Transformations		!Transformations
	\|-		\|-
			\|Entity table API link =[https://customer-service.datacair.com/api/ticket/customfield/6?limit=1000000000 https://customer-service.datacair.com/api/ticket/customfield/6]
	\|		\|
			* '''API Endpoint:''' <code>[https://customer-service.datacair.com/api/ticket/customfield/5 https://customer-service.datacair.com/api/ticket/customfield/6]</code>
			* '''Purpose:''' Retrieves the ''Entity'' custom field values for tickets.

			* '''Default Behavior:''' The API returns a maximum of '''50 records''' per request unless otherwise specified.
			\|-
			\|Datacair tickects table API link =https://customer-service.datacair.com/api/ticket/ticket?department=4&limit=1000000000
			\|
			* '''API Endpoint''': <code><nowiki>https://customer-service.datacair.com/api/ticket/ticket?department=4&limit=1000000000</nowiki></code>

			* '''Purpose''': Retrieves comprehensive ticket information for department ID '''4''', including metadata and key lifecycle fields. The <code>limit</code> parameter is explicitly set to a very high value to ensure all relevant records are returned in a single call, bypassing default pagination limits.
	\|}		\|}