Contractor Software Version Upgrades, Software Revisions and Patches Sample Clauses

Contractor Software Version Upgrades, Software Revisions and Patches. Contractor shall provide and implement ALL SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches to ensure: (a) the functionality of the SaaS Software and SaaS Services, as described in the Documentation, is available to Authorized Users; (b) the functionality of the SaaS Software and SaaS Services in accordance with the representations and warranties set forth herein, including but not limited to, the SaaS Software and SaaS Services conforming in all material respects to the specifications, functions, descriptions, standards, and criteria set forth in the Documentation; (c) the Service Level Standards can be achieved; and,
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
Contractor Software Version Upgrades, Software Revisions and Patches. Contractor shall provide and implement ALL SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software Patches to ensure: (a) the functionality of the SaaS Software and SaaS Services, as described in the Documentation, is available to Authorized Users; (b) the functionality of the SaaS Software and SaaS Services in accordance with the representations and warranties set forth herein, including but not limited to, the SaaS Software and SaaS Services conforming in all material respects to the specifications, functions, descriptions, standards, and criteria set forth in the Documentation; (c) the Service Level Standards can be achieved; and, (d) the SaaS Software and SaaS Services work with the non- hosted browser version. i. Deployment of these revisions will be mutually agreed upon between Contractor and City. ii. Release of software revisions as defined will be conducted on a schedule as determined by Contractor. Contractor shall provide no less than a thirty (30) calendar day prior written notice of when any such revision is scheduled to be released. City will be granted a fifteen (15) calendar day evaluation window to review release documentation regarding software modules being impacted and general revision changes. iii. After the evaluation period, Contractor will conduct a deployment of the revision to the City Test Environment. The software deployment will be scheduled in writing five (5) calendar days prior to actual deployment activities. As part of the upgrade activities within the Test Environment, Contractor may provide nominal testing to ensure all systems are functional and the revision deployment was successful. Post deployment activities include an e-mail or portal post to serve as written notification that this service has been completed. City will be allowed a forty-five (45) calendar day test window in which City has ability to test and raise issues with Contractor. Issue resolution will be managed per the process as described here within. Test Environment deployment activities will be conducted during a mutual agreed to time window and may not necessarily align with the production maintenance windows as described within this document. iv. In the event a SaaS Severity Level 1 or Severity Level 2 Issue has been identified and appropriately triaged and classified by both Contractor and City during the Test Environment deployment test window, Contractor will be required to correct the SaaS Issue. If the SaaS Issue can be correct...
Sample 1Sample 2
Contractor Software Version Upgrades, Software Revisions and Patches. Contractor shall provide and implement ALL SaaS Software Version upgrades, SaaS Software Revisions and SaaS Software patches to ensure: (a) that the functionality of the SaaS Application and SaaS Services, as described in the Documentation, is available to Authorized Users; (b) that the functionality of the SaaS Application and SaaS Services is in accordance with the representations and warranties set forth herein, including but not limited to, the SaaS Application and SaaS Services conforming in all material respects to the specifications, functions, descriptions, standards, and criteria set forth in the Documentation; (c) that the Service Level Standards can be achieved; and (d) that the SaaS Application and SaaS Services work with the non-hosted browser version. Any Authorized User may opt into Contractor’s “Early Access Group” to test and review SaaS Software Version upgrades, SaaS Software Revisions, and SaaS Software patches before they are deployed to all users.
Sample 1
Contractor Software Version Upgrades, Software Revisions and Patches. Contractor shall provide and implement all SaaS Application(s) version upgrades, SaaS Application(s) revisions and SaaS Application(s) patches to ensure: (a) that the functionality of the SaaS Application(s), as described in the Documentation, is available to Authorized Users; (b) that the functionality of the SaaS Application(s) is in accordance with the representations and warranties set forth herein, including but not limited to, the SaaS Application(s) conforming in all material respects to the specifications, functions, descriptions, standards, and criteria set forth in the Documentation; and (c) that the service level standards can be achieved. i. Planing: Contractor must assist the City with the planning and logistics of upgrades and updates.
Sample 1

Related to Contractor Software Version Upgrades, Software Revisions and Patches

  • 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.

  • Antivirus software All workstations, laptops and other systems that process and/or store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY must have installed and actively use comprehensive anti-virus software solution with automatic updates scheduled at least daily.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Embedded Software To the extent any goods contain Embedded Software (defined below) that is not Buyer’s Property, no title to such Embedded Software shall pass to Buyer, and Supplier shall grant Buyer, its customers and all other users a non-exclusive worldwide, irrevocable, perpetual, royalty-free right to use, load, install, execute, demonstrate, market, test, resell, sublicense and distribute such Embedded Software as an integral part of such goods or for servicing the goods (the “Buyer-Required License”). If such Embedded Software or any part thereof is owned by a third party, prior to delivery, Supplier shall obtain the Buyer-Required License from such third-party owner. “Embedded Software” means software necessary for operation of goods and embedded in and delivered as an integral part of goods.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • 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.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements.

  • Technology Upgrades Notwithstanding any other provision of this Agreement, Verizon shall have the right to deploy, upgrade, migrate and maintain its network at its discretion. The Parties acknowledge that Verizon, at its election, may deploy fiber throughout its network and that such fiber deployment may inhibit or facilitate PNG’s ability to provide service using certain technologies. Nothing in this Agreement shall limit Verizon's ability to modify its network through the incorporation of new equipment or software or otherwise. PNG shall be solely responsible for the cost and activities associated with accommodating such changes in its own network.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • 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.

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