Skip to main content
Docs / Project Modelling
Docs Menu

Site Scenarios and Saved Results

Keep a protected baseline for each site, test alternative scenarios in one case, edit their assets in a spreadsheet, and publish or archive the saved results in Project Modelling.

Create a site

  1. Open a Detailed Engineering Case and go to Design.
  2. Under Site and scenario, open Create site context.
  3. Enter a Site ID and a Site name.
  4. Select Create site from current draft.
Site and scenario panel with site ID site-north and site name North depot
The current draft becomes the protected baseline for North depot. An editable scenario called Initial alternative is created from it.

The baseline is protected. You edit the scenarios, not the baseline. One Site and Scenario selection controls Design, Value and Options. Changes stay in the case draft until you save.

Clone a scenario

  1. Choose the Scenario to copy.
  2. Enter a New scenario name.
  3. Select Clone selected scenario. To start again from the baseline, select Clone protected baseline.
  4. Change the new scenario, then select Save case revision.
Site and scenario panel after cloning the Larger battery scenario
The new Larger battery scenario is selected. Use Add site from current scenario to add another site.
Each site runs separately. A set of sites is not a combined electrical network.

Edit assets in the multisite spreadsheet

  1. Under Multisite asset spreadsheet, choose the scenario for each site.
  2. Select Edit selected scenarios.
  3. Change Generation kW, Storage kW, Storage kWh or Load annual kWh. You can also add or remove rows, or paste tab-separated rows.
  4. Select Validate and apply rows to case draft.
  5. Select Save case revision.
Multisite asset spreadsheet with a 2 kW, 4 kWh battery row
Two asset rows for scenario-2. The battery is set to 2 kW and 4 kWh. Baselines are never edited.

A blank cell means absent, not zero. Other design and cost fields stay the same. New rows use the model defaults, including zero costs, until you enter costs in Design.

While rows are loaded, you cannot change the scenario selection. Apply or discard the edits first with Validate and apply rows to case draft or Discard edits and reload rows.

Worked example: two battery sizes at one site

Site North depot has 8,760 kWh of annual load and a 2 kW solar array (4,380 kWh a year). The 10-year case uses a 10 kW import and export limit. Both scenarios have a total capex of A$1,800. We ran each scenario with Run and read Results.

ResultInitial alternative (1 kW, 2 kWh)Larger battery (2 kW, 4 kWh)
NPVA$3,374A$3,900
IRR41.51%46.13%
Discounted payback2.69 years2.42 years
First-year revenue and savingsA$801A$879
Annual onsite use2,675.98 kWh3,161.93 kWh
Annual import6,084.02 kWh5,598.07 kWh
Annual export1,651.86 kWh1,113.76 kWh
Self-sufficiency30.55%36.1%

The larger battery stores more solar for later use. Import falls by 485.95 kWh and export falls by 538.1 kWh. Both runs had the engineering gate review, so neither is a final feasibility answer.

Publish, archive and restore a saved result

  1. Go to Results → Saved result lifecycle. Each completed run of the case is listed with its revision.
  2. Select Publish result to mark a result for project use.
  3. Select Archive result to hide it from the default list.
  4. Tick Include archived results to show archived runs again.
  5. Select Restore and publish to bring an archived result back as published.
  6. Select Return to draft to remove the published status.
Saved result lifecycle showing a published run
Run 4e05652da177430ea775116ced82c5cb is published. Its stored result checksum stays with the run.
Saved result lifecycle after archiving, with no saved results in this view
After archiving, the default view shows "No saved results in this view".
Saved result lifecycle with archived results included and the run published again
With Include archived results ticked, Restore and publish returned the same run and revision to published.

Each action shows the message "The saved result was not recomputed or deleted." Restore keeps the same revision and the same result. A failed run shows "A completed stored result is required." and cannot be published.

To make a PDF or DOCX report from a saved run, see Saved Reports and Templates.

Publishing makes the saved result available inside your project. Existing access permissions and inputs stay unchanged.

Limits

  • Each site is modelled on its own. Sites do not share a connection or a network.
  • The spreadsheet changes only power, energy and annual load values. Check costs and other fields in Design.
  • Unsaved changes, such as applied rows or applied sizes, are lost if you reopen the case from Case history before saving.

Related Guides

Can't find what you need? Email support@networkmap.energy or call 1300 936 116. Sign in to Network Map.