01Citizen App — your city in your pocket
Report, track, verify — and never wait for a bus blindly again
1 · Ward supervisor acknowledges within 2 h (you get a notification)
2 · Crew assigned · status turns “In progress”
3 · You verify the fix — that's the loop that keeps the city honest
02City Ops — the control-room backbone
Same data, other side of the loop: dispatch, SLAs, fleet and waste routes
City Ops Control RoomGandhi Nagar · pilot ward
on the map to inspect & act
| Bus | Route | Status | Occupancy | Next ETA |
|---|
03The business behind the app
A civic platform must first serve citizens — then pay for itself
- Predictable commutes — live ETAs and last-mile options end “guess-waiting”
- A voice with visible outcomes — every report tracked, verified, rewarded
- Monsoon safety nudges 3 hours ahead, not after the water rises
- 77% lower cost per resolved issue; crews routed by data, not complaints
- Ready-made Smart Cities Mission & Swachh Bharat 2.0 compliance dashboards
- Citizen trust becomes measurable: 64% closures verified by the public
- Digitised demand: riders see verified trip demand hotspots
- Higher occupancy on last-mile legs; predictable daily income
- NagarConnect takes a small booking commission — win-win, not toll
- Points wallet funded by CSR budgets — measurable ESG outcomes
- Opt-in hyperlocal offers (cafes, stationery) — ads never in the civic loop
- Sponsor named impact: “This bin cluster cleaned by [Brand]”
Campus
- Up to 25,000 app users
- Transit tracking · waste module · civic reporting
- Ops dashboard + SLA alerts
- Email support · quarterly impact report
City Growth
- Up to 2,00,000 citizens
- Everything in Campus + predictive flood & traffic alerts
- Last-mile booking marketplace + commission engine
- Open API · SBM / SCM compliance exports
- 99.5% uptime SLA · dedicated success manager
Smart City Enterprise
- Unlimited zones, IoT sensor integrations
- Anonymised insight products for urban planners
- Command-centre integration (CCTV, EMS, flood sensors)
- Data-privacy audits & DPDP-aligned governance
Impact ledger — before vs after NagarConnect
| Metric | Today (manual) | With NagarConnect | Change |
|---|---|---|---|
| Average issue closure timepotholes, lights, waste | 21 days | 4.2 days | −80% |
| Cost per resolutioncrew trips, escalation overhead | ₹1,840 | ₹420 | −77% |
| Waste truck route distancefixed routes → fill-driven | baseline | −28% km | fuel + CO₂ saved |
| Bus wait-time uncertaintyarrival prediction error | ±18 min | ±3 min | −83% |
| Citizens who see the outcomeof their report | 18% | 81% | trust flywheel |
| Waterlogging warning lead timemonsoon season | 0 (reactive) | ~3 hours | safety impact |
Campus pilot (Gandhi Nagar)
One campus cluster, 5,000 users. Prove: 48h closure SLA, +3× reporting participation, one full monsoon event documented.
Two city ward clusters
Municipal SaaS contract, last-mile operator onboarding (30+ e-rickshaws), first anonymised insight reports sold to planners.
City-wide + replicate
Smart City Enterprise rollout, insight products across zones, template playbooks to replicate in 5 more SDG-11 partner cities.
04Brief, SDG 11 mapping & classroom notes
How each module answers the project brief — and where it is honestly still a simulation
| Challenge (from brief) | NagarConnect module | SDG target | 2030 outcome we commit to |
|---|---|---|---|
| Commuters lack real-time information on buses, trains and last-mile options | Live transit map · ETA boards · last-mile marketplace | SDG 11.2 | Safe, affordable, predictable multimodal commute for every student and resident |
| Waste collection is inefficient, bins overflow, routes are missed | Smart bins (fill sensors) · route optimisation · segregation score | SDG 11.6 | No bin above 85% for more than 4 hours; −28% collection km; 90% source segregation |
| Hazards, potholes and flooding are reported late or not at all | 30-second AI report flow · predictive monsoon watch · congestion index | SDG 11.5 / 11.b | Hazard nudges 3 h ahead; every blockage visible to ops within minutes |
| Citizens rarely see what happens after they report an issue | Transparent ticket timeline · citizen verification · rewards loop | SDG 11.3 | 81% of reporters see and verify the outcome — participatory civic governance |
| Day-to-day civic problems depend on slow, manual reporting | City Ops backbone · SLA watchlist · fleet & route analytics | SDG 16.6 / 11.a | 4.2-day average closure at 77% lower cost per issue |
Honest limits of this prototype
- All data is simulated — buses, bins, SLAs and alerts are scripted for demonstration, not live feeds.
- Map is schematic — a campus-style layout, not GPS survey; production would use GIS tiles.
- Sign-in is deliberately light — an alias plus one notification channel (email or SMS), no passwords. In production this becomes an OTP login with DPDP-compliant consent; notifications are transactional only.
- AI tagging is mocked — a real build would use an on-device/on-edge CV model with human review.
- Privacy by design: only the reporting flow is demoed end-to-end; production needs consent flows, DPDP compliance and data minimisation (aggregated insights only).
- Inclusion: production UI needs local-language support, voice reporting and low-bandwidth SMS fallback.
3-minute classroom script
- 0:00 — Intro page: motto, the four pain points, the loop. Tap Open the app → sign-in (name + email/phone — alerts only, no password; or skip as guest).
- 0:30 — Citizen App → Transit tab: buses moving, ETAs counting down; zoom/pan the map, tap the Dynamic Island for the next arrival. “Uncertainty is the real commute tax.”
- 1:00 — Report tab: full flow in 30 seconds → tracking ID. The Island announces it. Switch to City Ops: report already in SLA watchlist. Resolve it — the citizen gets a simulated SMS/email.
- 1:45 — Back to Citizen → My Reports → Verify. “The loop closes with the citizen, not for them.”
- 2:15 — City Ops → Overflow a bin → click pin → Dispatch truck. Waste intelligence in one gesture.
- 2:40 — Business tab → Impact ledger: who pays, what they save. Close on SDG 11.3 — participation.