How to Monitor Factory Solar Performance
Check generation, faults and actual bill savings separately
Quick links
Monitoring helps protect the value of a solar investment by showing whether the system is producing as expected and when a problem needs attention. Access to a dashboard is only the starting point: the information becomes useful when someone can interpret a change and get it investigated. The process should connect facilities staff, the service team and finance rather than leave each to read the same screen differently.
Agree what is being measured
Monitoring needs to distinguish electricity produced from electricity saved on the bill. Generation records output, direct consumption is the portion used on site, and imports and exports are electricity crossing the meter. A change in one does not always mean the others changed in the same way, which is why a single dashboard total cannot answer every performance question.
A factory may generate normally but receive a different bill because production, tariffs or the share of direct consumption changed. Monitoring should therefore be reviewed alongside utility records and operating information.
Ask the provider which measurements are available from the selected equipment and which values are estimated. A savings display may rely on assumptions about rates and consumption. Finance should understand those assumptions before using the display as an accounting result.
Keep output records from normal operation
A history of normal operation gives later readings something to be compared with. Daily and monthly records, alongside weather, shutdowns and known faults, help the service team judge whether a dip is temporary or part of a recurring pattern. Without that history, an isolated low figure is harder to interpret reliably.
Use the proposal’s generation estimate as a reference, while remembering that an annual forecast is not a promise of identical monthly output. Compare similar periods where possible and explain major changes in the operation.
The facilities team should know what a typical generation curve looks like and where equipment status is shown. That familiarity makes an unusual pattern easier to spot than relying on a manager who opens the platform only when the bill looks high.
Check data quality before drawing conclusions
Before treating a flat chart as lost generation, it is important to know whether the platform is receiving data. A communications gap can make an operating system appear inactive, leading to the wrong diagnosis if the display is taken at face value. Checking record completeness is therefore part of performance review, not just an IT task.
Do not ask unqualified staff to open equipment or change settings. Use the agreed support route for technical checks.
Record when communications were lost and restored. If the platform fills missing data later, distinguish restored records from an actual recovery in output. A sound monitoring process considers the measurement system as well as the solar equipment, particularly when reports support financial or contractual decisions.
Account for weather and operating changes
Lower output can result from weather, dirt, new shading, equipment faults or controls limiting generation. Ask the service team to check the likely causes. Do not accept weather as the explanation for a persistent decline without supporting evidence.
Where appropriate measurements exist, technical teams may compare output relative to resource conditions or use performance indicators that account for system size. Ask the provider which method is suitable for the installation.
Do not compare total output from factories with different system sizes or locations without adjusting for those differences. Ask the provider which measure it uses and what a change in that measure means for your own installation.
Define who receives alarms
An alarm only leads to action if it reaches someone responsible for responding. The inverter or platform may report an event, but who receives it and what happens next depend on the service arrangement. Establishing those responsibilities avoids assuming that an available alert means a provider is monitoring it continuously.
Name the factory contact and provider service contact. Agree who receives urgent alerts, who can arrange access and who confirms that work is complete. Add a second contact or handover arrangement for staff absences.
Verdant Solar’s commercial material describes remote performance and fault monitoring and review of operating trends. The exact frequency, platform and service commitment should be confirmed in the project’s O&M scope. Ask who receives alerts, who reviews the information and how you can access the records when the facilities team needs them.
Link monitoring to maintenance
Remote information can show that something changed without explaining everything that caused it. Some conditions require inspection or manufacturer-specified servicing by qualified personnel. Monitoring and maintenance therefore support one another: data can direct a visit, while inspection findings can explain a pattern the dashboard alone could not resolve.
Keep maintenance records alongside the performance history. Cleaning dates, equipment replacements, inspections and configuration changes can explain later differences in output.
When arranging a visit, provide the relevant period, alarms and observations in advance. This can make the investigation more targeted. A service report should state what was found, what was done and whether any follow-up remains with the customer or provider.
Give finance a monthly output and savings report
Management needs to understand whether a change in generation affected the business, not simply whether the chart rose or fell. A monthly report can connect actual output, the relevant forecast, missing data and major events with actions taken. Finance can then review electricity savings using the bill and consumption records rather than assume output and financial benefit are interchangeable.
Include measured direct use and exports where those records are available. Check bill savings using the TNB account and programme terms. Do not value every generated unit at one assumed rate if directly used and exported electricity have different financial values.
Retain the original forecast and any approved revisions. When comparing actual results, identify which version is being used and why. Do not change the expected result without recording the reason, such as a confirmed change in working hours.
Check performance against the actual contract
An annual estimate, an equipment output warranty and a project performance guarantee are different commitments. The monitoring data should not be interpreted as triggering a remedy unless the relevant agreement supports that conclusion.
For a suspected shortfall, collect the approved forecast, operating records and relevant event history. Ask the provider to explain the variance and the next action.
Investigate faults and arrange corrective work through the service process. If you also believe a contract commitment has not been met, check its measurement method, conditions and remedy separately. A low reading alone does not establish a claim.
Agree who reviews reports and follows up
A review process needs to be easy enough for the responsible team to maintain. One named owner, retained platform access and an agreed reporting interval give the business continuity when staff or service contacts change. Recording significant issues and follow-up is more useful than collecting readings without deciding who acts on them.
Verdant Solar’s commercial materials describe monitoring and maintenance. Ask which activities your offer includes, who investigates alerts and how findings lead to a service visit. Confirm the reporting and charges in the proposal before handover.
Use a simple monthly exception report
A monthly report can stay short. List the same items each time, and give each outstanding action an owner and next review date.
- Expected output.
- Actual output.
- Missing records.
- Known events.
- Unresolved faults.
Managers should be able to see what needs attention without searching through the monitoring platform.
If the cause is still unknown, mark it as under investigation. When resolved, add the service record and the result of follow-up checks. Keeping these records together helps the team recognise recurring faults and review service performance without reconstructing events from emails.