create report control block

(in the SCL) preconfigured by vendor (a set of empty control blocks without a payload)

in the SCL by SCT or preconfigured by vendor

configure report control

online through use of SetBRCBValues or SetURCBValues

in the SCL by SCT or preconfigured by vendor

create data set

online through use of CreateDataSet

in the SCL by SCT or preconfigured by vendor

connect both together

online through use of SetBRCBValues or SetURCBValues

in the SCL by SCT or preconfigured by vendor

dynamic reporting

There is a clean separation between the field level engineers and the control level engineers. The only exchange needed is the data model of the IEDs that is available very early in the process

As most of the configuration happens online there is a risk report configuration is not included in the *.scd. In fact that is the case in most cases as this would go against it pro.

static reporting

All information is in one file. This can be reused by:

• testing department to simulated and see the information flow

• allow to reuse configurations in the future. Reports rarely change in structure

• minimize the time needed to to configure clients. The more different types of clients there are the more this is an advantage

both the field level and station level engineers are working on the same file the SCL file or be more precise the *.scd file. They must coordinate in time: who has to do what when.

Adding or changing of reports cannot must go through the system configuration tool again.