UCAIug Issue Tracking System: Issueshttps://redmine.ucaiug.org/https://redmine.ucaiug.org/favicon.ico?15861924492024-01-05T13:58:15ZUCAIug Issue Tracking System
Redmine Market Management - CIM Issues #6667 (New): Add an association from ChargeType to Periodhttps://redmine.ucaiug.org/issues/66672024-01-05T13:58:15ZJan Owe
<p>Billing characteristics will consist of different prices for different periods. Associating ChargeType with Period will make it possible to have one or more prices for a period for the charge.</p> Market Management - CIM Issues #6664 (New): Add an association from MktActivityRecord to ChargeGrouphttps://redmine.ucaiug.org/issues/66642024-01-05T12:44:23ZJan Owe
<p>When sending grid billing masterdata, the MktActivityRecord will be the "event class" for which e.g. ChargeGroups with its ChargeType(s) will be provided. Hence the suggestion is to associate MktActivityRecord with ChargeGroup. Regarding ChargeGroup see also issue [[<a class="external" href="https://redmine.ucaiug.org/issues/6536">https://redmine.ucaiug.org/issues/6536</a>]] .</p> CIM Joint Issues - CIM Issues #6656 (New): Add altitudeCompensation to EndDeviceInfohttps://redmine.ucaiug.org/issues/66562023-12-20T09:50:10ZJan Owe
<p>When exchanging Metering configuration characteristics (master data) for gas installations, it may be a need to indicate if the Meter has built in altitude compensation functionality.</p> WG14 Part 9 Issues - CIM Issues #6543 (New): AccuracyClass for sensorshttps://redmine.ucaiug.org/issues/65432023-10-19T14:43:23ZDavid Haynes
<p>CurrentTransformer and PotentialTransform inherit from Sensor, and each have "accuracyClass" as attributes. It seems that "accuracyClass" should be promoted up to the Sensor parent, and inherited by everything sensor related.</p> Market Management - CIM Issues #6536 (New): Add an association from ChargeType to MarketParticipanthttps://redmine.ucaiug.org/issues/65362023-09-28T15:17:23ZJan Owe
<p>When sending aggregated grid billing data (time series) from a Billing Calculator to the Grid Company and/or the Energy Supplier, the “Charge ID” and related “Charge type” (e.g. fee, subscription or tariff) and “Charge type owner” are essential information elements.<br />ChargeType class is requested add to ESMP in ebIX® MR 2022/020, see <img src="https://redmine.ucaiug.org/issues/6533" alt="" /> . The association from ChargeType to MarketParticipant is among others used in the ebIX® BRS for Combined grid and supply billing.</p> Market Management - CIM Issues #6534 (New): Add an association from Series to ChargeTypehttps://redmine.ucaiug.org/issues/65342023-09-28T14:54:30ZJan Owe
<p>When sending aggregated grid billing data (time series) from a Billing Calculator 3 to the Grid Company<br />and/or the Energy Supplier, the “Charge ID” and related “Charge type” (e.g. fee, subscription or tariff) and<br />“Charge type owner” are essential information elements.<br />ChargeType class is requested add to ESMP in ebIX® MR 2022/020, see [[<a class="external" href="https://redmine.ucaiug.org/issues/6533">https://redmine.ucaiug.org/issues/6533</a>]] .<br />The association from Series to ChargeType is among others used in the ebIX® BRS for Combined grid and<br />supply billing.</p> Market Management - CIM Issues #6510 (New): Add an association between MarketEvaluationPoint and ...https://redmine.ucaiug.org/issues/65102023-08-21T15:11:12ZJan Owe
<p>When exchanging master data for an Accounting Point it may be needed to exchange the technology used for the energy production at the Accounting Point, such as hydro, wind or nuclear. <br />Among others the technology is required when the Metered Data Aggregator (MDA) sends aggregated metered data to the Imbalance Settlement Responsible in the four Nordic countries – in this case the technology is associated to the TimeSeries class. However, since the MDA needs to know the technology of each Accounting Point, to be able to aggregate measured data per type of technology, he must receive master data telling the technology. In the latter case, the technology must be associated with the Accounting Point. <br />The suggestion is to use the psrType attribute (using the Asset type list) from the MktPSRType class available in CIM and ESMP (EuropeanStyleMarketProfile/IEC62325-351/ESMPClasses). Since the technology in the future is supposed also to be relevant for other types of Metering Points, the suggestion is to associate the MktPSRType class with the MarketEvaluationPoint class.</p> IEC TC57 WG10 Future Work - WG10 Future Work #5942 (New): Activation and deactivation of a functi...https://redmine.ucaiug.org/issues/59422022-08-09T13:16:47ZVladan Cvejic
<p>The DO "mod" allows to activate or deactivate a function with online control.<br />Currently, to deactivate a function by configuration, it is necessary to instantiate the DO mod with valKind = RO or valKind = SET. It should be more appropriate to have a specific DO to do this.</p> WG13 Issues - CIM Issues #5303 (New): 5302:5303 61970 portion of TransformerTank to TransformerTa...https://redmine.ucaiug.org/issues/53032022-01-30T11:22:59ZPat Brown
<p>In the canonical UML, 61970 PowerSystemResource child classes inherit an association to AssetInfo. This means that, as a child of PowerSystemResource, the TransformerTank class has an allowed association to classes as diverse (and illogical) as EndDeviceInfo, SurgeArresterInfo and WireInfo. This situation forces 61970 profiles to articulate constraints that are actually universal and not profile-specific.</p> WG14 Issues - CIM Issues #5301 (New): 5302:5301 61968 portion of TransformerTankInfo to Transform...https://redmine.ucaiug.org/issues/53012022-01-30T11:01:03ZPat Brown
<p>In the canonical UML, 61968 AssetInfo child classes inherit an association to every PowerSystemResource child class, forcing 61968 profiles to articulate constraints that are actually universal and not profile-specific.</p> WG14 Part 1 Issues - CIM Issues #5207 (New): Add Business Roles into IRM Model (for Ed.4)https://redmine.ucaiug.org/issues/52072022-01-12T20:44:09ZHerbert FalkWG14 Part 1 Issues - CIM Issues #5200 (New): Add an activity diagram example in Appendix A.5https://redmine.ucaiug.org/issues/52002022-01-12T20:44:06ZHerbert FalkWG14 Part 1 Issues - CIM Issues #5196 (New): A consolidated IRM for WG13, WG14 and WG16https://redmine.ucaiug.org/issues/51962022-01-12T20:44:04ZHerbert FalkWG14 Part 1 Issues - CIM Issues #5171 (New): 61968 RDF statementhttps://redmine.ucaiug.org/issues/51712022-01-12T20:43:56ZHerbert FalkIEC TC57 WG10 Future Work - WG10 Future Work #5104 (New): Add a type code 'INV'https://redmine.ucaiug.org/issues/51042021-10-08T08:37:08ZMichael Haecker
<p>From WG 10 meeting October 2021, WG 17 report</p>
<p>Recommendation R31 for CIM_61850 harmonization:</p>
<p>In IEC 61850-6 add a standard type code "INV" with one terminal, that can be used for conducting equipment that is a power electronics connection (inverter or rectifier).</p>