Overview of eDART’s Gen Checkout Functionality
Overview of eDART’s Gen Checkout Functionality
July 2007
PJM ©2007
Topics
• High Level Explanation
• Form Level Explanation
• Process Overview for Handling Example
Checkouts
• Contacts
www.pjm.com
2
©2007 PJM
Topics
• High Level Explanation
• Form Level Explanation
• Process Overview for Handling Example
Checkouts
• Contacts
www.pjm.com
3
©2007 PJM
Background
• Unit availability scheduled in eMarket
• Unit outages submitted via eDART – Generator
Ticket (GT)
• No way to match up numbers and verify what is
scheduled in eMarket matches what is available,
based on outages
www.pjm.com
4
©2007 PJM
Gen Checkout Breakdown
• This functionality lists on a per unit basis the
eMarket values and compares them to outages
• Any issues are highlighted
• Companies “Acknowledge” when eMarket
values are in sync with outage availability, within
a specified tolerance
– Acknowledgement will be for Today or Tomorrow
www.pjm.com
5
©2007 PJM
Report Overview
eMarket Values
eDART MW Ticket Values
Economic Max
Emergency Max
Installed Capacity
Reductions
Ambient Adjustments
Adjusted Capacity
Difference
eDART Gen Checkout Calculations
www.pjm.com
6
©2007 PJM
Model Issue Resolution
eMarket
Gen Checkout
Gen Tickets
ABC1
ABC2
ABC
ABC
ABC3
ABC = ABC3 + ABC2 + ABC1
www.pjm.com
7
©2007 PJM
• Problem: Multiple units in
eMarket and one in Gen
Tickets
• Resolution: eMarket values
summed and shipped to
eDART
Model Issue Resolution (cont’d)
eMarket
Gen Checkout
Gen Tickets
ABC1
ABC
ABC1
ABC2
ABC3
ABC1 = ABC3 + ABC2 + ABC1
www.pjm.com
8
©2007 PJM
• Problem: Multiple units in
Gen Tickets and one in
eMarket
• Resolution: eDART values
summed under one unit
(usually the first unit)
Model Issue Resolution (cont’d)
• Problem: Multiple Units in
Gen Tickets mapped to
multiple eMarket Units
(ex. Combined cycles)
• Resolution:
– eMarket values summed
and shipped to eDART
– eDART values summed
under one unit
– eMarket sums compared to
eDART sums
www.pjm.com
9
©2007 PJM
Calculated Fields
• PJM Scheduling Coordinator (SC) will determine if under
Econ or Emerg Max
Condition
Adjusted Capacity
Difference ( %)
AC = ICAP + Amb. Adj. − Re duct − Incremental
Economic
Incremental = EmergencyMax − EconomicMax
AC = ICAP + Amb. Adj. − Re duct
Emergency
Diff =
Adj.Cap. − EconomicMax
× 100
AdjustedCap
Diff =
Adj.Cap. − EmergencyMax
× 100
AdjustedCap
*Note: Ambient Air values will be the opposite sign of what is reported in
Generator Tickets
www.pjm.com
10
©2007 PJM
Report Formats
• The report can be displayed in two formats:
– Breakdown: Unit by unit, showing the warning flags
– Totals: Summary by unit type
www.pjm.com
11
©2007 PJM
Difference Exception Flag (Underbidding)
• Underbidding – Adjusted Capacity exceeds
eMarket bid
• If the Difference is greater than 10% line will
appear in red
• Note: If Acknowledgement Tolerance violated for
any unit report cannot be acknowledged
www.pjm.com
12
©2007 PJM
Difference Exception Flags (Overbidding)
• Overbidding – eMarket bid exceeds Adjusted Capacity
• PJM Scheduling Coordinator sets Ambient Air Warning
and Acknowledgement Tolerance percentages & initiates
acknowledgement process
– Ambient Air tolerances for which the eMarket value can be above the
adjusted capacity and are set based on unit type.
• If Warning Tolerance is greater, then absolute value of
Difference line will appear in yellow
• If Ack. Tolerance greater, then Difference line will appear
in red
– If Ack. Tolerance violated for any unit, report cannot be acknowledged
www.pjm.com
13
©2007 PJM
Ambient Air Violation Quick Handling
• Ambient Air Tickets can be created directly from
Gen Checkout in order to checkout on tickets
which are acknowledgement violators for
eMarket values exceeding Adjusted Capacity
• An auto approve tolerance, set per unit type, will
automatically approve or even activate (if
scheduled to start within an hour) if the ambient
value in summation with the other ambient
tickets for unit are within tolerance
www.pjm.com
14
©2007 PJM
Acknowledgement Follow-Up
• After at least all “Ack. Violations” have been
resolved gen owner acknowledges report
• If valid reason for Ack. Violation remaining call
PJM Scheduling Coordinator to discuss and
Acknowledge
www.pjm.com
15
©2007 PJM
Miscellaneous Reports
• Past reports will remain on-line
• History Log of who acknowledged reports also
available
www.pjm.com
16
©2007 PJM
Topics
• High Level Explanation
• Form Level Explanation
• Process Overview for Handling Example
Checkouts
• Contacts
www.pjm.com
17
©2007 PJM
Where is Gen Checkout?
eDART Main Menu
Gen Checkout
Section
Click on “PJM
Status Report”
Gen Checkout is located in eDART under “PJM
Status Report”
www.pjm.com
18
©2007 PJM
Main Menu
• Five buttons comprise the Gen Checkout Menu:
– Today: Displays today’s Gen Checkout report
– Tomorrow: Displays tomorrow’s Gen Checkout report
– Historical: Allows users to view past Gen Checkout
reports
– Ack. Reports: Log of who acknowledged past Gen
Checkout reports and when
– Unit Translation Report: A description of how units in
eDART generator Ticket application are grouped
together in Gen Checkout and their names in the PJM
EMS
www.pjm.com
19
©2007 PJM
Process For Handling Current Day Checkout
• By 0300 and 1700 all acknowledgments should be
complete
• SC will call gen owner if not acknowledged
• Click “Today” on the Gen Checkout Menu to view current
days report
• Click “Tomorrow” on the Gen Checkout Menu to view
tomorrow’s report
• If there are any yellow or red rows, resolve them via GT
or eMarket
• Report values updated every 10 minutes
www.pjm.com
20
©2007 PJM
Discrepancy Handling
• Gen Checkout basically reporting mechanism
• All resolutions handled via eMarket and/or GT
– For more information on eMarket functionality please
go to http://www.pjm.com/etools/emrkt.html
– For more information on eDART – Generator Ticket
functionality please go to
http://www.pjm.com/etools/edart.html
Note: Interface available in Gen Checkout to bulk load Ambient Air
Generator Tickets w/ quick approval activation
www.pjm.com
21
©2007 PJM
Help for Handling Ambient Air Violations
• Additional form available in Gen Checkout which
displays units with acknowledgement violations for
overbidding
• Form suggests Gen Ticket ambient air value for each
violating unit
• User can determine which tickets to be created
automatically, and send them immediately to PJM
• User can also adjust ambient air value before sending it
to PJM
• Ambient air values within unit type tolerance approved
and sometimes activated automatically
www.pjm.com
22
©2007 PJM
Today’s Report
www.pjm.com
23
©2007 PJM
Today’s Report Filter
www.pjm.com
24
©2007 PJM
Today’s Report Filter (cont’d)
• Report Date: Current Date
• Last Synced: Timestamp for latest data sync with
eMarket
• Last Ack Start: Timestamp for when PJM SC requested
members to begin acknowledging reports
– Note: It is possible for the SC to ask for gen owners to reacknowledge report at later time
• Last Ack End: Timestamp for when dispatchers end
acknowledgement process
• Emergency Max: If “No”, then using Economic Max
www.pjm.com
25
©2007 PJM
Today’s Report Filter (cont’d)
• Warning Tolerance: Based on Unit Type if the difference
is less than this value, row will be in yellow
• Ack. Tolerance: Based on Unit Type if the difference is
less than this value, row will be in red
• If the report has not yet been acknowledged, then the
message “Acknowledgment Required” will display
• Company: Company for which user is affiliated
• ASM: Unit’s Ancillary Service Market (ASM)
www.pjm.com
26
©2007 PJM
Today’s Report Filter (cont’d)
• Zone: Unit’s Control Zone
– Multi-select using Ctrl or Shift keys
– All Zones selected by default
• Type: Type of units to be displayed
– Multi-select using Ctrl or Shift keys
– All Types selected by default
• Period: Hour ending time representing peak
hours shown
– Multi-select using Ctrl or Shift keys
– All Periods selected by default
www.pjm.com
27
©2007 PJM
Today’s Peak Report Filter (cont’d)
• Totals/Breakdown:
– Totals Report displays summary based on unit type
– Breakdown Report displays unit-by-unit breakdown
and includes flags (Default Report)
– Click “Apply Filter” to get report
www.pjm.com
28
©2007 PJM
Today’s Peak Report - Totals
www.pjm.com
29
©2007 PJM
Today’s Peak Report - Breakdown
www.pjm.com
30
©2007 PJM
Today’s Peak Report Buttons
• Acknowledge: Once acknowledgement process
initiated by SC (around 0230) to acknowledge
report, simply click this button
– NOTE: Remember this button will not appear unless
no red rows exist
• If certain rows must remain red please get in touch with SC
• Main Menu: Returns user to Status Report Menu
www.pjm.com
31
©2007 PJM
Sorting
• All columns except Period and Sales can be sorted by
user discretion
• Default sort is by unit name
• The columns will be sorted in the numerical order you
enter in the box above the column
– Ex: To sort on Unit Type then ICAP enter a “1” over Unit Type and
a “2” over ICAP
– Note: Be sure to remove any number that are over any columns
that you don’t wish in the sort order
www.pjm.com
32
©2007 PJM
Special Sorting
• Sorting for the columns Reduct, Amb. Adj., Econ Max,
Emerg Max, Adj. Cap. and Difference are handed
specially
– Sorting will not be performed on each period level
– Filtering is based on max period value
• Note: Unit headings will be repeated multiple times in the
report, so they are always visible
www.pjm.com
33
©2007 PJM
Column Definitions
• Zone: Units control zone
• Unit Name: Commercial name or name of unit group
eMarket
Gen Checkout
Gen Tickets
eMarket
Gen Checkout
Gen Tickets
ABC1
ABC1
ABC2
ABC
ABC
ABC
ABC1
ABC2
ABC3
ABC3
ABC = ABC3 + ABC2 + ABC1
www.pjm.com
34
©2007 PJM
ABC1 = ABC3 + ABC2 + ABC1
Column Definitions
•
•
•
•
Unit Type: Type of unit
ICAP: Installed capacity for unit
Sales: Units capacity sales
Period: Peak periods as outlined by PJM as the times
values evaluated for
– Period name displayed
– Hour Ending time represented shown in filter
www.pjm.com
35
©2007 PJM
Column Definitions (cont’d)
• Reduct: Sum of reduction of non-Ambient Air Generator
Outage Tickets for unit at time of Period
– Note: If unit was scheduled to have already returned, but was
not, outage will be included for next upcoming peak
• Example:
– Given:
»
»
»
»
Estimated End Time= 1300
Current Time= 1500
Day Peak Time= 1700
Eve Peak Time= 2200
– Result: Outage will be included in Day Period but not in Eve
– Also if MW Revision made on ticket reduction value used will be
based on revision applicable at each peak time
www.pjm.com
36
©2007 PJM
Column Definitions (cont’d)
• Amb. Adj: Sum of reduction of Ambient Air Generator
Outage Tickets for unit at time of Period multiplied by -1
– Amb. Adj = (-1) • (Reduction)
• Econ Max: Economic Max bid for period assigned in
eMarket
• Emerg Max: Emergency Max bid for period assigned in
eMarket
www.pjm.com
37
©2007 PJM
Column Definitions (cont’d)
• Adj. Capacity: Calculation of capacity remaining after
Generator Outage Ticket Reduction
• Difference: Calculation of difference between eMarket
values and Adj. Capacity
Condition
Adjusted Capacity
Difference ( %)
AC = ICAP + Amb. Adj. − Re duct − Incremental
Economic
Incremental = EmergencyMax − EconomicMax
AC = ICAP + Amb. Adj. − Re duct
Emergency
Diff =
Adj.Cap. − EconomicMax
× 100
AdjustedCap
Diff =
Adj.Cap. − EmergencyMax
× 100
AdjustedCap
*Note: Ambient Air values will be the opposite sign of what is reported in
Generator Tickets
www.pjm.com
38
©2007 PJM
Red & Yellow Flags
• If Warning Tolerance violated (for overbidding), line will
appear in yellow unless violates Ack. Tolerance
• If Ack. Tolerance violated (for under or overbidding), line
will appear in red
www.pjm.com
39
©2007 PJM
Outage Popup Report
• Since unit outage may
be summed, the Unit
History Report was
provided
• To access report click
on Unit Name
• Report split into
sections by Peak
Period
• Reduction value may
differ for the same
ticket by period if MW
Revisions entered
www.pjm.com
40
©2007 PJM
Unit Translation Report
• Translates Gen Ticket
Unit Name to Gen
Checkout Unit Grouping
to PJM EMS Equipment
Long Name
• In this example, Dummy
Units 1-11 will all be
rolled up (Capacity,
Reduction and Ambient
Adjustments) under
Dummy Unit 1 in Gen
Checkout
www.pjm.com
41
©2007 PJM
Ambient Air Violation Handling
• Gen. Checkout Ambient Ticket button visible if any units in
acknowledgement violation for overbidding.
www.pjm.com
42
©2007 PJM
Ambient Ticket Form
• After button click taken to form where only units in acknowledgements
violation displayed with suggested ambient value ( Econ/ Econ Value – Adj.
Cap)
• If under emergency conditions Emergency Max value displayed otherwise
Economic
• Default Start and End Dates cover current day if Gen Checkout for Today or
next day if Gen Checkout for tomorrow
www.pjm.com
43
©2007 PJM
Setup to Create Tickets
• Dates can be changed if decided to have ticket run for much longer
• If different ambient value desired for ticket, user can either update
Emer/ Econ Value which will recalculate Ambient Value or update
Ambient Value directly
• Important: Changing Emer/ Econ Value in this form does not change
any values in eMarket
• Then user can decide which tickets to be created by checking
Create Ticket
www.pjm.com
44
©2007 PJM
Final Steps
• After user checks “Continue” they are taken to the Verification form
• Only after clicking “Continue” will the tickets be created
• A confirmation form then shows the results with ticket numbers
www.pjm.com
45
©2007 PJM
Ticket Created by Gen Checkout
www.pjm.com
46
©2007 PJM
Ambient Tickets Quick Review Process
• Any Ambient Tickets created for start within an
hour and within Auto-Approve Tolerance ticket
activated immediately
• If scheduled for start next day and within AutoApprove tolerance ticket approved immediately
• Otherwise Ticket goes to status of submitted
www.pjm.com
47
©2007 PJM
Tolerance Validation Broad Check
• Tolerance validation also checks against previously submitted
tickets
• Tolerance range is set by unit type
• Example
- Unit Cap = 120 MW
Tolerance Cap= 10%
Ticket A
Ticket B
-10MW
Ticket Status = Approved / Active
-15 MW
Ticket Status = Submitted
• Tolerance validation works also when generator ticket submitted
from MW Generator ticket form
www.pjm.com
48
©2007 PJM
Tomorrow’s Report
• Same format as
Today’s Report
• Acknowledgement
process begins
around 1630
www.pjm.com
49
©2007 PJM
Historical Report
• Same format as
Tomorrow’s except user
enters date in Report
Date filter criteria
• The user can then see
the report for any date in
the past
www.pjm.com
50
©2007 PJM
Acknowledgment Report
• This report is a log of reports which your company has
been involved
www.pjm.com
51
©2007 PJM
Filters
• Report Date: Filters on date of report
• Last 30 days: Displays only values for report within last
30 days
– Default is TRUE
• From/To Date: Filters based on report date range
• Apply Filter: Filters report based on filter criteria
• Main Menu: Returns user to Status Report Menu
www.pjm.com
52
©2007 PJM
Columns
• Report Date: Date for which report is issued
• Initiate Date: Timestamp when PJM SC requests
acknowledgements
• Complete Date: Timestamp for when PJM SC freezes
acknowledgement process
• User ID: User who acknowledged report
• Ack. Date: Timestamp for acknowledgment
www.pjm.com
53
©2007 PJM
Topics
• High Level Explanation
• Form Level Explanation
• Process Overview for Handling Example
Checkouts
• Contacts
www.pjm.com
54
©2007 PJM
Example Scenario-Gen Ticket Needed
• Test Unit 1 beyond Acknowledgement Tolerance
• Message at top shows this must be addressed before
report can be acknowledged
www.pjm.com
55
©2007 PJM
Example Scenario-Gen Ticket Needed (cont’d)
• User determines eMarket
values are correct but
outage ticket must
submitted to identify
reason unit can’t supply
energy
• User submits eDART
tickets totaling 310 MWs
- Note: These tickets are not
applied to Gen
Checkout until the outage is
approved by PJM
www.pjm.com
56
©2007 PJM
Example Scenario-Gen Ticket Needed (cont’d)
The report can now be acknowledged
www.pjm.com
57
©2007 PJM
Example Scenario-eMarket Update Needed
• Test Unit C1
beyond
Acknowledgement
Tolerance
• Message at top
shows this must be
addressed before
report can be
acknowledged
www.pjm.com
58
©2007 PJM
Example Scenario-eMarket Update Needed (cont’d)
• User determines what
eMarket values need
to be updated
• User updates Econ
Max to 96 and Emerg
Max to 100
• Report ready for
acknowledgement
www.pjm.com
59
©2007 PJM
Example Scenario – Ambient Air Adjustment Needed
• User determines
Ambient Air ticket
needs to be entered.
• User clicks Ambient
Ticket
www.pjm.com
60
©2007 PJM
Example Scenario - Ambient Air Adjustment (cont’d)
• Ambient Air Ticket submitted through Ambient Air Form
www.pjm.com
61
©2007 PJM
Example Ambient Air Adjustment (cont’d)
• The report can now be acknowledged
www.pjm.com
62
©2007 PJM
Topics
• High Level Explanation
• Form Level Explanation
• Process Overview for Handling Example
Checkouts
• Contacts
www.pjm.com
63
©2007 PJM
Further Questions?
• If there are any further questions, please feel free to get in
touch with either:
–
–
–
–
Elliot Hoffman – hoffmael@pjm.com, 610-666-8844
Ron Lavan – lavanr@pjm.com, 610-666-2212
Sanjay Patil – patils@pjm.com, 610-666-4295
Ron DeLoach – deloar@pjm.com, 610-666-4231
www.pjm.com
64
©2007 PJM