CDCs like ACT have the DA originSrc (source). The GOOSE trip carries the value of DA originSrc to the DA origin (destination).
CDCs like APC have a DA origin (destination). An Operate service carries the origin service parameter to the DA origin (destination).
CDCs like MV are also used as a "source” (e.g., the FSCC has a measured value of CDC MV being used to send the measured value in an Operate service to an APC typed setpoint. The Operate service should carry the value of DA originSrc to the DA origin (destination). See ongoing work on 7-420 and AH TF Control over Goose. Unfortunately there is no DA originSrc in the MV as in ACT.
GOOSE and Operate as “control services” should be unified and use DA originSrc in the source Data Object.
DA originSrc would be modelled in any kind of “source object”, and origin in any kind of “destination object” independent of using C/S Operate (using destination addressing) or GOOSE (source addressing).
Proposal
The DA originSrc should be added as an option to all CDCs for measurements and status.
The ongoing work on 7-3 Amd 2 should take this extension into account.
Discussion
Created
Status
Approved
22 Nov 22
Future Improvement
Set to future improvement.
22 Nov 22
Approval (Future Improvement)
Set to future improvement and needs be further investigated in the 7-5 dealing with GOOSE action used to trigger an excecution of a control operation.
AMD2.2 has been canceled.