45   Missing AddCauses

Created: 15 Mar 2005

Status: In Force (green)

Part: Part 7-2 (2003)

Links:

Page:

Clause: 17.5.2.6

Paragraph: Table 39 and 40

Category: Issue may impact interoperability of implementations of Edition 1

Issue

Missing AddCauses

Proposal

add additional cause types

Discussion Created Status
28 Feb 12 In Force (green)
Using the Tracking of command includes the rspAddCause in the object directory and therefore in the ICD file. Therefore there is a standardized way to include the enumeration definition of AddCause for a given IED in case vendor specific extensions are added.

In case a client receives a neg addCause it can not interpretate, then its equivalent to the AddCause "Unkown". 		20 Feb 09 Ballot Period
If b). is the agreed way, the solution has to be decided: As an additional AddCause attribute in 8-1 will lead to interoperability problems between old and new solutions, probably an additional IED server capability tag in part 6 is the agreed solution? 11 Dec 06 Discussion (red)
My understanding is b). Allows private extension. This was the result of the GoE-Meeting on 1.11.04. The tissue was raised from Siemens that's why I can well remember the decision.
11 Jul 06 Discussion (red)
Regarding the open questions raised by Wolfgang, this tissue cannot be green. The questions have to be clarified first. 07 Jul 06 Discussion (red)
What is now the final proposal:
a). do not allow extensions?
b). allow private extensions in the negative range, with a private enumaration definition in SCL? 		04 Apr 05 In Force (green)
GoE-Meeting 1.11.04:
Final proposal
It is a common understanding to differentiate between communication level (MMS Service Errortype will be used) and application level (AddCauses will be used). But this could not be used to justify additional AddCauses.
Some arguments against additional AddCauses:
- Currently a detailed explanation or categories aren’t given for each AddCause to ensure unambiguity.
- Additional AddCauses leads to a higher granularity.
- Vendor specific implementation requires e.g. additional AddCauses in the future. Therefore this AddCause table couldn’t be finalised.
The definition of add cause is defined as Enumeration in an ICD file. This relates the text string to the number - and at engineering time the text string is used, and could also be used in an HMI. What has to be solved is that this enumeration in the negative range is IED type / Manufacturer specific. So, there must be several AddCause related numerations, and they must be clearly related to the IED / IED type. A possibility could be to model AddCause as 8-1 mapping specific attribute (like Oper, SBOw etc, introuduced in 8-1), which then references an
appropriate Enumeration - either the default, or an extended manufacturer specific one. The other possibility is to just reference the Enumeration in an additional server capability tag.
15 Mar 05 In Force (green)
Montreal:? most of these additional AddCauses seem to be covered by ServiceEroortype.
Therefore no other values shall be added. 		15 Mar 05 Discussion (red)

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1