Software Support During the Term, Seller shall use commercially reasonable efforts to provide all Software updates and qualified Software upgrades in accordance with the terms of the Service Contract as such materials become commercially available for distribution. Purchaser’s use of all Software, updates, and upgrades of Software shall be subject to this Agreement, the Original Terms, and the applicable XXXX.
Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.
Service Level Agreement 6.1 NCR Voyix will use commercially reasonable efforts to make the Service available to you at or above the Availability Rate set forth at xxxxx://xxx.xxx.xxx/support/aloha-sla. If NCR Voyix does not meet the Availability Rate, you are entitled to request a service-level credit subject to the terms of this Agreement. This credit is calculated as a percentage of the monthly recurring bill (or monthly pro rata share of billing, if billing does not occur monthly) for the Service for the month in which the Availability Rate was not met. The Availability Rate is determined by: (a) dividing the total number of valid outage minutes in a calendar month by the total number of minutes in that month; (b) subtracting that quotient from 1.00; (c) multiplying that difference by 100; and (d) rounding that result to two decimal places in accordance with standard rounding conventions. The number of outage minutes per day for a given service is determined by the lesser of the number of outage minutes.
6.2 Unavailability due to other conditions or caused by factors outside of NCR Voyix’s reasonable control will not be included in the calculation of the Availability Rate. Further, the following are expressly excluded from the calculation of the Availability Rate: (a) service unavailability affecting services or application program interfaces that are not used by you; (b) cases where fail-over to another data center is available but not utilized; (c) transient time-outs, required re-tries, or slower-than-normal response caused by factors outside of NCR Voyix’s reasonable control; (d) Scheduled Downtime, including maintenance and upgrades; (e) force majeure; (f) transmission or communications outages outside the NCR Voyix- controlled environment; (g) store-level down-time caused by factors outside of NCR Voyix’s reasonable control; (h) outages attributable to services, hardware, or software not provided by NCR Voyix, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services;
(i) use of the Service in a manner inconsistent with the documentation for the application program interface or the NCR Voyix Product; (j) your Point of Sale (“POS”) failure or the failure to properly maintain the POS environment, including updating the POS firmware or version of the software running on the POS as recommended by either NCR Voyix, a third-party POS reseller or servicer; and (k) issues related to third party domain name system (“DNS”) errors or failures.
6.3 To obtain a service-level credit, you must submit a claim by contacting NCR Voyix through the website at xxxxx://xxx.xxx.xxx/support/aloha-sla Your failure to provide the claim and other information will disqualify you from receiving a credit. NCR Voyix must receive claims within 60 days from the last day of the impacted month. After that date, claims are considered waived and will be refused. You must be in compliance with the Agreement in order to be eligible for a service-level credit. You may not unilaterally offset for any performance or availability issues any amount owed to NCR Voyix. If multiple Services experience an outage in a given month, the total credit for that month will be the highest credit allowed for any single Service which failed; there is no stacking of credits.
6.4 The remedies set forth in the Section are your sole and exclusive remedies for performance or availability issues affecting the Services, including any failure by NCR Voyix to achieve the Availability Rate.
Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA):
(a) we are liable for any remedy or rebate specified by the SLA; and
(b) subject to clauses 40 to 42, and to the express terms of the SLA, our liability for breach of the SLA is limited to such remedy or rebate.
Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.
(b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program.
(c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only.
(d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use.
(e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient.
(f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor.
(g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient.
(h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes.
(i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5.
(j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.
Research Support (a) Having regard to the resources reasonably available for such purposes, the Operator will cooperate with AHS to provide such participation by its Staff as may be reasonable in relation to the carrying out of research within the Province.
(b) The Operator agrees to promptly notify AHS in the event that it undertakes or agrees to participate in any form of clinical trial, research project, instrument use, or similar activity which in any way relates to the Services provided under this Agreement. The Operator shall, upon request, provide AHS with written evidence of Client disclosure and consent to research.
Compliance Support Services Provide compliance policies and procedures related to services provided by BNY Mellon and, if mutually agreed, certain of the BNY Mellon Affiliates; summary procedures thereof; and periodic certification letters. · Such Compliance Support Services are administrative in nature and do not constitute, nor shall they be construed as constituting, legal advice or the provision of legal services for or on behalf of a Fund or any other person, and such services are subject to review and approval by the applicable Fund and by the Fund’s legal counsel. · Provide access to Fund records so as to permit the Fund or TRP to test the performance of BNY Mellon in providing the services under this Agreement. · Such Compliance Support Services performed by BNY Mellon under this Agreement shall be at the request and direction of the Fund and/or its chief compliance officer (the “Fund’s CCO”), as applicable. BNY Mellon disclaims liability to the Fund, and the Fund is solely responsible, for the selection, qualifications and performance of the Fund’s CCO and the adequacy and effectiveness of the Fund’s compliance program.
Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.
Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.
Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").
