Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving (either itself or through the acts of a SUBLICENSEE) the following development milestones in its diligence activities under this AGREEMENT: (a) (b).
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.
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.
SCHEDULE AND MILESTONES The Parties shall execute one (1) Annex concurrently with this Umbrella Agreement. The initial Annex and any subsequent Annexes will be performed on the schedule and in accordance with the milestones set forth in each respective Annex.
Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-‐level domain strings across the Internet, certain top-‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.
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.
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.
PRODUCT SUBSTITUTION In the event a specified manufacturer’s Product listed in the Contract becomes unavailable or cannot be supplied by the Contractor for any reason (except as provided for in the Savings/Force Majeure Clause) a Product deemed in writing by the Commissioner to be equal to or better than the specified Product must be substituted by the Contractor at no additional cost or expense to the Authorized User. Unless otherwise specified, any substitution of Product prior to the Commissioner’s written approval may be cause for cancellation of Contract.
Development Rights The Employee agrees and declares that all proprietary information including but not limited to trade secrets, know-how, patents and other rights in connection therewith developed by or with the contribution of Employee's efforts during his employment with the Company shall be the sole property of the Company. Upon the Company's request (whenever made), Employee shall execute and assign to the Company all the rights in the proprietary information.
Parent Right to Access and Challenge Student Data The LEA shall establish reasonable procedures pursuant to which a parent, as that term is defined in 105 ILCS 10/2(g), may inspect and/or copy Student Data and/or challenge the accuracy, relevance or propriety of Student Data, pursuant to Sections 5 and 7 of ISSRA (105 ILCS 10/5; 105 ILCS 10/7) and Section 33 of SOPPA (105 ILCS 85/33). The Provider shall respond to any request by the LEA for Student Data in the possession of the Provider when Provider cooperation is required to afford a parent an opportunity to inspect and/or copy the Student Data, no later than 5 business days from the date of the request. In the event that a parent contacts the Provider directly to inspect and/or copy Student Data, the Provider shall refer the parent to the LEA, which shall follow the necessary and proper procedures regarding the requested Student Data.