...
Create report control block: Add report to the server
Configure the report control block: Define the behavior of the report
Create data set: Define the payload of the report in the DataSet element
Connect both together: Set the data set reference in the report control block
With those three basic steps we can now compare the two mentioned processes together as such:
Basic step | dynamic | static |
---|---|---|
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 |
...
pro’s and con’s
Type | pros | cons |
---|---|---|
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:
| 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. |
Mixing static and dynamic reporting
...