Common use of Compute the RTO Aggregate Market Flow for all M2M Flowgates Clause in Contracts

Compute the RTO Aggregate Market Flow for all M2M Flowgates. With the RTO_GTL and PAR_IMPACT known, we can now compute the RTO_MF for all M2M Flowgates as: Where: M2M_Flowgate-m = the relevant flowgate; RTO_MFM2M_Flowgate-m = the Market Flow caused by RTO generation dispatch and transaction scheduling on M2M Flowgate m after accounting for the operation of both the common and non-common PARs; RTO_GTLM2M_Flowgate-m = the generation to load flow for the entire RTO footprint on M2M Flowgate m; Parallel_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are not jointly scheduled by the participating RTOs; Shared_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are jointly scheduled by the participating RTOs; and PAR_ImpactM2M_Flowgate-m = the flow on M2M Flowgate m that is affected after accounting for the operation of both the common and non-common PARs.

Compute the RTO Aggregate Market Flow for all M2M Flowgates. With the RTO_GTL and PAR_IMPACT known, we can now compute the RTO_MF for all M2M Flowgates as: 𝑅𝑇𝑂_𝑀𝐹𝑀2𝑀_𝐹𝑙𝑜𝑤𝑔𝑎𝑡𝑒−𝑚 = 𝑅𝑇𝑂_𝐺𝑇𝐿𝑀2𝑀_𝐹𝑙𝑜𝑤𝑔𝑎𝑡𝑒−𝑚 + 𝑃𝑎𝑟𝑎𝑙𝑙𝑒𝑙_𝑇𝑟𝑎𝑛𝑠𝑓𝑒𝑟𝑠𝑀2𝑀_𝐹𝑙𝑜𝑤𝑔𝑎𝑡𝑒−𝑚 + 𝑆ℎ𝑎𝑟𝑒𝑑_𝑇𝑟𝑎𝑛𝑠𝑓𝑒𝑟𝑠𝑀2𝑀_𝐹𝑙𝑜𝑤𝑔𝑎𝑡𝑒−𝑚 − 𝑃𝐴𝑅_𝐼𝑚𝑝𝑎𝑐𝑡𝑀2𝑀_𝐹𝑙𝑜𝑤𝑔𝑎𝑡𝑒−𝑚 Where: M2M_Flowgate-m = the relevant flowgate; RTO_MFM2M_Flowgate-m = the Market Flow caused by RTO generation dispatch and transaction scheduling on M2M Flowgate m after accounting for the operation of both the common and non-common PARs; RTO_GTLM2M_Flowgate-m = the generation to load flow for the entire RTO footprint on M2M Flowgate m; Parallel_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are not jointly scheduled by the participating RTOs; Shared_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are jointly scheduled by the participating RTOs; and PAR_ImpactM2M_Flowgate-m = the flow on M2M Flowgate m that is affected after accounting for the operation of both the common and non-non- common PARs.

Compute the RTO Aggregate Market Flow for all M2M Flowgates. With the RTO_GTL and PAR_IMPACT known, we can now compute the RTO_MF for all M2M Flowgates as: Where: M2M_Flowgate-m = the relevant flowgate; RTO_MFM2M_Flowgate-m = the Market Flow caused by RTO generation dispatch and transaction scheduling on M2M Flowgate m after accounting for the operation of both the common and non-common PARs; RTO_GTLM2M_Flowgate-m = the generation to load flow for the entire RTO footprint on M2M Flowgate m; Parallel_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are not jointly scheduled by the participating RTOs; Shared_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are jointly scheduled by the participating RTOs; and PAR_ImpactM2M_Flowgate-m = the flow on M2M Flowgate m that is affected after accounting for the operation of both the common and non-non- common PARs.

Compute the RTO Aggregate Market Flow for all M2M Flowgates. With the RTO_GTL and PAR_IMPACT known, we can now compute the RTO_MF for all M2M Flowgates as: _2_− = _2_− + _2_− + ℎ_2_− − _2_− Where: M2M_Flowgate-m = the relevant flowgate; RTO_MFM2M_Flowgate-m = the Market Flow caused by RTO generation dispatch and transaction scheduling on M2M Flowgate m after accounting for the operation of both the common and non-common PARs; RTO_GTLM2M_Flowgate-m = the generation to load flow for the entire RTO footprint on M2M Flowgate m; Parallel_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are not jointly scheduled by the participating RTOs; Shared_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are jointly scheduled by the participating RTOs; and PAR_ImpactM2M_Flowgate-m = the flow on M2M Flowgate m that is affected after accounting for the operation of both the common and non-non- common PARs.

Compute the RTO Aggregate Market Flow for all M2M Flowgates. With the RTO_GTL and PAR_IMPACT known, we can now compute the RTO_MF for all M2M Flowgates as: RTO_MFM2M_FSowgate–n = RTO_GTLM2M_FSowgate–n + Parallel_TransfersM2M_FSowgate–n + Shared_TransfersM2M_FSowgate–n — PAR_IneactM2M_FSowgate–n Where: M2M_Flowgate-m = the relevant flowgate; RTO_MFM2M_Flowgate-m = the Market Flow caused by RTO generation dispatch and transaction scheduling on M2M Flowgate m after accounting for the operation of both the common and non-common PARsparsPARs; RTO_GTLM2M_Flowgate-m = the generation to load flow for the entire RTO footprint on M2M Flowgate m; Parallel_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are not jointly scheduled by the participating RTOs; Shared_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m caused by interchange schedules that are jointly scheduled by the participating RTOs; and PAR_ImpactM2M_Flowgate-m = the flow on M2M Flowgate m that is affected after accounting for the operation of both the common and non-non- common PARsparsPARs.