EDS SCED MP Handbook Draft for Workshop v01

advertisement
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
Texas Nodal:
EDS SCED Testing
Market Participant Handbook – DRAFT
This document and the content have been
drafted for discussion at the EDS SCED
Market Participant Workshop. Based on
the Workshop, ongoing planning meetings,
and Nodal Project deliveries the details
will be further refined.
Version 0.1
Wednesday, May 23, 2007
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
1
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
Revision History
Document Revisions
Date
Version
Description
Author(s)
5/23
0.1
Draft document created for EDS 3 SCED Planning
Workshop w/ Market Participants. This version is a working
draft for planning discussion with Participants.
IRT
TBD
0.2
Update to Document based on EDS 3 SCED Planning
Workshop and IRT continued planning.
IRT
(Target 5/31)
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
2
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
Table of Contents
1
2
3
INTRODUCTION ........................................................................................................................ 5
1.1
Handbook Overview ......................................................................................................... 6
1.2
Handbook Structure .......................................................................................................... 8
EDS COMMUNICATIONS ......................................................................................................... 8
2.1
Online Readiness Center .................................................................................................. 8
2.2
EDS Planning Workshops ................................................................................................ 8
2.3
EDS Kickoff Session ......................................................................................................... 9
2.4
EDS Weekly Conference Calls ......................................................................................... 9
2.5
Weekly Status Bulletin ...................................................................................................... 9
2.6
Issue Tracking Process .................................................................................................... 9
2.7
Entry / Exit Criteria .......................................................................................................... 10
EDS 3 RELEASE 5 - TRIAL OPERATION OF SCED ............................................................. 10
3.1
3.2
3.3
3.4
3.5
Version: 0.1
Release Overview ........................................................................................................... 10
3.1.1
Early Deliveries ............................................................................................... 10
3.1.2
Supporting Documents .................................................................................... 11
3.1.3
Nodal Sandbox ................................................................................................ 11
Phase 1 - Input Data Submittal and Validation ............................................................... 12
3.2.1
Phase Overview .............................................................................................. 12
3.2.2
EDS Activities .................................................................................................. 15
3.2.3
Market Participant Involvement ....................................................................... 17
3.2.4
Market Participant Systems Readiness .......................................................... 17
Phase 2 - SCED Execution (Simulated ICCP) ............................................................... 18
3.3.1
Phase Overview .............................................................................................. 18
3.3.2
EDS Activities .................................................................................................. 20
3.3.3
Market Participant Involvement ....................................................................... 20
3.3.4
Market Participant Systems Readiness .......................................................... 20
Phase 3 - Integrated SCED Execution (RT ICCP) ......................................................... 21
3.4.1
Phase Overview .............................................................................................. 21
3.4.2
EDS Activities .................................................................................................. 23
3.4.3
Market Participant Involvement ....................................................................... 23
3.4.4
Market Participant Systems Readiness .......................................................... 23
Phase 4 - Six Month LMP Posting (RT ICCP) ................................................................ 24
3.5.1
EDS Activities .................................................................................................. 24
3.5.2
Market Participant Involvement ....................................................................... 25
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
3
DRAFT – W orking Document
3.5.3
Version: 0.1
M a rket Pa rt ic ipa nt H a nd bo o k
Market Participant Systems Readiness .......................................................... 25
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
4
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
1 Introduction
The ERCOT Nodal Transition Plan, approved by the Technical Advisory Committee (TAC),
organizes transition activities into four tracks, which required participation from both ERCOT and
market participants. The Texas Nodal Program defined four Early Delivery Systems (EDS)
sequences to meet the requirements of the Systems Testing and Nodal Market Implementation
track of the Transition Plan. These sequences were further refined based on the Nodal project
delivery schedules to group Nodal functionality and features into nine incremental software releases
that will be used to meet the requirements outlined in the Nodal Transition Plan.
The EDS sequences and releases are outlined below:
EDS 1
 Release 1 – Alarm Processing
 Release 2 – Point-to-Point Checkout
EDS 2
 Release 3 – Trial Operation of State Estimator & Network Security Analysis
 Release 4 – Trial Operation of NMMS (Network Model Validation)
EDS 3
 Release 5 – Trial Operation of SCED, 6 month LMP posting
 Release 6 – Trial Operation of LFC, ACE
 Release 7 – Trial Operation of CRR, sample Settlement Statements
