Stakeholder center

Comments on EDAM BRS v1.4 Comments

Extended day-ahead market

Print
Comment period
Mar 14, 08:00 am - Apr 18, 05:00 pm
Submitting organizations
View by:

PacifiCorp
Submitted 04/11/2025, 04:01 pm

Contact

Rohan Chatterjee (rohan.chatterjee@pacificorp.com)

1. Please provide the version of the EDAM BRS your comments apply to
Please specify the version of the BRS your comments apply to

V1.4

2. Please provide any questions or comments your organization may have regarding section 5 of the EDAM BRS.
When providing input in the text box below, please specify the BRQ(s) to which your comment or question refers. Please note that there are currently two companion initiatives for EDAM that will be implemented at the same time: 1) EDAM Implementation, which addresses the entire market framework for the EDAM footprint, and 2) EDAM ISO BAA Participations Rules, which applies specific operational and settlement participation rules to the EDAM market for the ISO BAA (‘CISO’). This document pertains to the former.
3. Please provide any questions or comments your organization may have regarding the remainder of the EDAM BRS
When providing input in the text box below, please specify the section your comment or question refers to.
4. Please provide any additional questions or comments you may have.
When providing input, limit your questions and comments to the EDAM BRS and the EDAM Initiative.

 

ID#

 

Business Feature

Requirement Type

Potential Application(s) Impacted

 

Comment

EDAM- TSR- BRQ- 11141a

 

Step 2a: Support TCSC submission of TSR attributes for transient DA TSR Type 1 with CRN rights

Core

SIBR
  • EDAM- TSR- BRQ- 11141a requires TCSC submittal of TSR attributes for DA TSR Type 1 by 9:00, and EDAM- TSR- BRQ- 11144e requires TCSC submission of TSR attributes by 10:00am. Please explain which Bucket of transmission each of these requirements speak to?

 

  • We request clarification on what when might an EESC define a Transient Type 1 TSR?

 

Transient TSR  - “A TSR pair that is not registered in the Master File (MF), rather it is defined in the Scheduling Infrastructure and Business Rules (SIBR) system for a specific Trading Day.”

 

 

EDAM- TSR- BRQ- 11144b

Step 4: Dynamic Matching for Transient Type 2 TSRs at 9 am

 

Core

SIBR

EDAM- TSR- BRQ- 02051d

 

Core

MF
  • Request clarification on how MAXIMUM_CAPACITY is being calculated for Type 1-4 TSRs?

 

  • Request confirmation that MAXIMUM_CAPACITY for Types 1-4 TSRs are being calculated by EESC?

 

EDAM- TSR- BRQ- 11144f

Support TCSC submission of TSR attributes for Registered Type 2

 

Allow TCSC to submit TSR Type 2 self-schedules for registered TSR Type 2 before 9:00 am

Core

SIBR

Please clarify which transmission bucket pathway B2[P1/P2/P3] is associated with “Type 2 TSR Self-Schedules”?

 

 

 

 

Please clarify  which BRQ in v1.4 speaks to transmission released under Bucket 2, Pathway 3? Also please clarify which TSR Type [1/2/3] this capacity associated with B2P3 will be mapped to?
ISO response

Thank you for your thoughtful questions. Please find the answers below.

Section 5.5 (SIBR) – EDAM-TSR-BRQ-11141a and EDAM-TSR-BRQ-11144e: Please explain which Bucket of transmission is associated with Transient TSR Type 1s (11141a) and Registered Type 1 TSRs (11144e)?

Answer: All TSR Type 1 self-schedules are associated with Bucket 1, Pathway 1. Please note that SIBR, the Market, and Settlements do not use or recognize buckets and pathways; they use TSR Types instead because they are easily and clearly defined in the design.

Additionally, please note that the cut-off time to submit all Type 1 TSR bids (Registered and Transient) has been changed to 9:00 am to support the validation timeline. This change will be reflected in the next published iteration of the BRS.

Section 5.5 (SIBR) – Please provide clarification as to when might an EESC define a Transient Type 1 TSR in SIBR?

Answer: Transient Type 1 TSRs may be submitted into SIBR as early as 7 days before the DAM run, and must be submitted by 9 am on D+1 to be considered in that DAM run.

Section 5.5 (SIBR) – EDAM-TSR-BRQ-02051d: Please provide clarification as to how MAXIMUM_CAPACITY is being calculated for Type 1-4 TSRs?

Answer: Maximum Capacity is submitted as an attribute of the TSR, it is provided by the EESC or TCSC that submits the TSR attributes

Section 5.5 (SIBR) – EDAM-TSR-BRQ-02051d: Is the MAXIMUM_CAPACITY for all TSR Types (1-4) TSRs being calculated by EESC?

Answer: In SIBR the TCSC submits TSR attributes for Transient Type 1 and Type 2 TSRs, and the EESC submits attributes for Type 3 and Type 4 TSRs.

Section 5.5 – Please clarify which transmission bucket pathway B2 [P1/P2/P3] is associated with “Type 2 TSR Self-Schedules”?

Answer: TSR Type 2 Released Capacity is associated with Bucket 2, Pathway 2. Please note that SIBR, the Market, and Settlements do not use or recognize buckets and pathways; they use TSR Types instead because they are easily and clearly defined in the design.

Section 5.5 – Please clarify which requirement and TSR Type are associated with Bucket 2, Pathway 3?

Answer: TSR Type 4 is associated with Bucket 2, Pathway 3. Please see EDAM-TSR-BRQ-11146a for TSR Type 4 bid submission into SIBR. Please note that SIBR, the Market, and Settlements do not use or recognize buckets and pathways; they use TSR Types instead because they are easily and clearly defined in the design.

