50 likes | 62 Views
This document provides a summary of R7.1 participation and general issues encountered, as well as expectations for R7.2, including objectives, exit criteria, and kickoff activities for all R7 participants.
E N D
R7.1: UI ConnectivityConclusion EDS 3 Release 7 (CRR) February 15th, 2008
Table of contents R7.1 participation – summary General issues encountered in R7.1 What to expect for R7.2
R7.1 participation summary • Resolved all market participant reported issues. • 98% of active R7.1 participants completed testing.
General issues encountered in R7.1 • 404 or 500 error page while saving/navigating in auction portfolios • Confusion regarding drag-drop of source sinks • Confusion regarding steps described in scripts • Only one new defect raised regarding typed-in date format Low severity and priority Look for messages from CRR Operator We’ll be using them to publish frequently encountered issues going forward
What to expect for R7.2: fully structured mock monthly allocation/auction Objective • ERCOT conducts mock monthly allocation (NOIEs submit ERCOT-provided nominations) • ERCOT conducts mock monthly auction (CRR AHs submit ERCOT-provided bids and offers) • CRR AHs bilaterally trade CRRs as orchestrated by ERCOT Exit Criteria • Resolved all participant-reported issues regarding any of the following: • Upload of the bid/offer portfolios provided by ERCOT (in either XML or CSV) • Download of auction results • Initiation and/or acceptance (as orchestrated by ERCOT) of bilateral trades • If eligible NOIE – upload of nomination information provided by ERCOT • If eligible NOIE – download of allocation results • If CP – entering of credit limit assigned to market provided by ERCOT R7.2 KICKOFF (all participants) NOIE, WGR and catch-up activity only All R7 participants All R7 participants