DEMONSTRATED CAPACITY AND READINESS (RFP SECTION VII, A Sample Clauses

DEMONSTRATED CAPACITY AND READINESS (RFP SECTION VII, A. 6.) iPower is ready to begin on day 1 and we have the capacity to fulfill the anticipated contract requirements using current and long-standing employees, for whom resumes are provided in Appendix E. All these resources are current full-time iPower employees who are experienced, qualified, and available immediately upon contract award to support these efforts. Should the need arise, iPower also can tap into our matrixed team of SMEs and consultants who can be bought to bear whenever needed. Beyond this, iPower has an extensive resume database of qualified candidates who have already been interviewed and vetted, and we could recruit from this pool if necessary. iPower has a robust recruiting program that has enabled us to fill positions quickly, usually within 2 weeks or less. We also use existing partnerships with staffing firms to assist in filling niche positions quickly and seamlessly for our customers.
AutoNDA by SimpleDocs

Related to DEMONSTRATED CAPACITY AND READINESS (RFP SECTION VII, A

  • FREQUENCY AND CAPACITY LEVELS No restriction on frequency, capacity and aircraft type

  • Right to Contracted Capacity & Energy 4.4.1 The SPD will declare the CUF of the project and will be allowed to revise the same once within first year after COD of the project. Thereafter, the CUF for the Project shall remain unchanged for the entire term of the PPA. The declared annual CUF shall in no case be less than 17%. It shall be the responsibility of the SPD, entirely at its cost and expense to install such number of Solar panels and associated infrastructure(like project equipment)as may be necessary to achieve the required CUF, and for this purpose SPD shall make its own study and investigation of the GHI and other factors prevalent in the area which have implication on the quantum of generation. Further, arrangement of extra land for such installation shall be intimated to MSPDCL in advance and MSPDCL shall have to reply for the same in 7 days in the best interest of the project generation. However,non- availability of land shall not absolve SPD from his obligations under the PPA. SPD shall maintain generation so as to achieve annual CUF within + 10% and -15% of the declared value till the end of 10 years from COD, subject to the annual CUF remaining minimum of 15%, and within +10% and -20% of the declared value of the annual CUF thereafter till the end of the PPA duration of 25 years. The lower limit will, however, be relaxable by MSPDCL to the extent of non-availability of grid for evacuation which is beyond the control of the SPD. The annual CUF will be calculated every Contract Year. The compensation due to shortfall in generation shall be applied to the amount of shortfall in generation during the Contract Year. The amount of compensation shall be equal to the compensation payable (including equivalent amount of Electricity purchased from the grid for meeting load demand due to short fall in solar power) by the buying Entity, which shall ensure that the buying Entity is offset for all potential costs associated with low generation and supply of power under the PPA, subject to a minimum of 50% (fifty per cent) of the cost of this shortfall in energy terms, calculated at PPA tariff. The amount, being equal to the compensation payable, by the buying Entity for not meeting load requirements is only a measure of damage. It shall not be construed that the compensation is payable by SPD only if the buying Entity are required to pay compensation for such not meeting of load requirements or that the buying Entity or the SPD shall be required to prove or establish such payment of compensation for not meeting the load. SPD shall agree that the methodology specified herein above for calculation of liquidated damages payable by the SPD for shortfall in generation is a genuine and accurate pre-estimation of the actual loss that will be suffered by buying Entity. SPD shall further acknowledge that a breach of any of the obligations contained herein result in injuries and that the amount of the liquidated damages or the method of calculating the liquidated damages specified in this document is a genuine and reasonable pre-estimate of the damages that may be suffered by buying Entity in each case specified under this Agreement. However, this compensation shall not be applicable in events of Force Majeure identified under the PPA with MSPDCL, affecting supply of power by the SPD to the Buying Entity.

  • Power Factor Design Criteria (Reactive Power A wind generating plant shall maintain a power factor within the range of 0.95 leading to 0.95 lagging, measured at the Point of Interconnection as defined in this LGIA, if the ISO’s System Reliability Impact Study shows that such a requirement is necessary to ensure safety or reliability. The power factor range standards can be met using, for example without limitation, power electronics designed to supply this level of reactive capability (taking into account any limitations due to voltage level, real power output, etc.) or fixed and switched capacitors if agreed to by the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, or a combination of the two. The Developer shall not disable power factor equipment while the wind plant is in operation. Wind plants shall also be able to provide sufficient dynamic voltage support in lieu of the power system stabilizer and automatic voltage regulation at the generator excitation system if the System Reliability Impact Study shows this to be required for system safety or reliability.

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

  • Packet Switching Capability 4.5.1 The packet switching capability network element is defined as the function of routing or forwarding packets, frames, cells or other data units based on address or other routing information contained in the packets, frames, cells or other data units.

  • Contract Capacity The generation capability designated for the Project shall be the contract capacity in MW designated in the Cover Sheet, net of all auxiliary loads, station electrical uses, and Electrical Losses (the “Contract Capacity”). Throughout the Delivery Term, Seller shall sell and deliver all Product produced by the Project solely to Buyer. In no event shall Buyer be obligated to receive, in any Settlement Interval, any Surplus Delivered Energy. Seller shall not receive payment for any Surplus Delivered Energy. To the extent Seller delivers Surplus Delivered Energy to the Delivery Point in a Settlement Interval in which the Real-Time Price for the applicable PNode is negative, Seller shall pay Buyer an amount equal to the Surplus Delivered Energy (in MWh) during such Settlement Interval, multiplied by the absolute value of the Real-Time Price per MWh for such Settlement Interval.]

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Switching and Tagging Rules Each Party shall provide the other Parties a copy of its switching and tagging rules that are applicable to the other Parties’ activities. Such switching and tagging rules shall be developed on a non-discriminatory basis. The Parties shall comply with applicable switching and tagging rules, as amended from time to time, in obtaining clearances for work or for switching operations on equipment.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

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