Discussion on QSE connectivity and market submissions.
Focus on the importance of submitting current operating plans, offer curves, and outage scheduler for batteries.
Requirement to complete at least one successful transaction per transaction type within an eight-week period.
Explanation of telemetry setup and checkout process in a parallel two-step procedure.
Need for all new telemetry points to be requested and loaded into ERCOT's model.
Checkout process involves testing connectivity between QSE and ERCOT by signaling telemetry points and receiving feedback.
Three scorecards are used to assess submissions: generation resource, load resource, energy storage resource.
Expectation of submission for each resource type within the QSE’s fleet.
If all types of resources are present in a QSE, submission of transactions for each type is required.
If telemetry points are set up and transactions submitted successfully, scores will be marked as green.
Two scorecards are used in handbook number two: completion of telemetry setup and the checkout process.
Progress tracked for six weeks, measuring the setup of telemetry and conducting checkouts.
Scores roll up to the QSE level if multiple sub-QSEs exist.
▶️3 - Communicate any known Issues with On-going Trial
Environmental issue identified affecting user setup; QSEs can request assistance via RTCP email.
Load resource issue for ECRS capability in COP, acknowledgment missing for AS only offer submission response.
Next software release scheduled for May 28 to address two software defects.
Continued work on resolving environment issue and progress expected in quasi production environment.
▶️4 - Provide Snapshot of Cumulative QSE Scorecards
Market submission snapshot taken from Friday afternoon; new submissions over the weekend may not be updated until the next snapshot.
Important for QSEs to check their submissions if they appear red or incorrect. Contact via email to resolve discrepancies.
Calpine raised a concern about telemetry submission; clarified that telemetry is not included in the current scorecard.
Scorecard information is posted in slides available on the meeting page; individual details are not published publicly.
General questions about the process can be asked in the meeting; specific issues should be addressed via email.
API submission issues discussed; some users facing access privilege issues despite correct certificate setup, linked to permission errors during a system merge.
Telemetry setup progress mentioned; some users have all points set, others are still in progress. Kudos to those with complete setups.
Feedback on the telemetry point data flow from ERCOT to QSEs is being tested with a subset of resources to ensure connectivity.
Lag time of about three weeks for ICCP changes to reflect in scorecards noted; scores may improve with time and periodic model updates.
Participants encouraged to check and reach out with any concerns about their scorecards or system setups.
▶️5 - Support any Technical and/or Business Questions
Discussion on submitting questions related to market trials and general inquiries with a one-day response for simple queries.
Defect identified with load resources submitting non-zero ECRS capabilities; planned fix by May 28.
Confirmation that submitting zero ECRS capability is allowed; other AS capabilities can proceed if qualified.
Clarification regarding RTC+B TF task force meeting and sample file publications led by Maggie Shanks.
NFRC modeling not part of scorecards but necessary before go-live; existing units' NFRC already modeled.
Inquiry about QSEs scheduling RTCP ICCP checkouts and the process through rtcp@ercot.com.
Market trials scorecards available weekly, potential for audience-specific scorecards explored.
COP data submission issues with ERCOT RTC+B portal; resolutions being tested and expected by May 28.
Requests for publishing scorecards in Excel format registered; concerns mentioned about sensitive data.
Meeting noted to reconvene Tuesday after Memorial Day; next step actions for ERCOT outlined.
