37
Support by EERA-DTOC Software Frankfurt, 19 November 2013 Gregor Giebel, DTU Wind Energy, Risø, DK Igor Waldl, Felix Dierich, Overspeed, Oldenburg, DE Peter Stuart, RES, London, UK

EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Page 1: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Support by

EERA-DTOC SoftwareFrankfurt, 19 November 2013Gregor Giebel, DTU Wind Energy, Risø, DKIgor Waldl, Felix Dierich, Overspeed, Oldenburg, DEPeter Stuart, RES, London, UK

Page 2: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

DTOC software development: Goals

1. Definition of the end-user requirements for the software

2. Definition of the data and control interfaces to facilitate the coupling of existing models available with the partners

3. Design of the DTOC software

4. Development of the software to couple existing models at the various institutes to create integrated offshore wind farm design tools

2

Page 3: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Integration task

3

Page 4: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

EERA-DTOC portfolio of models

Name Partner Status ProgramsInput/

output

Script/

GUIDatabase interface IPR Com

CFDWake CENER Fluent, C++, OpenFOAM ASCII script Yes

CorWind Risoe DTU OpeDOS exe

DelphiCSV files no no + +

CRES-farm CRES Ope Linux/ Fortran77 ASCII no no +

CRES--flowNS CRES Ope Linux/ Fortran77 ASCII no no

DWM Risoe DTU Ope Fortran, pc, pc-cluster ASCII script +

ECNS ECN Beta Linux/ Fortran90 ASCII No No +

EeFarm ECN Alpha Matlab Matlab scripts

Script/

GUIyes + +

Farm-farm interaction ECN Ope Fortran ASCII No no +

FarmFlow ECN Ope DelphiASCII/

binaryGUI Yes + +

FlowARSM CRES Alpha Linux/ Fortran77 ASCII no no

FUGA Risoe DTU Ope Fortran, C, Delphi, pc ASCII Script/ GUI No +

NET-OP SINTEF Proto type Matlab ASCII script No +

Skiron/WAM CENER Ope Unix/ Fortran GRIB script yes

TOPFARM Risoe DTU Beta Matlab/C/ Fortran ASCII script +

UAEP Risoe DTU Matlab, pc ASCII/ binary no yes

VENTOS UPorto Beta Unix/ Fortran ASCII no yes + +

WAsP Risoe DTU Ope Windows pc ASCII Script/ GUI No + +

WCMS Fraunhofer Ope Matlab/JAVA OracleDB yes +

WRF Risoe DTU Ope Unix, Linux, Fortran90 netCDF Shell script yes

WRF/ROMS CIEMAT Ope Linux/ Fortran netCDF script yes + 4

Page 5: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

EERA-DTOC portfolio of models

Name Partner Status ProgramsInput/

output

Script/

GUIDatabase interface IPR Com

CFDWake CENER Fluent, C++, OpenFOAM ASCII script Yes

CorWind Risoe DTU OpeDOS exe

DelphiCSV files no no + +

CRES-farm CRES Ope Linux/ Fortran77 ASCII no no +

CRES--flowNS CRES Ope Linux/ Fortran77 ASCII no no

DWM Risoe DTU Ope Fortran, pc, pc-cluster ASCII script +

ECNS ECN Beta Linux/ Fortran90 ASCII No No +

EeFarm ECN Alpha Matlab Matlab scripts

Script/

GUIyes + +

Farm-farm interaction ECN Ope Fortran ASCII No no +

FarmFlow ECN Ope DelphiASCII/

binaryGUI Yes + +

FlowARSM CRES Alpha Linux/ Fortran77 ASCII no no

FUGA Risoe DTU Ope Fortran, C, Delphi, pc ASCII Script/ GUI No +

NET-OP SINTEF Proto type Matlab ASCII script No +

Skiron/WAM CENER Ope Unix/ Fortran GRIB script yes

TOPFARM Risoe DTU Beta Matlab/C/ Fortran ASCII script +

UAEP Risoe DTU Matlab, pc ASCII/ binary no yes

VENTOS UPorto Beta Unix/ Fortran ASCII no yes + +

WAsP Risoe DTU Ope Windows pc ASCII Script/ GUI No + +

WCMS Fraunhofer Ope Matlab/JAVA OracleDB yes +

WRF Risoe DTU Ope Unix, Linux, Fortran90 netCDF Shell script yes

WRF/ROMS CIEMAT Ope Linux/ Fortran netCDF script yes +

Run on Windows, on a

single PC

5

Page 6: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

EERA-DTOC portfolio of models

Name Partner Status ProgramsInput/

output

