Shortfall for Provisional ACL Sample Clauses

Shortfall for Provisional ACL. Prior to the Summer 2014 Capability Period if the Installed Capacity Supplier is a Responsible Interface Party, after each Special Case Resource with a Provisional Average Coincident Load has its Average Coincident Load determined for the Capability Period in which it had a Provisional Average Coincident Load (such determination in accordance with ISO Procedures and without regard to whether the resource was registered to the same Responsible Interface Party at the time of the ACL determination), the ISO shall determine if there is a shortfall due to the Provisional Average Coincident Load being higher than the Average Coincident Load. This shortfall will be equal to the value, if positive, of (x) the sum of (i) the amount of UCAP a Responsible Interface Party sold in an Monthly or an ICAP Spot Market Auction or certified Bilateral Transactions for a Special Case Resource and (ii) the Special Case Resource’s actual metered demand for the month in accordance with ISO Procedures, minus (y) the Special Case Resource’s Average Coincident Load. If the ISO does not receive data to determine the Average Coincident Load in accordance with ISO Procedures, for each Capability Period a Special Case Resource had a Provisional Average Coincident Load, for purposes of determining the shortfall, the Average Coincident Load shall equal zero. Beginning with the Summer of 2014 Capability Period if the Installed Capacity Supplier is a Responsible Interface Party, after each SCR with a Provisional ACL has its Verified ACL determined for the Capability Period in which it had a Provisional ACL (such determination in accordance with Section 5.12.11.1 and ISO Procedures) the ISO shall determine if there is a shortfall due to the Provisional ACL being greater than the Verified ACL. This shortfall shall be equal to the value, if positive, of (x) the Provisional ACL of the SCR, minus (y) the Verified ACL of the SCR. The shortfall calculated for the SCR for a month shall not exceed the amount of Installed Capacity associated with the SCR that was sold for that month. If the ISO does not receive data to determine the SCR’s Verified ACL for the Capability Period for which the SCR was enrolled with a Provisional ACL the Verified ACL shall equal zero.
AutoNDA by SimpleDocs

Related to Shortfall for Provisional ACL

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Additional Access Rights For the avoidance of doubt any grant of Access Rights not covered by the Grant Agreement or this Consortium Agreement shall be at the absolute discretion of the owning Party and subject to such terms and conditions as may be agreed between the owning and receiving Parties.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Cooling Off Period You may terminate this Contract with immediate effect at any time within the period of 14 days after the date this Contract is entered into without incurring any liability to DFMC.

  • Network Upgrades and Distribution Upgrades The Participating TO shall design, procure, construct, install, and own the Network Upgrades and Distribution Upgrades described in Appendix A. The Interconnection Customer shall be responsible for all costs related to Distribution Upgrades. Unless the Participating TO elects to fund the capital for the Distribution Upgrades and Network Upgrades, they shall be solely funded by the Interconnection Customer.

  • Child Support Enforcement Requirements Contractor is required to comply with the child support enforcement requirements of the County. Failure of the Contractor to comply with all federal, state, and local reporting requirements for child support enforcement or to comply with all lawfully served Wage and Earnings Assignment Orders and Notices of Assignment shall constitute a material breach of the Contract. Failure to cure such breach within 60 calendar days of notice from the County shall constitute grounds for termination of the Contract.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Jointly Provided Switched Access Services 7.5.1 Jointly Provided Switched Access Service is described and governed by the FCC and state access Tariffs, Multiple Exchange Carrier Access Billing (MECAB) and Multiple Exchange Carrier Ordering and Design (MECOD) Guidelines and based on LERG routing, and is not modified by any provisions of this Agreement. Both Parties agree to comply with such guidelines. CenturyLink and CLEC agree that the originating, intermediate, and terminating LECs for switched access will cooperatively determine the Jointly Provided Switched Access arrangements in which all parties concur.

Time is Money Join Law Insider Premium to draft better contracts faster.