Understanding OBIS codes
You see a label such as Grid consumption or Total consumption next to every reading. Behind it sits an OBIS code. It tells you which quantity you are looking at, and whether two values may be combined.
Where you meet the code
On the Measurement Data page, the Measurement column carries the label for every row. Hover over it and the code itself appears, for example 1-1:1.9.0 P.01. The CSV export contains both: the code and the label.
The three codes per energy direction
Every electricity meter carries three codes per energy direction: the measured total, and the two parts it splits into. For consumption these are
| Label | Code | Meaning |
|---|---|---|
| Total consumption | 1-1:1.9.0 G.01 |
everything the meter measured |
| Grid consumption | 1-1:1.9.0 P.01 |
the part of it you drew from the grid |
| Community share | 1-1:2.9.0 G.03 |
the part of it an energy community covered |
and for feed-in
| Label | Code | Meaning |
|---|---|---|
| Total generation | 1-1:2.9.0 G.01 |
everything the meter generated |
| Grid feed-in | 1-1:2.9.0 P.01 |
the part of it that flowed into the grid |
| Community share (generation) | 1-1:2.9.0 X.01 |
the part of it an energy community took up |
Which direction you see depends on your meter's energy direction. A meter with photovoltaics has a separate metering point ID for consumption and for feed-in, and therefore a separate series for each.
Gas meters have no community concept and carry a single code: Gas consumption (7-1:1.9.0 P.01). They deliver hourly values, electricity meters quarter-hourly ones.
Note:
G.01andP.01must not be added together. The total already contains the grid figure; the community share is what is left over: total consumption minus grid consumption, and never below zero. Adding the total and the grid figure counts the same energy twice.
If your meter is not in an energy community
The three codes are still in your data. The community share is then zero, and total consumption and grid consumption carry the same value. So you do not need to know whether a meter participates in order to read its values correctly.
If your meter is in an energy community
The community share is then greater than zero, and the grid operator additionally delivers a breakdown per community. Those series stay inside the application: analyses, the API and scheduled exports use the per-meter values. A meter taking part in several communities has one row per community and timestamp.
Which code your analyses use
Charts, reports and key figures read exactly one code per meter and timestamp: total consumption where it exists, otherwise grid consumption. For feed-in the same applies to total generation and grid feed-in. Values from several codes are never summed.
For costs and billing, grid consumption or grid feed-in is the right quantity, because only that energy flowed over the grid.
If your grid operator sends a series we do not yet know, we still store the values and show them with their code. They stay available in your export and enter no analysis.
The code says nothing about data quality
The OBIS code describes what was measured. How dependable a value is appears in the Data Quality column (L1, L2, L3). The levels are explained under Measurement Data.
For experts
OBIS codes are standardised in IEC 62056. The leading digit names the medium: 1-… is electricity, 7-… is gas. Which series a grid operator delivers for energy communities is set out in "Regelung für das Qualitätsmanagement der Smart-Meter-Kommunikation und Methodiken zur Ersatzwertbildung" (Oesterreichs Energie, 15.02.2024, in force from 07.10.2024).
Codes scoped to Meter apply to the whole metering point. Codes scoped to Community allocate values to a single energy community; a meter taking part in several has one row per community and timestamp. The API and scheduled exports use the meter-wide values. 1-1:2.9.0 G.03 sits in both scopes: per community, as the grid operator delivers it, and per meter as the third part of consumption.
Not every row comes from the grid operator. Where it does not deliver a total or a community share itself, we compute the value from the registers it did send and store it as a row of its own. A computed row looks the same to you as a delivered one.
| Code | Label | Scope | Meaning |
|---|---|---|---|
1-1:1.9.0 P.01 |
Grid consumption | Meter | energy drawn from the grid |
1-1:2.9.0 P.01 |
Grid feed-in | Meter | energy fed into the grid |
1-1:1.9.0 G.01 |
Total consumption | Meter | measured consumption before the allocation |
1-1:2.9.0 G.01 |
Total generation | Meter | measured generation before the allocation |
1-1:1.9.0 G.01T |
EC consumption (allocated) | Community | consumption at the participation factor; equals G.01 at 100% |
1-1:2.9.0 G.01T |
EC generation (allocated) | Community | generation at the participation factor; equals G.01 at 100% |
1-1:2.9.0 G.02 |
EC generation share | Community | share of the community's generation |
1-1:2.9.0 G.03 |
Community share | Meter and Community | consumption the community covered |
1-1:2.9.0 G.03R |
EC self-coverage (renewable) | Community | the part of that from renewable generation |
1-1:2.9.0 P.01T |
EC surplus remainder | Community | surplus left after the allocation |
1-1:2.9.0 X.01 |
Community share (generation) | Meter | generation the community took up |
7-1:1.9.0 P.01 |
Gas consumption | Meter | volume of gas drawn |
Austria's vocabulary has no standardised counterpart to G.03 for feed-in. 1-1:2.9.0 X.01 is therefore a code we assign ourselves; it is in no standard and comes from no grid operator.
The participation factor is the percentage with which a metering point takes part in one community: at least 1%, in whole percentage points, adding up to at most 100% per metering point.
