Insufficient use of R&D results in agriculture Sample Clauses

Insufficient use of R&D results in agriculture. The general situation in R&D is fully reflected in the area of agriculture despite the fact that there is a specific, long-term research in the sector. A major problems of the existing systems of knowledge transfer is their fragmentation, inflexibility and also the unwillingness of the business sphere to share the cost associated with knowledge transfer. We view this area as an opportunity to apply the principles of European innovative partnership and to establish operational groups and develop their activities. Development needs:  To support the adaptation of research results to specific needs through close cooperation of the practice with research institutions, to utilize innovation, to increase the added value and accelerate the introduction of the latest knowledge of environmental protection into practice.  To enable provision of advisory services utilising the R&D results in agriculture and forestry, covering topical issues.  Setting up and developing the work of operational groups following the principles of European Innovative Partnership. Specific needs and challenges of cross-border regions: o There is high potential mainly in sharing research and innovation infrastructure which is usually very costly and its cross-border and transnational use/sharing brings significant savings and increases the potential for building up research and innovation capacities in border areas. o Cooperation between individual specialisations and professional teams on both sides of the border offers high potential in the area of basic and applied research (increasing the participation of SMEs in research and innovation results, practical use, positive impacts on the labour market, supplier relationships etc.).
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs

Related to Insufficient use of R&D results in agriculture

  • Test Results The employer, upon request from an employee or former employee, will provide the confidential written report issued pursuant to 4.9 of the Canadian Model in respect to that employee or former employee.

  • How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.

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

  • Drug Test Results 1. All records pertaining to department-required drug tests shall remain confidential, and shall not be provided to other employers or agencies without the written permission of the person whose records are sought. However, medical, administrative, and immediate supervisory personnel may have access to relevant portions of the records as necessary to insure the acceptable performance of the officer's job duties.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • What To Do If You Find A Mistake On Your Statement If you think there is an error on your statement, write to us at the address(es) listed on your statement. In your letter, give us the following information:

  • Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.

  • The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.

  • MFMP Transaction Fee Reports The Contractor shall submit complete monthly MFMP Transaction Fee Reports to the Department. Reports are due 15 calendar days after the end of each month. Information on how to submit MFMP Transaction Fee Reports online can be located at xxxxx://xxx.xxx.xxxxxxxxx.xxx/business_operations/state_ purchasing/myfloridamarketplace/mfmp_vendors/transaction_fee_and_reporting. Assistance with transaction fee reporting is also available by email at xxxxxxxxxxxxx@xxxxxxxxxxxxxxxxxxxx.xxx or telephone at 866-FLA-EPRO (866-352- 3776) from 8:00 a.m. to 6:00 p.m. Eastern Time.

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

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