PROJECT RESULTS AND PROJECT IP Sample Clauses

PROJECT RESULTS AND PROJECT IP. The data and results of the Project Results is as stated in Item 5 of Schedule 1, unless otherwise agreed in writing between the Parties. Unless otherwise specified in Item 5 Schedule 1, the Parties agree that all rights, title and interest in the Project IP will be owned solely by the Party, or jointly by the Parties, that contribute to its development or creation and, in the case of jointly owned Project IP, the Parties will own the Project IP in shares proportionate to their respective intellectual contributions to the development or creation of that Intellectual Property. In the case of jointly owned Project IP, neither Party may: grant a licence of its share of any Project IP; or assign its share of the Project IP, without the written consent of the other Party, which will not be unreasonably withheld. The Parties agree that copyright in a student thesis will be owned by the student but the Party responsible for the student will ensure that the student enters into a written agreement which is consistent with this Agreement and the terms of this clause 5 before the student commences any Project activities. Each Party agrees to promptly provide written notice to the other Party of any Project IP that may have potential commercial value on becoming aware of any such Project IP. The Parties will consult and decide what (if any) measures should be taken to protect the Project IP and negotiate in good faith and using all best endeavours to agree the terms of any program of commercialisation arising from the Project IP so as to fairly share in any commercial return associated with the Project and the Project IP. Having regard to any requirements to protect potentially commercially valuable Project IP, each Party grants to each other Party a non-exclusive, non-transferable, perpetual, royalty free, worldwide licence to use the Project IP it owns for: non-commercial research, education and training purposes; and publication purposes (subject to clause 7 of this Agreement). The Parties are committed to appropriate recognition of contributions to invention and exploitation of Intellectual Property for the benefit of the Australian community. BACKGROUND IP The Parties agree that the ownership of Background IP is not affected by this Agreement and that all Background IP remains the property of the Party that makes it available for the purpose of carrying out the Project. No representations or warranties are made or given in relation to Background IP, however, each...
Sample 1Sample 2Sample 3See All (11)
AutoNDA by SimpleDocs
PROJECT RESULTS AND PROJECT IP. 5.1 All title, rights and interests in and relating to the Project Results and PIP will vest in and be owned by You on payment of the Fees.
Sample 1
PROJECT RESULTS AND PROJECT IP. 5.1 Unless otherwise specified in Item 5 of Schedule 1, the Parties agree that all rights, title and interest in the Project IP will be owned solely by the Party, or jointly by the Parties, that contribute to its development or creation and, in the case of jointly owned Project IP, the Parties will own the Project IP in shares proportionate to their respective intellectual contributions to the development or creation of that Intellectual Property.
Sample 1

Related to PROJECT RESULTS AND PROJECT IP

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • Research Project 3.1 These Materials and Data will be used by Recipient's PI solely in connection with the Research Project, as named and described in the attached research application (insert Research Project name below):

  • Project Information Except for confidential information designated by the City as information not to be shared, Consultant agrees to share Project information with, and to fully cooperate with, those corporations, firms, contractors, public utilities, governmental entities, and persons involved in or associated with the Project. No information, news, or press releases related to the Project, whether made to representatives of newspapers, magazines, or television and radio stations, shall be made without the written authorization of the City’s Project Manager.

  • Project Background 6.1.1. Brief description of Contracting Agency’s project background and/or situation leading to this Project

  • Course Materials The adoption of any course materials, print or electronic, after a Course Agreement is signed will require an agreed and signed addendum.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Intellectual Property/Work Product Ownership All data, technical information, materials first gathered, originated, developed, prepared, or obtained as a condition of this agreement and used in the performance of this agreement -- including, but not limited to all reports, surveys, plans, charts, literature, brochures, mailings, recordings (video or audio), pictures, drawings, analyses, graphic representations, software computer programs and accompanying documentation and printouts, notes and memoranda, written procedures and documents, which are prepared for or obtained specifically for this agreement, or are a result of the services required under this grant -- shall be considered "work for hire" and remain the property of the State of Vermont, regardless of the state of completion unless otherwise specified in this agreement. Such items shall be delivered to the State of Vermont upon 30- days notice by the State. With respect to software computer programs and / or source codes first developed for the State, all the work shall be considered "work for hire,” i.e., the State, not the Party (or subcontractor or sub-grantee), shall have full and complete ownership of all software computer programs, documentation and/or source codes developed. Party shall not sell or copyright a work product or item produced under this agreement without explicit permission from the State of Vermont. If Party is operating a system or application on behalf of the State of Vermont, Party shall not make information entered into the system or application available for uses by any other party than the State of Vermont, without prior authorization by the State. Nothing herein shall entitle the State to pre-existing Party’s materials. Party acknowledges and agrees that should this agreement be in support of the State's implementation of the Patient Protection and Affordable Care Act of 2010, Party is subject to the certain property rights provisions of the Code of Federal Regulations and a Grant from the Department of Health and Human Services, Centers for Medicare & Medicaid Services. Such agreement will be subject to, and incorporates here by reference, 45 CFR 74.36, 45 CFR 92.34 and 45 CFR 95.617 governing rights to intangible property.

  • Security of All Software Components Supplier will inventory all software components (including open source software) used in Deliverables, and provide such inventory to Accenture upon request. Supplier will assess whether any such components have any security defects or vulnerabilities that could lead to a Security Incident. Supplier will perform such assessment prior to providing Accenture with access to such software components and on an on-going basis thereafter during the term of the Agreement. Supplier will promptly notify Accenture of any identified security defect or vulnerability and remediate same in a timely manner. Supplier will promptly notify Accenture of its remediation plan. If remediation is not feasible in a timely manner, Supplier will replace the subject software component with a component that is not affected by a security defect or vulnerability and that does not reduce the overall functionality of the Deliverable(s).

  • Ownership Title to Project Deliverables This clause shall apply where Contractor is commissioned by the Authorized User to furnish project deliverables as detailed in the Purchase Order.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

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