Introduction

This report provides details of Diksha usage in terms of QR code Scans and Unique devices for each district of that state are shown. It helps the state to plan for improving the consumption of ETB in those districts.

JTBD

• Jobs To Be Done: As a state admin, I want to have a look at the performance of each district of the state such as consumption, failures in ETB.
• User Personas: The logged-in users who have State Admin role, report viewer role can access this report.
• System or Environment: works on for desktops with Chrome browser only.

District-wise Report

Description:

This report will provide only 2 months of consumption data of for every state and also help the state admin to identify the performance of each district in that state and tell how many new users are using the Diksha every month . and also It gives a better understanding of users using Diksha from that state. This report should get updated on a monthly basis. 

This report shows 2 fields i.e; graph and Table.

Graph:

     a. District-Wise devices:In the first graph, we will be displaying  2 bar charts with district's rank and the number of unique devices from each district in that state for the last month and before last month.

     b. District wise Scans: In the second graph, we will be displaying  2 bar charts with district's rank and the number of scans from each district in that state for the last month and before last month.

Details: In this report, we will be displaying 2 months of data i.e; Last month and before last month. Based on device Geo data ,  we will be calculating how many users used Diksha and scanned the QR code in that district for that month, Ranking and number of unique device count and Overall Scans are captured and are displaced in Diksha from displayed in the graph and table for each district of that state and according to that unique devices count and overall scans, the ranking should be allocated in the same order of first bar chart.

     In the second bar chart of graph 1&2, based on the before last month data, the ranking should be allocated with the number of unique devices and the overall scans to the district of that state in the same order of first bar chart of the graph 1.

     This report should be generated with both the graphs on every month 1st with the latest last month data and before to last month data.

Latest last month data should be aligned in the ascending order of district ranks of that state.

Graph 1:District-Wise unique devices

Graph 2: District wise Scans 

In this report, we should create 2 bar charts based on the device geo data the scans need to be calculated. Ranking and number of scans should be displayed for the district in that state for last month and the before last month.

Table:

District wise unique devices count and total scans counts of each district in that state are recorded for the last month and second last month.

Fields:

• Unique Device: Unique devices for the district in that month for a state
  • Logic: Based on the device location data how many of the devices are linked to that specific district in the state for a specific month. 
• Total Scans:  Count of scans from each district in that state

  NOTE: This report should be generated with both the graphs on every month 1st with the latest last month data and before to last month data.

  Latest last month data should be aligned in the ascending order of district ranks of that state
  • • Logic: Based on the device location data, overall how many QR scans got in that district for a specific month.

  
  

  
  

 District-wise Unique Devices over time

Description: 

This graph shows unique devices count for every week( i.e; from Monday to Sunday ) in  DIKSHA overtime and should be generated on every Monday on a weekly basis for that state.

Details: In this report, we will be displaying the user devices data on a weekly basis for that state. This data is calculated by the district wise. 

• Whenever the user goes on to the graph, they will be able to see overall data of the state. District wise filter should be enabled and the user should be able to get the data by filtering the district name whenever needed. 

• If no district is selected in the filter, Overall data should be displayed.

• This data is calculated based on the device location data. 

Graph : 

Table :

Note: Each district unique devices count is captured on a weekly basis for that state. This is for overtime and all the districts of that state are shown in the table and in the graph as well.

JIRA Ticket ID

Localization Requirements

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics