1788   Required LPHD nameplate and TCTR/TVTR settings not available in SCL

Created: 27 Aug 2021

Status: Future Improvement

Part: Part 9-2 (related to IEC 61869-9; 2016)

Links:

Page: Multiple

Clause: 6.903.2, 6.903.7, 6.903.8

Paragraph: Various

Issue

From IEC 61869-9 Section 6.903.2 (Variants):
"Device nameplate documents device capability (range of supported variants) with active configuration separately specified in the merging unit configuration file (Annex 9C)."

Nameplate data objects and TCTR/TVTR characteristics are required during the engineering phase of a project. This includes (but is not limited to) nameplate data object extensions such as LPHD.NamVariant, setting extensions such as TCTR.NamAccRtg, as well as mandatory setting data objects such as TCTR.ARtg, TCTR.AmpSv.sVC, TCTR.Clip, equivalents for TVTR, etc (as defined in 61850-7-4). Currently the only requirement is that these data objects and attributes exist in the server data model and values are not required to be defined in the SCL file. If the values are missing, the SCL file cannot be used to check that the system is engineered correctly. Therefore, 61869-9 should require these values to be defined in the SCL file for the device.

In addition, this statement is under chapter heading “Variants”, so it incorrectly implies that the variant code of the active configuration is included in the merging unit configuration file.

Proposal

CHANGE #1: In Section 6.903.2, delete "Device nameplate documents … in the merging unit configuration file (Annex 9C)." and replace with:
“The device capability (range of supported variant codes) is defined in the extension nameplate data object LPHD.NamVariant as defined in Table 903. The variant code of the active configuration can be derived from the sampled value control block and dataset configuration and is not stored explicitly in the merging unit configuration file.”

CHANGE #2: Mandate inclusion of LPHD nameplate information values in SCL.
Addition of the following text, inserted immediately before Table 903:
“Data objects from Table 903 shall have values for all mandatory data attributes defined in the device SCL files as DAI instance values or as DataTypeTemplates DA values.”

CHANGE #3: Mandate inclusion of TCTR nameplate and setting information values in SCL.
Addition of the following text, inserted immediately before Table 904: “Data attributes in Table 904 shall have values defined in the device SCL files as DAI instance values or as DataTypeTemplates DA values.”

Addition of the following text, inserted immediately before Table 905: “Data objects from Table 905 shall have values for all mandatory data attributes defined in the device SCL files as DAI instance values or as DataTypeTemplates DA values.”

Addition of the following text, inserted immediately after Table 905: “All status setting data objects (CDCs as defined in IEC 61850-7-3:2010, 7.6) and analogue setting data objects (CDCs as defined in IEC 61850-7-3:2010, 7.7) in the device TCTR logical nodes, shall have values for all mandatory data attributes defined in the device SCL files as DAI instance values or as DataTypeTemplates DA values. ”

CHANGE #4: Mandate inclusion of TVTR nameplate and setting information values in SCL.
Addition of the following text, inserted immediately before Table 906: “Data attributes in Table 906 shall have values defined in the device SCL files as DAI instance values or as DataTypeTemplates DA values.”

Addition of the following text, inserted immediately before Table 907: “Data objects from Table 907 shall have values for all mandatory data attributes defined in the device SCL files as DAI instance values or as DataTypeTemplates DA values.”

Addition of the following text, inserted immediately after Table 907: “All status setting data objects (CDCs as defined in IEC 61850-7-3:2010, 7.6) and analogue setting data objects (CDCs as defined in IEC 61850-7-3:2010, 7.7) in the device TVTR logical nodes, shall have values for all mandatory data attributes defined in the device SCL files as DAI instance values or as DataTypeTemplates DA values.”

Discussion Created Status
Approve 11 Oct 22 Future Improvement
I agree with Thierry's comment.
As we are not the editors of the IEC 61869-9, I suggest to comment in that sens the futures 61869-9 draft documents circulated by TC38.
All implementations should expose the values in their ICD files as initially intended in the informative annex 9C.
25 Mar 22 Approval (Future Improvement)
I agree with the concern that the mandated values by the product standard shall be exposed both as online values as well as in the SCL ICD/IID file of the product.
This is a generic 61850 requirements - it applies also to name space, description, configuration or setting values.
The proposed changes should be integrated in the next version of the standard. As it does not impact device interoperability but facilitate the engineering, propose to change to FutureImprovement and to encourage all product vendor to already fullfill the requested changes.
25 Mar 22 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 22.10.13.1