EDS 4
 Release 8 – Trial Operation of RT Settlements (no Shadow Settlements)
 Release 9 – Trial Operation of DAM, RUC, SASM, Full Settlements, EDW Extracts
 TXMACS 1.0 – Full Nodal Functionality & 168 hour testing
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
5
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
The Nodal program has adopted an incremental approach for releasing functionality into the EDS
environment to maximize the overall benefit of EDS by providing system functionality for Market
Participants to begin testing as early as possible. The objective of these early deliveries is to provide
MPs with sufficient tools to enable development of their systems. The EDS environment will be updated
incrementally as soon as a set of Nodal functionality has been tested internally by ERCOT. Once the integrated set
of system functionality has completed the internal ERCOT quality control testing, the EDS
environment will be updated for formal milestone testing activities. This incremental approach is
diagramed below:
1.1 Handbook Overview
The Market Participant Handbook has been created to provide Market Participants a detailed
testing guide for participation in the Early Delivery System (EDS) activities. The Handbook is
one of the guiding documents to help MPs understand how and when to engage in EDS
activities.
The testing activities described in this document will be guided by the Nodal Transition Plan and
the Nodal delivery schedule, however, the detailed testing schedule will be completed by
working collaboratively with the ERCOT subject matter experts and Market Participant
representatives.
The Early Delivery Systems are intended to:

Provide Market Participants with the tools to complete development and testing of
updated Nodal systems in as realistic environment as possible.
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
6
DRAFT – W orking Document




M a rket Pa rt ic ipa nt H a nd bo o k
Validate Nodal functionality and timelines including Day-Ahead, Adjustment Period and
Real-Time activities for ERCOT, Transmission Service Providers (TSPs) and Market
Participants (MPs).
Build stakeholder confidence that Nodal design and systems adhere to Nodal Protocols
and Nodal Transition Plan requirements.
Generate Locational Marginal Prices (LMPs) for distribution to ERCOT Market
Participants for at least six months prior to the Nodal Markets going live.
Confirm through a series of structured and unstructured testing that
"stable and accurate operation of the SCADA, Network Security Analysis,
Transmission Constraint Management, SCED, LFC, DAM, RUC, and real time
settlement system can be declared"
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
7
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
1.2 Handbook Structure
To ensure that both ERCOT and Market Participants are ready for Early Delivery System
activities it is critical that all participants have a common understanding of EDS activities, start
dates, and participation expectations. This document is intended to provide the following for
each EDS phase:
Needs to be refined
 Phase Overview
o Description, Objectives
o Functional Scope: Available Interfaces, Validation, Functionality, Data
o Schedule
 EDS Testing Period
o Activity List
o Structure
o Scripts
o Support
 MP Involvement
