Configuring Fluvius telecontrole

Fluvius decides what it expects from an installation in three documents: the study document (studiedocument) that says which flex products apply and which installations sit behind the Netflex cabinet, the zone sheet (zonefiche) of the congestion area, and the single line diagram on which the cabinet is drawn. Every setting on this page transcribes one of those documents. Keep them at hand, because a value that does not match them fails the certification, however well the installation behaves.

Almost everything lives on one page: Configuration → Grid & market → DSO RTU settings. Two settings live elsewhere and are covered at the end: the access powers under Grid settings and the IO module ports.

What applies to your connection

Every Netflex connection needs the base configuration. What comes on top depends on the flex products the study imposes, so check that first: it decides which sections matter and which stay empty.

A connection can have both flex products; then everything on this page applies.

Before you start

Collect from the customer and the installer:

• The study document: whether technical flex is imposed (steering of the assets through MAXSETAP and MINSETAP), and which installations Fluvius counts behind the cabinet.
• The zone sheet: the registered flexible consumption power for channel 6, and the Fall-Back Flex parameters when the connection has that formula.
• The single line diagram with the Netflex cabinet: it is leading for the certification. An installation drawn behind the cabinet is registered; one drawn outside it is not.
• The reference powers from the Fluvius DER register, when technical flex applies. Ask Fluvius for them; they are not the nameplates of the equipment. See asset setpoints.
• The contractual access powers of the connection, import and export.

1. Select the provider

Set Telecontrol provider to Fluvius Netflex. The rest of the form appears once a provider is selected. If the option is missing, the controller runs a version that does not support it yet; update the controller first.

Selecting the provider starts the IEC-104 server on the controller and lets the Fluvius RTU connect. The physical link is described in RTU connection; the controller's address on the RTU link is filled in by the platform, see Network configuration.

2. Emergency stops

Fluvius has two emergency stops, one for production (injection) and one for consumption (offtake). The form has a block per side, each with two lists:

The software stop always runs, whatever is configured here: on a production stop the EMS sets PV to zero and the battery to 0 kW, on a consumption stop the battery to 0 kW and the controllable loads off. The relay outputs add the physical disconnection Fluvius expects. How to wire a relay as a hold circuit, which actuation mode to pick and what the module's own watchdog must be set to is on Emergency stop.

3. Flex according to the study

This section transcribes the study document and decides which measurement channels Fluvius expects.

Without technical flex, Fluvius only steers the connection point (MAXSETP, MINSETP) and only expects channels 5 and 6. The asset reference powers and the production channels then play no role, and the form says so when a device is assigned to a channel the dossier does not expect.

4. Asset reference powers

Only with technical flex. The two powers Fluvius registered for the site, which MAXSETAP and MINSETAP are percentages of:

Enter the values from the Fluvius DER register, not the nameplates. Left empty, the EMS falls back to the installed power of the assets it steers, which keeps the site safe but does not match the inspector's arithmetic. The full reasoning, a worked example and the certification checklist are on Asset setpoints.

5. Netflex measurement channels

Fluvius registers a power per measurement channel and expects measurements only in the channels that registration covers. The Netflex measurement channels card lists every device that can carry a measurement and the channel it is reported in.

Every device starts in the channel that matches its type. Change it when the dossier says otherwise:

• A battery that Fluvius registered as flexible consumption belongs in channel 6, not in channel 4.
• EV chargers always go separately in channel 5, never in channel 6.
• An asset that is not part of the flex registration, for instance PV that is not drawn behind the cabinet, is set to Not reported. Fluvius then receives no measurement for it.

The summary cards show the installed power and the number of devices per channel. Two checks run on the configuration: a warning when devices sit in a channel the dossier does not expect (production channels without technical flex), and a comparison of the power configured in channel 6 with the registered flexible consumption power from the zone sheet.

6. The registered asset group

Below the channels, the Devices for telecontrol table lists the PV inverters and batteries with a switch that says whether the device belongs to the asset group Fluvius registered behind the cabinet. That membership decides whether the device counts at the virtual asset coupling point and whether the telecontrol laws steer it. See counted versus steered for what the switch does and does not mean.

Three settings have to tell the same story about the same diagram: the measurement channel of a device, its membership of the asset group, and the reference powers. A PV that is not drawn behind the cabinet is Not reported, outside the asset group, and absent from the production reference power. A PV that is drawn behind it is in channel 1, inside the group, part of the reference power, and steerable. Fluvius does not accept a mix, such as a PV that is reported only to offset the battery, and the measurement channels card flags the two halves of that mix: a device in the asset group that is not reported in an asset channel, and a device in an asset channel that is outside the group.

7. Fall-Back Flex

Connections with the Fall-Back Flex formula enable it in the same form: Fall-Back Flex active, the reduced power P_red, and for day-ahead zones the planning API settings. Fall-Back Flex covers the formula, the configuration fields and the monitoring.

8. Access powers under Grid settings

MAXSETP and MINSETP are percentages of the contractual capacity of the connection. The EMS takes that capacity from Configuration → Grid & market → Grid settings: the access power for consumption is the base of MAXSETP, the access power for injection the base of MINSETP. Enter the contractual values, before any safety margin. For a Fall-Back Flex connection the import access power is P_base from the bid form.

9. The IO module ports

The relay outputs and inputs assigned in step 2 are shown on the Ports page of the IO module (Configuration → Devices, open the module). The diagram shows which port carries which function, and the table below it shows the actuation mode of each relay output. Check here that every emergency stop has a port and that the actuation mode matches the wiring.

Checklist before the certification

• [ ] Provider set to Fluvius Netflex, and the DSO RTU dashboard shows a recent snapshot with every setpoint at 100 %.
• [ ] Both emergency stops have a relay output that physically disconnects the assets, and the module's watchdog and safe state are set.
• [ ] Technical flex matches the study document, and the registered flexible consumption power matches the zone sheet.
• [ ] With technical flex: both reference powers come from the Fluvius DER register.
• [ ] Every device is in the channel of the dossier, devices outside the registration are Not reported, and the channel 6 coverage check is green.
• [ ] The asset group agrees with the single line diagram, and no registered device is unmanaged.
• [ ] The access powers under Grid settings equal the contractual capacities.
• [ ] Every device Fluvius may steer is controllable in the EMS.

Commissioning and certification describes how the test itself runs and how to follow the values on the DSO RTU dashboard while the inspector sends them.