UCAIug Issue Tracking System: Issueshttps://redmine.ucaiug.org/https://redmine.ucaiug.org/favicon.ico?15861924492024-03-28T13:34:58ZUCAIug Issue Tracking System
Redmine WG16 Issues - CIM Issues #6745 (New): Need for consistent approach for Market Productshttps://redmine.ucaiug.org/issues/67452024-03-28T13:34:58ZScott Coe
<p>Market Products are not used consistently in the CIM because market products are not really consistent across markets...</p>
<p>Energy is the universal commodity; however, even when considering universal grid support products the names vary. In the North America, they call the load frequency control the Regulation product, but in Europe is is Secondary Reserve. Standby/emergency reserve products are more varied. Tertiary Reserve in Europe is split into Synchronous and Non-Synchronous Reserve in the North America. But in even in North America, there is inconsistent usage. PJM calls it Synchronized/Non-Synchronized, MISO and SPP have Spinning and Supplemental, NYISO/ISO-NE/CAISO use Spinning and Non-Spinning, and finally ERCOT has Responsive and Non-Spinning.</p>
<p>One of the oldest market enumerations, MarketProductType does not follow the typical format. We have: EN, RU, RD, SR, NR, RC, LFU, LFD, REG, RPU, CO2e, RMU, and RMD. Changing to Energy, RegulationUp, RegulationDown, SynchronousReserve or SpinningReserve, NonSynchronousReserve or NonSpinningReserve, ReliabibilityUnitCommitment, LoadFollowingUp, LoadFollowingDown, CarbonDioxideEquivalent, RegulationMileageUp, and RegulationMileageDown would break things.</p>
<p>Then we have a similar enumeration: ResourceCapacityType. RU, RD, SR, NR, MO, FO, RA, RMR which map to RegulationUp, RegulationDown, SynchronousReserve or SpinningReserve, NonSynchronousReserve or NonSpinningReserve, MustOffer, FlexibleOffer, ResourceAdequacy, and ReliabilityMustRun. Clearly a different use, but some of the concepts here overlap.</p>
<p>Finally, the most recent is ResourceCertificationKind which allows us to flag when a resource is certified to provide a service. Here the enumeration is properly formatted (all but one entry, that is) and again have a strong correlation to products: RegulationUp, RegulationDown, SpinningReserve, NonSpinningReserve, ReliabilityMustRun, BLACKSTART, DemandSideResponse, SynchronousCondenser, ReliabilityUnitCommittment, Energy, Capacity.</p> WG14 Part 3 Issues - CIM Issues #6744 (New): CrewStatusKind enumeration is missing values for dea...https://redmine.ucaiug.org/issues/67442024-03-26T16:56:48ZMartin Millermartin.miller@glires.com
<p>The current CrewStatusKind enumeration only contains entries for assignment of crews and the only value (fieldComplete) that represents the deassignment of a crew also represents the completion of work. It is missing any entries that represent the deassignment of a crew without completement of work.</p>
<p>At a minimum the enumeration needs an additional value to represent the concept of "Deassigned" which means that "the crew is no longer working on the outage in the field, without the outage being corrected". <br />Ideally, there would also be a second additional value to represent the concept of "Rejected" which means that "the crew has refused an assignment."</p> IEC 61850 User Feedback Task Force - Feature #6739 (New): How to deal with 'Beh' and 'Health' of ...https://redmine.ucaiug.org/issues/67392024-03-18T10:37:35ZMichael Haecker
<p>For site testing, users shall use the test mode to isolate devices/functions to prevent from flooding control centres with test data.</p>
<p>Whereas data marked "test" can be filtered out, changes of 'Beh' cannot be filtered out. When, for example, changing the active parameter set, the user will create data towards the control centre for LN instances which are activated/inactivated through this change.<br />[Part 7-4 Annex A: "Regardless of the status of LN.Beh, the quality test attribute of Mod, Beh and Health shall be q.test=false."]</p>
<p>In an automation system where a gateway is used to interface the control centre, this gateway could implement a feature to block the information flow of a device in test. Where a direct link via IEC 61850 is used, such blocking is not possible.</p> IEC 61850 User Feedback Task Force - Improvement #6738 (New): Amending TGSN LN class with setting...https://redmine.ucaiug.org/issues/67382024-03-18T10:14:44ZMichael Haecker
<p>The LN classes TCTR and TVTR inherit from 'InstrumentTransformerLN' some settings which can be used for adapting the output signal.</p>
<p>TGSN LN class is missing the settings for scaling, linerarization, wideing of a focussed range.</p> IEC 61850 User Feedback Task Force - Bug #6737 (New): Amending TGSN LN class with signal characte...https://redmine.ucaiug.org/issues/67372024-03-18T09:57:10ZMichael Haecker
<p>The model of a generic sensor does not provide characteristics about the analogue signal type which is used to receive the sensor value.</p>
<p>TC57/WG18 are proposing to amend the model with a setting to state the analogue signal type.</p> WG13 Issues - CIM Issues #6736 (New): Quality61850 Class does not match the definition of Quality...https://redmine.ucaiug.org/issues/67362024-03-12T21:05:03ZTom Berry
<p>CIM definition is missing Inconsistent, Inaccurate Boolean<br />IEC 61850 does not define Source = DEFAULTED</p>
<p>Encoding is now<br />/*
* Bit(s) Name Value<br /> 0-1 Validity Good 0 0<br /> Invalid 0 1<br /> Reserved 1 0<br /> Questionable 1 1<br /> 2 Overflow<br /> 3 OutofRange<br /> 4 BadReference<br /> 5 Oscillatory<br /> 6 Failure<br /> 7 OldData<br /> 8 Inconsistent<br /> 9 Inaccurate<br /> 10 Source Process 0<br /> Substituted 1<br /> 11 Test<br /> 12 OperatorBlocked<br /> */</p> WG16 Issues - CIM Issues #6735 (New): new disclaimer note on every Inf* UML diagram indicating to...https://redmine.ucaiug.org/issues/67352024-03-11T19:54:31ZBecky Iverson
<p>We need to indicate the usage of Inf in a more explicit way to avoid confusions.</p> WG16 Issues - CIM Issues #6734 (New): Review use/inheritance of Document by UCA TF 16 classes, pr...https://redmine.ucaiug.org/issues/67342024-03-11T14:58:20ZBecky Iverson
<p>UTF 14 is reviewing all classes that are inheriting from Document and has request UTF 16 to review the use of Document class.</p> CIM Joint Issues - CIM Issues #6730 (New): Evaluation of the Pipeline Open Data Standard (PODS)https://redmine.ucaiug.org/issues/67302024-03-07T17:09:26ZDavid Haynes
<p>An organization that has a "pipes model" has been located. All of the WGs interested in Redmine issue <a class="issue tracker-9 status-1 priority-2 priority-default" title="CIM Issues: Multi-commodity Support (New)" href="https://redmine.ucaiug.org/issues/6729">#6729</a> should consider [[<a class="external" href="https://pods.org/">https://pods.org/</a>]] . <br />The PODS organization was funded by oil and gas companies in an effort to make an "open" pipeline standard, suitable to carry GIS data.<br />They use Enterprise Architect to maintain their model. They also can provide the model in the form of a data base.<br />Descriptions of their model and organization are attached.<br />Their IP rules are different than the UCAIug. It is copyrighted and only joined members (of the PODS association) may use the model. <br />It doesn't appear that they publish written documents with an SDO like the CIM UG does with the IEC. Nevertheless, according to their website, there are over 200 implementations in 36 countries.</p>
<p>Is there an interest in a liaison between the CIM UG and PODS? If so, what would we like to share?</p> CIM Joint Issues - CIM Issues #6729 (New): Multi-commodity Supporthttps://redmine.ucaiug.org/issues/67292024-03-07T16:57:20ZDavid Haynes
Many utilities sell multiple commodities (electricity, gas, water, and more). Many vendors make products that support more than one commodity. <br />The issue has been batted around for years within WG14 and the issue raised at a CAG meeting. The IEC managers would like usecase information around this subject.<br />We think there is potentially some common use cases to be found in the areas of:
<ul>
<li>Meter Reading and Control</li>
<li>Asset Management</li>
<li>Work Management</li>
<li>Energy Planning (EMS/DMS)</li>
<li>SCADA</li>
<li>Energy markets</li>
</ul>
<p>In addition to potential usecase capture, we should think about how much energy should be expended within the CIM to support multiple commodities, or should another WG with another model be sought to become a partner, and merely map the two models at some prescribed interface?</p> Client - Issues #6728 (New): cSg13 refers to PIXIT entry Sg5/Sg6 but not clarified in the expecte...https://redmine.ucaiug.org/issues/67282024-03-05T12:34:33ZRichard Schimmel
<p>The expected result requires the client to read the SGCB.resvTms but that is optional according to PIXIT Sg6! The PIXIT entry Sg6 has no Edition indication. So when PIXIT says No the client will fail the expected result.</p>
<p>Propose: update the expected result to allow PIXIT Sg6=No behavior. Update the PIXIT Entry Sg6 edition.</p> Client - Issues #6727 (New): cDsN1bc, cFtN2 have no non-Ed2 specific error codehttps://redmine.ucaiug.org/issues/67272024-03-05T12:26:20ZRichard Schimmel
<p>Same as for cSrvN10 also cDsN1b/cDsN1c (MMS GetNameList) and cFtN2 (MMS fileDirectory) have no Ed1 specific error code.<br />I propose to deprecate these test cases just like cSrvN10.</p> WG13 Issues - CIM Issues #6632 (New): update definition of deprecatedhttps://redmine.ucaiug.org/issues/66322023-12-11T10:49:27ZSvein Olsen
<p>IEC 61970-301 defines <<deprecated>> as:<br />“4.7.5 Deprecations<br />The CIM model may at times contain packages, classes, attributes, or associations that have been identified as deprecated. These items will be noted in the documentation or with a UML stereotype of “deprecated”. A deprecated item is retained in the present version of the model, but is expected to be removed from future versions. An item that has not been deprecated is not guaranteed to be retained in future versions, but using an item marked as deprecated should be avoided if possible."</p> WG13 Issues - CIM Issues #6616 (New): Add SubstationKindhttps://redmine.ucaiug.org/issues/66162023-11-30T16:45:11ZSvein Olsen
<p>There is a need to provide substation categorization. The IEC Electropedia is including different type of categories. There are different implementation extensions that include it. As part of TF 14 Part-7 Design work it is relevant to have a consistent categories for substation.</p> WG14 Part 9 Issues - CIM Issues #6549 (New): Switch Contention Issuehttps://redmine.ucaiug.org/issues/65492023-10-24T22:26:02ZDavid Haynes
<p>There are many relays controlling many loads. Sometimes these assets can be switched on or off for different reasons. While working on lines, it is a common practice to employ "lock out / tag out" procedures. In this scenario, the workman physically places a padlock on a switch to prevent its movement. Then, at the end of the job the workman physically removes his padlock to restore normal operation of the switch. While the safety issue is nicely handled by the physical locks, an operational issue still remains. What if a CIS declares that a particular RCD switch inside of a revenue meter is to be opened due to non-payment. Then what if this same switch is made available to the DERMS for load control purposes? A DR system might (even as part of a group) ask that the switch participate in a load shed, then upon completion, that the switch be closed in. What is the switch to do? How would it know to revert to an open position? What if that is obsolete information? What are the expectations for the AMI network / load control system? Should there be a "system of record" that is the official keeper of allowable switching activity? Should there be the means for a back office system to effectively place a "lock" on a switch position and prevent other back office systems from operating it? Can multiple systems place locks similar to the physical lockout/tagout mechanism described above? Or rather, should there be a "list"? Should there be a "do not open" list and a "do not close" list? (Someone might be on life support, someone may have moved out, etc.)<br />Meters con not only have a big 200A disconnect, they might have a number of small relays designed to control individual loads like irrigation pumps, or anything else the utility wires them to.<br />There are also specialized switches the AMI network might control -- usually installed beneath a given revenue meter -- to control smaller loads within a home. Should these be lockable too?<br />We can't have multiple systems fighting over the switch position. We need a switch management plan.</p>
<p>This issue is related to Issue <a class="issue tracker-9 status-1 priority-2 priority-default" title="CIM Issues: Group Management (New)" href="https://redmine.ucaiug.org/issues/6542">#6542</a>.</p>
<p>For discussion purposes, we think the scope of this issue is limited to switches that are not on the feeder that a lineman could interact with. These switches are covered by Part 3. But there are switches that are otherwise safe to operate that are in scope.</p>