Read a plan as a conditional pathway
A system plan compares development paths under assumptions and scenarios. A project appearing in a pathway is not the same as a funded, consented and commissioned project. Timing and dependencies can change system benefits.
The lesson
6 chaptersBrowse the chapters
01What the ISP decides—and what it does not
The Integrated System Plan is AEMO's scenario-based plan for developing the NEM power system. Read the final 2026 report and its assumptions together: an optimal development path is an outcome conditional on demand, technology costs, policy and delivery assumptions, not a guaranteed forecast.
Separate three decisions: a system need, a proposed investment to meet it, and the approvals and contracts needed to deliver that investment. A project appearing in a system plan does not, on its own, establish funding, land access, connection approval or an operational date.
Start your brief with edition, scenario, geography, planning horizon and the decision you are supporting. Use ESOO for the relevant adequacy outlook and ISP for the long-term development pathway; neither is an interval trading forecast.
02From assumptions to a development pathway
Read demand, electrification, consumer resources, fuel, generation retirement and technology-cost assumptions before comparing headline capacity numbers. Nameplate capacity (MW), storage energy (MWh) and annual production (MWh) cannot be added into a single capacity total.
A different cost or timing assumption can change the preferred sequence of generation, storage and network investment. Compare scenarios using the same metric and year. If two tables use different price bases or modelling boundaries, reconcile them before drawing a ranking.
Build an assumptions register with a central value, downside case, source and review trigger. For each material change, state whether it changes total system cost, timing, reliability exposure or the location of investment.
03REZs, connections and delivery dependencies
A renewable energy zone can coordinate resource development and network investment, but a regional designation does not eliminate each project's technical, environmental and commercial gates. Read Appendix A3 alongside the network-investment evidence in A5.
Identify the network path, transfer limitation, connection studies and commissioning sequence required for a project's output to reach consumers. A completed generator behind an unfinished transfer path may face a very different dispatch and revenue profile from the investment base case.
Keep dependency dates separate. Record the source date and whether each milestone is planned, approved, under construction or operational. Do not combine an old proponent estimate with a new planning scenario without explaining the difference.
04Transmission options: compare net benefits, not just capacity
Use the 2026 ISP cost-benefit analysis in Appendix A6 to understand system-level benefits and sensitivities. Then distinguish that planning analysis from a project's regulatory investment test, approvals, procurement and construction evidence.
Synthetic screening example: an option has present-value benefits of A$1.5bn and costs of A$1.1bn, giving A$0.4bn net benefit and a benefit-cost ratio of 1.36. A 25% cost increase raises costs to A$1.375bn and reduces net benefit to A$0.125bn. This simple arithmetic is not an ISP model rerun.
Timing matters as well as totals. A one-year delay can change which generation is constrained, what replacement supply is needed and when benefits begin. State discount rate, price basis, present-value date and the treatment of uncertainty in any comparison.
05Tasmania and the interconnector perspective
For Tasmania, relate hydro availability and water opportunity value to demand, interconnection and mainland prices. Analyse TAS1 and VIC1 at matching intervals; distinguish their price spread from losses, congestion rent and the value of incremental transfer capability.
Basslink, Marinus Link and Hydro Tasmania are distinct assets or organisations, not interchangeable descriptions of the Tasmanian market. Compare each asset's status and operating or project constraints using current owner information. Never treat proposed interconnection as existing capability.
Use the ISP network appendix to locate relevant developments such as Marinus Link, VNI West and HumeLink, and read generation/storage assumptions for Snowy 2.0 separately. A name in an appendix is not evidence that every component is commissioned; maintain a dated project register.
06Produce a reviewable planning brief
Choose one network development from the 2026 ISP. Create a four-column evidence table: system need, assumed timing/capability, independent project evidence, and unresolved dependency. Cite the exact appendix, table or figure rather than only the landing page.
Prepare a base case and a delay case. Recalculate one clearly bounded economic measure and describe one operational consequence. Mark actual published values separately from invented sensitivity inputs. If a source conflicts, preserve both dates and explain which evidence controls your decision.
Submit a one-page recommendation with a trigger for review: a revised ISP assumption, changed approval, cost estimate, construction milestone or adequacy outlook. This is the bridge to Topic 40's investment appraisal, not a substitute for that specialist work.