68 New CDC ACI
This tissue has following status: green
Created: 15 Mar 2005
Category: Issue for edition 2 of this part
Issue: When a command is done over an element, it is very useful to know who done it. For example, when operation “open switch” is done by a CSWI, the originator is not stored in ACT common data class. This comment is related as a new CDC required for a comment on part 7-4.
Proposal: Add origin attribute of Originator type, to ACT common data class or
Define a new common data class (ACI) as follows:
configuration, description and extension
d VISIBLE STRING255
dU UNICODE STRING255
cdcNs VISIBLE STRING255
cdcName VISIBLE STRING255
dataNs VISIBLE STRING255
set to green
Some clarifications why that TISSUE has been raised:
Typically, control operations and data of a control CDC are used to operate a device. These data have the attribute "origin" (with FC=CO) in order to determine the originator of a control.
In some cases, GOOSE mesages are used instead. In that case, the conteol value is transmitted with a data of the CDC ACT. So far, it was not possible, to supply the "origin" information with such an operation request. With the proposed extension, this will be possible.
|14 Jun 05
Ballot date added
||11 May 05
||17 May 05
accepted as proposed by Christoph Brunner on March 29th. Data Attribute origin will be added as optional in the ACT CDC.
|02 Apr 05
Also with the client/server based control services, the originater (the client) is known. Still we have introduced origin in the CDCs (not only as status ST but also as control CO). Therefore, I would suggest to add it as optional to the CDC ACT.
I would propose the following text for the final proposal:
"Basically accepted. Add an optional attribute origin of type Originator to the CDC ACT"
|29 Mar 05
Privacy | Contact | Disclaimer