Modeling and Simulation of Intelligent Electrical Power Grids. Peter Palensky TU Delft

Transcription

1 Modeling and Simulation of Intelligent Electrical Power Grids Peter Palensky TU Delft 1

2 (~1.75*10^28) 2

3 Kinetic equations Temperature Co T = k/n * Σ mi*v 2 i s n o i llis? k = some constant n = number of molecules m = mass of molecule v = velocity of molecule T = absolute temperature 3

4 Pressure Temperature P T = P*V / N*R P = pressure V = volume N = amount of substance (in moles) R = ideal gas constant T = absolute temperature 4

5 Electrical Power Grids? g n i h c t i Sw Topology All elements, parameters Matrices I=Y V V = Voltages I = Currents Y = nodal admittance matrix 5

6 Electrical Power Grids Complex already! Weasle around problems Conservative rules Over-engineer Damping, inertia, etc. Image: NREL 6

7 Intelligent Electrical Power Grids A System of Systems 7

8 Paradigm shift needed P? 8

9 One of the new (?) things: Data 1) Metering 2) More metering (PMUs, etc.) 3) Unstructured data 4) Asking controllers/ DERs/IoT PMU: Phasor Measurement Unit IoT: Internet of Things DER: Distributed Energy Resources 9

10 First attempts: 2004 Early, experimental platform App(lication) as the goal! Communicating box Multi-agent system Intelligent Loads Scalability? 10

11 Even more challenges for Grid as Platform Scalability? Interoperability, Interfaces? Data/function/infrastructure ownership? Security, Resilience? Physics vs. Data vs. Economics? Upgrades/Updates? Basic rules/standards or anarchy? Governance, fairness? 11

12 Grid connects worlds... physical world roles/behavior continuous models game theory models energy generation, transport, distribution, consumption, etc. agents acting on behalf of a customer, market players, etc. information technology cyberphysical energy system aggregate/stochastic discrete models statistical models controllers, communication infrastructure, software, etc. weather, macro-view of many individual elements, etc. 12

13 Heterogeneity within worlds Power System Physics: electricity, mechanics, hydraulics,... Within electricity grid: multi-view, different models Electromagnetic Transients (EMT) µs: switching, lighting, harmonics Phasor Domain / Transient Stability (TS) ms: machines, controls 13

14 How to solve? Research on cyber(multi)physical ecosystems Understand, validate, optimize Traditional (analytical) methods limited New Methods Flexible, Modular Scalable Allow scenario handling How to find? Go through typical examples 14

15 Case 1: Thermal System with Market Consumption Thermal Flow SUM Information Thermal domain H1 [house] Discrete controller H2 [house] Agents/Market Stochastic events Market Price Hn [house] Environment Price Agent On/Off Describe via bond graph Analyze interplay of continuous domain and asynchronous events Scalability of methods Tset Heater Controller Thermal Mass Tin P E Energy Counter Switch Vent Schedule Out0 conduct1 Q_dot_amb Out1 conduct2 15

16 Case 2: UC1 + el. power station Plus: Electrical domain Ideal grid Non-ideal power station Plus: Mechanical domain Tightly coupled elements! Further use cases 3: 4: 5: 6: 7: Thermal grid Non-trivial market Communication network non-ideal grid EV-charging EV: electric vehicle 16

17 Options for modeling a hybrid system (0) Squeeze submodels into one tool Language, solver, method n-1 submodels in wrong language Tedious Error prone Brutal simplifications (1) Universal tool Universal language, solver, etc. (2) Co-simulation Combine specialized languages, solvers, etc. 17

