: Public Note
Created: 08/01/2011 15:43:43
Modified: 09/01/2011 03:34:30
Project:
Advanced:
[tk, 2011-01-09]<br/><ul>
<li><font color="#ff0000">I have moved association of SubControlArea from GeneratingUnit to Mkt_GeneratingUnit (that was the only remaining direct one). In particular, you'll have to dig into the new package IEC61970::ControlArea, because some minimum concepts, as required for EMS, are defined there with CIM14+ - see with WG13 how and where to consolidate and avoid repetition. I think that package has been defined to support ENTSO-E, and IEC62325 will probably want to extend some of those classes. - </font><font color="#008040"><b>Removed association</b></font></li><li>To follow naming conventions, you'll have to rename all the attributes having unit names in them (e.g. maxMW -#gt; maxP or maxActivePower).  -<font color="#008040"><b> Plan to do</b></font></li><li><font color="#ff0000">There are two classes with the same name: Mkt_Line, in EnergyScheduling and in ReferenceData packages.</font> This is probably consequence of merging 2 models (I suspect the one from EnergyScheduling, with association to TransmissionRightOfWay is obsolete; and Mkt_Line is to be kept). Ensure you consolidate the two into one Mkt_Line. - <font color="#008040"><b>Removed extra Mkt_Line from EnergyScheduling</b></font></li><li><font color="#ff0000">RegisteredGenerator has 65 own attributes plus 33 inherited from RegisteredResource (not shown) - a bit insane</font>. First compare with attributes defined on IEC61970::Production::GeneratingUnit and then consider grouping attributes that always go together and that are defined in both classes, into various #lt;#lt;Compound#gt;#gt;-s - then you can dicrease the number of attributes by "distributing" them into smaller chunks.</li><li><font color="#ff0000">LogicalConfiguration and ConfigurationMemeber (and related Configuration, not shown here) sound like a local application configuration, and not the data to be exchanged with the standard CIM. Consider removing those classes, in which case the shadow classes Mkt_ThermalGeneratingUnit and Mkt_CombinedCyclePlant become superfluous and can be removed as well. - </font><font color="#008040"><b>Classes are required, will consider renaming to a more appropriate representation.</b></font></li></ul>
<br/><br/>