Networking Events Sample Clauses

Networking Events. ‌ There will be at least two networking events during the duration of the project. In these events, a presentation of progress in case studies and preliminary conclusions will be presented to external stakeholders. Moreover, interactions between all interested parties will be encouraged to serve as useful feedback for the key partners in terms of successful implementation of the project. The above-described networking events, will be held, one in the Czech Republic and one in Italy, at the end of the second and third years of the project respectively. The following table summarizes the project events, including, type, time, number and involved partner. Event When How many Involved partner Roundtables 2 per annual meeting 4 SLU USB AFS MUC Together with different WP and case activities 3 WP and case leaders Workshops 1 per partner meeting 4 SLU USB AFS MUC Together with different WP and case activities 3 WP and case leaders Training activities/user meetings 1 per partner 19 All partners Conference Final meeting 1 SLU Networking Events In conjunction with the partner’s meeting 2 USB UNIBO
Sample 1
AutoNDA by SimpleDocs
Networking Events. Companies and SARIO will have free access to all Plug and Play community events (including monthly Community Meetings, CEO Talks, Meet-ups, etc.). The aim of this access is establishing trade relations. Plug and Play must inform the Companies and SARIO about all Plug and Play social events well in advance (at least 10 days) of the event.
Sample 1
Networking Events. As part of the preparatory activities for EPOS-SP Work Package 3, an initial networking event with other relevant initiatives was held in Vienna, Austria during the European Geosciences Union (EGU) General Assembly 2019. This event brought together representatives from solid Earth research infrastructures in other countries and regions including EPOS, AuScope (Australia), Earth Cube, UNAVCO and IRIS (USA), as well as related clustering activities including representatives from the European Environmental Research infrastructures (ENVRI) community. This initial event was intended to be a preliminary meeting to identify common areas of interest for future collaborative efforts, and to establish a framework for regular meetings. It was agreed that a series of side events would be coordinated to coincide with large annual geoscience conferences where most if not all of the different initiatives would have representatives in attendance. In addition, the timing of these various conferences would allow a regular schedule of half-yearly meetings to be organised. The preferred target events would be the annual EGU General Assembly that takes place in Vienna each year, usually during April or May; and the AGU Fall Meeting that is held annually in the USA during December. Other further meeting opportunities were also identified including the Geological Society of America (GSA) and Xxxxxxxxxxx conferences.
Sample 1

Related to Networking Events

  • Qualifying Events In order to be eligible for COBRA continuation, you need to have experienced a Qualifying Event. A Qualifying Event is one of the events listed below which would result in loss of coverage if not for the COBRA continuation:

  • Emergency Situations If the condition is an emergency, this will be communicated to the Contractor with the request that corrections are to be accomplished immediately. The Contractor shall respond to the notice in emergency situations within twenty-four hours. If the Contractor fails to respond within this time limit, the Owner may correct the defect and charge the Contractor for the Work. If it is determined the complaint is not the responsibility of the Contractor, the Contractor shall be promptly paid for the cost of the corrective work. The Contractor shall give notice in writing to the Owner when corrections have been completed.

  • Events Beyond Our Control If an Event Beyond Our Control occurs and prevents Us from performing any of Our obligations under this Contract to any extent, then We are not required to perform that obligation to the extent and for as long as We are prevented by that Event Beyond Our Control. If such an Event Beyond Our Control occurs and We consider it appropriate to do so, We may notify You of the Event Beyond Our Control by any reasonable means, including by a public announcement.

  • Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.

  • Program Monitoring and Evaluation (c) The Recipient shall prepare, or cause to be prepared, and furnish to the Association not later than six months after the Closing Date, a report of such scope and in such detail as the Association shall reasonably request, on the execution of the Program, the performance by the Recipient and the Association of their respective obligations under the Legal Agreements and the accomplishment of the purposes of the Financing.”

  • Transition from Existing Evaluation System A) The parties may agree that 50% of more of Educators in the district will be evaluated under the new procedures at the outset of this Agreement, and 50% or fewer will be evaluated under the former evaluation procedures for the first year of implementation of the new procedures in this Agreement.

  • INTERNET PLANNING, ENGINEERING AND OPERATIONS ‌ Job Title: Internet/Web Engineer Job#: 2620 General Characteristics Integrally involved in the development and support of all Internet/Intranet/Extranet sites and supporting systems. Works closely with other IT groups and customers to define the system design and user interface based on customer needs and objectives. Participates in all phases of the development and implementation process, and may act as a project manager on special projects. Ensures the integration of the Web servers and all other supporting systems. Responsible for system tuning, optimization of information/data processing, maintenance and support of the production environment.

  • Emergency Closures A. The University’s inability to make a Room available to me for any reason beyond the University’s control including, but not limited to, natural disaster, fire, flood, earthquake, condemnation, pandemic, quarantine, utility malfunction, infestation, or other emergency or force majeure event shall not constitute a breach of this Agreement by the University. In such circumstances, the University shall have no liability to me in any way for injuries, reimbursement, damages, inconvenience, annoyance or compensation of any kind. The University may attempt to find, but cannot guarantee, an alternative space for me. If the unavailability of my Room or an alternative space persists for more than 72 hours, I may terminate this Agreement and Check out during said unavailability without penalty provided that I shall be responsible for all financial obligations incurred up to the date of such termination. The University agrees to provide me with a pro rata refund, calculated from the date of such termination to the end of the Agreement Period, of any prepaid housing and dining payment made to the University, and to return my Deposit pursuant to this Agreement. Upon resumption of standard operations, Agreement Termination requirements and charges will apply as described in Section XIV.

  • Events If either Party hereto is at any time either during this Agreement or thereafter prevented or delayed in complying with any provisions of this Agreement by reason of strikes, walk-outs, labour shortages, power shortages, fires, wars, acts of God, earthquakes, storms, floods, explosions, accidents, protests or demonstrations by environmental lobbyists or native rights groups, delays in transportation, breakdown of machinery, inability to obtain necessary materials in the open market, unavailability of equipment, governmental regulations restricting normal operations, shipping delays or any other reason or reasons beyond the control of that Party, then the time limited for the performance by that Party of its respective obligations hereunder shall be extended by a period of time equal in length to the period of each such prevention or delay.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

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