← all projects
Case study · IoT · route optimization

Smart Waste Management
real-time bins, optimized routes, measurable impact.

Urban waste collection runs on fixed schedules regardless of whether bins are full. This system replaces schedules with data: ESP8266 microcontrollers with HC-SR04 ultrasonic sensors monitor bin fill levels every 30–60 seconds, push readings to ThingSpeak cloud, and trigger a GraphHopper route optimizer for collection vehicles. Measured result: 20–30% reduction in travel distance and 34% fuel savings over traditional fixed-schedule collection. Selected for the NCC Idea & Innovation Camp — Republic Day 2026.

Repository ↗
±1 cm
SENSOR ACCURACY
30%
TRAVEL DISTANCE SAVED
34%
FUEL SAVINGS
33%
TIME SAVED PER ROUTE
99.2%
SYSTEM UPTIME

01 · The problem

Metropolitan waste collection in India operates largely on fixed schedules — trucks leave at set times, follow predetermined routes, and collect from every bin regardless of fill level. The consequences are predictable: overflowing bins before trucks arrive (public health risk), trucks making collection trips to bins that are 20% full (fuel and time waste), and no data-driven way to adjust allocation as urban areas grow.

The core insight driving this project: waste generation is non-uniform and dynamic. Market areas fill bins in hours; residential areas take days. A system that measures fill level in real time and routes vehicles only where needed changes both the economics and the environmental footprint of urban waste collection.

02 · System architecture

HC-SR04 Ultrasonic Sensor2 cm – 4 m range · ±1 cm accuracy · 30–60s update
WIRED TO ESP8266 (NODE MCU) — WIFI ENABLED MICROCONTROLLER
ESP8266 ProcessingMeasure distance → calculate fill % → threshold check (80%) → send alert if full
HTTP OVER WIFI → THINGSPEAK CLOUD API
ThingSpeak CloudReal-time data store · visualization dashboard · REST API endpoints
DUAL MOBILE APP LAYER
Truck Driver AppGraphHopper route optimization · turn-by-turn nav · priority ranking by fill level
Public User AppBin location map · overflow reporting · collection schedule

03 · Fill level calculation

The sensor is mounted at the top of the bin pointing downward. Fill percentage is calculated from the measured distance and known bin height:

Fill % = ((Bin_Height − Measured_Distance) / Bin_Height) × 100
Example: Bin height = 120 cm · Measured distance = 24 cm
Fill % = ((120 − 24) / 120) × 100 = 80% → Alert triggered

Collection is triggered at 80% fill threshold — leaving headroom for overflow while maximizing vehicle utilization. The ESP8266 checks this threshold on every reading cycle (every 30–60 seconds) and fires an HTTP POST to ThingSpeak only when fill exceeds the threshold or changes significantly, minimizing bandwidth consumption.

04 · Measured results

Traditional vs optimized collection for a 10-bin metropolitan zone, measured across prototype deployment:

METRICTRADITIONAL ROUTEOPTIMIZED ROUTEIMPROVEMENT
Total distance12.5 km8.2 km34% reduction
Time required45 minutes30 minutes33% faster
Fuel consumed3.8 L2.5 L34% less fuel
Cost per cycle~₹200~₹130₹70 saved/cycle
Sensor accuracy±1 cm—
System uptime99.2%—

At 30 collection cycles per month, the ₹70 per-cycle saving translates to ₹2,100/month for a 10-bin zone — before accounting for reduced vehicle wear, fuel price volatility, or the environmental impact of 1.3L fewer liters burned per cycle.

Travel
−34%
Time
−33%
Fuel
−34%
Cost
−35%

05 · Recognition — NCC Idea & Innovation Camp 2026

🏆 CERTIFICATE OF APPRECIATION · THAKUR COLLEGE OF ENGINEERING & TECHNOLOGY

Selected for NCC Idea & Innovation Camp — Republic Day 2026

Awarded a Certificate of Appreciation by TCET in recognition of outstanding achievement in being selected for the Idea & Innovation Camp — Republic Day 2026, a prestigious national-level platform conducted under the National Cadet Corps. The project "Smart Waste Management" was recognized for demonstrating the ability to develop innovative solutions addressing real-world urban challenges. Signed by the Principal, Mentor & OIC TCET NCC Unit, and Associate NCC Officers.

06 · Design decisions & limitations

80% threshold — not 100%.

Triggering collection at 80% rather than full capacity provides headroom for unexpected overflow surges (events, market days) while still catching bins before they become a nuisance.

HTTP over WiFi — not LoRa or cellular.

WiFi was chosen for prototype simplicity and cost. Production deployment at metropolitan scale would require LoRaWAN or NB-IoT for reliable coverage without per-bin WiFi infrastructure. Documented limitation, not a design flaw in a research prototype.

GraphHopper for route optimization.

Open-source routing engine using turn-by-turn navigation with bin priority ranking by fill level. Proximity-based sorting ensures high-fill bins are serviced first within geographic clusters.

10-bin prototype, not city-scale deployment.

Results are from a prototype zone. At scale, additional complexity arises from bin density, vehicle capacity constraints, multi-shift scheduling, and integration with municipal IT systems.