2. About Breakfast Revolution
The problem of malnutrition in India is grave and needs urgent attention. Malnutrition is more
common in India (43%) than in Sub-Saharan Africa (26%).
There is a need to tackle this in an evidence-based, sustainable & scalable manner that is cost-
effective, acceptable to local communities & uses local resources.
Breakfast Revolution has designed a program to fight malnutrition leveraging low-cost
interventions along with stringent monitoring and strong community buy-in by providing tasty,
nutritious, cost-effective and safe breakfasts.
5 products – Biscuits, Soya Plain, Soya Chatpata, Bajra Puff and H.P Mixture.
For further information visit http://www.thebreakfastrevolution.org/
3. Vision
• India without Malnutrition
Mission
• Tackle micronutrient (vitamins and minerals) and protein deficiency in children,
adolescents and women from the poorest communities in a cost effective way
Strategy
• Distribution of the products
• Monitoring and Evaluation (M&E) of health indicators
• Behaviour change communication
4. Current Process
Step 1: Get the list
of patients
• Record the name, case ID, gender, contact details, address, hub
centre, registration date in Microsoft Excel
Step 2: Set up an
appointment
• Call up the patient to fix a date and suitable venue for meeting
Step 3: Preparation
of the order
• Required number of boxes are made in the office
5. Step 4: First
Delivery
• Six field workers are allocated different hub centres
• They carry the patient files along with the boxes to record the height and
weight of the patient at the time of delivery
Step 5: Transferring
the data
• The date of delivery, height and weight of the patient are transferred to the
excel from the files by a person in the office
Step 6: Second
delivery
• A second box needs to be delivered within 25-30 days after the first delivery
• Follow up calls are made to set up a meeting and if the patient is unavailable
the meeting is postponed
6. Problems in the Current Process
Patient volumes
◦ Difficult to keep track of every patient in Microsoft Excel
◦ Tough to know which patient to call as required filters have not been applied to the last date
of delivery
◦ No reminders are set, which often causes a delay in the delivery
Transfer of data
◦ Since the data is collected in files, transferring of the data in Excel is tedious and time
consuming
◦ As the entire data is transferred by a single person in the office there are high chances of
error and loss of the data
7. Impact of Problems in Current Process
Problem Incorrect Data Missed Appointments Financial
Difficult to keep track of patient volumes
Difficulty in patient follow up
Transfer of data
8. Objective of the To Be system
Create a sustainable and scalable, evidence based system for administering the Breakfast
Revolution program
Ensure timely & correct dispensing of breakfast items
Facilitate correct recording of data
Reporting & Analytics to develop insights, measurement of progress or effectiveness of the
NGO activities
9. Key Functional Requirements
Functionality Description of functionality
In built data validation Since data is entered manually for local resources with low computer
literacy, the system to detect (& prevent) incorrect data entry
Ability to create reminders for
follow-up appointments
As the volume of patient increases, it will be important to get reminders
from the system for ensuring timely dispensation & follow-up
Workflow for approval of data entry In addition to the data validation at time of data entry, it will be
important to have a provision of approval by an appropriate authority
Offline mobile data entry capture Field workers should be able to capture data in an offline mode, which
can then be uploaded to the system
Reporting and analysis As the program progresses, various reports should be available to
determine the effectiveness of the program
Administration Ability to add/delete new users, user profile, define workflows, etc.
10. Non-functional Requirements
User Interface
◦ Easy to use for low computer-literate users
◦ Minimal or no training required
Cost of Development & Maintenance
◦ It should be cost-effective
◦ Low (or no) maintenance
Architecture
◦ Basic application security to be in-built
◦ Scalability, performance and volume requirements to be addressed
◦ Easy import/export of data in bulk
11. User profiles for the to-be application
User Profile No of Users No of transactions/ month User characteristics
Data entry Currently there are 5-6 users
and may go upto to 10-12 in
the next 12-18 months based
on popularity of the program
Currently about 700
transactions per month, which
will increase at about 200
transactions every month
These are local resources who
may not be computer literate
There is attrition at this level and
so new users may come in from
time to time
The data entry will be done from
desktops at the back-office
Reporting 1-2 Senior Program Leaders They will need weekly, monthly
& yearly reports to determine
progress of the program
The reports may have to be
available on mobile devices
