Common use of IRO Clause in Contracts

IRO. 010-2 R3.1. A mutually agreeable format X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-010-2 R3.2. A mutually agreeable process for resolving data conflicts X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-010-2 R3.3. A mutually agreeable security protocol X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-017-1 R2. Each Transmission Operator and Balancing Authority shall perform the functions specified in its Reliability Coordinator’s outage coordination process. X Single MOD-001-1a R1. Each Transmission Operator shall select one of the methodologies1 listed below for calculating Available Transfer Capability (ATC) or Available Flowgate Capability (AFC) for each ATC Path per time period identified in R2 for those Facilities within its Transmission operating area: - The Area Interchange Methodology, as described in MOD-028 - The Rated System Path Methodology, as described in MOD-029 - The Flowgate Methodology, as described in MOD-030 X Single Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details MOD-001-1a R6. When calculating Total Transfer Capability (TTC) or Total Flowgate Capability (TFC) the Transmission Operator shall use assumptions no more limiting than those used in the planning of operations for the corresponding time period studied, providing such planning of operations has been performed for that time period. X Single MOD-008-1 R1. Each Transmission Operator shall prepare and keep current a TRM Implementation Document (TRMID) that includes, as a minimum, the following information: X Single

IRO. 010-2 R3.1. A mutually agreeable format X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details IRO-010-2 R3.2. A mutually agreeable process for resolving data conflicts X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-010-2 R3.3. A mutually agreeable security protocol X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-017-1 R2. Each Transmission Operator and Balancing Authority shall perform the functions specified in its Reliability Coordinator’s outage coordination process. X Single MOD-001-1a R1. Each Transmission Operator shall select one of the methodologies1 listed below for calculating Available Transfer Capability (ATC) or Available Flowgate Capability (AFC) for each ATC Path per time period identified in R2 for those Facilities within its Transmission operating area: - The Area Interchange Methodology, as described in MOD-028 - The Rated System Path Methodology, as described in MOD-029 - The Flowgate Methodology, as described in MOD-030 X Single Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details MOD-001-1a R6. When calculating Total Transfer Capability (TTC) or Total Flowgate Capability (TFC) the Transmission Operator shall use assumptions no more limiting than those used in the planning of operations for the corresponding time period studied, providing such planning of operations has been performed for that time period. X Single MOD-008-1 R1. Each Transmission Operator shall prepare and keep current a TRM Implementation Document (TRMID) that includes, as a minimum, the following information: X Single Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details MOD-008-1 R1.1. Identification of (on each of its respective ATC Paths or Flowgates) each of the following components of uncertainty if used in establishing TRM, and a description of how that component is used to establish a TRM value: - Aggregate Load forecast. - Load distribution uncertainty. - Forecast uncertainty in Transmission system topology (including, but not limited to, forced or unplanned outages and maintenance outages). - Allowances for parallel path (loop flow) impacts. - Allowances for simultaneous path interactions. - Variations in generation dispatch (including, but not limited to, forced or unplanned outages, maintenance outages and location of future generation). - Short-term System Operator response (Operating Reserve actions ). - Reserve sharing requirements. - Inertial response and frequency bias. X Single

IRO. 010-2 R3.1. A mutually agreeable format X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-010-2 R3.2. A mutually agreeable process for resolving data conflicts X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-010-2 R3.3. A mutually agreeable security protocol X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-017-1 R2. Each Transmission Operator and Balancing Authority shall perform the functions specified in its Reliability Coordinator’s outage coordination process. X Single MOD-001-1a R1. Each Transmission Operator shall select one of the methodologies1 listed below for calculating Available Transfer Capability (ATC) or Available Flowgate Capability (AFC) for each ATC Path per time period identified in R2 for those Facilities within its Transmission operating area: - The Area Interchange Methodology, as described in MOD-028 - The Rated System Path Methodology, as described in MOD-029 - The Flowgate Methodology, as described in MOD-030 X Single Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details MOD-001-1a R6. When calculating Total Transfer Capability (TTC) or Total Flowgate Capability (TFC) the Transmission Operator shall use assumptions no more limiting than those used in the planning of operations for the corresponding time period studied, providing such planning of operations has been performed for that time period. X Single MOD-008-1 R1. Each Transmission Operator shall prepare and keep current a TRM Implementation Document (TRMID) that includes, as a minimum, the following information: X Single

IRO. 010-2 R3.1. A mutually agreeable format X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-010-2 R3.2. A mutually agreeable process for resolving data conflicts X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details IRO-010-2 R3.3. A mutually agreeable security protocol X X Each The CAISO and TE shall each maintain compliance with this requirement with respect to its operations as identified in the operating procedure 3130 established by the CAISO. IRO-017-1 R2. Each Transmission Operator and Balancing Authority shall perform the functions specified in its Reliability Coordinator’s outage coordination process. X Single MOD-001-1a R1. Each Transmission Operator shall select one of the methodologies1 listed below for calculating Available Transfer Capability (ATC) or Available Flowgate Capability (AFC) for each ATC Path per time period identified in R2 for those Facilities within its Transmission operating area: - The Area Interchange Methodology, as described in MOD-028 - The Rated System Path Methodology, as described in MOD-029 - The Flowgate Methodology, as described in MOD-030 X Single Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details MOD-001-1a R6. When calculating Total Transfer Capability (TTC) or Total Flowgate Capability (TFC) the Transmission Operator shall use assumptions no more limiting than those used in the planning of operations for the corresponding time period studied, providing such planning of operations has been performed for that time period. X Single MOD-008-1 R1. Each Transmission Operator shall prepare and keep current a TRM Implementation Document (TRMID) that includes, as a minimum, the following information: X Single Responsibility Standard Req. Text of Requirement CAISO TE Responsibility (either Each, Split, Single or N/A) Responsibility Details MOD-008-1 R1.1. Identification of (on each of its respective ATC Paths or Flowgates) each of the following components of uncertainty if used in establishing TRM, and a description of how that component is used to establish a TRM value: - Aggregate Load forecast. - Load distribution uncertainty. - Forecast uncertainty in Transmission system topology (including, but not limited to, forced or unplanned outages and maintenance outages). - Allowances for parallel path (loop flow) impacts. - Allowances for simultaneous path interactions. - Variations in generation dispatch (including, but not limited to, forced or unplanned outages, maintenance outages and location of future generation). - Short-term System Operator response (Operating Reserve actions ). - Reserve sharing requirements. - Inertial response and frequency bias. X Single