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
|
| |
| |
| |
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 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 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"
|
| |
| 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 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
|
| |
| 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"
|
| |
| 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"
|
| |
| 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"
|
| |
| 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 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"
|
| |
| 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"
|
| |
| "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
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"
|
| |
| 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 Warehouse distribution lat/long map
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 Heat map Planned vs Actual campaign progression line graph
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"
|
| |
| Requirement Develop the Overview page for the HCM Dashboard This page will have 9 cards Population covered KPI card Bed nets distributed KPI card Bed nets not delivered 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"
|
| |
| Requirement Develop the KPI cards for the HCM Dashboard
Common Actions and Validations Users who have access to this: All levels 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
|
| |
| 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 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 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"
|
| |
| 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"
|
| |
| Requirement Develop the KPI cards for the HCM Dashboard This page will have 6 cards 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 | |