Script/

GUIDatabase interface IPR Com

CFDWake CENER Fluent, C++, OpenFOAM ASCII script Yes

CorWind Risø DTU OpeDOS exe

DelphiCSV files no no + +

CRES-farm CRES Ope Linux/ Fortran77 ASCII no no +

CRES--flowNS CRES Ope Linux/ Fortran77 ASCII no no

DWM Risø DTU Ope Fortran, pc, pc-cluster ASCII script +

ECNS ECN Beta Linux/ Fortran90 ASCII No No +

EeFarm ECN Alpha Matlab Matlab scripts

Script/

GUIyes + +

Farm-farm interaction ECN Ope Fortran ASCII No no +

FarmFlow ECN Ope DelphiASCII/

binaryGUI Yes + +

FlowARSM CRES Alpha Linux/ Fortran77 ASCII no no

FUGA Risø DTU Ope Fortran, C, Delphi, pc ASCII Script/ GUI No +

NET-OP SINTEF Proto type Matlab ASCII script No +

Skiron/WAM CENER Ope Unix/ Fortran GRIB script yes

TOPFARM Risø DTU Beta Matlab/C/ Fortran ASCII script +

UAEP Risø DTU Matlab, pc ASCII/ binary no yes

VENTOS UPorto Beta Unix/ Fortran ASCII no yes + +

WAsP Risø DTU Ope Windows pc ASCII Script/ GUI No + +

WCMS Fraunhofer Ope Matlab/JAVA OracleDB yes +

WRF Risø DTU Ope Unix, Linux, Fortran90 netCDF Shell script yes

WRF/ROMS CIEMAT Ope Linux/ Fortran netCDF script yes +

Runs on Cluster under

UNIX/Linux

6

Page 7: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

User Requirements

7

Page 8: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

• A robust, efficient, easy to use and flexible tool created to facilitate the optimised design of individual and clusters of offshore wind farms.

• A keystone of this optimisation is the precise prediction of the future long term wind farm energy yield and its associated uncertainty.

EERA-DTOC vision

8

Page 9: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Design and model selection guided by end-users

Two main user groups were identified:• Strategic planners• Developers of offshore wind farms

Associated users could be:• Consultants• Research institutions• Manufacturers• System Operators

Users

9

Page 10: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

• As a developer I can determine the wake effects of neighbouring wind farm clusters on a single wind farm.

• As a developer I can determine the optimum spacing, position, turbine model and hub height of turbines within an offshore wind farm.

• As a strategic planner I can determine the optimum strategic infrastructure to accommodate offshore wind farm clusters.

• 14 relevant user stories in total

Selected User Stories

10

Page 11: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

• As a developer I can determine the optimum spacing, position, turbine model and hub height of turbines within an offshore wind farm.

Software supports the comparison of many design scenarios.

Comparative reporting enables selection of optimisedconfigurations.

Score for comparison: Levelised Cost of Energy

Optimisation process

11

Page 12: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Optimisation Process

• Scenario 1• Scenario 2• Scenario 3• Scenario 4• Scenario 5• Scenario 6• Scenario 7

Wake Model

Electrical Model

Energy model

1. Generate Design Options

2. Evaluate Design Options

3. Compare Design Options

4. Iterate steps 1 to 3

What decision parameter can we use to compare design options?

12

Score: Levelized cost of energy

Page 13: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Model Chains

13

Page 14: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Wind climate/Wind farm model coupling

WRF wind speed field with cluster

influence

Wind farm clusters

14

Page 15: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Wind climate/Wind farm model coupling

Local wind farm

15

Page 16: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Wind climate/Wind farm model coupling ctd.

WRF level at hub height, wind

climate for eachturbine position

16

Page 17: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Model Workflow WP1

Dynamical Mesoscale flow model

Mesoscale wake modelMicroscale wake model

Reanalysis Inputs

Microscale wake model

Wind farmsLayout

Wind farmPower production

AEPcalculator

Wind farmAEP

Time SeriesDatabase

Mesoscale Wake Deficits

Hybrid Mesoscale wake model

CorWindinputs

DynamicalStatistical-Dynamical

Wind farmsPower Curve

Lib, Tab,NetCDF

17

Page 18: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Model Workflow “Electrical”

Cost Model

Grid Optimization(System Services)

Grid Optimization(Layout)Forecasts & Predictability

Time Series Generation

System Services(WCMS)

Inter-array(eeFarm II,

AEDIC)

Inter-array(eeFarm II, …)

Offshore Optimization(NET-OP, …)

Offshore Optimization(NET-OP, …)

Cost Model(DTOC Cost Model, etc)

