Evaluation under the Deliverability Interconnection Standard Sample Clauses

Evaluation under the Deliverability Interconnection Standard. If the Large Facility requests XXXX, the ISO will determine whether the requested XXXX is likely to require System Deliverability Upgrades by performing a preliminary, non-binding evaluation of the deliverability of the Large Facility’s requested XXXX under the NYISO Deliverability Interconnection Standard. If the ISO determines that a preliminary deliverability evaluation is required in the SRIS, such requirement will be documented in the SRIS Scope. A Large Facility for which the ISO does not require a deliverability evaluation in the SRIS may, at Developer’s option, elect to include in the SRIS scope a preliminary evaluation of the Large Facility under the Deliverability Interconnection Standard. The preliminary deliverability evaluation will state the assumptions upon which it is based; state the results of the preliminary analyses; and, as applicable, identify and provide preliminary, non-binding cost estimates for potential System Deliverability Upgrades at a high level. The preliminary deliverability evaluation will be performed in accordance with the Class Year Study deliverability procedures set forth in Sections 25.7.3, 25.7.5, 25.7.8 and 25.7.9 of Attachment S to the OATT; provided, however, that the Large Facility will be evaluated individually and not on an aggregate basis with other projects. If the SRIS deliverability evaluation determines that a Large Facility is not deliverable for its full amount of requested XXXX, the ISO will (1) identify, at a high level, potential System Deliverability Upgrades to make the facility fully deliverable for the full amount of requested XXXX; and (2) provide preliminary non-binding cost estimates for such potential System Deliverability Upgrades. The identification and cost estimates of potential System Deliverability Upgrades in this preliminary deliverability evaluation may be based on generic information. If the Large Facility for which the SRIS includes a deliverability evaluation pursuant to this Section 30.7.3.2 and such evaluation identifies potential System Deliverability Upgrades, the evaluation of such upgrades will be refined in the Class Year Study prior to the Class Year Deliverability Study and subsequently revised, as necessary, in light of Class Year Deliverability Study results that may alleviate the need for or require alternative System Deliverability Upgrades. To the extent the ISO identifies alternative potential System Deliverability Upgrades, the Developer may elect which System Deli...
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs

Related to Evaluation under the Deliverability Interconnection Standard

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.

  • Transmission Delivery Service Implications Under ER Interconnection Service, Interconnection Customer will be eligible to inject power from the Generating Facility into and deliver power across the Transmission System on an “as available” basis up to the amount of MW identified in the applicable stability and steady state studies to the extent the upgrades initially required to qualify for ER Interconnection Service have been constructed. After that date FERC makes effective MISO’s Energy Market Tariff filed in Docket No. ER04-691-000, Interconnection Customer may place a bid to sell into the market up to the maximum identified Generating Facility output, subject to any conditions specified in the Interconnection Service approval, and the Generating Facility will be dispatched to the extent the Interconnection Customer’s bid clears. In all other instances, no transmission or other delivery service from the Generating Facility is assured, but Interconnection Customer may obtain Point-To-Point Transmission Service, Network Integration Transmission Service or be used for secondary network transmission service, pursuant to the Tariff, up to the maximum output identified in the stability and steady state studies. In those instances, in order for Interconnection Customer to obtain the right to deliver or inject energy beyond the Point of Interconnection or to improve its ability to do so, transmission delivery service must be obtained pursuant to the provisions of the Tariff. The Interconnection Customer’s ability to inject its Generating Facility output beyond the Point of Interconnection, therefore, will depend on the existing capacity of the Transmission or Distribution System as applicable, at such time as a Transmission Service request is made that would accommodate such delivery. The provision of Firm Point-To-Point Transmission Service or Network Integration Transmission Service may require the construction of additional Network or Distribution Upgrades.

  • Contract Deliverables The Contractor shall provide information technology staff augmentation services, including comprehensive management of staff, as set forth in this Contract. The term “staff” refers to the temporary staff provided by the Contractor to render information technology services identified by Customers, but that staff shall not be deemed an employee of the State or deemed to be entitled to any benefits associated with such employment. Contracts resulting from this solicitation should not be structured as fixed-price agreements or used for any services requiring authorization for payment of milestone tasks. Contractor shall only provide information technology staff augmentation services for those Job Titles awarded to the Contractor and shall be paid on an hourly basis. The Department’s intent is for Contractor’s information technology staff to provide services closely related to those described in the Job Family Descriptions document. Detailed scopes of work, specific requirements of the work to be performed, and any requirements of staff shall be provided by the Customer in a Request for Quote. The Contractor shall possess the professional and technical staff necessary to allocate, outsource, and manage qualified information technology staff to perform the services requested by the Customer. The Contractor shall provide Customers with staff who must have sufficient skill and experience to perform the services assigned to them. All of the information technology staff augmentation services to be furnished by the Contractor under the Contract shall meet the professional standards and quality that prevails among information technology professionals in the same discipline and of similar knowledge and skill engaged in related work throughout Florida under the same or similar circumstances. The Contractor shall provide, at its own expense, training necessary for keeping Contractor’s staff abreast of industry advances and for maintaining proficiency in equipment and systems that are available on the commercial market. The Contractor shall be responsible for the administration and maintenance of all employment and payroll records, payroll processing, remittance of payroll and taxes, and all administrative tasks required by state and federal law associated with payment of staff. The Contractor shall, at its own expense, be responsible for adhering to the Contract background screening requirements, testing, evaluations, advertising, recruitment, and disciplinary actions of Contractor’s information technology staff. The Contractor shall maintain during the term of the Contract all licenses, permits, qualifications, insurance and approvals of whatever nature that are legally required to perform the information technology staff augmentation services.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives. C.1. <Title> Deliverable 1

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Access Controls The system providing access to PHI COUNTY discloses to 20 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 21 must use role based access controls for all user authentications, enforcing the principle of least privilege.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Provide Data In Compliance With Laws LEA shall provide data for the purposes of the DPA in compliance with the FERPA, PPRA, IDEA, 603 C.M.R. 23.00, 603 CMR 28.00, and Massachusetts General Law, Chapter 71, Sections 34D to 34H, and the other privacy statutes quoted in this DPA. LEA shall ensure that its annual notice under FERPA includes vendors, such as the Provider, as “School Officials.”

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