PGE
Submitted 04/10/2025, 12:28 pm

Contact

Alina (A5D5@pge.com)

1. Please provide the version of the EDAM BRS your comments apply to
Please specify the version of the BRS your comments apply to

EDAM BRS Version 1.4

2. Please provide any questions or comments your organization may have regarding section 5 of the EDAM BRS.
When providing input in the text box below, please specify the BRQ(s) to which your comment or question refers. Please note that there are currently two companion initiatives for EDAM that will be implemented at the same time: 1) EDAM Implementation, which addresses the entire market framework for the EDAM footprint, and 2) EDAM ISO BAA Participations Rules, which applies specific operational and settlement participation rules to the EDAM market for the ISO BAA (‘CISO’). This document pertains to the former.

Section 5.1: Business Process: Manage Model & Contract Implementation & Full Network Model (Master File)

BRQ 02318 -Remove Existing Base ETSR Apnodes.
Remove existing Apnodes that are associated with WEIM ETSRs. Base ETSR Apnode mapping shall be updated to Transfer Location, as defined in EDAM-TSR-BRQ-02316

PGE Question: With the removal of existing Base ETSR Apnodes, will there be any changes to the data structure or any other changes. Could you please help to Clarify.

Section 5.2: Business Process:  Manage Forecasting(ALFS)

In version 4 of the EDAM BRS, CAISO appears to make a distinction between the EDAM entities in BRQ 04052 and the WEIM entities in BRQ 04052a.   
•    BRQ 04052: Non-Participating DR Schedules
•    BRQ 04052a: Non-Participating DR Schedules in 5 minute granularity
o    Note: This applies to WEIM Entities and CISO BAA load forecast zone.

  1. PGE Question: Can CAISO please clarify if the distinction between BRQ 04052 and BRQ 04052a is related to the granularity requirement for WEIM and CISO BAA, or whether there are other factors as well?
  2. PGE Question: BRQ 04052 talks about load forecasts zones that have enabled DR Inclusion Flag and confirmed DR Performance Factor option, using similar mechanism as receiving existing LF: Non-Participating DR Schedules and the notes, EDAM Entity shall include CAISO BAA is striked out from the requirement. Can CAISO please help to clarify why CAISO BAA is not included under EDAM Entity as PGE is in the CISO BAA load forecast zone?

Section 5.5 Business Process: Manage Bid Submission and TSR Submission (SIBR, TSR submission)

BRQ - TSRBRQ11145c Type 3 TSR Pairs with the CISO BAA .System shall generate a bid for the MATCHING_RES_ID when the MATCHING_SC_ID=CISO with the same Capacity Limit and AS self-provision as the

  1. PGE Question: Is the requirement incomplete or is any wording missing from the above requirement. Can CAISO please clarify?

 

 

ISO response

Thank you for your thoughtful questions. Please find the answers below.

Section 5.1 – EDAM-TSR-BRQ 02318 (MF): With the removal of existing Base ETSR Apnodes, will there be any changes to the data structure or any other changes?

Answer: No, there will not be any additional changes to the data structure of WEIM ETSRs. The WEIM Base ETSR Apnodes are used today for the LMP of base transfer deviations; this will now be based on the Transfer Location rather than the Apnode.
 

Section 5.2 – EDAM-BRQ-04052 and EDAM-BRQ-04052a (ALFS): Please clarify if the distinction between BRQ 04052 and BRQ 04052a.

Answer: EDAM-BRQ-04052 is to receive non-participating DR Schedules from the EDAM Entity. EDAM-BRQ-04052a is to receive non-participating DR schedules from WEIM Entity/Sub-entity (i.e. entities not in EDAM but in WEIM). This is the only distinction between the two requirements.

Section 5.2 – EDAM-BRQ-04052 (ALFS): Please clarify why CAISO BAA is not included under EDAM Entity.

Answer: This BRQ pertains to how the CAISO will receive non-participating DR schedules from EDAM Entities. The requirement is to develop a new functionality to receive this data from EDAM Entities; currently the CAISO does not have a mechanism to receive this data from EDAM Entities. This has no implications on what is considered a part of the EDAM forecasts zones. Additionally, the requirement establishes that non-participating DR must be set at EDAM/WEIM Entity level consistent with how the EDAM/WEIM Entity is configured in Master File.

CAISO BAA non-participating DR schedules will continue to be received through existing channels (this data is already being shared with the CAISO BAA forecasting team today). The CAISO, as an EDAM Entity, will provide the non-participating DR schedules to the market at the BAA level. Note that in the future there will a separate initiative to automate non-participating DR submittals from CAISO LSEs.

Section 5.5 – EDAM-TSR-BRQ-11145c: PGE Question: Is the requirement incomplete or is any wording missing from the above requirement. Can CAISO please clarify?

Answer: Yes this was an oversight, we apologize for the confusion. The requirement should read as follows (additions in bold/italic) “System shall generate a bid for the CISO TSR as the MATCHING_RES_ID when the MATCHING_SC_ID=CISO with the same Capacity Limit and AS self-provision as that of the Matching TSR.

3. Please provide any questions or comments your organization may have regarding the remainder of the EDAM BRS
When providing input in the text box below, please specify the section your comment or question refers to.

We are currently reveiwing the remainder of EDAM BRS Version 1.4

4. Please provide any additional questions or comments you may have.
When providing input, limit your questions and comments to the EDAM BRS and the EDAM Initiative.

No questions

Back to top