Watcher Utilization Data Sample Clauses

Watcher Utilization Data. As of version 9.2 onward of the Cloudshell Software, the CloudShell Software will include an additional service (''CloudShell Watcher'') collecting CloudShell utilization information including information regarding your CloudShell reservations (''Sandboxes'') such as max concurrent Sandboxes per day, total Sandboxes started per day, number of unique uses per day, number of public Blueprints, number of Blueprints with active Sandbox per day - this general aggregate information is kept in a secure and protected manner and is not related to any specific CloudShell user or person. This data being collected collects no personal information, no customer password information, personal information or information regarding any of your content and is being sent online to QualiSystems (''Watcher Utilization Data''). The Watcher Utilization Data is saved locally to the CloudShell server machine (''CloudShell Server''). For the purpose of collection of the Watcher Utilization Data the CloudShell Server will send, periodically, via internet connection, the Watcher Utilization Data to QualiSystems’s dedicated storage located on the Cloud , in a secured, anonymized and encrypted manner. You hereby confirm that you are aware that, and provide your full consent to have the Watcher Utilization Data on the CloudShell Server sent to QualiSystems as detailed above. QualiSystems shall be entitled to make use of such Watcher Utilization Data for and in order to enhance your usage of the Software including by offering optimization of your utilization of the Software as well as assistance in monitoring of the Software for possible malfunctions and the ongoing improvement of our products, and Your use abilities and subject to our current Privacy Policy. For the purpose of possible malfunctions detection, locally stored Watcher Utilization Data will also be collected by QualiSystems during Service or Support request relating to the Software. The Watcher Utilization Data will be collected by the CloudShell monitor (which is already inherent part of CloudShell). The CloudShell monitor should be executed on the CloudShell Sever and then the Watcher Utilization Data will be packed together with the logs (which are collected by the monitor).
AutoNDA by SimpleDocs

Related to Watcher Utilization Data

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.

  • Utilization Utilization shall be defined as Trunks Required as a percentage of Trunks In Service. 1 During implementation the Parties will mutually agree on an Economic Centum Call Seconds (ECCS) or some other means for the sizing of this trunk group. 4.6.3.1 In A Blocking Situation (Over-utilization): 4.6.3.1.1 In a blocking situation, CLEC is responsible for issuing ASRs on all two-way Local Only, Local Interconnection, Third Party and Meet Point Trunk Groups and one-way CLEC originating Local Only and/or Local Interconnection Trunk Groups to reduce measured blocking to design objective blocking levels based on analysis of trunk group data. If an ASR is not issued, AT&T-21STATE will issue a TGSR. CLEC will issue an ASR within three (3) business days after receipt and review of the TGSR. CLEC will note “Service Affecting” on the ASR. 4.6.3.1.2 In a blocking situation, AT&T-21STATE is responsible for issuing ASRs on one-way AT&T-21STATE originating Local Only and/or Local Interconnection Trunk Groups to reduce measured blocking to design objective blocking levels based on analysis of trunk group data. If an ASR is not issued, CLEC will issue a TGSR. AT&T- 21STATE will issue an ASR within three (3) business days after receipt and review of the TGSR. 4.6.3.1.3 If an alternate final Local Only Trunk Group or Local Interconnection Trunk Group is at seventy-five percent (75%) utilization, a TGSR may be sent to CLEC for the final trunk group and all subtending high usage trunk groups that are contributing any amount of overflow to the alternate final route. 4.6.3.1.4 If a direct final Meet Point Trunk Group is at seventy-five percent (75%) utilization, a TGSR may be sent to CLEC. If a direct final Third Party Trunk Group is at ninety percent (90%) utilization, a TGSR may be sent to CLEC.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • MWBE Utilization Plan A. In accordance with 5 NYCRR § 142.4, Bidders are required to submit a completed Utilization Plan on Form MWBE 100 with their bid. B. The Utilization Plan shall list the MWBEs the Bidder intends to use to perform the Contract, a description of the Contract scope of work the Bidder intends the MWBE to perform to meet the goals on the Contract, and the estimated or, if known, actual dollar amounts to be paid to an MWBE. By signing the Utilization Plan, the Bidder acknowledges that making false representations or including information evidencing a lack of good faith as part of, or in conjunction with, the submission of a Utilization Plan is prohibited by law and may result in penalties including, but not limited to, termination of a contract for cause, loss of eligibility to submit future bids, and/or withholding of payments. Any modifications or changes to the agreed participation by New York State Certified MWBEs after the Contract award and during the term of the Contract must be reported on a revised MWBE Utilization Plan and submitted to OGS. C. By entering into the Contract, Bidder/Contractor understands that only sums paid to MWBEs for the performance of a commercially useful function, as that term is defined in 5 NYCRR § 140.1, may be applied towards the achievement of the applicable MWBE participation goal. When an MWBE is serving as a broker on the Contract, only 25 percent of all sums paid to a broker shall be deemed to represent the commercially useful function performed by the MWBE. D. OGS will review the submitted MWBE Utilization Plan and advise the Bidder of OGS acceptance or issue a notice of deficiency within 30 days of receipt. E. If a notice of deficiency is issued; Bidder agrees that it shall respond to the notice of deficiency, within 7 business days of receipt, by submitting to OGS a written remedy in response to the notice of deficiency. If the written remedy that is submitted is not timely or is found by OGS to be inadequate, OGS shall notify the Bidder and direct the Bidder to submit, within 5 business days of notification by OGS, a request for a partial or total waiver of MWBE participation goals on Form BDC 333. Failure to file the waiver form in a timely manner may be grounds for disqualification of the bid or proposal. F. OGS may disqualify a Vendors Submission as being non-responsive under the following circumstances: (a) If a Bidder fails to submit an MWBE Utilization Plan; (b) If a Bidder fails to submit a written remedy to a notice of deficiency; (c) If a Bidder fails to submit a request for waiver; or (d) If OGS determines that the Bidder has failed to document good faith efforts. G. If awarded a Contract, Contractor certifies that it will follow the submitted MWBE Utilization Plan for the performance of MWBEs on the Contract pursuant to the prescribed MWBE goals set forth in clause IV-A of this Section. H. Bidder/Contractor further agrees that a failure to submit and/or use such completed MWBE Utilization Plan shall constitute a material breach of the terms of the Contract. Upon the occurrence of such a material breach, OGS shall be entitled to any remedy provided herein, including but not limited to, a finding of Contractor non- responsiveness.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

  • Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Utilization Management Contractor shall maintain a utilization management program that complies with applicable laws, rules and regulations, including Health and Safety Code § 1367.01 and other requirements established by the applicable State Regulators responsible for oversight of Contractor.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!