1897   Data-change and data-update inclusion bitstring bits set in a report

Created: 28 Nov 2023

Status: Conformance Test Preparation

Part: Part 7-2 (2020; Edition 2.1)

Links:

Page: 53

Clause: 6.3.3.3

Paragraph: Reason for inclusion in reports (ReasonForInclusio

Issue

It is stated in the standard that ‘data-change’ and ‘data-update’ are mutually exclusive of each other.

It is also mentioned in 17.2.3.2.3.2 that it is preferable to send only a single report when changes meet more than one TrgOps criteria.

However, both data-change and data-update can happen within same scan cycle and will generate a report with both inclusion bits set. e.g. BCR common data class.

Proposal

Allow data-change and data-update ReasonForInclusion bits to be set within a same report for same data object when client has enabled both trigger options.

Discussion Created Status
No compatibility problem could be found.

Replace text in 6.3.3.3 with:
'general-interrogation', and 'integrity' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInReport attribute.

Replace text in 6.3.3.4 with:
'general-interrogation', 'integrity' and 'application-trigger' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInLog attribute.

No compatibility issue identified. A client with limitation can adapt the ReportControlBlock.TriggerOptions anyhow limiting the scope of reporting to either dataChange or dataUpdate.
01 Apr 25 Conformance Test Preparation
Replace text in 6.3.3.3 with:
'general-interrogation', and 'integrity' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInReport attribute.

Replace text in 6.3.3.4 with:
'general-interrogation', 'integrity' and 'application-trigger' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInLog attribute.

No compatibility issue identified. A client with limitation can adapt the ReportControlBlock.TriggerOptions anyhow limiting the scope of reporting to either dataChange or dataUpdate. 		11 Feb 25 Analysis Of Compatibility
Replace text in 6.3.3.3 with:
'general-interrogation', and 'integrity' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInReport attribute.

Replace text in 6.3.3.4 with:
'general-interrogation', 'integrity' and 'application-trigger' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInLog attribute. 		21 Jan 25 Verify Draft Implementation
'data-change' and 'data-update' are mutually exclusive of each other for each particular data attribute as specified in Table 5.
An FCD is composed of several dataAttributes. Each of the data attribute may have up to 1 trigger option defined.
In case of a BCR[ST], the case can happen that
. the BCR[ST].actval is dChg,
- while BCR[ST].q is qChg,
. and BCR[ST].frVal is dUpd.
If all the 3 attributes changes within a BufTm interval, then the 3 trigger options are superposed, and if the RCB.Trg allows [dChg qChg, dUpd] then the reasonForInclusion will indicate all the 3 reason at the same time, if the Server choose to gather the changes - see IEC 62850-7-2 - 17.2.32.3.2 Note 3: For changes that meet more than one TrgOps criteria, it is preferable to send only a single report in such case.

Changes in 6.3.3.3 and 6.3.3.4 are required to allow data-change and data-update can happen in the same report resp. log.

Proposed changes:
Replace text in 6.3.3.3 with:
'general-interrogation', and 'integrity' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInReport attribute.

Replace text in 6.3.3.4 with:
'general-interrogation', 'integrity' and 'application-trigger' reasons for inclusions are mutually exclusive of all other ReasonForInclusionInLog attribute. 		17 Dec 24 Drafting Implementation
Test procedure change to be reviewed. 03 Dec 24 Discussion (red)
Conformance test cases sRp3/sBr3 correct as published. 29 Oct 24 Conformance Test Verification
https://redmine.ucaiug.org/issues/6886 27 Aug 24 Conformance Test Preparation
Move to conformance test preparation.
Modelling test shall verify that dchg and dupd cannot be true for a give DA. 		16 Jul 24 Conformance Test Preparation
append sentence in 6.3.3.3 and 6.3.3.4
"'data-change' and 'data-update' are mutually exclusive of each other"

with
"for each particular data attribute as specified in Table 5."

As stated in IEC 61850-7-3 Clause 7-1: Sometimes, both dchg and dupd are specified as a possible trigger option for the DataAttribute. In that case, the concrete implementation shall select one of them

No incompatibility issue could be identified.


21 May 24 Analysis Of Compatibility
append sentence in 6.3.3.3 and 6.3.3.4
"'data-change' and 'data-update' are mutually exclusive of each other"

with
"for each particular data attribute as specified in Table 5." 		23 Apr 24 Verify Draft Implementation
Accepted.
What is meant is:
'data-change' and 'data-update' are mutually exclusive of each other for each particular data attribute as specified in Table 5.
Proposed change : append sentence in 6.3.3.3 and 6.3.3.4
"'data-change' and 'data-update' are mutually exclusive of each other"

with
"for each particular data attribute as specified in Table 5." 		19 Dec 23 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 25.2.18.2