1044   TapChg in AVCO

Created: 15 Mar 2013

Status: In Force (green)

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

Links:

Page: 31

Clause: 5.4.6

Paragraph:

Category: Issue may impact interoperability of implementations of Edition 2

Issue

TapChg is included in two LN AVCO as "Change voltage" and ATCC as "Change tap position". I found it disturbing that one DO has two meanings.
In ATCC which is "Automatic tap changer controller" it is correct to use TapChg but in AVCO that is "a voltage controller independent of the control method being used" I don't understand the use of TapChg because as it is independent on control methods the functionality can be based on something else than tap changer.

Proposal

I would suggest to use something more generic, maybe StepChg, VolStep or VolChg.

Discussion Created Status
Change to status "final proposal" for the proposal: AVCO.TapChg should be changed to optional.
12 Jun 13 Ballot Period
In the LN AVCO the DO TapChg should be changed to optional.
Other proposals should be discussed within the task force of WG10 for FACTS.
06 May 13 Discussion (red)
TapChg is mandatory in AVCO so it is a good question what the optional SptVol (or VolSpt according to tissue 932), Voltage setpoint, shall be used for?
In ATCC TapChg, Change tap position, and TapPos, Set tap position, are conditional "depending on the tap-change method, at least one of the two controls, TapChg or TapPos shall be used for manual operation"
25 Mar 13 Discussion (red)
As far as I remember, TapChg is conditional optional in AVCO; alternate possibility is to control the voltage with a setpoint. 25 Mar 13 Discussion (red)
It was mainly the use of TapChg that I opposed to.
AVCO is said to be "a voltage controller independent of the control method being used". But the inclusion of the Mandatory TapChg assumes that the function is controlling a tap changer and for that it exist the ATCC. This rules out any other methods for controlling the voltage.
I can agree to that maintaining TapChg in AVCO if it is made Optional so it will be possible to include another DO that suites better for the used method.
25 Mar 13 Discussion (red)
22 Mar 13 Discussion (red)
With the UML exercise, I think we've made this uniform for all 6 DOs TapChg. Below the text generated from UML for the DO semantic table with UML 02v12 (note: I've just fixed in UML 02v13 the doc for YLTC.TapChg to read the same as the others):

(YEFN) (controllable) Tap position adjustment in given direction (raise, lower), or adjustment stop (stop).
(YLTC) Operating with value in 'ctlVal' initiates the tap position adjustment in given direction (raise, lower), or stops it (stop). The change of its status value indicates the result of operation.
(ANCR) (controllable) Tap position adjustment in given direction (raise, lower), or adjustment stop (stop).
(ARCO) (controllable) Tap position adjustment in given direction (raise, lower), or adjustment stop (stop).
(ATCC) (controllable) Tap position adjustment in given direction (raise, lower), or adjustment stop (stop).
(AVCO) (controllable) Tap position adjustment in given direction (raise, lower), or adjustment stop (stop).
15 Mar 13 Triage

 

Privacy | Contact | Disclaimer

Tissue DB v. 23.12.13.1