...
| # | 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 | |
| 4 | 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 | ||
| 5 | 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 | |
| 6 | 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 | ||
| 7 | 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 | |
| 8 | 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 | |
| 9 | 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 | ||
| 10 | 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? | |
| 11 | 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 | |
| 12 | 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 |
...
Out of scope for this feature OR potentially saving for future development