1456   Annex A and Mod/Beh/Health

Created: 21 Oct 2015

Status: In Force (green)

Part: Part 7-4 (2010; Edition 2)

Links: #1374 On-blocked Mode & Quality , #1370 Mod/Beh definition of value=2 "on-blocked" is contradictory to part 6 , #1330 proposal in tissue 830 seems not consistent with 7-3 Ed2 , #1273 Behavior of DOI "Beh" due internal condition , #1205 Behavior computation , #838 Testing in Beh=Blocked , #830 Mode/Behaviour & Quality , #712 interpretation of quality operatorBlocked , #671 mistake in definition of Mod & Beh

Page:

Clause: annex A

Paragraph:

Category: Issue may impact interoperability of implementations of Edition 2

Issue

According to proposal of Task Force User Feedback (Meeting of WG10, October 2015, in Brussels), a clarification about Mod/Beh/Health will be added to the first paragraphs of annex A.

Proposal

Add the following sentence to the first paragraph of annex A:
"Switching between the modes (Mod.stVal) should only happen as a result of an operator command to the data object Mod. This can be a remote command as well as result of an IED local action. Mod and Beh are always accessible by the services." (The added part is the middle sentence).

The third paragraph will be changed (added the second sentence):
"Mod, Beh and Health will always have validity=good. Regardless of the status of LN.Beh, the quality test attribute of Mod, Beh and Health shall be q.test=false."

Add a note:
"Note: To ensure backwards compatibility with implementations, it is recommended that the client or subscriber application ignores q.test of the received data Mod, Beh and Health. The means to ignore q.test is a local issue and can be configurable."

The proposed new version of annex A is given in the attachment and shall replace the last attachment of tissue #1331.