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 #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 #6435 (New): Compression of Sample Value Messageshttps://redmine.ucaiug.org/issues/64352023-06-21T09:34:08ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/719272">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/719272</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #6419 (New): Logical Nodes for SLD/Topology Aware Fu...https://redmine.ucaiug.org/issues/64192023-06-21T09:09:56ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724217">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724217</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #6413 (New): Asset Management of Setting & Configura...https://redmine.ucaiug.org/issues/64132023-06-21T08:40:06ZVladan Cvejic
<p>Link to Collaboration tool discussion:<br /><a class="external" href="https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724241">https://collaborate.iec.ch/#/pages/workspaces/137211/documents/145326/details/539706/discussions/724241</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #6265 (New): track changes in SCL to know when a dev...https://redmine.ucaiug.org/issues/62652023-02-14T15:06:05ZCamille Blochcamille.bloch@se.com
<p>Following discussion in Kansas City about the usage of ConfRev for gooses, it has been clearly identified that ConfRev is an indicator for runtime about change which may have an impact on the runtime but without other way to identify it. This is way today, ConfRev is limited to Dataset update tracking.</p>
<p>Regarding the engineering of the system, this is not enough to identify when a device needs to be updated after a new version of the SCD.</p>
<p>We need for example to know each time a communication parameter of a goose has change imply the reconfiguration of the subscribers of the goose message.</p>
<p>As ConfRev is related to runtime, we need an additional mechanism.</p>
<p>A proposal has been done in 2017 which was never implemented in SCL. We need to review it and integrate the link with the new SCL version tracking bring with Ed2 AMD 2</p> IEC TC57 WG10 Future Work - WG10 Future Work #5966 (New): Indicate typical SIUnit for every DO wi...https://redmine.ucaiug.org/issues/59662022-09-13T14:04:13ZVladan Cvejic
<p>In IEC61850-7-4, some DO with CDC MV have a SIUnit that is indicated in the description of the DO.</p>
<blockquote>
<p>Example : in MMET, DO EnvTmp of CDC MV has the description : "Temperature of environment [°C]."</p>
</blockquote>
<p>But a lot do not have any.<br />It would be interesting for the comprehension of the semantic of the DO, to indicate a SIUnit for every DO with CDC MV (or indicate clearly if it has no unit)</p>
<hr />
<p>In addition, it could be interesting to add a dedicated attribute for this purpose, in the NSD files, instead of having this information in the description</p> IEC TC57 WG10 Future Work - WG10 Future Work #5965 (New): Schedules - allow updates to single val...https://redmine.ucaiug.org/issues/59652022-09-13T13:11:36ZVladan Cvejic
<p>Context: how to use IEC 61850 for DER and microgrids (IEC 61850-90-23 CD1).</p>
<p>IEC 61850-7-4 prescribes that schedules may only be updated whilst they are offline. This is a conservative approach that allows for validation of all the settings to ensure consistency before re-starting i.e. evaluating the schedule output. <br />There are two approaches:<br />1. Stop the running schedule; change it, restart<br />2. Write to another schedule with a higher priority and start that; stop the original schedule; change it, restart it; stop the second schedule.</p>
<p>This approach is unnecessarily complex for some cases. A common use case is to update a schedule for one or more periods in the future. In these cases, updating individual schedule values will not affect the current schedule output, so there is no need to require the schedule to be deactivated and reactivated.</p>
<p>See also <a class="issue tracker-4 status-2 priority-2 priority-default overdue" title="Improvement: Need to Change 8-1 to allow multiple DOs to be written (In Progress)" href="https://redmine.ucaiug.org/issues/3098">#3098</a></p> IEC TC57 WG10 Future Work - WG10 Future Work #5928 (New): CIM-61850 Harmonization - extend tPhase...https://redmine.ucaiug.org/issues/59282022-08-09T13:05:41ZVladan Cvejic
<p>IEC 62361-102 Recommendation R9</p>
<p>The SCL enumeration for phases is more restricted than the PhaseCode enumeration defined<br />in the CIM. It suits the physical equipment found in large substations but is inefficient for<br />modelling equipment found in distribution networks or consumer premises. At present users<br />are forced to define sets of Equipment and SubEquipment instances in order to model single<br />real-world devices.</p> IEC TC57 WG10 Future Work - WG10 Future Work #5927 (New): CIM-61850 Harmonization - Add PosFlwIn ...https://redmine.ucaiug.org/issues/59272022-08-09T13:02:28ZVladan Cvejic
<p>IEC 62361-102 Recommendation R15</p>
<p>8.5 Direction of positive flow<br />8.5.1 General<br />The Measurement logical nodes that supply measurements of power and current do not have any settings/configuration to indicate the direction of positive flow relative to the primary equipment connectivity.<br />It is common practice to indicate the earthing point (terminal) of CTs in the drawings, which is either 'towards the busbar' or 'towards the line'. All other engineering artefacts must follow the given/defined scheme for the project. As IEC 61850 is focussed on the functions rather than on the type of bays, there is no means to indicate the producer/consumer use of them. TVTR and TCTR, which could be the appropriate LNs to host this information, do not include it today.<br />For physical devices, the international convention is to use the terminal designations ‘P1’ and ‘P2’ on the primary, ‘S1’ and ‘S2’ on the secondary side, where ‘1’ is the one closer to the energy source.</p>
<p>The CIM attribute is named “Analog.positiveflowin” and has the following definition:<br /><em>If true then this measurement is an active power, reactive power or current with the convention that a positive value measured at the Terminal means power is flowing into the related PowerSystemResource.</em></p> IEC TC57 WG10 Future Work - WG10 Future Work #5904 (New): Introduce alarm and counter DOs in 7-4https://redmine.ucaiug.org/issues/59042022-07-14T15:27:15ZBenoît Lepeuple
<p>Based on the outcome of the 90-18, IEC 61850 ed3 is the good time to introduce alarm DOs based on the ALM CDC and counter DOs in 7-4.</p>
Potential work items:
<ul>
<li>Establish a preliminary list of candidate DOs by searching the term 'alarm' in DO description or 'alm' in DO names. These are #1 candidates. Todo based on 7-4 and 90-x documents/models</li>
<li>Have experts review existing logical nodes and establish a list of additional alarms.</li>
</ul>
<p>The same goes for counters with the CNT CDC: New DOs for counting of time-in-state and number-of-state-changes where relevant</p> IEC TC57 WG10 Future Work - WG10 Future Work #5103 (New): Modified/new CDC for IEEE H27https://redmine.ucaiug.org/issues/51032021-10-08T07:27:57ZMichael Haecker
<p>From WG 10 meeting October 2021, IEEE H27</p>
<p>Preliminary registration</p>
<p>PC37.251 defines CDC which deviate from the ones standardized in IEC 61850-7-3.<br /> ING<br /> VSG<br />(possibly also ASG: additional user configurable value limits, see also TF UF item 'F 5089')</p>