Notes:
|
This system use case describes the steps necessary in the process of defining a network model suitable for exchange between the TSO and the DSO which includes expected network development plans in the future. The exchange itself is not part of this system use case.<br/><br/>According to ENTSO-E's network codes, the DSO and TSO should exchange expected network development plans and the current status of their respected network every 6 months. This is step forward in the current planning practice as no such formal information exists. <br/><br/>In order to successfully perform network studies the network models are usually constructed in the bus-branch representation. On the other hand, network models in Network Model Management Systems are usually constructed in the node-breaker representation. The challenge for this use case is to perform the required transformation from one representation to the other while keeping a high level of detail and extracting the necessary information only for the defined observability area. Additionally, the information regarding the expected network development plans for the future either have to be preserved if the plans are part of the Network Model Management system or added subsequently if part of any other system. Also, the foreseen network development plans have to be constructed in the bus-branch representation of the model.<br/><br/>The transformation is achieved through Network Topology Processing which is functionality present in many wide-spread planning application or systems in DSO's and TSO's. The functionality calculates the connectivity of the network and eliminates all unnecessary network elements for planning studies. For example, it treats closed switches as branches and eliminates any branches with open switches.<br/><br/>The bus-branch representation serves as a representative network equivalent which is further limited to the observability area.<br/><br/>This process is triggered by a related use case, update of Network models representation.<br/>
|