|
Goals/Scope
The vision is to support OpenLMIS users with both routine reporting and ad-hoc analysis. Users need a way to visualize and extract data.
Background
Routine reporting
- if a report is queried/run/delivered on a routine basis, meaning more than once a year
- A template can be defined to run the report
Ad-hoc analysis
- user can define desired data element combinations (via a programming language or wizard)
- Not routine and the combination of data elements is run infrequently (once year)
User Personas
| User | Tech aptitude | Scope of supervision | Kind of Reports | Access (how/when) | Frequency** | Report Types |
|---|---|---|---|---|---|---|
Store Manager | Low | Only responsible for one geographic facility but may have multiple storerooms | Routine |
| Monthly or more (if available) |
|
Intermediate Store Manager (could be district, regional, providence) |
| Supervises a subset of facilities or specific zone. Facilities must be mapped to zones. | Routine |
| Monthly or weekly depending on replenishment schedules |
|
Central Personnel or Central Program personnel |
| National supervision of all geographic facilities OR national supervision of one program. | Routine Some ad-hoc (where VAN is rolled out) |
|
|
|
Administrator (unclear if this persona would support reporting) | ||||||
| Implementer |
| Ad-hoc |
**If the implementer is using stock management, frequency of reports would increase.
Assumptions
- If the implementer is using stock management, frequency of reports would increase with transaction data.
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 | Short identifier for the story | Describe the user and what they are trying to achieve As a ______ I want/need to ________ so that I _______. - High level acceptance criteria | Relevant labels to distinguish source. From which system, or which country? | Must Have, Nice to Have |
|
| 2 |
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 |
|---|---|
| Create user personas and outline objectives |
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 |
Example reports
Assuming the perspective of a national-level program manager who wants visibility into the activity of their program by region/district, but who would also like the option to get granular-level visibility into facility-by-facility data as well.
1 - Stockout days
- Ideally would be able to view on a map geographically
- Could show avg. # of stockout days in a district – aggregated data from all facilities in that district to give a picture of the overall stockout rate for that district
- User could click on the facility list and see the specific facilities reporting stockouts
2- Stock levels/Consumption
- Nice to view on a map geographically
- Shows SOH at beginning of period and SOH at the end of period for each facility
- Graph could show min/max levels to indicate that stock delivery is adequate to bring stock levels up to max, if they’re ordering too much, or too little
- Can show that a facility stock level is below the min or near stocking out
3 -Timeliness and completeness of reporting
- Could show aggregate for the district of whether district is reporting on time
- Similar to Stockout Report, user could click on the facility list and see the specific facilities which were not reporting on time
4 - On Time and full deliveries
- Could show aggregate data for a district/region for on time and complete deliveries that month.
- Similar to Stockout Report, user could click on the facility list and see the specific facilities which reported delayed or incomplete deliveries
Some other ideas we tossed around but didn’t discuss as thoroughly were:
Financial Reports
A program manager would use this report to measure how much money a facility should have (relating to cost recovery)
A program manager could also see a graph depicting the total costs of requisitions for their area (get a clearer picture of where their money is going)
Could see whether facility is in the red/black based on cost recovery analysis
Emergency Orders
Good to show on a map - district level making emergency orders to provincial level, potential risk of stockouts.
Out of Scope
- List the features discussed which are out of scope or might be revisited in a later release.