UCAIug Issue Tracking System: Issueshttps://redmine.ucaiug.org/https://redmine.ucaiug.org/favicon.ico?15861924492024-02-20T17:04:44ZUCAIug Issue Tracking System
Redmine IEC TC57 WG10 Future Work - WG10 Future Work #6714 (New): Improve the models used for power regul...https://redmine.ucaiug.org/issues/67142024-02-20T17:04:44ZMichael Haecker
<p>LN class ATCC offers a big model of an automation to control a transformer tap changer. It is tailored towards voltage regulation, but does not address (not limited to)<br />- regulation on the principle of reactive power<br />- regulation on the principle of active power<br />- regulation of parallel transformers (cf. IEEE C57.153).</p>
<p>Separate from the ATCC model, individual LN classes exists (AVCO, ARCO e.g.) dealing with regulation principles, but without the data for controlling a given primary equipment. These LN classes can be used for regulating any equipment (transformers, capacitor banks, Petersen coils, resistors e.g.), but they are not as complete as the ATCC model.</p>
<p>The models should be completed and possibly harmonized to an overall modelling concept of power regulation, considering the compatibility aspect for existing implementations.</p> IEC TC57 WG10 Future Work - WG10 Future Work #6703 (New): Part 80-4 Mapping to COSEM : add reacti...https://redmine.ucaiug.org/issues/67032024-02-09T20:43:03ZTom Berry
<p>IEC TS 61850-80-4 Translation from the COSEM object model (IEC 62056) to the IEC 61850 data model<br />recommends adding these data objects to MMTR and MMTN</p>
<p>VArhQ1 BCR Reactive Energy QI O 1-b:5.8.0.255<br />VArhQ2 BCR Reactive Energy QII O 1-b:6.8.0.255<br />VArhQ3 BCR Reactive Energy QIII O 1-b:7.8.0.255<br />VArhQ4 BCR Reactive Energy QIV O 1-b:8.8.0.255<br />SupVAh BCR Apparent Energy- (QII+QIII) O 1-b:10.8.0.255<br />DmdVAh BCR Apparent Energy+ (QI+QIV) O 1-b:9.8.0.255</p> IEC TC57 WG10 Future Work - WG10 Future Work #6701 (New): Integration of proposed and canceled am...https://redmine.ucaiug.org/issues/67012024-02-08T11:25:23ZVladan Cvejic
<p>Reminder: Integration of proposed and canceled amendment 2 of part 7-3</p> IEC TC57 WG10 Future Work - WG10 Future Work #6700 (New): Investigate to align to the new CIM mod...https://redmine.ucaiug.org/issues/67002024-02-08T08:43:27ZAurelie Dehouck
<p>The Model of PowerTransformers changed after CIM v15 (for the reasons explained bellow).</p>
<p>SCL model of CIM PowerTransformer is aligned to older model.</p>
<p>Investigate to align with this new model for harmonization.</p>
<hr />
<p>Copied from "Common Information Model (CIM) Primer: Eighth Edition" - EPRI (<a class="external" href="https://www.epri.com/research/products/000000003002006001">https://www.epri.com/research/products/000000003002006001</a>)</p>
" <br /><strong>Transformers After CIM v15</strong><br />As the CIM has moved beyond its original roots in modeling balanced transmission networks into the distribution world there was a desire to create a single, harmonized transformer model that is:
<ul>
<li>Suitable for phase balanced or unbalanced networks</li>
<li>Suitable for representing unbalanced construction commonly used for low voltage distribution networks</li>
<li>Allows for simultaneous representation of network components as both balanced and unbalanced depending upon the level of detail desired (that is, when performing detailed phase unbalance studies on nominally balanced high voltage networks, or for modeling the transition between balanced and unbalanced representations)</li>
</ul>
<p>A group of experts worked on an update to the CIM transformer model to reflect these requirements, which was then integrated into the draft of CIM v15.</p>
<strong>Changes to Transformer Model</strong><br />There are a number of significant changes compared with the previous model that was described in the previous section:
<ul>
<li><strong>PowerTransformer</strong> now inherits from <strong>ConductingEquipment</strong> rather than Equipment so the <strong>Terminals are now associated with the PowerTransformer rather than the windings</strong> as with the previous representation.</li>
<li><strong>TransformerWinding</strong> now <strong>renamed to TransformerEnd</strong> . This is because the term winding was felt to imply that the model represented the internal configuration of the transformer, but in reality the TransformerWinding was really describing the transformer’s terminals. Since the term Terminal is already used in the CIM TransformerTerminal would have been confusing and ambiguous so the term TransformerEnd was used instead.</li>
<li>Additional classes were added to model transformer tanks, typically used in distribution systems where a single transformer contains multiples tanks each with its own TransformerTankEnds.</li>
<li>The transformer impedance and admittance attributes as star or mesh explicitly. Previously these attributes appeared on the TransformerWinding<br />class which meant that on a two-winding transformer the impedance between the primary and secondary windings would be put on the primary<br />winding with zero values on the secondary winding.</li>
<li>Impedances and admittances can be defined once and re-used across multiple instances, reflecting the concept of catalogues of common values that are used across multiple instances in distribution networks. The ability to explicitly define impedance and admittance values on the TransformerEnd is still maintained.</li>
<li>The TapChanger model is expanded to explicitly model not only ratio and phase tap changers explicitly but also specializations of PhaseTapChanger for symmetrical and asymmetrical models.</li>
</ul>
<p>"</p> IEC TC57 WG10 Future Work - WG10 Future Work #6613 (New): IEC61850 Tissue 1833: Service SettingGr...https://redmine.ucaiug.org/issues/66132023-11-28T13:48:46ZCamille Blochcamille.bloch@se.com
<p>Discussion in the tissue hihlighted:<br />"The solution proposed 05 Oct 22 (Marked with status Approval(Editorial)) does not allow SCL file to "remember" the value from the ICD file and therefore does not provide a mechanism to later increase numOfSGs after decreasing them.</p>
<p>One suggestion would be require that the SCT create a new optional attribute containing the value from ICD file whenever numOfSGs was decreased. SCT would never be allowed to modify this new attribute value but could use it to later increase numOfSGs.<br />One issue could be that ICT would refuse the SCD file because it contained an attribute prohibited in the schema declared in originalSCLxxx attribute.</p>
<p>Second suggestion is to not allow SCT to reduce the count of numOfSGs."</p> IEC TC57 WG10 Future Work - WG10 Future Work #6604 (New): IEC61850.Tissue #1754 Event driven sche...https://redmine.ucaiug.org/issues/66042023-11-21T06:48:52ZVladan Cvejic
<p>Part 7-4, page 169, clause 6.6.9, table 70:<br />The type of the external trigger InSyn in Table 70 is not defined.</p>
<p>Note: InSyn is also used for Statistical LN … but the definition there is not applicable for scheduling.</p>
<p>“F.3.2.3 External synchronization” defines BOOLEAN … and the behavior only for statistical LN … NOT for FSCH!</p> IEC TC57 WG10 Future Work - WG10 Future Work #6579 (New): How to add utility process name to DOshttps://redmine.ucaiug.org/issues/65792023-11-07T14:40:47ZVladan Cvejic
<p>Currently SCL has poor support for handling gateway/RTU-funktions where signal names are translated for remote communication. The specified sigal has a utility process name independent of used protcol. E.g. "start of distance protection". This needs to be associated with its IEC 61850 implementation (xxPDIS1.Str.general, xxPDIS2.Str.general etc.). The 80-1 part describes how 104 addresses can be added to SCL but also other utility fields are important to be able to include in SCL for specification and documentation purposes. Desired solution by Vattenfall is to have vendors use DA description to add utility process name.</p> IEC TC57 WG10 Future Work - WG10 Future Work #6578 (New): Extension of the AddCause required to r...https://redmine.ucaiug.org/issues/65782023-11-07T14:27:54ZVladan Cvejic
<p>During the review of the control model of the Proxy/Gateway in IEC 61850-80-6 we found that the existing enumeration for the AddCause does not include values to reflect the situation where the Proxy/Gateway issues a negative confirmation to the control center client when the communication with the underlying IED that executes the command is disturbed, or the connection to the device is lost. <br />This issue is not only relevant for the communication to the control center, but on always when the control action involves more than one communication level, e.g. Substation Scada to Breaker IED via an bay controller IED. <br />Attached is a slide set which explains the need and proposes the new enumerated values for the AddCause.</p> IEC TC57 WG10 Future Work - WG10 Future Work #6561 (New): Modeling of primary equipmenthttps://redmine.ucaiug.org/issues/65612023-10-26T09:20:27ZVladan Cvejic
<p>With regards to the modeling - to take into account differences between communication interface of equipment and model of the same primary equipment.<br />To be in line with CIM modeling (harmonization with 61850 aspects).<br />Primary equipment nameplate info in electronic format (accessible from SCL file).</p>
<p>JWG work, new TF?</p> IEC TC57 WG10 Future Work - WG10 Future Work #6524 (New): https://iec61850.tissue-db.com/tissue/6...https://redmine.ucaiug.org/issues/65242023-09-15T14:30:41ZHenry Dawidczak
<p>In tissue <a class="issue tracker-5 status-5 priority-2 priority-default closed" title="Issues: T1702 - Limit LTRK to one instance on a server (Closed)" href="https://redmine.ucaiug.org/issues/670">#670</a> (tissues of Part 7-4 ed.2) the idea is confirmed to create a new DO SetMod (State GREEN, for edition 3). <br />The DO was not included in Edition 2.1.</p> IEC TC57 WG10 Future Work - WG10 Future Work #6448 (New): GOOSE treatment as a commandhttps://redmine.ucaiug.org/issues/64482023-06-21T09:46:02ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724220">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724220</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #6447 (New): Enhanced Quality Information for Measur...https://redmine.ucaiug.org/issues/64472023-06-21T09:44:53ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724795">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724795</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #6446 (New): SCL Modelling of Fault Measurements (RFMX)https://redmine.ucaiug.org/issues/64462023-06-21T09:44:13ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724779">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724779</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #6441 (New): Extensions to "Z" Logical Nodes (e.g. ...https://redmine.ucaiug.org/issues/64412023-06-21T09:39:17ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/719080">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/719080</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #6439 (New): Inter-substation GOOSE Naming conventio...https://redmine.ucaiug.org/issues/64392023-06-21T09:37:25ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724752">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724752</a></p>