Usage Monitoring. Customer is solely responsible for its own adherence to volume and use limitations indicated on the applicable Addendum. ESO may monitor Customer’s use of the Software, and if Customer’s usage exceeds the level indicated in the applicable Addendum (an “Overage”), Customer shall owe ESO the Fee corresponding to such usage level at a rate no higher than ESO’s then-standard pricing for new customers at an equivalent usage level. ESO may invoice for Overages immediately.
Usage Monitoring. Solely for the purpose of verifying Customer’s compliance with this Agreement, Supplier may monitor and review Customer’s usage of the SaaS and Customer shall provide Supplier with such additional records and assistance as Supplier may reasonably require. Such information and records shall constitute Confidential Information of Customer.
Usage Monitoring. RapidSOS monitors and collects configuration, performance, usage, and consumption data relating to the use of RapidSOS Services by Personnel, and may monitor Agency’s use of the RapidSOS Services, in each case: (a) to facilitate the delivery of the RapidSOS Services (such as tracking entitlements, providing support, monitoring the performance, integrity, and stability of the RapidSOS Services’ infrastructure, and preventing or addressing service or technical issues), (b) to improve the RapidSOS Services and provide anonymized analytics, (c) to ensure compliance with the terms of this Agreement. Agency shall not block or interfere with any such monitoring. For the avoidance of doubt, Agency acknowledges and agrees that RapidSOS may from time to time collect for its internal use in order to facilitate the delivery and maintenance of the RapidSOS Services, configuration, performance, usage and consumption data relating to the use of the RapidSOS Services by Customers and/or Agency consisting of: (a) date and time of event; (b) type of operation executed by the flow execution (e.g. SMS, call, 9-1-1 call, telephony events, etc.);
Usage Monitoring. Development of a system describing global usages of RCF, from a systematical and dynamical point of view, based on underlying monitoring tools. Task leader: UPEM (Xxxxxxxx Xxxxxxxx). Participants: AIT, CWTS, Joanneum, CNR, USFD, Ingenio Task 2 – Open Data VRE Deliver a tailored VRE operated and empowered by D4Science, in order to bridge RCF and OpenAIRE. This VRE will allow delivering to the RISIS community tailored and specific datasets collected by OpenAIRE and selected to satisfy the needs of the RISIS community. The VRE will therefore open a directional bridge from the open access and open science communities accessible through the OpenAIRE infrastructure.
ST 2.1 APIs design and documentation To exploit this connection to OpenAIRE, shortly identified as publication and access, a full set of APIs will be properly designed and documented.
Usage Monitoring. Fulfillment Party shall take all reasonable steps necessary to monitor End-User's usage of the Software Product as specified in Exhibit 1 hereto, and to advise Legato, where applicable, when End-User has reached the quantity limits permitted therein.
Usage Monitoring. Vice-Chancellors are responsible for educating subordinates about appropriate cellular telephone procedures and monitoring their usage (see xxxx://xx.xxxx.xxx/cellphones). In emergency situations, these managers may grant exceptions to these usage policies. In such circumstances, any charges incurred for personal use must be reimbursed by the employee on a timely basis.
Usage Monitoring. Usage monitoring tracks how the features and components of an application are used. An operator can use the gathered data to: • Determine which features are heavily used and determine any potential hotspots in the system. High-traffic elements might benefit from functional partitioning or even replication to spread the load more evenly. An operator can also use this information to ascertain which features are infrequently used and are possible candidates for retirement or replacement in a future version of the system. • Obtain information about the operational events of the system under normal use. For example, in an e-commerce site, you can record the statistical information about the number of transactions and the volume of customers that are responsible for them. This information can be used for capacity planning as the number of customers grows. • Detect (possibly indirectly) user satisfaction with the performance or functionality of the system. For example, if a large number of customers in an e-commerce system regularly abandon their shopping carts, this might be due to a problem with the checkout functionality. • Generate billing information. A commercial application or multitenant service might charge customers for the resources that they use. • Enforce quotas. If a user in a multitenant system exceeds their paid quota of processing time or resource usage during a specified period, their access can be limited or processing can be throttled. To examine system usage, an operator typically needs to see information that includes: • The number of requests that are processed by each subsystem and directed to each resource. • The work that each user is performing. • The volume of data storage that each user occupies. • The resources that each user is accessing. An operator should also be able to generate graphs. For example, a graph might display the most resource-hungry users, or the most frequently accessed resources or system features. Usage tracking can be performed at a relatively high level. It can note the start and end times of each request and the nature of the request (read, write, and so on, depending on the resource in question). You can obtain this information by: • Tracing user activity. • Capturing performance counters that measure the utilization for each resource. • Monitoring the resource consumption by each user. For metering purposes, you also need to be able to identify which users are responsible for performing which operations, and ...
Usage Monitoring. (Sprint only). This is a special budget protecting feature that is only available for Customers using Sprint wireless services. This feature includes email alerts are sent at 50, 75, and 90 percent usage with devices cut off if they reach 100 percent, trend reports for each end user, email notification of plan change requests when complete.
Usage Monitoring. The Company has the capability to, and anticipates that it may, monitor usage of the Software and Services in order to ensure compliance with the provisions of this agreement, provided support and other Services where applicable, and collect and aggregate certain data and information about use of the Software and Services, which the Company expects will help it to improve its products and services. Customer acknowledges and agrees to, without restriction or charge, Company’s use, execution, reproduction, display, performance, modification and distribution of such data and information.
Usage Monitoring. You will not take any action designed to or with the effect of concealing your usage of the CC Service, nor will you take any action to interfere with TCPs (or its
