emmos 2013 renewable resource integration training

©2011 Copyright. Confidential and proprietary to The Structure Group, LLC. ©2011 Copyright. Confidential and proprietary to The Structure Group, LLC.

EMMOS 2013 Renewable Resource Integration Training

Presented by Bob Knox

1

September, 2013


Agenda

Introductions Integration Basics 7-Step Integration Plan Closing Thoughts

2


Contact Information

3

Bob Knox, Sr. Manager & Historian Lead E-Mail: [email protected] Phone: (302) 545-4656

Mario Marchelli, Director - EMCS E-Mail: [email protected] Phone: (832) 563-0897

mailto:[email protected]



Objectives

• Understand key integration concepts for Renewable Generation • Introduce a 7-step Integration Strategy • Provide Examples of Wind Integration

– PI System – SCADA System

• Identify Industry Trends and Challenges • Discuss Best Practices and Lessons Learned

4


What is Integration (Really)?

5

• Connecting systems together –Many types of Systems – Power Generation, IT, Social

• Make smaller systems conform to a larger whole • Developing uniformity across systems


North American Top 20 Wind Owners

6

0.00

1,000.00

2,000.00

3,000.00

4,000.00

5,000.00

6,000.00

7,000.00

8,000.00

9,000.00

As of Nov. 2011


Turbine Manufacturers

7


Top Turbine Manufacturers

8


Integration Evolution

9

SCADA, Controller, RTUs, PLC, ICCP, etc.

EAM, Settlements, Historian, Outages, etc.

Dispatchable Intermittent Resources, Condition

Monitoring

Service Oriented Architectures, Cloud Computing, ESB, etc.


Maturity Model for Integration

10

As of Nov. 2011

Discrete data Limited value

Actionable Information – KPI’s

Distributed Control Systems (DCS) Distributed OSIsoft PI Historians Large Population of Data

Post Event Analysis DCS, PLC & PI

Business Intelligence Reliability, 4-Block

Outage & De-rate (UCF) Maintenance & Market

Relate all Data Sources Integration Framework

(PI, Plant Alarms, Maximo, SAP, UCF, GADS, Predictive Monitoring, NeuCo, LIMS, Plant View ..)

KPI’s Dashboards

Fleet Optimization

Drives Performance Excellence Process Costs, Asset Health,

Operational Performance, Market Value, Fleet Optimization

WEB Visualizing Plant Alarm, DCS Real-time WEB Graphics

Easy Access to Information

Standard User Interface WEB Visualization

System Dashboards Fleet Status Assessment

Fleet Drill down Subject Matter Experts

Engineering Applications Process Discrete to Data

Process Discrete Data Alarm Management

Expert Systems Predictive Monitoring, Optimization

Advanced Analysis & Process Optimization Equipment and Process Monitoring Closed Loop Process Optimization

50%

50%

50%

50%

50%

25%

15%

% Complete


Wind Integration Architecture

11


Integration Roadmap

12

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display

Step 4: Alert and Notify

Step 5: Calculate and

Analyze

Step 6: Integrate

Step 7: Report and

Share


Step 0: Pre-integration Readiness

13

Integration Check-list: Assemble the integration team, incl. SMEs Project management incl. timeline and budgets Review documents incl. GIA, PPA, and TSA Identify integration gaps and develop mitigation plan Business party coordination – internal and external


IT Integration Team

14

IT Project Manager

Infrastructure Lead

Commercial Lead Solution Lead

SCADA & External

Integration lead

Business SME Technical SME

Overall PM; Project schedule, timelines, and budget

Solution architect; Technical coordination across project disciplines

Operations and business expert; market

operations, regulatory, etc.

Circuits and communications; network infrastructure; Telco and LEC issues

Commercial applications; generation scheduling and dispatch integration; asset and outage mgt.

Integration to the PI system; forecasting and reporting; SCADA to PI configurations

3rd party SCADA and RTU; Generation dispatch and RTU; Market/ISO dispatch


