Float Case Load Sample Clauses

Float Case Load. Management will use best efforts to access additional resources to assist with any increased case load in the event of floating.
AutoNDA by SimpleDocs

Related to Float Case Load

  • Total Contract Amount The contract total for services shall not exceed $1,200,000. Pricing shall be per Exhibit F attached.

  • Equipment Usage The equipment must remain in use for the specific project for which it was obtained in accordance with 2 CFR § 200.313(c)(1), unless the provision in 2 CFR § 200.313(c)(4) applies.

  • Funding Availability This Contract is at all times subject to state appropriations. The Department makes no express or implied representation or guarantee of continued or future funding under this Contract. The Department has, as of the date of the execution of this Contract, obtained all requisite approvals and authority to enter into and perform its obligations under this Contract, including, without limitation, the obligation to make the initial payment or payments required to be made under this Contract on the date or dates upon which such initial payment or payments may otherwise be disbursed during the current contract period, (i.e., Sept ember 1, 2015, through August 31, 2017). The Grantee acknowledges the Department’s authority to make such payments is contingent upon the Texas Legislature's appropriation to the Department of sufficient funds and the availability of funds to the Department for such purpose. If the State of Texas or the federal government terminates its appropriation through the Department or fails to pay the full amount of the allocation for the operation of any grant or reimbursement program hereunder , or the funds are otherwise unavailable, the Department may immediately and without penalty reduce payments or terminate this Contract, in whole or in part. Upon termination of the Contract or reduction of payments, the Grantee shall return to the Department any unexpended funds already disbursed to the Grantee. Neither the Department nor the State of Texas shall incur liability for damages or any loss that may be caused or associated with such termination or reduction of payments. The Department shall not be required to give prior notice for termination or reduction of payments.

  • Under-Frequency and Over Frequency Conditions The New York State Transmission System is designed to automatically activate a load- shed program as required by the NPCC in the event of an under-frequency system disturbance. Developer shall implement under-frequency and over-frequency relay set points for the Large Generating Facility as required by the NPCC to ensure “ride through” capability of the New York State Transmission System. Large Generating Facility response to frequency deviations of predetermined magnitudes, both under-frequency and over-frequency deviations, shall be studied and coordinated with the NYISO and Connecting Transmission Owner in accordance with Good Utility Practice. The term “ride through” as used herein shall mean the ability of a Generating Facility to stay connected to and synchronized with the New York State Transmission System during system disturbances within a range of under-frequency and over-frequency conditions, in accordance with Good Utility Practice and with NPCC Regional Reliability Reference Directory # 12, or its successor.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Line Outage Costs Notwithstanding anything in the NYISO OATT to the contrary, the Connecting Transmission Owner may propose to recover line outage costs associated with the installation of Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades on a case-by-case basis.

  • CAISO Monthly Billed Fuel Cost [for Geysers Main only] The CAISO Monthly Billed Fuel Cost is given by Equation C2-1. CAISO Monthly Billed Fuel Cost Equation C2-1 = Billable MWh ◆ Steam Price ($/MWh) Where: • Steam Price is $16.34/MWh. • For purposes of Equation C2-1, Billable MWh is all Billable MWh Delivered after cumulative Hourly Metered Total Net Generation during the Contract Year from all Units exceeds the Minimum Annual Generation given by Equation C2-2. Equation C2-2 Minimum Annual Generation = (Annual Average Field Capacity ◆ 8760 hours ◆ 0.4) - (A+B+C) Where: • Annual Average Field Capacity is the arithmetic average of the two Field Capacities in MW for each Contract Year, determined as described below. Field Capacity shall be determined for each six-month period from July 1 through December 31 of the preceding calendar year and January 1 through June 30 of the Contract Year. Field Capacity shall be the average of the five highest amounts of net generation (in MWh) simultaneously achieved by all Units during eight-hour periods within the six-month period. The capacity simultaneously achieved by all Units during each eight-hour period shall be the sum of Hourly Metered Total Net Generation for all Units during such eight-hour period, divided by eight hours. Such eight-hour periods shall not overlap or be counted more than once but may be consecutive. Within 30 days after the end of each six-month period, Owner shall provide CAISO and the Responsible Utility with its determination of Field Capacity, including all information necessary to validate that determination. • A is the amount of Energy that cannot be produced (as defined below) due to the curtailment of a Unit during a test of the Facility, a Unit or the steam field agreed to by CAISO and Owner. • B is the amount of Energy that cannot be produced (as defined below) due to the retirement of a Unit or due to a Unit’s Availability remaining at zero after a period of ten Months during which the Unit’s Availability has been zero. • C is the amount of Energy that cannot be produced (as defined below) because a Force Majeure Event reduces a Unit’s Availability to zero for at least thirty (30) days or because a Force Majeure Event reduces a Unit’s Availability for at least one hundred eighty (180) days to a level below the Unit Availability Limit immediately prior to the Force Majeure Event. • The amount of Energy that cannot be produced is the sum, for each Settlement Period during which the condition applicable to A, B or C above exists, of the difference between the Unit Availability Limit immediately prior to the condition and the Unit Availability Limit during the condition.

  • Reallocation to a Class with a Lower Salary Range Maximum 1. If the employee meets the skills and abilities requirements of the position and chooses to remain in the reallocated position, the employee retains existing appointment status and has the right to be placed on the Employer’s internal layoff list for the classification occupied prior to the reallocation.

  • Check Meters Developer, at its option and expense, may install and operate, on its premises and on its side of the Point of Interconnection, one or more check meters to check Connecting Transmission Owner’s meters. Such check meters shall be for check purposes only and shall not be used for the measurement of power flows for purposes of this Agreement, except as provided in Article 7.4 below. The check meters shall be subject at all reasonable times to inspection and examination by Connecting Transmission Owner or its designee. The installation, operation and maintenance thereof shall be performed entirely by Developer in accordance with Good Utility Practice.

  • System Availability System Availability percentage is calculated as follows:  Total MinutesintheMonth −Downtime   System Availability%age =  Total MinutesintheMonth *100    System Availability SLA (“SLA”) 99.5% System Availability percentage during each Month for productive versions Credit 2% of Monthly Subscription Fees for each 1% below SLA, not to exceed 100% of Monthly Subscription Fees Excluded Downtime Total Minutes in the Month attributable to: (i) a Scheduled Downtime for which a Regular Maintenance Window is described in Section 4 below, or (ii) any other Scheduled Downtime according to Section 4 for which the customer has been notified at least five (5) business days prior to such Scheduled Downtime or (iii) unavailability caused by factors outside of SAP’s reasonable control, such as unpredictable and unforeseeable events that could not have been avoided even if reasonable care had been exercised. Scheduled Downtime Scheduled Downtime for the applicable Cloud Services to which customer has subscribed is set forth in Section 4 below entitled “Maintenance Windows for Cloud Services”.

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