Project

General

Profile

Issues #6886

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

Added by IEC 61850 TPWG 7 months ago. Updated 1 day ago.

Status:
Closed
Priority:
Normal
Assignee:
Richard Schimmel
Due date:
04/01/2025
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
https://iec61850.tissue-db.com/tissue...
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
sMdl18, sRp3/sBr3
Closed Reason:
No Action Taken
Triggering Tissue 2:
Triggering Tissue 3:

Description

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

#1

Updated by IEC 61850 TPWG 7 months ago

  • Due date set to 10/01/2024
  • Status changed from New to In Progress
  • Assignee set to Richard Schimmel
#2

Updated by IEC 61850 TPWG 6 months ago

  • Due date changed from 10/01/2024 to 10/29/2024
#3

Updated by Richard Schimmel 5 months ago

  • Test Case ID set to sMdl18, sRp3/sBr3

sRp3/sBr3 already states in the expected result: "the reason code is one of the configured trigger options". This will prohibit dupd+dchg!
sMdl18 states that in the SCL the DA: "is conformant with 61850-7-3 Trigger option". That may be clarified.

#4

Updated by IEC 61850 TPWG 5 months ago

  • Due date changed from 10/29/2024 to 11/12/2024
  • Status changed from In Progress to Resolved
#5

Updated by Thierry Dufaure 4 months ago

Is sMdl18 verifying that only dchg="true" or dupd="true" are mutually exclusiv in the (DataTypeTemplate) DA declaration?

#6

Updated by IEC 61850 TPWG 4 months ago

  • Due date changed from 11/12/2024 to 12/10/2024
  • Status changed from Resolved to In Progress
#7

Updated by Richard Schimmel 4 months ago

sMdl18 also checks the TrgOps in the SCL file do match with those in the NSD. If the NSD does not allow dupd than the SCL will fail. For sure dchg and dupd are mutually exclusive. This should in principle prevent a report with reason-code "dupd" and "dchg" for the same element. The tissue is about a report, not the SCL.

#8

Updated by IEC 61850 TPWG 3 months ago

  • Due date changed from 12/10/2024 to 02/04/2025

Waiting for TISSUE resolution.

BCR can have both dchg and dupd in some rare cases.

#9

Updated by IEC 61850 TPWG 2 months ago

  • Due date changed from 02/04/2025 to 03/04/2025
#10

Updated by IEC 61850 TPWG 29 days ago

  • Due date changed from 03/04/2025 to 04/01/2025
#11

Updated by Richard Schimmel 28 days ago

sMdl18 requires each attribute in the SCL has one trigger condition => no need to change
sRp3/sBr3 verifies the following trigger conditions:
- on integrity
- on update (dupd)
- on data-change
- on data-change and quality-change
- on data-change, quality-change and integrity with a valid integrity period

The special case of BCR that may have an attribute with dupd and another attribute with dchg, may result in a report with both reason codes. But that will never happen in sRp3/sBr3 because the trigger condition combination dupd and dchg is not tested!
I see no reason to change the existing test procedures.

#12

Updated by IEC 61850 TPWG 1 day ago

  • Status changed from In Progress to Closed
  • Closed Reason No Action Taken added
  • Closed Reason deleted (--Not Set---)

No change to test procedures per Richard's explanation.

Also available in: Atom PDF