Asset Operations

WebinarApril 30, 2015

Slide Title

2

Asset Operations Solutions2

Consistent process to track plant conditions and capture changes

– Improve communication – Reduce duplicative recording – Increase consistency– Standardize processes– Alert / warn on deviation, data-not-

provided-by-deadline– Audit data entry, approval, and submittal

3

Slide Title

3

In a nutshell

Module Purpose

Outage Management Capture and manage planned, urgent, and emergency events

JournalLogging Application. Automated journal logging for operations, plants, and other departments

Plant InstructionsWorkflow Messaging between Dispatchers and Plant Controllers

Plant Interface

Allow the power plants to declare unit limits, ramp rates and other characteristics. Allow plants to view day-ahead schedules and (backup) dispatch instructions

GADS

Used to manage Generating Availability Data Systems (GADS) event lifecycle, including outages, derates, reserve shutdowns, and metrics

Energy SchedulingAutomate declaration and ISO Self-Scheduling of Qualifying Facilities (QF) and Must-Take Resource Contracts

4

Slide Title

4

• Scenario #1– Forced Outage event automating a Journal Entry

• Scenario #2– Declaration of Limits Change from a Plant

• Scenario #3– Issue Message from a RT Operator to Power Plants

• Scenario #4– Issue Instruction for a Manual Change of Load– Issue Instruction to reach Set Point

3 Scenarios

5

Slide Title

5

• Leverage PCI’s Journal Technology

• A recording of any occurrence the impacts power system operation or business

• Searchable• Auditable• Configurable

– Create – Customize– Automate

Operator Logging

6

Slide Title

6

Operator Logging

Utilize the journal to enter and monitor events Record various event types throughout the day Monitor daily events in a rolling report grouped by Operating Date and

Hour Ending Many Default Log Types provided “out-of-the box” Custom Log Types may also be defined

• Each log type has a unique definition of attributes• Attributes may be required• Attributes may utilize GenBase data

Slide Title

7

Example Business Applications

Operator annotation of events:– Record a brief outage (unit Bravo unresponsive for 10 minutes)

Record operator action– Checklist of Shift to-do-list.

Personnel conflict– Plant operator refused instruction

Deviation from schedule/dispatch– Operator instructs plant to back down from dispatch point due to

negative prices Internal system failure

– Computer failed to respond. Rebooted computer. Used backup process. Inter-tie checkout

– Record checkout with counterparty, counterparty agent and time of checkout

Uses: Settlement, Legal, Managerial, Compliance

7

8

Slide Title

8

Suggested Log Types

Log Type Description

Outage Log Logs approval of forced outage records. Automatically generated on approval by GSMS Outage Management.

Ops Superintendent

Journal entries as chronicled by the operations superintendent.

Security - The following roles/group will be granted WRITE access to these logs by default: Superintendents

System Log Log used by dispatchers only

Security - The following roles/group will be granted access to these logs by default: RT Dispatchers

Fuel Issues Notes pertaining fuel or issues with fuel supply

Security - The following roles/group will be granted WRITE access to these logs by default: Plant Management, Plant Operations, Superintendents, RT Dispatchers, DA Analyst

Power Marketing Notes related to sales and purchasing (trades)

Could split Power Marketing into two log types: RT Trades and DA Trades or use an attribute to sub-group them

Security - The following roles/group will be granted WRITE access to these logs by default: Superintendents, RT Dispatchers, DA Analyst

Curtailments Couple journal with PCI e-tag application to automatically log tag cuts

Security - The following roles/group will be granted WRITE access to these logs by default: Superintendents, RT Dispatchers, DA Analyst

9

Slide Title

9

Add Journal Entry

User can add Journal Entries

User can filter, edit, or export

Journal Entries

Journal Entries can happen in RT, DA or any other time

10

Slide Title

10

Sample Log Report

Slide Title

1111

Scenario#1: Automated Journal Entry

Journal – Outage Log Triggered from Forced Outage Event (B)

Email: Email distribution may be configured to issue email notices of Events

B

ACoal Pl

User records a Forced Outage (A)

Slide Title

13

Plant Interface13

• Make Daily Declarations of key offer inputs

• Notification and approval process to Front-Office for inclusion in Offers

• Auditable

14

Slide Title

14

PI MW Limits

Hourly Limit Declarations.

Effective until changed

15

Slide Title

15

PI: Ramp Rates

Ramp Rate Curves Default Ramp

Rate

Choice for unit offers

16

Slide Title

16

Startup Parameters

(A)

(B)

(C)

• Capture Other Unit Characteristics such as Start Times, Costs, and Fuel Requirements (A)

• Start-up Limits (B)

• Notification Times and current Temperature State (C)

17

Slide Title

17

PI: Requests & Approvals

Open Request

Approve Request

18

Slide Title

18

Used to created auditable and systematic procedures between departments within an organization

Message Categories:• Broadcasts• Instructions

Records 3-part communications between parties.

Plant Instructions

Situational Awareness

Column Group 1

Columns Group 2

Split screen provides monitoring for ~70 units without screen scroll

(A) Select 1 or more Units or Plants and choose an Action (B) to issue an Instruction

(A)

(B)

Slide Title

20

Capability for a group to send a message to one or more other users Spotlight: An Operations group can create, edit and send messages to

one or more Plants• For commonly-used messages, the system will allow Dispatchers

the ability to send pre-formatted messages.• Plants will be required to acknowledge messages.• Authorized users will be able to view and search historical

messages

Broadcasts

21

Slide Title

21

Add new Broadcast

Slide Title

22

o Manually Change Loado Go To …o Go To Emergency Maxo Go to Emergency Mino Hold Generation

o Go To Set Pointo Change AGC Blocko Start Up Procedureo Shut Down Procedureo Change (MSU) Configuration Blocko Custom

Instructions

Capability for one party to deliver instructions to others• Spotlight: Managing operations instructions to plants • Multiple types of instructions:

• Requires response by the Plant Control Room within 3 minutes• Plants is required to acknowledge messages• Authorized users may view and search historical messages

Issue – Startup Instruction

Startup Response

26

Slide Title

26

Location User ContextPlant Site Plant Manager PlantPlant Site Plant Operator PlantPlant Site Plant Viewer PlantPlant Site Co-owner PlantPlant Site 3rd Part Contract Plant / OfficeTradefloor Real Time Dispatcher Real-TimeTradefloor Real Time Trader Real-TimeTradefloor Superintendent Real-TimeTradefloor Day Ahead Analyst PlanningPlanning Outage Coordinator PlanningVaries GADS Admin GADSBack Office Settlement Analyst Settlement ValidationRegulatory Compliance Audit / VerificationIT Admin All

Who benefits?

27

Slide Title

27