On-Premise Software System as a Service Clause Samples

The 'On-Premise Software System as a Service' clause defines the provision of software that is installed and operated on the customer's own hardware, but is delivered and managed under a service-based model. In practice, this means the vendor is responsible for maintaining, updating, and supporting the software, even though it physically resides on the customer's premises. For example, the customer may pay a recurring fee for access to the software and related services, rather than purchasing a perpetual license. This clause addresses the need for organizations to retain control over their data and infrastructure while benefiting from the convenience and support typically associated with cloud-based software services.
On-Premise Software System as a Service. If Customer purchases an “on-premises Software System as a service,” where Equipment and software Products are installed at Customer Sites or on Customer-Provided Equipment, and such software is generally licensed on a subscription basis (i.e., as Subscription Software), then such Subscription Software will be subject to the SSA and not the EPSLA. Any (a) Equipment purchased, (b) firmware preinstalled on such Equipment, and (c) Microsoft operating system Licensed Software are subject to the EPSLA. On-premises Software Systems as a service described in this Section are provided as a service and, accordingly, do not qualify for the System Warranty. System completion, however, is determined in accordance with the provisions of Section 3 – Software System Completion below.
View SourceView Similar (4)
On-Premise Software System as a Service. If Customer purchases an “on-premises Software System as a service,” where software Products are installed at Customer Sites or on Customer-Provided Equipment, and generally licensed on a subscription basis (i.e, as Subscription Software), then such Subscription Software is subject to Section 3 of the SLA. The firmware preinstalled on Equipment included with an on-premises Software System as a service purchase, and any Microsoft operating system Licensed Software are subject to Section 2 of the SLA.
View Source
On-Premise Software System as a Service. If DIR Customer purchases an “on-premises Software System as a service,” where Equipment and software Products are installed at DIR Customer Sites or on DIR Customer-Provided Equipment, and such software is generally licensed on a subscription basis (i.e., as Subscription Software), then such Subscription Software will be subject to the SSA and not the CSA. Any (a) Equipment purchased, (b) firmware preinstalled on such Equipment, and (c) Microsoft operating system Licensed Software are subject to the CSA and its Software License Agreement exhibit. On-premises Software Systems as a service described in this Section are provided as a service and, accordingly, do not qualify for the System Warranty. System completion, however, is determined in accordance with the provisions of Section 3 – Software System Completion below.
View Source

Related to On-Premise Software System as a Service

  • Installation Services The Bitstream 2a Service includes a Standard Install as set out below (in each case to the extent that the relevant provisioning works are not already complete for the relevant Service Order).1

  • CONTINUOUS IMPROVEMENT The Supplier shall at all times during the Framework Period comply with its obligations to continually improve the Goods and/or Services and the manner in which it provides the Goods and/or Services as set out in Framework Schedule 12 (Continuous Improvement and Benchmarking).

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.