: Public Note
Created: |
05/18/2011 01:22:33 PM |
Modified: |
07/02/2011 12:02:28 PM |
|
Project: |
|
Author: |
Jean-Luc |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{361A4217-9B8C-422e-9FDA-AAD2533394B0} |
Appears In: |
OperationalLimitsNotes |
ENTSO-E branches may have up to "N" OperationalLimits in an OperationalLimitSet associated with branch terminals. The term "operational" is a CIM definition and it is not the same as ENTSO-E definitions. Any limits for operational, planning or other purposes can be exchanged using this object.<br /></p><p>ENTSO-E voltage limits must be specified as an OperationalLimitSet associated with the terminal of a conducting equipment instance at the TopologicalNode and containing one high VoltageLimit and one low VoltageLimit.<br /></p><p>Since the terminal assignment is always explicitly exchanged as OperationalLimitSet.Terminal and given that the exchange of a Terminal.sequenceNumber is not necessary.<br /></p><p>The OperationalLimitType.direction is absolute value (OperationalLimitDirectionKind.absoluteValue) for all OperatonalLimitType objects except the high (OperationalLimitDirectionKind.high) and low (OperationalLimitDirectionKind.low) voltage limits.<br /></p><p>To further explain the above statements, the following should be noted:<br /></p><p>· At least one of the limit types must be provided (this is the minimum requirement)<br /></p><p>· The PATL limits must be specified for all Transformers and at both ends of the ACLineSegment<br /></p><p>· All types of limits are exchanged (at the same time) if required by the specific exchange process, which could change depending on the business use for the exchanged files.<br /></p><p>For operations, the parties involved in the exchange need to clearly define what limit types will be included in the exchange.<br /></p>