A perspective on European TSOs migration to CIM data exchange

Transcription

1 Youssef AKEL A perspective on European TSOs migration to CIM data exchange CIM planning and operations exchanges seen from RTE

2 Plan 1. Planning and operations data exchanges from RTE 2. Migration of data exchanges to CIM 3. Lessons learnt and interoperability

3 1. Planning and operations data exchanges from RTE

4 Utility project story Very large interconnected power system Operated by TSOs

5 RTE, the French TSO RTE has a special position in Europe km of lines from 63 to 400 kv 46 cross-border lines o The network operated by RTE is the biggest in Europe About employees Own R&D division Active role in the CIM adventure since a long time o Designed our own EMS and planning tool

6 Planning and operations data exchanges Each TSO is responsible of the operation of his own part of the grid... Grids are all interconnected impossible to be safely operated without short term and long term coordination One of the aspects of this coordination lies in data exchange between TSOs: for day-to-day system operation for future grid planning purposes TSO to TSO exchanges

7 2. Migration of data exchanges to CIM

8 Where we were: Needed to standardize data exchange formats Back in 2003: Used a basic custom-made data format (UCTE DEF format)

9 Where we are: Today migration to CIM ENTSO-E profile is ongoing Profile and not information model! Main advantages of moving to CIM: 1. Object identification: - Using unique identifiers (through space and time) - Avoiding aggregation of equipment - Combining operation and planning databases 2. Partitioning into equipment, topology and state variables - Taking into account the occurrence of variation of each piece of data - Bus branch modelling: output of a topology processing 3. Data mastership principles: - MAS exchanges: non overlapping subsets, separated by Boundary - Not interested in how A models B, but how A models A

10 Where we are: CIM ENTSO-E profile is for model exchange: Only the interface is impacted Create a new translator! Philosophy of CIM: 1. Object identification 2. Partitioning into equipment, topology and state variables 3. Data mastership principles In reality, it does impact tools, data, internal processes Even more, it drives us to improving tools, data and internal processes: This is the road to follow!

11 3. Lessons learnt and interoperability

12 Lessons learnt and interoperability Information model vs profile We have not used the CIM as our information model - But have implemented a specific translator based on the profile, at the interface of our tool Validation Having one shared validation tool is vital - Being able to state undeniably what is good modelling and what is not - Error: Missing required attributes - Solution? Validation and compliance only concern profiles - And not CIM, nor information model - Error: wrong profile version used - Solution?

13 Lessons learnt and interoperability Data issues: Interoperability is more than about having the perfect translator, it is also about having good and robust data! - Also, if you do some network reduction (removing lower voltage levels), make sure the data is still coherent - Error: no load flow convergence after network reduction - Solution? Making the best out of CIM/profile: Using GeneratingUnit types - Error: No instance of ThermalGenU, NuclearGenU, HydroGenU used - Solution? Using Substation as container of VoltageLevel, and VoltageLevel as container of TopologicalNode - Consequence: definition of where is located be a Switch, a Line, a PowerTransformer - Error: Each TopologicalNode exported into 1 Substation - Solution?

14 Lessons learnt and interoperability Xnodes: Each CIM ENTSO-E model has to have dangling references - The model can only be complete after the addition of the Boundary - Just like you cannot read TP or SV if you don t have EQ! - Error: Xnodes contained in the model - Solution? - Error: No load flow convergence after having removed Xnodes - Solution? EnergyConsumer have to be given and belong to TSO MAS Implementation time and detail level We are late in CIM ENTSO-E profile and interoperability is not that automatically achieved - This profile is based on CIM14v02! - Utilities and vendors have not reached a good understanding of the profile yet - So don t try to make things better by making them worse (e.g. pushing to more detailed modelling )

15 Moving forward! Utilities also have an important role in the development of the standard EQ/TP/SV partition is a good way of testing the standard - Compare two exports from two consecutive hours: - Error: SynchronousMachine changed to an EnergyConsumer - Solution? Modelling problem in the exporting tool of pumped-storage - Error: OperationalLimits changing - Solution? Dynamic line ratings Smart Grid friendly! - Error: RegulatingControl s targetvalue changing - Solution? Use OperatingState: i.e. what control is doing at a certain point in time

16 Questions? Thank you for your attention youssef.akel (at) rte-france.com

17 Importance of OperatingState: Values after and before load are different in: Voltage: When reactive power limits reached on a voltage controlled bus Voltage: When the target value is somewhere between two discrete taps of a TapChanger Active power: When there is an active power imbalance (only on the Slack node generator / or on all participating generators in case of distributed slack nodes) Active power: When you merge different MAS Active power: When you disconnect an regulating conducting equipment