R10/R10A

M-1 load curve of a C2 or C4 point, at 5 or 10 minute intervals. Used to follow customer consumption in detail. A file normally carries a single PRM, but every Corps it contains is read, so a file carrying several PRM feeds several sources.

R10 and R10A are read by the same interpreter and produce the same keys.

Insights configuration

Property	Value
Meter number of the source	`Identifiant_PRM`
Mapping config of the variable	See below
Granularity	5 or 10 minutes, as published

See Source configuration for the other properties.

Mapping config

R10_Classe-2_{Statut_Point}

Segment	Description	Values
`Classe-2`	Fixed. The flow carries measurements, never indexes.	—
`{Statut_Point}`	Status of the measurement point, from the `Statut_Point` attribute	`R` → `RELEVE` `E` → `ESTIME` `C` → `CORRIGE`

Points are grouped by status, so a file mixing statuses feeds one variable per status.

Note

Any other status — including S, mains outage — is written as RELEVE. Those points land in the RELEVE variable together with the read ones.

Example

R10_Classe-2_ESTIME

Data point


Timestamp	The `Horodatage` attribute of the point. No offset: read as Europe/Paris, stored in UTC — see Timestamps.
Value	The `Valeur_Point` attribute of the point

What is not stored

A point without Horodatage, or without Valeur_Point — the attribute is absent when the measurement was not read, or when a correction has not been made yet.
A status whose points are all skipped produces no series at all, and therefore no warning about a missing variable.

  DOCS 2026.08
  
                    Documentation changelog →

Documentation Center