Asset Operations Webinar April 30, 2015

Slide Title 2 Asset Operations Solutions 2 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

Slide Title 3 3 In a nutshell ModulePurpose Outage ManagementCapture and manage planned, urgent, and emergency events Journal Logging Application. Automated journal logging for operations, plants, and other departments Plant Instructions Workflow 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 Scheduling Automate declaration and ISO Self-Scheduling of Qualifying Facilities (QF) and Must-Take Resource Contracts

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 4 3 Scenarios

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 5 Operator Logging

Slide Title 6 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

Slide Title 8 8 Suggested Log Types Log TypeDescription 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 CurtailmentsCouple 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

Slide Title 9 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

Slide Title 10 Sample Log Report

Slide Title 11 Scenario#1: Automated Journal Entry Journal – Outage Log Triggered from Forced Outage Event (B) distribution may be configured to issue notices of Events B A Coal Pl User records a Forced Outage (A)

Slide Title 12 Outage Management Planned Outage Forced Outages: Urgent and Emergency Events Plant Test Schedules PSS / AVR Events

Slide Title 13 Plant Interface 13 Make Daily Declarations of key offer inputs Notification and approval process to Front-Office for inclusion in Offers Auditable

Slide Title 14 PI MW Limits Hourly Limit Declarations. Effective until changed

Slide Title 15 PI: Ramp Rates Ramp Rate Curves Default Ramp Rate Choice for unit offers

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)

Slide Title 17 PI: Requests & Approvals Open Request Approve Request

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. 18 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

Slide Title 21 Add new Broadcast

Slide Title 22 o Manually Change Load o Go To … o Go To Emergency Max o Go to Emergency Min o Hold Generation o Go To Set Point o Change AGC Block o Start Up Procedure o Shut Down Procedure o Change (MSU) Configuration Block o 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

Slide Title 23

Issue – Startup Instruction

Startup Response

Slide Title 26 LocationUserContext Plant SitePlant ManagerPlant Plant SitePlant OperatorPlant Plant SitePlant ViewerPlant Plant SiteCo-ownerPlant Plant Site3 rd Part ContractPlant / Office TradefloorReal Time DispatcherReal-Time TradefloorReal Time TraderReal-Time TradefloorSuperintendentReal-Time TradefloorDay Ahead AnalystPlanning Outage CoordinatorPlanning VariesGADS AdminGADS Back OfficeSettlement AnalystSettlement Validation RegulatoryComplianceAudit / Verification ITAdminAll 26 Who benefits?

Slide Title 27