Administration of Effective Load Carrying Capability Analysis Sample Clauses

Administration of Effective Load Carrying Capability Analysis. The Office of the Interconnection shall post final ELCC Class UCAP and ELCC Class Rating values at least once per year in a report that also includes appropriate details regarding methodology and inputs. The Office of the Interconnection shall post this report and shall communicate ELCC Resource Performance Adjustment values to applicable Generation Capacity Resource Providers no later than five months prior to the start of the target Delivery Year, as described in the PJM Manuals. Starting with the 2023/2024 Delivery Year, Accredited UCAP values for the applicable Delivery Year shall establish the maximum Unforced Capacity that an ELCC Resource can physically provide or offer to provide in the applicable Delivery Year. The Office of the Interconnection shall also post preliminary ELCC Class Rating values for nine subsequent Delivery Years. For any Delivery Year for which a final ELCC Class Rating has not been posted and a preliminary ELCC Class Rating has been posted, the Accredited UCAP of an ELCC Resource for such Delivery Year shall be based on the most recent preliminary ELCC Class Rating value for that Delivery Year, together with the most recently calculated ELCC Resource Performance Adjustment value for that ELCC Resource. Except to the extent specified above or otherwise specified, the preliminary ELCC Class Rating values for future years are non-binding and are only for indicative purposes. A Generation Capacity Resource Provider can offer or provide capacity from an ELCC Resource that is not subject to a capacity market must offer obligation (as specified in Tariff, Attachment DD, Section 6.6) at a level less than the Accredited UCAP for such resource. In order to facilitate the effective load carrying capability analysis, the Generation Capacity Resource Provider of each ELCC Resource must submit to the Office of the Interconnection the required information as specified in the PJM Manuals by no later than August 15 prior to the calendar year for the RPM Auction in which the ELCC Resource intends to submit a Sell Offer or otherwise commit to provide capacity, except for Delivery Years prior to the 2026/2027 Delivery Year such required information must be provided to the Office of the Interconnection in accordance with the PJM Manuals. The required information may include relevant physical parameters, relevant historical data such as weather data and actual or estimated historical energy output, and documentation supporting such parameters and hi...
Sample 1
AutoNDA by SimpleDocs

Related to Administration of Effective Load Carrying Capability Analysis

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.

  • Interconnection Customer Compensation for Actions During Emergency Condition The CAISO shall compensate the Interconnection Customer in accordance with the CAISO Tariff for its provision of real and reactive power and other Emergency Condition services that the Interconnection Customer provides to support the CAISO Controlled Grid during an Emergency Condition in accordance with Article 11.6.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Certification Regarding Debarment, Suspension, Ineligibility and Voluntary Exclusion - Lower Tier Covered Transactions (a) The prospective lower tier participant certifies, by submission of this proposal, that neither it nor its principals is presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation in this transaction by any federal department or agency.

  • Enhanced Optional Daily Usage File (EODUF 13.1 The EODUF service Agreement with terms and conditions is included in this Attachment as Exhibit C. Rates for EODUF are as set forth in Exhibit D.

  • Maintenance and Warranty Service Reports The report shall include the name of the Authorized User and all of the information in Section 2.24.1 and be submitted electronically in Microsoft Excel 2010 or newer version unprotected, via e-mail to the attention of the OGS Contract Administrator.

  • REQUIREMENT ON ELIGIBILITY AND REGISTRATION OF E-BIDDERS 1.1. Any interested party who intend to participate in the online public auction ("E-Bidders") auction can register as a user by logging onto PAH Website

  • Certification of Funds; Budget and Fiscal Provisions; Termination in the Event of Non-Appropriation This Agreement is subject to the budget and fiscal provisions of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement. THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.

  • 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.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!