The UK 2050 Calculator Web Flash Excel Wiki
Register or sign in
This is a wiki Anyone can contribute, therefore we don't vouch for its accuracy.

Team contacts and responsibilities

Responsibilities

Sophie Hartfield

  • Ensuring team is joined up and delivers on time
  • Whitehall clearance
  • External stakeholders: considering what we want from them and contacting them to talk them through how the process will work
  • Support in heat and bio meetings

Tom Counsell

  • Calculator operability
  • Power and heat network, transmission losses, district heat, fossil fuel indigenous production
  • Wiki functionality
  • The web tool
  • Support in heat and bio meetings

Michael

  • Power costs – getting agreement across Whitehall
  • Identifying power sector stakeholders
  • Power sector wiki
  • Project planning
  • Other (see list below)
  • Heat costs (until 16th May)

Neil

  • Transport costs – getting agreement across Whitehall
  • Identifying transport sector stakeholders
  • Transport sector wiki
  • Keeping note of economic methodology issues
  • Other (see list below)

Alistair

  • Bioenergy costs – getting agreement across Whitehall
  • Identifying bioenergy sector stakeholders
  • Bioenergy sector wiki

Rees

  • Heat costs – getting agreement across Whitehall
  • Identifying heat sector stakeholders
  • Heat sector wiki

Nazmiye

  • Making the Calculator consistent with Markal
  • Improving representation of industry
  • Other (see list below)
  • Improving Markal (e.g. updating some of the physical constraints assumptions in Markal with better assumptions from the Calculator).

Jan (some of this done by Nazmiye depending on Jan’s capacity)

  • Industry costs – getting agreement across Whitehall
  • Identifying industry sector stakeholders
  • Industry sector wiki

Other - work that Alistair and Rees don’t need to get involved with:

  • Getting the economic methodology signed off across Whitehall.
  • Identifying the “bombs” in the analysis and drafting lines to take prior to Summer release.
  • Testing the calculator for operability/bugs, any perverse/counterintuitive results and “bombs” and drafting the lines to take.
  • Testing the wiki (if we use one).
  • Peer reviewing the rest of the team’s spreadsheets.