Anatomy of a GIA

• Generator Interconnection Agreement –Agreement between the generator owner/operator and the

transmission owner/operator and the ISO –Specifies the following:

• Commercial and legal terms • Interconnection operations, metering, maintenance, performance • Financial agreements

–Things to look for in the GIA • Circuits, RTUs, and communications • Metering obligations – who? • Real-time data reporting – i.e. MET data

15


Anatomy of a PPA

• Power Purchase Agreement –Agreement between the “Seller” (Generator) and “Buyer”

(Energy Off-Taker) –Specifies the following:

• Commercial and legal terms • Forecasting and Reporting, metering and settlements • Availability, maintenance, and curtailments

–Things to look for in the PPA • Circuits, RTUs, and communications • Reporting and real-time requirements to the buyer • Metering data requirements • Settlement calculations

16


Anatomy of a TSA

• Turbine Supply Agreement –Agreement between the Generator and the “OEM” (Energy

Off-Taker) –Specifies the following:

• Commercial and legal terms • Turbine construction, maintenance, and performance • Electronic and SCADA systems

–Things to look for in the TSA • Availability guarantees and calculations • SCADA system details and description

17


GIA/PPA/TSA Document Review

18

Requirement GIA PPA TSA

Circuits and Communications Req: Provide data and POTS circuit and RTU to Transco Who: Infrastructure Lead

Req: POTS lines to be installed for MV90 data collection. Who: Infrastructure Lead

Req: Dedicated circuit for OEM support of assets. Who: Infrastructure Lead

Metering Req: Metering data must be provided to Transco. Who: SCADA/Ext Lead; Commercial Lead

Req: MV90 must be collected and stored and reported. Who: Solution Lead; Commercial Lead

N/A

Outage Management Req: Outages must be reported to Transco. Who: SCADA/Ext Lead; Solution Lead; Commercial Lead

Req: Outages must be tracked and reported. Who: Solution Lead; Commercial Lead

N/A

SCADA Equipment Req: RTUs must be installed to support data transfer to Transco. Who: SCADA/Ext Lead

Req: SCADA data must include req. data from OEM and substation. Who: SCADA/Ext lead; Solution lead

Req: OEM will provide the SCADA devices and software Who: SCADA/Ext Lead

Reporting Req: Monthly reporting for outages. Who: Solution Lead; SCADA/Ext Lead

Req: Forecasting and monthly reporting. Who: Solution Lead; SCADA/Ext lead

Req: Availability must be tracked as perf liability for OEM Who: Solution Lead

Review the GIA, PPA, and TSA and identify solution requirements that need to be met by the integration team, such as…


Business Party Coordination

19

Scheduling and Market Partipants

Transmission Operator

Energy Buyer and Off-Taker

Generation Scheduling & Dispatch

Accounting and

Settlements

Operations

External Business Parties

Internal Business Parties


Step 1: Prepare for Integration

20

Integration Check-list: Acquire SCADA and network architecture and diagrams Acquire circuits and provision IT infrastructure Understand OEM SCADA data sources and footprint Understand balance-of-plant data sources (substation, MET,

vibration, etc.) Procure and install servers and hardware


Diagrams and Drawings

• Network Architecture Diagrams –Help to identify SCADA devices, equipment, and IT infrastructure

such as routers, switches, and firewalls • Communication Diagrams – provided from Telco, LEC • Substation and Single Line Diagrams

–Identify substation, feeders, and interconnection design –Useful for designing substation displays

• Floor Plans –Physical locations of cabinets, panels, and other hardware

• Site Surveys –Used to determine the geography, topology, and geographical

coordinates of the site

21


Network Architecture Diagram Example

22


Floor Plan Example

23


SCADA Sources & Data Acquisition

24

Turbine Data: Real-Time Source: Turbine Controllers SCADA: OPC DA/HDA Others: Modbus, DNP3

Turbine Data: History ** Source: OEM Data Logger SCADA: Relational (SQL Server) Others: OPC HDA

