Emil

Emil is the chief engineer. He builds the models, prepares the data they stand on and runs them — and he is the assistant with by far the largest tool surface, because engineering a scenario properly is where most of the actual work lives.

• 01

  Demand, to end-use level

  Sectoral and sub-sectoral demand across residential, buildings, transport and industry — decomposed until the assumption you care about is actually visible rather than buried in an aggregate.

• 02

  Supply, storage and networks

  Generation fleets, storage assets and network topology across all four carriers, at whichever granularity the study needs — one node per country, bidding zones, or unit by unit.

• 03

  Geography and climate

  Build a model section straight from the map, and run it across multiple PECD climate years — wind, hydro inflow and temperature — including SSP2-4.5 forward trajectories.

• 04

  Model organisms

  Scenarios behave like organisms rather than files: combine two, mutate one parameter set, graft a region from another model, reproduce a variant. Lineage survives every one of those operations.

• 05

  Analysis and solve preparation

  Deep analysis over model results, and full preparation of PLEXOS-bound work. Hosted solve execution is held behind licensing and isolated-worker architecture — Emil prepares now, executes when that lands.

Ask Emil for "the same scenario but with the 2003 climate year and Iberian electrolysers at unit level" and you get a run, not a rebuild.

What working with Emil is actually like