Available data
The assistant can answer only from the data in this table. Each person sees only the Plants that their account can access.
Levels and resolutions
| Level | Data | Resolution | Time range in one question | Tool |
|---|---|---|---|---|
| Portfolio | Operation Overview table of each Plant | One row for each Plant for one day | One day | get_portfolio_dashboard (site_overview) |
| Portfolio | Yield for the last 7 days | Daily | 7 days | get_portfolio_dashboard (last_7_days_yield) |
| Portfolio | Device status and string health summary | Current status | Now | get_portfolio_dashboard (devices_status_summary, string_health) |
| Portfolio | Alarm status, as on the Operation Overview screen | Alarms in the time range | Up to 92 days | get_portfolio_dashboard (alarm_status) |
| Plant | Yield, PR, availability, irradiation | Daily | Up to 366 days | get_plant_daily_performance |
| Plant | Stored DataHub Plant metric values | 5 minutes, as stored | Up to 31 days, but 1,000 rows allow about 3 days for one metric or 1 day for 3 metrics | query_plant_5min |
| Plant | Other stored daily values, including curtailment, soiling, revenue, temperature-corrected PR, and monthly values | Daily, as stored | Up to 366 days, maximum 1,000 rows | query_plant_daily |
| Plant | Power, yield, and performance charts | 1, 5, 15, 30, or 60 minutes | One day | get_plant_chart |
| Plant | Live production and device communication status | Current status | Now | get_plant_dashboard |
| Plant | Disconnected strings | Current status | Now | get_plant_dashboard (disconnected_strings) |
| Plant | Active alarms, alarm history, and details | Current alarm state and lifecycle times | The selected range filters alarm creation time; ten alarms per page | list_alarms, get_alarm |
| Device | Device IDs, names, types, parents, labels, and attributes | Not time-based | Not applicable | list_devices |
| Device | Named device telemetry (exact, case-sensitive keys) | 1, 5, 15, 30, or 60 minutes | One day, one device, up to 10 metrics | query_device_telemetry |
| Inverter | Daily yield, availability, derating loss, operation time, and unavailability, overspill, and soiling loss | Daily | Up to 366 days, all inverters or selected inverters | query_inverter_daily |
| String | String analytics, as on the String Analytics screen (for example average current and normalized power) | One record for each string for each day | One day for each question | get_string_daily_analytics |
| String | Stored current (Idc) and voltage (Udc) of each string | 5, 15, 30, or 60 minutes | Up to 7 days, from approximately the last 72 days | query_string_5min |
Resolution and size
| Data | Use it for | Limit |
|---|---|---|
| Daily values | Candidates for an investigation. They do not show when a fault started. | One data point for each Plant, device, or string for each day |
| Plant time series | Stored values as they are | 1,000 rows in one answer. Select metric keys from the tool schema. |
| Chart and device telemetry | The shape of a day | Up to 288 data points for each metric for each day at 5 minutes |
| String analytics | Processed daily values | One record for each string for each day |
| String current and voltage | Weak strings | 1,000 records in one answer. A Plant with 114 strings gives about 16,500 records for one day at 5 minutes. |
For string current and voltage, start with one inverter at 15 or 60 minutes. Then ask for 5 minutes for a short time range. If a question needs more than 1,000 records, the assistant tells you to make it smaller.
Example questions
Show the stored 5-minute power and irradiance at [Plant name] from [start time] to [end time] on [date]. Tell me which values are missing.
Show daily yield, PR, and availability at [Plant name] from [start date] to [end date]. State the timezone and tell me which days have missing values.
Show [Plant name] power and irradiance on [date] at 5-minute intervals.
Analyze the string analytics of [Plant name] for [date]. List the weakest strings and tell me how many records you used.
Compare the string analytics of [Plant name] for [date], [date], and [date]. Tell me which weak strings stay weak on all three days.
For a comparison over many days, ask for each day by name. The assistant reads string analytics one day at a time.
Show the current and voltage of the strings of [inverter] at [Plant name] on [date] at 15-minute resolution. Tell me which strings have low current. Then show those strings at 5-minute resolution from [start time] to [end time].
Show daily yield, availability, and soiling loss of each inverter at [Plant name] from [start date] to [end date]. Tell me which inverter has the lowest yield.
Not available
- String current and voltage older than approximately 72 days.
- Inverter loss values at a resolution of less than one day.
- Work orders.
- Month and year charts, heat maps, the loss waterfall, and insights charts.
- DataHub metric values for devices other than the stored string and inverter values above.
Read the answer
- A missing value is not zero. For device telemetry, an empty series can also mean a wrong metric key. The assistant states the key that it used.
- Daily and processed values do not prove a hardware fault. Confirm with a site check or higher-resolution data.
- A clock time with no zone is Plant time. If you name a zone, such as SG (UTC+8), the assistant states both times.
- Device telemetry covers one Plant day.