MET Station: Real-Time Source: RTU, OEM Data Logger, Controller SCADA: DNP3, OPC Others: Vendor Proprietary

Condition Monitoring: Real-Time Source: RTU, Data Logger, Controller SCADA: DNP3, OPC Others: Vendor Proprietary

Substation: Real-Time Source: Revenue Meters, Power Delivery Assets (Transformers, Relays, Switches, etc.) SCADA: Data Concentrator, DNP3, OPC

Transco/ISO/MP: Real-Time Source: RTU to 3rd Party SCADA: Data Concentrator, DNP3, OPC


Data Logger vs. 1-Second Data

25

POW

ER

TIME

Typical industry standard data logger output (10-minute average)

1 second data output

Power (10 min)

• Capture data in full-resolution –Impacts the quality of the analysis –Don’t miss anything important!


SCADA by Turbine OEM

26

Real-Time SCADA Data Logger SCADA HMI

Clipper Modbus to turbine controller RTU

On-site SQL Server database with 10-minute aggregations

TOPS reporting solution and database (central reporting)

GE OPC DA server to turbine controller


Web based client – by farm

Suzlon OPC DA server to turbine controller

Central data collection (Denmark / India) of 10-minute aggregations

Suzlon reporting portal (web client) (central reporting)

Vestas OPC DA server to turbine controller


Vestas Online Business – by farm

RePower OPC DA server to turbine controller

FTP file access to 10-minute aggregations – must be licensed


Nordex OPC XML/DA server to turbine controller




Integration Roadmap

27

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display



Analyze

Step 6: Integrate

Step 7: Report and

Share


Step 2: Collect and Store Data

28

Integration Check-list: Obtain OEM SCADA software and installations Configure SCADA/GMS and/or PI System points Install and configure OEM SCADA software, PI interfaces, and

other related 3rd party software End-to-end data testing, incl. SCADA-to-GMS (and/or PI) point

check outs Establish data flow monitoring


SCADA Protocols - OPC

• What is OPC? –OPC Foundation Definition: Open Connectivity via Open

Standards –i.e. “You can get to it” via “a loosely defined standard

implemented differently be every vendor” –Microsoft COM / DCOM technology – circa 1998 –Software based data concentration

• Requires an OPC Server – provider of SCADA • Used by OPC Clients – consumers of SCADA • OEM / Vendor defined implementation

29


SCADA Protocols: OPC DA / HDA / XML / UA

• OPC DA – most basic OPC providing current values, timestamps, and quality only

–Basic data types: Boolean, Byte, Short/Long, Float, Double, Char, String, Dword (32-bit unsigned integer / flags)

–OPC Namespace implemented by OEM/vendor –ItemID uniquely identifies OPC data point – path and

measurement • OPC HDA– same as OPC DA but with historical access • OPC XML-DA – supports web services and SOAP • OPC XML-UA – Unified Architecture – next generation

of OPC

30


SCADA Protocols - IEC 61850 & IEC 61400

• IEC 61850 is a Standard with many SCADA protocols and vendors that adhere to the Standard

• Intelligent Electronic Devices (IED) –Common devices found in substations including relays,

transformers, breakers, etc. –Distribution Automation, Protection, and Control – i.e. intelligent

re-closers • Control System Vendors

–Many renewable SCADA vendors implement IEC 61850 IED controllers that follow IEC 61850

• Data integration directly to IEC 61850 is possible using integration middleware software (Sisco AX-S4 IEC 61850 interface)

31


SCADA Protocols – DNP/3

• Distributed Network Protocol • Adopted by IEEE • Secure authentication to SCADA devices • Master Station to device Slave configuration

–Master instructs the slave

• Supports multiple events per object (point) • Interfaces to RTUs and IEDs

32


Data Concentrators - Hardware

• Aggregates many SCADA sources to a common data access point through SCADA / RTU gateway

• Provides additional data security and abstraction to SCADA sources

• Vendors: SEL, Subnet, Siemens • Schweitzer Engineering Laboratories (SEL)