o Target Roles
o Participation Expectations
o Preparation Activities (Data, Digital Certs, Workshop, New Data, …)
o MP System Readiness
o Training
2 EDS Communications
2.1 Online Readiness Center
Online readiness support for the ERCOT and market participant transition to the nodal market as
well as supporting EDS documentation can be found in the Nodal Transition Readiness Center
on the ERCOT Nodal Website: http://nodal.ercot.com/readiness/index.html
2.2 EDS Planning Workshops
To ensure that both ERCOT and the Market Participants maximize the benefits of the EDS,
starting in May the EDS team will be scheduling monthly planning workshops and ongoing
conference calls to complete the details required for EDS execution. The workshops will focus
on: test preparations; testing scenarios; the detailed test procedures and schedule of the test
sequences; test sequence planning at the QSE and Resource level; and a substantive list of
specific entry and exit criteria for each EDS Release; and the final exit criteria that signifies the
completion of all Transition Plan activities that support a declaration of readiness. The EDS
planning workshops will provide input for the test plans and test scenarios to support the day-today testing activities.
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
8
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
2.3 EDS Kickoff Session
Need to refine
Channel: Meeting (Austin),
WebExAudience: NTPM, EDSC
Timing: 3 wks. before EDS start
Materials: Agenda, EDS Handbook
Notes: Cover the following:
• Pre-EDS preparation activities that should be nearing completion
• Review enrollment process for preliminary testing
• Review how MPs will be able to access systems
• Q&AAfter meeting, post meeting notes, Q&A, presentation on web
2.4 EDS Weekly Conference Calls
Need to refine
Channel: Conference Call
Audience: Participating MPs
Timing: TBDMaterials: TBD
2.5 Weekly Status Bulletin
Need to refine:
Channel: Market Notice, web
Audience: EDSC, NTPM
Timing: End of test week
Materials: Weekly status bulletin
Notes: Covers weekly status during formal testing. Interim bulletins may be sent, as needed.
2.6 Issue Tracking Process
Prior to the delivery of market systems and associated business functionality to the EDS
environment each application will be run through a series of testing phases to find and resolve as
many of the system defects as possible. These phases include a round of testing at the vendor site
(Pre-FAT), a round of onsite testing for Acceptance (FAT), and a round of Regression and
Integration Testing (I-Test). Internally defects will be logged and tracked for resolution. Given
the accelerated release of many of the system to allow Market Participants an early opportunity
to resolve issues with their own systems that will interface with the ERCOT market tools, it is
anticipated that there will be items discovered as the quality of the systems improves during
Market Participant testing that need to be resolved. These items should be reported to ERCOT
using the following Market Participant Issue Reporting Form (sample in appendix). All items
will be investigated by ERCOT testing personnel and logged into the defect tracking system.
Defect statuses will be discussed at the end of the week wrap-up call as well as posted on the
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
9
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
Nodal Readiness Center website which will be updated weekly (process overview in appendixTBD)
2.7 Entry / Exit Criteria
To begin and end each of the EDS 3 Releases, a defined set of entrance and exit criteria must be
defined to ensure readiness. Specific criteria will need to be defined for both ERCOT and the
Market Participants to help ensure that the test phase will be productive. During the market trials
planning phase, the team will be working with Market Participants to finalize a set of measurable
criteria.
3 EDS 3 Release 5 - Trial Operation of SCED
3.1 Release Overview
SCED will be the first business function to be released to the EDS environment. The release
procedure will follow the ERCOT release mechanism described earlier in the document. Early
system deliveries will initially provide QSEs the opportunity to submit, modify, cancel, and
retrieve input data for SCED execution. During the release the EDS environment will be further
upgraded to provide the functionality for SCED execution utilizing ERCOT and QSE test offers
and to begin distribution of Base Points and LMPs.
3.1.1 Early Deliveries
The Trial Operations of SCED will be executed in several phases, incrementally adding
interfaces and functionality until a fully integrated and tested product is released to the EDS
environment The Early Delivery System approach will provide ERCOT and Market Participants
the ability to begin Market testing as early as practical.
The following phases and objectives have been defined:
Phase 1 - Input Data Submittal and Validation
 Provide a SCED environment for Market Participant EDS Activities
 Verify QSEs ability to utilize Web Service interfaces to submit, modify, cancel, and
retrieve three part offers, COP, and output schedules
 Verify QSEs understanding of SCED input validation rules
 Utilize both the User Interface and Web Services interfaces for SCED inputs
Phase 2 - Simulated SCED Execution
 Utilize new and updated MP Registration data
 Utilize SCED Market Participant Offer Methodology (based on defined scenarios)
 Simulate SCED RT Inputs based on defined scenarios
 Execute SCED and distribute Base Points and LMPs for MP evaluation
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
10
DRAFT – W orking Document

M a rket Pa rt ic ipa nt H a nd bo o k
Review SCED produced Base Points and LMPs for reasonability
Phase 3 - Integrated SCED Execution (RT ICCP)
 Utilize new ICCP Data
 Utilize SCED Market Participant Offer Methodology (align with Zonal operations)
 Verify SCED inputs from real-time operations
 Verify QSE ability to receive correct Resource Base Points and LMPs via ICCP
 Review SCED produced Base Points and LMPs for reasonability
Phase 4 - Six Month LMP Posting (RT ICCP)
 LMP reasonability attained
 Publish LMPs and other data available as required in the Nodal Protocols
 Utilize SCED Market Participant Offer Methodology (align with Zonal operations)
 Begin six months of SCED execution and LMP posting period as required by the Nodal
