Project Presentations Sample Clauses

Project Presentations. Project presentations extend and promote knowledge of the NSDI and the valuable work of the awardee. Participants are requested to make formal presentations of their activities at a local, State, regional, national conference or meeting. The applicant is requested to budget sufficient funds to travel to the meeting or conference. An alternative is to publish a paper or article in a professional journal or newsletter.
AutoNDA by SimpleDocs
Project Presentations project for the duration of the Ground Lease, or as The Developer shall be responsible for obtaining community input to the Project from the applicable neighborhood board and/or other interested community groups, and other organizations as required by HHFDC. The Developer shall conduct a public informational briefing on the Developer’s Proposal in the community within three calendar months of the HHFDC Board approval of the Developer and its Proposal, unless otherwise extended at the sole discretion of HHFDC.
Project Presentations. The Developer shall be responsible for obtaining community input on the Project from the applicable neighborhood board and/or other interested community groups, and other organizations as requested by HHFDC. The Developer shall conduct a public informational briefing on the proposed Project to the Makakilo/Kapolei/Honokai Xxxx Neighborhood Board No. 34 and the Villages of Kapolei Association within six months of the HHFDC Board approval of the Developer and its Proposal for development of the Property, unless otherwise extended at the sole discretion of HHFDC.
Project Presentations. The City shall acknowledge the District in presentations or publications related to the Project.
Project Presentations. The Developer shall be responsible for obtaining community input on the Project from interested community groups, and other organizations as requested by HHFDC. The Developer shall conduct a public informational briefing on its proposed master plan for the Project Site and receive input on the design and development of the Project in the community commencing within six calendar months of the HHFDC For Action, unless otherwise extended at HHFDC’s sole discretion. The Developer shall develop and implement a robust public engagement program to obtain input from the residents, businesses, community stakeholders, and government agencies, which will inform the final design of the Project. Besides the public information briefing described in the previous paragraph, the Developer shall hold additional public meetings or design charrettes as necessary during the planning process to receive input on the design and development of the Project. It is important to get the public input. The Developer shall be responsible for any additional governmental briefings on the proposed master plan for the Project Site and design and development of the Project including but not limited to required public hearings and briefings before the Urban Design Review Board and the Maui Planning Commission for the Special Management Area use permit for the Project.
Project Presentations. No additional project workshop will be required as part of this amendment. Scope of Work - Residuals BPJ Study Amendment No. 1 P age 1 of 6 Updated: September 1, 2019 TASK 2 – DESKTOP ANALYSIS:

Related to Project Presentations

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • Construction Documents Phase Services 3.4.1 Based on the Owner’s approval of the Design Development Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Construction Documents for the Owner’s approval. The Construction Documents shall illustrate and describe the further development of the approved Design Development Documents and shall consist of Drawings and Specifications setting forth in detail the quality levels and performance criteria of materials and systems and other requirements for the construction of the Work. The Owner and Architect acknowledge that, in order to perform the Work, the Contractor will provide additional information, including Shop Drawings, Product Data, Samples and other similar submittals, which the Architect shall review in accordance with Section 3.6.4.

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

  • Project Engineer If the Project has been designed by the Project Engineer, the Project Engineer is to act as the Owner's representative, assumes all duties and responsibilities, and has the rights and authority assigned to Project Engineer in the Contract Documents in connection with completion of the Work all in accordance with the Contract Documents.

  • Project Planning GOVERNMENTAL APPROVALS; ENVIRONMENTAL COMPLIANCE; PUBLIC INFORMATION 30 4.1 Planning and Engineering Activities 30 4.2 Site Conditions 30 4.3 Governmental Approvals 30 4.4 Environmental Compliance 34 4.5 Community Outreach and Public Information 35

  • Project Changes 1.8.1. All changes shall be administered per the UGC.

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

  • Project Website The State will develop and maintain a website that will be made available in advance of the first public meeting for this project. The Engineer shall provide project information for the project website to the State including documents related to project background, study area limits, study objectives, project photos, study area maps, material presented at public meetings, and contact information for requesting additional information. The project website will be updated with the documents and other information provided by the Engineer to the State after each set of public meetings and the final report in PDF format provided by the Engineer will be posted by the State to give the general public access to the document.

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

  • CONSTRUCTION AND RELATED ENGINEERING SERVICES A. General construction work for buildings (CPC 512) 1) Unbound* 2) None 3) None 1) Unbound* 2) None 3) None

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