The project explicitly focuses on non-intrusive pool monitoring and high-risk event detection from camera streams.
AquaGuard
AquaGuard focused on non-intrusive pool-safety monitoring by using YOLO-based detection on camera streams to surface high-risk events earlier.
A source-backed case study built for recruiter review
This reading path makes the problem choice, evidence quality, user framing, execution decisions, and proof trail visible without overstating what the sources support.
Gold-medal iCE-CInno 2024 project delivering a CCTV-compatible computer-vision workflow for real-time drowning-risk detection.
Earned Gold Medal recognition at iCE-CInno 2024 in the university undergraduate category.
Inference pipeline based on YOLO models with service interface for near-real-time detection reporting.
Problem framing before execution
The case-study layer starts with why this problem was selected and how the context justified investment.
Problem Framing Map
Pool safety monitoring can fail when high-risk behavior depends on delayed human observation rather than early machine-assisted detection.
AquaGuard is documented as a competition-recognized computer-vision safety concept centered on CCTV-compatible drowning-risk detection.
It is a strong Wave 3 addition because it combines public recognition, safety-critical framing, and real-time-oriented ML system reasoning.
Problem statement
Pool safety monitoring often depends on delayed human observation, increasing critical response risk.
Solution thesis
Developed a computer-vision detection flow to identify high-risk behavior from camera streams and trigger early alerts.
What supports the narrative
Evidence is surfaced with its source type and credibility note so the recruiter can quickly see what is directly backed versus intentionally constrained.
The project earned Gold Medal recognition at iCE-CInno 2024.
Credibility Notes
- ●The case should be framed as safety-oriented ML concept and workflow evidence, not as a deployed life-critical product with field validation.
- ●No false-positive, recall, or deployment reliability metric is added unless explicitly supported in source.
User framing stays explicit
When formal research artefacts are not available, the page still explains who the work served and why that user framing is justified by the existing sources.
The problem statement and solution framing explicitly revolve around earlier alerting for safety monitoring.
The strongest public signal comes from competition recognition and real-time-oriented system framing.
How design thinking translated into decisions
The goal is to show the trace from research and insight to concrete product or system decisions, then to the outcomes those decisions supported.
Design Thinking Flow
Each step keeps the movement from evidence to action explicit before the rationale expands it.
- Step 1Safety-risk framing
Defined the project around earlier risk detection rather than generic object detection performance.
Signal: Response urgency became the central product need. - Step 2Camera-compatible approach
Chose a non-intrusive monitoring direction using visual streams instead of requiring wearable or manual input signals.
Signal: The system remained aligned with practical CCTV deployment contexts. - Step 3Recognition-backed packaging
Turned the concept into a reviewable competition artefact with clear safety-system narrative.
Signal: Award context strengthens credibility without overstating real-world rollout.
Decision Rationale
Each decision keeps the path from insight to execution visible before ending on the outcome signal.
Safety monitoring loses value when inference is too slow for practical response windows.
Used a YOLO-based detection approach to match near-real-time monitoring needs.
The project narrative stays aligned with speed-sensitive safety use cases.
Pool environments benefit from monitoring approaches that do not depend on active user participation.
Framed the solution around CCTV-compatible computer-vision detection.
The product direction becomes easier to understand as a practical safety workflow.
Execution choices and delivery details
This section preserves the technical and operational substance: architecture, responsibilities, trade-offs, and implementation quality signals.
System Design
Inference pipeline based on YOLO models with service interface for near-real-time detection reporting.
Source-backed Impact
Earned Gold Medal recognition at iCE-CInno 2024 in the university undergraduate category.
Responsibilities
- ●Built model workflow and evaluation process
- ●Collaborated on deployment-ready inference path
Stack Decisions
- ●Used YOLO-based approach for real-time-oriented detection constraints
Trade-offs
- ●Accepted model complexity to improve detection sensitivity
Challenges
- ●Balancing false positives with safety-critical recall
What was delivered and what can be verified
Outcome claims remain conservative and source-backed, while proof records and recruiter-safe links surface the strongest verification trail available.
Validation Signals
- ●Gold Medal iCE-CInno 2024 is recorded as project proof.
- ●The project record documents a real-time CCTV-compatible drowning-risk detection workflow.
Source-backed Outcomes
- ●Gold Medal iCE-CInno 2024
- ●Real-time CCTV-compatible drowning-risk detection workflow
Proof
- International Award
Gold Medalist iCE-CInno 2024
UMPSA
Links
What the project proves, and what it does not
Strong case studies show both what was learned and where the current evidence stops.
Retrospective
A production path should include an incident-labeling feedback loop for continuous model improvement.
Evidence Limits
- ●Current sources do not provide field deployment evidence, calibrated safety metrics, or operational incident outcomes.
- ●The project should remain framed as competition-recognized safety-system reasoning and ML workflow evidence.
Lessons
- ●Safety products require rigorous scenario-based validation