: Public Note
Created: |
09/01/2011 02:07:13 |
Modified: |
27/01/2011 17:16:51 |
|
Project: |
|
Author: |
T. Kostic |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{0029595F-A80F-451e-8B9F-82B32AAFEE1E} |
Appears In: |
13-OperationalLimit, OutageSchedule |
[tk, 2011-01-09]<br/><ul>
<li>Mkt_OperationalLimit: Note that from that class you don't have access to specific subtypes of OperationalLimit (as the class doc implies). I don't see very well why to associate an OperationalLimit with the OutageSchedule (because the Y1 axis in the schedule should in effect be the limit during the outage). If you really need this association for something else, you'll need 4 shadow classes instead of Mkt_OperationalLimit. - <font color="#008040"><b>Removed Mkt_OperationalLimit class</b></font></li><li><font color="#ff0000">[c-028] Mkt_OutageSchedule: For IEC61968-3, in the first half of 2011 we'll be working on outage-related classes in IEC61968::InfOperations and for several attributes currently in Mkt_OutageSchedule class we have actual relationships to objects (instead of strings). WG16 and WG14 should work together on WG16 requirements. - </font><font color="#008040"><b>Mkt_OutageSchedule will remain for now, consider for future.</b></font></li></ul>
<br/><br/>