Modeler learning path

From a blank project to evidence you can defend.

Modeler is most trustworthy when every study preserves the chain from source and scope to input, scenario, solve and result ID. Follow these guides in order once; return directly to the solved example you need afterward.

Modeler evidence chain
Source → scope → scenario → solve → verified result

The series

Five guides, one evidence chain

Each guide begins with a solved result, then supplies the formulation, benchmarks, exact actions, engineering interpretation, five professional lenses, trust checks, FAQs and machine-readable HowTo markup.

  1. 01Getting startedThe safest first Modeler study is a result-first evidence chain: define one decision, load and inspect a sourced network, preserve the base case, change one scenario, lint and solve it, reconcile the physical result, compare economics and carbon, then stress-test the conclusion.45 minutes plus solve time
  2. 02Data Shop guideThe Modeler Data Shop turns a documented slice of Energy Atlas Intelligence into a model or an attachment. You select the dataset, geography, coverage window, resolution and target; the server re-validates the request and records an idempotent ingest order.60 minutes including QA
  3. 0330 MW BESS exampleFor a small BESS screen, solve an untouched base, rank buses by local price stress and evening ramp, place 30 MW / 4 h at the top-ranked bus, re-solve the cloned scenario, and compare physical and market metrics over the same horizon.75 minutes plus paired solves
  4. 04National BESS sitingRank every bus on the price spread and ramp severity the nodal solve actually produced, place capacity on the top-ranked buses in proportion to score, re-solve the clone on identical settings, and then check the resulting revenue against a market benchmark before calling it revenue — on this network the model puts 98.4% of a 5 GW fleet into the northern load pocket for delivery reasons, not arbitrage.60 minutes plus paired solves
  5. 05150 MW data-centre exampleA credible data-centre power screen separates policy, observed market and grid data, derived energy arithmetic and modeled nodal impacts. For Dholera, test an untouched base, a 150 MW flat load, and the same load with a 30 MW / 4 h co-located BESS over one identical horizon.90 minutes plus paired native-hourly solves
  6. 06Agent guideThe Modeler Agent is safest when a prompt names the target asset or selected component, the value and unit, the active scenario, the action, the comparison and the required truth label. Every mutation should appear as a typed action chip and be verified in the model afterward.45 minutes plus any requested solve

Choose by question

I have never used Modeler

Start with Getting started; it creates one base, one scenario and one result comparison.

I need India grid data

Use the Data Shop guide to choose a dataset, scope, lineage and target without losing provenance.

I am developing a small BESS

Run the 30 MW / 4 h single-site example and keep operational value separate from project ROI.

I am evaluating a data centre

Use the Dholera example to combine policy, market, carbon and nodal network evidence.

I want an agent to operate Modeler

Use the Agent guide’s six-field prompts, typed action checks and minimal handoff packet.

Blocked or seeing a different screen?

Open Modeler help & troubleshooting →