Loads¶

Loads are the measurements you gather yourself. They record how much energy a meter consumed and generated in each 15-minute interval, and you upload them to RECreation. They are different from DSO measurements, which are validated data that the distribution system operator (E-Redes) sends for CPEs.

What a Load Contains¶

A Load is one record per meter and 15-minute interval:

Uploading a record for a meter and timestamp that already exist replaces it. Uploads can be JSON or CSV (see Upload Templates). A CSV file may give a single net energy column (Energia, where positive is consumption and negative is generation) or separate Consumo and Geracao columns. The CSV Hora column is the end of the interval, so 00:15 is stored as the interval starting at 00:00. The endpoints are in the Loads API.

Loads are also used for the energy management modules, where the same data is stored separately as load forecasts: expected future consumption and generation instead of measurements.

How Loads Are Used¶

Resource measurements¶

Every resource is attached to one meter. The platform reads that meter's Loads and computes the resource's net metered energy as consumption − generation. This is what the Market and Settlement use to know what each resource did.

CPE measurements in simulation¶

In a real community the DSO tells the platform how much energy was allocated to each CPE. In a simulation there is no DSO, so RECreation emulates the allocation from the CPE Loads of each interval:

• Proportional and dynamic communities: if the community consumes at least as much as it generates, each CPE is allocated its consumption ÷ total consumption × total generation and there is no surplus. Otherwise, each CPE is allocated all of its consumption, and what is left of its generation after covering its share of the community's consumption is surplus.
• Fixed communities: the allocation uses the fixed coefficients that you provided for each interval. See Allocation Coefficient Methods and Upload Fixed Coefficients.

The result is a set of values approximately equal to what the DSO would send in an ideal scenario. They are only meant for simulation and preview, not as final values.

Real operation¶

In a real (PROD) community, CPE Loads are ignored by the Market and Settlement. For every CPE the platform reads the DSO measurements. Internal meter Loads are still read for the resources behind them. The Loads you upload for a CPE can still be kept for your own reference and charts, but they have no effect on results.

Data Requirements¶

Market clearing and settlement fail when data is missing or inconsistent, so Loads must follow these rules:

1. Every 15 minutes. One record per interval, at the start of the interval.
2. No gaps. Every interval of every session must be present on every meter, CPE and internal. The Market stops with an error that states how many rows it expected (sessions × CPEs) and how many it found.
3. Consistent hierarchy. The data of the internal meters must add up to the data of the CPE they sit behind.

Loads vs DSO Measurements¶