PROJECT PRESS Sample Clauses

PROJECT PRESS. RELEASES Press releases were created by both Shurepower and the EPA in order to promote the eTRU and hybrid electrification technology to a wider audience by presenting the technology’s positive operational effects as well as their roles in the project. The Shurepower press release was mainly focused on announcing the project and explaining the potential benefits that can be seen by using eTRU technology instead of standard TRU technology, including reduced emissions, fuel use and noise. This press release, attached in Appendix H, also explained the role and described the expertise of each partner involved in the project. The focus of the U.S. EPA press release was towards the agency’s role in this project. EPA recognizes that this hybrid eTRU technology is a method of reducing diesel fuel use and emissions of TRUs and included a brief description of the eTRU technology. This press release was distributed to the media immediately prior to the previously mentioned press event. Both press releases are being included in
Sample 1
AutoNDA by SimpleDocs

Related to PROJECT PRESS

  • 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 Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

  • Project Summary The main objective of the LIFE GAIA Sense project is to demonstrate Gaiasense, an innovative “Smart Farming” (SF) solution that aims at reducing the consumption of natural resources, as a way to protect the environment and support Circular Economy (CE) models. More specifically, this project will launch 18 demonstrators across Greece, Spain and Portugal covering 9 crops (olives, peaches, cotton, pistachio, potatoes, table tomatoes, industrial tomatoes, grapes, kiwi) in various terrain and microclimatic conditions. They will demonstrate an innovative method, based on high-end technology, which is suitable for being replicated and will be accessible and affordable to Farmers either as individuals or collectively through Agricultural Cooperatives. Moreover, LIFE GAIA Sense aims to promote resource efficiency practices in SMEs of the agricultural sector and eventually, contribute to the implementation of the Roadmap to a Resource Efficient Europe. This project will demonstrate a method on how the farmer will be able to decide either to use or avoid inputs (irrigation, fertilizers, pesticides etc.) in a most efficient way, without risking the annual production. The focus is on the resource consumption reduction side of CE, and the results will be both qualitatively and quantitatively, considering the resources’ efficiency in agricultural sector.

  • PROJECT 3.01. The Recipient declares its commitment to the objectives of the Project. To this end, the Recipient shall carry out the Project in accordance with the provisions of Article IV of the General Conditions.

  • 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 Work PURCHASER shall complete the following projects in accordance with the specifications provided in Exhibits B, C, D, E, and F and written instructions from STATE. Project locations are shown on Exhibit A unless otherwise described. PURCHASER shall furnish all material unless otherwise specified.

  • Construction Phase Services 3.1.1 – Basic Construction Services

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

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