Attribute |
Public completeDescription
|
Details:
Alias: |
|
Initial: |
|
Stereotype: |
|
Ordered: |
|
Range: |
|
Transient: |
False |
Derived: |
False |
IsID: |
False |
Notes:
|
This system use case focuses on two main procedures required for optimal coordination of long term network development planning between DSO and TSO. <br/><br/>The first procedure describes the process of updating a network model representation since the last information exchange between the TSO and the DSO related to long-term network development planning. This system use case uses the system use case Definition of representative network equivalent in observability area as one of the activities. The process focuses on establishing the changes between the previous version of the model that was exchanged and the newest version of the model.<br/><br/>The identified changes are then packaged as a CIM change model according to the relevant standards.<br/><br/>The second part of the use case focuses on the actual exchange of the change model and utilizes a Data Exchange Platform that both the TSO and the DSO use for their mutual exchanges. <br/><br/>The process can be triggered by either the TSO or the DSO. There is also a time-trigger related to ENTSO-E's network codes which state that such an exchange should take place every 6 months. If no updates to the network model from either the TSO or the DSO was made, or no future development plans have been altered in the last 6 months, the TSO and the DSO should exchange information that no relevant changes were made to the representative network equivalent in the observability area.<br/>
|
|
Public scope
|
Details:
Alias: |
|
Initial: |
|
Stereotype: |
|
Ordered: |
|
Range: |
|
Transient: |
False |
Derived: |
False |
IsID: |
False |
Notes:
|
This system use case describes the information needed for updating a network model representation from the previous version that was exchanged between TSO and DSO inside an observability area.<br/>
|
|