1297   How to differentiate preconfigure Datasets from those generated by the System Configuration Tool

Created: 04 Aug 2014

Status: In Force (green)

Part: Part 6 (2009-12; Edition 2)

Links: #1444 Need to support fixed and SCT controlled Datasets

Page: 63

Clause: 9.3.2

Paragraph: Table 11

Category: No impact on this part


Table 11, ConfDataSet specifies:
"If ConfDataSet is not specified, then the default value of its max attribute is equal to the number of preconfigured data sets, and they may only be modified".

After a while, it is not possible to remember which Datasets were preconfigured and which were not. Typical Use Case: for a retrofit of a Substation, the engineer gets the SCD file from the Substation which may have been engineered 5 years before by somebody else. He/she cannot know whether the Datasets engineered in the SCD file were originally predefined in the ICD/IID file, or whether they were added by the System Configuration Tool.


Add another element or attribute to tDataSet (chapter 9.3.7), e.g. "predefined" with "true", "false" and "unknown" as possible values. All Datasets defined by the IED configuration tool must have this set to true, all others false.

- For backwards compatibility reason, the default value is "unknown".
- An IED Configuration Tool which creates Datasets must mandatorily set these values to "true".
- A System Configuration Tool which creates Datasets must mandatorily set these values to "false".
- in case of value "unknown", the engineer using the System Configuration Tool must decide how to proceed.

Discussion Created Status
15 Oct 14 In Force (green)
As this also means that "they may be modified (only)" it is totally irrelevant if they were preconfigured or not. See also Tissue 1298.
Therefore not accepted
05 Aug 14 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.