18 (0) Use tool of subdomain Example: Omnet++ discrete event scheduler For communication networks Parameters in config file Topology in *.ned files Agent behavior in C++ code class Sensor : public csimplemodule { protected: virtual void initialize(); virtual void handlemessage(cmessage *msg); }; Define_Module(Node); void Node::initialize() { if (blabla) { cmessage *msg = new cmessage(something); send(msg, "value"); } } void Sensor::handleMessage(cMessage *msg) { do_something; } [General] network = Testnetwork1 Testnetwork1.Controller5.KP = truncnormal(3,1) simple Sensor { parameters: int datarate; gates: output value; } network Testnetwork1 { types: channel C extends ned.dataratechannel { datarate = 100Mbps; ber = 2e-10; delay = 75us; } submodules: Sensor47: Sensor; Controller5: Controller;... connections: Sensor47.value <--> C <--> Controller5.port++; Controller5.ctrlval <--> C <--> Valve12.setpoint;... } 18

19 Discrete Simulation Platform Power system simulation Matlab prototypes Translate to OMNeT++ Discrete event simulator open source, cross-platform Models of Telecommunications Generators, loads, grid,... Infoserver server Info Required behavior Communication Communication channel channel (Distributed) (Distributed) Algorithm Algorithm Environment Environment climate,human human ( (climate, behaviour etc.) ) behaviour etc. EnergyResource Resource Energy (load,generator, generator,etc.) etc.) (load, Powergrid grid Power Achieved behavior Testing Algorithms Communication 19

20 Extremely simplified models First tries: continuous model, 28 state discrete, etc. etc. etc. Simplified Markov Model with two states Computationally inexpensive T=0 FLUSH pflush(t) FLUSH pflush(t) Full / DRAIN Not full T T Not empty Empty / STORE 20

21 Linear, analytic solutions useless ΔT NORMAL OPERATION ΔT ΔThigh ΔThigh ΔTlow Power ΔTlow ton ΔT toff DRAIN Power ton toff time STORE ΔT ΔThigh ΔThigh ΔTlow Power ΔTlow Power ton toff time time FLUSH ton toff time 21

22 How to represent physical models Analytic Causal No solver No interaction Unidirectional flow of information Transfer functions, blocks Simulink, Ptolemy Good for controls Acausal Bidirectional flow of information Equation-based model Modelica, Simscape Good for (multi)physics 22

23 (1) Universal tool approach (a) Agent-oriented / modular (b) Monolithic Autonomous objects GridLAB-D, Omnet++ Equation-based model Modelica, Simscape Both Use object oriented languages Are compiled into executable 23

24 (1a) Agent-oriented models Model split into (large) number of autonomous objects Communicate variables with each other Determine synchronization points Discrete event scheduler coordinates V O2 O1 O3 On Sync Scheduler Good scalability 24

25 (1a) Time synchronization Objects update their states Objects predict personal sync time time Object 1 Object 2 Object 3 order of execution Object 4 25

26 (1a) Time synchronization Objects update their states Objects predict personal sync time time Object 1 Object 2 Object 3 order of execution Object 4 26

27 (1a) Time synchronization Objects update their states Objects predict personal sync time time Object 1 Object 2 Object 3 order of execution Object 4 27

28 (1a) Results agent oriented minimum step size is lower bound Good performance Perfect event handling Module, extensible Hierarchies possible BUT ~n ~n^2 Physics? (no integrators) 28

29 (1b) Monolithic models Simscape, Modelica Equations compiled into executable Numerical solver finds zero crossings Convenient, multi-domain physics Strong syntax, good docu Model Executable flattening Flat Model ODE sorting Sorted Equations Index reduction Index Reduced Equations 29

30 (1b) Connectors link physical properties Flow: Ia+Ib+Ic=0 Potential: Va+Vb+Vc Flow Variables A I V I V B I V C Potential Variables 30

31 (1b) Potential & flow variables: Energy conservation Domain Potential Variables Variables Position Force Angle Torque Magnetic Magnetic potential Magnetic Flux Flow, Hydraulic Pressure Volume Flow Rate (Bio)Chemical Concentration Reaction Rate Electrical Voltage Current Thermodynamics Temperature Heat Flow Rate Mechanics Flow 31

32 (1b) Modelica code example package Energy package Interfaces partial connector HeatPort Thermal port for 1-dim. Heat transfer Types.Temperature T; flow Types.HeatFlowRate Q_flow; end HeatPort;... end Interfaces; package Components model House4 "House and Temperature lumped thermal element storing heat" Types.Temperature T(start= , displayunit="degc") "Temperature of element"; parameter Energy.Types.ThermalCapacity Cth = "Heat capacity of element ; parameter Types.Density ro = ; parameter Types.Volume volume = 200; Interfaces.HeatPort_a port_a; equation T = port_a.t; ro*volume*cth*der(t) = port_a.q_flow; end House4; model Heater... end Heater;... end Components;... end Energy; 32

33 Use Case 1 SimScape results 33

34 (1) One Tool bottom line... Both options not ideal Missed events? 107 Physics in agents? 105 Performance? Parallel computing? M DASSL Simulation time in seconds M LSODAR 106 A dynamic 1 day M RungeKutta 10 4 A fixed M Euler Number of Houses days model time M xxx: Monolithic, A xxx: Agent based 34

35 (2) Co-Simulation normal simulation Model ODEs/DAEs One modeling tool, one solver (e.g. Euler, RK45, DASSL, ODE15s, etc.) # solvers Co-Simulation Multiple solvers/tools Pick the best! Coupled models >1 >1 Parallel Simulation CoSimulation 1 Simulation Hybrid Simulation 1 >1 ODE: ordinary differential equation DAE: differential-algebraic equation # models 35

36 Coupling of Models r coupled systems of DAEs m external steps during simulation time u1 u2 Model 1 Model 2 y1 y2 1-n internal steps during one external step 36

37 Coupling principles Explicit coupling exchanges data at every external step once One or more (internal) steps external step (synchronization point) Implicit coupling iterates each external step until the system converges # steps determines error 37

38 Numerical Co-Simulation Combine models Solve collaboratively Multidisciplinary problems possible Simulated system Energy Market Simulator Car Usage Simulator Distribution Grid Simulator Communication Network Simulator Battery Simulator Power Electronics/ Controls Simulator Difficult... Real system 38

39 EMT-TS Grid Co-Simulation Fast parts in EMT Details, switching, power electronics Big system in TS Simulated in EMT Simulated in TS Simulated in TS 39

40 Challenges in Co(upled) Simulation Optimizer Scenario Multiple simulators Multiple models How to couple? Scenario Handling? Interface? create Initial states Parameters u time series Strategy Utility function Scripting Engine init result Co-Simulation Solver FMU Model y y u u y Solver FMU Model u y y u u u Solver FMU Model y 40

41 Case 7 dynamic demand-response household load profiles taken from measurement campaign small scale distribution grid realistic battery model medium/low voltage network with consumers stochastic driving patterns derived from real-world car sharing data charging control algorithm distributed charging power regulation 41

42 Case 7 implementation (commercial) PowerFactory Power system Loads, generation Dymola/Modelica Batteries GridLAB-D Charging controls Charging agents Vehicle driving 42

43 Case 7 implementation (FOSS) PSAT/Octave Open Modelica Batteries GridLAB-D Power System Vehicles, charging 4DIAC Grid controls FOSS: Free and/or Open Source Software 43

44 Agent/discrete Part Done in GridLAB-D Sequence of car activities Configured via carsharing monitoring data Stochastic model Input to discrete numerical model 44

45 Results: details, details, details Detailed models Unbalanced grid Chemical battery Emulated controls Real-time simulation Multi-focus Battery aging Grid limits Agent convergence Economic optimum 45

46 Results: dynamic step size control 46

47 Results: ICT & Physics Impact of communication latency, packet loss, etc. Various communication channels (power line, etc.) 47

48 Smart Grids Modeling Bottom Line Hybrid systems Cyber-physical (-socio -economic -environmental -etc.) Multi-disciplinary problem Tools, modeling principles, teams Language (natural, formal) Co-simulation can help Harmonization of analytic and numeric methods 48

49 Peter Palensky 49