Usage Model Sample Clauses

Usage Model. MSP agrees to pay the applicable monthly usage Fees, as calculated based on the usage-based tier (“Usage Based Program Tier”) designated in the Order Form, which shall be the greater of the (i) Fees calculated per Device for all Customer Devices that the Software has been made available (regardless of usage) at any time during that month, or (ii) the applicable Usage Based Program Tier minimum. Unless otherwise agreed in the applicable Order Form, Malwarebytes shall invoice MSP the applicable Fees at the end of each calendar month and MSP shall pay such Fees within 30 days from the date of invoice. MSP acknowledges that as part of committing to the usage based billing model, it commits to a certain Usage Based Program Tier which requires MSP commit to a certain minimum monthly payment regardless of actual usage. Accordingly, if MSP makes the Software available to less than that minimum number of Devices in a calendar month, then MSP’s payment obligations for such month shall still require the payment of monthly usage Fees calculated based on the minimum number of Devices associated with the Usage Based Program Tier it has committed to.
AutoNDA by SimpleDocs
Usage Model. MSP agrees to pay the applicable monthly usage fees, as designated in the MSP Portal, per Device for all Customer Devices that the Software has been made available at any time during that month. Malwarebytes shall invoice MSP the applicable fees at the end of each calendar month and MSP shall pay such fees within 30 days from the date of invoice. For example, if the Software has been installed on 5,000 Devices in month one and in month two only 2,000 of those Devices actively use the Software, however, the Software remains installed on the remaining 3,000 Devices for at least one day of that month, then in both month one and month two, MSP shall pay the applicable monthly fees for all 5,000 Devices. MSP acknowledges that as a condition for electing to use the usage model, the minimum license Device quantity that Malwarebytes makes available for licensing the Software is 25 Devices per month. Accordingly, if MSP makes the Software available to less than 25 Devices in a calendar month, then MSP’s payment obligations for such month shall still require the payment of monthly usage fees for 25 Devices.
Usage Model. The Motive Duet "Infrastructure Software" (consisting of Motive Duet Server, Motive Solo Server, and Motive Integration Server licenses), Motive Solo Self Service Licenses, and Motive Support Desktop Licenses shall be provided and licensed on an [*]. Compaq will use the Motive Software for providing basic service and standard warranty support for Compaq systems only. Software provided under this Exhibit shall not be used to support Compaq's [*] line or any other product sold by Compaq's [*].

Related to Usage Model

  • Service Providing Methodology 1.3.1 Party A and Party B agree that during the term of this Agreement, where necessary, Party B may enter into further service agreements with Party A or any other party designated by Party A, which shall provide the specific contents, manner, personnel, and fees for the specific services.

  • Methodology 1. The price at which the Assuming Institution sells or disposes of Qualified Financial Contracts will be deemed to be the fair market value of such contracts, if such sale or disposition occurs at prevailing market rates within a predefined timetable as agreed upon by the Assuming Institution and the Receiver.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Contract Schedule The information set forth in the Contract Schedule is true and correct.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Trademarks and Service Marks In the event the Administrative Agent forecloses on its security interest in the License Agreements and transfers the License Agreements to a Person who does not meet the Successor Manager Requirements, then Sprint PCS shall have the right to terminate the License Agreements and cause the Administrative Agent to release its security interest in the License Agreements immediately prior to such transfer.

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