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 Issues - CIM Issues #6621 (Review): Add the Design sub-package to the Enterprise packagehttps://redmine.ucaiug.org/issues/66212023-12-05T19:18:02ZHenry Dotson
<p>Sufficient work has been completed by the Part 7 working group to add the "Design" sub-package to the "Enterprise" package and indicate its dependencies on other "Enterprise" sub-packages.</p> WG14 Issues - CIM Issues #6620 (New): Enterprise Package Name Related Model Updateshttps://redmine.ucaiug.org/issues/66202023-12-05T19:07:35ZHenry Dotson
<p>The CIM UML model package name change from "IEC61968" to "Enterprise" has created the need to update some model element names for consistency.</p> CIM Joint Issues - CIM Issues #6584 (New): Handling unit multiplier needs joint WG concensus on a...https://redmine.ucaiug.org/issues/65842023-11-08T12:55:38ZTodd Viegut
<p>Handling unit multiplier</p>
<p>WG13 needed a policy with respect to how unit multpliers are to be exchanged. For example CDPSM has need for Length to be in <strong>km</strong> for line length, but in <strong>meters</strong> for conductor spacing. IEC 61970-552 does not provide for the exchange of unit symbols or unit multpliers. Therefore, manual documentation is required in profiles. Possibly different model parts assembled together may have different unit multipliers such as combining a distribution and transmission model together. With current work in progress for the upcoming IEC 61970-301 Ed 8.0 (i.e. CIM18) and the accompanying editions of IEC 61970-452, IEC 61970-456, etc. there is the planned introduction of the new unbalanced profiles which will require concensus on an approach.</p>
<p>WG13 has issue: <a class="external" href="https://redmine.ucaiug.org/issues/5014">https://redmine.ucaiug.org/issues/5014</a> for addressing this cross-cutting concern within the context of WG13. This CIM Joint issue is to raise visibility across WG14, WG16, WG21 so that we have a common understanding/policy for how we will address this.</p> WG13 Issues - CIM Issues #6553 (New): Removal of InfGrid package InfSIPShttps://redmine.ucaiug.org/issues/65532023-10-25T19:55:45ZBecky Iverson
<p>CIM17 included a proposed set of modeling to support SIPS in the InfGrid package. In CIM18, this package has been removed. It is understood that there is a new Inf package for ENTSO-E extensions that may have some of the similar modeling support for SIPS, but without the existing InfSIPS package that existed in CIM17, there is no way to harmonize or compare the SIPS support between the different modeling suggestions. Please return the InfSIPS package to the InfGrid package for use in the upcoming modeling sessions for review of SIPS support to be included in the Grid->Base package.</p> 61850-7-5 and 61850-7-500 - IEC61850-7-5 #6377 (New): Update the Switchgear / Breaker Modelhttps://redmine.ucaiug.org/issues/63772023-06-14T13:17:15ZVladan Cvejic
<p>There exist the LNs XCBR/XSWI ("operative model") and the "supervision" LNs SCBR and SOPM. In addition, there are trip and control circuits. The number of instances needed depends on the switchgear technology (single phase switching/tripping and three phase control/tripping). The DOs in the LNs are not always in line with allocated tasks of the LNs. Therefore, a careful consistent and comprehensive remodeling is needed.</p> CIM Joint Issues - CIM Issues #6372 (New): Inconsistencies in Nameplate data for DERshttps://redmine.ucaiug.org/issues/63722023-06-12T13:18:19ZScott Coe
<p>Perhaps an issue for other equipment as well, but at least for DERs there is confusing modelling of DER nameplate data in the Dynamics sub-package of the Grid Package. DERNameplateData includes fields such as "acVmax" and "reactiveSusceptance" which seem to be not exclusive to dynamic response. Furthermore, this data appears to me to be more related to the asset world, and perhaps should be modelled as DER Datasheet info, rather than in Grid.</p>
<p>A related issue is that similar data appears in "DERNameplateDataApplied", also in dynamics. This represents the settings information which are bounded by the manufacturer limits, but can be configured (presumable at install but perhaps also via software controls) as protection settings are re-evaluated by the utility.</p> WG14 Issues - CIM Issues #5967 (Review): Refactoring of Contact Informationhttps://redmine.ucaiug.org/issues/59672022-09-13T14:54:51ZHenry DotsonCIM Joint Issues - CIM Issues #5963 (Review): mRID topics [incl GMDM #19]https://redmine.ucaiug.org/issues/59632022-09-12T14:09:24ZYang Feng
<p>The usage of mRID has been brought up during the GMDM IOP and followings are the topics to be covered</p>
<p>• Should the UML be changed to make the mRID a UUID instead of a string?<br />• The omission of mRID in favor of rdf:ID/rdf:about has been inadequately canonized. How can we canonize this in a way that does not retroactively break anyone’s software? <br />• When the mRID is included, what should be done when the mRID value does not exactly match the fully-expanded rdf:ID/rdf:about?<br />• What should be done for mRIDs that are not UUIDs but that do not correctly override the xml:base?<br />• What should be done when a 61968-100 mRID does not conform to the xml:base nor exactly match the fully-expanded rdf:ID/rdf:about?</p> WG13 Issues - CIM Issues #5375 (In Progress): Clean up transformer documentation - Margaret remov...https://redmine.ucaiug.org/issues/53752022-06-02T20:54:18ZYang Feng
<p>Margaret has decided to remove the some of the paragraphs describing distribution network models (e.g., distribution transformer, tap changer... more can be found in the attached document) from Part-11 documents.<br />These paragraphs should be reviewed and re-applied to where they fit, either in 301 or Part-13 document.</p>
<p>Pat Brown wrote<br />This Redmine issue is focused on cleaning up transformer documentation that currently exists in multiple locations: 61970-301 template, 61968-11 template, 61970-452 template, 61968-13 template and UML. <br />Other Redmine issues focus on transformer modelling improvements (esp. for transformers modelled with tanks):<br /> - Redmine 5302: association from TransformerTank to TransformerTankInfo<br /> - Redmine 6147 [GMDM #1]: streamlining of tank-based transformer modelling<br /> - Redmine 6148 [GMDM #2]: TapChanger and TapChangerInfo .ctRatio, .ptRatio attributes<br /> - Redmine 6341 [GMDM #4]: support for transformer type description / derivation</p> WG14 Issues - CIM Issues #5318 (Review): Address modeling is too complexhttps://redmine.ucaiug.org/issues/53182022-02-22T15:55:50ZHenry Dotson
The compound datatypes ElectronicAddress, StreetAddress, StreetDetail, TownDetail, and TelephoneNumber have the following deficiencies:
<ol>
<li>StreetAddress has attributes that have other compound address datatypes</li>
<li>ElectronicAddress is not flexible</li>
</ol> WG13 Issues - CIM Issues #5309 (In Progress): Support on FACTS device modelinghttps://redmine.ucaiug.org/issues/53092022-02-07T03:03:16ZYang Feng
<p>Generic FACTS device modeling is currently not available and need to be supported, while only its specialty SVC is supported. It contains, e.g., Static Synchronous Series Compensator (SSSC), Unified Power Flow Controller (UPFC), Thyristor-Controlled Series Capacitor (TCSC), Static Synchronous Compensator (STATCOM), and etc.</p>
<p>Wiki Reference: <a class="external" href="https://www.sciencedirect.com/topics/engineering/flexible-ac-transmission-systems#:~:text=FACTS%20devices%20are%20static%20power,congestion%20management%20and%20loss%20optimization">https://www.sciencedirect.com/topics/engineering/flexible-ac-transmission-systems#:~:text=FACTS%20devices%20are%20static%20power,congestion%20management%20and%20loss%20optimization</a>.</p> WG14 Part 4 Issues - CIM Issues #5264 (Review): ProcedureStep and revision of Procedurehttps://redmine.ucaiug.org/issues/52642022-01-13T14:40:48ZHerbert FalkWG14 Part 4 Issues - CIM Issues #5255 (Review): ProcedureStep and revision of Procedurehttps://redmine.ucaiug.org/issues/52552022-01-13T14:38:01ZHerbert FalkWG14 Part 11 Issues - CIM Issues #5250 (In Progress): Document identificationhttps://redmine.ucaiug.org/issues/52502022-01-13T12:39:41ZHerbert Falk
<p>Provide the ability for any number of individual documents to be associated to various objects (e.g. Assets to a drawing, specification sheet, PowerSystemResource, Location, etc.) (26)</p>