Exploitable foreground Sample Clauses

Exploitable foreground. The exploitation strategies outlined at the start of the project are described in the DoW. Table B2.1 will summarise the exploitable foreground as identified by the consortium. Progress along each exploitation track will be monitored by the Exploitation Manager and will be reported in the end of the project in the final PUDF. Table B.2a. Overview table with exploitable foreground OVERVIEW TABLE WITH EXPLOITABLE FOREGROUND Type of exploitable foreground Description of exploitable foreground Confidential Exploitable product(s) or measure(s) Sector(s) of application Timetable, commercial or any other use Patents or other IPR exploitation (licences) Owner & other beneficiary(s) involved e.g. General advancement of knowledge e.g. Commercial exploitation of R&D results TableB.2b. Exploitation activities of the consortium: template table EXPLANATION OF THE EXPLOITABLE FOREGROUND Lead partner name Describe the innovation content of the result to be exploited. Who will be the customer? What benefit will it bring to the customers? When is the expected date of achievement in the project? What is the time to market? What are the costs to be incurred after the project and before exploitation? What is the approximate price range of this result / price of licences? What is the market size in Million € for this result? What is the trend? How will this result rank against competing products in terms of price / performance? Who are the competitors for this result? How fast and in what ways will the competition respond to this result? Who are the project partners involved in the result? Who are the industrial partners interested in the result (partners, sponsors, etc…)? Have you protected or will you protect this result? How? When? References [1] Grant Agreement Annex I (DoW): available in the E2SWITCH document repository: xxxx://xxx.x0xxxxxx.xx/members/repository/legal/DOW_E2SWITCH_2013-09- 13_final_bookmarks.pdf [2] Consortium Agreement: xxxx://xxx.x0xxxxxx.xx/members/repository/legal/E2SWITCH_CA_signed.pdf
AutoNDA by SimpleDocs
Exploitable foreground. As mentioned for the ‘Applications’ list, the ‘Exploitable Foreground’ one is compiled for IRPWind and EERA JP Wind. All partners and members should contribute to update it.. The document will be accessible through the ‘knowledge transfer’ section of the IRPWind website, as well as through the online technology transfer network (explained in section 0). Please find the full list of scientific publications in Appendix F. Per topic that is listed, the owner of the relevant foreground will provide a text that explains its exploitability. As suggested by [2], this text shall elaborate on: − Its purpose − How the foreground might be exploited, when and by whom − IPR exploitable measures taken or intended − Further research necessary, if any − Potential/expected impact (quantify where possible)

Related to Exploitable foreground

  • Foreground Regarding Foreground, EC-GA Article II.26. - Article II.29. shall apply with the following additions:

  • Exploitation (i) Exploitation of intellectual property may take the form of patenting by the originator singly or in combination with other agencies.

  • Manufacture 2.1. The LED(s) on the LED module shall be equipped with suitable fixation elements.

  • Third Party Technology The Company makes use of third party technology to collect information required for traffic measurement, research, and analytics. Use of third party technology entails data collection. We therefore would like to inform clients the Company enables third parties to place or read cookies located on the browsers of users entering the Company’s domain. Said third parties may also use web beacons to collect information through advertising located on the Company’s web site. Please note that you may change your browser settings to refuse or disable Local Shared Objects and similar technologies; however, by doing so you may be disabling some of the functionality of Company’s services.

  • Licensed Products Lessee will obtain no title to Licensed Products which will at all times remain the property of the owner of the Licensed Products. A license from the owner may be required and it is Lessee's responsibility to obtain any required license before the use of the Licensed Products. Lessee agrees to treat the Licensed Products as confidential information of the owner, to observe all copyright restrictions, and not to reproduce or sell the Licensed Products.

  • Product Technical Support & Maintenance Licensee shall have the option of electing the Product technical support and maintenance (“maintenance”) set forth in the Contract by giving written notice to Contractor any time during the Centralized Contract term. Maintenance term(s) and any renewal(s) thereof are independent of the expiration of the Centralized Contract term and will not automatically renew. Maintenance shall include, at a minimum, (i) the provision of error corrections, updates, revisions, fixes, upgrade and new releases to Licensee, and (ii) Help Desk assistance with locally accessible “800” or toll free, local telephone service, or alternatively on-line Help Desk accessibility. Contractor shall maintain the Products so as to provide Licensee with the ability to utilize the Products in accordance with the Product documentation without significant functional downtime to its ongoing business operations during the maintenance term. Authorized User shall not be required to purchase maintenance for use of Product, and may discontinue maintenance at the end of any current maintenance term upon notice to Contractor. In the event that Authorized User does not initially acquire or discontinues maintenance of licensed Product, it may, at any time thereafter, reinstate maintenance for Product without any additional penalties or other charges, by paying Contractor the amount which would have been due under the Contract for the period of time that such maintenance had lapsed, at then current NYS net maintenance rates.

  • Foreground IP This subparagraph d. shall not apply to unmodified commercial off‐the‐shelf goods. If Services or goods are developed, modified or redesigned pursuant to this Contract then the paragraphs below apply.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • SEXUAL EXPLOITATION 22.1 The Contractor shall take all appropriate measures to prevent sexual exploitation or abuse of anyone by it or by any of its employees or any other persons who may be engaged by the Contractor to perform any services under the Contract. For these purposes, sexual activity with any person less than eighteen years of age, regardless of any laws relating to consent, shall constitute the sexual exploitation and abuse of such person. In addition, the Contractor shall refrain from, and shall take all appropriate measures to prohibit its employees or other persons engaged by it from, exchanging any money, goods, services, offers of employment or other things of value, for sexual favors or activities, or from engaging in any sexual activities that are exploitive or degrading to any person. The Contractor acknowledges and agrees that the provisions hereof constitute an essential term of the Contract and that any breach of this representation and warranty shall entitle UNDP to terminate the Contract immediately upon notice to the Contractor, without any liability for termination charges or any other liability of any kind.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

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