[VIMS/VLMIS] CCE : Monitoring and Supervision

Target release
Epic	Cold Chain Management & Reporting
Document status	DRAFT
Document owner	@JSI
Technical Lead	Ashraf Islam

Goals/Scope

Background

Assumptions

All users are expected to know how to use basic Internet tools.

User Stories

	Title	User Story	Label	Importance	Notes
1	Equipment functionality report	As a DIVO or RIVO, I would like to see a report showing the functional status of the equipment for the facilities I supervise... so that I can assist with key decisions.	VIMS	Must Have
2	storage capacity report	As a RIVO i should be able to know and see the storage capacity which is available and the storage capacity required to store Regional routine vaccine Acceptance Criteria The system should be able to compute required storage capacity( this will pull some of the parameters from Program Data .eg surviving infants) and compare with the Available storage capacity(this will sum the litres of Functional refrigerators only in that particular store)	VIMS	Must Have
3	Min/Max temperature report	As a DIVO, I would like to generate a report of facilities needing cold chain maintenance based on temperature alarms from monthly reports… so that I can reduce the risk of damaging vaccines due to temperature excursions. Acceptance Criteria I can select facility level and period ragne	VIMS	Must Have
4	Replacement plan report	As a National logistician i should be able to get report for CCE replacement plan and CCE functionality status By Regions, Districts and Health facilities Acceptance Criteria 1. Replacement plan report with numbers of refrigerators under that particular year of replacement so that when i click that number it directs towards that list of CCE. 2. Replacement plan for Region, District and Health facilities (regions),National Level (districts) and National Level (health facilities) respectively. 3. Pie charts which shows proportional by functionality status.		Nice to have	You could potentially do this ad hoc reporting via a reporting engine like Tableau. Core system may not need this (annual) routine report.
5	status alerts	As a RIVO I want to receive a text message/System notification when a refrigerator at my District Vaccine Stores (DVS) becomes non-functional So that I can make sure that a repair technician is dispatched Acceptance Criteria When an equipment becomes non-functional, RIVO receives a SMS notification. "<model> from facility <x> has been changed from functional to non-functional" DIVO and RIVO receives email every week with list of non-functional refrigerators (either in the body of the email, or as an attachment) For each non-functional refrigerator, the following info is displayed Facility's District, Facility Name, Manufacturer, Model, Non-Functional Reason, Days in Non-Functional Status, Refrigerator Capacity, Energy Source List is sorted by Days in Non-Functional Status descending Checkbox that Region/District has scheduled repairman DIVO/RIVO is the one to change status back to functional System should track how long it takes to fix from request Possibility of using repair date reported by technician rather than DIVO/RIVO changing the functional status		Nice to have ? Maybe certain pieces are must haves	Need to see in discussion if stakeholders need to have SMS notifications over other functionality. How important each SMS notification is (those necessary for certain workflows) versus how we can leverage email notifications. Currently v3 includes email notifications (not SMS or system notifications)