Re-Supply Domain Parent Page
Thsis page summarizes all the discussions had regarding this domain.
Contents
To Do
Domain Overview
Definitions, so we are all on the same page:
- Pull SC = Requisitions SC = lower level sends requisitions orders to upper level and that's the foundation on what the amount of stock to give that level is built on. Req. Orders can be multiple time periods depending on local practice (biweekly, monthly, quarterly, as needed, emergency, etc).
- Push SC - Allocations SC = upper level determines how much stock to give to lower level based on review of stock usage and supply data from the lower levels. Again, they might do this over multiple time periods depending on local practice.
- Pick-up based transport model: lower level picks-up the stock from upper level
- Delivery-based transport model: upper levels delivers the stock to the lower level
- You can have 5 types of supply chains as a result in a country and among st countries:
- Pull/Requisition based that is pick-up transport model
- Pull/Requisition based that is delivery transport model
- Push/Allocation based that is pick-up transport model
- Push/Allocation based that is delivery transport model
- Ad-hoc, in that what's done on the ground is opposite of what country or region or district says it does on paper/in theory
- One tricky part is figuring out which domain supports the workflow needed to stock up campaigns aka outreach aka mobile brigades. Given how long SM domain already is, suggest putting it in here during the workshop discussion.
This domain is focused on supporting the workflows needed to execute the order pick-ups and the order deliveries. CONSIDER DOMAIN NAME CHANGE to DELIVERY/PICK-UP DOMAIN?
Overall Domain Features
This section covers the features and stories relevant to both delivery and pick-up models
Card # | Prepare Order based on Requisitions |
---|---|
1 | View Pending Requisitions As an issuer of stock 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: Label: VIMS |
Prioritize Pending Requistions As a issuer of stock 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: Label: VIMS | |
Round Up Order to Pack-Size As a DIVO, I would like to round up the stock order to packaging size… so that I can eliminate the need for the RIVO to adjust the amount distributed. Label: VIMS | |
Top-Up Requistion Order to meet Buffer Guidelines As a DIVO or Intermediate Warehouse Manager, I would like to automate the ordering process by having the system automatically calculate the routine top-up so that I can ensure I have ordered the proper amount of buffer stock based on my catchment area. Acceptance Criteria
| |
View and Print Order List As a DIVO or Intermediate Warehouse Manager, I would like to print a requisition based on the stock to be picked from inventory so that I can be guided as to what lot numbers should be packed for delivery. Acceptance Criteria
| |
View Orders from Regions As a National Logistician I want to be able to view and check the list of orders come from regions so that i can print them in a consolidated list before I send them manually to MSD Acceptance Criteria:
| |
Final Stock Movement Report As DIVO, RIVO and National user, I want to get a report which show what quantity moved from one storage point to another due to requisitions fulfilment Acceptance Criteria
|
Card # | Prepare Order based on Allocations |
---|---|
All SELV load amounts/plan distribution stories since its allocation based | |
DELIVERY SUB-DOMAIN features
SELV stories for workflow support when a logisitician arrives at facility
PICK-UP SUB-DOMAIN features
Order Receipt Confirmation
CAMPAIGNS SUB-DOMAIN features
HCMIS and DVDMT
Notes to Facilitator
Archive
OpenLMIS: the global initiative for powerful LMIS software