[SELV/SIIL] Distribution/Re-Supply Domain: Plan a Distribution

Target release	Vaccine Module
Epic	Distribution/Re-Supply
Document status	DRAFT
Document owner	Vidya Sampath
Technical Lead	Technical Lead who reviews or supports document

Goals/Scope

- This is an informed push (allocation) based supply chains, vaccines are directly delivered to the level below instead of the level going to pick up the vaccines from the level above and the person dropping off makes the decisoin on how much to leave. This page captured the functionality requests for the personas responsible for planning the allocations and distributions.
- In informed push based SCs, users will reference this information when estimating how to package deliveries to an area and load the cold box/distribution truck

Background

Are there any country specific features that should be noted? Who are the personas? Who are the users that will be interacting with this functionality? What are their challenges, responsibilities, and level of connectivity? These personas are intended to be representative archetypes of the key stakeholders who will participate in theses workflows/scenarios.

Personas involved:

Intermediate Vaccine Warehouse/Store Manager (involved in decisions around allocation amounts leaving the intermediate warehouse) --

Intermediate Level Logistician/Distributor/Field Coordinator (assists persona above in allocation amounts to be packed into truck; also responsible for actual distribution of products and making allocation decisions at facility depending on SOH and stock available for him/her to distribute)

Assumptions

What are technical or business specific details and characteristics that should be known to explain the environment? List the assumptions you have such as user, technical or other business assumptions. (e.g. users will primarily access this features from a tablet).

User Stories

Short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system.

#	Title	User Story	Label	Importance	Notes
1	View load amounts for different variables	As a FC and/or intermediate warehouse manager, I want to view the load amounts for the scheduled delivery period so that I can pack the truck with the necessary amounts. I want to view the following: For the scheduled delivery period (could be bi-annual, quarterly, monthly, fortnight, a set of # days – eg every 40 days – etc which is configured in the system) For the area that the truck is going to (delivery zone) and disaggregated for each district and HC within it. I want to view the information in vials and/or doses, depending on my EPI program's decision	SELV, SIIL	Must Have	Splitting out types of vials by dose helps warehouse person pack What you see here is tied
2	View and manipulate load amounts (advanced)	As a FC, I want to view the total load amount, per product, for the area I am going to visit, and then have an input method that allows me enter my existing amount I have, so that I can then know the missing amount still needed to load up the truck with amount needed for distribution to that area. (NOTE – still open debate – is this under another domain wsuch as stock management?]		Very nice to have	Advanced ++ – system automatically calculating how much I have and showing me what's still needed when I open this page
3	View CCE status along with load amounts (existing RTM feature)	As a FC and/or intermediate warehouse manager, I want to know the CCE status of the facilities to which I am dropping off vaccines so that in the event of non-functional or erractic functioning of CCE, I can follow-up to see if I should even be planning to visit that facility. This way, I am not unnecessarily taking more vaccines than I need on my trip.	SELV	Must have where Nexleaf's CT is available	Note – move this to RTM feature
4	Facilities that make up a delivery area/zone	As a system admin, I want to be able to configure which facilities are in my delivery area and who is assigned to plan the visit and record data from the visit (details TBD)	SELV	Must have

Diagrams

Include any business process mapping, mockups, diagrams or visual designs relating to these requirements. Describes the tasks and the personas who perform those activities. The diagram provides the context for the user stories and serves as a focal point for achieving clarity and agreement among stakeholders. Looks like a standard flow chart.

Dependencies

Identify initial dependencies that are on the critical path for this functionality and may affect the delivery time and serving of business goals. Include links to stories.

Description	Link
Name of story or release	Link to JIRA

Open Questions

Initial communication between stakeholders and the development team to help understand scope and estimates.

Below is a list of questions to be addressed as a result of this requirements document:

#	Question	Outcome	Status
1	(e.g. How we make users more aware of this feature?)	Communicate the decision reached	Open, In Progress, Closed, and date of closure

Out of Scope

- List the features discussed which are out of scope or might be revisited in a later release.

Save