–SEL 2032 / SEL 3530 – RTAC –Supports multiple protocols including DNP/Modbus/IEC

61850

33


Data Concentrators - Software

• Aggregates many SCADA sources to a common data access point / gateway through Windows technologies

• Protocol Converters –Used to convert SCADA protocols to OPC DA/HDA –i.e. Modbus/DNP3/IEC 61850 to OPC –i.e. OPC XML-DA to OPC DA/HDA

• Vendors: Matrikon, Kepware, Advosol, SISCO –Matrikon – leaders in OPC conversion technologies –SISCO – ICCP and IEC 61850/61400 conversion

34


Emerging Trend – Direct to Controller

35

Bypass the OEM SCADA system and connect directly with the controller. This requires that the Vendor/OEM provide direct access to the turbine controllers!

Bachmann M1 Controller (in situ - Sulzon S64 turbine)

Direct Controller Access: • Access to all state variables • Access to 1-2 second data • Many connection methods • Ability to use IEC standards:

• IEC 61850 • IEC 61400-25

Value: Expanded data points, full data resolution


OEM SCADA Integration

36

OEM SCADA Controller OPC IEC 61850 Native Interface


PI Interfaces

• Common PI Interfaces –PI-OPC Interface: 1 of every 3 interfaces sold by OSIsoft

• Handles OPC DA/HDA/XML-DA SCADA • Typical for Real-Time turbine controller data • Easy to configure; Good utility and troubleshooting tools

–PI-DNP3 Interface: • Handles DNP3 SCADA • Typical for Real-Time substation and MET equipment • Often requires configuration assistance in conjunction with SCADA

expert

–PI-Modbus • Handles Modbus Serial/TCPIP SCADA • Usually abstracted by data concentrator

37


PI Interface Architecture

• Considerations and Best Practices –Central vs. Distributed Data Acquisition

• Vendor/OEM OPC server solution can drive design • Data concentration across multiple farms / single farm

–PI Interfaces and Buffering • Data buffering: PI Buffer Server or PI Buffer Subsystem • OSIsoft recommends putting interfaces close to SCADA source • Practical design approach – Supportability vs. Reliability balance

–PI Interface Scalability and Tuning • PI OPC interfaces require scalability tuning for high point-counts • Interface monitoring is very important

– Stale data – PI Interface Status Utility – Interface performance – Event counting and PerfMon

38


Integration Roadmap

39

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display



Analyze

Step 6: Integrate

Step 7: Report and

Share


Step 3: Monitor and Display

40

Integration Check-list: Prepare asset management applications and asset models Edit or modify displays for addition of new sites Update data dashboards and situational awareness

applications Modify system security for user access to new site data


Asset Management Applications

• Enterprise Asset Management (EAM) –SAP, IBM/Maximo, Ventyx –Enterprise level management of asset inventory and

hierarchy, maintenance management, work order management, etc.

–Allows API and web service level integration access to other systems

• Asset and Demographic Databases –Generally custom solutions –Database level integration access to other systems –Great for query and report integration!

41


Demographic Database Example

42

Basic Demographic and Asset Records Only


PI Spotlight: PI-AF Asset Hierarchy

43

• PI-AF Asset Model • By Turbine Model, Farm,

Region, State, Portfolio • Contains the asset hierarchy for

all turbines, wind farms, etc. • Data attribution for both PI

tags and demographic database


PI Spotlight: PI-AF Asset Templates

44


Monitoring and Displays

• Asset Performance and Monitoring –Fleet Level Summary and Displays –Substation Displays – what is being delivered! –KPIs and Dashboards –Asset Level Displays

• Generation Forecasting –Forecasting vendors – AWS True Power, 3-Tier, Global

Weather Corporation –Forecasting Displays

45


Control Room Monitoring

46


Fleet Summary – Turbine State

47


SCADA – ERCOT Dashboard

48


Fleet Summary - Capacity

49


PI Web Parts Dashboard

50

