...
| Page Properties | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals/Scope
This functionality seeks to provide users of the system a way to estimate vaccine product need across a series of variables. Successful acceptance of this functionality would involve the following:
...
Estimates of the product is displayed/viewable in multiple views, such as – estimates of all products for a certain facility, district, store, province, region, etc; need estimates of a single product over multiple time periods (month, six weeks, quarters, years, etc).
Background
Effective vaccine management requires accurate vaccine forecasting and needs estimation, as well as adequate stock ordering that follows the delivery schedule, in conformity with cold chain capacity. This page focuses on the former and adequte stock ordering is captured under the "delivery/supply requirements" pages.
...
The accuracy of vaccine forecasting and needs estimation depends upon both the level of implementation (national, district or local service delivery) and the time period of estimation used (month, year, multi-year). Whichever method is applied, the accuracy of the estimation will depend upon the quality of data used; this is a pressing issue in the iSC space, and which we will cover under the "Reporting" Domain when looking at ways of reporting the "In-Full Order Delivery" indicator.
Assumptions
- Users will primarily access this information in close conjecture with the features in the "delivery/re-supply domain"
- In push based SCs, users will reference this information when estimating how to package deliveries to an area and load the cold box/distribution truck
- In pull based SCs, users will reference this information when estimating how much to request for their next order
- In both scenarios, it is likely that while users will "View" this information online, they would also take a print out of the page to show in meetings, with supervisors etc so that needs to be considered
User Stories
| # | Title | User Story | Label | Importance | Notes |
|---|---|---|---|---|---|
| 1 | View Needs Esitmates for Facilities in a district | As a district EPI supervisor, I want to see the needs estimates for all the facilities in my district so that I can ensure the stock in my district depot is enough to meet their needs via next scheduled re-supply and so I know when to place a requisition order from the level above for additional stock. | SELV | Must Have | |
| 2 | View Needs Estimates for Storage Points under a specific intermediate store | As an intermediate vaccine store manager, I want to see the needs estimates for all the storage points dependent on me (district depots, zonal depots, etc) so that I can ensure the stock in my district depot is enough to meet their needs via next scheduled re- and so I know when to place a requisition order from the level above for additional stock. | SELV | Must Have | |
| 3 |
Diagrams
Dependencies
| Description | Link |
|---|---|
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | From Tech/Brandon: How much is OpenLMIS intended to be the "planning tool" that people use to plan these amounts? If the planning process and the formulas and policies are highly variable by country and program/funder, then maybe it's better if the planning happens outside OpenLMIS, and OpenLMIS simply gets informed about the target amounts/ideal stock amounts. | Open |