Select sites and assets in a conversation

Why explicit scope matters

Vega can search the active account for sites and components, but a name in ordinary text can still be ambiguous. An @ reference inserts the current user-facing site and component names in a form Vega can resolve reliably.

Before starting, select the correct account and use Inventory to confirm which component contains the measurement you need.

Select an entire site

1. In the Chat message box, type @.
2. Begin typing the site name if the list is long.
3. Choose the intended site.
4. Choose All components at site name.
5. Complete the question with a metric, period, and requested output.

The inserted reference looks like @Main Warehouse. Use a site-wide scope only when all relevant components should be considered. A site can contain utility, solar, calculated, and other components whose values should not automatically be added together.

Select one component

1. Type @ and search for the site.
2. Choose the site.
3. Search or browse the components at that site.
4. Choose the required component.
5. Check the inserted reference before sending.

For accounts with several sites, the reference includes both levels, for example:

@Main Warehouse / Grid Meter

When the account contains exactly one site, Vega may offer its components directly and insert only the component reference.

The picker supports the keyboard: use the up and down arrow keys to move, Enter to insert the highlighted option, and Escape to close it. Select Load more when the required site is not on the first result page. If loading fails, use Retry.

Choose the right level

Use a component reference when asking about:

• one utility measurement point,
• one solar installation, inverter, array, or other device,
• an invoice associated with a particular meter,
• component health or metadata, or
• a series that could be confused with another component’s series.

Use a site reference when asking Vega to describe the facility, list its components, or compare appropriate values across that site’s assets.

For several sites or components, insert each intended reference and state how they should be treated:

Compare monthly consumption for @North Office / Grid Meter and @South Office / Main Meter from January through June 2026. Keep the two components separate.

Avoid double counting

Parent, child, and virtual components can represent related values. A parent total may already include its descendants, and a calculated component may derive its value from physical components.

Do not select a parent and all its children for one total unless you know they are independent series. Ask Vega:

List the component hierarchy and explain which component should be used for a non-overlapping site total. Do not calculate the total yet.

Then send the analytical question using the confirmed component.

Confirm the scope in the answer

After Vega responds, ask:

State the exact site references, component references, metric definitions, units, and period used in the result.

Check that:

• the active account did not change,
• current display names were used,
• consumption was not confused with production,
• power in kW was not confused with energy in kWh,
• the site-wide selection did not include overlapping components, and
• the period has sufficient data.

If the scope is wrong, correct it explicitly in the same conversation and ask Vega to recalculate. For a completely different facility or purpose, start a new conversation so old context does not carry over.