|
Provide statistics about Order and item fill rates
Status in eLMIS: Implemented.
Status in OpenLMIS: Not implemented within OpenLMIS, can be created in Tableau
Priority: High priority for Tanzania
Use: A priority for systems interfaced with WMS/ERP, labor/data entry intensive to get if not interfaced (requiring delivery)
Used by both warehouse and facility, but especially for warehouse as part of the performance KPIs - they are accountable to their
At a facility it is good to know if your order is getting filled/to what level (tech. a different report but there are elements in it that would be used prior to delivery/receipt) - trends can be useful for advocacy if need to make complaints or encourage more procurement etc.- hold people accountable
The report shows:
Note: PDF and Excel export includes addional datapoint Supplimental Funds Used
Parameters:
In this story user means or one of the following, Health Facility incharge, DMO, Community and Regional Management Team (C/RHMT), Logistics officer/Advisors, Senior level decision maker, M&E officer/Advisor etc
# | Title | User Story | Label | Importance | Notes | JIRA Tickets |
---|---|---|---|---|---|---|
1 | Report | As an user/supervisor/admin I want to be able to ... | Reports | Must have for TZ | ||
2 | View order fill rate | As a user, I need to see how my order was fulfilled and which products were not fulfilled | Reports | Must have for TZ | ||
3 | View item fill rate | A a user, I need to how much each product was fulfilled. | Reports | Must have for TZ | ||
4 | Export reports to Excel | As a user, I need to be able to export all reports and analysis reporting results into Excel so that I can process the data more and analyze it in Excel. | Reports | Must have for TZ | ||
5 | Print reports with headings and logs | As a user, I need to be able to print reports with customized headings and logos so that I can file the report for future references. | Reports | Must have for TZ | ||
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.
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 |
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 |