M2M Entitlement Topology Model and Impact Calculation Clause Samples

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 ...
View SourceView Similar (29)
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;
View SourceView Similar (9)
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:
View SourceView Similar (3)
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;
View Source

Related to M2M Entitlement Topology Model and Impact Calculation

  • PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:

  • Post-Commercial Operation Date Testing and Modifications Developer and Connecting Transmission Owner shall each at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice and Applicable Reliability Standards as may be necessary to ensure the continued interconnection of the Large Generating Facility with the New York State Transmission System in a safe and reliable manner. Developer and Connecting Transmission Owner shall each have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities (including required control technologies and protection systems) and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer’s Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Contract Sales Reporting. Contractor shall report total Contract sales quarterly for this Cooperative Purchasing Agreement to Enterprise Services, as set forth below. Contract Sales Reporting System. Contractor shall report quarterly Contract sales in Enterprise Services’ Contract Sales Reporting System. Enterprise Services shall provide Contractor with a login password and a vendor number. The password and vendor number shall be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized Purchasers specified herein during the term of the Contract. If there are no Contract sales during the reporting period, Contractor must report zero sales. Due dates for Contract Sales Reporting. Quarterly Contract Sales Reports must be submitted electronically by the following deadlines for all Contract sales invoiced during the applicable calendar quarter: Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.25 percent on the purchase price for all Cooperative Purchasing Agreement sales (the purchase price is the total invoice price less applicable sales tax) under this Cooperative Purchasing Agreement. The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Contract sales invoiced (not including sales tax) x .0125. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services shall invoice Contractor quarterly based on Contract sales reported by Contractor. Contractor is not to remit payment until Contractor receives an invoice from Enterprise Services. Payments must be received within thirty (30) calendar days of the invoice issue date from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference the invoice number. Contractor’s VMF payment to Enterprise Services must reference this Contract number, the year and quarter for which the VMF is being remitted, and Contractor’s name as set forth in this Contract, if not already included on the face of the check. Contractor’s failure to report accurate total net Contract sales, to submit a timely Contract sales report, or to remit timely payment of the VMF to Enterprise Services, shall be cause for Enterprise Services, at its discretion, to suspend Contractor or terminate this Contract or exercise remedies provided by law. Without limiting any other available remedies, the parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums, the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) calendar days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Contract Sales Report. Contractor shall provide to Enterprise Services a detailed annual Contract sales report. Such report shall include, at a minimum, the following: The Goods and/or Services sold and provided (including, as applicable, category or another identifier); Services purchased by Purchaser; and Contract price. This report must be provided in an electronic format that can be read by Microsoft (MS) Excel. Such report is due within thirty (30) calendar days of the annual anniversary of the effective date of this Contract.