Country-Specific Provisions Argentina
Specific Provisions 4.1 Unless the CERT otherwise agrees, based on exceptional circumstance and sufficient justification, Implementing Agreements shall be for an initial term of up to, but no more than, five years.
4.2 An Implementing Agreement may be extended for such additional periods as may be determined by its Executive Committee, subject to approval of the CERT. Any single extension period shall not be greater than five years unless the CERT otherwise decides, based on exceptional circumstances and sufficient justification.
4.3 Notwithstanding Paragraph 4.2, should the duration of the programme of work of an Annex exceed the term of the Implementing Agreement to which it relates, the CERT shall not unreasonably withhold approval to extend the Implementing Agreement for such additional period to permit the conclusion of the work then being conducted under the Annex.
4.4 Either the Contracting Parties or the Executive Committee of each Implementing Agreement shall:
4.4.1 approve the programme activities and the annual programme of work and budget for the relevant Implementing Agreement;
4.4.2 establish the terms of the contribution for scientific and technical information, know-how and studies, manpower, capital investment or other forms of financing to be provided by each participant in the Implementing Agreement;
4.4.3 establish the necessary provisions on information and intellectual property and ensure the protection of IEA copyrights, logos and other intellectual property rights as established by the IEA;
4.4.4 assign the responsibility for the operational management of the programme or project to an entity accountable to the Executive Committee of the relevant Implementing Agreement;
4.4.5 establish the initial term of the Implementing Agreement and its Annexes;
4.4.6 approve amendments to the text of the Implementing Agreement and Annexes; and
4.4.7 invite a representative of the IEA Secretariat to its Executive Committee meetings in an advisory capacity and, sufficiently in advance of the meeting, provide the Secretariat with all documentation made available to the Executive Committee members for purposes of the meeting.
Specific Provision The grievant shall cite on the grievance form the specific article(s) and/or section(s) or combination thereof that the grievant alleges to have been violated. Failure to cite said provision(s) shall relieve the Employer of any obligation to process the grievance.
State Specific Provisions N/A. ATTACHED EXHIBIT. The Exhibit noted below, if marked with an "X" in the space provided, is attached to this Note: X Exhibit A Modifications to Multifamily Note
License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.
of the Technical Provisions The Project Schedule shall be used by the Parties for planning and monitoring the progress of the Work and as the basis for determining the amount of monthly progress payments to be made to DB Contractor.
Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.
Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.
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.
