Upgrades; End of Support Sample Clauses

Upgrades; End of Support. ▇▇▇▇▇▇+Gyr and Customer will mutually agree on an Upgrade schedule for Cloud Software. Services include at least one (1) Cloud Software Upgrade per calendar year. Customer agrees to remain on a Supported Release of Cloud Software. Cloud Software DOES NOT INCLUDE any application or tools software running on local Customer computers or other Customer equipment. Customer acknowledges that new features may be added to the SaaS Services based on market demand and technological innovation. Accordingly, as ▇▇▇▇▇▇+Gyr develops enhanced versions of the SaaS Service, ▇▇▇▇▇▇+Gyr may cease to maintain and support older versions of the Cloud Software (“EOS). ▇▇▇▇▇▇+Gyr will use commercially reasonable efforts to provide Support Services with respect to older version of the Cloud Software that may accompany the SaaS Service. ▇▇▇▇▇▇+Gyr shall have no obligation to support Cloud Software outside of ▇▇▇▇▇▇+Gyr’s stated EOS policy for the applicable Cloud Software. Such EOS policies shall be made available to Customer either in the accompanying Documentation or upon request and are subject to update from time to time in ▇▇▇▇▇▇+Gyr’s reasonable discretion with no less than a twelve (12) month EOS notification period.
View SourceView Similar (2)

Related to Upgrades; End of Support

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

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

  • System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the ISO OATT.

  • DISCONNECTION OF SUPPLY 14.1 When can we arrange for disconnection? (a) you do not pay your bill by the pay-by date and, if you are a residential customer, you: (i) fail to comply with the terms of an agreed payment plan; or (ii) do not agree to an offer to pay the bill by instalments, or having agreed, you fail to comply with the instalment arrangement; (b) you do not provide a security deposit we are entitled to require from you; or (c) you do not give access to your premises to read a meter (where relevant) for 3 consecutive meter reads; or (d) you fail to give us safe and unhindered access to the premises as required by clause 11 or any requirements under the energy laws; or (e) there has been illegal or fraudulent use of energy at your premises in breach of clause 16 of this contract; or (f) we are otherwise entitled or required to do so under the Rules or by law.

  • Customer Content As part of the Services provided under this Agreement, Customer Data will be stored and processed in the data center region specified in the applicable Ordering Document. Axway shall not access Customer Content except in response to support or technical issues where Customer provides Axway with prior Customer’s written authorization required to access such Customer Content. Axway is not responsible for unauthorized access, alteration, theft or destruction of Customer Content arising from Customer’s own or its authorized users’ actions or omissions in contravention of the Documentation. Customer’s ability to recover any lost data resulting from Axway’s misconduct is limited to restoration by Axway from the most recent back-up.