PROJECT PROPOSALS 9 Sample Clauses

PROJECT PROPOSALS 9. 5.1 Development and approval of Phase 1 Project Proposal 9
Sample 1
AutoNDA by SimpleDocs

Related to PROJECT PROPOSALS 9

  • Bidding and Proposal Phase 1.5.1 In conjunction with the development of the Guaranteed Maximum Price and at other times as appropriate to the Project, the Architect/Engineer shall assist the Owner and Construction Manager by receiving and recording requests for Bid and Request for Proposal (“RFP”) Documents, receiving and resolving questions about Bid and RFP Documents; preparing addenda, issuing addenda, and accounting for addenda issued; attending pre-bid and pre-proposal conferences and HUB meetings; evaluating bids and proposals; and assisting in preparing and awarding multiple contracts for construction. Architect/Engineer shall answer inquiries from bidders and proposers at Owner’s request, and shall prepare and issue any necessary addenda to the bidding or proposal documents.

  • Technical Proposals Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate PWS/SOO requirements. Written technical proposals shall normally address: * Technical Approach and descriptive narrative of the contractor's understanding of the requested effort * PWS in response to a SOO * Integrated Master Plan (if applicable) * Integrated Master Schedule (if applicable) * Key Personnel Assigned * Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable) * Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only)) * Period of Performance * Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) * Security (including clearance level) * Teaming Arrangement (including subcontracting; identify new ACAs) * Small Business Plan (if a large business) * Other Pertinent Data, such as assumptions made.

  • Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)

  • Cost Proposal After the Approved Working Drawings are approved by Landlord and Tenant, and the Contractor and subcontractors have been selected pursuant to Section 4.1 above, Landlord shall provide Tenant with a cost proposal in accordance with the Approved Working Drawings setting forth the reconciled bids and copies of all sub-bids, which cost proposal shall include, as nearly as possible, the cost of all Tenant Improvement Allowance Items to be incurred in connection with the construction of the Tenant Improvements (the "COST PROPOSAL"). The Cost Proposal shall reflect bids that will be priced by Contractor on an individual item-by-item or trade-by-trade basis. Landlord and Tenant shall work together in good faith in an attempt to agree upon a mutually acceptable Cost Proposal as soon as reasonably possible. Notwithstanding the foregoing, portions of the cost of the Tenant Improvements may be delivered to Tenant as such portions of the Tenant Improvements are priced by Contractor (on an individual item-by-item or trade-by-trade basis), even before the Approved Working Drawings are completed (the "PARTIAL COST PROPOSAL") for purposes of facilitating the early purchase of items and construction of the same. Tenant shall approve and deliver the Cost Proposal to Landlord within seven (7) business days of the receipt of the same, or, as to a Partial Cost Proposal within five (5) business days of receipt of the same, and upon receipt of the same by Landlord, Landlord shall be released by Tenant to purchase the items set forth in the Cost Proposal or Partial Cost Proposal, as the case may be, and to commence the construction relating to such items. If Tenant disapproves the Cost Proposal or Partial Cost Proposal, Tenant shall provide Landlord with a reasonably sufficient explanation, and in such event, Landlord and Tenant shall use good faith, diligent efforts to work with each other and Contractor to address Tenant's reasons for disapproving the Cost Proposal or Partial Cost Proposal, whichever is the case and a new Cost Proposal (or Partial Cost Proposal, as applicable) shall be prepared and the process described in this Section 4.2 shall be repeated. The date by which Tenant must approve and deliver the Cost Proposal or the last Partial Cost Proposal to Landlord, as the case may be, shall be known hereafter as the "COST PROPOSAL DELIVERY DATE". The total of all Partial Cost Proposals, if any, shall be known as the Cost Proposal.

  • Project Approach € Project schedules and budgets are reviewed by the Project Manager on a weekly basis during our company-wide Project Managers Meeting using project status reports generated by our control software (Deltek Vision). Progress is compared to the schedule and budget to ensure adequate resources are available and that necessary coordination is occurring. Costs are reported real time, with actual labor based on time sheet entry and actual expense costs based on invoices. The reporting system can be customized to track specific tasks or efforts in multiple categories, making it flexible enough to adapt to any project specific requirements. We hold regular project coordination meetings to facilitate communication and information transfer among the design team. These meetings are held weekly and are supplemented with e-mail communication, as well as telephone conversations. We hold monthly project status meetings with your project manager to update project status, discuss priorities, and receive direction from City staff. This provides an opportunity for communication and information to flow openly between the City and the design team. These meetings are supplemented by communications that will occur via e-mail and telephone. We conduct meetings with other agencies and stakeholders impacted by the work as needed. E-mail and telephone communication work well for quick questions or minor issues, but we have found that the most effective means of communication with other agencies and stakeholders is the “old-fashioned” face- to-face mexxxxx. Xxbble’s record of providing quality civil engineering services to our clients reflects our ability to manage multiple projects effectively and efficiently. Our philosophy is that each project is personally overseen by one of our principal officers, thereby providing immediate attention to all project aspects (i.e. negotiations, communications, schedule, budgets).

  • Additional proposals If the Company at any time during the continuance of this Agreement desires to modify expand or otherwise vary its activities carried on pursuant to this Agreement beyond those specified in any approved proposal, it shall give notice of such desire to the Minister and within 2 months after giving such notice shall submit to the Minister detailed proposals in respect of such modifications expansions or variations and such other matters as the Minister may require. The provisions of clause 4 and 5 (including (for the avoidance of doubt) clause 5(9)) shall apply, the necessary changes being made, to proposals submitted pursuant to this clause.

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

  • New Project Approval Consultant and District recognize that Consultant’s Services may include working on various projects for District. Consultant shall obtain the approval of District prior to the commencement of a new 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!