Introduction

This report provides details of Diksha usage in terms of QR code Scans and Unique devices for each district of a state. All the graphs show the usage status per month. This report is updated on date 1st of every month. The data and dashboards are state specific.

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 on monthly basis.
• 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 the latest 2 months of consumption data (Total no of unique Devices + Total no of Scans).

  Each report shows 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 for the last month and before last month.

Graph 1:District-Wise unique devices

This report will provide  2 months of data i.e; Before last month and the last month. This data should be calculated based on device Geolocation details of both (Portal and App), In this graph,

we will be showing the count of unique devices which used DIKSHA either through Portal or App. We need to display the ranking of districts in descending order of a total number of unique devices (which accessed Diksha) for districts, means the district which has the highest number of unique devices accessed Diksha, should be given rank 1, followed by district with Rank 2 which has second highest uniques devices accessing Diksha. These numbers are taken on a monthly basis. We would be showing ranking for two months (last month and before last month) in two different bar chats. 

In the second bar chat of graph, the district names should be shown as in the bar graph1, The ranking should be allocated with the number of unique devices in that district of the state in the same order of the first bar chat. 

This report should be generated with both the graphs on day first of every month with the latest data of last month and before to last month data.

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

Graph 2: District wise Total Scans 

This report will provide 2 months of data i.e; Before last month and Last month. This data should be calculated based on the device GEOdata the total scans (Get Page + app) 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.

Ranking of districts in descending order of a total number of QR Code Scans in that districts, means the district which has the highest number Total QR Code Scans, should be given rank 1, followed by district with Rank 2 which has second highest Total QR Code Scans. These numbers are taken on a monthly basis. We would be showing ranking for two months (last month and before last month) in two different bar chats. 

In the second bar chat of graph, the district names should be shown as in the bar graph1, The ranking should be allocated with the number of Total QR code Scans in that district of the state in the same order of the first bar chat. 

This report should be generated with both the graphs on day first of every month with the latest data of last month and before to last month data.

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

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.
• Rank: The ranking is given to all the districts in the state.
  • Logic: Based on the unique devices count the ranking should be allocated. 
• Total Scans:  Count of scans from each district in 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 ) over a period of one year and should be generated every Monday on a weekly basis for that state.

Details: In this report, we will be displaying the unique user devices data (portal + app) on a weekly basis for that state. This data is calculated district wise. 

• Whenever the users go 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 :

We will be showing a matrix of unique devices which have accessed Diksha ( Portal + App) for a particular district on a weekly basis. In case there is no mapping available for any of the city to the district, district cell will display "Unknown". However corresponding data will be shown in week cells.

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