Skip to main content
Docs / Project Modelling
Docs Menu

Saved Reports and Templates

Generate repeatable reports from completed saved runs. Reuse a saved configuration or pin a private DOCX template version.

Generate a report

  1. Save and run a case. Open Project Modelling → Results → Report.
  2. Under Saved reports, check Selected run. Unsaved changes are not report inputs.
  3. Enter Report title and, if needed, Company name.
  4. Choose Report formats: JSON, CSV, XLSX, PDF or DOCX. DOCX requires a selected immutable template version.
  5. Leave filters empty for all available data. To filter Columns or Year indices, first select exactly one entry in Tables.
  6. Select Generate report. Review its status in History for selected run.
Saved report title, formats and result filters
Report inputs identify a saved run, selected formats and optional result filters.
Filters select result cells, not confidential information. Every delivery includes an evidence ZIP with the full saved input assumptions and source warnings. Review that ZIP before sharing. Model year indices are 0–200, not calendar years.

Preview and download

  1. In the completed history entry, choose Preview beside a supported artifact.
  2. Read the preview in the browser. Use Close preview when finished.
  3. Select the artifact’s Download button for the file. A Download only label means there is no inline preview.
Inline JSON report preview for a saved screening run
The JSON preview shows saved year-one values, not new calculations from draft edits.

Preview support depends on file type and size. ZIP and DOCX artifacts are download-only. If the browser cannot display a PDF, use its download button. A preview is not a separate saved report.

Reuse or regenerate a saved configuration

  1. Open the required entry in History for selected run.
  2. Read Saved configuration and the run, revision and configuration digest.
  3. Select Reuse configuration to put the saved settings back into the form. Review them before generating.
  4. Select Regenerate saved configuration to create another export from the saved configuration.
  5. Use Refresh history to reload outcomes. The history view lists the latest 100 exports for the selected run.
Completed report history with reuse, regenerate and download controls
Completed records keep their own configuration digest, artifact list and outcome.

Upload a private DOCX template

  1. Create a DOCX file with literal placeholders from the list below.
  2. Expand Private DOCX templates. Enter Template name and choose DOCX template file.
  3. Select Upload new template.
  4. Choose the exact Template and Template version. Review its SHA-256 and detected placeholders.
  5. Select DOCX in Report formats, then Generate report.
Private DOCX template version 1 and its supported placeholders
Version 1 of the example template contains four supported placeholders.

Supported placeholders are {{title}}, {{company_name}}, {{run_id}}, {{revision_id}}, {{spec_digest}}, {{generated_at}} and {{result_summary}}. Include {{result_summary}} to show selected data and estimate warnings. No formulas or loops are evaluated.

The upload limit is 5 MiB. Embedded PNG/JPEG branding is retained. Macros, links, fields and embedded objects are rejected. Templates are private to your account.

For later use, select Load templates. To revise a selected template, choose another file and select Upload new template version. Existing versions stay unchanged. Download selected template retrieves the pinned source file.

Worked example: a saved screening report

We generated November screening example from saved run 6b59870c6134437bbef17028405f7366. It used a modelled 20-year quick solar screening case in AUD. Its first-year saved values included revenue and savings 149,250 AUD, operating cost 5,000 AUD and net cash flow 144,250 AUD.

The JSON export completed with an 18,731-byte JSON file, a 15,426-byte evidence ZIP and an export-binding.json file. We uploaded Screening summary template version 1 with these four placeholders:

{{title}}
{{company_name}}
Run {{run_id}}
{{result_summary}}

Generating with that version added a 3,039-byte DOCX artifact. Reuse and regeneration kept the saved run and configuration references. These sizes describe this example only; report sizes vary with the inputs and selected formats.

Export a site or participant allocation

  1. Under Site, participant and calendar-year scope, select Load financial scope.
  2. Select the required Sites or Participants. These come from the saved run’s allocation, not the current draft.
  3. Review Scoped cashflows and any column or model-year filters. Select Generate report.
  4. Check the site and participant scope in the completed history entry.
