Project Co Bound. Project Co will be bound to the provisions of this Section 2.
Project Co Bound Sample Clauses
Related to Project Co Bound
Project Contracts Authority shall upon its election, succeed, without the necessity of any further action by the Concessionaire, to the interests of the Concessionaire under such of the Project Contracts as the Authority may in its discretion deem appropriate, and shall upon such election be liable to the Contractors only for compensation accruing and becoming due and payable to them under the terms of their respective Project Contracts from and after the date the Authority elects to succeed to the interests of the Concessionaire. For the avoidance of doubt, it is hereby agreed, and the Concessionaire hereby acknowledges, that all sums claimed by such Contractors as being due and owing for works and services performed or accruing on account of any act, omission or event prior to such date shall constitute debt between the Concessionaire and such Contractors, and the Authority shall not in any manner be liable for such sums. It is further agreed that in the event the Authority elects to cure any outstanding defaults under such Project Contracts, the amount expended by the Authority for this purpose shall be deducted from the Termination Payment.
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.
Construction Plans Tenant shall prepare final plans and specifications for the Tenant Improvements that (a) are consistent with and are logical evolutions of the Approved Schematic Plans and (b) incorporate any other Tenant-requested (and Landlord-approved) Changes (as defined below). As soon as such final plans and specifications ("Construction Plans") are completed, Tenant shall deliver the same to Landlord for Landlord's approval, which approval shall not be unreasonably withheld, conditioned or delayed. All such Construction Plans shall be submitted by Tenant to Landlord in electronic .pdf, CADD and full-size hard copy formats, and shall be approved or disapproved by Landlord within ten (10) business days after delivery to Landlord. Landlord's failure to respond within such ten (10) business day period shall be deemed approval by Landlord. If the Construction Plans are disapproved by Landlord, then Landlord shall notify Tenant in writing of its objections to such Construction Plans, and the parties shall confer and negotiate in good faith to reach agreement on the Construction Plans. Promptly after the Construction Plans are approved by Landlord and Tenant, two (2) copies of such Construction Plans shall be initialed and dated by Landlord and Tenant, and Tenant shall promptly submit such Construction Plans to all appropriate Governmental Authorities for approval. The Construction Plans so approved, and all change orders approved (to the extent required) by Landlord, are referred to herein as the "Approved Plans."
Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.
Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.
Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.
Project Documents In addition to any other pertinent and necessary Project documents, the following documents shall be used in the development of the Project:
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.
Design Development Documents See Section 2, Part 1, Article 2.1.5.
Project contract 1. For each approved project a project contract shall be concluded between the Programme Operator and the Project Promoter.
