CompletedGlobal Bronze

Global Youth Summit on Net-Zero Future

UNESCO East Asia & GAUC @ Tsinghua 2024.09Team Lead
Global Bronze Award
Climate Action
Youth Leadership
Innovation

Climate Action · Youth Innovation · Low-carbon Product Proposal

Project Overview

Our team “Double-LT” proposed **Smart Green Home-stay**, a replicable low-carbon model for rural revitalisation. The solution integrates: • Rooftop PV (ABC solar cells) for on-site clean power and carbon reduction; • Water harvesting & recycling (rain/spring/greywater) for potable and non-potable reuse; • Temperature-control wall systems (PCMs/ICFs/SIPs) to stabilise indoor climate and cut HVAC load. The aim is an immersive, eco-friendly stay that balances tourism income with measurable emissions and water savings.

What I Worked On

  • Led scoping and storyline; aligned problem → constraints → trade-offs → metrics.
  • Sized rooftop PV and sketched payback sensitivities to anchor feasibility.
  • Outlined water capture/reuse scheme and basic quality tiers for end-uses.
  • Compared envelope options (PCMs/ICFs/SIPs) and mapped comfort/HVAC impact.
  • Defined KPI set and field-data plan (PV yield, water reuse logs, temperature profiles).
  • Built the decision-ready deck; assigned ‘decision pages’ so each chart answered a question.

Takeaways

Two things won judges over: **systems thinking** and **replicability**. Rather than a single gadget, we showed how PV, water reuse and thermal envelopes reinforce each other around one homestay so revenue, comfort and emissions reduction move together.

Narrative discipline mattered: turning scattered technical pieces into a single spine—problem → constraints → options → metrics—kept the deck tight and decision-oriented. Assigning work by “decision pages” ensured every exhibit earned its slide.

If iterating, I’d add a light **LCOE/LCCA** and a simple **bill-of-materials** to make cost/benefit legible for local operators. On measurement, a **field-data plan** plus a small replication kit would let other villages copy with minimal engineering debt.

Teamwise, early scope guardrails helped; we could have prototyped visuals sooner. Next time I’d time-box a “visual sprint” first, then back-fill analysis so the end-state stays crisp.