Time limitation for dissemination of Knowledge Sample Clauses

Time limitation for dissemination of Knowledge. If Dissemination of Knowledge would not adversely affect its protection or its use, the Participants shall ensure that it is disseminated within a period of two years after the end of the CRP. Should the Participants fail to do so, the concerned Funding Partners of the PLANT-KBBE Initiative may disseminate the Knowledge. In doing so, the concerned Funding Partners of the PLANT-KBBE Initiative shall take particular account of the following factors: The need to safeguard intellectual property rights; The benefit of swift dissemination, for example in order to avoid duplication of research efforts and to create synergies between projects; Confidentiality; The Legitimate Interests of the Participants, in particular the acknowledgement of authorship Specific rules for Massively Produced Data or Resource In order to avoid duplication of research efforts in the very specific case of the MPDR, the Participants hereby agree to disseminate MPDR within six (6) months after they have been made available to the Participants (which then could be before the term of the CRP). Nonetheless, the Participants may agree on a case by case basis that a portion of a MPDR may not be disseminated immediately in reason of its high competitive potential – taking into account that dissemination rules of article 10.2.1 shall nonetheless apply in such case. Dissemination of MPDR shall be royalty-free (maintenance costs may be nonetheless requested).
AutoNDA by SimpleDocs

Related to Time limitation for dissemination of Knowledge

  • Updated Information Submission by Developer The updated information submission by the Developer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. Developer shall submit a completed copy of the Large Generating Facility data requirements contained in Appendix 1 to the Large Facility Interconnection Procedures. It shall also include any additional information provided to Connecting Transmission Owner for the Interconnection Feasibility Study and Interconnection Facilities Study. Information in this submission shall be the most current Large Generating Facility design or expected performance data. Information submitted for stability models shall be compatible with NYISO standard models. If there is no compatible model, the Developer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Developer’s data is different from what was originally provided to Connecting Transmission Owner and NYISO pursuant to an Interconnection Study Agreement among Connecting Transmission Owner, NYISO and Developer and this difference may be reasonably expected to affect the other Parties’ facilities or the New York State Transmission System, but does not require the submission of a new Interconnection Request, then NYISO will conduct appropriate studies to determine the impact on the New York State Transmission System based on the actual data submitted pursuant to this Article 24.3. Such studies will provide an estimate of any additional modifications to the New York State Transmission System, Connecting Transmission Owner’s Attachment Facilities, or System Upgrade Facilities or System Deliverability Upgrades based on the actual data and a good faith estimate of the costs thereof. The Developer shall not begin Trial Operation until such studies are completed. The Developer shall be responsible for the cost of any modifications required by the actual data, including the cost of any required studies.

  • Return of material containing or pertaining to the Confidential Information 7.1 The Disclosing Party may, at any time, and in its sole discretion request the Receiving Party to return any material and/or data in whatever form containing, pertaining to or relating to Confidential Information disclosed pursuant to the terms of this Agreement and may, in addition request the Receiving Party to furnish a written statement to the effect that, upon such return, the Receiving Party has not retained in its possession, or under its control, either directly or indirectly, any such material and/or data.

  • Meaning of Confidential Information For the purposes of this Contract, the term “Confidential Information” means all information and documentation of a party that: (a) has been marked “confidential” or with words of similar meaning, at the time of disclosure by such party; (b) if disclosed orally or not marked “confidential” or with words of similar meaning, was subsequently summarized in writing by the disclosing party and marked “confidential” or with words of similar meaning; and, (c) should reasonably be recognized as confidential information of the disclosing party. The term “Confidential Information” does not include any information or documentation that was: (a) subject to disclosure under the Michigan Freedom of Information Act (FOIA); (b) already in the possession of the receiving party without an obligation of confidentiality; (c) developed independently by the receiving party, as demonstrated by the receiving party, without violating the disclosing party’s proprietary rights; (d) obtained from a source other than the disclosing party without an obligation of confidentiality; or, (e) publicly available when received, or thereafter became publicly available (other than through any unauthorized disclosure by, through, or on behalf of, the receiving party). For purposes of this Contract, in all cases and for all matters, State Data is deemed to be Confidential Information.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • Disclosure to FERC or its Staff Notwithstanding anything in this Section 17 to the contrary, and pursuant to 18 C.F.R. § 1b.20, if FERC or its staff, during the course of an investigation or otherwise, requests information from one of the Interconnection Parties that is otherwise required to be maintained in confidence pursuant to this Interconnection Service Agreement, the Interconnection Party, shall provide the requested information to FERC or its staff, within the time provided for in the request for information. In providing the information to FERC or its staff, the Interconnection Party must, consistent with 18 C.F.R. § 388.122, request that the information be treated as confidential and non-public by FERC and its staff and that the information be withheld from public disclosure. Interconnection Parties are prohibited from notifying the other Interconnection Parties prior to the release of the Confidential Information to the Commission or its staff. An Interconnection Party shall notify the other Interconnection Parties to the Interconnection Service Agreement when it is notified by FERC or its staff that a request to release Confidential Information has been received by FERC, at which time any of the Interconnection Parties may respond before such information would be made public, pursuant to 18 C.F.R. § 388.112.

  • Definition of Confidential Information The term “Confidential Information” shall mean all information that either party discloses (a “Disclosing Party”) to the other party (a “Receiving Party”), whether in writing, electronically, or orally and in any form (tangible or intangible), that is confidential, proprietary, or relates to clients or shareholders (each either existing or potential). Confidential Information includes, but is not limited to:

  • Release of Confidential Information No Party shall release or disclose Confidential Information to any other person, except to its Affiliates (limited by FERC Standards of Conduct requirements), subcontractors, employees, consultants, or to parties who may be considering providing financing to or equity participation with Developer, or to potential purchasers or assignees of a Party, on a need-to-know basis in connection with this Agreement, unless such person has first been advised of the confidentiality provisions of this Article 22 and has agreed to comply with such provisions. Notwithstanding the foregoing, a Party providing Confidential Information to any person shall remain primarily responsible for any release of Confidential Information in contravention of this Article 22.

  • Disclosure to FERC its Staff, or a State. Notwithstanding anything in this Article 22 to the contrary, and pursuant to 18 C.F.R. section 1b.20, if FERC or its staff, during the course of an investigation or otherwise, requests information from one of the Parties that is otherwise required to be maintained in confidence pursuant to this Agreement or the NYISO OATT, the Party shall provide the requested information to FERC or its staff, within the time provided for in the request for information. In providing the information to FERC or its staff, the Party must, consistent with 18 C.F.R. section 388.112, request that the information be treated as confidential and non-public by FERC and its staff and that the information be withheld from public disclosure. Parties are prohibited from notifying the other Parties to this Agreement prior to the release of the Confidential Information to the Commission or its staff. The Party shall notify the other Parties to the Agreement when it is notified by FERC or its staff that a request to release Confidential Information has been received by FERC, at which time the Parties may respond before such information would be made public, pursuant to 18 C.F.R. section 388.112. Requests from a state regulatory body conducting a confidential investigation shall be treated in a similar manner if consistent with the applicable state rules and regulations. A Party shall not be liable for any losses, consequential or otherwise, resulting from that Party divulging Confidential Information pursuant to a FERC or state regulatory body request under this paragraph.

  • Return or Destruction of Confidential Information If an Interconnection Party provides any Confidential Information to another Interconnection Party in the course of an audit or inspection, the providing Interconnection Party may request the other party to return or destroy such Confidential Information after the termination of the audit period and the resolution of all matters relating to that audit. Each Interconnection Party shall make Reasonable Efforts to comply with any such requests for return or destruction within ten days of receiving the request and shall certify in writing to the other Interconnection Party that it has complied with such request.

  • Interested Party for the purpose of filing a dispute relating to a solicitation, as used in this section, means an actual or prospective bidder or offeror whose direct economic interest would be affected by the award of a Contract or by the failure to award a Contract.

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