Transition Plan
3.1.2 Supporting Documents
Reference: Nodal Website
EDS Detailed Plan
MMS SCED Requirements
MMS DA Requirements
Market Participant Submission Items
Machine to Machine Interfaces
3.1.3 Nodal Sandbox
The Nodal Sandbox is a Pre-Early Delivery Systems (EDS) Environment for the testing of interfaces
between Market Participants and ERCOT. This environment provides the tools for QSEs to interface
with the Web Services architecture prior to delivery of the core EDS systems. This environment is
not intended for application functionality, stress, stability, or full production verification. All of the
services on the Sandbox will utilize he same XML structures and functions that will be deployed to
the EDS but have loopback functionality to provide correct XML responses but do not interact with
other applications. Target delivery timelines are outlined below.
ERCOT highly recommends Market Participants utilize the Nodal Sandbox, prior to EDS testing, to
validate connectivity, understanding of specific web services, and technical architecture.
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
11
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
3.2 Phase 1 - Input Data Submittal and Validation
3.2.1 Phase Overview
EDS Environment
During the Input Data Submittal and Validation phase, the EDS environment will be upgraded to
include a stand alone SCED environment and the External Web Service infrastructure to support
data submittal into the SCED system for validation. Market Participants planning on utilizing the
External Web Services for communicating with Nodal Systems and who have progressed past the
capabilities of the Nodal Sandbox will be able to request access to the EDS environment and signup
for support workshops to test interconnectivity with SCED. QSEs who would like to test the MP
User Interface will be able to sign up for testing workshops. The diagram below highlights the
components that will be tested during this phase.
Phase 1: SCED Input Data Submission and Validation
* Three-Part Offer
(Energy Offer Curve)
Market
Participant
Submission
Tools
* Inc/Dec Offers
User
Interface
Validation
* COP
Web
Services
MIS / EDW
MMS - SCED
* Base Points
* LMPs
* Output Schedules
`
STUB DATA (Reg)
Other
EMS
* Zonal ICCP Data Points
* Nodal ICCP Data Points
EMS
* State Estimator Solution
* SCADA - Telemetry
* Transmission Constraint
Manager
* Load Frequency Control
* Resource Limit Calculator
REG
* Resource Parameters
* Resource – QSE mapping
NMMS
S&B
* Competitive Constraint Test results
* Settlement System Info (V-OM and
HR)
* NMMS Hub and Load Zone
definitions
* Note: Only the colored components will be tested during this phase.
EDS Testing Schedule
The Input Data Submission and Validation phase is targeted to take place during August and
September 2007. During this two month period the EDS environment will be available for QSEs
who have moved past the loop back capabilities of the Nodal Sandbox and want to begin testing
backend validation capabilities. The EDS team will provide a schedule of testing windows (1-2
weeks) and testing support workshops (2 hours each) that QSEs will be able to sign up for on a first
come first serve basis.
The diagram below shows a typical EDS testing week:
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
12
DRAFT – W orking Document
Monday
Tuesday
Wednesday
M a rket Pa rt ic ipa nt H a nd bo o k
Thursday
Friday
Monday Conf Call
Morning Workshop
Morning Workshop
Morning Workshop
Friday Conf Call
Channel: Conf Call
Channel: Conf Call
Audience: Single QSE and
team
Subj: Support EDS
Activities
Channel: Conf Call
Audience: Single QSE and
team
Subj: Support EDS
Activities
Channel: Conf Call
Audience: Single QSE and
team
Subj: Support EDS
Activities
Channel: Conf Call
Afternoon Workshop
Afternoon Workshop
Afternoon Workshop
Channel: Conf Call
Audience: Single QSE and
team
Subj: Support EDS
Activities
Channel: Conf Call
Audience: Single QSE and
team
Subj: Support EDS
Activities
Channel: Conf Call
Audience: Single QSE and
team
Subj: Support EDS
Activities
Audience: All QSEs
Subj: Overview of weekly
activities
Audience: All QSEs
Subj: Review EDS progress
& issues

Monday Conference Call - Used to communicate with all EDS participants on
 EDS activities planned for the week
 Updates to online support documents & tools
 Resolved issues or environment updates

Mid Week Workshops - The Nodal support team will have two workshop slots for each day
Tue, Wed, Thus. Individual QSEs will have the opportunity to signup for support from
ERCOT Subject Matter Experts to walk through EDS testing
activities or work on
specific QSE issues. A detailed calendar of EDS workshops
and testing activities will
be available on the Nodal Readiness Center?

Friday Conference Call - Used to communicate with all EDS participants on
 EDS activities accomplished during the week
 Updates to online support documents & tools
 Identified software or environment updates
During the workshops participants will become familiar with Market Participant Input Data
Interfaces (User Interface, Web Services)
 Three-Part Offers (Energy Curve component), including FIP & FOP)
 Current Operating Plan (COP)
 Output Schedule
 Incremental and Decremental Offer Curves (DSR)
External Web Services
During this testing phase, the priority 1 External Web Services outlined below will be incrementally
deployed into the EDS environment as the back-end integration and internal testing is complete. All
of the priority 1 Web Services will be available as stubs in the Nodal Sandbox environment prior to
EDS.
Priority 1 - External Web Services Availability (SCED)
Submission Type
Imp
Sandbox
Group
Target
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
EDS 3
Target
13
DRAFT – W orking Document
Submission Type
M a rket Pa rt ic ipa nt H a nd bo o k
Imp
Group
Sandbox
Target
EDS 3
Target
1
1
Jul 07
Jul 07
Aug 07*
Aug 07
1
July 07
Aug 07
1
July 07
Aug 07
1
1
1
1
July 07
July 07
July 07
July 07
Aug 07*
Aug 07
Aug 07
Aug 07
Offers
Three-Part Supply Offer (Energy)
Inc/Dec Energy Offer
Schedules
Output Schedule (incl. DSR)
Other Market Interfaces
COP
Other Web Service Components
Bid Set Acceptance
Bid Set Error
Get MRID
System Status
* Three Part Offer and Bid Set Acceptance may be released late July.
Note: Some of the required fields in the Web Services interface specifications may not apply to the
early SCED testing, however, stub data will need to be used to ensure that the Web Services can be
successfully submitted. These details will be worked out in the planning workshops and scripts.
Details about the external web services are provided in Machine-to-Machine (External) Interface Specification
v0.94
Market Management System (MMS) - SCED
Submission
Window opens
for OD HE 01-24
Adjustment
Period QSE Input
Data Validation
Offer Creation
and Validation
SCED Execution
SCED Outputs
The initial EDS environment will provide Market Participants the capability to submit input data
prior to the Operating Day and during the Adjustment Period. The tables below describe the
capabilities and requirement coverage of the initial MMS system to support input data validation.
The requirements documentation and specific details can be found on the Nodal Website.
Pre-DAM Activities
Req
1
PD2
Req Specification Name
QSE Submittal of COP, Bids, Offers, and
Trades
General Validation Process of QSE Input
2
PD3
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
Description
Partial Only for COP, Output
Schedules, Three-part
offers and Inc-Dec Offers
Partial No Credit Limit
validation; no Phase 2
validation
14
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
Validation of DAM Submissions and Other Trades
Req
3
VA10
4
5
VA13
VA14
Req Specification Name
Validation of Three-Part Supply Offer - StartUp and Minimum-Energy Offer and Energy
Offer Curve
Notice of Validation Rules
Validation of COP
Description
Partial Energy Curves Only
Partial
Adjustment Period QSE Input Data Validation
Req
Req Specification Name
6
FR1
Adjustment Period QSE Data Submission
7
FR2
8
FR78
DSR Output Schedule Submission
Energy Offer Curve Submission and
Modification
Energy Offer Curve Withdrawal
Energy Offer Curve Validation
Percentage of FIP and Percentage of FOP
Mitigated Offer Cap and Floor Calculation
Process
Energy Offer Curve and Output Schedule for
RMR Resource
Output Schedule Validation
Output Schedule Validation at Submission
Output Schedule Validation at Operating
Period
Output Schedule Submission by Telemetry at
Operating Period
Output Schedule Notification Two Hour
Ahead
Output Schedule Validation at the End of
Adjustment Period
Additional Incremental/Decremental Energy
Offer Validation
9 FR79
10 FR4
11 FR4-1
12 FR5
13 FR6
14 FR7
15 FR8
16 FR9
17 FR9-1
18 FR10
19 FR10-1
20 FR12
Description
Partial COP; Energy Offer
Curves; Output Schedule
(non DSR); Inc/Dec
Offers (DSR)
Full Partial Partial
Full
Full
Partial
Partial
Partial
Full
Full
Partial
Partial
Full
Full
3.2.2 EDS Activities
The early testing of SCED input data validation will provide the opportunity to test a subset of the
system functionality and validation components. Specific Market Participant submission testing
activities will be defined during the EDS planning workshops and included in this Handbook.
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
15
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
Below is an initial list of EDS submission testing activities:
MMS User Interface / External Web Services

Current Operating Plan - COP Display / COP
o Submit, Update, Query
o Receive valid Transaction Identifier / mRID
o Rejection of COP due to out of HSL/LSL range - (HSL/LSL submitted is out of the
high/low reasonability limit range)
o
o
Validate overwriting behavior of COP (New Submission, Update)
Review results

Three-Part Energy Offer Display / Three Part Supply Offer
o Submit, Update, Query, Cancel
o Cancel w/ valid Output Schedule
o Submit w/ specific Expiration Date/Time
o Validate overwriting behavior of Energy Offer Curve
Reject if FIP% and FOP% incorrect (resource type dependent)
o Receive valid Transaction Identifier / mRID
Rejection due to invalid Energy Offer Curve (must be monotonically nondecreasing and all prices within applicable caps/floors)
o Rejection if resource type is RMR or Load Resource
o Review all results

Output Schedule Display / Output Schedule
o Submit, Update, Query, Cancel Output Schedules (DSR/Non-DSR)
o Rejection due to valid Energy Offer Curve
o Receive valid Transaction Identifier / mRID
o Rejection due to no COP
o Rejection when MW level is not between LSL & HSL of COP
o Rejection due to violation of SCED Up/Down ramp rates
o Review results

Incremental, Decremental Offer Curve Display / Inc/Dec Energy Offer
o Submit, Update, Query, Cancel (DSR)
o Receive Transaction identifier / mRID
o Rejection if first pq quantity is not 0 MW
o Review results

QSE Notifications / Notification
o Notification for SCED related items only
Other Web Service Components

Acceptance / Error Notification
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
16
DRAFT – W orking Document
o
o
M a rket Pa rt ic ipa nt H a nd bo o k
Receive Bid Set Acceptance
Receive Bid Set Error
Testing Structure
Test Scripts
To enable EDS testing, RECOT shall provide MPs with test scripts that detail the inputs, system
notifications and outputs from SCED. These test scripts shall distinguish the activities that need to
be performed by both ERCOT and MPs
3.2.3 Market Participant Involvement
The activities and functionality being tested in EDS 3 are relevant to the following Market
Participant groups:
QSEs with resources: SCED Input Data Submissions
ERCOT: offer receipt, external interfaces and integration, data processing and
validations
The EDS SCED Input Data Submission and Validation tools are available for every Market
Participant to begin validation and testing of internal systems to ensure Go-Live readiness in
December 2008. Participation is highly recommended for this phase.
3.2.4 Market Participant Systems Readiness
Market Participants planning on utilizing Web Services in production should have an Early Delivery
System or tools to support data creation and submission during this phase.
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
17
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
3.3 Phase 2 - SCED Execution (Simulated ICCP)
3.3.1 Phase Overview
EDS Environment
During the initial SCED execution phase, the EDS environment will be upgraded to provide the data
and tools necessary to begin execution of SCED. At this point all QSEs with resources are expected
to be participating to ensure that the SCED output is beneficial to all Market Participants.
Phase 2: SCED Execution (Simulated ICCP)
* Three-Part Offer
(Energy Offer Curve)
Market
Participant
Submission
Tools
* Inc/Dec Offers
User
Interface
Validation
* COP
Web
Services
MIS / EDW
MMS - SCED
* Base Points
* LMPs
* Output Schedules
`
STUB DATA (EMS)
STUB DATA (Other)
Other
EMS
* Zonal ICCP Data Points
* Nodal ICCP Data Points
EMS
* State Estimator Solution
* SCADA - Telemetry
* Transmission Constraint
Manager
* Load Frequency Control
* Resource Limit Calculator
REG
* Resource Parameters
* Resource – QSE mapping
NMMS
S&B
* Competitive Constraint Test results
* Settlement System Info (V-OM and
HR)
* NMMS Hub and Load Zone
definitions
* Note: Only the colored components will be tested during this phase.
EDS Testing Schedule
The SCED Execution (Simulated ICCP) phase is targeted to take place during October and
November 2007.
The diagram below shows a sample EDS calendar:
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
18
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
October-07
Monday
Tuesday
1
Weekly activities
breifing call
9-11 MPI Workshop
2-4 MPI Workshop
Final Sessions for last
QSEs
Final Sessions for last
QSEs
Final Sessions for last
QSEs
9
13/14
11
12
9-12 SCED Testing
End of week wrap-up
1:30-4 SCED Testing call
SCED Integrated
SCED Integrated
SCED Integrated
9-12 SCED Testing
1:30-4 SCED Testing
9-12 SCED Testing
1:30-4 SCED Testing
18
19
9-12 SCED Testing
End of week wrap-up
1:30-4 SCED Testing call
SCED Integrated
SCED Integrated
SCED Integrated
17
9-12 SCED Testing
1:30-4 SCED Testing
23
9-12 SCED Testing
1:30-4 SCED Testing
25
26
9-12 SCED Testing
End of week wrap-up
1:30-4 SCED Testing call
SCED Integrated
SCED Integrated
SCED Integrated
29
Weekly activities
breifing call
6/7
9-12 SCED Testing
1:30-4 SCED Testing
16
24
30
31
1
9-12 SCED Testing
1:30-4 SCED Testing
9-12 SCED Testing
1:30-4 SCED Testing
9-12 SCED Testing
1:30-4 SCED Testing
SCED Integrated
SCED Integrated
SCED Integrated
Sat/Sun
5
End of week wrap-up
call
9-12 SCED Testing
1:30-4 SCED Testing
22
Weekly activities
breifing call
10
Friday
4
9-11 MPI Workshop
2-4 MPI Workshop
15
Weekly activities
breifing call
Thursday
3
9-11 MPI Workshop
2-4 MPI Workshop
8
Weekly activities
breifing call
Wednesday
2
20/21
27/28
2
End of week wrap-up
call
External Web Services
During this testing phase, the priority 2 and 3 External Web Services outlined below will be
incrementally deployed into the EDS to allow Participants to begin querying SCED output data.
Priority 2 - External Web Services Availability (SCED)
Submission Type
Imp
Sandbox
Group
Target
EDS 3
Target
Outputs
Real-Time System Load
Market LMPs and SPPs
Mitigated Curves
2
2
2
Aug 07
Aug 07
Aug 07
Priority 3 - External Web Services Availability (SCED)
Submission Type
Imp
Sandbox
Group
Target
Oct 07
Oct 07
Oct 07
EDS 3
Target
Outputs
Unit Availability
Version: 0.1
3
Sep 07
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
Nov 07
19
DRAFT – W orking Document
Submission Type
Proxy Curves
M a rket Pa rt ic ipa nt H a nd bo o k
Imp
Group
3
Sandbox
Target
Sep 07
EDS 3
Target
Nov 07
3
Sep 07
Nov 07
Notifications
Notices and Alerts
Market Management System (MMS) - SCED
Submission
Window opens
for OD HE 01-24
Adjustment
Period QSE Input
Data Validation
Offer Creation
and Validation
SCED Execution
SCED Outputs
[ NEED TO ADD IN MMS REQUIREMENTS TABLE ]
3.3.2 EDS Activities
SCED Stand-Alone Execution
o
EMS Simulated Data Inputs
o
SCED Execution, Base Point Creation, LMP Creation
o
Base Point & LMP Report Distribution (Temporary Solution)
o
SCED External API Outputs (TBD)
3.3.3 Market Participant Involvement
The activities and functionality being tested in EDS 3 are relevant to the following Market
Participant groups:
QSEs with resources: SCED Input Data Submissions
ERCOT: offer receipt, external interfaces and integration, data processing and
3.3.4 Market Participant Systems Readiness
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
20
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
3.4 Phase 3 - Integrated SCED Execution (RT ICCP)
3.4.1 Phase Overview
EDS Environment
Phase 3: SCED Execution (RT ICCP)
* Three-Part Offer
(Energy Offer Curve)
Market
Participant
Submission
Tools
* Inc/Dec Offers
User
Interface
Validation
* COP
Web
Services
MIS / EDW
MMS - SCED
* Base Points
* LMPs
* Output Schedules
`
STUB DATA (Other)
Other
EMS
* Zonal ICCP Data Points
* Nodal ICCP Data Points
EMS
* State Estimator Solution
* SCADA - Telemetry
* Transmission Constraint
Manager
* Load Frequency Control
* Resource Limit Calculator
REG
* Resource Parameters
* Resource – QSE mapping
NMMS
S&B
* Competitive Constraint Test results
* Settlement System Info (V-OM and
HR)
* NMMS Hub and Load Zone
definitions
* Note: Only the colored components will be tested during this phase.
EDS Testing Schedule
The SCED Execution (RT ICCP) phase is targeted to take place during November and December
2007.
The diagram below shows a sample EDS calendar:
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
21
DRAFT – W orking Document
Monday
Tuesday
M a rket Pa rt ic ipa nt H a nd bo o k
Wednesday
Thursday
Friday
Sat/Sun
December-07
1/2
3
Weekly activities
breifing call
4
5
6
7
9-12 SCED Testing
9-12 SCED Testing
9-12 SCED Testing
End of week wrap1:30-4 SCED Testing 1:30-4 SCED Testing 1:30-4 SCED Testing up call
SCED Integrated
10
Weekly activities
breifing call
SCED Integrated
11
Weekly activities
breifing call
SCED Integrated
13
14
9-12 SCED Testing
9-12 SCED Testing
9-12 SCED Testing
End of week wrap1:30-4 SCED Testing 1:30-4 SCED Testing 1:30-4 SCED Testing up call
SCED Integrated
17
12
SCED Integrated
18
24
19
SCED Integrated
25
15/16
SCED Integrated
20
21
9-12 SCED Testing
9-12 SCED Testing
9-12 SCED Testing
End of week wrap1:30-4 SCED Testing 1:30-4 SCED Testing 1:30-4 SCED Testing up call
SCED Integrated
8/9
22/23
SCED Integrated
26
27
28
CHRISTMAS
CHRISTMAS
CHRISTMAS
CHRISTMAS
CHRISTMAS
NO TESTING
NO TESTING
NO TESTING
NO TESTING
NO TESTING
29/30
31
NEW YEARS
NO TESTING
External Web Services
During this testing phase, the priority 4, 5, and 6 External Web Services outlined below will be
incrementally deployed into the EDS environment as the back-end integration and internal testing is
complete.
Priority 4 - External Web Services Availability (SCED)
Submission Type
Imp
Sandbox
Group
Target
EDS 3
Target
Outputs
Load Distribution Factors
4
Oct 07
Priority 5,6 - External Web Services Availability (SCED)
Submission Type
Imp
Sandbox
Group
Target
Dec 07
EDS 3
Target
Outputs
Binding Constraints
Active Contingencies in SCED
Competitive Constraints
Shift Factors
Dynamic Ratings
5
5
5
5
6
Nov 07
Nov 07
Nov 07
Nov 07
Dec 07
Jan 08
Jan 08
Jan 08
Jan 08
Jan 08
Market Management System (MMS) - SCED
Submission
Window opens
V efor
r sOD
i o nHE
: 001-24
.1
Adjustment
Period QSE Input
Data Validation
Offer Creation
and Validation
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
SCED Execution
SCED Outputs
22
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
[ NEED TO ADD IN REQUIREMENTS TABLES ]
3.4.2 EDS Activities
SCED Integrated System
o
Utilize SCED Market Participant Offer Methodology
o
EMS Real Time ICCP Data Inputs (Required for SCED)
o
Execution of SCED using Real-Time ICCP data
o
Distribution of SCED outputs through ICCP
o
SCED External API Outputs
o
SCED MIS Reporting
3.4.3 Market Participant Involvement
3.4.4 Market Participant Systems Readiness
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
23
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
3.5 Phase 4 - Six Month LMP Posting (RT ICCP)
3.5.1 Phase Overview
EDS Environment
Phase 4: Six Months SCED Execution & LMP Publishing
* Three-Part Offer
(Energy Offer Curve)
Validation
User
Interface
Market
Participant
Submission
Tools
* COP
Web
Services
* Inc/Dec Offers
MIS / EDW
MMS - SCED
* Base Points
* LMPs
* Output Schedules
`
EMS
* Zonal ICCP Data Points
* Nodal ICCP Data Points
Other
Siebel
EMS
NMMS
S&B
(MP REG)
* State Estimator Solution
* SCADA - Telemetry
* Transmission Constraint
Manager
* Load Frequency Control
* Resource Limit Calculator
* Resource Parameters
* Resource – QSE mapping
* Competitive Constraint Test results
* Settlement System Info (V-OM and
HR)
* NMMS Hub and Load Zone
definitions
* Note: Only the colored components will be tested during this phase
EDS Testing Schedule
Monday
Tuesday
January-08
Wednesday
1
Thursday
Friday
Sat/Sun
2
3
4
5/6
9
10
11
QSE Offer Submission End of week wrapSCED Operation
up call
LMP Publishing
12/13
14
15
16
17
18
QSE Offer Submission QSE Offer Submission
QSE Offer Submission End of week wrapSCED Operation
SCED Operation
SCED Operation
up call
LMP Publishing
LMP Publishing
LMP Publishing
19/20
21
22
23
24
25
QSE Offer Submission QSE Offer Submission
QSE Offer Submission End of week wrapSCED Operation
SCED Operation
SCED Operation
up call
LMP Publishing
LMP Publishing
LMP Publishing
26/27
28
29
30
31
QSE Offer Submission QSE Offer Submission
QSE Offer Submission End of week wrapSCED Operation
SCED Operation
SCED Operation
up call
LMP Publishing
LMP Publishing
LMP Publishing
NEW YEARS DAY
NO TESTING
7
Weekly activities
breifing call
Weekly activities
breifing call
Weekly activities
breifing call
Weekly activities
breifing call
Version: 0.1
8
QSE Offer Submission
SCED Operation
LMP Publishing
QSE Offer Submission
SCED Operation
LMP Publishing
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
24
DRAFT – W orking Document
M a rket Pa rt ic ipa nt H a nd bo o k
External Web Services
3.5.2 EDS Activities
SCED Six Months of LMP Posting
o
Utilize SCED Market Participant Offer Methodology (initial period TBD)
o
Allow Market Participants to submit any Offers (transition date TBD)
3.5.3 Market Participant Involvement
The activities and functionality being tested in EDS 3 are relevant to the following Market
Participant groups:
QSEs with resources:
ERCOT:
3.5.4 Market Participant Systems Readiness
Version: 0.1
L a s t Mo d i f i e d : 2 / 1 5 / 2 0 1 6
25
Download