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
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. 24.4.30.1