Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving the following development milestones in its diligence activities under this AGREEMENT: (a) (b).
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.
Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.
Development Milestone Payments In partial consideration for the rights and licenses granted to Coya hereunder, within ten days after the first achievement of each milestone event in a given Indication set forth in this Section 5.2 (Development Milestone Payments) with respect to a Product (each, a “Development Milestone Event”) by or on behalf of Coya or any of its Affiliates or Sublicensees, Coya shall provide ARScience Bio written notice to ARScience Bio identifying the Development Milestone Event achieved. Upon receipt of any such notice of first achievement of a Development Milestone Event by Coya or its Affiliates or Sublicensees, ARScience Bio will promptly invoice Coya for the applicable Development Milestone Event and Coya will make a milestone payment to ARScience Bio in the amount set forth in this Section 5.2 (Development Milestone Payments) corresponding to such Development Milestone Event (each, a “Development Milestone Payment”) within 45 days of receipt of such invoice. On an Indication-by-Indication basis, each Development Milestone Payment shall be payable only upon the first achievement of the corresponding Development Milestone Event by a Product, in any given Indication for which the Development Milestone Events have not been previously achieved (each such Indication, a “New Indication”). No amounts shall be due for subsequent or repeated achievements of such Development Milestone Event with respect to the same or different Mono Product or Combination Product, as applicable, in such Indication. Accordingly and for clarity, the Development Milestone Payment shall be paid only once, when first achieved by Coya, an Affiliate or a Sublicensee, but no payment shall be due if the same milestone is subsequently achieved by one of Coya, an Affiliate or a Sublicensee. For clarity, the amounts owed in Column (a) below shall be due for the first Combination Product to achieve the Development Milestone Events in a New Indication and the amounts owned in Column (c) below shall be due for the first Mono Product to achieve the Development Milestone Events in a New Indication. Any Combination Product or Mono Product to achieve the Development Milestone Events in a New Indication after the first achievement of the Development Milestone Events as described in the foregoing sentence will cause the amounts in Column (b) with respect to a Combination Product and Column (d) with respect to a Mono Product to be due and payable by Coya upon each such occurrence. If the first Product to achieve a Development Milestone Event in any Indication is a Combination Product, the amounts in Column (a) below shall be due and payable by Coya. If the next Product to achieve a Development Milestone Event in a New Indication is a Mono Product, the amounts in Column (c) below would be due and payable by Coya; provided, that if such next Product to achieve a Development Milestone Event in a New Indication is a Combination Product, the amounts in Column (b) would be due and payable by Coya. By way of example, if a Combination Product achieves IND Acceptance in ALS, and is the first Product to achieve a Development Milestone Event under this Agreement, [***] will be due and payable by Coya. If subsequently a Mono Product achieves IND Acceptance in ALS, no Development Milestone Payments will be due and payable by Coya under this Agreement. However, if subsequently any Combination Product achieves IND Acceptance in Alzheimer’s disease, [***] would be due and payable by Coya.
Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:
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.
Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.
Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.
Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.
SCHEDULE AND MILESTONES The planned major milestones for the activities for this Annex defined in the "Responsibilities" Article are as follows:
