Compute the RTO Interchange Scheduling Impacts for all M2M Flowgates Sample Clauses

Compute the RTO Interchange Scheduling Impacts for all M2M Flowgates. For each scheduling point that the participating RTO is responsible for, determine the net interchange schedule in MWs. Table 3 below identifies both the participating RTO that is responsible for each listed scheduling point, and the “type” assigned to each listed scheduling point. Table 3. List of Scheduling Points Scheduling Point Scheduling Point Type Participating RTO(s) Responsible NYISO-PJM common NYISO and PJM HTP Scheduled Line common NYISO and PJM Linden VFT Scheduled Line common NYISO and PJM Neptune Scheduled Line common NYISO and PJM PJM shall post and maintain a list of its non-common scheduling points on its OASIS website. PJM shall provide to NYISO notice of any new or deleted non-common scheduling points prior to implementing such changes in its M2M software. non-common PJM NYISO non-common scheduling points include all Proxy Generator Buses and Scheduled Lines listed in the table that is set forth in Section 4.4.4 of the NYISO’s Market Services Tariff that are not identified in this Table 3 as common scheduling points. The NYISO shall provide to PJM notice of any new or deleted non-common scheduling points prior to implementing such changes in its M2M software. non-common NYISO Where: sched_pt = the relevant scheduling point. A scheduling point can be either a proxy or a scheduled line; RTO_Transferssched_pt = the net interchange schedule at a scheduling point; Importssched_pt = the import component of the interchange schedule at a scheduling point; WheelsInsched_pt = the injection of wheels-through component of the interchange schedule at a scheduling point; Exportssched_pt = the export component of the interchange schedule at a scheduling point; and WheelsOutsched_pt = the withdrawal of wheels-through component of the interchange schedule at a scheduling point. The equation below applies to all non-common scheduling points that only one of the participating RTOs is responsible for. Parallel_Transfers are applied to the Market Flow of the responsible participating RTO. For example, the Parallel_Transfers computed for the IESO-NYISO non-common scheduling point are applied to the NYISO Market Flow. Where: M2M_Flowgate-m = the relevant flowgate; nc_sched_pt = the relevant non-common scheduling point. A non-common scheduling point can be either a proxy or a scheduled line. Non-common scheduling points are identified in Table 3, above; Parallel_TransfersM2M_Flowgate-m = the flow on M2M Flowgate m due to the net interchange schedule at the non-...

Compute the RTO Interchange Scheduling Impacts for all M2M Flowgates. For each scheduling point that the participating RTO is responsible for, determine the net interchange schedule in MWs. Table 3 below identifies both the participating RTO that is responsible for each listed scheduling point, and the “type” assigned to each listed scheduling point.