Subscription License A Subscription license will commence on the date specified in the Notification Form and continue in force for the fixed initial term specified therein. The license is firm and cannot be cancelled or otherwise reduced or terminated by Customer during the license term. On expiry of the initial term, the subscription license will terminate unless renewed. Unless otherwise stated in the applicable Notification Form, each subscription license will include the provision of Support Services.
Software Subscription Use Case Red Hat Storage Server for On- Premise Red Hat Storage Server for On-Premise is intended to be used as a storage system and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non- server hardware such as desktops or workstations. Red Hat Storage Server for On-Premise is intended for use on a dedicated System, Physical Node, Virtual Node or Virtual Guest; running other applications and/or programs of any type on the System, Physical Node, Virtual Node or Virtual Guest can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage Server for Public Cloud Red Hat Storage Server for Public Cloud is intended to be used as a storage system and will be supported only when used as a storage node. When running in Amazon Web Services, an EC2 M1 Large dedicated instance is required in order to be supported. Running other applications and/or programs of any type on the same instance can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server. Red Hat Storage for Red Hat Enterprise Linux OpenStack Platform Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended to be used as a storage system with Red Hat Enterprise Linux OpenStack Platform and will be supported only when used as a storage node. Red Hat Storage Server is not supported on non-server hardware such as desktops or workstations. Red Hat Storage Server for Red Hat Enterprise Linux OpenStack Platform is intended for use on a dedicated Physical Node; running other applications and/or programs of any type on the Physical Node can have a negative impact on the function and/or performance of the Red Hat Storage Server and is not a supported Use Case. Each Red Hat Storage Server Subscription includes one Software Subscription to Red Hat Enterprise Linux Server and the Scalable File System Add-on, which are supported solely in connection with the use of Red Hat Storage Server.
SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.
Commercialization License Subject to the terms of this Agreement, including without limitation Section 2.2 and Theravance's Co-Promotion rights in Section 5.3.2, Theravance hereby grants to GSK, and GSK accepts, an exclusive license under the Theravance Patents and Theravance Know-How to make, have made, use, sell, offer for sale and import Alliance Products in the Territory.
COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.
Development Milestone Payments Pfizer shall make the payments set forth below within [**] days (or [**] days after [**] following the first occurrence of each event described below for a Licensed Product Covered by a Valid Claim that achieves such milestone (each event a “Development Milestone” and each payment a “Development Milestone Payment”). Development Milestone Development Milestone Payment [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**] [**]. The Development Milestone Payment in clause (2) of this Section 3.3 may become payable as set forth in Section 4.6. Whether or not the Development Milestone in clause (2) of this Section 3.3 is achieved, the Development Milestone Payment in clause (2) shall, pursuant to Section 4.6, in all cases become payable prior to the time the Development Milestone Payment in clause (3) of this Section 3.3 becomes payable. With respect to the Development Milestone in clause (3) of this Section 3.3, in the case of a [**] that is determined to have become [**], such Development Milestone, if achieved based on such [**], shall be achieved upon [**]; provided, however, if either [**], such Development Milestone shall be deemed to have been met on the date of such determination. With respect to the Development Milestone in clause (8) of this Section 3.3, such Development Milestone will be paid in [**], provided that if such Licensed Product [**]. (For the avoidance of doubt, all payment [**] that became payable prior to such [**] shall continue to be payable and there shall be [**] of the [**] Development Milestone Payment will be deemed to have been achieved and payable on [**], and will be paid by Pfizer within [**] days thereafter, until the earlier of [**]. For example, [**] of such Development Milestone, such Development Milestone Payment would be paid [**] of the Development Milestone [**]. For the avoidance of doubt: (a) except for (i) the Development Milestone Payment set forth in clause (6) of this Section 3.3 [**], (ii) the Development Milestone Payment set forth in clause (8) of this Section 3.3 [**] and (iii) the Development Milestone Payment set forth in clause (9) of this Section 3.3 [**], each Development Milestone Payment shall be payable only once upon achievement of the applicable Development Milestone and only on the first occurrence of the corresponding Development Milestone regardless of the number of Licensed Products and (b) satisfaction of a Development Milestone by an Affiliate or by a sublicensee or assignee of, or Third Party retained by, Pfizer or its Affiliates shall be deemed to have been satisfied by Pfizer for the purposes of this Section 3.3.
User Subscriptions 2.1. Subject to the Customer purchasing the User Subscriptions in accordance with clause 3.3 and clause 8.1, the restrictions set out in this clause 2 and the other terms and conditions of this agreement, the Supplier hereby grants to the Customer a non- exclusive, non-transferable right, without the right to grant sublicenses, to permit the Authorised Users to use the Services and the Service Definition Document during the Subscription Term solely for the Customer's internal business operations.
2.2. In relation to the Authorised Users, the Customer undertakes that:
2.2.1. the maximum number of Authorised Users that it authorises to access and use the Services and the Service Definition Document shall not exceed the number of User Subscriptions it has purchased from time to time;
2.2.2. it will not allow or suffer any User Subscription to be used by more than one individual Authorised User unless it has been reassigned in its entirety to another individual Authorised User, in which case the prior Authorised User shall no longer have any right to access or use the Services and/or the Service Definition Document;
2.2.3. each Authorised User shall keep a secure password for his use of the Services, that such password shall be changed no less frequently than monthly and that each Authorised User shall keep his password confidential;
2.2.4. it shall maintain a written, up to date list of current Authorised Users and provide such list to the Supplier within 5 Business Days of the Supplier's written request at any time or times;
2.2.5. it shall permit the Supplier to audit the Services in order to establish the name and password of each Authorised User. Such audit may be conducted no more than once per quarter, at the Supplier's expense, and this right shall be exercised with reasonable prior notice, in such a manner as not to substantially interfere with the Customer's normal conduct of business;
2.2.6. if any of the audits referred to in clause 2.2.5 reveal that any password has been provided to any individual who is not an Authorised User, then without prejudice to the Supplier's other rights, the Customer shall promptly disable such passwords and the Supplier shall not issue any new passwords to any such individual; and
2.2.7. if any of the audits referred to in clause 2.2.5 reveal that the Customer has underpaid Subscription Fees to the Supplier, then without prejudice to the Supplier's other rights, the Customer shall pay to the Supplier an amount equal to such underpayment as calculated in accordance with the prices set out in Schedule 1 within 10 Business Days of the date of the relevant audit.
2.3. The Customer shall not access, store, distribute or transmit any Viruses, or any material during the course of its use of the Services that:
2.3.1. is unlawful, harmful, threatening, defamatory, obscene, infringing, harassing or racially or ethnically offensive;
2.3.2. facilitates illegal activity;
2.3.3. depicts sexually explicit images;
2.3.4. promotes unlawful violence;
2.3.5. is discriminatory based on race, gender, colour, religious belief, sexual orientation, disability; or
2.3.6. is otherwise illegal or causes damage or injury to any person or property; and the Supplier reserves the right, without liability or prejudice to its other rights to the Customer, to disable the Customer's access to any material that breaches the provisions of this clause.
2.4. The Customer shall not:
2.4.1. except as may be allowed by any applicable law which is incapable of exclusion by agreement between the parties and except to the extent expressly permitted under this agreement:
i. attempt to copy, modify, duplicate, create derivative works from, frame, mirror, republish, download, display, transmit, or distribute all or any portion of the Software and/or the Service Definition Document (as applicable) in any form or media or by any means; or
ii. attempt to de-compile, reverse compile, disassemble, reverse engineer or otherwise reduce to human-perceivable form all or any part of the Software; or
2.4.2. access all or any part of the Services and the Service Definition Document in order to build a product or service which competes with the Services and/or the Service Definition Document; or
2.4.3. use the Services and/or the Service Definition Document to provide services to third parties; or
2.4.4. subject to clause 21.1, license, sell, rent, lease, transfer, assign, distribute, display, disclose, or otherwise commercially exploit, or otherwise make the Services and/or the Service Definition Document available to any third party except the Authorised Users; or
2.4.5. attempt to obtain, or assist third parties in obtaining, access to the Services and/or the Service Definition Document, other than as provided under this clause 2.
2.5. The Customer shall use all reasonable endeavours to prevent any unauthorised access to, or use of, the Services and/or the Service Definition Document and, in the event of any such unauthorised access or use, promptly notify the Supplier.
2.6. The rights provided under this clause 2 are granted to the Customer only, and shall not be considered granted to any subsidiary or holding company of the Customer[DRAFTING NOTE: use the following wording where the client is a public sector body:[, nor to any Contracting Authority other than the Customer]].
Subscription Period 5.1.1 The Subscription Period is binding upon both Zensai and the Customer, meaning the Customer cannot terminate the Service, the Support Services and this SAAS Agreement during a Subscription Period. Notwithstanding the above, the Customer can terminate the Subscription due to a material default in the Services, cf. Section 10.3, or if a material change to the terms and conditions of the SAAS Agreement comes into force, cf. Section 16.1, and if the Customer is not in breach of the SAAS Agreement, Zensai will refund a pro rata portion of the Subscription Fee for the remaining un- used period of the Service and Support Services.
5.1.2 The Subscription Fee for the Subscription Period is defined in the Quote. The Customer may add Users or upgrade the Service during the Subscription Period but may not downgrade the number of Users during the Subscription Period. For Support Services, the Customer may upgrade its level of Helpdesk Services during a Subscription Period, but the Customer may not downgrade to a lower service level.
5.1.3 The initial Subscription Period shall be defined in the Quote as accepted by the Customer and shall cover a minimum of 12 months. At the end of the initial term, the Subscription is subject to automatic renewal with a Subscription Period running for terms of 12 months, or longer periods if agreed in a new Quote. The Subscription Fee will be invoiced upon renewal for pre-payment. The Subscription may be changed or terminated by the Customer with a notice of no less than 60 days before renewal.
5.1.4 Zensai may terminate the SAAS Agreement by giving a notice of twelve (12) months before the end of a Subscription Period.
Subscription Term The transfer of Software Subscription(s) to Cloud Access does not change the start date or the duration of the original Software Subscription(s) and once your Software Subscription expires, your access to the Software Subscription in the Vendor’s Cloud will cease, unless otherwise renewed. You may renew your Software Subscription with Red Hat directly or an authorized partner.
Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:
