Usage Metrics Sample Clauses

Usage Metrics. The Customer agrees that it shall not access or use, or permit access to or use of, the Offering in excess of the applicable Usage Metric(s). If such excess use is made, the Customer agrees that it shall pay Darktrace's then-current standard fees for any such excess use. Where the Usage Metric is a per User basis (as specified on the applicable Product Order Form), Customer agrees that: (i) the maximum number of Users that it authorizes to access and use the Offering and the Documentation shall not exceed the number of User subscriptions it has purchased under that Product Order Form; and (ii) it will not allow any User subscription to be used by more than one individual User unless it has been reassigned in its entirety to another individual User, in which case the prior User shall no longer have any right to access or use the Offering and/or Documentation.

Usage Metrics. Usage Metrics for the SAP Fieldglass Cloud Services, to the extent referenced in the Order Form, are defined as follows:

Usage Metrics. 2.1. The Usage Metrics for the Cloud Service are defined below:

Usage Metrics. Client shall monitor its own use of the Subscription Services and should it require additional licenses or exceed the usage rights granted under Schedule “B”, it shall notify Nakisa of its additional requirements. Nakisa shall monitor Client’s use of the Subscription Services to ensure compliance with Usage Metrics and the terms of the Agreement and the Subscription Services Agreement. Client may request an increase to the Usage Metrics at any time during the Subscription Services Agreement Term by providing Nakisa with a Usage Metrics change request (“UMCR”). The additional Usage Metrics shall be applied, for the benefit of the Client, to the remaining Subscription Services Agreement Term. The fees in regards to the additional Usage Metrics shall be determined by Xxxxxx, at its sole discretion, within ten (10) days from the receipt of a UMCR. Any increase to the Usage Metrics during the Subscription Services Agreement Term will continue to apply for any subsequent renewal term. The Client shall remain responsible towards Nakisa for the Service Fees during the Subscription Services Agreement Term even when the Client uses less than the Usage Metrics purchased. Xxxxxx will inform Client about any actual use by Client in excess of the Usage Metrics stated in Schedule “B” of this Subscription Services Agreement. In the event Xxxxxx becomes aware that (i) Client underpaid Service Fees to Nakisa and/or (ii) Client has used the Subscription Services in excess of the Usage Metrics stated in Schedule “B” of this Subscription Services Agreement, Nakisa shall immediately invoice the Client and the Client shall pay the invoice for additional Usage Metrics within thirty (30) days from the receipt thereof. Nakisa may require that the Client execute a UMCR for the purchase of additional Usage Metrics. The additional Service Fees for any excess use shall accrue from the date the excess use began.

Usage Metrics. Your license to Tableau Software will be subject to either User-Based or Core-Based restrictions, as identified in the Documentation and on the applicable Ordering Document, or if there is no Ordering Document, as otherwise designated by Tableau. For the avoidance of doubt, not all usage metrics are applicable to all Software.

Usage Metrics. Services may be based on different usage metrics including, but not limited to, Permitted Users, Domains and Takedowns (each as defined in the applicable Supplemental Terms). “Permitted Users” means all end users of the Services being individuals employed by or otherwise under Customer’s control. Customer will allow only the number of Permitted Users shown in the applicable Services Order to access and use the Services. Customer may add Services or increase the number of Domains, Takedowns, or Permitted Users at any time during the Subscription Term, however, Customer must provide Reseller or Mimecast with advance notice prior to doing so and additional fees may apply. During a Subscription Term, it is not possible for Customer to (i) reduce the number of Domains, Takedowns, or Permitted Users; (ii) downgrade any of the Services ordered; or (iii) remove any of the Services ordered. Any reduction, downgrade, or removal of Services may be made effective at the start of a Renewal Term, but only if Mimecast receives notice of such change not less than ninety (90) days prior to the renewal date.

Usage Metrics. 2.1. The Usage Metric for the Cloud Service is User. User is any individual authorized to access the Cloud Service.

Usage Metrics. Certain F5 Services may be subject to Usage Metrics, as specified in an Order, the Documentation, or the Service-Specific Terms. Upon written request from us, you will: (a) certify in writing compliance with the applicable Usage Metrics (for example, by providing written evidence of the number of user accounts being monitored by the F5 Services); and/or (b) provide us reasonable access to your usage records and/or other internal logs, solely for the purpose of validating your compliance with the applicable Usage Metrics. If your use of the F5 Services exceeds the applicable Usage Metrics (“Excess Usage”), the Parties may work together to reduce such usage so that it conforms to applicable limits. If you are unable or unwilling to abide by any Usage Metrics, you will execute an Order for additional quantities of the applicable F5 Services promptly upon our request in order to become compliant with such Usage Metrics. You will be liable for fees associated with any Excess Usage determined in accordance with this Section.

Usage Metrics. 2.1. The applicable Usage Metric is Capacity Unit. Customer may exercise the Capacity Units on AI Services.

Usage Metrics. 2.1. The Usage Metric for the Cloud Service is User. User is any individual authorized to access the Cloud Service. 2.2. SAP Sales and Service Core, intelligent sales add-on is an optional service that can be included in the subscription with the following Cloud Service versions for an additional fee: SAP Sales and Service Core, SAP Sales Cloud, enterprise edition, SAP Service Cloud, enterprise edition, and SAP Sales Cloud, professional edition. The Usage Metric for SAP Sales and Service Core, intelligent sales add-on is User. SAP Sales and Service Core, intelligent sales add-on is not available in all data centers in which SAP Sales and Service Core is hosted. 2.3. SAP Sales and Service Core, service agent console is an optional service that can be included in the subscription with the following Cloud Service versions for an additional fee: SAP Sales and Service Core, SAP Sales Cloud, enterprise edition, SAP Service Cloud, enterprise edition, and SAP Service Cloud, professional edition. The Usage Metric for SAP Sales and Service Core, service agent console is User. SAP Sales and Service Core, service agent console is not available in all data centers in which SAP Sales and Service Core is hosted. 2.4. SAP Sales and Service Core, Dynamic visit planning add-on is an optional service that can be included in the subscription with the following Cloud Service versions for an additional fee: SAP Sales and Service Core, SAP Sales Cloud, enterprise edition and SAP Sales Cloud, professional edition. The Usage Metric for SAP Sales and Service Core, Dynamic visit planning add-on is User. SAP Sales and Service Core, Dynamic visit planning add-on is not available in all data centers in which SAP Sales and Service Core is hosted. Geo-codes in Dynamic visit planning are not for external use and may not be extracted from the Cloud Service via APIs or any other means.