Cost Model(DTOC Cost Model, etc)

NWP Forecast (GFS, WRF,etc)

NWP Forecast (GFS, WRF,etc)

Variability & Predictability

(Fh Model)

Predictability(Fh Model)

Synth. TS(CorWind, meas., etc)

Synth. TS(CorWind, meas., etc)

Wake Effects(Missed)

Wake Effects(out of scope)

Page 19: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Yield modelling

Filtering Vertical extrapolation Long TermOn site mast data (raw) Long term ref. masts

Virtual data

Gross Energy

Clean data HH Data

LT Wind Data

Lay outLayout Opt

Power curve

Net Energy

Gross energy

WP1

WP2

Availability

Wave conditions

Distance to O&M base

% losses

Uncertainty Cost

Specifications

ParametersNet AEP

P50/P90

19

Page 20: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Total tool overview

Dynamical Mesoscale flow model Mesoscale wake model

Microscale wake model

Reanalysis Inputs

Microscale wake modelWind farms

Layout

Wind farmPower production

AEPcalculator

Wind farmAEP

Time SeriesDatabase Mesoscale Wake Deficits

Hybrid Mesoscale wake model

CorWind inputs

DynamicalStatistical-Dynamical

Wind farmsPower Curve

Lib, Tab,NetCDF

Filtering Vertical extrapolation Long TermOn site mast data (raw) Long term ref. masts

Virtual data

Gross Energy

Clean data HH Data

LT Wind Data

Lay out

Layout OptPower curve

Net Energy

Gross energy

WP1

WP2

Availability

Wave conditions

Distance to O&M base

% losses

Uncertainty Cost

Specifications

ParametersNet AEP

P50/P90

20

Cost Model

Grid Optimization(System Services)

Grid Optimization(Layout)Forecasts & Predictability

Time Series Generation

System Services(WCMS)

Inter-array(eeFarm II,

AEDIC)

Inter-array(eeFarm II, …)

Offshore Optimization(NET-OP, …)

Offshore Optimization(NET-OP, …)

Cost Model(DTOC Cost Model, etc)

Cost Model(DTOC Cost Model, etc)

NWP Forecast (GFS,

WRF,etc)

NWP Forecast (GFS,

WRF,etc)

Variability & Predictability

(Fh Model)

Predictability(Fh Model)

Synth. TS(CorWind, meas., etc)

Synth. TS(CorWind, meas., etc)

Wake Effects(Missed)

Wake Effects(out of scope)

Page 21: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Total tool overview – very complex!

21

Page 22: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Applications

22

Page 23: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

As a developer, I can determine the wake effects of neighbouring wind farm clusters on a single wind farm.

Example User Story

23

Page 24: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Ex: Energy prod. of single farm in cluster

Wind farm clusters/meso-scaleeffects

Wind speed field with wind farm cluster influence

Single wind farm model

Wind farm AEP with consideration ofcluster influence

WRF with wind farm extension:WRF @ Risoe DTUWRF @ Ciemat

WAsP/ParkFarmFlowJensen model

24

Page 25: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

WRF/Farm model coupling

WRF

WRF netCDF

Tab for each wturbine site

Park

WAsP

AEP Google maps

Turbine clustersTurbine types

Turbine types

Turbine positionsTurbine types

Turbine positions single farmRepresentative meteo

DTOC XML

Page 26: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Ex: Calculate one farm in presence of Cluster

26

Page 27: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

WRF/Farm model coupling Google maps

27

Page 28: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

One transp. From IWES power plant behaviour of cluster

28

Page 29: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

The Software Product

29

Page 30: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Handling and Comparing Scenarios

30

Page 31: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Modelling: Energy and Electrical Part

31

Page 32: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Graphical and tabular reporting

32

Page 33: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

GIS integration

Converts DTOC XML ↔ ESRI Shapefiles (industry standard)33

Page 34: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

• The sub-models are protected by IPR…• …but the interfaces in the model chain are going to be

open

• File formats for data exchange are based on existing industry standard formats, e.g. the WAsP types based on XML

Open interfaces

34

Page 35: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

Conclusion

35

Page 36: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

DTOC software development timeline

36

2012 2013 2014

existingmodels

end userrequirements

dry runs proof ofconcept

pre-design

prototype

design

DTOC V0.5 DTOC V1.0

test reports

Page 37: EERA-DTOC Software · DTOC software development: Goals 1. Definition of the end-user requirements for the software 2. Definition of the data and control interfaces to facilitate the

DTOC: From concepts to product

Energy Production

GIS Scenarios

Electrical Issues

Reporting

37