Project Summaries Sample Clauses

Project Summaries. Following Execution of this Contract, the Contractor shall provide summaries of project status to the [bureau/division/program coordinator] once every [six months] during the time in which this Contract is in effect. Such summaries shall include a brief description (1 or more pages) indicating the work completed to date and the anticipated project completion date if different from the current Contract expiration date.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Project Summaries. If requested by DEEP, the Contractor shall provide summaries of project status to DEEP during the time in which this Contract is in effect. Such summaries shall include a brief description indicating the work completed to date.
Sample 1
Project Summaries. Following execution of this contract, the Contractor shall provide summaries of the Project’s status to the BIG Program Coordinator, DEP, once every six months during the time in which this contract is in effect. Such summaries shall include a brief description (1 or more pages) indicating the work completed to date and the anticipated project completion date if different from the current contract expiration date.
Sample 1
Project Summaries. The l-5 corridor study resulted in thirteen specific project recommendations. The following is a summary of the recommended deployment for the corridor. Develop a system that allows route, weather, and traffic condition information to be sent to local broadcast radio stations. Each station would then have the capability to broadcast this information to its listeners. Develop an ice detection and warning system at selected locations. Sensors would detect when bridge and road conditions become icy and a warning system would disseminate real-time, site- specific information to travelers, WSDOT maintenance personnel, and the WSP. (WWW). Install traveler information kiosks at rest stops along the corridor. Traveler information would include both static and real-time data applicable to the corridor. drivers and drivers of other high profile vehicles. Develop a portable TMS to be utilized by WSDOT and WSP personnel during special events and maintenance and construction activities. Portable devices would include VMS, traffic signals, CCTV, and vehicle detection systems. warning system will be activated upon sensing a potentially hazardous condition. Implement a variable speed limit signing and weather warning system in the Mt. Xxxxxx hills area (MP 223-228). The system will detect changing weather conditions and provide motorists with information, weather-related warnings, and variable speed limits. Expand the WSDOT SC&DI network along l-5 from Marysville (MP 206) to the Mt. Vernon interchange (MP 223). The expanded coverage along this stretch of roadway would provide better traffic management capabilities and increased motorist safety.
Sample 1
Project Summaries. Contractor will summarize the information from Tasks 5.2 and 5.3 and also provide relevant project information and narrative text for these projects, such that this information could be used in future grant applications. Contractor will create summary sheets (2-pages each) for each project.
Sample 1
Project Summaries. During the Term, within thirty (30) days after the end of the Calendar Year ending December 31 or such other date within such Calendar Year as mutually agreed between the Parties, GSK shall disclose to Codexis a summary of [***]. Such summary shall be provided to Codexis in sufficient detail to provide to Codexis reasonable information into GSK activities with respect to GSK’s use of the Platform Technology for the purpose of enabling Codexis to anticipate GSK’s progression toward achievement of milestone events as set forth in Article 7 and to monitor GSK’s compliance with this Agreement. Each such summary shall include [***] SV\1263057.27 [***]; provided that, in the event [***], the information provided by GSK in any such summary report from such time onwards [***].
Sample 1
Project Summaries. During the Term, within thirty (30) days after the end of the Calendar Year ending December 31 or such other date within such Calendar Year as mutually agreed between the Parties, GSK shall disclose to Codexis a summary of [***]. Such summary shall be provided to Codexis in sufficient detail to provide to Codexis reasonable information into GSK activities with respect to GSK’s use of the Platform Technology for the purpose of enabling Codexis to anticipate GSK’s progression toward achievement of milestone events as set forth in Article 7 and to monitor GSK’s compliance with this Agreement. Each such summary shall include [***] [***]; provided that, in the event [***], the information provided by GSK in any such summary report from such time onwards [***]. [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions.
Sample 1
AutoNDA by SimpleDocs

Related to Project Summaries

  • 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 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 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 Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Development Reports Beginning six months after Effective Date and ending on the date of first commercial sale of a Licensed Product in the United States, LICENSEE shall report to Cornell progress covering LICENSEE's (and Affiliate's and Sublicensee's) activities and efforts in the development of rights granted to LICENSEE under this Agreement for the preceding six months. The report shall include, but not be limited to, activities and efforts to develop and test all Licensed Products and obtain governmental approvals necessary for marketing the same. Such semi-annual reports shall be due within sixty days (60) of the reporting period and shall use the form as provided herein as Appendix C.

  • Project Overview Project Title [Drafting note: ARENA to complete. Insert full long name in accordance with ARENA’s naming convention] i.e. [GMS Number] [Powerworks, voltage control on the Pacific Islands Study] [GMS Number] [study/ project/ fellowship/ scholarship/ R&D Project] Contract Number [Drafting note: ARENA to complete – to be obtained from ARENA’s GMS] Recipient [Drafting note: Recipient to insert full legal name and ABN] Guidelines and policies Advancing Renewables Program – Program Guidelines, 2020 (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/XXXXX_XXX_Xxxxxxxxxx_XX_Xxxxxx_Xxxxx_XXXXX.xxx) ARENA Variation Policy (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxxx-xxxxxxxxx-xxxxxxxxx-xxxxxx.xxx) ARENA Report Writing Guidelines (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxx-xxxxxxx-xxxxxxxxxx.xxx)

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

  • Projects There shall be a thirty (30) km free zone around the projects excluding the Metro Vancouver Area. For local residents, kilometers shall be paid from the boundary of the free zone around the project. Workers employed by any contractor within an identified free zone who resides outside of that same free zone will be paid according to the Kilometer Chart from the project to their residence less thirty

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