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

Use this section  to elaborate on:

• Jobs To Be Done: As a state admin, the performance of each district of the state such as consumption, failures in ETB on a monthly basis should be monitored.
• 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 over time

Description:

This graph provides overall consumption data on a weekly basis (i.e; from Monday to Sunday ) over a period of one year and should be generated every Monday  for that state.

Details: In this report, we will be displaying the total QR scans data (portal + app) on a weekly for that state. This data is calculated by the district wise. 

• This report provides 3 consumption datasets
  • Total no of QR Code Scans
  • Unique devices in that district for that state. 
  • Total no of content plays
• For each dataset, the Graph should be created and it should have districtwise filter option.
• This report should be calculated over a period of time.
• If no district is selected in the filter, Overall data should be displayed.
• This data is calculated based on the device location data.

Graph:

  Graph description:

• X-axis with Date of data updated and in Y-axis with a total count.
• 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. 
• All the district values should be shown in the dropdown.

Table:

Table description:

District Name: All the districts in the state should be shown.

Unique Devices: Total no of unique devices opened Diksha in that district from that state   

Logic

• APP: Total no of unique devices used Diksha APP in that week from that district in that state.
• Portal: Total no of unique devices used Diksha portal on the web (i.e; in Desktop and mobile web) in that week from that district in that state. 
• Total: APP + Portal

Total no of QR code scans: Total no of QR code scans which include both APP and portal.

Logic

• APP: Total no of  QR code scans (from Diksha or different app) from those unique devices of that week from that district in that state.
• Portal: Total no of  QR code scans from those devices in GET page (i.e; in Desktop and mobile web) in that week from that district in that state. 
• Total: APP + Portal

NOTE: Total scans include both Successful scans, Failed scans, and Unlisted scans.

Total no of content plays: Total no of content plays which include both APP and portal.

Logic

• APP: Total no of content plays from those unique devices in that week from that district in that state.
• Portal: Total no of  content plays from those unique devices  (i.e; in Desktop and mobile web) in that week from that district in that state. 
• Total: APP + Portal

Updated on: The date when the data got updated 

Points to be considered

• In this table, each week data should be added next to the previous week data and so on.
• In case, If there is no mapping available for any of the city to the district, the district cell will display as "Unknown". However corresponding data will be shown in week cell.
• 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

Insert the JIRA Ticket ID created for this story here. Click the + sign on the toolbar, select JIRA Issue/Filter from the list and either select a JIRA issue from the list or create one.   

Localization Requirements

Use this section to provide requirements to localize static content and/or design elements that are part of the UI in the following table. Localization of either the framework, content or search elements should be elaborated as a user story. To add or remove rows in the table, use the table functionality from the toolbar.   

Telemetry Requirements

Use this section to provide requirements of the events for which telemetry should be captured. To add or remove rows in the table, use the table functionality from the toolbar.   

Non-Functional Requirements

Use this section to capture non-functional requirements in the following table. To add or remove rows in the table, use the table functionality from the toolbar.   

Impact on other Products/Solutions

Use this section to capture the impact of this use case on other products, solutions. To add or remove rows in the table, use the table functionality from the toolbar.   

Impact on Existing Users/Data 

Use this section to capture the impact of this use case on existing users or data. To add or remove rows in the table, use the table functionality from the toolbar.   

Key Metrics