Reports: building and scheduling a report
Monitoring & Control β Reports β + β choose a template
The editor has five tabs down the left β General, Style, Columns, Schedule and Reminders β with Save and Close in the footer. Working through them in order takes a couple of minutes and the report then runs by itself.
General β what the report covers
- Report Name β what recipients will see. Include the audience or portfolio; "Monthly β Northside PPA" beats "Report 4".
- Folder β where it lives in the library, or root level.
- Period β the reporting period. The template tells you which ones it supports (for example Daily, Weekly, Monthly, Yearly).
- Report Language β the output language, independent of your own interface language. Set it per audience.
- Assignment β Assign Systems From: Custom (pick systems by hand), Groups (a system group) or Customers (everything belonging to a customer).
Prefer Groups or Customers over Custom wherever you can: the report then follows the portfolio automatically as sites are added or sold, instead of quietly going out of date.
Style β how it looks
- Header Background, Footer Background, Header Alignment, Logo Width β the branding.
- Cover page β None, Custom or PDF (supply your own cover).
- System Address in Header β include the site's address.
- Hide Alerts Icons β remove the operational alert markers from a document meant for owners.
- Show Expected β include the expected figures next to actuals so variance is visible.
- Hide Revenue β leave money out of a purely technical report.
- Hide Normalized β drop the normalised columns for a less technical audience.
- Environment Contribution β add the COβ and trees-equivalent section that owners and marketing teams like.
- Additional Components β extra sections the template supports.
- AI Executive Summary β prepend a written summary of the period generated from the report's own data. Useful for busy recipients; read it before the first send so you are comfortable with the tone.
Columns β what it carries
The same metric catalogue as the fleet table: production, revenue, meter figures, PR variants, availability, irradiation, weather-adjusted energy, data-quality checks and more, plus Completeness, which tells the reader how much of the period actually had data β the column that stops an incomplete month being read as a bad month.
Keep the set short. A report with fifteen columns is usually one nobody reads; three or four well-chosen ones travel much further.
Schedule β when it goes out
- Active β the switch that makes it automatic.
- Timezone and Hour β when it is generated and sent. Pick an hour after the previous period's data has landed; early-morning sends can catch an incomplete final day.
- Recipients β who receives it.
Reminders
A reminder attached to the report itself, with its own recipients and schedule β for the human tasks around it, such as reviewing a draft invoice report before the billing run.
Common tasks
Owner report in five minutes. Template: PV Periodic β General: name, Monthly, Assignment by Customer β Style: Show Expected on, Environment Contribution on β Columns: production, expected, actual vs expected, PR β Schedule: Active, 08:00 local, recipients β Save.
Internal triage report. Template: Least Performed Systems β weekly β columns focused on PR and availability β recipients: the operations list.
Report an owner can read. Hide Normalized, Hide Alerts Icons, keep four columns, and turn on the AI Executive Summary.
Check before it goes live. Save with Schedule inactive, generate once, read it, then activate.
Common questions
Recipients did not get it.
Check Active on the Schedule tab and the recipient list, then Reports Archive to see whether it generated at all.
The report shows fewer systems than expected.
Assignment is probably Custom and the newer sites were never added. Switch to Groups or Customers.
Numbers differ from the portal.
Compare periods and timezone first β a report generated at 05:00 for "yesterday" can include a partial final interval. The Completeness column makes this visible.