Table of Contents
To read iSolarCloud usefully at a business, start with three checks: confirm the plant, establish how recent the data is, and identify what each measurement covers. Then compare generation, grid imports, exports and consumption over the same period. If something looks wrong, save the time, curve and device message. This turns monitoring into evidence for a decision.
This workflow is for an owner or responsible operator of a commercial solar plant in Ukraine. Available screens depend on the plant type, connected equipment, account permissions and software version. Access to iSolarCloud does not, by itself, establish that every measurement or control function is available at your site.
Confirm the plant, server and time
At handover, record the plant name, owner account, inverter models, communication device and support contact. Ukraine is included in the European server region. When signing in, select the server used to register the account. If the plant disappears from your list, check these details with the installer before creating another plant.
Before analysing a problem, check the date, time zone and timestamps of the available measurements. A screenshot without time is difficult to compare with a production shift or outage log. Record when you made the observation separately: at 12:20, you might be looking at a last available reading from 12:10.
This guide reflects web platform capabilities checked in October 2026. The app can arrange controls differently. Ask for a demonstration using your own account. The Sungrow equipment page provides product context; establish the installed model and version from the site's records.
During handover, review one completed day with the installer: find generation, inspect a device, review events and export data. Record the relevant sections in the business's operating instructions. This exposes missing permissions or measurements needed for monthly reporting before an incident occurs.
Separate power, energy and status
Power in kW describes the rate of production or consumption at a moment or over an interval. Energy in kWh describes the quantity over a period. A reading of 60 kW at noon does not mean 60 kWh was produced that day. If 60 kW were maintained for one hour, the corresponding energy would be 60 kWh.
Read flow directions together with the measurement names. Do not identify grid imports or exports from a curve's colour alone. Check the legend and sign convention in the particular report. Use this short reading guide:
| Measurement | Operator's question | Limit of the conclusion |
|---|---|---|
| PV power, kW | Which device and timestamp? | Not the day's energy total |
| Generation, kWh | When does the period begin and end? | Not necessarily all consumed on site |
| Imports and exports | Where is the measurement taken? | One feeder may not represent the whole business |
| Device status | When was it last updated? | Status alone cannot establish production performance |
For a battery, distinguish state of charge, expressed as a percentage, from charging or discharging power. A percentage cannot be added to an energy balance. Storage changes the calculation even when the operator's immediate question concerns solar generation.
Identify the metering boundary
An inverter's generation data does not describe every load at the business. Establishing exchange with the grid requires suitable measurement at the agreed connection point. The web platform's demand analysis is unavailable without a meter. Check other readings against the actual electrical arrangement rather than assuming a building icon represents the whole site.
Ask the installer to mark each measurement boundary on the single-line diagram. Does it include the warehouse, charging points and neighbouring building? Is another inverter, generator or battery present? Without those answers, a convincing balance may describe only part of the business.
If consumption becomes implausible after a wiring change, give support the change date and affected connections. A qualified specialist should verify measurement locations, directions and scaling. The operator should not move current transformers or open electrical panels to make the chart look right.
Check one interval with an energy balance
Consider a hypothetical hour: PV generation on the AC side is 60 kWh, grid imports are 40 kWh, and grid exports are 10 kWh. Assume no battery or generator, matching measurement boundaries and synchronised time. Losses are not modelled separately. These are teaching inputs, not results from an actual installation.
- Solar energy used on site: 60 - 10 = 50 kWh.
- Site consumption from the balance: 60 + 40 - 10 = 90 kWh.
- Share of solar generation used on site: 50 / 60 × 100 ≈ 83.3%.
- Share of consumption supplied by solar: 50 / 90 × 100 ≈ 55.6%.
The percentages answer different questions. The first describes where the solar output went; the second describes solar's contribution to the business's demand. A high first percentage can coexist with substantial grid purchases. Consider both when investigating whether to shift a production process.
With storage, charging and discharging must be included, and identifying the origin of battery output requires additional accounting. Do not carry this simple formula into a mixed system without checking the arrangement. Similarly, do not replace a missing reading with zero merely to complete the balance.
Compare like with like
Start with a daily curve, then examine the suspect period more closely. Select the device, measurement and available interval. Record those choices in your analysis notes. A monthly total shows production scale but can conceal short interruptions or missing communications.
When comparing inverters, account for connected module capacity, orientation, shading and operating limits. Different roofs need not produce identical curves. First compare a device with its own history under similar conditions; then look for simultaneous changes elsewhere.
For differences between specific model specifications, see the Sungrow SG110CX and SG125CX-P2 comparison.
Connect observations to the site log: shift start, production shutdown, maintenance or a grid outage. A production drop occurring at the same time as another event is a reason to investigate, rather than proof of causation. Keep the observation, such as reduced output, separate from a suspected explanation.
Use matching intervals. Hourly average power can conceal a brief peak or dip visible in finer data. Request the available detail appropriate to the task, but do not invent what happened between recorded points. State the limits of the available resolution in the management conclusion.
Distinguish missing data from faults
A blank part of a curve does not establish zero production. Check which devices stopped reporting, when the gap began and whether it coincided with an internet change or loss of power to communication equipment. Ask the responsible site employee to establish the plant's actual condition under the site's procedure.
Do not promise that every historical reading will return after communications resume. Recovery depends on the device and circumstances. Mark the period as incomplete, retain the available records and ask support what can be recovered. Keep the gap visible until it has been resolved.
For a fault message, retain the exact code, device name, occurrence time and current state. Recurrence after the message disappears also matters. Follow the equipment instructions and agreed service process for the response. A cleared message does not close an investigation if output remains unusual or the event keeps returning.
If thermal imaging is part of the agreed investigation, review what a solar PV thermal inspection report should include.
Keep a report with its explanation
The web platform provides exports of available data and reports. Before exporting, check the plant, period, measurements and units. Include the site, reporting period and download date in the local filename. Preserve the original export separately from a spreadsheet used for your own calculations.
For the monthly review, add a short note covering data completeness, known interruptions, equipment changes and unresolved questions. Align the period with the business's accounting records. If daily values do not add up as expected, investigate filters, gaps and the definition of the metric first.
For a performance conclusion, compare forecast and actual solar generation after accounting for weather and operating events.
Consider monetary estimates separately from physical generation. A management conclusion requires agreed price inputs and calculation rules. A displayed figure cannot replace checking bills and contracts. Keep confirmed kWh separate from an economic estimate that has not yet been reconciled.
Assign a report recipient and an owner for each unresolved issue. Record the next action and expected evidence, such as a service explanation or revised export. Retain both versions when figures change, with an explanation, so decisions remain traceable through changes of staff.
Grant access for a defined task
Web plant sharing distinguishes viewing data from administration that includes configuring plant operation. Begin with viewing rights when somebody needs to review a report. Agree broader permissions for a specific job with the responsible person at the business.
Do not make sharing the owner's password the routine support method. Agree a separate user, required permissions and when access should be reviewed or removed. Check remaining access after changing contractors. Handle protection settings, operating changes and firmware updates through a separately agreed procedure.
Prepare an actionable support request
A useful request states what you expected, what happened, when it happened and what was already checked. Instead of “the plant is performing badly”, write: “one inverter stopped updating after 11:10, the others still report; the router was changed at 10:50”. This is another hypothetical example showing the necessary precision.
- Plant name, responsible contact, affected model and serial number.
- Date, time zone, start time and duration of the deviation.
- Exact message code, screenshot with its legend and available export.
- Recent changes to communications, wiring, equipment or production schedule.
- The requested outcome and agreed access to the plant.
Send serial numbers and site information through the agreed support channel. After receiving a response, record the conclusion, actions and verification of the result. Bring this package when discussing solar plant maintenance, so monitoring, diagnostics and response times can be agreed for the actual plant and service contract.