Smart Grids: bridging the gap between design and. implementation. IDE4L Symposium, Brescia 18 th May Davide Della Giustina

Transcription

1 Smart Grids: bridging the gap between design and ideal grid for all implementation IDE4L Symposium, Brescia 18 th May 2016 Davide Della Giustina Unareti SpA, Smart Grid Department, Italy

2 SLIDE 2 What is it about? Demonstration is «an act of showing that something exists or is true by giving proof or evidence» [ In the context of a research project this means to implement in a specific location the proposed architecture and to verify that it is compliant with the use case defined by the project To «give the proof» means to be able to reply to the following questions: 1. Is the test replicable in different conditions? Test the same UC in different locations Cover all the use cases 2. How can we say that a UC has been verified? What should be measured? KPI definition 3. How can we compare results from different demos? Same units? Same time scale? KPI definition

3 SLIDE 3 Design for integrability A research project with many partners provides several benefits sharing of different backgrounds (ICT, EE, ) sharing of different perspectives (university, industry, utility, ) However, this also brings about an extra complexity, which has been addressed by IDE4L since the beginning: Each group could have a partial insight of the project to avoid the definition of several sub-optimal architectures instead of a common one IDE4L promotes a strong and joint design phase Each group could be more focused on developing its own brick to avoid a situation where bricks work fine independently, but do not interface properly when tested together because interfaces have not been considered in the design IDE4L includes interfaces in the design process and adds an intermediate step between development and testing

4 SLIDE 4 Testing phase: a three-step procedure Use cases, e.g.: 1. Monitoring of LV grid (PC + state estimation + RTU + Smart meters + interfaces) Building-blocks, e.g.: 1. Algorithms 2. Protection devices 3. Third party devices 4. Third party software Groups of buildingblocks, e.g.: 1. State estimation algorithm within a PC connected to an RTU via a interface 1 st Dev. lab 2 nd Integration. lab 3 rd Demo

5 SLIDE 5 From the general architecture to the physical design A project should design a general architecture based on the full set of use cases considered by the project general enough to be applicable everywhere This architecture has to be «projected» on the specific demo site To achieve this goal IDE4L introduces the so called Physical Model it is an abstract model containing the minimum information needed to describe a specific demonstrator its purpose is to identify the components to be installed/tested in a demo to run one or more use cases From this model the list of components is derived At last, the BoM is obtained combining the demo description vs the component list

6 SLIDE 6 Physical Model Reference network topology Secondary substation: Power Transformer MV/LV breakers DVR Primary substation: Power Transformer MV breakers LV network: STATCOM Loads Productions

7 SLIDE 7 Physical Model Automation components IEDs: SCADA Protections Smart meters SW gateways: Developed during the project!!!interfaces to be tested!!! HW Gateways: Modbus

8 SLIDE 8 Physical Model Telecommunication Switches: PS SS Control center Modems: BPL

9 SLIDE 9 Physical Model Information exchange Monitoring & control use case

10 SLIDE 10 Component list Abstract component Layer Component Provider APP NR wp5/uc3m APP SE/PC wp5/tut CT Switch CISCO CGR 1120 CT PLC (modem) Current API-2000-SA EE DVR/STATCOM "prototype" EE MV-CBR ABB/DY800 EE LV-CBR Schneider/NSX250B EE CT/VT Altea/CVS CONV EE I0 Thytronic IED SCADA Selta SCADA IED NTP Meinberg/LANTIME M300 IED PSAU/SSAU Standard PC IED (GW) Cooper/SMP IED PD Telvent/HU_AF+AB_AC IED (GW) 850-modbus Schneider/G3200 IED SM INDRA/EMIEL IED PV-CTRL Fronius/Galvo IT MMS server/client Unareti IT DLMS/COSEM client Unareti Who is the provider? external internal

11 SLIDE 11 Interaction list: highlight interaction between two components Component 1 Component 2 Protocol Responsible Location PD SAU IEC TLV Seville SM SAU DLMS/COSEM Unareti Italy PD PD IEC TLV Seville SCADA/DMS (GW) IEC Unareti Italy (GW) PD IEC Unareti Italy SAU SAU IEC RWTH Germany SCADA/DMS SAU CIM Unareti Italy SAU *-CTRL IEC Unareti Italy Interaction list is the starting point of the integration lab Same process for all the demos: 1. Physical model 2. Component list 3. Interaction list

12 SLIDE 12 Bill of Material: demo description vs component list Component Provider Number SE/PC wp5/tut 1 Switch CISCO CGR DVR "prototype" 1 STATCOM "prototype" 4 LV-CBR Schneider/NSX250B 1 SSAU Standard PC 1 SM INDRA/EMIEL 18 DLMS/COSEM client Unareti 1

13 SLIDE 13 Summary Use Cases Demo description KPIs Architecture Physical Model Component List Interaction List BOM Developments Integration s Supply Demo implementation Testing Results, Replicability,

14 SLIDE 14 Development site

15 SLIDE 15 Integration labs

16 SLIDE 16 Lab demonstrators

17 SLIDE 17 Field demonstrators

18 SLIDE 18 MV demonstrator: 1 HV/MV substation 2 MV/LV substations FLISR use case LV demonstrator: PV and Heat Pumps Real-time monitoring Load and production forecast State estimation

19 SLIDE 19 MV demonstrator: 1 MV/MV substation 3 MV/LV substations Real-time monitoring FLISR use case LV demonstrator: PV high penetration Real-time monitoring Load and production forecast State estimation Power control

20 SLIDE 20 LV demonstrator: Real-time monitoring Load and production forecast State estimation Power control

21 Thank you!