Oct 19–Nov 11Build
Builder stint
- Design, load, query, validate, and document one system.
- Complete the receiver-centered handoff pack.
36-614 · two-project final
Build, Hand Off, Receive
Each team builds one client system through November 11, transfers it on November 13, then operates and improves the other system through December 2.
The Climate and EV projects are distinct and only loosely related. Every team is graded in both roles: builder and receiver.
The systems
Climate Risk & P&C Insurance
- PostgreSQL
- NOAA Storm Events, HURDAT2, GHCN-Daily, NWS
- ACS, Zillow, geocoding, or xView2 enrichments where useful
- Underwriting, loss-frequency/severity, hail, and event-trend questions
EV Fleet Siting & Grid Context
- PostgreSQL or DuckDB
- EIA, NREL AFDC, FHWA freight
- eGRID, ACS, OSM/TIGER context
- Charging gaps, freight corridors, schedules, and upgrade-study priorities
Evidence boundary: public sources listed in the brief do not measure transformer/substation capacity. Proxy measures must not be presented as measured capacity.
Timeline
Nov 13Transfer
Formal knowledge handoff
- Twenty-minute KT, access transfer, smallest-success run.
- Builders observe the first receiver cold-start step.
Nov 16–Dec 2Receive
Receiver stint
- Reproduce one result, answer a new question, and extend the inherited system.
- Professor McGovern Parts I and II due Dec 1; acceptance test Dec 2.
Acceptance evidence
Builder pack
- Source inventory and ER diagram
- Data dictionary with grain, units, provenance
- Rerun-safe ingestion and validation
- Eight client queries and safe Python entry point
- Runbook, known issues, recovery notes
Receiver pack
- Timestamped cold-start log
- Reproduced builder result
- New client question and tested query
- One scoped, tested improvement
- Transfer-failure and evidence-boundary reflection