Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
When the country-level/province-level/district-level/administrative- level of the user login to the HCM admin account as assigned, they can navigate to the following sections
Dashboard
User management
Complaints
This is the national-level dashboard view for the country head, for a specific campaign. This dashboard displays the overall data of a campaign running in various provinces with a drill-down behaviour so that the supervisor can also view the data for a specific province/district when required.
This is the campaign-level dashboard for the province. Here, the user can view the overall performance and the status of the campaign which is running at the province/state level. A user can also drill-down to the boundary levels.
For the selected campaign, the “Registration & Delivery” section majorly focuses on the data collected by the field-level workers. It shows the status of the campaign at a ground level, in each district and administrative post of the province.
For the selected campaign running for a province, the ‘Complaints’ section shows the data about the complaints that have been generated by the FLWs, supervisors and warehouse managers at any point of time in the process of an ongoing campaign.
For the selected campaign, the ‘Inventory’ section majorly focuses on the data of how the inventory movement is managed within the warehouses or is being managed within the internal team.
This is the campaign-level dashboard for a province/district. The user can view the overall analytics of the activities that the supervisor performs. This supervision dashboard does not have any of the drill-down approaches available for it’s any of the graphs.
Click here for details.
The Dashboard of the Health Campaign Platform offers a wide range of features that deliver a comprehensive view of campaign performance. It empowers supervisors to easily monitor their teams, assess campaign progress, and quickly address any obstacles that may arise.
The Dashboard equips campaign supervisors with real-time insights to evaluate their teams' effectiveness and make data-driven decisions for optimising campaign performance. Featuring intuitive visualisations and customisable metrics, supervisors can easily track key performance indicators (KPIs) such as campaign coverage, engagement, and inventory movement. The Dashboard also provides a comprehensive view of team productivity and individual performance, enabling supervisors to identify top performers and areas that may need additional support. With these powerful tools, supervisors can efficiently monitor and manage their teams, ensuring the success of the health campaign.
The Dashboard's intuitive interface makes tracking campaign progression seamless for supervisors. They can effortlessly monitor campaign milestones, goals, and progress against predefined targets, allowing them to assess the campaign's overall health and take corrective actions when necessary. Moreover, the Dashboard offers historical and predictive data, along with trend analysis, enabling supervisors to identify patterns and make data-driven decisions to optimise strategies for future campaigns. With these powerful features, supervisors can effectively analyse campaign performance and continuously refine their approach for maximum impact.
Apart from performance tracking, the dashboard provides campaign supervisors with efficient tools to troubleshoot roadblocks. It promptly highlights any issues or bottlenecks that may impact campaign progress, allowing supervisors to quickly identify and address them. Additionally, supervisors can drill down into specific boundaries, such as villages, to pinpoint areas that require attention and proactively take measures to resolve challenges. With these capabilities, supervisors can effectively overcome obstacles and ensure smooth campaign execution at all levels, from a macro to a micro level, to achieve desired outcomes.
The HCM Dashboard is purposefully designed to be user-friendly, with an intuitive and easy-to-navigate interface that requires minimal training to get started. Its robust features and user-centric design empower campaign supervisors to efficiently monitor, evaluate, and troubleshoot campaign performance. With this powerful tool, supervisors can effectively drive the success of their health campaigns, making informed decisions and taking corrective actions as needed. The HCM Dashboard is a valuable asset for campaign supervisors, ensuring a seamless and effective management of health campaigns.
Click here for the installation guide.
After a supervisor logs into the HCM web app, the project services will be invoked to set the locations that are tagged to the user.
Based on the details of the user logged in to the dashboard, the project-staff-search is invoked to get the projects associated with the user.
A Project-Search is then invoked to get the complete project-details which includes campaign start and end dates, boundary information, etc.
The MDMS API is invoked to get more details about the project based on “projectType”.
The egov-Location service is invoked to get the boundary information based on boundaryCode that was obtained from the project details.
A supervisor can navigate to their corresponding dashboards (national/ provincial/district) using the following URLs:
- https://health-demo.digit.org/digit-ui/employee/dss/dashboard/national-health-dashboard
- https://health-demo.digit.org/digit-ui/employee/dss/dashboard/district-health-dashboard
On the dashboards, users can only view the information which was synced corresponding to the projects they are associated with. As more devices sync, the dashboards will be updated with the latest synced data.
End point
Request Method
Request Payload
/project/staff/v1/_search
POST
{
"ProjectStaff": {
"staffId": "loggedInUserId"
},
"RequestInfo": {
"authToken": "string",
}
}
/project/v1/_search
POST
{
"RequestInfo": {
"authToken": "string"
},
"Projects": [
{ "id":"projectId",
"tenantId": "string"
}
]
}
/egov-mdms-service/v1/_search?tenantId=default
POST
{
"MdmsCriteria": {
"tenantId": "default",
"moduleDetails": [
{
"moduleName": "HCM-PROJECT-TYPES",
"masterDetails": [
{
"name": "projectTypes"
}
]
}
]
},
"RequestInfo": {
"authToken": "string"
}
}
/egov-location/location/v11/boundarys/_search?hierarchyTypeCode=ADMIN&tenantId=default&codes=<boundarycode>&boundaryType=<boundaryType>
POST
{
"RequestInfo": {
"authToken": "string"
}
}
The date range can be controlled with the following three options provided to the user:
Custom Date Range
Today
Cumulative
Custom Date Range: The user will be able to choose any date range between the campaign start date and the current day
Today: The date picker will be disabled and the date range will be set to the current day.
Cumulative: The date picker will be disabled and the date range will be set for the duration of the campaign start date to the current day.
Heatmaps display the boundary-based coverage for a campaign using a relative colours gradient scale. The colour of a boundary changes based on the coverage percentage value, and the user is allowed to click on a higher level boundary (state) to drilldown to the lower level regions (state → district).
The chart component uses a react-simple-maps library to render the geographical map of the target region.
The component expects a GeoJSON file which is stored as a static file in the MDMS.
The component fetches the aggregated data from the analytics service and plots it on the geographical map to show the coverage achieved by the boundaries.
The GeoJSON files are stored in MDMS under the “map-config” module:
https://github.com/egovernments/health-campaign-mdms/tree/DEV/data/default/map-config
End point
Request method
Request payload
/egov-mdms-service/v1/_search?tenantId=default
POST
{
"MdmsCriteria": {
"tenantId": "string",
"moduleDetails": [
{
"moduleName": "map-config",
"masterDetails": [
{
"name": "national-map"
}
]
}
]
},
"RequestInfo": {
"authToken": "string"
}
}
/dashboard-analytics/dashboard/getChartV2
POST
{
"aggregationRequestDto": {
"visualizationType": "TABLE",
"visualizationCode": "string",
"queryType": "",
"filters": {},
"moduleLevel": "",
"aggregationFactors": null
},
"headers": {
"tenantId": "string"
},
"RequestInfo": {
"authToken": "string"
}
}
Stacked collection displays the metric data in a columnar fashion on the national dashboard (landing page). It grows vertically based on the length of the metric charts that are configured as part of the collection.
Setting the vizType field to “stacked-collection” will enable this chart. A stacked view is enabled only on the landing page (Example: National dashboard).
A collection of metrics which are displayed in a grid-based fashion. If the “valueType” of a metric is ‘percentage’, then this chart will display a circular progressbar for the metric. This is a vizType which accepts one or more ‘metric’ charts as children.
Setting the vizType field to "stacked-collection" will enable this chart on the dashboard pages (Example: Provincial dashboard).
A list of cards inside a container that grows vertically. The container displays a vertical scrollbar if the number of items in the container is more than the height of the container.
Setting the vizType field to "stacked-table" will enable this chart on the landing page (Example: National dashboard). The vizType accepts a ‘table’ chart as its child and uses the table chart data to render the list of cards on the page.
A card with a horizontal list of items displayed on top of the dashboard. It displays the items in a single row with the labels on top and the value at the bottom.
This chart can be enabled by setting the “vizType” to “bannercard”. This visualisation accepts a ‘table’ chart as its child, and the table chart’s response should include only a single row.
The brush component enabled for bar charts will let the users zoom and pan a bar chart without losing view of any data item. This enables the chart to have any number of bars, and the user can focus on the selected range by adjusting the brush displayed at the bottom of the charts.
No additional setup is required for enabling the brush component. It is enabled on bar charts by default if the chart contains more than one bar.
Reference: https://recharts.org/en-US/examples/BrushBarChart
The visibility of the default filters displayed on the dashboard page can be controlled using a new configuration field introduced in the “MasterDashboardConfig.json” file.
Include the filters that need to be hidden from the dashboard within the “hideFilterFields” array. The UI has the logic to conditionally show/hide the filters based on this field. Allowed elements in the array: ModuleFilter, DateRange, DDR, Ulb, Denomination.
The pie chart component can be made to display the cumulative value in the centre of the chart based on the “showLabel” config field set for pie charts.
Set the “showLabel” field for a pie chart (ChartApiConfig.json) to ‘true’ to enable the label.
The line chart can be configured to display future projections based on the existing data set by enabling a configuration field in the respective chart configuration.
Set the “predictionPath” field in the line chart configuration to point to a specific aggregation path from which the prediction data needs to be calculated. If the “predictionPath” is not available for a line chart, then the prediction will be skipped for the respective chart.
The table chart can be configured to display a footer row at the bottom to show the cumulative total of the row values for all columns with numeric values. Percentages and non-numeric values will not be included in the total value.
Set the “showFooter” field in the line chart configuration to ‘true’. This will enable the footer row for the respective table chart.
The charts can be configured to filter the data only for the current day without hard-coding the date range in the aggregation query.
Set the “filterForCurrentDay” field in the line chart configuration to ‘true’. This will override the date range in the backend and filter only the data that are inserted for the current day.
Line charts can be configured to display percentages calculated based on the results from two aggregation paths.
Ensure that there are exactly two aggregation queries.
The result from the first query will be used as the numerator and the second result set will be used as the denominator for the percentage calculation.
Set ‘percentage’ as the value of the ‘action’ field in the chart configuration.
Line charts can be configured to divide one dataset by another to calculate the quotient value.
Example: This is used in the inventory chart on the health dashboard to calculate the number of days the stock will last in an inventory by dividing the existing count by the target value.
Ensure that there are exactly two aggregation queries .
The result from the first query will be used as the numerator and the second result set will be used as the denominator to calculate the quotient.
Set ‘division’ as the value of the ‘action’ field in the chart configuration.
Line charts can be configured to calculate the sum of two aggregated datasets returned by the aggregation queries.
Example: This is used in the inventory chart that displays the number of stocks that are available in hand by calculating the sum of the incoming stocks.
Ensure that there is more than one aggregation query preset to calculate the sum.
Mention the “actionName” as “SumComputedField” within the chart’s computedFields.
Include the aggregation paths that are required to calculate the sum.
Line charts can be configured to perform the division on a bucket of data by a constant value. This can be used to calculate the percentage share of individual bucket items by comparing with the total sum of data.
Example: This is used in the complaints chart which displays the district-wise share of complaints by comparing against the overall number of complaints registered for the entire province.
Ensure that there are exactly two aggregation queries. The first should return the aggregation results in a bucket. The second result should be the sum of the values.
Set “divisionbyconstant” as the value of the ‘action’ field.
Line charts do not retain the original sort order after performing the computation. Using the sort action, the computed results can be sorted based on the bucket keys or values in both ascending and descending order.
The “computedFields” object accepts the ‘sort’ field and the value should denote the order of the sorting expected.
The ‘sort’ field accepts four values:
- sortValueAsc: To sort based on the increasing order of the values.
- sortValueDesc: To sort based on the decreasing order of the values.
- sortKeyAsc: To sort based on the increasing order of the keys.
- sortKeyDesc: To sort based on the decreasing order of the keys.
Enabling insights’ calculation based on the day shows the comparison between the current day’s data and the previous day’s data.
Setting the ‘interval’ field to ‘day’ inside the ‘insight’ object will enable day-wise insight calculation
The date range selected for fetching the data should not be more than a single day to calculate day-wise insights.
Enabling Insights calculation for a date range shows the comparison between the Data from (project start date to the current date) and (project start date to the previous day).
Setting the ‘insightInterval’ field to “dateRange” inside the “insight” object will enable date-range insight calculation.
The date range Insight interval can be applied only for date ranges more than one day.
Following are the features of the HCM Product Dashboard:
Bar charts with percentage and number toggle.
Brush component for bar charts to zoom in and out for an enhanced view.
Heat maps with zoom-in/out, toggle, and drill-downs to show coverages.
Date range selection through the calendar date picker and toggle buttons to select ‘Today’ and ‘Cumulative’ date ranges.
A new component to display the list of cards based on the chart data, and includes a collection of numeric data and a circular progress bar.
Predictive line graphs to show planned versus actual campaign progression.
Multi-campaign card layout to view campaigns of multiple types happening simultaneously.
Progress bar to show the campaign duration.
Tabular charts with drill-down, search, toggle, and sort functionalities.
Pie charts with the aggregation are shown at the centre.
Stacked bar charts.
Hover definitions and sub-headings to show more details about a specific card.
Download all charts and pages in PDF and JPG formats.
Share all charts and pages in PDF and JPG formats across WhatsApp and email.
The Dashboard of the health campaign platform boasts an array of features that provide a comprehensive view of campaign performance, enabling supervisors to monitor their teams with ease, evaluate campaign progression, and swiftly troubleshoot any roadblocks.
This release made use of the existing DIGIT capabilities and components with minor enhancements to build different widgets to visualize the campaign KPIs. These widgets are categorised into distinct modules. The dashboard is designed such that three levels of distinct users can access the dashboard:
National
Province/State
District
There is a separate national-level page that lists all the indicators related to different campaigns across the country. From this page, the user can navigate to the respective provinces’(state’s) overview page.
The overview page is the landing page for district-level and state-level/provincial-level supervisors once they click on the respective campaign type in the card layout. A national-level supervisor will arrive at this page by clicking on the respective province(state) name from the national dashboard page. This page has a summary of the most important KPIs from each of the individual modules.
The registration and delivery page is common across all levels of supervisors. This page consists of all indicators and visualisations related to the registration of households, individuals, and the delivery of health interventions such as bednets.
The complaints page is common across all levels of supervisors. This page consists of all the indicators related to the complaints filed during the course of a campaign.
The inventory page, which is common across all levels of supervisors, consists of all information related to the stock movement across warehouses.
The features of the dashboard are described below:
General
Each page of the dashboard and individual widgets can be downloaded as PDF and JPG.
Each page of the dashboard and individual widgets can be shared across WhatsApp or email as PDF and JPG.
The tabular charts can be downloaded as Excel sheets.
The search feature in the filter boxes and service tabular reports.
Definitions for all the metrics and chart elements are viewable by hovering over the desired element/metric.
Change the period of data between today and cumulative, or select a custom date through the calendar widget
Card layout navigation for the landing page to cater to different types of health campaigns such as LLIN, SMC, IRS, etc.
National Dashboard Page
View the households, population, and distribution coverage across all provinces/states as aggregate.
View households and population coverage for each province/state through a heat map.
View provinces/states where the campaign is live and navigate to their individual dashboards.
Overview Page
Completeness of the data in the dashboard through the sync rate card.
Daily and cumulative coverage of the households, population, and interventions (bed nets).
Instances where there was no delivery due to any particular reason.
Details regarding complaints raised by frontline workers, supervisors, or the help desk.
Information pertaining to inventory movement in warehouses
Registration & Delivery Page
Coverage of household, individual, and distributions illustrated through bar graphs and heat maps.
Number of households where no delivery has taken place.
Comparison of planned campaign progression and actual campaign progression.
A summary table with drill-down upto village level that details all the KPIs on the page.
Complaints Page
Volume and ratio of complaints generated by the nature of the complaints.
Volume and ratio of complaints generated for different geographical boundaries.
Volume and ratio of the complaints as they move across workflows and statuses.
Information about the resolution time taken for complaints and the average time taken for complaints to move between different statuses.
Inventory Page
Inventory in stock at the warehouse.
Duration for which current inventory in stock will suffice for distribution.
Stock movement details (inbound, outbound, returned) for each warehouse.
Percentage and number toggle for bar charts.
Brush component for bar charts.
Heat maps with zoom-in/out, recenter buttons, and drill-downs.
Today, cumulative toggle filters.
A new component to display the list of cards based on the chart data, and includes a collection of numeric data and a circular progress bar,
Predictive line graphs.
Multi-campaign card layout.
Progress bar to show campaign duration.
Enhanced pie charts that show the aggregated value at the centre.
The Health Campaign Management DIGIT Dashboard is a tool designed to support decision-making for health campaign management teams. It presents important campaign metrics in an intuitive and visually appealing format, promoting transparency, accessibility, and accountability in data management. Users can easily monitor campaign progress, generate detailed reports, measure coverage, and identify potential challenges. This information can inform future planning and help ensure adequate stock management. The dashboard also enables users to track the progress of healthcare campaign services.
The HCM dashboard offers the following capabilities:
Geographical boundary-wise project/Campaign status view
Consolidated and interactive dashboard, with a progress bar to show the duration of the campaign and its progress over time.
Multi-campaign card layout for easy comparison and analysis.
Various filters are available to customise and focus on specific analytical data. Convenient toggle filters for viewing data by today or cumulative figures.
Visually appealing format for easy understanding of a campaign’s progress.
Access to key metrics to measure campaign coverage and identify areas for improvement.
Ability to drill-down the chart and explore in-depth details for applicable key performance indicators (KPIs).
Heat maps with zoom-in/out, recenter buttons, and drill-downs for an in-depth analysis.
Facilitation of data-driven decision-making.
Enhanced pie charts display the aggregated value in the centre of the chart.
Clear sub-headings for detailed information.
Clear and comprehensive explanations of each attribute.
Generation of detailed summary reports with a single click.
Ability to track the progress rate of healthcare campaign services.
Predictive line graphs to project future campaign progress.
Planning stock requirements and future campaigns.
Ability to toggle the chart between percentage and number views.
User Role
Scope of Action
Role Description
Country head
View only
This indicator shows the number of households that were visited by all the frontline workers (FLWs) across all the provinces for today for the selected campaign type.
Country head
View only
This indicator shows the number of the households that were visited by all the FLWs across all the provinces till today since the start of the campaign for the selected campaign type.
Country head
View only
This indicator shows the total population covered by the FLWs across all the provinces for today for the selected campaign type.
Country head
View only
This indicator shows the total population covered by all (FLWs across all the provinces till today since the start of the campaign for the selected campaign type.
Country head
View only
This indicator shows the total bed nets distributed by all FLWs across all the provinces for today for the selected campaign type.
Country head
View only
This indicator shows the total bed nets distributed by all the FLWs across all the provinces till today since the start of the campaign for the selected campaign type.
Country head
View the percentage of households covered in every province.
Hover on any province to view the province name and percentage.
Hover on the title to view the definition.
Click on any province to view the district-level-wise household coverage data.
Close the district filter to go back to the province-level view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user will be able to view the percentage of the households that have been covered till the latest date as per the micro-plan targets set in each province.
Country head
View the percentage of population covered in every province.
Hover on any province to view the province name and percentage.
Hover on the title to view the definition.
Click on any province to view the district-level-wise population coverage data.
Close the district filter to go back to the province-level view.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
The country head will be able to view the percentage of population that has been covered till the latest date as per the micro-plan targets set in each province.
Country head
View the list of provinces where the campaign was performed or is going on.
Click on “View dashboard”.
Search for a specific province name.
In the tabular form, the list of the provinces where the campaign has performed or is ongoing, will list the data points of “Total households visited today”/“Total Household visited cumulative”/ “Household Coverage”/ “Population Coverage”.
It also has a “View Dashboard” button which navigates the user to a specific province-level dashboard.
User Role
Scope of Action
Role Description
Country head
Province head
District officer
View the data sync rate for the assigned/selected province/district.
Hover on the indicators to see the definitions.
Hover on the title to view the definition.
This will show the total number of users (FLWs), who are assigned for duty within that province/district for the selected date range.
Country head
Province head
District officer
View the data sync rate for the assigned/selected province/district.
Hover on the indicators to see the definitions
Hover on the title to view the definition.
This is the count of the total number of FLWs who have synced the data at least once in a day.
(Multiple syncs from the same device not considered in a day).
Country head
Province head
District officer
View the data sync rate for the assigned/selected province/district.
Hover on the indicators to see the definitions.
Hover on the title to view the definition.
This is the percentage of the total FLWs who have synced their device at least once for the selected date range.
Country head
Province head
District officer
View the households visited.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This field shows the count of households visited for the particular day or a date range as selected.
Country head
Province head
District officer
View the households targeted.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
This field shows the count of household targets to be completed for a particular day or a date range as selected.
Country head
Province head
District officer
View the cumulative households visited.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
This field shows the total count of the households that have been visited in the province/ district till yet (From the starting day of the campaign).
Country head
Province head
District officer
View the household coverage.
Hover on the title to view the definition..
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is the percentage of household coverage achieved against the micro-plan target set from the campaign start date (Cumulative data).
Country head
Province head
District officer
View the population covered.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
This field shows the total population that has been covered for the selected day or the date range.
Country head
Province head
District officer
View the cumulative population covered.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
This field shows the tota population that has been covered from the start of the campaign.
Country head
Province head
District officer
View the population targeted.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This field shows the total population that needs to be covered for a particular day or a selected date range as per the micro plan set.
Country head
Province head
District officer
View the population coverage.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
This is the percentage of citizens’ coverage achieved against the microplan target set from the campaign start date (Cumulative data).
Country head
Province head
District officer
View the bed nets distributed.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
This field shows the total number of bed nets that have been delivered for a particular day (today) or a selected date range.
Country head
Province head
District officer
View the cumulative bed nets distributed.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
This field shows the total count of bed nets that have been delivered to households from the starting date of the campaign.
Country head
Province head
District officer
View the bed nets targeted.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This field shows the total number of bed nets that have been targeted for distribution as per the micro-plan set for the day or the selected date range.
Country head
Province head
District officer
View the bed nets distribution coverage.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This field shows the total percentage of bed nets distribution coverage achieved against the micro-plan target.
Country head
Province head
District office
View the households where delivery did not happen.
Drill-down chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This shows the total number of households where the intervention was not delivered due to any particular reasons (not limited) such as:
Rejected by the beneficiary.
House was closed.
Beneficiary relocated.
Country head
Province head
District officer
View the complaints generated.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The complaint card shows the data visualisation in the form of a pie-chart of the statuses of all complaints registered for the selected date range or a day. These statuses are: :
Open
Resolved
Rejected
Country head
Province head
District officer
View the households’ coverage ranking.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user will be able to view a bar-graph for the data of the total percentage of households covered as per the micro-plan at the assigned user boundary level where the interventions have been delivered.
The district/ administrative post bars in the graph are arranged in a descending order (highest - lowest) so that the user can compare the campaign coverage across the different boundaries.
Country head
Province head
District officer
View the number of days to the last inventory bar chart.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can view the bar graph, which will indicate to the user that in each boundary, how many days can the existing stock across all warehouses within those boundaries be sufficient for the campaign
The bar graph shows the ‘boundary’ data at the x-axis as assigned and the “Number of days” in the y-axis.
There can be multiple warehouses in each boundary, so the collective data of the stock is compared to the current daily consumption and then the prediction is depicted in the graph.
Country head
Province head
District officer
View the checklists completion rate in the bar chart.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is a bar graph chart that shows the percentage of supervisors who have filled all assigned checklists for the selected date range or a day.
User Role
Scope of Action
Role Description
Country head
Province head
District head
Users can toggle the graph data between the count (actual number) and percentage against the micro-plan targets.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user will be able to view a bar-graph for the data of the total number of households where the interventions have been covered (visited and delivered plus visited but not delivered) by the FLW as per the selected day or a date range.
Country head
Province head
District head
The user can toggle and view the population covered data in two different formats:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Here the user will be able to view the bar graph for the data count of the total population that has been covered (visited and delivered plus visited but not delivered) for the intervention delivery by the FLWs for the selected day or the date range.
Country head
Province head
District head
The user can toggle and view the data of Bed Nets Distributed to the households in two different format:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
In this bar graph, the user will be able to view the data of the total bed nets that have been delivered by the FLWs to the households for the selected day or the date range.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Here the user will be able to view the bar graph, for the data count of “Number of households” where the intervention (such as bed nets) delivery have not taken place due to a particular reason as per the selected day or a date range.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The current geo map is in the form of a heat map, which shows the “percent of targets that have been achieved” by the FLW’s as per the micro-plan set for the boundary data.
The Geo map has a RED-AMBER-GREEN color code which helps in depicting the performance of the targets achieved.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The current geo map is in the form of a heat map which shows the “percent of population that has been covered” (i.e. Intervention delivered) as per the set micro-plan target.
The geo map has a RED-AMBER-GREEN colour code which helps in depicting the performance of the target achieved.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The current geo map is in the form of a heat map which shows the “percent of Bed nets” that has been distributed to the households as per the micro-plan for the selected boundary data from the start date of the campaign.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is a line chart comparison of the campaign’s daily plan target versus the actual daily progress.
Household: This will be a line chart that shows the campaign progression for households delivery planned against the actual.
Population: This will be a line chart that shows the campaign progression for population covered planned against the actual.
Bed nets: This will be a line chart that shows the campaign progression for bed nets distributed that is planned against the actual.
The X-axis shows that ‘date’ from when the campaign started till the campaign end date, whereas the Y-axis shows the coverage count.
The campaigns target date marked in the chart makes it easy for the user to predict by which date the campaign will meet its target.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
The boundary tabular Report have following KPI data:
Target achieved (% of household): Percentage of household coverage achieved against the micro-plan targets.
Target achieved (% of population): Percentage of population coverage achieved against the micro-plan targets.
Target achieved (% of bednets distributed): Percentage of bed nets distribution coverage achieved against the micro-plan targets.
Households visited: The total number of households visited for the selected date range.
Population covered: This is the total population covered as per the selected date range.
Bednet distributed: This is the total number of bed nets distributed as per the selected date range.
Not delivered (Closed): This is the total number of households where the FLW went to deliver the bed nets but the household was ‘closed’. Therefore, the intervention was not delivered.
Not delivered (Refused): This is the total number of households where the FLW went to deliver the bed nets, but the household ‘refused’ the intervention. Therefore, the intervention was not delivered.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search day.
This is a tabular chart that shows the summary data for each day of the campaign.
The date tabular report have following KPI data:
Target achieved (% of household): Percentage of household coverage achieved against the micro-plan targets for a particular date.
Target achieved (% of Population): Percentage of population coverage achieved against the micro-plan targets for a particular date.
Target achieved (% of bednets distributed): Percentage of bed nets distribution coverage achieved against the micro-plan targets for a particular date.
Households visited: The total number of households visited for the selected date range for a particular date.
Population covered: This is the total population covered as per the selected date range for a particular date.
Bed net distributed: This is the total number of bed nets distributed as per the selected date range for a particular date.
Not delivered (Closed): This is the total number of households where the FLW went to deliver the bed nets but the household was ‘closed’. Therefore, the intervention was not delivered for a particular date.
Not delivered (Refused): This is the total number of households where the FLW went to deliver the bed nets but the household ‘Refused’. The intervention, therefore the intervention, was not delivered for a particular date.
User Role
Scope of Action
Role Description
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is a bar chart that shows the total complaint data for the selected day or the date range. On the X-axis, the user can view the boundary data, and on the Y-axis, he/she can view the count of complaints.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is a pie chart view which shows the percentage of the different category types of complaints that have been created by the warehouse manager, supervisor, and the FLW.
All the users will see the complaint data as per their allotted boundary-level.
Country head
Province head
District head
The user can toggle and view the data of complaints by their status in two different formats:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is a stacked bar chart that shows the split data of complaints by their status across different boundaries for the selected date or date range.
The status of the complaints are:
Resolved
Open
Dropped
Country head
Province head
District head
The user can toggle and view the data of complaints by their type in 2 different formats:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is a stacked bar chart that shows the split data of complaints by their type across different boundaries for the selected date or date range.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This is a bar chart which shows the total complaints for each sub-boundary as a percentage of the total complaints generated within the assigned/selected province/district.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The bar graph shows the information: In each boundary, what is the average time required for the resolution of all the complaints generated for a day or a date range selected.
In the graph, the X-axis shows the boundary data, whereas the Y-axis shows the number of hours.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
This is the complete statistical report of the complaints that have been generated by the supervisor, warehouse manager and the FLWs in the campaign across the specific boundaries as per the selected day or date range.
The fields that the summary report focus on:
Boundary name: This is the district/AP/ locality/village name as per the user role assigned.
Register: This is the count of the total complaints that have been created in the system for the respective boundary irrespective of their status for the day or the selected date range.
Resolved: This is the count of the total complaints that have the status marked as ‘resolved’ in the system for the respective boundary for the day or the selected date range.
Dropped by Supervisor: This is the count of the total complaints that have the status marked as ‘rejected’ in the system for the respective boundary for the day or the date range.
Open: This is the count of the total complaints that have the status marked as open in the system for the respective boundary for the day or the date range (All the complaints which are not ‘Resolved’ or ‘Rejected’ are treated as ‘Open’).
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search day.
This is the complete statistical report of the complaints that have been launched by the supervisor, warehouse manager, and the FLWs in the campaign, at each day/date.
The fields that the summary report focus on:
Date: This is the field where the user will see the dates.
Register: This is the count of the total complaints that have been created in the system on a specific date irrespective of their status and boundary.
Resolved: This is the count of the total complaints that have the status marked as ‘resolved’ in the system till the specific date, irrespective of the boundaries.
Dropped by supervisor: This is the count of the total complaints that have the status marked as ‘rejected’ in the system till the specific date, irrespective of the boundaries.
Open: This is the count of the total complaints that have status marked as ‘open’ in the system till the specific date, irrespective of the boundary
(All the complaints which are not ‘Resolved’ or ‘Rejected’ are treated as ‘Open’).
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
This is the summary report which only focuses on the data of the ‘OPEN’ complaints in the campaign.
The summary report of the open complaints can be viewed as per the boundary level.
The fields that the summary report for the open complaints focus on:
Boundary name: This lists the name of the boundaries as per the user assigned role, and users can also see the status of ‘open complaints’.
Open since <6 hrs: This is the count of complaints which are open from the last 6 hours, and yet pending for any further action till today.
Open since >=6 hrs & <12 hrs: These are the counts of complaints which are open for more than or equal to 6 hours but less than 12 hours, and yet pending for any further action.
Open since >=12 hrs & <24 hrs: These are the counts of complaints which are open for more than or equal to 12 hours but less than 24 hours, and yet pending for any further action.
Open since >=24 hrs & <48 hrs: These are the counts of complaints which are open for more than or equal to 24 hours but less than 48 hours, and yet pending for any further action.
Open since >=48 hrs: These are the counts of complaints which are open from more than or equal to 48 hours, and yet pending for any further action.
User Role
Scope of Action
Role Description
Country head
Province head
District head
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Here the user can view the bar graph, which will indicate to the user that in each boundary, how many days can the existing stock across all warehouses within those boundaries will be sufficient for the campaign
The bar graph shows the ‘boundary’ data at the x-axis as assigned and the “number of days” in the y-axis.
There can be multiple warehouses in each boundary, so the collective data of the stock is compared to the current daily consumption and then the prediction is depicted in the graph.
Country head
Province head
District head
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user is able to view the side-by-side bar graph which indicate the user, about the current “availability of stock”, as of today (i.e. what is the stock in hand) at the boundary and compare it against what is the “required stock” to complete the campaign as per the micro-plan set for the boundary.
Country head
Province head
District head
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
The report for the inventory section have the following boundary KPI values as:
Boundary name: This will indicate the boundary data to the user as per their role assigned.
Nets to receive as per micro-plan: This shows the total number of bed nets, including all the warehouses in the boundary, that should have been received as per the bed nets micro-plan set, for the selected date or date range.
Nets received: This shows the total number of actual bed nets that the warehouses in the boundary have received for the selected date or date range.
Nets distributed: This is the count of the bed nets that has been sent out/ distributed to the households, for the boundary for the selected date range.
Nets returned: This is the total count of bed nets that have been returned via all the warehouses within the boundary for the selected date or date range.
Nets in stock: This is the total number of bed nets that are available in the boundary with all the warehouses as of today.
Days to last: This is the total number of days the bed net stock across all the warehouses that can last as of today for the boundary.
User Role
Scope of Action
Role Description
Country head
Province head
District head
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by national-level supervisors as per the date or date range selected for the selected province.
Provincial-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by national-level supervisors as per the date or date range selected for the assigned province.
District-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by national-level supervisors as per the date or date range selected for the assigned district.
Country head
Province head
District head
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level users:
Here the user will be able to view the bar chart that shows the percentage completion of the different checklists by provincial-level supervisors as per the date or date range selected for the selected province.
Provincial-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by provincial-level supervisors as per the date or date range selected for the assigned province.
District-level users:
Here the user will be able to view the bar chart that shows the percentage completion of the different checklists by provincial-level supervisors as per the date or date range selected for the assigned distict.
Country head
Province head
District head
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by district-level supervisors as per the date or date range selected for the selected province.
Provincial-level users:
Here the user will be able to view the bar chart that shows the percentage completion of the different checklists by district-level supervisors as per the date or date range selected for the assigned province.
District-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by district-level supervisors as per the date or date range selected for the assigned district.
Country head
Province head
District head
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Here the user will be able to view the bar chart that shows the percentage of total workers among all the users created within each boundary who have synced their device at least once, for the selected date range.
A formal sign-off came from the product team after completing the functional, UI, and data testing of the dashboard for V 1.0 capabilities. No critical show-stopper issues were observed.
The dashboard has been tested on the following aspects:
Data Accuracy:
Data ingested from the HCM App is reflected correctly on the dashboard.
Accuracy of calculations and aggregations.
Data displayed is up-to-date and correctly refreshed.
Data Completeness:
All data ingested from the app is reflected in the dashboard.
Presence of all metrics, and dimensions as expected.
Functionality:
Data filter, search, sort, drill-downs (tabular charts), data export, download, hover, date picker, and navigation functionalities.
UI:
The UI elements match the design in Figma.
All the widgets, graphs, and charts as per the design are present on the dashboard.
The other set of features that were part the testing include:
Lat-long maps
Multi-level drilldowns for bar charts
Supervision module
About, FAQ, and Calculation pages
Heat/Lat-long maps, re-centre button
Bar chart with target line on the Registration & Delivery page
The data testing was done by ingesting the micro plan data and transactional data for 1 province. However, testing with high-volume data (ingestion through Kibana) to simulate the scenario of Group IV distribution (3 provinces) and for outliers is pending and will be completed by June 1st half. All the known functional and UI bugs, and enhancements were noted during testing. The estimated resolution timeline is as follows:
Medium priority Bugs - May 25th
Low-priority bugs and enhancements Mid-June
Planned vs Actual graph - May 19th
The following are the user stories for the Campaign Management Dashboard:
Uncovered Population Bar Chart with Target Line
Description
Develop the uncovered population bar graph with target line for the registration & delivery page
Common Actions and Validations
Users who have access to this: All users
CTA: Drill down should be applicable by clicking on each bar
For National and provincial users: The default aggregation will be at the district level. ** The drill down will be as follows for the bars *** District → AP → Locality → Village ** For the Target line the drill-down will be as follows: *** Province → District → AP → Locality
For District users: The default aggregation will be at AP level ** The drill down will be as follows for the bars *** AP → Locality → Village ** For the Target line, the drill-down will be as follows: *** District → AP → Locality ** AP → Locality → Village
Upon hovering over the heading, the definitions as per the Excel sheet should appear
The axes labels should be there as per figma ** For the target line, the label should show as per figma ** For the bars, the legend should read as “Uncovered population”
The card should be downloadable as pdf/jpg
The card should be sharable as pdf/jpg across WhatsApp, email
Hovering over each bar on the graph should display the ** Value for that bar ** The name of the boundary
Upon drilling down, the filter should appear with an 'x' to remove the filter as per figma
For each level of drill-downs, the filter should keep on appearing and only display results applicable for that filter
The target line should change according to the calculation sheet for each level of drill-down
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Households not visited against Target
Bar chart with target line
Product Testing: HCM Dashboard
Description
Functional & Data Testing: HCM Dashboard
Actions & Validations
To test the HCM Dashboard on the following aspects:
Data Accuracy: Test the accuracy of the data displayed on the dashboard. This can include:
Compare data on the dashboard with the source data to ensure that it matches.
Check that calculations and aggregations are accurate.
Verify that the data displayed on the dashboard is up-to-date and has been correctly refreshed.
Data Completeness: Test that all expected data is being displayed on the dashboard. This can include:
Verify that all expected data sources are being accessed and that no data is missing.
Check that all expected metrics and dimensions are present on the dashboard.Data Consistency: Ensure that data displayed on the dashboard is consistent with other sources of data. This can include:
Verify that data displayed on the dashboard matches data displayed in other systems.
Ensure that all metrics and dimensions are consistently defined and used across the dashboard.
Performance: Test how well the dashboard performs. This can include:
Test the dashboard loading time and ensure that it is within acceptable limits.
Test how quickly data is refreshed on the dashboard.
Verify that the dashboard can handle large amounts of data without performance degradation.
User Acceptance: Test that the dashboard meets the needs of end-users. This can include:
Validate that the data and metrics displayed on the dashboard are relevant to end users.
Ensure that the dashboard is intuitive and easy to use.
Verify that the dashboard provides the necessary level of detail and interactivity.
Security: Test that the dashboard is secure. This can include:
Ensure that only authorised users have access to the dashboard.
Test that users can only view data they are authorised to see.
Verify that the dashboard is protected against common security vulnerabilities.
Acceptance Criteria
All actions and validations are satisfied
Limit Drill-down for Summary report in Inventory Page
Description
Limit Drill-down for Summary report in Inventory Page
Reasoning
The distribution of warehouses is such that there are District warehouses (ADs) and Community warehouses (ACs) within each district.
The default view will show the aggregation of stock movement metrics across both ADs and ACs within a district. But in the next level of drill-down, i.e. at the AP level, the aggregation will be shown across ACs and this excludes ADs which are tagged to that district.
Showing drill-downs from District → Individual warehouses with the current DIGIT tabular chart configuration is not achievable. Since an aggregation query is required and showing each warehouse stock movement doesn’t require aggregation
Actions & Validations
Disable the drill-down for the Summary Chart in the Inventory Page.
The default view will be set district wise or AP wise depending on the level of supervisors
For National/Provincial supervisors: ** The default view will show districts and each district will aggregate the stock movements of all ADs and ACs within that district
For District supervisors: ** The default view will show APs and each AP will aggregate the stock movements of {color:#ff5630}only ACs{color} within that AP.
Clicking on the district name Should not open the next level of drill-down
The district/AP names should be shown in the DIGIT font colour for non-hyperlink fonts
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
This should not change any other configurations
This change should not affect the existing calculations
The change should not affect any other widgets in the dashboard
KPI calculations review
KPI calculations review
District Supervisor Checklists completion rate bar chart
Requirement
Develop the district supervisor's checklists completion rate bar graph
Common Actions and Validations
This graph will not have any drill-downs
Upon hovering over each KPI, the definitions as per the excel sheet should appear
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis
In the absence of data, the respective error message should be shown
The graph should change w.r.t to the date range filter
Default filter will be TODAY
The frequency of checklist fill rate for each supervisor against checklist name is as below
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Provincial Supervisor Checklist fill rate bar chart
Requirement
Develop the Provincial supervisor's checklists completion rate bar graph
Common Actions and Validations
This graph will not have any drill-downs
Upon hovering over each KPI, the definitions as per the excel sheet should appear
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis
In the absence of data, the respective error message should be shown
The graph should change w.r.t to the date range filter
Default filter will be TODAY
The frequency of checklist fill rate for each supervisor against checklist name is as below
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Registration & Delivery Page Drilldowns
Registration & Delivery Page Drilldowns
Overview Page - Drilldowns
Description
Implement drill downs for the widgets on the Overview page
Actions & Validations
The drill-downs for each widget should be configured separately
Applying the drill-down on any one chart should not affect another
This page will be accessible for all levels of dashboard users by clicking on the Registration & Delivery tab or from the side panel
The entire page is downloadable and sharable (Whatsapp, email) as pdf/jpg
Each card should be downloadable and sharable (Whatsapp, email) as pdf/jpg
The ‘Today’s' Date is visible on the top header and will be the default filter for all cards
The custom date range picker should work as per the DIGIT configuration
The breadcrumbs should be present to navigate as per Figma
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Updating Chart colours for HCM dashboard
Updating Chart colours for HCM dashboard
Complaints by Type Pie chart
Requirement
Develop the Complaints by type pie chart
Common Actions and Validations
Hovering over each pie should display the data in % and absolute numbers along with the labels
The % values should be shown next to each slice of the pie by default
The legends should be there indicating the colour code against the type of complaint
Upon hovering over the heading the definitions as per the excel sheet should appear
In the absence of data, the respective error message should be shown
The graph should change w.r.t to the date range filter
The default filter will be TODAY
The calculation for each slice should be as per the KPI sheet
The Total value should be calculated as separate and shown at the centre of the pie
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Complaints by Boundary bar chart
Requirement
Develop the Complaints by status bar chart
Common Actions and Validations
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis
Upon hovering over the heading the definitions as per the excel sheet should appear
In the absence of data, the respective error message should be shown
The graph should change w.r.t to the date range filter
The default filter will be TODAY
There will not be any toggle for this chart
The brush component should be available to zoom in/out and horizontal scroll
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs
Complaints by Status Stacked bar chart
Requirement
Develop the Complaints by status bar chart
Common Actions and Validations
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis
Upon hovering over the heading the definitions as per the excel sheet should appear
In the absence of data, the respective error message should be shown
The graph should change w.r.t to the date range filter
The default filter will be TODAY
There should be toggle for % and Number
For % toggle ** Each bar should sum to 100% with Open, resolved, and rejected as splits (For eg: 25%, 30%, 45%) ** Each stack should be distinguishable by color as per Figma
For Number toggle ** The actual value of the number of complaints should be shown on the bars. (Eg: Open: 150, Resolved: 40, Rejected: 20)
The calculation for each toggle should be as per Figma
The brush component should be available to zoom in/out and horizontal scroll
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Landing Page Creation - National, Provincial, District users
Requirement
Create the Landing pages for all levels of dashboard users
Common Actions and Validations
This landing page will be common for all the services that the user has access to such as Dashboard, User Management, Complaints, etc.
There will be different landing pages for National, Provincial, and District level supervisors
For the National supervisor: ** The UI should be as per the Figma design ** The type and the country name should be listed as CTA links under the Dashboard card *** Eg: {{LLIN - Mozambique}} *** {{MDA - Mozambique}} *** {{IRS - Mozambique}} etc. ** Clicking on the respective link should navigate to the national-level page for that type of campaign. For eg: Clicking on the {{LLIN -Mozambique}} link should take the user to the LLIN campaign National level page for Mozambique
For the Provincial level supervisors: ** The UI should be as per the Figma design ** The type and the province name should be listed as CTA links under the Dashboard card ** If the user is tagged to different campaigns(projects), then the CTA should have both the campaign type and the campaign boundary mentioned *** For eg: If ‘Provincial Supervisor 1’ has access to only the LLIN campaign in Tete province, then only ‘'{{LLIN - Tete}} '' should be listed as CTA in the card, clicking on which the user will be navigated the provincial level dashboard for Tete for LLIN campaign *** If Provincial Supervisor 2 has access to LLIN and IRS campaigns in Tete and LLIN campaign in Nampula and MDA in Maputo, then the Dashboard card will have the following CTAs **** {{LLIN - Tete}} **** {{IRS - Tete}} **** {{LLIN - Nampula}} **** {{MDA - Maputo}} *** Clicking on each of them should navigate the user to the respective campaign type in the respective provinces
For the District level supervisors: ** The UI should be as per the Figma design ** The type and the district name should be listed as CTA links under the Dashboard card ** If the user is tagged to different campaigns(projects), then the CTA should have both the campaign type and the campaign boundary mentioned *** For eg: If ‘District Supervisor 1’ has access to only the LLIN campaign in Angonia District, then only ‘'{{LLIN - Angonia}} '' should be listed as CTA in the card, clicking on which the user will be navigated the district-level dashboard for Angonia for LLIN campaign *** If District Supervisor 2 has access to LLIN and IRS campaigns in Angonia and LLIN campaign in Zumbo and MDA in Chiuta, then the Dashboard card will have the following CTAs **** {{LLIN - Angonia }} **** {{IRS - Angonia}} **** {{LLIN - Zumbo}} **** {{MDA - Chiuta}} *** Clicking on each of them should navigate the user to the respective campaign type in the respective provinces
Acceptance Criteria
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
The landing page should be working as above for all 3 types of users
The users should only have access to those campaigns to those they are assigned"
Custom style for Overview cards
Scope:
To add custom styling to the existing dashboard collection component to match the look expected based on the figma mockup
The same icons used in the figma deigned should be exported to the web app
Creation of campaign links card
Scope:
To create a custom card on the user landing page with the links to all the campaigns
The cards should be shown for both National and Provincial supervisors
The card needs to be tailored for health campaigns and the list of campaigns that are active needs to be fetched from MDMS configuration rather than making it static within the UI
Bed nets distributed KPI card
Requirement
Bed nets distributed KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
Failure to load data / not having data should show error message accordingly
No CTA on the card
Each metric within the card should behave as per below for the application of the date filter
Bed nets distributed: ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Total bed nets distributed ** Insights → Applicable ** Definition on hover → Applicable ** Date Range Filter Applicable → No
Bed nets Targeted for distribution ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Bed nets Coverage ** Insights → Yes ** Definition on hover → Applicable ** Date Range Filter Applicable → No
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Population Covered KPI Card
Requirement
Population covered KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
Failure to load data / not having data should show error message accordingly
No CTA on the card
Each metric within the card should behave as per below for the application of the date filter
Population Covered: ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Total Population Covered ** Insights → Applicable ** Definition on hover → Applicable ** Date Range Filter Applicable → No
Population Targeted ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Population Coverage ** Insights → Yes ** Definition on hover → Applicable ** Date Range Filter Applicable → No
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Households KPI card
Requirement
Households visited KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
Failure to load data / not having data should show error message accordingly
No CTA on the card
Each metric within the card should behave as per below for application of date filter
Households visited: ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Total households visited ** Insights → Applicable ** Definition on hover → Applicable ** Date Range Filter Applicable → No
Households Targeted ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Households Coverage ** Insights → Yes ** Definition on hover → Applicable ** Date Range Filter Applicable → No
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
National Supervisors Checklists Completion Rate Bar graph
Requirement
Develop the National supervisor's checklists completion rate bar graph
Common Actions and Validations
This graph will not have any drill-downs
Upon hovering over each KPI, the definitions as per the excel sheet should appear
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis
In the absence of data, the respective error message should be shown
The graph should change w.r.t to the date range filter
Default filter will be TODAY
The frequency of checklist fill rate for each supervisor against checklist name is as below
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Data Sync Rate Bar graph
Requirement
Develop the Data sync rate bar chart for the HCM Dashboard
Actions & Validations
The graph should be ordered in alphabetical order of the X-axis values
The graph should show district-wise data for national and provincial supervisors' dashboards by default before drilling down
The graph should show AP-wise data for district supervisors' dashboards by default before drilling down
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis ( Eg: X axis: Districts Y axis: Sync Rate)
The definition as per the excel sheet should appear as subheading beneath the chart title
In the absence of data, the respective error message should be shown
The graph should not change w.r.t date filter and should always show TODAY’s value
The graph should enable drilling down to the lowest boundary levels
The drilldown will be: ** For National & Provincial supervisors, the default aggregation will be at the district level *** District → AP ** For District level supervisors, the default aggregation will be at AP level and there won’t be any drill-down post that
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Summary Report
Requirement
Develop the summary report tabular chart for the Inventory page of the HCM Dashboard
Common Actions and Validations
Users who have access to this: All levels
+For National and provincial users: The default aggregation will be at the district level.+ ** The drill down will be as follows *** District → District level warehouses + AP level warehouses + Locality/Village level warehouses ** Eg: District A, has *** 2 district level warehouses *** 3 AP level warehouses *** 2 community level warehouses ** As a National/Provincial supervisor, I will see District A, B, C etc…as rows ** Clicking on District A will show the drill down with the following rows *** District A warehouse 1 *** District A warehouse 2 *** District A AP w/h 1 *** District A AP w/h 2 *** District A AP w/h 3 *** District A community w/h 1 *** District A community w/h 2
+For District users: The default aggregation will be at AP level+ ** The drill down will be as follows *** AP → AP level warehouses + Locality/Village level warehouses ** Eg: AP A, has *** 3 AP level warehouses *** 2 community/village level warehouses ** As a District supervisor, I will see Administrative Post A, B, C etc…as rows ** Clicking on AP A will show the drill down with the following rows *** AP A warehouse 1 *** AP A warehouse 2 *** AP A warehouse 3 *** AP A community/village w/h 1 *** AP A community/village w/h 2
This tabular chart WILL NOT have a day wise toggle ** Date Filter → Applicable ** Each boundary name (district or AP) will be clickable and clicking on it will drill down the table to the next level. The corresponding boundary name will appear as filter with a 'x' to remove the filter ** !Screenshot 2023-02-07 at 9.51.25 AM.png|width=107,height=45! All the columns should be sortable by clicking on the column heading (alphabetically / desc/asc) This should work as per how it works in other DIGIT dashboard tabular charts ** There will be no insights for each cell ** The pagination should be followed as per Figma ( 10 rows per page)
The tabular chart should be downloadable as excel
There should be search box in the top for searching the name of the boundary
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Warehouse Distribution Lat/Long Map
Requirement
Develop the warehouse distribution lat long map for the HCM Dashboard
Common Actions and Validations
All the warehouses within the province(For national and Provincial supervisors) & District (For district supervisors) should be shown as points
Upon clicking on any particular warehouse coordinate, the following details of that warehouse should be shown ** Warehouse ID: From the Front line app ** Stock received: Calculation as per 4.5 (KPI sheet) ** Stock distributed: Calculation as per 4.6 (KPI sheet) ** Stock returned: Calculation as per 4.7 (KPI sheet) ** Stock in hand: Calculation as per 4.8 (KPI sheet) ** Will last for: Calculation as per 4.9 (KPI sheet) ** Status *** Sufficient: Highlighted In {color:#36b37e}Green{color} color and font color as per figma **** If ‘Will last for’ >= (Difference between Today’s Date & Campaign End date) *** Insufficient: Highlighted In {color:#bf2600}Red{color} color and font in red color **** If ‘Will last for’ < (Difference between Today’s Date & Campaign End date)
Clicking on ‘+' '-’ should zoom in/out of the map
If the coordinates are staggered together, upon zooming in, then the coordinates of one warehouse should be distinguishable from the other
The zoom-in level should be kept to the extent where individual warehouses are distinguishable from one another
For District Supervisors
Tooltip upon hovering over any boundary should show that boundary name and the total no.of households covered within that boundary
Clicking on ‘+' '-’ should zoom in/out the map
If the coordinates are staggered together, upon zooming in, then the coordinate of one household should be distinguishable from the other.
The zoom-in level should be kept at the extent where individual households are distinguishable from one another
Clicking on another boundary should update the table with the data for that boundary
Hovering over any boundary should show in the tooltip the following ** the name of the boundary ** the static message: “{{Click on any warehouse to see stock movement details}}”
Hovering should highlight the boundary in different stroke color
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The total number of geo coordinates should match with the total number of households in the tooltip for each boundary
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
The hover, and zoom in/out functionalities should work as mentioned above"
Stock in Hand Bar chart
Requirement
Develop the stock in hand bar chart in the Inventory module for the HCM Dashboard
Common Actions and Validations
This chart will be a side by side bar chart that shows Required bed nets and Available bed nets
The brush component should be there in the horizontal axis for zoom in/out and for horizontal slide
At 100% zoom out, all the bars should be visible at the same time
The graph should be ordered in alphabetical order of the X-axis values
The graph should show district wise data for national and provincial supervisors dashboards by default before drill down
The graph should show AP wise data for district supervisors dashboards by default before drill down
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis ( Eg: X axis: Districts Y axis: No.of days to last inventory)
The definition as per the excel sheet should appear as sub heading beneath the chart title
In the absence of data, the respective error message should be shown
In the absence of data for any boundaries, the respective bar name/s should be shown in the X-axis with the bar height =0
The graph should not change w.r.t date filter and should always show TODAY’s value
The graph should enable drill down to lowest boundary levels
The drill down will be: ** For National & Provincial supervisors, the default aggregation will be at district level *** District Name → District level warehouses + AP level warehouses + Locality level warehouses + village level warehouses ** For District level supervisors, the default aggregation will be at AP level *** AP Name → AP level warehouses + Locality level warehouses + village level warehouses
+Note: Eg: Under District A, if there are 5 district warehouses and 10 community warehouses, then the total number of warehouses within district A will be 15. So the bar for District A upon drill down will show 15 bars.+ +So the sum total of 'stock in hand' across all 15 warehouses should be considered.+
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
No. of days to last inventory Bar chart
Requirement
Develop the Inventory Status bar chart
Common Actions and Validations
The graph should be ordered in alphabetical order of the X-axis values
The graph should show district wise data for national and provincial supervisors dashboards by default before drill down
The graph should show AP wise data for district supervisors dashboards by default before drill down
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis ( Eg: X axis: Districts Y axis: No.of days to last inventory)
The definition as per the excel sheet should appear as sub heading beneath the chart title
In the absence of data, the respective error message should be shown
The graph should not change w.r.t date filter and should always show TODAY’s value
The graph should enable drill down to lowest boundary levels
The drill down will be: ** For National & Provincial supervisors, the default aggregation will be at district level *** District Name → District level warehouses + AP level warehouses + Locality level warehouses + village level warehouses ** For District level supervisors, the default aggregation will be at AP level *** AP Name → AP level warehouses + Locality level warehouses + village level warehouses
+Note: Eg: Under District A, if there are 5 district warehouses and 10 community warehouses, then the total number of warehouses within district A will be 15. So the bar for District A upon drill down will show 15 bars.+ +So the sum total of 'stock in hand' across all 15 warehouses should be considered.+ +The micro plan target should be the daily bednets target for province A+
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Summary Report
Requirement
Develop the summary report tabular chart for Registration & Delivery page of the HCM Dashboard
Common Actions and Validations
Users who have access to this: All levels
For National and provincial users: The default aggregation will be at district level. ** The drill down will be as follows *** District → AP → Locality → Village
For District users: The default aggregation will be at AP level ** AP → Locality → Village
For the Boundary Toggle: ** Date Filter → Applicable → [~accountid:63bea783c52a63dcda8315fc] updated. please note ** Each boundary name (district or AP) will be clickable and clicking on it will drill down the table to the next level. The corresponding boundary name will appear as filter with a 'x' to remove the filter ** !Screenshot 2023-02-07 at 9.51.25 AM.png|width=107,height=45! All the columns should be sortable by clicking on the column heading (alphabetically / desc/asc) This should work as per how it works in other DIGIT dashboard tabular charts ** There will be no insights for each cell ** The pagination should be followed as per Figma ** +Please note : There is one more column ( Target achievement (% of nets) ) after Target achievement (% of Population) which is not displayed in Figma+
For the Day toggle ** Date Filter → Not Applicable → [~accountid:63bea783c52a63dcda8315fc] updated. Please note ** There will not be any drill down for any rows ** The design should match that of Figma ** The total column at the end should be highlighted in bold as shown in Figma ** There will be no insights for each cell ** The pagination should be followed as per Figma
The tabular chart should be downloadable as excel
There should be search box in the top for searching the name of the boundary and Date for the respective toggles
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Planned vs Actual Campaign Progress Line Graph
Requirement
Develop the Planned vs Actual Line graph for the HCM Dashboard
Common Actions and Validations
Users who have access to this: All levels
For National and provincial users: The graph will be for the selected/ assigned Province
For District level users: The graph will be for the selected/ assigned District
CTA: Not Applicable
The toggle for households, population and nets should change the graph according to the calculation for each
The X-axis label should be ** {{Date}}
The Y-axis label should be ** For Household graph *** {{Number of households}} ** For Population graph *** {{Population}} ** For Bed nets graph *** {{Number of bed nets}}
Upon hovering over the heading, the definitions as per the excel sheet should appear
The card should be downloadable as pdf/jpg
The card should be sharable as pdf/jpg across WhatsApp, email
Hovering over the line should show ** The Label on X and Y axes ** The value on the Y-Axis ** For eg: *** 3-June-22: 2500 Households *** 4-June-22: 35000 Population *** 5-June-22: 34000 bed nets
The trend line is required from ( today's date to the date of completion of the target) and not required from day 0. (Can be a continuation of the normal line only)
The X-intercepts of the extrapolation should show the date of completion of target
The Y intercept should show the respective target value
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Households Visited Lat/Long Map
Requirement
Develop the household visited lat long map for the HCM Dashboard
Common Actions and Validations
For National & Provincial Supervisors
The tooltip upon hovering over any boundary should show that boundary name and the total no.of households covered within that boundary. The said district should be highlighted with different stroke color as per Figma
Clicking on ‘+' '-’ should zoom in/out of the map
If the coordinates are staggered together, upon zooming in, then the coordinate of one household should be distinguishable from the other
The zoom-in level should be kept to the extent where individual households are distinguishable from one another
For District Supervisors
Tooltip upon hovering over any boundary should show that boundary name and the total no.of households covered within that boundary
Clicking on ‘+' '-’ should zoom in/out the map
If the coordinates are staggered together, upon zooming in, then the coordinate of one household should be distinguishable from the other.
The zoom-in level should be kept at the extent where individual households are distinguishable from one another
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The total number of geo coordinates should match with the total number of households in the tooltip for each boundary
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
The hover, and zoom in/out functionalities should work as mentioned above
The drill down feature upon clicking should work as mentioned"
Target Achievement Heat Map
Requirement
Develop the Target achievement heat map for the HCM dashboard
Common Actions and Validations
Users who have access to this: All users
The default view will be that at ** The province level - for national and provincial level users, with all district boundaries and district-level coverage (% ) displayed ** The district level - for district level users ( The AP level boundaries wont be able to display because of lack of shape files)
CTA: ** There will be 3 toggles on the card that lets users to switch the coverage view between Households, Population, and Bed nets ** Clicking on each toggle should change the graph accordingly based on the KPI calculation ** If the user selects a date range of which the start and end date are outside the Campaign start and end date for that boundary, then the graph should show the colour for NO DATA use case for that boundary (Grey) and NOT 0% ** The user should be able to *** zoom in/out using **** the slider ( + / -) buttons *** Move across the map by click+drag ** By default all district-wise boundaries should be shown for that province, with the coverages of each district displayed on top in % (For national and provincial level users). Since the shape files are not available, further drilling down will not be applicable for this. ** By default, the district map and the coverage % of that district should be displayed (for district level users). AP boundaries cannot be shown due to lack of shape files and also further drill down as well.
Upon hovering over any district, the insights should be displayed ( % change w.r.t the previous day as shown in the Figma)
The insights for delta = 0 should be ‘'Same as yesterday’' with no arrow
The definition should be displayed upon hover for the card title based on what is mentioned in the KPI card.
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
The hover, and zoom in/out functionalities should work as mentioned above
The drill down feature upon clicking should work as mentioned"
Bed nets not delivered Bar Chart
Requirement
Develop the Bed nets not delivered bar chart for the HCM Dashboard
Common Actions and Validations
Users who have access to this: All users
CTA: Drilldown should be applicable by clicking on each bar
For National and provincial users: The default aggregation will be at district level. ** The drill down will be as follows *** District → AP → Locality → Village
For District users: The default aggregation will be at AP level ** AP → Locality → Village
Upon hovering over the heading, the definitions as per the excel sheet should appear and the subheading should be there as per Figma
The axes labels should be there as per figma
The card should be downloadable as pdf/jpg
The card should be sharable as pdf/jpg across whatsapp, email
Hovering over each bar on the graph should display the ** Value for that bar ** The name of the boundary ** The drill down link listed as shown in the figma ** For eg: as below !Screenshot 2023-02-06 at 9.26.24 PM.png|width=163,height=115!
Upon drilling down, the filter should appear with an 'x' to remove the filter as per figma ** !Screenshot 2023-02-06 at 9.28.40 PM.png|width=159,height=50!
For each levels of drilldowns, the filter should keep on appearing and only display results applicable for that filter
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Bed nets distributed Bar Chart
Requirement
Develop the bed nets distributed bar chart for the HCM Dashboard
Common Actions and Validations
Users who have access to this: All users
CTA: Drill down should be applicable by clicking on each bar
For National and provincial users: The default aggregation will be at district level. ** The drill down will be as follows *** District → AP → Locality → Village
For District users: The default aggregation will be at AP level ** The drill down will be as follows *** AP → Locality → Village
Upon hovering over the heading, the definitions as per the excel sheet should appear
The axes labels should be there as per figma
The card should be downloadable as pdf/jpg
The card should be sharable as pdf/jpg across whatsapp, email
Hovering over each bar on the graph should display the ** Value for that bar ** The name of the boundary ** The drill down link listed as shown in the figma **
Upon drilling down, the filter should appear with an 'x' to remove the filter as per figma ** !Screenshot 2023-02-06 at 9.28.40 PM.png|width=159,height=50!
For each levels of drill downs, the filter should keep on appearing and only display results applicable for that filter
The toggle between % and Number should work properly and the bars should be calculated as per the KPI sheet calculations
The Y-axis labels should be as follows ** For # *** Bed nets distributed ** For % *** % of bed nets distributed against micro plan target
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Population Covered Bar chart
Requirement
Develop the population covered bar chart for the HCM Dashboard
Common Actions and Validations
Users who have access to this: All users
CTA: Drill down should be applicable by clicking on each bar
For National and provincial users: The default aggregation will be at district level. ** The drill down will be as follows *** District → AP → Locality → Village
For District users: The default aggregation will be at AP level ** AP → Locality → Village
Upon hovering over the heading, the definitions as per the excel sheet should appear
The axes labels should be there as per figma
The card should be downloadable as pdf/jpg
The card should be sharable as pdf/jpg across whatsapp, email
Hovering over each bar on the graph should display the ** Value for that bar ** The name of the boundary ** The drill down link listed as shown in the figma **
Upon drilling down, the filter should appear with an 'x' to remove the filter as per figma ** !Screenshot 2023-02-06 at 9.28.40 PM.png|width=159,height=50!
For each levels of drill downs, the filter should keep on appearing and only display results applicable for that filter
The toggle between % and Number should work properly and the bars should be calculated as per the KPI sheet calculations
The Y-axis labels should be as follows ** For # *** Population covered ** For % *** % of population covered against micro plan target
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Households visited bar chart
Requirement
Develop the households visited bar chart for the HCM Dashboard
Common Actions and Validations
Users who have access to this: All users
CTA: Drill down should be applicable by clicking on each bar
For National and provincial users: The default aggregation will be at district level. ** The drill down will be as follows *** District → AP → Locality → Village
For District users: The default aggregation will be at AP level ** AP → Locality → Village
Upon hovering over the heading, the definitions as per the excel sheet should appear
The axes labels should be there as per figma
The card should be downloadable as pdf/jpg
The card should be sharable as pdf/jpg across whatsapp, email
Hovering over each bar on the graph should display the ** Value for that bar ** The name of the boundary ** The drill down link listed as shown in the figma **
Upon drilling down, the filter should appear with an 'x' to remove the filter as per figma ** !Screenshot 2023-02-06 at 9.28.40 PM.png|width=159,height=50!
For each levels of drill downs, the filter should keep on appearing and only display results applicable for that filter
The toggle between % and Number should work properly and the bars should be calculated as per the KPI sheet calculations
The Y-axis labels should be as follows ** For # *** Number of households visited ** For % *** % of households visited against micro plan target
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Coverage by Province
Requirement
Develop the 'Coverage by Province' card for the HCM dashboard
Common Actions and Validations
Users who have access to this: National Level
CTA: Applicable. Clicking on the ‘View Dashboard’ button should take the user to the respective province dashboard
This card should be part of all campaign tabs (LLIN, IRS, MDA, etc..)
Upon hovering over each KPI, the definitions as per the excel sheet should appear
The card should have the menu option at top right corner through which the user can download/share the card by email/whatsapp in pdf/jpg
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet"
Population Covered Heat Map
Requirement
Develop the Population coverage heat map for the HCM dashboard
Common Actions and Validations
Users who have access to this: National Level
The default view will be that at the national level with all provincial boundaries and province-level population coverage (% ) displayed
CTA: ** The user should be able to *** zoom in/out using **** the slider ( + / -) buttons *** Move across the map by click+drag ** Clicking on on any province should display the district-wise boundaries automatically for that province, with the population coverages of each district displayed on top in % ** Upon clicking on the province, the respective filter should appear below the heading with an ‘x' button to remove the filter. Clicking on 'x’ will remove the filter and the map should go back to the initial provincial level boundary and coverage %
Upon hovering over any province, the insights should be displayed ( % change w.r.t the previous day as shown in the Figma)
Upon hovering over any district upon drill down, the insights should be displayed ( % change w.r.t the previous day as shown in the Figma)
The insights for delta = 0 should be ‘'same as yesterday’' with no arrow
The definition should be displayed upon hover for the card title based on what is mentioned in the KPI card.
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
The hover, and zoom in/out functionalities should work as mentioned above
The drill down feature upon clicking should work as mentioned"
Households Coverage Heat Map
Requirement
Develop the Households coverage heat map for the HCM dashboard
Common Actions and Validations
Users who have access to this: National Level
The default view will be that at the national level with all provincial boundaries and province-level household coverage (% ) displayed
CTA: ** The user should be able to *** zoom in/out using **** the slider ( + / -) buttons *** Move across the map by click+drag ** Clicking on on any province should display the district-wise boundaries automatically for that province, with the household coverages of each district displayed on top in %. ** Upon clicking on the province, the respective filter should appear below the heading with an ‘x' button to remove the filter. Clicking on 'x’ will remove the filter and the map should go back to the initial provincial level boundary and coverage %
Upon hovering over any province, the insights should be displayed ( % change w.r.t the previous day as shown in the Figma)
Upon hovering over any district upon drill down, the insights should be displayed ( % change w.r.t the previous day as shown in the Figma)
The insights for delta = 0 should be ‘'same as yesterday’' with no arrow
The definition should be displayed upon hover for the card title based on what is mentioned in the KPI card.
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
The hover, and zoom in/out functionalities should work as mentioned above
The drill down feature upon clicking should work as mentioned"
Checklist fill rate Bar chart
Requirement
Develop the Checklist Fill rate bar chart
Common Actions and Validations
The graph should be ordered in alphabetical order of the X-axis values
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis
Upon hovering over each KPI, the definitions as per the excel sheet should appear
In the absence of data, the respective error message should be shown
The graph should change w.r.t to the date range filter
Default filter will be TODAY
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Number Of Days To Last Inventory
Requirement
Develop the Inventory Status bar chart
Common Actions and Validations
The graph should be ordered in alphabetical order of the X-axis values
The graph should show district wise data for national and provincial supervisors dashboards by default before drill down
The graph should show AP wise data for district supervisors dashboards by default before drill down
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis ( Eg: X axis: Districts Y axis: No.of days to last inventory)
The definition as per the excel sheet should appear as sub heading beneath the chart title
In the absence of data, the respective error message should be shown
The graph should not change w.r.t date filter and should always show TODAY’s value
The graph should enable drill down to lowest boundary levels
The drill down will be: ** For National & Provincial supervisors, the default aggregation will be at district level *** District Name → District level warehouses + AP level warehouses + Locality level warehouses + village level warehouses ** For District level supervisors, the default aggregation will be at AP level *** AP Name → AP level warehouses + Locality level warehouses + village level warehouses
+Note: Eg: Under District A, if there are 5 district warehouses and 10 community warehouses, then the total number of warehouses within district A will be 15. So the bar for District A upon drill down will show 15 bars.+ +So the sum total of 'stock in hand' across all 15 warehouses should be considered.+ +The micro plan target should be the daily bednets target for province A+
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Households Coverage Ranking Bar chart
Requirement
Develop the Households Coverage Ranking bar chart
Common Actions and Validations
The graph should be ordered in descending order of magnitude from left to right
Hovering over each bar should display the data on both X and Y axis
The legends should be there indicating X and Y axis
Upon hovering over each KPI, the definitions as per the excel sheet should appear
In the absence of data, respective error message should be shown
The graph should change according to the selected date range filter
Default filter will be TODAY
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Supervision Page
"Requirement
Develop the Supervision page for the HCM Dashboard
This page will have 4 cards
National Supervisors checklist fill rate bar chart
Provincial supervisors checklist fill rate bar chart
District supervisor's checklist fill rate bar chart
Data sync rate bar chart
Common Actions and Validations
The Date filters will be Today, Cumulative, Custom
All the tabs (Overview, Reg&Del, Complaints, Inventory, Supervision) should be accessible from the tab and/or from the side panel
This page will be accessible to all levels of users (National, Provincial, and District)
For national-level users,
They will arrive at this page by clicking on the respective ' Coverage by Province' card in the National Page and then clicking on the ‘Supervision’ Tab
The default view will be at the provincial level (Aggregate of all districts within)
The default date filter will be for TODAY
For Provincial level users
They will click on the respective link ( ‘'Campaign Type - Province name’') from the landing page and and then clicking on the ‘Supervision’ Tab will arrive at this page
The default view will be at the assigned province (Aggregate of all districts within)
The default date filter will be for TODAY
For District Level users
They will click on the respective link ( ‘'Campaign Type - District name’') from the landing page and and then clicking on the ‘Supervision’ Tab will arrive at this page
The default view will be at the assigned district (Aggregate of all APs within)
The default date filter will be for TODAY
The entire page is downloadable and sharable (WhatsApp, email) as pdf/jpg
Each card should be downloadable and sharable (WhatsApp, email) as pdf/jpg
The progress bar should be available at top as per Figma
The breadcrumbs should be present to navigate
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working"
Complaints Page
Requirement
Develop the Complaints page for the HCM Dashboard
This page will have 6 cards
Complaints by Boundary bar chart
Complaints by type Pie chart
Complaints by status stacked bar chart
Complaints by Type stacked bar chart
Boundary wise share of complaints bar chart
Average complaints resolution time (Hrs) bar chart Summary report (Total Complaints)
Summary report (Open Complaints)
Common Actions and Validations
The Date filters will be Today, Cumulative, Custom
All the tabs (Overview, Reg&Del, Complaints, Inventory, Supervision) should be accessible from the tab and/or from the side panel
The drilldown will be available at the lowest level at which the users are created
This page will be accessible to all levels of users (National, Provincial, District)
For national-level users,
The default view will be at the provincial level (Aggregate of all districts within) The default date filter will be for TODAY
For Provincial level users
The default view will be at the assigned province (Aggregate of all districts within) The default date filter will be for TODAY
For District Level users
The default view will be at the assigned district (Aggregate of all AP's within)
The default date filter will be for TODAY
The entire page is downloadable and shareable (WhatsApp, email) as pdf/jpg
Each card should be downloadable and sharable (WhatsApp, email) as pdf/jpg
The progress bar should be available at top as per Figma The breadcrumbs should be present to navigate
All the bar charts should have the brush component based on the number of bars
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working"
Inventory Management Page
Requirement
To create the inventory management page for the HCM dashboard
This page will have 4 cards
Number of days to last inventory bar chart
Stock in Hand bar chart
Warehouse distribution lat/long map
Summary report
Common Actions and Validations
This page will be accessible for all levels of dashboard users by clicking on the Inventory tab or from the side panel
The entire page is downloadable and shareable (WhatsApp, email) as pdf/jpg
Each card should be downloadable and shareable (WhatsApp, email) as pdf/jpg
The ‘Today’s' Date is visible on the top header and will be the default filter for all cards unless specified otherwise in respective cards
The custom date range picker should work as per the DIGIT configuration
The breadcrumbs should be present to navigate as per Figma
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Registration and Delivery Page
Requirement
Develop the KPI cards for the registration & delivery tab for HCM Dashboard
This page will have 8 cards
Households visited bar chart
Population covered bar chart
Bed nets distributed bar chart
Bed nets not delivered bar chart
Households visited Lat/Long map
Target Achievement
Heat map Planned vs Actual campaign progression line graph
Summary report
Common Actions and Validations
This page will be accessible for all levels of dashboard users by clicking on the Registration & Delivery tab or from the side panel
The entire page is downloadable and shareable (Whatsapp, email) as pdf/jpg
Each card should be downloadable and sharable (Whatsapp, email) as pdf/jpg
The ‘Today’s' Date is visible on the top header and will be the default filter for all cards
The custom date range picker should work as per the DIGIT configuration
The breadcrumbs should be present to navigate as per Figma
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working"
Overview Page
Requirement
Develop the Overview page for the HCM Dashboard
This page will have 9 cards
Data sync KPI card
Households KPI card
Population covered KPI card
Bed nets distributed KPI card
Bed nets not delivered pie chart
Complaints pie chart
Households coverage ranking bar chart
Inventory status bar chart
Checklist fill rate bar chart
Common Actions and Validations
The Date filters will be Today, Cumulative, Custom
All the tabs (Overview, Reg&Del, Complaints, Inventory, Supervision) should be accessible from the tab and/or from the side panel
There will be no drill downs or CTAs on the first 5 charts
For Households coverage ranking bar chart, Inventory status bar chart, and Checklist fill rate bar chart the drill down should be available by clicking on each bar of the chart.
The drill down will be available at the lowest level at which the users are created
This page will be accessible to all levels of users (National, Provincial, District)
For national-level users,
They will arrive at this page by clicking on the respective ' Coverage by Province' card in the National Page
The default view will be at the provincial level (Aggregate of all districts within)
The default date filter will be for TODAY
For Provincial level users
They will click on the respective link ( ‘'Campaign Type - Province name’') from the landing page and will arrive at this page
The default view will be at the assigned province (Aggregate of all districts within)
The default date filter will be for TODAY
For District Level users
They will click on the respective link ( ‘'Campaign Type - District name’') from the landing page and will arrive at this page
The default view will be at the assigned district (Aggregate of all AP's within)
The default date filter will be for TODAY The entire page is downloadable and shareable (WhatsApp, email) as pdf/jpg
Each card should be downloadable and sharable (WhatsApp, email) as pdf/jpg
The progress bar should be available at top as per Figma The breadcrumbs should be present to navigate
The Date range filter should be applicable for all cards except ‘Inventory Status’ graph
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working"
Complaints KPI card
Requirement
Develop the KPI cards for the HCM Dashboard
Common Actions and Validations
Users who have access to this: All levels
CTA: Not Applicable
The pie chart should display according to the status of complaints captured in the complaint module of the mobile app
The pie chart should change according to the date range selected
The % of each slice should be visible on the pie chart
Upon hovering over the pie chart, the absolute numbers and name of that slice should appear
The total value of all households not delivered as absolute number should be displayed as shows in the Figma
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Data Sync KPI card
Requirement
Data Sync Rate KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
The users created will be captured for each boundary from the user management module
The users synced should consider only those users who have synced at least once and more than 1 syncs from the same user should be considered as only one
Failure to load data / not having data should show error message accordingly
No CTA on the card
Each metric within the card should behave as per below for the application of the date filter
Data Sync Rate ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Total Staff on Duty ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → Yes
Total Staff Synced ** Insights → NA ** Definition on hover → Applicable ** Date Range Filter Applicable → No
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Bed nets delivered KPI card
Requirement
Households not delivered KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
Failure to load data / not having data should show error message accordingly
No CTA on the card
Each metric within the card should behave as per below for the application of the date filter
The pie chart should display according to the reasons for non delivery captured in the mobile app
The pie chart should change according to the date range selected
The % of each slice should be visible on the pie chart
Upon hovering over the pie chart, the absolute numbers and name of that slice should appear
The total value of all households not delivered as absolute number should be displayed as shows in the Figma
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs
The total households not delivered should be the sum total of all reasons
Bed nets distributed KPI card
Requirement
Bed nets distributed KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
Failure to load data / not having data should show error message accordingly
Bed nets distributed today: ** Insights → Applicable ** Definition on hover → Applicable
Total Bed nets distributed ** Insights → Applicable ** Definition on hover → Applicable
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Population Covered KPI card
Requirement
Population covered KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
Failure to load data / not having data should show error message accordingly
Population covered today: ** Insights → Applicable ** Definition on hover → Applicable
Total population covered ** Insights → Applicable ** Definition on hover → Applicable
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
Households KPI card
Requirement
Household KPI card to be developed as per the Figma UI and calculation sheet below.
Common Actions and Validations
Failure to load data / not having data should show error message accordingly
Households visited today: ** Insights → Applicable ** Definition on hover → Applicable
Total Households visited ** Insights → Applicable ** Definition on hover → Applicable
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working
Hover states should work as stated in the ‘Actions and Validations’ section
All metrics should reflect correct data
All metrics calculations are aggregated according to the KPI sheet
Performance testing to be done
Should support localisation for multiple languages for all key-value pairs"
National Level Page
Requirement
Develop the KPI cards for the HCM Dashboard
This page will have 6 cards
Households KPI card
Population covered KPI card
Bed nets distributed KPI card
Households Coverage Heat map
Population Coverage Heat map
Coverage by province KPI card
Common Actions and Validations
This page will be accessible only for National Level Dashboard users
This will be the landing page for National Level Dashboard users
The entire page is downloadable and shareable (Whatsapp, email) as pdf/jpg Each card should be downloadable and shareable (Whatsapp, email) as pdf/jpg
The ‘Today’s' Date is visible on the top header
Different campaigns will have different tabs ( LLIN, MDA, etc.. ) and clicking on each tab name should navigate to the respective campaigns.
For Mozambique for V1.1 only LLIN tab is required All the metrics displayed will be aggregated at the national level for that particular campaign (eg: LLIN)
The breadcrumbs should be present to navigate
Acceptance Criteria
The calculation for all KPIs under each metric should be as per the KPI sheet above
The UI should be as per the Figma design
All Actions and Validations mentioned above should be working"
Dashboard Stories for development (Part -2)
Requirements:
Map input sources (from form fields) to respective indicators
Define mathematical operations to generate output indicators based on data inputs (if applicable) Eg. Calculate difference between 2 data inputs and display on the dashboard (stock received minus stock distributed to calculate the stock remaining)
Define widget to be used to visualise data Define threshold validation to against indicators (if applicable)
Data visualised on the dashboards would be in an aggregated form (source of truth being the line listed captured by the front line workers).
All indicators must be generated from the data points collected using various data collection forms during campaign planning (planning will provide targets and estimates) and execution (execution will provide actual data to view against targets and estimated derived from planning)"
Product Testing & Sign off - Dashboard
Product Testing & Sign off - Dashboard
Test Data Preparation - Dashboard
Test Data Preparation
National level view
overall left and right padding of widgets - 24 px.
Low
National level view
Space between widgets -24px
Low
National level view
Heading to be left aligned with the widgets
Low
National level view
Space between heading and the widgets - 32 px
Low
Households / pop/ bnets delivery cards
Icons to be resized to 40x40px
Medium
Urvi
Completed
Households / pop/ bnets delivery cards
Space and padding of the KPIs inside the cards to be in alignment with figma
Medium
Urvi
Completed
Households / pop/ bnets delivery cards
Font size of the KPIs to be 36pts. Colour also to be changed to secondary.
High
Urvi
Completed
Household coverage
Space between heading and subhead to be 8px
Low
Bhanu
Household coverage
The ellipses dots on the the top right corner to be aligned to the heading
Medium
Bhanu
Household coverage
Restriction of infinite horizontal and vertical scroll.
High
Bhanu
To be discussed
Household coverage
Strokes of the shape outlines to be 1pt
High
Bhanu
In progress
Household coverage
Custom alignment of the KPIs on maps to be centered to the shape
High
Bhanu
To be discussed
Household coverage
Filter chips to be in alignment with figma
Low
Bhanu
Household coverage
Right and bottom padding of the zoom notch - 24px
Low
Bhanu
Household coverage
Tooltips should be attached to the shape and not the KPI
High
Bhanu
in progress
Population coverage
All changes in household coverage are applicable here as well
Medium
Bhanu
Coverage by province
Heading top padding to be fixed
Medium
Indroneil
Needs change in generic chart component
Coverage by province
Search and ellipses to be top aligned with the heading
Medium
Indroneil
Needs change in generic chart component
Coverage by province
Search field to be resized based on figma - height 32px, outline colour to be changed
Medium
Indroneil
Needs change in generic chart component
Coverage by province
The Tete card to be resized and aligned so that outer padding is 24px
Medium
Indroneil
Completed
Coverage by province
Font size of KPIs to be consistent
High
Indroneil
Completed
View Dashboard CTA
Hover be highlighted in Orange (Primary) and not blue
Medium
Indroneil
in progress
Secondary Button
Remove radius of the button
High
The three dots (Ellipses) on widgets
To be top aligned with the heading and a padding of 24px top and bottom
Medium
Tooltip - on data sync card
Font size in the tooltip to be 14px and the placement to be consistent
High
Urvi
In Review
Setting the font size to 14 px might make it inconsistent with other tooltips as the fontsize for them is larger.
Filters in table
There should be 16px space between the chip and the label.
Medium
Filters in table
Close icon color and placement to be in line with figma
Medium
Overview
overall left and right padding of widgets - 24 px.
Low
Overview
Space between widgets -24px
Low
Overview
Heading to be left aligned with the widgets
Low
Overview
Space between heading and the widgets - 32 px
Low
Filter
The filter toggle to be closer (16px from the Date range input)
Medium
Tabs
Font size of the inactive tabs to be 16pts, weight - 400
High
bhanu
Tabs
16px space between the progress bar and the numbers
Medium
Data Sync
2nd Label of second KPI to be in a single line
High
Urvi
In Review
Achieved upto 1280px, the line will wrap if the width is below this.
Households
Icon size to be 40px
Medium
Households
Check Horizontal & Vertical alignment of KPI labels
Medium
Households
Insights - Arrow icon size to be reduced to 16x16px. Space between the insight and the icon to be 4 px
Medium
Households
The donut chart is slightly cut on the top and bottom. The container of the card has to expanded
Low
Population covered
All changes that are applicable to household card
Medium
Bednets distributed
All changes that are applicable to household card
Medium
Households not delivered
Inner card padding to be 24px
Medium
Households not delivered
Space between heading and subhead to be 8px
Low
Households not delivered
Size of the donut chart to be increased
Medium
Households not delivered
Alignment of the donut chart to be horizontal with the adjacent pie widget
Low
Households not delivered
Alignment of the donut chart should not shift due the filter/ drill down appearing
Medium
Complaints by type
All changes that are applicable to households not delivered card
Medium
Households coverage ranking
Inner padding around the card to be 24 px
Medium
Households coverage ranking
Space between the graph and the heading is 32 px
Medium
Households coverage ranking
Space between the header and the subhead to be 8 px
Medium
Households coverage ranking
Y Axis labels to have percentage (%) along with the number
High
Bhanu
InProgress
Households coverage ranking
Tooltip to be in line with figma. Remove blue border. Make the name bold
High
Urvi
In Review
Inventory status
All changes that are applicable to household coverage ranking
Medium
Households Visited
Overall inner padding to be 24 px
High
Households Visited
The ellipses(three dots) to be top aligned with the heading
Medium
Households Visited
Percentage / Number toggle height to be 28px
Low
Households Visited
The space between graph and heading to be 32px
Medium
Households Visited
Percentage to be displayed on the labels
High
Bhanu
In Progress
Households Visited
Tooltip to be in line with figma
Low
Urvi
In Review
Population covered
All changes that are applicable to Household visited card
Medium
Bednets distributed
All changes that are applicable to Household visited card
Medium
Households not delivered
All changes that are applicable to Household visited card
Medium
Target Achievement
Space between heading and subhead to be 8px
Low
Target Achievement
The ellipses dots on the the top right corner to be aligned to the heading
Medium
Target Achievement
Restriction of infinite horizontal and vertical scroll.
High
Target Achievement
Strokes of the shape outlines to be 1pt
High
bhanu
In Progress
Target Achievement
Alignment of the KPIs on maps to be centered to the shape
High
Target Achievement
Filter chips to be in alignment with figma
Low
Target Achievement
Right and bottom padding of the zoom notch - 24px
Low
Target Achievement
Tooltips should be attached to the shape and not the KPI
High
bhanu
In Progress
Target Achievement
Space between toggle and ellipses to be 16px
Low
Planned vs actual campaign progression
Target date lines are mising in the graph
High
Planned vs actual campaign progression
Tooltip to be in line with figma
Low
Urvi
Planned vs actual campaign progression
Overall inner padding to be 24 px
Medium
Planned vs actual campaign progression
The ellipses(three dots) to be top aligned with the heading
Medium
Planned vs actual campaign progression
The space between graph and heading to be 32px
Medium
Summary Report
Overall inner padding to be 24 px
Medium
Summary Report
Sort icon to be aligned to the column heading
High
Summary Report
Column headers to be in single line and the attributes to be in the second line. Make the table scrollable horizontal if needed.
High
Summary Report
Remove the outlines for all the rows. There should be only background blocks
Medium
Summary Report
The size of the day and boundary toggle to be same
Medium
Summary Report
The space between the toggle and the search bar to be 16px
Medium
Summary Report
Pagination to be in line with Figma
Medium
Complaints by boundary
Overall inner padding to be 24 px
High
Complaints by boundary
The ellipses(three dots) to be top aligned with the heading
Medium
Complaints by boundary
Percentage / Number toggle height to be 28px
Low
Complaints by boundary
The space between graph and heading to be 32px
Medium
Complaints by boundary
Percentage to be displayed on the labels
High
Bhanu
In Progress
Complaints by boundary
Tooltip to be in line with figma - have a radius
Low
Urvi
In Review
Complaints by boundary
Height of the card to be adjusted to the adjacent card
Medium
Complaints by type
The donut chart to be made larger
Medium
Complaints by type
Tooltip to be in line with figma
Low
Urvi
Complaints by status
All changes that are applicable to complaints by boundary
Medium
Complaints by type & Boundary
All changes that are applicable to complaints by boundary
Medium
Boundary wise share of complaints
All changes that are applicable to complaints by boundary
Medium
average complaint res time
All changes that are applicable to complaints by boundary
Medium
Summary Report (Open Complaints)
Overall inner padding to be 24 px
Medium
Summary Report (Open Complaints)
Sort icon to be aligned to the column heading
High
Summary Report (Open Complaints)
Column headers to be in single line and the attributes to be in the second line. Make the table scrollable horizontal if needed.
High
Summary Report (Open Complaints)
Remove the outlines for all the rows. There should be only background blocks
Medium
Summary Report (Open Complaints)
Pagination to be in line with Figma
Medium
Summary Report (Total Complaints)
All changes that are applicable to Summary (Open complaints)
Medium
Inventory status
Overall inner padding to be 24 px
High
Inventory status
The ellipses(three dots) to be top aligned with the heading
Medium
Inventory status
The space between graph and heading to be 32px
Medium
Inventory status
Percentage to be displayed on the labels
High
Inventory status
Tooltip to be in line with figma - have a radius
Low
Urvi
In Review
Stock in hand today
There should be space of 4px between available stock and req stock bars
Medium
Stock in hand today
The available stock bar should have a radius similar to req stock
Medium
Stock in hand today
The ellipses(three dots) to be top aligned with the heading
Medium
Stock in hand today
The space between graph and heading to be 32px
Medium
Stock in hand today
Percentage to be displayed on the labels
High
Stock in hand today
Tooltip to be in line with figma - have a radius
Low
Urvi
In Review
Summary report
Overall inner padding to be 24 px
Medium
Summary report
Sort icon to be aligned to the column heading
High
Summary report
Remove the outlines for all the rows. There should be only background blocks
Medium
Summary report
Pagination to be in line with Figma
Medium
Some guiding features like tooltips for the scroll and zoom component should be present
Call to be taken on labels instead of legends for graphs. Gives more clarity and a sense of Segregation.
Sort icon to be more common and functional
This document is a step-by-step promotion guide to setup/promote the Health Campaign Management (HCM) Dashboard to higher environments. The guide can be used by implementation teams and other external teams to set up the product.
1.0
10/05/2023
This version covers the HCM Dashboard promotion guide.
List of core digit services used:
The HCM Dashboard consumes the same core services that are used by HCM Platform services.
Refer to this document for the list of core services to be deployed for the HCM dashboard.
The following image of the Dashboard analytics service is required for the HCM dashboard:
Dashboard analytics service
dashboard-analytics:dashboard-v1.1.0-2ad7482dbd-32
The core dashboard analytics service with specific enhancements have been added for the HCM Dashboard.
This section will detail the promotion guide steps for the HCM Dashboard.
Tags created for the release artefacts:
Dashboard chart configurations
dashboard-v1.1.0
Dashboard analytics service
dashboard-v1.1.0
MDMS
dashboard-v1.1.0
DIGIT UI
health_v1.1.0
Refer to this document to promote the backend services and configurations.
DIGIT UI
digit-ui:health_v1.1.0-91a6f61fc1-375
DIGIT micro UI with enhancements specific for the health Dashboard.
The HCM Dashboard includes UI enhancements that are part of the image mentioned above. The stylesheet and the global config used by the UI are as follows:
Deploying the above image to the target environment will include the HCM dashboard for eligible users.
Health Dashboard
Bar charts with percentage and number toggle.
Brush component for bar charts to zoom in and out for an enhanced view.
Heat maps with zoom-in/out, toggle, and drill-downs to show coverages.
Date range selection through the calendar date picker and toggle buttons to select ‘Today’ and ‘Cumulative’ date ranges.
A new component to display the list of cards based on the chart data, and includes a collection of numeric data and a circular progress bar.
Predictive line graphs to show planned versus actual campaign progression.
Multi-campaign card layout to view campaigns of multiple types happening simultaneously.
Progress bar to show the campaign duration.
Tabular charts with drill-down, search, toggle, and sort functionalities.
Pie charts with the aggregation are shown at the centre.
Stacked bar charts.
Hover definitions and sub-headings to show more details about a specific card.
Download all charts and pages in PDF and JPG formats.
Share all charts and pages in PDF and JPG formats across WhatsApp and email.
Drill-downs for bar charts.
Supervision module.
About, FAQ, and Calculation pages.
Heat/Lat-long maps re-centre button.
Bar chart with target line on the Registration & Delivery page.
Go
General
Not showing the brush component in the downloads/sharing of charts? Not Done. Enhancement.
The dashboard view at 100% of screen size is not enough to show 1 graph without scrolling and also the tabular chart names (Day toggle) are not aligned at 100%. At 80% the dashboard view looks good. Possible to make the 80% view as default? Not Done. Enhancement.
At 100%
At 80%
Page is getting refreshed automatically in between and landing on overview page Not Done. Bug.
Changing the hand symbol to mouse arrow pointer wherever there is only hover and no clickHand hover. Not Done. Enhancement. Can be picked.
Edit profile page
a. Localisation missing in the fields Not Done Bug
b. After clicking on ‘Edit Profile’ the page is stuck after clicking on Save. Not Done Bug.
Windows issue for share – to add Enhancement
Comment: In windows system, the share option is like this.
Localisation label missing Not Done Bug
Swathi Comment: Abhishek Suresh Can you explain this?
Neelakantan S can we do this at UI level.
Rename breadcrumb of National dashboard as per Figma Not Done Bug
Swathi Comment: Type of Bug: UI . Need to fix.
The title of the Page is not as per Figma - ‘’LLIN Campaign National Dashboard’’. Also the title should be configurable. Ie. it should be the same as the link which the user clicked on the landing page. Not Done. Bug. So the title should be → ‘’Name of the link on the card layout that the user selects” + Campaign National Dashboard. It should be “LLIN Campaign National Dashboard”
Swathi Comment: Type of Bug: UI . Need to fix.
For the households, population covered, Bed nets distributed Not Done Bug
a. Font size of number is not matching as per figma
b. Text is not as per figma (bold, size)
c. Insights (= no change from yesterday) → There should be no ‘=’ sign before
d. Missing → (Cumulative) under Total households/population/bednets
Swathi Comment: Type of Bug: UI. Need to fix it.
For household coverage & population coverage heat maps, even if there is no data for a boundary, the boundary name needs to be shown upon hovering In Progress Not Mentioned
Swathi Comment: Type of bug: Functional and UI. This was not mentioned Earlier.
For households coverage and population coverage heat maps, the insights should be shown on boundary and not KPI In Progress Bug
Swathi Comment: Type of bug Functionality &UI. Need to fix this.
There should be a restriction on the heat map to limit the extent of scrolling outside the map area. Currently the user can scroll too far outside the map area into the white space and it is difficult to get back on the map area by scrolling back in Not Done Bug
Swathi Comment: This has already brought points to Neelakantan S point of view . But he said it’s difficult to fix.
On the heat maps, if there is no change wr.t previous day, then only the message ‘’same as yesterday’’ should be displayed and not 0% . This should be applicable for all insights where delta = 0 In Progress
Swathi Comment: Type of Bug UI. Need to fix it.
The different stroke color upon hover over boundary is not being shown after drill down for lower level boundaries Invalid.
The font of the numbers on the heat maps needs to match with figma. Currently its not readable. Not Done
Swathi Comment: Type of Bug: UI. Need to discuss with Neelakantan S. Can we change it to Bold?
In the coverage by province - Not Done
a. Localisation missing on the no results
b. The kebab menu is not of the same shade as per figma
c. The search bar should show ‘Search province’ and not ‘Search’ as mentioned in Figma.
Swathi Comment: Type of Bug: UI. Need to discuss with Neelakantan S. Need to fix it.
When downloading/ sharing the coverage by province card, the text is getting misaligned - Not Done Enhancement
Please change the subheading to “Click on ‘View Dashboard ’ next to each province name to view the province level dashboard ” Not Done Enhancement Can be picked
Swathi Comment: This is done as per Figma Abhishek Suresh. So making it as an Enhancement
‘Total households visited today’- Not Done Bug
a. Rename Total Households Visited → Total Households Visited Cumulative
Swathi Comment: This is done as per Figma Abhishek Suresh . So making it as Enhancement. Type of bug: UI. Need to fix it.
Today Households Visited should be present all time. Even we don’t have any data. It need to show 0.. Need to fix it
The breadcrumb is not correct as per Figma. Not Done. Bug.
Swathi Comments: Type of bug UI: Need to fix it.
The title LLIN Campaign Dashboard should be configurable based on the selection from the Landing Page Not Done Enhancement
Swathi Comments:
Abhishek Suresh Can you Please explain this.
Neelakantan S The title of the overview page should be user selection from the card layout.
The name of the selected province should appear in the page title along with LLIN Not Done Bug
Eg: Tete, Zambezia
The title should be configurable. i.e. it should be the same as the link which the user clicked on the landing page. So the title should be → ‘’Name of the link on the card layout that the user selects” + Campaign Dashboard + (Name of the province that the user selects). For eg: LLIN Campaign Dashboard (Tete)
Swathi Comment: Type of bug: UI. Need to fix it. The name of the province & district should also been shown as per Figma.
In the Custom Date range selection, Not Done. Bug.
Not able to select the first 2 days of the Start date of the campaign (30th,31st). The number of days in the campaign as per progress bar is 7 days. The cumulative selection shows the campaign start date as 30th, which means the campaign end date should be 5th April. But in the calendar, April 6th is also highlighted.
Swathi Comment: Not able to select the first 2 days of the Start date of the campaign(30th,31st)-->
Abhishek Suresh For this need you need to change the month in the date picker.
The no.of days in the campaign as per progress bar is 7 days. The cumulative selection shows the campaign start date as 30th, which means the campaign end date should be 5th April. But in the calendar, April 6th is also highlighted.--->
For this we need to discuss with Neelakantan S.
When downloading the entire page as PDF, the last portion and the graphs in that is not being displayed.
Also when sharing the page as pdf/image across email/Whatsapp same issue. Not Done. Enhancement.
Swathi Comments: Type of bug:Functionality. Need to fix it. This is happening for the PDF download at 100% screen.
The labels are not matching as per Figma Not Done For households, Population, Bed nets distributed KPI cards
a. Cumulative missing in the brackets
b. For selected date range missing in brackets
Swathi Comments: Type of bug:UI. We had used the KPI sheet labels.
So, Abhishek Suresh can you please confirm which we need to follow. Earlier it was told that I need to follow the KPI sheet.
7. The insights are missing for Total households visited till Today for Households, Population, Bed nets distributed KPI cards Not Done Bug
Swathi Comment: Type of bug: Functionality. Need to fix it.
8. Tool tips are getting cropped
a. Total bed nets distributed till today
b. Bed nets coverage till today
Swathi Comment: Type of bug UI Need to fix it.And this depends on screen resolution.
9. Rename tooltip to → “ The total number of households where no delivery has taken place for the selected date range” Enhancement Not Done Can be picked
10. Rename tooltip to → “ Total number of complaints by status for the selected date range” Enhancement Not Done Can be picked
11. Households coverage ranking chart Enhancement Not Done Can be picked
a. Show % next to the numbers on the Y-axis (eg: 20%)
b. Rename legend from Households Percentage → Households coverage. Same should be applied on the labels that appear when you hover on each bar
12. On the brush component , the name of the boundary (Angonia) is coming up Bug Not Done (Same across all graphs)
Swathi Comment: Type of bug: UI. Need to remove the names on the brush component. Need to fix it
13. By default - the custom date range is selected for the page. It should be ‘Today’ Bug. Not Done.
Swathi Comment: Need to fix it.
14. Sub heading missing as per Figma. Make the sub heading same as the tool tip - Bug Not Done
Swathi Comment: Type of bug UI Need to fix it.
15. While downloading/sharing the graphs, the sub headings are getting distorted - Bug. Not Done (Please check this for all graphs with sub headings). Same for complaints by type pie chart).
Sub headings missing for following charts Not Done Bug
a. For Number of days chart.. The sub heading should be → “No.of days the inventory can last as of today”.
b. For stock in hand chart - subheading to be same as figma
Swathi Comment: Type of bug: UI. Need to fix.
Default date for the page is not set for Today. Instead it is for Custom. Not Done. Bug.
Swathi Comment: Need to fix it.
Rename the tooltip District → District Name
Swathi:Comment: This was not mentioned anywhere Abhishek Suresh in the KPI sheet also. So I considered it an Enhancement. Need to fix it
This is not done yet. The summary report has drill-down Invalid Part of V1.1
Swathi:Comment: This was done as part of the V1.1. Not in V1.0.
Summary Report Not Done Bug
a. Localisation missing for district names
b. The default is not set to a→z alphabetically for district names
Swathi Comment: Type of bug: UI.
a. Localisation missing for district names yeah this is not done still. Till Start fixing this.
b. Need to fix it
Nets returned missing in the summary report Not Done Enhancement
Swathi:Comment: The Dev team has mentioned that they are not considering a few columns even if it is present In KPI sheet. So, I need to clarify whether it needs to be considered or not.
The page share and download buttons are not working Not Done Bug
Swathi Comment: Type of Bug: Functionality. Need to fix it. No Options are shown to download or Share.
The page download and share buttons are not working Not Done Bug
Swathi Comment: Type of Bug: Functionality. Need to fix it. No Options are shown to download or Share.
Households visited bar chart
a. On Y axis, add % next to the numbers –eg: 20%, 10% etc for % toggle Not Done Enhancement
b. For %: Edit legend to → % of Households visited against target Not Done Enhancement
c. For #, edit legend to → Number of households visited Not Done Enhancement
d. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold Bug Not Done
3. Population covered graph
a. Add % next to the numbers on the Y-axis for % toggle Not Done Enhancement
b. For % toggle: Rename legend to → % of Population covered against target Not Done Enhancement
c. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold Bug Not Done
4. Bed Nets distributed graph
a. Add % next to the numbers on the Y-axis for % toggle Not Done Enhancement
b. For % toggle: Rename legend to → % of bednets distributed against target Not Done Enhancement
c. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold Enhancement Not Done
5. Households not delivered
a. The tooltip is getting cropped Bug Not Done
Swathi Comment: This happens when we use 100% screen. It is working correctly on 80% of the screen. Type of bug:UI. Need to fix it.
b. Rename tooltip to → “ The total number of households where no delivery has taken place for the selected date range” Enhancement Not Done
c. The legend and upon hovering over the bar should only read ‘’Households not delivered’’.. Currently it has ..by district attached. Remove this Bug Not Done
Swathi Comment: Type of UI.
d. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold Bug Not Done
6. Target achievement map
a. The font on the map (% and the name) are not readable. Its different to that of Figma. Please align this as of Figma Bug Not Done
Swathi Comment: Type of bug:UI. Need to fix it.
b. The boundary thickness is much higher. Pls reduce this Bug Not Done
Swathi Comment: Type of bug:UI. Need to fix it.
c. Spell-check : Achievement → Achievement Bug Not Done
Swathi Comment: Type of bug:UI. Need to fix it.
d. he tooltip upon hovering should be done over the boundary and not the text Bug Not Done
Swathi Comment: Type of bug:Functional & UI. Need to fix it.
e. The subtext is not as per Figma → Target achievement across boundaries. (Click on the boundary to drill-down) Bug Not Done
Swathi Comment: Type of bug:UI. Need to fix it.
f. Spacing between the toggle and kebab menu is too low. Please maintain it as per figma Not Done Bug
Swathi Comment: Type of bug: UI. Need to fix it.
g. There should be a restriction on the heat map to limit the extent of scrolling outside the map area. Currently the user can scroll too far outside the map area into the white space and it is difficult to get back on the map area by scrolling back in Not Done Bug.
Swathi Comment:This has already brought points to Neelakantan S point of view . But he said it’s difficult to fix. This has already brought point to Neelakantan S. But he said it’s difficult to fix.
h. For the insights case ‘Same as yesterday’ , 0% should not be shown. Only ‘Same as yesterday’ is required. Not Done Enhancement
i. The sub heading is getting distorted while downloading/sharing the map
7. Planned versus Actual Campaign Progression
a. Toggle and charts missing for Population, Nets Invalid Part of V1.1
b. ‘’Number of Households” legend missing on the Y-axis Not Done Bug
Swathi Comment: b. Type of bug: UI. Need to fix this
c. Rename legends Not Done Bug
- Target → Planned
- Distributions → Actual
- Prediction_Distributions → Prediction (Localisation Missing)
Swathi Comment: Type of bug: UI & Functionality. Need to fix this.
d. The X-intercept for Planned and Actual plots is not shown. The X-intercept should read as per how its in Figma (Planned target date & Expected Target Date) Not Done. Bug.
Swathi Comment: Neelakantan S will answer this .
e. The title of the graph should not have (Households) in brackets Invalid
Swathi Comment: This is kept because present we had only done only for Household.
8. Summary Report
a. Localisation missing for boundary names Not Done Bug
Swathi Comment: Type of Bug UI. Need to fix.
b. Rename HH → Households
Swathi Comment: This is same as KPI sheet
Rename the tooltip District → District Name Not Done Enhancement
c. The tool tip for Target Achievement % Population is not correct in both Boundary and Day toggle. Please change it to as per KPI sheet Not Done Bug
Swathi Comment: Type of Bug UI. Need to fix.
d. Rename tooltip for Rejected, Relocated, Closed for both Boundary & Day toggle to → “ The total number of households where no delivery has taken place for the selected date range” Enhancement Not Done.
Complaints by Boundary
a. The name of boundary is appearing on the brush component Bug Not Done
Swathi Comment: Abhishek Suresh can you plz explain this.
b. Not enough spacing between the sub heading and the graph Bug Not Done
Swathi Comment: Type of Bug UI. Need to fix.
c. Sub heading getting distorted while downloading/sharing the graph Bug In Progress
d. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold. Ref to Figma Bug Not Done
Swathi Comment: Type of Bug UI. Need to fix.
2. Complaints by Type
a. The pie chart is not covering the whole of the space and there is too much white space. Pls refer to Figma Bug Not Done
Swathi Comments: Neelakantan S needs to confirm this.
b. The tooltip definition for the title is missing. Ref to KPI sheet Bug Not Done
Swathi Comment: Type of Bug UI. Need to fix.
3. Complaints by Status
a. Remove ‘by District’ from all legends and tooltips on hover Bug Not Done
b. Boundary name appearing on brush component Bug Not Done
c. The spacing between title and the graph is low. Ref to Figma Bug Not Done
d. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold. Ref to Figma Bug Not Done
Swathi Comment: From a to d. Type of Bug UI. Need to fix.
4. Complaints by Type & Boundary
a. Boundary name appearing on brush component Bug Not Done
b. The spacing between title and the graph is low. Ref to Figma Bug Not Done
c. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold. Ref to Figma Bug Not Done
d. The tooltip definition for the title is missing. Ref to KPI sheet Bug Not Done
Swathi Comment: From a to d. Type of Bug UI. Need to fix.
5. Boundary wise share of complaints
a. Boundary name appearing on brush component Bug Not Done
b. The spacing between title and the graph is low. Ref to Figma Bug Not Done
c. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold. Ref to Figma Bug Not Done
d. The tooltip definition for the title is missing. Ref to KPI sheet Bug Not Done
e. Add % to the numbers on the Y-axis (50%, 60% etc..) Enhancement Not Done
f. Rename the legend from ‘’Complaints by District’’ → ‘’% of Total Complaints by District’’
Swathi Comment: From a to d. Type of Bug UI. Need to fix.
a. Boundary name appearing on brush component Bug Not Done
b. The spacing between title and the graph is low. Ref to Figma Bug Not Done
c. The tool tip definition is wrong. Bug Not Done
d. The font of the text upon hovering over graph- No distinction btw boundary name and status: Make the boundary name in bold. Ref to Figma Bug Not Done
e. Title getting distorted while sharing/downloading Bug Not Done
Swathi Comment: From a to d. Type of Bug UI. Need to fix.
7. Summary Report (Total Complaints)
a. Localisations missing for boundary names Bug Not Done
Swathi Comment:Type of Bug UI. Need to fix.
b. The Dates column sorting is not proper Bug Not Done
Swathi Comment:Type of Bug UI. Need to fix.
Swathi Comment: Type of Bug Functional . Need to fix.
8. Summary Report (Open Complaints)
a. Change the calculation to include the case = Enhancement Not Done
- Open since < 6 hrs
- Open since >= 6 hrs & <12 hrs
- Open since >=12 hrs & < 24 hrs
- Open since >= 24 hrs & <48 hrs
- Open since > = 48 hrs
- Localisations missing for boundary names Bug Not Done
9. Share/Download buttons for the page not working
Background
Design
This document describes the need and scope of a dashboard for executing digital health campaigns, explaining the product’s features, specifications, purpose, and functionalities. It also provides a descriptive view of the dashboard portal along with the specification of each element, and the analytics data involved in it.
When the country-level/province-level/district-level/administrative- level of the user login to the HCM admin account as assigned, they can navigate to the following sections:
Dashboard
User management
Complaints
We will also discuss and focus on the ‘dashboard’ service that has been provided to all the admin-level users as per their roles and hierarchy in the system
When the user logins to the admin page, he/she will be able to see a dashboard card, which will list all the campaigns that are currently running and that they have been assigned to.
This is the national-level dashboard view for the country head, for a specific campaign. This dashboard displays the overall data of a campaign running in various provinces with a drill-down behaviour so that the supervisor can also view the data for a specific province/district when required.
The country-level dashboard is viewed by the country head only, The process of navigating to the country-level dashboard is shown below:
This is the campaign-level dashboard for the province. Here, the user can view the overall performance and the status of the campaign which is running at the province/state level. A user can also drill-down to the boundary levels.
Country Head: After navigating from the national dashboard and selecting a province/state, the country head can view this page, with aggregated data from all districts.
Province-Level (state-level) Head: There can be different province-level heads who may be managing different provinces in the country. They will arrive at this page after clicking on the respective campaign type on the landing page. After logging into the admin panel, the province-head will only see the campaigns listed in the dashboard box at the landing page, which they have been assigned. When they select the campaign by its name, they directly land on the overview page of the campaign dashboard, that is, they will not see the national-level dashboard page.
District Head: A province has multiple districts, therefore, there are multiple district heads who might be assigned and managing a single district. The district head will have access to the dashboard data for the district that they have been assigned to, and view the aggregated data just for their district.
For the selected campaign, the “Registration & Delivery” section majorly focuses on the data collected by the field-level workers. It shows the status of the campaign at a ground level, in each district and administrative post of the province.
District head: A province has multiple districts, and hence, there are multiple district heads who might be assigned to and managing a single district. The district head will have access to the dashboard data for the specific district that they have been assigned to, and will view the data just for their district.
Country head/National-level user: After navigating from the national dashboard and selecting a province, the country head can view the province-level dashboard with all the collective data of different district and administrative blocks.
Province-level head : There can be different province level heads who may be managing different provinces in the country. Therefore, the province-level manager will have accesst to the dashboard of the province which he/she has been assigned to and managing.
For the selected campaign running for a province, the ‘Complaints’ section shows the data about the complaints that have been generated by the FLWs, supervisors, and warehouse managers at any point of time in the process of an ongoing campaign.
Country head: After navigating from the national dashboard and selecting a province, the country head can view the province-level dashboard with all the collective data of different district and administrative blocks.
Province-level head: There can be different province-level heads who may be managing different provinces in the country. Therefore, the province-level manager will have access to the dashboard of the province which he/she has been assigned to and managing.
District head: A province has multiple districts, and therefore, there are multiple district heads who might be assigned to and managing a single province. The district head will have access to the dashboard data for the specific district that they have been assigned to, and will view the data just for their district.
For the selected campaign, the ‘Inventory’ section majorly focuses on the data of how the inventory movement is managed within the warehouses, or is being managed within the internal team.
Country head/National-level user: After navigating from the national dashboard and selecting a province, the country head can view the province-level dashboard for the selected campaign with all the collective data of different districts and administrative blocks.
Province-level head: There can be different province-level heads who may be managing different provinces in the country. Therefore, the province level manager will have access to the dashboard of the province which he/she has been assigned to and is managing.
District head: A province has multiple districts, and therefore, there are multiple district heads who might be assigned and managing a single district. The district head will have access to the dashboard data for the specific district that they have been assigned to, and will view the data just for his/her district.
This is the campaign-level dashboard for a province/district. The user can view the overall analytics of the activities that the supervisor performs. This supervision dashboard does not have any of the drill-down approaches available for any of the graphs.
Country head: After navigating from the national dashboard and selecting a campaign for the province, the country head can view the province-level dashboard with all the collective data of different district and administrative blocks.
Province-level head: There can be different province-level heads who may be managing different provinces in the country. Therefore, the province-level manager will have an excess of the dashboard of the province to which he/she has been assigned to, and managing. After logging into the admin panel, at the landing page, the province head will only see the campaigns listed in the dashboard box which they have been assigned to. When they select the campaign by its name, they directly land on the overview page of the campaign dashboard, that is, they will not see the national-level dashboard page.
District head: A province has multiple districts, and therefore, there are multiple district heads who might be assigned and managing a single district. The district head will have access to the dashboard data for the district that they have been assigned, and will view the data just for their district.
- Able to fill the checklist & sync, but the data is not reflecting in Kibana.
6. Average Complaint Resolution time (hrs)
User type
Role description
Navigation
Description
Country
The country-level user is the super admin who can view the performance and manage the campaign running.
Login < Dashboard < Select the Campaign < View National Level dashboard data
The country-level admin user will be able to see the national-level dashboard, which will display the data of all the campaigns running countrywide with respect to all the provinces and districts. They can drill down the dashboard to view the details of the campaigns in each province.
Province
The province-level admin user can view the performance of the ongoing campaign for their province.
Login < Dashboard < Select the Campaign < View Campaign dashboard data
The province-level admin user views the campaign dashboard, which has the data aggregated across all the districts where the campaign is going on.
District Officer
There can be various districts under a province. Therefore, a district-level officer has the responsibility of managing the campaign running for their allotted district.
Login < Dashboard < Select the Campaign < View Campaign dashboard data for the allotted district
The district-level admin officer views the campaign dashboard. This campaign-level dashboard has the data of the specific district that they have been allotted.
Supervisor
Role-based admins are the users who manage the campaigns running in a specific administrative block to which they have been assigned to.
Do not have access to the dashboard, They only use the mobile application that has been provided to them.
As the supervisor warehouse manager does not have dashboard access, they only use the mobile application that has been provided to them where the application has the option to view the report of all the FLW's working under them and monitor their performance.
Locality
(FLW)
Field-level workers are the ground-level workers who distribute the campaign inventory to the citizens, thereby fulfilling the campaign's requirements and making the campaign successful.
Do not have access to the dashboard. They only used the mobile application that has been provided to them.
The field-level workers have a registration and delivery mobile application that have been provided to them, where in the ‘report’ section they can view the analytics of their performance only.
Indicator/ visualisation
Drill-down
Description
Actions a user can take
Homepage
After logging in, the admin lands on the home screen where he/she can view the cards for:
Dashboard
User management
Complaints
In the ‘Dashboard’ card, the user can view the list of all the different campaigns that are running with respect to the users’ account. They can also access the about, FAQ, and calculation pages related to the dashboard from here
Can view the HCM landing page.
View the dashboard card with the list of campaigns in which the user is involved.
Click on the “Campaign Name” to view the specific campaign-related data in the dashboard.
User type
Role description
Country head
The country head can only view the national level–dashboard which will show the status of the campaign running in various provinces of the country. The country head has a provision to drilldown the campaign performance for specific provinces and districts.
Super admin LOGIN
Country head logs in to his/her account
The user Lands on the HCM “HOMEPAGE”.
After successful logging in, the user lands on the homepage where they can view a card named ‘Dashboard’. This card lists all the campaigns that are running in the country.
SELECT THE CAMPAIGN from the list of ongoing campaigns available.
From the list of the campaigns, the country head selects the campaign name for which he/she wants to view the dashboard.
Indicator/ visualisation
Drill-down
Description
Actions a user can take
Alternative
Household: Households visited today
-
This indicator shows the number of households that were visited by all the frontline workers (FLWs) across all the provinces for today for the selected campaign type.
View only
This also shows the additional percententage (%) increase or decrease in the households that were visited from the previous day.
Household: Total households visited
-
This indicator shows the number of the households that were visited by all the FLWs across all the provinces till today since the start of the campaign for the selected campaign type.
View only
-
Population covered:
Population covered today
This indicator shows the total population covered by the FLWs across all the provinces for today for the selected campaign type.
View only
This also shows the additional percentage (%) increase or decrease in the households visited from the previous day.
Population covered:
Total population covered
-
This indicator shows the total population covered by all (FLWs across all the provinces till today since the start of the campaign for the selected campaign type.
View only
-
Bed nets distributed:
Bed nets distributed today
-
This indicator shows the total bed nets distributed by all FLWs across all the provinces for today for the selected campaign type.
View only
This also shows the additional percentage (%) increase or decrease in the households visited from the previous day.
Bed nets distributed
Total bed nets distributed
-
This indicator shows the total bed nets distributed by all the FLWs across all the provinces till today since the start of the campaign for the selected campaign type.
View only
-
Household coverage (%)
The country-level head (user) can click on any of the provinces of the country, to drilldown to a province-level map and view the household coverage percentage at the district-level for that selected province.
The user will be able to view the percentage of the households that have been covered till the latest date as per the micro-plan targets set in each province.
View the percentage of households covered in every province.
Hover on any province to view the province name and percentage.
Hover on the title to view the definition.
Click on any province to view the district-level-wise household coverage data.
Close the district filter to go back to the province-level view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
If the country level head hovers over a province, they can see the percentage change in the coverage for that province/district with respect to the previous day as tooltip.
Population coverage (percentage)
The country-level head can click on any of the provinces of the country to drilldown to the province-level map and view the population coverage percentage at the district-level for that selected province.
The country head will be able to view the percentage of population that has been covered till the latest date as per the micro-plan targets set in each province.
View the percentage of population covered in every province.
Hover on any province to view the province name and percentage.
Hover on the title to view the definition.
Click on any province to view the district-level-wise population coverage data.
Close the district filter to go back to the province-level view.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
If the country level head hovers over a province, they can see the percentage change in the coverage for that province/district with respect to the previous day as tooltip.
Coverage by province
This view lists all the provinces where the campaign took place or is currently going on.It highlights a few of the data points about the campaign.The user can click on the “View dashboard” button, which will redirect him/her to the specific province-level dashboard of the campaign.
In the tabular form, the list of the provinces where the campaign has performed or is ongoing, will list the data points of “Total households visited today”/“Total Household visited cumulative”/ “Household Coverage”/ “Population Coverage”.
It also has a “View Dashboard” button which navigates the user to a specific province-level dashboard.
View the list of provinces where the campaign was performed or is going on.
Click on “View dashboard”.
Search for a specific province name.
-
User Type
Role Description
Navigation
Description
Country head
The country-level user is the super admin who can view the performance and manage all the campaigns running at all the levels.
Login < select a campaign dashboard < select a province < view dashboard < Overview
After viewing the list of provinces where the selected campaign is running in the national dashboard, the country head clicks on “view dashboard” to view the province-level dashboard for the campaign.
Province head
The province-level admin user can view the performance of the campaign ongoing for his province.
There can be multiple provinces allotted to the province head admin users, under the country head.
Login < select a campaign from dashboard card < Overview
The province-level head will only be able to view the data of provinces that they have been assigned to.
District officer
The district-level user can view the performance of the campaign ongoing for their assigned district.
Login < select a campaign from dashboard card < Overview
The district officer will only be able to view the aggregated data of the district they have been assigned to.
Indicator/ visualisation
Drill-down?
Description
Actions user can take
Alternative
Data Sync
Total users created
-
This will show the total number of users (FLWs), who are assigned for duty within that province/district for the selected date range.
View the data sync rate for the assigned/selected province/district.
Hover on the indicators to see the definitions.
Hover on the title to view the definition.
Data Sync
Total users synced at least once
-
This is the count of the total number of FLWs who have synced the data at least once in a day.
(Multiple syncs from the same device not considered in a day).
View the data sync rate for the assigned/selected province/district.
Hover on the indicators to see the definitions
Hover on the title to view the definition.
At every start of the day, this value is “0”.
As the field counts the unique syncs from different users, multiple syncs from the same device is not taken into consideration.
Data Sync
Sync rate
-
This is the percentage of the total FLWs who have synced their device at least once for the selected date range.
View the data sync rate for the assigned/selected province/district.
Hover on the indicators to see the definitions.
Hover on the title to view the definition.
Households
Household visited
-
This field shows the count of households visited for the particular day or a date range as selected.
View the households visited.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Users can change the date range filter from the top, as required, based on which the household visited data gets changed.
Households
Household targeted
-
This field shows the count of household targets to be completed for a particular day or a date range as selected.
View the households targeted.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
National-level role: Micro plan data for the household targeted at a province level.
Province-level role: Micro-plan data for the household targeted at a province level.
District-level role: Micro-plan data for the household targeted at a district level
Households
Total household visited
-
This field shows the total count of the households that have been visited in the province/ district till yet (From the starting day of the campaign).
View the cumulative households visited.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
National-level role: Count of the households visited for the selected province.
Province-level role: Count of the households visited for the assigned province.
District-level role: Count of the households visited for this assigned district.
This also shows the additional percentage increase or decrease in the households being visited from the previous day.
Households Households coverage
-
This is the percentage of household coverage achieved against the micro-plan target set from the campaign start date (Cumulative data).
View the household coverage.
Hover on the title to view the definition..
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level role: Household target at the province level.
Province-level role: Household target at the province level.
District-level role: Household target set at the district level.
Population covered
Population covered
-
This field shows the total population that has been covered for the selected day or the date range.
View the population covered.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
Users can change the date range filter from the top, as required, based on which the population covered data gets changed.
Population covered
Total population covered
-
This field shows the tota population that has been covered from the start of the campaign.
View the cumulative population covered.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
National-level role: At the selected province level.
Province-level role: At the assigned province level.
District-level role: At the respective distric assigned.
This also shows the additional percentage increase or decrease in the populatio that have been covered compared to the previous day.
Population covered
Population targeted
-
This field shows the total population that needs to be covered for a particular day or a selected date range as per the micro plan set.
View the population targeted.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level role: Population targeted as per the microplan set for the province.
Province-level role: Population targeted as per the microplan set for the assigned province.
District-level role: Population to be targeted as per the microplan set for the district.
This also shows the additional percentage increase or decrease in the population that have been covered compared to the previous day.
Population covered
Population covered against micro plan
-
This is the percentage of citizens’ coverage achieved against the microplan target set from the campaign start date (Cumulative data).
View the population coverage.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
National-level role: population coverage achieved as per the microplan set at the province level.
Province-level role: Population coverage achieved as per the microplan set at the province level.
District-level role: Population coverage achieved as per the microplan set at the district level.
Bed nets distributed
Bed nets distributed
-
This field shows the total number of bed nets that have been delivered for a particular day (today) or a selected date range.
View the bed nets distributed.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
Bed nets distributed
Total nets distributed
-
This field shows the total count of bed nets that have been delivered to households from the starting date of the campaign.
View the cumulative bed nets distributed.
Hover on the title to view the definition.
Download the card as PDF/JPG
Share the card in email/Whatsapp as PDF/JPG.
National-level role: Bed nets distributed for the selected province.
Province-level role: Bed nets distributed for the assigned province.
District-level role: Bed nets distributed for the assigned district.
This also shows the additional information of percentage increase or decrease for the bed nets that were distributed to the households from the previous day.
Bed nets distributed
Bed nets targeted
-
This field shows the total number of bed nets that have been targeted for distribution as per the micro-plan set for the day or the selected date range.
View the bed nets targeted.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level role: The bed nets targeted for distribution as per the micro-plan for the province.
Province-level role: The bed nets targeted for distribution as per the micro-plan for the province.
District-level role: The bed nets targeted for distribution as per the micro-plan for the district.
Bed nets distributed
Bed Nets Coverage
-
This field shows the total percentage of bed nets distribution coverage achieved against the micro-plan target.
View the bed nets distribution coverage.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level role: Bed nets distribution coverage achieved against the micro-plan target for the selected province
Province-level role: Bed nets distribution coverage achieved against micro-plan target for the assigned province
District-level role: Bed nets distribution coverage achieved against the micro-plan targets for the assigned district.
This also shows the additional information of percentage increase or decrease for the bed nets that were distributed to the households against the micro-plan compared to the previous day.
Bed Nets not delivered
-
This shows the total number of households where the intervention was not delivered due to any particular reasons (not limited) such as:
Rejected by the beneficiary.
House was closed.
Beneficiary relocated.
View the households where delivery did not happen.
Drill-down chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
At the centre of the pie-chart, the count of total households where the intervention has not been delivered.
The data points/ categorisation of the reason for the intervention not delivered are as per the options configuration done at the MDMS for the application.
Complaints
-
The complaint card shows the data visualisation in the form of a pie-chart of the statuses of all complaints registered for the selected date range or a day. These statuses are: :
Open
Resolved
Rejected
View the complaints generated.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
At the centre of the pie-chart, it displays the sum of the total number of complaints that have been created.
Household coverage ranking
-
The user will be able to view a bar-graph for the data of the total percentage of households covered as per the micro-plan at the assigned user boundary level where the interventions have been delivered.
The district/ administrative post bars in the graph are arranged in a descending order (highest - lowest) so that the user can compare the campaign coverage across the different boundaries.
View the households’ coverage ranking.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level role: All the districts within the selected province will be displayed in the bar chart.
Province-level role: All the districts within the selected province will be displayed in the bar chart.
District-level role: All the administrative posts within the selected districts will be displayed in the bar chart.
The user can hover over the bar of any district, which will show the percentage value of the households that have been covered till yet.
Number Of Days To Last Inventory
National/ Country head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
Province Head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
District head: This type of user can drill down the chart from: Administrative Post < Locality < Village
The user can view the bar graph, which will indicate to the user that in each boundary, how many days can the existing stock across all warehouses within those boundaries be sufficient for the campaign
The bar graph shows the ‘boundary’ data at the x-axis as assigned and the “Number of days” in the y-axis.
There can be multiple warehouses in each boundary, so the collective data of the stock is compared to the current daily consumption and then the prediction is depicted in the graph.
View the number of days to the last inventory bar chart.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover on the bar column in the graph, which will show data in the tooltip for the count of how many days the inventory can last for the selected boundary bar.
Overall Checklists Completion Rate
-
This is a bar graph chart that shows the percentage of supervisors who have filled all assigned checklists for the selected date range or a day.
View the checklists completion ratein the bar chart.
Drill-down the chart.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
National-level role: This shows the district data on the x-axis.
Province-level role: This shows the district data on the x-axis.
District-level role: This shows the Administrative post data in the x-axis.
User Type
Role Description
Navigation
Description
Country head/ Nation-level user
The country-level admin user is the super admin who can view the performance of all the campaigns running at all the levels.
Login < select a campaign type from dashboard card < coverage by province < select a province < Overview page < navigate to Registration & Delivery page
After viewing the “Coverage by province” section in the national dashboard, the user clicks on “view dashboard” to view the province-level dashboard for the campaign.
Province head
The province-level admin user can view the performance of the campaign ongoing for their assigned province only.
There can be multiple province-level admin users allotted for different provinces under the country head.
Login < select a campaign from dashboard card < Overview page < navigate to Registration & Delivery page
At the province level, the head will only be able to view the dashboard of the assigned provinces that they have been assigned to.
District Head
There are multiple district heads under every province who are managing their assigned administrative post area.
Login < Select the campaign from the dashboard card < Overview page < navigate to the Registration & Delivery page
As the district-level head, they will be only viewing the data in the dashboard for their specific assigned district.
Indicator/ Visualisation
Drill-down
Description
Actions user can take
Alternative
Households visited
National/ country head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
Province Head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
District Head: This type of user can drill down the chart, from: Administrative Post < Locality < Village
Note: The drill-down will take place for the respective boundary when the user clicks on the boundary data bar on the graph.
The user will be able to view a bar-graph for the data of the total number of households where the interventions have been covered (visited and delivered plus visited but not delivered) by the FLW as per the selected day or a date range.
Users can toggle the graph data between the count (actual number) and percentage against the micro-plan targets.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover over the column of any district/ administrative post/locality/ village, which will show the data value.
Population covered
National/ Country head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
Province Head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
District Head: This type of user can drill down the chart, from: Administrative Post < Locality < Village
Note: The drill-down will take place for the respective boundary when the user clicks on the boundary data bar on the graph.
Here the user will be able to view the bar graph for the data count of the total population that has been covered (visited and delivered plus visited but not delivered) for the intervention delivery by the FLWs for the selected day or the date range.
The user can toggle and view the population covered data in two different formats:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover over the column of any district/ administrative post/locality/ village, which will show the data value.
Bed nets distributed
National/ Country head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
Province Head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
District Head: This type of user can drill down the chart, from: Administrative Post < Locality < Village
Note: The drill-down will take place for the respective boundary when the user clicks on the boundary data bar on the graph.
In this bar graph, the user will be able to view the data of the total bed nets that have been delivered by the FLWs to the households for the selected day or the date range.
The user can toggle and view the data of Bed Nets Distributed to the households in two different format:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover over the column of any district/ administrative post/locality/ village, which will show the data value.
Bed nets not delivered
National/ Country head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
Province Head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
District Head: This type of user can drill down the chart, from: Administrative Post < Locality < Village
Note: The drill-down will take place for the respective boundary when the user clicks on the boundary data bar on the graph.
Here the user will be able to view the bar graph, for the data count of “Number of households” where the intervention (such as bed nets) delivery have not taken place due to a particular reason as per the selected day or a date range.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover over the column of any district/ administrative post/locality/ village, which will show the data value.
Target achievement
Households
National/ Country head: The user will be able to view the country-level map, which can be drilled-down to the province-level and then further to the district-level.
Province Head: The user will be able to view the assigned province-level map, and can further drill down to the district-level map.
District head: The user will be able to view the district map assigned only.
The current geo map is in the form of a heat map, which shows the “percent of targets that have been achieved” by the FLW’s as per the micro-plan set for the boundary data.
The Geo map has a RED-AMBER-GREEN color code which helps in depicting the performance of the targets achieved.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
For the “Target achieved” map, the user can toggle between the:
Household
Population
Bed nets
Target achievement
Population
National/ Country head: The user will be able to view the country-level map, which can be drilled-down to the province-level and then further to the district level.
Province head: The user will be able to view the assigned province-level map, and can further drill-down to the district-level map.
District head: The user will be able to view the district map assigned only.
The current geo map is in the form of a heat map which shows the “percent of population that has been covered” (i.e. Intervention delivered) as per the set micro-plan target.
The geo map has a RED-AMBER-GREEN color code which helps in depicting the performance of the target achieved.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
For the “Target achieved” map, the user can toggle between the:
Household
Population
Bed nets
Target achievement
Bednets
National/ country head: The user will be able to view the country-level map, which can be drilled-down to the province level and then further to the district level.
Province head: The user will be able to view the assigned province-level map, and can further drill-down to the district-level map.
District head: The user will be able to view the district map assigned only.
The current geo map is in the form of a heat map which shows the “percent of Bednets” that has been distributed to the households as per the micro-plan for the selected boundary data from the start date of the campaign.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
For the “Target achieved” map, the user can toggle between the:
Household
Population
Bed nets
Planned vs actual campaign progress
This is a line chart comparison of the campaign’s daily plan target versus the actual daily progress.
Household: This will be a line chart that shows the campaign progression for households delivery planned against the actual.
Population: This will be a line chart that shows the campaign progression for population covered planned against the actual.
Bed nets: This will be a line chart that shows the campaign progression for bed nets distributed that is planned against the actual.
The X-axis shows that ‘date’ from when the campaign started till the campaign end date, whereas the Y-axis shows the coverage count.
The campaigns target date marked in the chart makes it easy for the user to predict by which date the campaign will meet its target.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
For the planned versus actual progress of the campaign, the user can also navigate to:
Household
Population
Bed nets
Summary report
Boundary
This tabular chart shows the data according to the boundary.
Clicking on each boundary will drill-down to the next level of the boundary, and so forth.
This is the complete report of the campaign which will be drilled-down from the district to the village-level.
National/ Country head: Will see the report data starting from the district and further can drill-down to the village-level
Province Level: Will see the report data starting from the district and further can drill down to the village-level.
District: Will see the report data starting from the administrative post and further can drill down to the locality and then to the village-level.
The boundary tabular Report have following KPI data:
Target achieved (% of household): Percentage of household coverage achieved against the micro-plan targets.
Target achieved (% of population): Percentage of population coverage achieved against the micro-plan targets.
Target achieved (% of bednets distributed): Percentage of bed nets distribution coverage achieved against the micro-plan targets.
Households visited: The total number of households visited for the selected date range.
Population covered: This is the total population covered as per the selected date range.
Bednet distributed: This is the total number of bed nets distributed as per the selected date range.
Not delivered (Closed): This is the total number of households where the FLW went to deliver the bed nets but the household was ‘closed’. Therefore, the intervention was not delivered.
Not delivered (Refused): This is the total number of households where the FLW went to deliver the bed nets, but the household ‘refused’ the intervention. Therefore, the intervention was not delivered.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
For the summary report of the campaign, the user can view the data as per:
District (boundaries)
Date (Day)
Summary report
Day
-
This is a tabular chart that shows the summary data for each day of the campaign.
The date tabular report have following KPI data:
Target achieved (% of household): Percentage of household coverage achieved against the micro-plan targets for a particular date.
Target achieved (% of Population): Percentage of population coverage achieved against the micro-plan targets for a particular date.
Target achieved (% of bednets distributed): Percentage of bed nets distribution coverage achieved against the micro-plan targets for a particular date.
Households visited: The total number of households visited for the selected date range for a particular date.
Population covered: This is the total population covered as per the selected date range for a particular date.
Bed net distributed: This is the total number of bed nets distributed as per the selected date range for a particular date.
Not delivered (Closed): This is the total number of households where the FLW went to deliver the bed nets but the household was ‘closed’. Therefore, the intervention was not delivered for a particular date.
Not delivered (Refused): This is the total number of households where the FLW went to deliver the bed nets but the household ‘Refused’. The intervention, therefore the intervention, was not delivered for a particular date.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search day.
For the summary report of the campaign, the user can view the data as per:
District (boundaries)
Date (Day)
User Type
Role Description
Navigation
Description
Country head
The country-level user is the super admin who can view the performance and manage all the campaigns running at all the levels.
Login < select a campaign type from dashboard card < coverage by province in National Dashboard < select a province < “view dashboard” < Overview page< navigate to Complaints
After viewing the coverage by province in the national dashboard, the user clicks on “view dashboard” to view the province-level dashboard for the campaign.
Province head
The province-level admin user can view the performance of the campaign ongoing for his/her assigned province.
There can be multiple province-level admin users allotted for different provinces under the country head.
Login < select a campaign from dashboard card < Overview page < navigate to Complaints
The province-level head will only be able to view the dashboard of the provinces that they have been assigned for.
District Head
There are multiple district heads under every province who are managing their assigned district area in the province.
Login < Select the campaign from the dashboard card < Overview page < navigate to complaints
The district-level head will only be able to view the data in the dashboard for the district specifically assigned to him/her.
Indicator/ Visualisation
Drill-down
Description
Actions user can take
Alternative
Complaints By Boundary
National/ Country head: Will see the bar graph with the district and can further drill down Administrative Post < Locality < Village
Province Level: Will see the bar graph with the district and can further drill down Administrative Post < Locality < Village.
District: Will see the bar graph with the administrative post and can further drill down to Locality < Village
This is a bar Chart that shows the total complaint data for the selected day or the date range. On the X-axis, the user can view the boundary data, and on the Y-axis, he/she can view the count of complaints.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can also hover over any of the bar columns which will show the specific data in the tool-tip format.
Complaints By Type
-
This is a pie chart view which shows the percentage of the different category types of complaints that have been created by the warehouse manager, supervisor, and the FLW.
All the users will see the complaint data as per their allotted boundary-level.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
This category type of complaint is already added in the system. Therefore, when the supervisor or FLW wants to launch a complaint, they need to select the complaint type.
Complaints by status
National/ Country head: Will see the bar graph with the district and can further drill down to the Administrative Post < Locality < Village
Province-level: Will see the bar graph with the district and can further drill down to the Administrative Post < Locality < Village.
District: Will see the bar graph with the administrative post and can further drill down to the Locality < Village
This is a stacked bar chart that shows the split data of complaints by their status across different boundaries for the selected date or date range.
The status of the complaints are:
Resolved
Open
Dropped
The user can toggle and view the data of complaints by their status in two different formats:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Users can hover at any of the stacks of the bar to view the complaint status data for any of the required boundaries.
Complaint By Type & Boundary
National/ Country head: Will see the bar graph with the district and can further drill down to the Administrative Post < Locality < Village
Province-level: Will see the bar graph with the district and can further drill down Administrative Post < Locality < Village.
District: Will see the bar graph with the Administrative Post and can further drill down to the Locality < Village
This is a stacked bar chart that shows the split data of complaints by their type across different boundaries for the selected date or date range.
The user can toggle and view the data of complaints by their type in 2 different formats:
Percentage
Count
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Users can hover at any of the stacks of the bar to view the complaint type data for any of the required boundaries.
Boundary-wise share of complaints
National/ Country head: Will see the bar graph with the district and can further drill down Administrative Post < Locality < Village
Province-level: Will see the bar graph with the district and can further drill down to the Administrative Post < Locality < Village
District: Will see the bar graph with the administrative post and can further drill down to the Locality < Village
This is a bar chart which shows the total complaints for each sub-boundary as a percentage of the total complaints generated within the assigned/selected provicne/district.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
Users can hover at any of the bars of the bar chart to view the percentage for the complaints for that boundary in the tool-tip message format.
Average complaint resolution time (Hrs)
National / Country head: Will see the bar graph with the district and can further drill down to the Administrative Post < Locality < Village
Province Level: Will see the bar graph with the district and can further drill down Administrative Post < Locality < Village.
District: Will see the bar graph with the administrative post and can further drill down to the Locality < Village
The bar graph shows the information: In each boundary, what is the average time required for the resolution of all the complaints generated for a day or a date range selected.
In the graph, the X-axis shows the boundary data, whereas the Y-axis shows the number of hours.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can also hover over any of the bar columns in the bar chart which will show the selected boundary data (hrs) in the tool-tip format.
Summary report (Total complaints)
Boundary
Country head: Will see the report with the district and can further drill down to the Administrative Post < Locality < Village
Province-level: Will see the report with the district and can further drill down to the Administrative Post < Locality < Village
District: Will see the report with the administrative post and can further drill down to the Locality < Village
This is the complete statistical report of the complaints that have been generated by the supervisor, warehouse manager and the FLWs in the campaign across the specific boundaries as per the selected day or date range.
The fields that the summary report focus on:
Boundary name: This is the district/AP/ locality/village name as per the user role assigned.
Register: This is the count of the total complaints that have been created in the system for the respective boundary irrespective of their status for the day or the selected date range.
Resolved: This is the count of the total complaints that have the status marked as ‘resolved’ in the system for the respective boundary for the day or the selected date range.
Dropped by Supervisor: This is the count of the total complaints that have the status marked as ‘rejected’ in the system for the respective boundary for the day or the date range.
Open: This is the count of the total complaints that have the status marked as open in the system for the respective boundary for the day or the date range (All the complaints which are not ‘Resolved’ or ‘Rejected’ are treated as ‘Open’).
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
For the summary report of the total complaints, the user can toggle the report between:
Boundaries
Day
Summary teport (Total complaints)
Day
-
This is the complete statistical report of the complaints that have been launched by the supervisor, warehouse manager, and the FLWs in the campaign, at each day/date.
The fields that the summary report focus on:
Date: This is the field where the user will see the dates.
Register: This is the count of the total complaints that have been created in the system on a specific date irrespective of their status and boundary.
Resolved: This is the count of the total complaints that have the status marked as ‘resolved’ in the system till the specific date, irrespective of the boundaries.
Dropped by supervisor: This is the count of the total complaints that have the status marked as ‘rejected’ in the system till the specific date, irrespective of the boundaries.
Open: This is the count of the total complaints that have status marked as ‘open’ in the system till the specific date, irrespective of the boundary
(All the complaints which are not ‘Resolved’ or ‘Rejected’ are treated as ‘Open’).
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search day.
For the summary report of the total complaints, the user can toggle the report between:
Boundaries
Day
The toggle for the day has the data report with the dates. Therefore, the date range filter does not have any effect on the data.
Summary Report (Open complaints)
Country head: Will see the report with the district boundary and can further drill down to the Administrative Post < Locality < Village
Province-level: Will see the report with the district boundary and can further drill down to the Administrative Post < Locality < Village
District: Will see the report with the administrative post and can further drill down to the Locality < Village
This is the summary report which only focuses on the data of the ‘OPEN’ complaints in the campaign.
The summary report of the open complaints can be viewed as per the boundary level.
The fields that the summary report for the open complaints focus on:
Boundary name: This lists the name of the boundaries as per the user assigned role, and users can also see the status of ‘open complaints’.
Open since <6 hrs: This is the count of complaints which are open from the last 6 hours, and yet pending for any further action till today.
Open since >=6 hrs & <12 hrs: These are the counts of complaints which are open for more than or equal to 6 hours but less than 12 hours, and yet pending for any further action.
Open since >=12 hrs & <24 hrs: These are the counts of complaints which are open for more than or equal to 12 hours but less than 24 hours, and yet pending for any further action.
Open since >=24 hrs & <48 hrs: These are the counts of complaints which are open for more than or equal to 24 hours but less than 48 hours, and yet pending for any further action.
Open since >=48 hrs: These are the counts of complaints which are open from more than or equal to 48 hours, and yet pending for any further action.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
Open complaints are the total number of complaints with any status apart from ‘Resolved’ or ‘Rejected’.
User type
Role description
Navigation
Description
Country head/ Nation-level
The country-level admin user is the super admin who can view the performance of all the campaigns running at all the levels.
Login < select a campaign type from dashboard card < coverage by province < select a province < view dashboard < Overview < navigate to inventory management
After viewing the “Coverage by province” section in the national dashboard, the user clicks on “view dashboard” to view the province-level dashboard for the campaign.
Province head
The province-level admin user can view the performance of the campaign ongoing for his/her assigned province only. There can be multiple province-level admin users allotted for different provinces under the country head.
Login < select a campaign from dashboard card < Overview < navigate to inventory management
The province level head will only be able to view the dashboard of the assigned provinces that they have been assigned to.
District head
There are multiple district heads under every province who are managing their assigned administrative post area.
Login < Select the campaign from the dashboard card < Overview < navigate to inventory management
The district-level head will only view the data in the dashboard for their specific assigned administrative post.
Indicator / Visualisation
Drill-down?
Description
Actions user can take
Alternative
Number of days to last inventory
National/ Country head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
Province head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
District gead: This type of user can drill down the chart, from: Administrative Post < Locality < Village
Here the user can view the bar graph, which will indicate to the user that in each boundary, how many days can the existing stock across all warehouses within those boundaries will be sufficient for the campaign
The bar graph shows the ‘boundary’ data at the x-axis as assigned and the “number of days” in the y-axis.
There can be multiple warehouses in each boundary, so the collective data of the stock is compared to the current daily consumption and then the prediction is depicted in the graph.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover on the bar column in the graph, which will show a data in tooltip for the count of how many days the inventory can last for the selected boundary bar.
Stock in-hand
National/ Country head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
Province head: This type of user can drill down the chart, from: District < Administrative Post < Locality < Village
District head: This type of user can drill down the chart, from: Administrative Post < Locality < Village
The user is able to view the side-by-side bar graph which indicate the user, about the current “availability of stock”, as of today (i.e. what is the stock in hand) at the boundary and compare it against what is the “required stock” to complete the campaign as per the micro-plan set for the boundary.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover on the bar column in the graph which will show a data in tool-tip for the count of stock (Available/ Required) for the selected boundary bar.
Summary report
This tabular chart shows the data according to the boundary.
There will be no drill-downs for this sumamry report.
National/ Country head: Will see the report data starting from the district and can drill-down to the Administrative post and then to the locality and the village-level.
Province-level: Will see the report data starting from the district and can drill down to the administrative post, then to the locality and the village-level.
District: Will see the report data starting from the administrative post and then to locality and finally the village-level.
The report for the inventory section have the following boundary KPI values as:
Boundary name: This will indicate the boundary data to the user as per their role assigned.
Nets to receive as per micro-plan: This shows the total number of bed nets, including all the warehouses in the boundary, that should have been received as per the bed nets micro-plan set, for the selected date or date range.
Nets received: This shows the total number of actual bed nets that the warehouses in the boundary have received for the selected date or date range.
Nets distributed: This is the count of the bed nets that has been sent out/ distributed to the households, for the boundary for the selected date range.
Nets returned: This is the total count of bed nets that have been returned via all the warehouses within the boundary for the selected date or date range.
Nets in stock: This is the total number of bed nets that are available in the boundary with all the warehouses as of today.
Days to last: This is the total number of days the bed net stock across all the warehouses that can last as of today for the boundary.
Hover on the title to view the definition.
Drill-down the charts.
Close the filter to go back to the previous view.
Download the card as Excel.
Sort columns.
Search boundary.
-
User type
Role description
Navigation
Description
Country head
The country-level user is the super admin who can view the performance and manage all the campaigns running at all the levels.
Login < select a campaign dashboard < select a province < view dashboard < Overview < navigate to supervision page
After viewing the list of provinces where the selected campaign is running in the national dashboard, the country head clicks on “view dashboard” to view the province-level dashboard for the campaign.
Province head
The province-level admin user can view the performance of the campaign ongoing for his/her province.
There can be multiple provinces allotted to the province head admin users, under the country head.
Login < select a campaign from dashboard card < overview page < navigate to supervision page
The province-level head will only be able to view the data of provinces that he/she has been assigned to.
District officer
The district-level user can view the performance of the campaign ongoing for his/her assigned district only.
Login < select a campaign from dashboard card < overview page < navigate to supervision page
The district officer can only view the data of the districts in the province that he/she has been assigned to.
Indicator/ Visualisation
Drill-down
Description
Actions user can take
Alternative
National supervisors checklists completion rate
-
National-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by national-level supervisors as per the date or date range selected for the selected province.
Provincial-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by national-level supervisors as per the date or date range selected for the assigned province.
District-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by nationa- level supervisors as per the date or date range selected for the assigned distict.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover over the bar of the bar graph, and view the percentage completion rate for the checklist bar that is selected.
Provincial supervisors checklists completion rate
-
National-level users:
Here the user will be able to view the bar chart that shows the percentage completion of the different checklists by provincial-level supervisors as per the date or date range selected for the selected province.
Provincial-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by provincial-level supervisors as per the date or date range selected for the assigned province.
District-level users:
Here the user will be able to view the bar chart that shows the percentage completion of the different checklists by provincial-level supervisors as per the date or date range selected for the assigned distict.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover over the bar of the bar graph, and view the percentage completion rate for the checklist bar that is selected.
District supervisors checklists completion rate
-
National-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by district-level supervisors as per the date or date range selected for the selected province.
Provincial-level users:
Here the user will be able to view the bar chart that shows the percentage completion of the different checklists by district-level supervisors as per the date or date range selected for the assigned province.
District-level users:
The user will be able to view the bar chart that shows the percentage completion of the different checklists by district-level supervisors as per the date or date range selected for the assigned distict.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
The user can hover over the bar of the bar graph, and view the percentage completion rate for the checklist bar that is selected.
Data sync
There will be no drill-down for this chart and the users will see the data for the boundary they have been assigned to or selected.
Here the user will be able to view the bar chart that shows the percentage of total workers among all the users created within each boundary who have synced their device at least once, for the selected date range.
Hover on the title to view the definition.
Download the card as PDF/JPG.
Share the card in email/Whatsapp as PDF/JPG.
