Operational Metrics. Operational Metrics – Metrics on trouble tickets opened by CENTURYLINK and West or reported by the Customer through the West portal accessed ticket system, specifically • Trouble tickets – Number of tickets opened and closed each month • Trouble tickets – Average time between ticket open and ticket close time. It should be noted that the average ticket close time may not be equivalent to the service resolution time in the case where there were delays in the customer providing additional information needed for West to triage and resolve reported system issues.
Operational Metrics. From time to time, Ventiv may collect and process technical and related information about Customer’s use of the Software and System (which may include, without limitation, ingest volume, search concurrency, number of unique user logins, Internet protocol address, session duration, policy, claims and risk data, frequency, severity and type of risk or claim and other similar data), may analyze and aggregate your data and information with data and/or information Ventiv may have obtained or may in the future obtain from other of its clients, publicly available sources and/or data providers, and may disclose such analyses and aggregated data to individual prospective or current Ventiv clients, provided that (i) your data is synthesized and made anonymous prior to such use, (ii) Ventiv does not use such synthesized and anonymous data of yours in a manner which would allow you to be identified, and (iii) your data is not transferred to such prospective or current clients.
Operational Metrics. A. Availability. Overture will maintain [*]% Availability as measured by [*] production query logs, verified by [*] with at least [*] intervals, reported [*]. In the event of discrepancies between these two sources, Yahoo and Overture will work together to determine root cause of such discrepancy. If Availability falls below [*]%, Problem Resolution would occur, and the Cure Period (i.e., the process under Article IV, Section
Operational Metrics. The Service Provider and the State of Delaware shall reach agreement on operational metrics and document said metrics in the Service Level Agreement. Examples include but are not limited to: a) Advance notice and change control for major upgrades and system changes b) System availability/uptime guarantee/agreed-upon maintenance downtime c) Recovery Time Objective/Recovery Point Objective d) Security Vulnerability Scanning
Operational Metrics. The Seller and the State shall reach agreement on operational metrics and document said metrics in the Service Level Agreement. Examples include but are not limited to:
Operational Metrics. The Service Provider and New Castle County shall reach agreement on operational metrics and document said metrics in the Service Level Agreement. Examples include but are not limited to: Advance notice and change control for major upgrades and system changes System availability/uptime guarantee/agreed-upon maintenance downtime Recovery Time Objective/Recovery Point Objective Security Vulnerability Scanning By signing this Agreement, the Service Provider agrees to abide by all of the above Terms and Conditions. Service Provider Name/Address (print): Service Provider Authorizing Official Name (print): Service Provider Authorizing Official Signature: Date:
Operational Metrics. SuccessionHR monitors and collects Operational Metrics for its own business purposes, such as improving, testing, and maintaining the Platform and developing additional products and services. Customer grants to SuccessionHR an irrevocable, non-exclusive, transferable, worldwide, and royalty-free right to collect, analyze and use Operational Metrics relating to its delivery of services that may be in part derived from, or related to, the Customer Data, including the generation of reports for internal, external, and public use, and to use Operational Metrics for SuccessionHR’s internal business purposes.
Operational Metrics. Gathr monitors and collects anonymized statistics, metrics, analytics, and data regarding the performance and operation of the Gathr Platform in connection with Customer’s and/or its Authorized Users’ use of the Gathr Platform and other operational and technical metrics necessary to manage and perform Gathr Platform (collectively, “Operational Metrics”) for Gathr’ own business purposes, such as improving, testing, and maintaining the Gathr Platform and developing additional products and services. Customer grants to Gathr a non-exclusive, irrevocable, transferable, worldwide, and royalty-free license to collect, analyze and use Operational Metrics relating to its delivery of the Gathr Platform that are derived from, or related to, Customer Data, including the generation of reports for internal, external, and public use, and to use Operational Metrics for Gathr’ internal business purposes. Gathr may only publicly distribute Operational Metrics in aggregate, non-personally identifiable form that cannot be used to identify Customer or any individual Authorized User.
Operational Metrics. The Vendor and the City technical staffs shall reach agreement on operational metrics and document these metrics in the Agreement or elsewhere in writing. Examples include, but are not limited to:
Operational Metrics
