ZSI, HSE, ICISTE, IPTS Sample Clauses

ZSI, HSE, ICISTE, IPTS. − Stock taking and analysis on the hand side of existing information on EU-Russia relations and its framework (Four Common Spaces, shifting geopolitical framework expressed by the maceration of the triad dominance and the EU’s and Russia’s response to it in terms of international S&T policies etc.) with an explicit focus on their implications for science and technology and on the other hand side of the findings of WP1, the relevant literature and the results of other relevant strategic projects (incl. a S&T Delphi study HSE whose results will be available end of 2009).
AutoNDA by SimpleDocs
ZSI, HSE, ICISTE, IPTS. Establishment of an EU-Russian expert panel to support the design of one structural scenario for future S&T and innovation cooperation (such as the potential variable geometries of cooperation and cooperation modes) and two different thematic scenarios (targeting at the most suitable priorities for S&T and innovation cooperation between EU MS/AC and Russia, in which Russia is equally performer as Europe or at least has the potential to do so; and will be built upon deliverables D1.8, D2.1.1, D2.1.2, D2.3, D3.4.1,D3.4.2andD3.5.1).
ZSI, HSE, ICISTE, IPTS. − Planning and implementing 3 scenario development workshops to be held in Seville, Moscow, Vienna accompanied by interviews and on-line questionnaires involving up to 200 experts from EU MS/AC and Russia. ZSI, HSE, ICISTE, IPTS − Preparing the Delphi questionnaires through a small drafting meeting held in Vienna. Implementation of the scenario-based Delphi study involving at least 400 experts from EU MS/AC and Russia; two feedback circles are envisaged (main methods: inquiry of the experts already involved in scenario-building and further extension of the respondents network via targeted online-questionnaires). The results from the Delphi exercise shall support the identification of common interests within sub-themes and willingness for cooperation between researchers from EU MS/AC and Russia. These will be framed within the three thematic priorities for S&T and innovation cooperation between EU MS/AC and Russia already identified in order to align EU MS/AC and Russia priorities.
ZSI, HSE, ICISTE, IPTS. − Preparing recommendations for a sustainable mid-term cooperation policy in S&T and innovation between the EU MS/AC and Russia through a small drafting meeting held in Brussels. Funding organisations shall participate in this meeting to ensure that the future definition of priorities are based on a realistic understanding of what issues researchers are keen on pursuing and how such issues are regarded by the users of research results (e.g. industry). This is critical to assure that the recommendations highlights funding of high quality research. ZSI, HSE, ICISTE, IPTS Partners involved: ZSI, HSE, ICISTE, IPTS Efforts : ZSI : 20,5 PM, travel : 5 EU-EU, 1 EU-RU HSE : 20,5 PM, travel : 8 RU-EU ICISTE : 6,75 PM, travel : 4 RU-EU IPTS : 13,5 PM, travel : 7 EU-EU, 1 EU-RU Travel of external workshop participants : 12 EU-EU, 20 EU-RU, 4 RU-RU 3 small expert workshops (15 participants each) 3 project meetings (10 participants each) Layout, editing, printing and shipping of the foresight report (11.500,00 €, ZSI) Procurement of an online-questionnaire tool for running questionnaires in Cyrillic and Latin (6.000,00 €, HSE)

Related to ZSI, HSE, ICISTE, IPTS

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Research, Science and Technology Cooperation 1. The aims of cooperation in research, science and technology, carried out in the mutual interest of the Parties and in compliance with their policies, will be: (a) to build on existing agreements already in place for cooperation on research, science and technology; (b) to encourage, where appropriate, government agencies, research institutions, universities, private companies and other research organizations in the Parties to conclude direct arrangements in support of cooperative activities, programs or projects within the framework of this Agreement, specially related to trade and commerce; and (c) to focus cooperative activities towards sectors where mutual and complementary interests exist, with special emphasis on information and communication technologies and software development to facilitate trade between the Parties. 2. The Parties will encourage and facilitate, as appropriate, the following activities including, but not limited to:

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • COMMERCIAL COMPUTER SOFTWARE If performance involves acquisition of existing computer software, the following Company Exhibit is incorporated by reference: CCS Commercial Computer Software License (Company – July 2010).

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.

  • Technology Research Analyst Job# 1810 General Characteristics Maintains a strong understanding of the enterprise’s IT systems and architectures. Assists in the analysis of the requirements for the enterprise and applying emerging technologies to support long-term business objectives. Responsible for researching, collecting, and disseminating information on emerging technologies and key learnings throughout the enterprise. Researches and recommends changes to foundation architecture. Supports research projects to identify and evaluate emerging technologies. Interfaces with users and staff to evaluate possible implementation of the new technology in the enterprise, consistent with the goal of improving existing systems and technologies and in meeting the needs of the business. Analyzes and researches process of deployment and assists in this process.

  • Project Team Cooperation Partnering 1.1.3 Constitutional Principles Applicable to State Public Works Projects.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.

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