> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voltview.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# On-site assets

> Generation and storage on the site, next to the meter.

VoltView already tracks what a site **buys** from the grid. On-site assets cover what the site **makes and stores**: rooftop solar, ground-mount arrays, and batteries.

We connect to the inverter or installer monitoring portal ourselves. We do not resell a third-party device network. v1 is **read-only**. We do not charge, discharge, or change setpoints.

<CardGroup cols={2}>
  <Card title="Solar" icon="sun" href="/assets/solar">
    Generation, self-consumption, and export, mapped to the site and its import MPAN.
  </Card>

  <Card title="Batteries" icon="battery-full" href="/assets/batteries">
    State of charge and charge/discharge power. After solar is live.
  </Card>
</CardGroup>

## What this is for

Meter data answers "what did we import." Asset data answers the rest:

* How much did the array generate this interval.
* How much of that was used on site versus exported.
* Whether a battery charged from solar, from the grid, or discharged into the building.

Without that, solar savings are a forecast and a bill, not a measured loop against the half-hourly meter. How that meter counts kWh, kvarh, and peak demand is in [Electricity meters](/metering/overview).

## Who owns the feed

The asset owner owns the monitoring login. That is not always the occupier.

| Arrangement                    | Who owns the array | Whose portal we need                    |
| ------------------------------ | ------------------ | --------------------------------------- |
| Self-funded                    | The customer       | Customer's installer or OEM login       |
| PPA / funded rooftop           | The funder         | The funder's portal, with their consent |
| Landlord-owned, tenant offtake | The landlord       | Landlord or their installer             |

If the customer does not own the array, a monitoring login from them is not enough. Ask the owner. Do not scrape a portal you do not have rights to.

## How it sits next to meters

An asset belongs to a **site**. Generation and discharge are then compared to that site's **import MPAN** (and export MPAN if there is one).

```
Site
├── Meters (import MPAN, optional export MPAN)
├── Solar systems (inverter / portal)
└── Batteries (inverter / BMS / portal)
```

v1 does not invent a new site type. It adds assets onto the site you already have.

## What v1 will and will not do

| In v1                                                       | Not in v1                                   |
| ----------------------------------------------------------- | ------------------------------------------- |
| Read generation, power, and (for batteries) state of charge | Remote control or optimisation              |
| Map each asset to a site and import MPAN                    | Virtual power plant or flexibility dispatch |
| Show self-consumption versus export once both feeds exist   | Price or tariff inputs on the asset         |
| Store history next to half-hourly meter data                | A public catalogue of every OEM on day one  |

Solar ships first. Batteries follow the same connect-and-map pattern once the solar path is proven.

## Connecting an asset

1. Confirm who owns the array or battery, and that they will share the monitoring login or API token.
2. Create the asset on the site in VoltView.
3. Connect the OEM or installer portal.
4. Map it to the import MPAN (and export MPAN if the site has one).
5. Wait for the first successful pull, then compare generation to meter import.

If the portal cannot issue an API token, a read-only user on the monitoring dashboard is the fallback. CSV export is last resort and is not a live feed.

## Coverage

We add OEM portals one at a time, starting with the platforms on live pilots. There is no claim of "every inverter." If a site uses a portal we do not support yet, we say so and take a file export or a later connector. See [Solar](/assets/solar) for the current list.