M2M Entitlement Topology Model and Impact Calculation Sample Clauses
M2M Entitlement Topology Model and Impact Calculation. The M2M Entitlement calculation shall use both RTOs’ static topological models to determine the Non-Monitoring RTO’s mutually agreed upon share of a M2M Flowgate’s total capacity based on historic dispatch patterns. Both RTOs’ models must include the following items: a static transmission and generation model; generator, load, and PAR shift factors; generator output, load, and interchange schedules from 2009 through 2011 or any subsequent three year period mutually agreed to by the Parties; a PAR impact assumption that the PAR control is perfect for all PARs within the transmission models except the PARs at the Michigan-Ontario border; new or upgraded Transmission Facilities; and Transmission Facility retirements. Each Party shall calculate the GLDFs using a transmission model that contains a mutually agreed upon set of: (1) transmission lines that are modeled as in-service; (2) generators; and (3) loads. Using these GLDFs, generator output data from the three year period agreed to by the Parties, and load data from the three year period agreed to by the Parties, the Parties shall calculate each Party’s MW impact on each M2M Flowgate for each hour in the three year period agreed to by the Parties. Using these impacts, the Parties shall create a reference year consisting of four periods (“M2M Entitlement Periods”) for each M2M Flowgate. The M2M Entitlement Periods are as follows: M2M Entitlement Period 1: December, January, and February; M2M Entitlement Period 2: March, April, and May; M2M Entitlement Period 3: June, July, and August; and M2M Entitlement Period 4: September, October, and November. For each of the M2M Entitlement Periods listed above the Non-Monitoring RTO will calculate its M2M Entitlement on each M2M Flowgate for each hour of each day of a week that will serve as the representative week for that M2M Entitlement Period. The M2M Entitlement for each day/hour, for each M2M Flowgate will be calculated by averaging the Non-Monitoring RTO’s Market Flow on an M2M Flowgate for each particular day/hour of the week. The Non-Monitoring RTO shall use the Market Flow data for all of the like day/hours, that occurred in that day of the week and hour in the M2M Entitlement Period, in each year contained within the three year period agreed to by the Parties to calculate the Non-Monitoring RTO’s average Market Flow on each M2M Flowgate. When determining M2M settlements each Party will use the M2M Entitlement that corresponds to the hour of the week and to ...
M2M Entitlement Topology Model and Impact Calculation. The M2M Entitlement calculation shall use both RTOs’ static topological models to determine the Non-Monitoring RTO’s mutually agreed upon share of a M2M Flowgate’s total capacity based on historic dispatch patterns. Both RTOs’ models must include the following items:
1. a static transmission and generation model;
2. generator, load, and PAR shift factors;
3. generator output, load, and interchange schedules from 2009 through 2011 or any subsequent three year period mutually agreed to by the Parties;
4. a PAR impact assumption that the PAR control is perfect for all PARs within the transmission models except the PARs at the Michigan-Ontario border;
M2M Entitlement Topology Model and Impact Calculation. The M2M Entitlement calculation shall use both RTOs’ static topological models to determine the Non-Monitoring RTO’s mutually agreed upon share of a M2M Redispatch Flowgate’s total capacity based on historic dispatch patterns. Both RTOs’ models must include the following items:
M2M Entitlement Topology Model and Impact Calculation. The M2M Entitlement calculation shall be based on a static topological model to determine a non-Monitoring RTO’s share of a M2M Flowgate’s total capacity based on historic dispatch patterns. The model must include the following items:
1. a static transmission and generation model;