How to Query Floating / Index-Priced Volumes

The floating views — fct_volume_pwr_floating_15m, fct_volume_pwr_floating_15m_deal, and the EWE wrapper equivalents — expose volumes for power deals settled against a published index (instrument_sub_type = 'PWR Index') rather than at a fixed agreed price.

When to use which view

Need	View
Fixed-price deals (VWAP)	fct_volume_pwr_15m
Floating / index deals (index price)	fct_volume_pwr_floating_15m
Both, joined together	Both, joined on (delivery_date_utc, begin_utc, business_case, grid)

The floating views have the same gap-fill, partition-pruning, and date-filter rules as the fixed views.

Column shape difference

Floating views replace the VWAP columns with a single index price:

Fixed	Floating
buy_vwap_price_eur_per_mwh	—
sell_vwap_price_eur_per_mwh	—
—	power_index_price_eur_per_mwh

And they add:

• internal_business_unit
• external_business_unit
• power_index_name

The grain is correspondingly wider: business_case + grid + internal_BU + external_BU + power_index_name + begin_utc (+ deal_id on the _deal variant).

Basic query

select
    delivery_date_utc,
    begin_utc,
    business_case,
    grid,
    power_index_name,
    sum(volume_buy_mw)                  as volume_buy_mw,
    sum(volume_sell_mw)                 as volume_sell_mw,
    avg(power_index_price_eur_per_mwh)  as avg_index_price
from fct_volume_pwr_floating_15m
where delivery_date_utc = current_date
group by 1, 2, 3, 4, 5
order by 1, 2, 3, 4, 5

Index price interpretation

power_index_price_eur_per_mwh is the index print for the period, for example the EPEX PWR EPEX_DE_INTRADAY 15min index for 2026-04-15 14:30 UTC. It is the published 15-minute price for the period from core_endur_index_pricing_15m_daily. One row's price is not weighted by anything in the view.

• One reference source per index. The price comes from the index's own reference source, which is set on the index definition in Endur. Every row on the same index and period carries the same price, whatever the deal, business case or business unit.
• Looked up when you query. The views look the price up by index and delivery day each time you query them. You always see the current price that Numera holds for that index and delivery day, and a revised index price appears the next time you query.
• Missing prices. Where the index has no price for the delivery day, the EWE wrappers show 0 and the numera-core views show NULL. Monthly indices carry their monthly value instead; see Indices without 15-minute prices.

A given (business_case, grid, period) cell can have multiple rows if multiple (internal_BU, external_BU, power_index_name) combinations contribute. The price is per-index, so different rows can have different prices in the same cell.

Indices without 15-minute prices

The monthly market-value indices have no 15-minute prices in Endur, only one value per month:

• PWR_MMW_Wind_OnShore_DE.EUR
• PWR_MMW_Solar_DE.EUR
• PWR_MMW_Wind_OffShore_DE.EUR

Volumes on these indices appear in the floating views as normal. Their power_index_price_eur_per_mwh carries the month's value in every 15-minute period of that month, where months are calendar months in German time (Europe/Berlin):

• Published months: the published monthly market value, from about the 10^th of the following month.
• Months not yet published, and future months: Endur's forward value for the month, which follows the German monthly baseload forward. It is updated with every load until the published value replaces it.
• No value at all: 0 in the EWE wrappers and NULL in the numera-core views.

A UTC delivery day can span two German months. For example, 2026-10-31 from 23:00 UTC is already November in Germany, so the last four periods of that UTC day carry November's value.

Because the price is flat over the month, it is not a 15-minute market price. Use it as the monthly settlement value.

Filtering to a single index

select
    delivery_date_utc, begin_utc, business_case, grid,
    sum(volume_buy_mw)                  as volume_buy_mw,
    sum(volume_sell_mw)                 as volume_sell_mw,
    avg(power_index_price_eur_per_mwh)  as index_price
from fct_volume_pwr_floating_15m
where power_index_name = 'PWR EPEX_DE_INTRADAY 15min'
  and delivery_date_utc between '2026-04-01' and '2026-04-30'
group by 1, 2, 3, 4

Spread analysis vs fixed-price VWAP

Join fixed and floating views on the same (delivery_date_utc, begin_utc, business_case, grid) cell. The fixed-price VWAP and the index price are both in EUR/MWh.

select
    fp.delivery_date_utc,
    fp.begin_utc,
    fp.business_case,
    fp.grid,
    fp.volume_buy_mw,
    fp.buy_vwap_price_eur_per_mwh,
    fl.power_index_name,
    fl.power_index_price_eur_per_mwh,
    fp.buy_vwap_price_eur_per_mwh - fl.power_index_price_eur_per_mwh as buy_vwap_vs_index
from fct_volume_pwr_15m fp
left join fct_volume_pwr_floating_15m fl
    on fp.delivery_date_utc = fl.delivery_date_utc
   and fp.begin_utc         = fl.begin_utc
   and fp.business_case     = fl.business_case
   and fp.grid              = fl.grid
where fp.delivery_date_utc between '2026-04-01' and '2026-04-07'
  and fp.volume_buy_mw > 0
order by 1, 2

When more than one index applies to a (business_case, grid) cell, the LEFT JOIN fans out; pick a single index or aggregate per power_index_name.

Deal-grain drill-down

select
    delivery_date_utc, begin_utc,
    deal_id, business_case, grid,
    internal_business_unit, external_business_unit,
    power_index_name,
    volume_buy_mw, volume_sell_mw,
    power_index_price_eur_per_mwh
from fct_volume_pwr_floating_15m_deal
where delivery_date_utc = current_date
  and volume_buy_mw + volume_sell_mw > 0
order by deal_id, begin_utc

The volume_buy_mw + volume_sell_mw > 0 predicate is a quick way to suppress gap rows when you only want active intervals.

Pitfalls

Don't filter on instrument_sub_type

It's already applied upstream — every row in the floating views satisfies instrument_sub_type = 'PWR Index'. Adding the predicate is redundant; a different value just yields zero rows.

A zero index price does not mean a zero price was published

In the EWE wrappers, power_index_price_eur_per_mwh is 0 on gap rows, the same as the volume columns, and also where the index has no 15-minute price. In the numera-core views, a missing price is NULL. To tell "no trade in this slot" apart from "no published index price", count rows with volume_buy_mw + volume_sell_mw > 0 instead of inspecting the price.

Don't sum the index price across deals or business cases

The index price is not additive. Every deal, business case and business unit on the same index and period carries the same price, so SUM(power_index_price_eur_per_mwh) multiplies it by the number of rows. When you roll up across deals, business cases or business units, take one price per (power_index_name, begin_utc) with MAX(...), or volume-weight it:

sum(volume_buy_mw * power_index_price_eur_per_mwh) / nullif(sum(volume_buy_mw), 0) as buy_weighted_index_price

Don't average the index price across periods naively

In the EWE wrappers, AVG(power_index_price_eur_per_mwh) over a day includes gap-row zeros, dragging the average down. Either filter to volume > 0 first or volume-weight the average yourself. In the numera-core views, AVG skips NULL prices, so periods without a price drop out of the average.

Related

• Concepts: VWAP vs index price
• Reference: Numera-core views
• Compute P&L and net position