...
| # | Title | User Story | Label | Importance | Notes | JIRA Ticket | |
|---|---|---|---|---|---|---|---|
| 1 | View forecasted need | Supplier views forecasted amount for the receiver site, by EPI product, and for the re-supply time period scheduled in the system Source for 'Forecasted Amount' – Multiple Options below; aslo cross-ref Forecasting and Estimation Domain i) Uploaded onto OpenLMIS via an upload file With this option, an admin uploads a file containing forecasted amounts, per facility, by product and time period. So the work to estimate is done outside OpenLMIS/not OpenLMIS responsibility. OpenLMIS only pulls info from this upload file and displays to user. Display should show forecasted amounts per product, by facility, for the chosen time period. ii) OpenLMIS calculates forecasted amount and displays it (WHO calculator) | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | MVP | Calculation of Forecasted Amount is done outside OpenLMIS – national EPI logistician consults microplans and central annual census-based forecasting to arrive at catchment population needs estimates per product for the year. This then in uploaded to OpenLMIS by system admin.|||
| 2 | View SOH | Supplier views SOH of the receiver site Options: 1) If receiver site has OpenLMIS, then the "view" will show their most recent SOH update for a product and time stamp for when that update was done 2) If receiver site does not have OpenLMIS, then the supplier has to first (on a separate screen) update SOH per product and the "view page" would display this after it's been saved/synced. | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | MVP | Assumptions: If the receiver node has OpenLMIS, they have updated their SOH If the receiver node does not have OpenLMIS, the supplier has some way of accessing SOH outside the system and manually entering it into OpenLMIS VS note: what about viewing own (i.e. supplier) SOH as a critical step in decision-making? | ||
| 3 | View CCE status | Supplier views CCE functionality status of the receiver site; if CCE is broken or functioning erratically, then Supplier takes action (outside of OpenLMIS) and then decides if re-supply should happen and how much (in case re-supply is to stock a cold box only versus a full CCE, etc). As an intermediate warehouse manager, I want to know the CCE status of the facilities to which I am preparing fulfillment of vaccines so that in the event of non-functional or erratic functioning of CCE, I can follow-up to see if I should even be preparing this fulfillment From: SELV | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | MVP Down vote: 1 (Ryan McWhorter) | |||
| 4 | View total CCE capacity | Supplier views total CCE capacity at supplier site | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | MVP | |||
| 5 | View pipeline | Supplier is able to see what stock is coming into her/his own CCE so that a determination can be made whether rationing of re-supply to lower nodes is necessary or not | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up votes: 6 | |||
| 6 | View net CCE capacity | Supplier is able to view the net CCE capacity at receiver site, based on their SOH as well as how many CCE is working properly | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up votes: 3 | |||
| 7 | View previous consumption | Applies only to requisition based SCs If a requisition asks for more or less than what is in the plan/forecasted for that receiving site, then supplier views previous consumption history to see if they point to more or less being consumed. | Req + Del SC Req + PU SC | Next | Lot of work to be done here in terms of scope of story. How far back does consumption go? And when does supplier view? When the requisition ask is less than or more than by a certain % or even if it's 1 dosage more or less than forecasted? | ||
| 8 | View session plans | Supplier is able to view the session plans for the receiving site | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up Vote: 4 | Big understanding gap in terms of what is needed and why so many votes in favour. | ||
| 9 | View utilization | Supplier is able to view historical vaccine utilization (i.e actual doses count administered of each product – program data) to inform re-supply decisions for the future | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up Vote: 5 | Need to determine why this is more important or better data point to rely on for re-supply decision-making instead of using consumption data reported via SM domain (i.e. all issues out of CCE regardless of given to people or wasted). |
...
Out of scope for this feature OR potentially saving for future development