Describing impacts Sample Clauses

Describing impacts. ‌ An important part of the CascEff-project is the description of system impacts. It is clear that system impacts are multidimensional, for example due to the fact that societal sectors are very different in nature. Here, the choice is to describe impacts in terms of a number of consequence categories as well as in terms of more general overall system impact level. The consequence categories used are the following: ● Technical consequences encompass the damage and loss of technical components, physical assets, loss of production, etc. ● Organizational consequences relate to the organisations and institutions that manage the systems; encompassing impacts on e.g. organisational capacity, coordination, and information management, etc. ● Social consequences encompass impacts on community such as political instability and civil unrest. ● Human consequences encompass impact on population such as health-issues, reduced well-being, casualties and injuries. ● Economic consequences encompass impacts in terms of direct costs2. ● Environmental consequences encompass the effects on natural resources, flora and fauna.
Sample 1
AutoNDA by SimpleDocs

Related to Describing impacts

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

  • System Impact Study An assessment by the Transmission Provider of (i) the adequacy of the Transmission System to accommodate a Completed Application, an Interconnection Request or an Upgrade Request, (ii) whether any additional costs may be incurred in order to provide such transmission service or to accommodate an Interconnection Request, and (iii) with respect to an Interconnection Request, an estimated date that an Interconnection Customer’s Customer Facility can be interconnected with the Transmission System and an estimate of the Interconnection Customer’s cost responsibility for the interconnection; and (iv) with respect to an Upgrade Request, the estimated cost of the requested system upgrades or expansion, or of the cost of the system upgrades or expansion, necessary to provide the requested incremental rights.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Project Timeline The Project Timeline establishes a start and end date for each Phase of the Project. Developed during the Initiate & Plan Stage and revised as mutually agreed to, if needed, the timeline accounts for resource availability, business goals, size and complexity of the Project, and task duration requirements.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline: • •

  • Overall Project Schedule The Construction Progress Schedule that is approved by the Owner.

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

  • Product Description The lead products covered by this Settlement Agreement is limited to following Amazon Identification Number (ASIN) B0BBMRLNV9, with the description, "Lesnow 63-37 Tin Lead Rosin Core Solder Wire for Electrical Soldering 0.8mm Soldering Wire Electronics Solder Content Solder Flux 1.8% (0.8mm, 50g)," which was offered for sale by the Settling Entity on xxxxxx.xxx, hereinafter the “Product” or “Products.”

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