332   Ambiguity in use of trigger options

Created: 21 Jun 2006

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page: 088

Clause: 14.2.3.2.3.2

Paragraph:

Category: No impact on this part

Issue

As I understand a report is to be issued ,whenever an internal event due to any of the trigger options mentioned in the report control block occurs. And the trigger options applying to each data attribute is specified in 7-3. as mentioned in NOTE 2.(page 88)
"
NOTE 2 With the specification of the common data classes in IEC 61850-7-3, the trigger option applying to
a specific DataAttribute is defined."

But I find that there are many attributes with missing trigger option in 7-3.Why is this so and how reporting is to be handled in this case?

For example,lets say I have a dataset configured with only a single FCDA (XCBRxxx.ST.Pos.t)and in my Report Control Block, I have TrgOp=dchg.In this case is the server supposed to send any report at all ?



Proposal

A statement similar to "Data attributes with empty trigger options will not trigger any reports other than that due to GI & integrity poll" may be added .

Discussion Created Status
changed to green. The 7-2 clauses for reporting and logging ( Edition 1) can be found at ftp.sisconet.com. Username=wg10revision pw: iec61850. Passive FTP must be used for retrieval. 16 Feb 07 In Force (green)
See TISSUE 453 for revised.
If no TrgOp defined is 7-3, then the reporting of the changed attributes can only occur for integrity and GI.
Each DATA-SET member is evaluated for reported on its own basis. Therefore if "t" is a DATA-SET member, it may only be reported for integrity and GI purposes.
If "t" is part of an FCDA/FCD DATA-SET member, then it will be reported based upon the appropriate TrgOp of the FCDA/FCD.

see actualized figure "Data set members and reporting" in revised text attached to TISSUE 453.
14 Dec 06 Ballot Period

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1