Check whether your data is ready

Why data readiness matters

Vega can analyze only the data available in the active account. A polished answer or chart can still be misleading if it uses the wrong meter, an incomplete period, a failed document index, or duplicated assets.

Run the checks in this guide before invoice reconciliation, site comparisons, investment analysis, or any decision that depends on exact values.

Step 1: Confirm account and scope

1. Check the active account name in the top-right corner.
2. Open Inventory.
3. Search for the intended site.
4. Confirm its name, country, address, owner, and tags.
5. Open the site and identify the components required for the analysis.
6. Check that each component belongs to the correct site.

Write down the intended scope: site, components, metric, direction, and date range. This becomes the basis for checking completeness.

Step 2: Check inventory health

1. Review the site’s Health value in the Inventory list.
2. Open the site and select Health.
3. Read the status summary.
4. Follow links to affected components.
5. Select Ask AI when you need an explanation of the status. Vega opens the contextual conversation beside the Health page, so you can inspect the source status while asking follow-up questions.
6. Open each important component’s Health tab.

A health warning does not always invalidate all data. Determine which component, period, or capability is affected.

Closing the contextual conversation does not delete it. If you want more room, use the panel action to open that conversation as a full-page chat.

Step 3: Check synchronization

1. Open the site.
2. Select Sync.
3. Review the latest site and component synchronization jobs.
4. Look for failures, jobs still running, or an unexpectedly old last update.
5. If authentication fails, update the connection from the component’s Settings using Replace connector credentials.
6. Refresh the synchronization status.
7. Trigger synchronization only if that action is part of your normal responsibility.
8. Wait for synchronization to finish before checking measurements again.

For a newly connected source, historical data may continue arriving after the component first appears.

Step 4: Inspect measurements

For every component used in the analysis:

1. Open the component.
2. Select Measurements.
3. Choose the required date range.
4. Confirm that values exist from the beginning through the end of the period.
5. Check the interval and unit.
6. Identify gaps, flat lines, duplicated patterns, or unexpected zeros.
7. Confirm whether the series represents consumption, production, power, energy, or another metric.
8. Compare a small sample with the source platform or a trusted record.

Use complete periods when comparing. For example, compare full calendar months rather than an unfinished current month with a complete previous month.

Step 5: Check invoices

If the analysis uses invoices, review Upload and manage energy invoices first:

1. Open the relevant metering component.
2. Select Invoices.
3. Confirm that the required billing periods are present.
4. Expand the invoices and check supply point, meter number, billing dates, and units.
5. Open the source files and verify important totals.
6. Check for duplicate or overlapping billing periods.
7. Confirm that invoice dates align with the measurement range.

Invoice periods do not always follow calendar months. Use the exact start and end dates shown on the invoice.

Step 6: Check reference documents

If the question relies on a contract, audit, or spreadsheet, review Add and manage reference documents first:

1. Open Documents.
2. Search for the expected file.
3. Confirm that it is the correct version.
4. Check that indexing status is Done.
5. Open or preview the file and confirm that the relevant section is readable.
6. Reindex or replace the file if its status is pending or failed.

Do not assume that a file is searchable merely because it appears in the list.

Step 7: Check solar configuration

For solar performance analysis, verify the properties described in Connect a solar power plant:

• installed peak power,
• system loss assumption,
• tilt and azimuth,
• site coordinates,
• production series and units,
• array or inverter hierarchy, and
• the period covered by synchronization.

Incorrect orientation or capacity can make a healthy plant appear to underperform against a benchmark.

If the question uses an operational PV forecast, also open the component’s PV Forecast tab and confirm that the requested date has a value, an issuance time, and no inconsistent-input warning. Current forecasts normally cover the site’s local day through D+2; a configured PV installation can still be ineligible when site coordinates, tilt, azimuth, direct connector support, or weather synchronization are missing. Follow Use and interpret PV forecasts for the complete check.

Step 8: Test the scope in Chat

Use the site and asset selector, then ask Vega a narrow validation question before the full analysis:

For the selected site and components, list the measurement series, units, earliest available timestamp, latest available timestamp, and any gaps during the requested period.

Then ask:

State exactly which sites, components, invoices, and documents you would use for this analysis.

Compare the response with your checklist. Correct the scope before asking for conclusions, and follow Verify Vega’s answers before acting when reviewing the result.

Data-readiness checklist

Proceed when all relevant statements are true:

• The correct account is active.
• Sites and components are assigned correctly.
• Required connectors are healthy.
• Synchronization is current.
• The date range has sufficient measurement coverage.
• Metrics, units, and directions are understood.
• Invoice periods and meter identifiers match.
• Required documents are the correct versions and indexed.
• Solar configuration is complete when relevant.
• The required PV forecast exists, is coherent, and covers the requested date when relevant.
• Vega confirms the intended analytical scope.

What to do when data is not ready

Do not hide missing data by shortening or changing the question without noting it.

Instead:

1. Record the affected site, component, series, and period.
2. Check health and synchronization details.
3. Correct inventory or configuration information you are authorized to maintain.
4. Replace unreadable invoice or document files.
5. Contact the data owner or support team for access, connector, or persistent processing problems.
6. Repeat the readiness check after the correction.
7. Clearly state any remaining limitation in the final analysis.

A result with a documented limitation can still be useful. A result that silently assumes complete data is much harder to trust.