View Source

Target release	Release name or number
Epic	Reporting - Stock Imbalance
Document status
Priority
eLMIS Status	Implemented
OpenLMIS Status	Not Implemented
PATH
OpenLMIS	Mary Jo Kochendorfer (Deactivated)
JSI	Ashraf

Goals/Scope

The stock imbalances report by facility shows lists of facilities that are stocked out, over stocked, under stocked; and to identify products which facilities have left out of the R&R which they should have included.

Status in eLMIS: In eLMIS

Status in OpenLMIS: Not implemented within OpenLMIS, can be created in Tableau

Priority: High priority

Background

The stock imbalance report shows lists of facilities and product combinations.

Use:

Only counts from regular requisitions (emergency should be incorporated into regular)
As the reports are being used, there is a shift to wanting notifications to alert people to the situation rather than requirement to look for that information
Different users will want to see these things differently - also want to reduce the number of reports
WHEN do people use this - it is retrospectively, different users will look at different times throughout the month/period

For each it shows:

the average monthly consumption
the closing balance
the closing balance in terms of months of supply
the ordered quantity.
A status of “stock out” (0), “under stock” (months of supply < 3), adequately stocked (MOS 3-6), over stocked (MOS > 6) and unknown (AMC=0).

Parameters:

program
period (which can be an A / B / C quarter period)
stock status filter (all, or one or more statuses)
geographic filter which can be entire country or a subset
facility type filter (optional)
facility filter (optional)
product category filter (optional) - eg antibiotics, antimalarials etc - simpler way to shorten the report
product filter (optional)

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 feature 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	See under and overstocked levels at facilities	As a logistic officer I need to have data on overstocked and understocked facilities so that I can decide on re-distributions of products to ensure they are not out of stock at facilities.	Tanzania eLMIS report	Must have
2	Identify missing products on R&R for facilities	As a logistic officer I need to identify products which facilities have left out of the R&R which they should have included so that products are not out of stock in facilities.	Tanzania eLMIS report	Must have	ordered quantity on the report
3	Export reports to Excel	As a logistic Officer 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.	Tanzania eLMIS reports	Must have
4	Print reports with headings and logs	As a logistic officer I need to be able to print reports with customized headings and logos so that I can file a report for future reference.	Tanzania eLMIS reports	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	For Tanzania user stories: review the users, "so thats" added, review the label, and review the priority level.	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.