Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.
Multi-year Planning Targets Schedule A may reflect an allocation for the first Funding Year of this Agreement as well as planning targets for up to two additional years, consistent with the term of this Agreement. In such an event, the HSP acknowledges that if it is provided with planning targets, these targets:
a. are targets only,
b. are provided solely for the purposes of planning,
c. are subject to confirmation, and
d. may be changed at the discretion of the Funder in consultation with the HSP. The HSP will proactively manage the risks associated with multi-year planning and the potential changes to the planning targets; and the Funder agrees that it will communicate any changes to the planning targets as soon as reasonably possible.
For clarity the time allowances provided in clause 2.10 shall operate to reduce the maximum timetabled classroom teaching time specified in clause 4.2 of this agreement.
Geographic Area and Sector Specific Allowances, Conditions and Exceptions The following allowances and conditions shall apply where relevant. Where the Employer does work which falls under the following headings, the Employer agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.
License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license.
(b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement.
(c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement.
(d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.
(e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.
Presentation of Potential Target Businesses The Company shall cause each of the Initial Shareholders to agree that, in order to minimize potential conflicts of interest which may arise from multiple affiliations, the Initial Shareholders will present to the Company for its consideration, prior to presentation to any other person or company, any suitable opportunity to acquire an operating business, until the earlier of the consummation by the Company of a Business Combination or the liquidation of the Company, subject to any pre-existing fiduciary obligations the Initial Shareholders might have.
Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.
Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.
a. The contractor shall notify all potential subcontractors and suppliers and lessors of their EEO obligations under this contract.
b. The contractor will use good faith efforts to ensure subcontractor compliance with their EEO obligations.
Research Program The term “Research Program” shall mean the research program to be undertaken by TSRI under the direction and control of the Principal Investigator as expressly set forth on Exhibit A hereto.
Third Party Components The Products and Services may contain third party components (including open source software) subject to separate license agreements. To the limited extent a third party license expressly supersedes this XXXX, such third party license governs Customer’s use of that third party component.
