PROJECT TASK ORDER Sample Clauses

PROJECT TASK ORDER. The terms and conditions of this Master Agreement apply to each project for which Consultant is selected by State to provide Services. Consultant will provide Services for State projects under this Master Agreement via a Task Order Agreement between State and Consultant. The Task Order will include provisions substantially similar to this Master Agreement, with any necessary amendments or additions thereto, and will describe and establish the fee for the specific project to be completed. New Task Orders may only be issued until the expiration of the term of this Master Agreement. The Master Agreement will remain in full force and effect for the duration of any Task Order issued under this Master Agreement. It is expected that the Task Orders will include, but not be limited to, the identical or similar language as included in Exhibit “<T-EXH-4-TO>”, which is attached and incorporated herein by this reference.
Sample 1
AutoNDA by SimpleDocs
PROJECT TASK ORDER. The terms and conditions of this Master Agreement apply to each project for which Consultant is selected by LPA, or State on behalf of LPA, to provide Services. Consultant will provide Services for individual LPA projects under this Master Agreement via a Task Order Agreement between LPA and Consultant. The Task Order will include provisions substantially similar to this Master Agreement, with any necessary amendments or additions thereto, and will describe and establish the fee for the specific project to be completed. New Task Orders may only be issued until the expiration of the term of this Master Agreement. The Master Agreement will remain in full force and effect for the duration of any Task Order issued under this Master Agreement. It is expected that the Task Orders will include, but not be limited to, the identical or similar language as included in Exhibit “<T-EXH-A CE MA>”, which is attached and incorporated herein by this reference.
Sample 1
PROJECT TASK ORDER. The terms and conditions of this Master Agreement apply to each project for which Consultant is selected by State, LPA, or State on LPA’s behalf to provide Services. Consultant will provide Services for individual State <Recreation Road> or LPA projects under this Master Agreement via a Task Order Agreement between State or LPA and Consultant. The Task Order will include provisions substantially similar to this Master Agreement, with any necessary amendments or additions thereto, and will describe and establish the fee for the specific project to be completed. New Task Orders may only be issued until the expiration of the term of this Master Agreement. The Master Agreement will remain in full force and effect for the duration of any Task Order issued under this Master Agreement. It is expected that the Task Orders will include, but not be limited to, the identical or similar language as included in Exhibit “<T-EXH-4-TO>”, which is attached and incorporated herein by this reference.
Sample 1
PROJECT TASK ORDER. The terms and conditions of this Master Agreement shall apply to each project for which the Consultant is selected by an LPA to provide Services. Each project the Consultant provides Services for an LPA hereunder shall be initiated by a “Task Order.” Each properly executed Task Order will result in an agreement between an LPA and Consultant incorporating the terms of this Master Agreement.
Sample 1
PROJECT TASK ORDER. For each proposed Project, JOL will submit to Cadista a Technology Transfer Document (each a “TTD”) containing data with respect to such proposed Project. The specific details of each Project that is ultimately agreed upon between JOL and Cadista shall be separately negotiated and specified in writing on terms and in form acceptable to each of JOL and Cadista (each such writing, a “Project Task Order”). Each Project Task Order will cover the applicable categories of services set forth in the sample Project Task Order template that is attached hereto as Exhibit A, and will include (among other things), as appropriate, information concerning the Product Candidate(s) and its strength(s), the scope of the Cadista Services (as defined in Section 2 below), timeline and explanation of fees and costs payable therefor.
Sample 1
PROJECT TASK ORDER. 1.1 This Agreement shall apply to as many projects as OWNER and ENGINEER agree will be performed under the terms and conditions of this Agreement. Each project ENGINEER performs for OWNER hereunder shall be designated by a “Task Order.” A sample Task Order is attached to this Agreement and marked as Exhibit “A”. No Task Order shall be binding or enforceable unless and until it has been properly executed by both OWNER and ENGINEER. Each properly executed Task Order shall become a separate supplemental agreement to this Agreement.
Sample 1

Related to PROJECT TASK ORDER

  • Task Order X19.5 The Contractor submits a Task Order programme to the Service Manager within 2 days of receiving the Task Order Z The additional conditions of contract are Z1 to Z11 always apply. Z1 Cession delegation and assignment

  • 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.

  • Work Order (s) means a detailed scope of work for a Service required by Transnet, including timeframes, Deliverable, Fees and costs for the supply of the Service to Transnet, which may be appended to this Agreement from time to time.

  • Task Orders All orders issued hereunder are subject to the terms and conditions of this contract. The contract shall control in the event of conflict with any order. When mailed, an order shall be "issued" for purposes of this contract at the time the Government deposits the order in the mail, or, if transmitted by other means, when physically delivered to the contractor.

  • Project Timeline The Project Timeline establishes a start and end date for each Phase of the Project. Developed during the Initiate & Plan Stage and revised as mutually agreed to, if needed, the timeline accounts for resource availability, business goals, size and complexity of the Project, and task duration requirements.

  • 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.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Milestone Schedule Please state the status and progress of each Milestone and identify any completed Milestone(s) for the previous calendar quarter.

Time is Money Join Law Insider Premium to draft better contracts faster.