Type something to search...

Asking Vega and investigating energy performance

Verify Vega's answers before acting

Check included data, evidence, sources, and assumptions before acting on an insight.
Table of contents
  1. Check the scope
  2. Look at the evidence
  3. Read the response metadata
  4. Check warnings and non-verdicts
  5. Separate observations from recommendations
  6. Copy and review a result
  7. Continue the investigation

Check the scope

Before using an answer, confirm that it covers the site, assets, and dates you intended. A technically correct result can still be misleading when the scope is different from your question.

Ask Vega to state:

  • the site and component references,
  • measurement definitions and units,
  • exact start and end timestamps with time zone,
  • aggregation interval and statistic,
  • invoice or document identifiers, and
  • data coverage and warnings.

Compare those details with the @ references in your question and the records in Inventory.

Look at the evidence

Charts and summaries make patterns easier to see, but they should be read alongside the underlying context. Check the units, comparison period, data coverage, and any gaps called out in the response.

Ask Vega to show its basis when you need more detail:

  • “Which meters are included in this total?”
  • “What period did you use as the baseline?”
  • “Are there gaps in the available data?”
  • “Show the values behind this conclusion.”

For a numerical answer, request a table small enough to inspect. Confirm that energy totals use kWh, power values use kW, and maximum, minimum, and average statistics have not been interchanged.

Missing values are not zero. A partial current period should not be compared directly with a complete previous period unless the answer clearly normalizes or limits both periods.

Read the response metadata

Hover over the metadata icons on an AI response:

  • The book indicates that the response used searchable knowledge sources. Its tooltip shows the available source composition, such as account documents and named knowledge-base retrievers.
  • The tool hierarchy icon lists application tools used when no knowledge-base source was used.

These indicators help explain how the response was produced; they do not by themselves prove that every statement is correct. For contracts, reports, and invoices, open the original record and verify decisive wording or values.

If neither icon is present, ask Vega explicitly which data or source supports the answer rather than assuming it queried account data.

Check warnings and non-verdicts

Treat phrases such as insufficient coverage, overlapping intervals, unavailable, incomplete, or insufficient history as limitations, not as successful checks.

For example, invoice reconciliation deliberately withholds a verdict when measurement completeness is below the required threshold or intervals overlap. Historical invoice comparison cannot label a value normal without enough comparable baselines. See Compare invoices with measured consumption for the exact workflow.

Separate observations from recommendations

An observation describes what the available data shows. A recommendation suggests a possible action based on that observation. Validate important recommendations against operational constraints, safety requirements, and your organization’s procedures.

Ask Vega to structure a decision-oriented answer as:

  1. observed facts,
  2. calculation or comparison,
  3. assumptions and missing information,
  4. possible explanations, and
  5. recommended next checks.

An explanation can be plausible without being demonstrated by the available data. Require Vega to say what evidence would confirm it.

Copy and review a result

Hover over a message and select Copy message. Vega copies the visible table when the response is showing a table, the visible chart when supported by the browser, or otherwise the message text.

After copying, retain the scope, period, units, and limitations with the result. A chart without those details is easy to misinterpret outside its original conversation.

Use the thumbs-up or thumbs-down action to submit feedback on an AI response. You can add an optional comment, change existing feedback, or delete it. Feedback records your assessment; it does not correct the answer automatically. Send a follow-up with the correction when you need a revised result.

Continue the investigation

Useful insights often lead to better questions. Compare the result with another period, break a total down by asset, or ask what additional data would increase confidence. Keeping the investigation in one conversation preserves context as you work.

For a material decision, finish with:

Restate the conclusion with the exact scope, dates, values, coverage, sources, assumptions, and unresolved checks. Do not include claims that are not supported by the available evidence.

If the subject changes, preserve the original investigation and start a new conversation.