Landing page for:
View SOH of receiver site
View Requisitions from receiver site
Set amounts to allocate / issue
...
List out the user stories under the activity. Put the "next up" under the Out of Scope section.
Step 1 - View Critical Element
This set of stories captures the data that the "supplier" needs to view on the screen as First Step when taking re-supply decisions, regardless of Requisition or Allocation supply model
| # | 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 | 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 | 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). |
Step 2
The set of user stories below captures what happens next in preparing an order once the above critical elements data is available to Supplier to make his/her decision
| # | Title | User Story | Label | Importance | Notes | JIRA Ticket |
|---|---|---|---|---|---|---|
| 1 | Batch view SOH | Supplier can batch view SOH of receiver sites for allocation (for settings where both supplier and receiver nodes use OpenLMIS) | Allocation + Del SC Allocation + PU SC | MVP | Mary Jo Kochendorfer (Deactivated), do you recall the conversation around this? I'm now unsure of what we meant by this piece. | |
| 2 | Capture SOH | Supplier captures SOH of receiver site on OpenLMIS (for settings where only supplier has OpenLMIS and receiver is using paper systems) | Allocation + Del SC Allocation + PU SC | MVP | Assumption is that HFs have provided SOH data to DIVO via paper, SMS, phone call, or in-person prior to the re-supply process kicks-off and the DIVO uses this information to input SOH data per product per site into OpenLMIS | |
| 3 | Basic view requisitions | Supplier views a list of all the requisition orders As an intermediate vaccine warehouse manager, I want a screen where I can view all my pending requisitions and select one to view and convert to issue so that I can react to requisitions sent to me Acceptance Criteria: From: VIMS | Requisition + Del SC Requisition + PU SC | MVP | Assumption is that DIVO has already submitted requisition requests which have been approved so Supplier is viewing the approved order request | |
| Capture requisitions | Supplier (DIVO) captures the requisitions amounts in OpenLMIS, as requested by a HF via a paper requisition form (in settings where only supplier node has OpenLMIS) | Requisition + Del SC Requisition + PU SC | MVP | |||
| Grouping requisitions | System groups/batches for multiple requistions | Requisition + Del SC Requisition + PU SC | Next Up votes: 5 | Mary Jo Kochendorfer (Deactivated), do you have more details on this one? I will also look back at the user stories I have for reference after I finish these tables up | ||
| Prioritize requisitions | Provides ability to re-order requisitions in terms of priorities (assigned by rules) As an intermediate vaccine warehouse manager, I want facilities that I supply to only be able to have one pending requisition at any given time so that I can prioritize those facilities that have been waiting longest for their requisitions to be filled Acceptance Criteria: From: VIMS | Requisition + Del SC Requisition + PU SC | Next | |||
| Reject approved requisitions | Reject an entire requisition order (though approved) Edge case | Requisition + Del SC Requisition + PU SC | Next | Need to find out more about when this is likely to happen; also, what is the next set of actions that this option provides – once rejection happens, does the receiver get notification to re-submit? etc | ||
| Managing exceptions | System should be able to manage exception cases (deviations from rules, ad-hoc events) etc | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up Vote: 2 | This was a new sticky note placed on the board without any discussions on Day 3; so vague and broad in scope that we'd require a lot of work to define some boundaries around managing exceptions | ||
| Supplier sets allocation amounts | Supplier sets allocation amounts instead of just going by what system says s/he should allocate) | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | MVP | |||
| FEFO and supplier SOH based allocation amounts | System recommends allocation amounts based on FEFO and amount of antigen that is available in supplier''s CCE | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up Votes: 13 | I reckon this should actually be two stories (one for FEFO and one for RIVO's own available stock) - correct? | ||
| Top-up to max. policy amounts | System recommends top-up amount to max (if such policy exists for this level) | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up Votes: 6 | Is there a story in the requisition workflow that does this for the node doing the requisitioning? In VIMS, it is the requesting node that has the system automatically calculate the routine top-up for that level before node hits submit | ||
| Bundling | System groups antigens to their associated dry stock (diluents) | Allocation + Del SC Allocation + PU SC Req + Del SC Req + PU SC | Next Up Votes: 4 | |||
Assumptions
- insert
Diagrams
Dependencies
insert
Open Questions
Below is a list of questions to be addressed as a result of the vaccine workshop:
| Question | Outcome | |
|---|---|---|
Out of Scope
Out of scope for this feature OR potentially saving for future development.
Archive Content
Scenario A (RIVO as supplier, DIVO as receiver; both use OpenLMIS)
| SC type (ordered by priority) | Preparing Re-Supply Order | ||
|---|---|---|---|
Allocation (and delivery to receiver site) Assumption: DIVO has updated SOH in OpenLMIS | View Critical Elements | View SOH of receiver site | Ability to set amounts to allocate |
| Reference Step 1 table above for what made MVP and got addtl votes | Batch view/allocate | RIVO sets amounts to allocates instead of going by just what system says s/he should | |
System recommends based on FEFO and amount of antigen available in RIVO's stock **Received 9 votes up | |||
| System recommends top-up amount to max. (if min max policy exists for that country) | |||
Grouping antigens to their associated dry stock (syringes, diluents) etc (bundling) **Received 4 votes up | |||
Requisition (and delivery to receiver) Assumption: DIVO has already submitted requisition request and it has been approve so now Supplier is viewing an "order request" | View Critical Elements | View Requisitions | Ability to set amounts to issue/allocate |
| Reference Step 1 table above for what made MVP and got addtl votes | Basic view (list of requisition orders | Same set of workflow stories as ones identified above for allocation | |
Grouping/ Batch for multiple requisitions **Received 5 votes up | |||
| Prioritize reqs | |||
| Reject already approved requisitions (Edge case) | |||
Managing exception cases **Received 2 votes up | |||
We did not have time to discuss workflows that are needed to support pick-up based systems but we believe the needs would be mostly similar to the ones identified here.
Scenario B (DIVO as supplier, HF as receiver; DIVO uses OpenLMIS, HF uses paper-based systems)
| SC type (ordered by priority) | Preparing Re-Supply Order | ||
|---|---|---|---|
Allocation (and pick-up by HF) Assumption: HFs have provided SOH data to DIVO (via paper, SMS, phone call, in-person etc); asynchronous | View Critical Elements | View SOH of receiver site | Set order fill quantities |
| Reference Step 1 table above for what made MVP and got addtl votes | Capture SOH of reciever site on OpenLMIS | DIVO sets amounts | |
System recommends based on FEFO and amount of antigen available in DIVO's stock **Received 9 votes up | |||
System recommends top-up amount to max. (if min max policy exists for that country) **Received 6 votes up | |||
Requisition (and pick-up by HF) Assumption: HFs are submitting paper requisitions to DIVO at pick-up; HF don't requisition if CCE is broken; real-time | View Critical Elements | Requisition info-capture | Set order issue quantities |
| Reference Step 1 table above for what made MVP and got addtl votes | Capture SOH and requisition amount into OPenLMIS from paper-form given by HF | Same set of workflow stories as ones identified above in this table for allocation | |
Allocation (and delivery to HF) Assumption: HFs have provided SOH data to DIVO (via paper, SMS, phone call, in-person etc) ** Entire workflow Did not make MVP cut by JOsh but received 11 votes in support | View Critical Elements | View SOH of receiver site | View load amounts |
| Reference Step 1 table above for what made MVP and got addtl votes | Same set of workflow stories as ones identified above in this table for allocation pick-up | For each HF for set time period across the delivery zones, based on critical elements data | |
| Along with above, also view CCE status of HF | |||
| Along with above two items, also view whether HF is open during planned visit time/date | |||
Requisition (and delivery to HF) Assumption: HFs are submitting paper requisitions to DIVO before delivery; HF don't requisition if CCE is broken ** Entire workflow did not make MVP cut by Josh; also, small group thought this was least seen at country level but Amy changed mind next day and provided 6 countries that do this at last mile (Cameroon, Uganda, Kenya, Lesotho, Ethiopia, TZ); workflow did not receive any specific votes on Day 3 | View Critical Elements | Requisition info-capture | Set order issue quantities |
| Reference Step 1 table above for what made MVP and got addtl votes | Same set of workflow stories as ones identified above in this table for requisition pick-up | Same set of workflow stories as ones identified above in this table for requisition pick-up | |
Dependencies
insert
Open Questions
Below is a list of questions to be addressed as a result of the vaccine workshop:
...
Out of Scope
...