Team:IISER-Pune-India/TeamNotebook/Team Notebook 11e9906b405543a29361e38a50c81024/Team Meeting 3 a94d41bd75d14837ba22b3cc2242a21d

Team Meeting 3

Team Meeting 3

DescriptionMaking rubric
HP sub-branch
Property 1
Property 2

Rubric Creation

  1. Who stands to gain/stakeholders
  1. Use well-characterised parts (for eg if degrading cellulose, there already exist many parts for these, which are experimentally verified which can be directly used in our project)
  1. Local vs. Global scale projects :
    1. we can choose a problem that has potential globally but we can focus on, locally
    1. scalability
  1. We can have projects which have both a consumer base and have efforts directed towards marginalised communities
    1. Akash: there's a need to include the communities in our project plans from the beginning, rather than focus on them after we design a project in the context of a consumer base (no temporal separation)
    1. Misaal: We can start with a more general framework, and then spend resources to give a marginalised community-context, as it might become very contextualised.
    1. Sanjana: Not focusing on the mar. com. from the start could lead to us spending a lot of time in between the project to try and figure out how to amene our project towards either the mar. com. or the consumer base
  1. Software-Hardware both aspects
    1. Making a hardware isn't necessary, developing/characterising a part
    1. Having it is a plus, so we could try for one piece of hardware + one piece of software
  1. If we attempt to compete with an already existing item for hardware, it should be cheaper/safer
  1. Project Safety
  1. Might want to avoid as much regulation as possible
  1. Abstraction, modularity, rational design, blackbox
  1. A layman should be able to use it-

Rubric (ranked priority-wise)

#1 Safety ::::: Feasibility (can it be applied in the real world > characterised parts >= if previous projects exist)

#2 SDG (also eco-friendly, marginalised communities)

#3 Impact (how does it compare to the current solution, what scales, economic feasibility, stakeholders)

#4 Product (Software-Hardware) ::::: Engineering Principles

#5 Scalability (in people/time)


GOAL 1: No Poverty

GOAL 2: Zero Hunger

GOAL 3: Good Health and Well-being

GOAL 4: Quality Education

GOAL 5: Gender Equality

GOAL 6: Clean Water and Sanitation

GOAL 7: Affordable and Clean Energy

GOAL 8: Decent Work and Economic Growth

GOAL 9: Industry, Innovation and Infrastructure

GOAL 10: Reduced Inequality

GOAL 11: Sustainable Cities and Communities

GOAL 12: Responsible Consumption and Production

GOAL 13: Climate Action

GOAL 14: Life Below Water

GOAL 15: Life on Land

GOAL 16: Peace and Justice Strong Institutions

GOAL 17: Partnerships to achieve the Goal


  • rubric
  • informal brainstorming sessions until Sunday
    • discuss on brainstorming channel
  • meeting on Sunday at 1730 hrs

Copy of Ideas rated by rubric

NameSafety, FeasibilitySDGImpactProduct/Engineering Pr.Scalability
Information ProcessingSafety: +1, feas.: +0.5 (needs more research)irrelevanthigh if feasiblesoftwareincreasing the number of analytes (depends on the model we choose)
siRNASafe, feasibleending hunger-more research neededmore research needed
e-WasteSafe* (cyanogenic, effluents, pretreatment), feasible sustainable cities, communities; innovation and infras.; responsible consumption; clean water-bioreactor, software?scalable
Hydrogen FuelSafe, feasibleclimate action, affordable and clean energy, responsible consumption, sustainability of cities-bioreactor, software?depends on if hydrogen fuel gets used in the future
Carbon Capturesafe, feasibleclimate action, responsible consumption, sustainability of cities, industry inn., -""scalable