Fleet Capacity

By Wind Farm

All Wind Farms PI-AF Tree


PI Web Parts Dashboard

51

All Farms in PI-AF

By Turbine

All Turbines in Farm


Substation Display – PI ProcessBook

52


Substation Display – SCADA

53


Asset Display – by Turbine

54


Asset Display – by MET Station

55


Geospacial Displays – Google Earth

56


Geospacial Displays - SCADA

57


Geospacial Displays – SCADA (Zoom)

58


Integration Roadmap

59

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display

Step 4: Alert and

Notify


Analyze

Step 6: Integrate

Step 7: Report and

Share



60

Integration Check-list: Analyze and identify triggers for alarms and notifications Configure alarms and points in GMS/PI Configure PI notifications and messaging Alarm, notification, and acknowledgement testing Long-term tuning of alarms and notifications


Alarming Basics

• Alarming –Handled by either Generation Management System (GMS)

or by other tools, such as PI Alarm View –Alarm States – Inactive, Active, Acknowledged,

Unacknowledged –SCADA Alarms triggered by one or more out-of-bound

conditions – i.e. Breaker Opened, voltage deviation, temperature over maximum range, etc.

–May force an action on the part of an operator or other employee

61


Alarm Life-cycle

62

Courtesy: ABB/Ventyx Sympony Plus White Paper 2010


Typical Renewable Alarms

• Operational Alarms –Breaker Status of Feeders or Interconnection –Wind Speeds above Cut-In but no Generation –Voltage Deviation –Temperature Alarms – Bearings, Gearbox, Generator –Overspeed Alarms – Gearbox, Generator –Blade Asymmetry

• Non-Operational Alarms –Stale or bad SCADA data –Comm Errors or other similar failures –IT servers, equipment, or device errors or failures

63


Notifications

• Types of Notification –Audible or visual notification – alarming application sends

visible or audible alarm –Electronic notification – send operator an e-mail, text, chat,

etc. to immediately alert –Auto-Dialer notification – 3rd party service will call and alert

the operator of an error

• Notification applications –PI Notifications –Smart Signal or other similar application

64


PI Notifications – Breaker Alarm

65


Integration Roadmap

66

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display



Analyze

Step 6: Integrate

Step 7: Report and

Share


Step 5: Calculate and Analyze

67

Integration Check-list: Configure KPIs, aggregates, and other calculations Configure analysis tools for historical data Configure generation forecast calculations


Key Performance Indicators

68

• Performance metrics used to more effectively measure operational or financial conditions

• Can be calculated by turbine, farm, region, state, or any other demographical distinction

• Can be calculated along any time range – instantaneously, hourly, daily, monthly, etc.

• Example: At what capacity did the Vestas V100 turbines operate in California during August 2013?

–KPI: Capacity Factor –Demographic: Vestas V100 model types –Time Range: Aug 1 to Aug 31 2013


Key Performance Indicators

69

• Capacity Factor: Energy Produced / Installed Capacity • Availability Factor: Hours Run / Hours Available

–Simple availability vs. manufacturer availability –Impacts O&M contracts –Market and Transco Curtailment impacts Hours Available

• Expected Energy: Energy according to Manufacturer Specs –Derived from Manufacturer Power Curves –Wind Speed and Air Density and Sheer Factor adjustments

• Manufacturer Lost Production: Expected Energy – Energy Produced

–Impacts O&M contracts and warranty • Common Status – common status of the turbine state

normalized across OEM types in the fleet


Data Aggregations

70

• KPIs in Aggregate –Measure KPI performance by farm, state, region, OEM type,

etc. –Potentially available directly from OPC / Data Logger and/or

plant controller –Can be calculated from aggregations for all turbines at a farm

• Accumulators –Production: i.e. Total production of a turbine or farm –Time: i.e. Total run hours of a turbine, Amount of time that a

turbine was in a ‘good’ status • Other Aggregates

–# of Operating Turbines for a given time range


Data Aggregations – Substation

71

