nursery-school-monitoring

byRaghoba Desai

PROJECT PROMPT: AI-BASED NURSERY SCHOOL SAFETY & WELLBEING MONITORING SYSTEM 1. Project Overview Develop a complete AI-powered monitoring system for nursery and preschool children. The system should help school administrators and authorized staff monitor student attendance, meal status, potential health concerns, and classroom safety using CCTV cameras, a web dashboard, and teacher-assisted reporting. The system must be practical, affordable, privacy-focused, and achievable within 15–20 days as a working MVP. 2. Main Features A. Student Attendance Monitoring * Register students with their name, class, age, parent contact, and authorized pickup details. * Record daily present, absent, late, and early departure status. * Use teacher-assisted attendance, QR codes, or an approved camera-based presence system. * Display daily attendance percentage and monthly reports. * Send attendance notifications to parents, subject to consent and school policies. B. Meal and Nutrition Monitoring * Maintain a student-wise meal checklist for breakfast, lunch, snacks, and water intake. * Allow teachers or caregivers to mark: ate well, ate partially, refused food, or meal not recorded. * Use optional camera-based observation to flag a possible meal-time concern where technically feasible. * Never claim that a child ate a specific quantity based solely on an ordinary CCTV recording. * Notify authorized staff when a child repeatedly refuses meals or has a recorded concern. C. Child Safety and Physical Punishment Detection * Use classroom CCTV to explore detection of potentially unsafe physical actions, such as hitting, pushing, or rough handling. * Use action-recognition models to flag suspicious events for human review. * Save a short incident clip or timestamped event reference where legally permitted. * Provide a secure incident-review panel for authorized administrators. * Include incident status: new, under review, verified, or dismissed. * Do not automatically declare that a teacher committed abuse based on an AI prediction. * Do not use facial emotion recognition to determine guilt, fear, or intent. D. Possible Illness and Wellbeing Alerts * Allow teachers to record symptoms such as fever, vomiting, unusual tiredness, injury, or discomfort. * Where feasible, flag visible events such as a child falling or remaining unusually inactive for an extended period. * Require staff verification before generating a health alert. * Never diagnose a disease using CCTV. * Provide an urgent incident workflow for suspected injury or immediate danger. E. Admin and Teacher Dashboard Create a modern, responsive web application with the following pages: 1. Secure login and role-based access. 2. Dashboard with total students, present students, absent students, meal concerns, and open safety incidents. 3. Student registration and profiles. 4. Attendance calendar and reports. 5. Meal tracking and daily meal reports. 6. CCTV camera status and live feed, if supported by the camera. 7. AI-generated event alerts with timestamps and review status. 8. Health and wellbeing reports. 9. Parent notification history. 10. Settings, audit logs, privacy controls, and user management. Use a clean, professional, child-friendly interface with a light background, readable charts, clear alert indicators, and responsive layouts. 3. Recommended Technology Stack Frontend: * React.js with Tailwind CSS. * Recharts for dashboard charts. Backend: * Python FastAPI. * REST APIs for attendance, students, incidents, meals, and notifications. Database: * PostgreSQL for student information, attendance, incidents, and reports. * Store CCTV footage separately; do not put large video files directly in the database. AI and Computer Vision: * Python, OpenCV, and Ultralytics YOLO for suitable object-detection tasks. * Evaluate an action-recognition model for possible unsafe physical interactions. * Use a vision-language API only if it is necessary and permitted for the selected workflow. * Keep attendance identification separate from incident detection. Infrastructure: * Existing CCTV cameras or an authorized test video source. * Local processing computer or an appropriately secured cloud server. * Encrypted storage, access controls, backups, and audit logs. 4. System Workflow 1. The administrator registers students, staff, classrooms, and authorized users. 2. CCTV cameras provide an authorized video stream. 3. The video-processing service samples frames or short clips. 4. The AI service processes supported visual events. 5. The backend creates a timestamped alert when a configured event is detected. 6. The administrator reviews the event and its permitted evidence. 7. An authorized person confirms, dismisses, or escalates the alert. 8. Attendance and meal records are updated by the camera system only where reliable; otherwise, staff enter the information. 9. Parents receive only approved, relevant notifications. 10. The dashboard generates daily and monthly reports. 5. API Requirements Design the following backend endpoints: * POST /api/students * GET /api/students * POST /api/attendance * GET /api/attendance/daily * POST /api/meals * GET /api/meals/daily * POST /api/incidents * GET /api/incidents * PATCH /api/incidents/{id}/review * GET /api/cameras/status * POST /api/notifications * GET /api/reports/summary Implement authentication, role-based permissions, request validation, error handling, and audit logging. 6. Privacy and Security * Obtain appropriate school authorization and informed parent/guardian consent before processing children’s video. * Assess applicable Indian child-protection, privacy, and data-protection requirements before deployment. * Avoid facial recognition and biometric identification in the MVP. * Process video locally where possible. * Do not continuously upload classroom footage to external AI services. * Use restricted, encrypted incident storage and a defined deletion schedule. * Do not use automated AI results to discipline teachers or children. * Provide an emergency escalation process for credible safety concerns. * Use synthetic or consented test footage during development. 7. Deliverables Generate: * Complete project architecture. * Frontend and backend source code. * Database schema and sample records. * AI/video-processing module with a documented fallback if real-time action recognition is unavailable. * REST API documentation. * Admin and teacher dashboards. * Testing instructions and sample test data. * Local installation and deployment instructions. * Project report, workflow diagram, and final presentation. * Itemized budget, hardware requirements, API requirements, and 15–20-day development schedule. Prioritize a functional, demonstrable MVP over unsupported claims of fully automatic monitoring. Build the application in working modules, test each module, and clearly label features that require further model training or real-world validation.