Average Usage Sample Clauses

Average Usage. Class Members shall be entitled to a cash payment equal to the greater of Five Dollars ($5.00) or 65% of the Calculated Amount (“Average Usage Benefit”). Under no circumstances can the Average Usage Benefit exceed Four Hundred Twenty-Five Dollars ($425.00) per Valid Claim.
AutoNDA by SimpleDocs

Related to Average Usage

  • Leave Usage Full shift absences on vacation, sick leave, compensating time off, or holiday in lieu taken by employees on scheduled ten-hour workshifts shall result in the deduction of ten (10) hours from employees’ accrued leave balances.

  • Average Daily Balance To get the "Average Daily Balance" of Purchases, we take the beginning balance of your Credit Card account each day, add any new Purchases, and subtract any Cash Advances, payments, or other credits which were applied to Purchases, unpaid FINANCE CHARGES, late charges, membership fees, and other fees. If you paid the Purchases balance in full by the Payment Due Date in the previous billing cycle, in the current billing cycle we will credit payments otherwise applicable to Purchases based on our allocation method as of the first day of the current billing cycle. These computations give us the Purchases daily balance. To get the "Average Daily Balance" of Cash Advances, we take the beginning balance each day, add any new Cash Advances, and subtract any Purchases, payments, or other credits which were applied to Cash Advances, unpaid FINANCE CHARGES, late charges, membership fees, and other fees. This gives us the Cash Advances daily balance. Then we add up all of the Purchases or Cash Advance daily balances for the billing period and divide each total by the number of days in the billing period. This gives us the "Average Daily Balances."

  • Data Usage We may use Data for the following purposes (in each case to the extent permitted by law):

  • Enhanced Optional Daily Usage File (EODUF)

  • Word Usage Words used in the masculine shall apply to the feminine where applicable, and wherever the context of this Agreement dictates, the plural shall be read as the singular and the singular as the plural.

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

  • Average Contribution Amount For purposes of this Agreement, to ensure that all employees enrolled in health insurance through the City’s HSS are making premium contributions under the Percentage-Based Contribution Model, and therefore have a stake in controlling the long term growth in health insurance costs, it is agreed that, to the extent the City's health insurance premium contribution under the Percentage-Based Contribution Model is less than the “average contribution,” as established under Charter section A8.428(b), then, in addition to the City’s contribution, payments toward the balance of the health insurance premium under the Percentage-Based Contribution Model shall be deemed to apply to the annual “average contribution.” The parties intend that the City’s contribution toward employee health insurance premiums will not exceed the amount established under the Percentage-Based Contribution Model.

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

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

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