Project text Sample Clauses

Project text. [This refers to the proposal after introducing the changes, if any, during the negotiation]
AutoNDA by SimpleDocs
Project text. [This refers to the proposal after introducing the changes, if any, during the negotiation between phase 0proposal submission and phase 1 – MATCH. The proposal will be integrated by the Contracting Party.] ANNEX 2 – DECLARATION OF SME STATUS SMEs CHECK LIST Organisation legal name Is your organisation engaged in (an) economic activit(y)ies1? (Yes or No) If NO, you are not an SME. If YES, go to the next set of questions. What is for your last approved accounting period: Your number of employees? (in annual working unit) Your turnover? (in €) Your annual balance sheet total? (in €) The duration (in months) of your last approved accounting period The closing date (dd/mm/yyyy) of your last approved accounting period Name and signature of the authorised legal representative Official exchange rate at the day of the closure of the accounting period (xxxx://xx.xxxxxx.xx/budget/inforeuro) If your number of employees is equal or superior to 250 persons (AWU) and your annual turnover is equal or exceeds EUR 50 million and/or your annual balance sheet total is equal or exceeds EUR 43 million, you are not an SME. If you are under all these ceilings, go to the next set of questions (1 and 2). 1 – Does your organisation meet the following situations (1/2):

Related to Project text

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

  • Project Implementation 2. The Borrower shall:

  • Project Team To accomplish Owner’s objectives, Owner intends to employ a team concept in connection with the construction of the Project. The basic roles and general responsibilities of team members are set forth in general terms below but are more fully set forth in the Design Professional Contract with respect to the Design Professional, in the Program Management Agreement with any Program Manager, and in this Contract with respect to the Contractor.

  • TASK 1 GENERAL PROJECT TASKS PRODUCTS

  • Project Term The Project shall commence on the Signature Date, and shall endure for the Project Term.

  • Project Team Cooperation Partnering 1.1.3 Constitutional Principles Applicable to State Public Works Projects.

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

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

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

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