Financial report scope
Select the stored allocation to export. Unassigned is an explicit remainder.
A financial scope exports allocated cash-flow rows only. It does not filter energy tables or recalculate whole-run totals. Calendar-year selection needs explicit stored dates and a valid source timezone. Model-year numbers are not dates. These filters are not access controls: the accompanying evidence ZIP still contains the full saved inputs.

In our one-year example, selecting operator produced a completed JSON report of 8,396 bytes. Its history states Participant scope: operator. The file size is specific to this example.

Completed operator report
The completed record preserves the selected participant and configuration digest.

Batch reports by allocation

  1. Expand Batch selected run variations and select Load saved runs.
  2. Select completed runs from the current case. Each run stays separate.
  3. Select Separate report per stored site or Separate report per allocated participant as needed. Clear unrelated table and column filters. Current site and participant filters narrow the split.
  4. Optionally select a template version and choose Add selected template to batch.
  5. Select Generate selected runs. Check each outcome, not just the batch message.

Our example selected one saved run and the participant split. It produced three completed reports: operator, owner and Unassigned. The last record preserves the source reconciliation remainder; it is not another participant’s income.

Participant report batch
Each allocation receives its own report and saved scope.

A batch accepts up to 10 completed runs and up to 5 pinned template versions, with at most 20 report outcomes including allocation splits. Invalid scopes and larger batches are rejected before report creation. Different runs and currencies are never combined.

Before sharing

  • Check that the report uses the intended run and revision.
  • Read engineering status, missing values and source warnings.
  • Keep the report’s modelled scope and engineering status with its conclusions.
  • Inspect all attachments, especially the full-assumptions evidence ZIP.

Export energy across model years

  1. Open Results → Report → Saved reports for the completed run.
  2. Set Scoped data to Annual energy (all model years and variations). Select Load financial scope.
  3. Choose Energy variations. Select Annual model energy in Tables, then choose Year indices and Columns. Empty filters include all available rows.
  4. Choose the format and select Generate report. Check the saved configuration, then preview or download the artifact.
Model years 1, 2 and 10 were selected. These are indices, not calendar dates.
Model years 1, 2 and 10 were selected. These are indices, not calendar dates.

Worked example: six selected rows from a ten-year case

We exported the saved joint-dispatch run 97b268c67196466482287c602a87771a. It retained one variation, assets[0].capacityKw=2, and ten model years. We selected years 1, 2 and 10, with Year, Variation, Participant ID, Generation (kWh), Export (kWh) and Basis columns.

The JSON report completed at 3,792 bytes. It exported 6 rows from 20 available participant-year rows. The saved energy-kwh shares were 60% for the site host and 40% for the battery owner:

Model yearHost generation (kWh)Owner generation (kWh)
12,6281,752
22,6281,752
102,6281,752

Each year reconciles to the saved 4,380 kWh generation estimate. Every row retained: “Saved model annual estimates; later years may repeat or extrapolate the supplied profile. Not measured energy.” Repeated values are not evidence of future physical delivery.

The JSON preview shows the row count, allocation and model-estimate basis.
The JSON preview shows the row count, allocation and model-estimate basis.
Alternative variations are separate and must not be added together. Load, generation and bus-flow columns overlap; do not sum them as one energy total. Each column uses only the explicit energy-kwh allocation and its unassigned remainder. Missing values stay unavailable with reasons. Older runs cannot supply alternatives they never saved. Calendar-year filtering needs verified stored dates; annual model-year numbers do not provide them. Use Energy paths (first simulated year) for the separate dated path export. No future interval trace is invented from annual totals.
Engineering Studies reports are separate. For a chart report from a workflow run, see Projects and Flows. For a study presentation, see Engineering Exports and Handoffs.

Related Guides

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