• Substation vs. Wind Farm Data –Recorded by Power Delivery Equipment –Revenue Meter Aggregations

• Real-time power as reported by revenue meter • Invoice and settlement data! • MV90 Data Streams – settlement gospel!

–Substation data can be used to validate turbine data • Gross Energy * Power Loss Factor = Low Side Energy

• Substation data is not always available –Limited by visibility to data concentrators and SCADA sources –i.e. Energy delivered to Transco substation


PI Calculations

• Data Aggregations –PI Performance Equations: PI calculations using PI functions,

syntax, and conditionals –PI Totalizers: PI calculations for sum/avg/range (etc) across a

period of time or # of events –PI ACE: .NET calculations – requires PI module database –PI-AF Data Reference / Analysis Rule Plug-Ins - .NET plug-ins

to PI-AF –PI ABACUS – announced for 2014

• Example: Total Active Power (kW)

72


PI Analysis

• Data Analysis –PI Datalink – Excel Add-In to do ad-hoc analysis of PI data

• Provides lists of data according to the data functions selected

–PI Coresight – used to do ad-hoc Analysis of the PI AF asset model

–Microsoft Power Pivot (Power View) – Microsoft BI (MDA) tool accessible within Microsoft Excel for analysis

73


Integration Roadmap

74

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display



Analyze

Step 6: Integrate

Step 7: Report and

Share


Step 6: Integrate to Other Systems

75

Integration Check-list: Configure interfaces to Financial and Settlement systems Configure interfaces to Outage Management systems Configure interfaces to Generation Scheduling systems Configure interfaces to Generation Dispatch Integrate to ISO / Market Dispatch


PI Web Services

76


Settlements Integration

• Hourly integrated generation to settlement systems –Accounting and accruals –Invoicing systems

• Data Source should be revenue quality data for settlements and invoices

–Revenue meter data – MV90 –ISO Market sources

77


Settlements Integration

78


Settlement Integration using PI-AF

79

PI-AF Model • AF Table links to business

database for LLC Relationships

• Both turbine and revenue meter generation modeled

• One element per turbine in heirarchy

PI OLEDB Enterprise Config. • TVFs used to “columnize”

templates • Views used to configure

and join table lookup and PI point data references in templates

Web Services • Custom web services

developed in .NET to query PI OLEDB Ent.

• Web methods are mapped directly to PI OLEDB Ent. queries

• Security mapping in PI-AF is assigned App Pool account


Outage Management Integration

• Automatically log outages into the outage management system

–Logging of generating capacity of wind farm –Automated creation and update of tickets in the ISO /

market systems

• NERC GADS Reporting –Classification of outages according to GADS coding system –Sources of reduced capacity

• ISO / Market and Transco Curtailments • Maintenance and outages – planned and unplanned • How do you differentiate these in SCADA?

80


Outage Management Integration

81


Outage Management Integration using PI-AF

82

Operating Turbines • PI PE calculations

determines normalized operating state for every turbine

• Operating Turbines by farm calculated by PI-AF Roll-Up Plug-In

PI Notifications • Custom PI-AN Delivery

Channel Plug-In developed for outage web service security and data requirements

• PI Notification service sends updated operating turbine count to web service hourly

Outage Web Service • Unplanned capacity

calculated (Unplanned = Total Capacity – Planned Outages – Current Capacity)

• Revised capacity auto-updated in MISO CROW system


Generation Scheduling Integration

• Generation Forecasting –Statistical vs. Theoretical Forecast Methods –Several 3rd Party Wind Forecasting Providers –Theoretical Wind Forecast Methods

• Forecast Types –Based on ISO / Market Requirements

• Real-Time / Hour Ahead Forecast (MISO 5-Min DIR) • Day Ahead Forecasting • Intra-Day Forecasting • Extended Forecasting

• Integration to Internal, External, and 3rd Parties

83


Scheduling Integration - Internal

84


Scheduling Integration using PI-AF

85

SQL Server • Weather data stored in

