---

???? Neftaly AquaHarvest Software Prototype / MVP Development

For: Neftaly Monthly May SCDR-3 Science and Innovation Competition

Component: Smart Monitoring and Dashboard System for Atmospheric Water Harvesting

---

???? 1. Objective of the Software MVP

The goal of the software prototype is to:

• Monitor real-time sensor data (humidity, temperature, water flow)
• Display data in a user-friendly mobile or web interface
• Alert users about system maintenance, water levels, and performance
• Serve as a learning tool for Neftaly youth in IoT and programming

---

???? 2. Core Features of the Software MVP

Feature	Description
Live Data Display	Humidity, temperature, and water collected (in liters)
Dashboard Interface	Web or mobile app (MVP) showing real-time and historical data
System Status Monitoring	Indicates whether system is online, offline, or needs maintenance
Alerts & Notifications	Alerts for low yield, cleaning due, or sensor error
Youth Leaderboard (Beta)	Tracks contributions from different Neftaly clubs (for gamified engagement)
Open-source Integration	Codebase shared via GitHub or GitLab for replication and learning

---

????️ 3. Tools and Technologies

Function	Technology Used
Microcontroller	ESP32 or Arduino Uno with Wi-Fi module
Sensor Data	BME280 (Temp, Humidity), YF-S201 (Flow)
Programming Language	C++/Arduino, Python (for backend if needed)
Frontend Interface	MIT App Inventor, Blynk App, or ReactJS
Backend (MVP)	Firebase (realtime DB), or local server
Data Transmission	Wi-Fi or GSM (SIM800L module)

---

???? 4. MVP Development Steps

Week 1 – Hardware & Sensor Integration

• Connect sensors to ESP32 board
• Write firmware to read data every 30 seconds
• Send data via Wi-Fi to Firebase or local server

Week 2 – Frontend Dashboard

• Use Blynk, MIT App Inventor, or simple React dashboard
• Display:
  • Current temperature, humidity
  • Liters of water collected per day
  • Graph of past 7 days’ water yield

Week 3 – Alerts & Maintenance System

• Add thresholds:
  • Low RH warning
  • Low water output alert
• Use push notifications via Blynk or app notification feature

Week 4 – MVP Testing and Debugging

• Test with simulated or real sensors
• Record data over 3 days
• Ensure sync and display on all connected devices

---

???? 5. MVP User Interface Preview

Screen	Features Shown
Home Screen	System status (Online/Offline), Daily Yield (L)
Sensors Dashboard	Real-time temp, RH, water flow
History Graph	Line chart of yield vs. time
Alerts Panel	Notifications: cleaning due, low humidity alert
Club Dashboard (Beta)	Leaderboard of Neftaly youth clubs contributing data

---

???? 6. Educational and Engagement Value

• MVP will be co-developed by Neftaly youth (aged 15–25)
• Offers exposure to:
  • Embedded systems programming
  • Real-time data processing
  • UI/UX design for development impact
• Will be used to train other clubs across Neftaly regions

---

???? 7. Testing Plan

Test Parameter	Target Outcome
Sensor Accuracy	Within ±5% of reference device
Data Transmission Lag	< 5 seconds from ESP32 to app
App Uptime	95% functional availability over 3 days
User Feedback Score	> 80% ease-of-use from test users

---

???? 8. Open Source and Replication

• All code will be shared via GitHub repository
• Includes:
  • Arduino sketches
  • App source code
  • Documentation for setup and deployment
• Promotes peer-led innovation and open learning across Neftaly chapters

---

✅ Conclusion

The Neftaly AquaHarvest software MVP is a powerful complement to the physical water harvesting system. It enables data-driven decision-making, enhances transparency, and encourages youth involvement in real-world technology development. With minimal infrastructure, it can be scaled, customized, and replicated in low-resource environments across the continent.

---