SQL data warehouse • SQL Functions used to

model production forecast by plant

• PI-RDBMS interface used to import hourly forecast from SQL Server (*-7d)

PI-AF and PI OLEDB Enterprise • PI-AF elements modeled

to represent total plant forecast

• PI OLEDB Enterprise used for TVFs and views needed to support web service queries

Web Services • Custom web services

developed in .NET to query PI OLEDB Ent.

• Web methods are mapped directly to PI OLEDB Ent. queries

• Security mapping in PI-AF is assigned App Pool account


ISO / Market Dispatch Integration

• Dispatchable Intermittent Resources –Provides better grid reliability by providing the system

operator ability to curtail wind generation as needed –Most system operators have implemented or will be

implementing Wind curtailment measures –Can be done for a variety of reasons

• Oversupply of generation - • Transmission congestion • Operational curtailment

• Requires integration to Control Systems • Better forecasting methodologies needed for financial

performance

86


Market Dispatch Integration

87


MISO Curtailment Example

88

Blue Line = Forecast Yellow Line = Dispatch Red Line = Actual Gen

Dispatch Down


Dispatch Performance Monitoring

89


Integration Roadmap

90

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display



Analyze

Step 6: Integrate

Step 7: Report and

Share


Step 7: Business Party Reporting

91

Integration Check-list: Determine reporting requirements for business parties – i.e.

market participants, financial stakeholders, energy buyers, settlements, etc. Configure reports for each participant Configure reporting engine and automation


External Reporting

• Reporting to Scheduling and Market Participants –Generation Forecasting reports

• Day-ahead, Intra-day, and Extended Forecast • Real-time Expected Energy – Dispatchable Wind Assets

–Weather and real-time reporting –Outage Reporting

• Reporting to Energy Off-Takers –Generation Interval Reporting

• Daily reports for Expected Energy • Month-end reporting

–Outage Reporting

92


Internal Reporting

• Reporting to Finance and Settlements –Production Reporting

• Monthly reporting of hourly generation by Farm • OEM data logger is required for operational reporting • MV90 data is required for settlements

• Operational Reporting –Outage Reporting

• Monthly downtime and planned outages • Wind Farm curtailments per wind farm

–Weather Reporting

93


Production Reports

94


Production Loss Reporting

95


Automated Reporting

• Automated Periodic Reporting –Interface to electronic destinations is often required,

including e-mail, FTP, or web services –Frequency of reporting is prohibitive in many cases

• Impossible to manually generate a new report every 5-minutes or hourly

• Manual report generation is prone to errors and mistakes

–Applications available to generate and send reports • SQL Server Reporting Services – auto-generate reports through

report subscriptions • E-recipients can be tricky to handle – web service calls, varieties of

FTP and SFTP, custom e-mail attachments / bodies, etc.

96


Generation Forecasting Example 1

97


Generation Forecasting Example 2

98


Data Determinants to 3rd Party Weather Provider

99


Web Service to Energy Off-Taker

100


SSRS Report Subscriptions

101

Use Microsoft SQL Server Reporting Services to automatically generate and send reports to report recipients of different e-Recipient types.


Integration Roadmap

102

Step 1: Prepare

Step 2: Collect and

Store

Step 3: Monitor and

Display



Analyze

Step 6: Integrate

Step 7: Report and

Share Integration Complete!


What’s Next for Renewables?

• Rise of Big Data –Wind and Solar have a very high point/MW ratio –Higher resolution data for new devices such as

Synchrophasers –Quicker and more nimble data analysis

• Fault Detection and Reliability –Fault analysis handled by central engineering and

operations –Quicker detection and better response times

• More data from other sources such as batteries, advanced meters, pumps, etc.

103


Contact Information

104

Bob Knox, Sr. Manager & Historian Lead E-Mail: [email protected] Phone: (302) 545-4656

Mario Marchelli, Director - EMCS E-Mail: [email protected] Phone: (832) 563-0897



emmos 2013 renewable resource integration training

Documents