AREAS OF COLLABORATION The School will collaborate under Xxxx Innovation Mission to establish, operate and support ATL in India within the school premises with financial support from NITI Aayog.
PRINCIPLES OF COLLABORATION The parties agree to adopt the following principles when carrying out the Project (Principles):
Collaboration We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.
Limitations of Use The Services and Atlantic Broadband Equipment, including any firmware or software embedded in Atlantic Broadband Equipment or used to provide the Services, are protected by trademark, copyright, and/or other intellectual property laws and international treaty provisions. You are granted a limited, non-sublicensable, non- transferable revocable license to use such firmware and software in object code form (without making any modification thereto) strictly in accordance with this Agreement. You acknowledge and understand that you are not granted any other license to use the firmware or software embedded in Atlantic Broadband Equipment or used to provide the Services. You expressly agree that you will use Atlantic Broadband Equipment exclusively in connection with the Services. You shall not reverse, compile, disassemble, or reverse engineer or otherwise attempt to derive the source code from the binary code of the firmware or software. If you decide to use the Services through an interface device not provided by Atlantic Broadband, which Atlantic Broadband reserves the right to prohibit in particular cases or generally, you warrant and represent that you possess all required rights to use that interface device with the Services, including all software and firmware licenses. You will indemnify and hold harmless Atlantic Broadband against any and all liability arising out of your use of such interface device with the Services.
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.
Notification of Modifications of Licensed Materials From time to time Publisher may add, change, or modify portions of the Licensed Materials, or migrate the Licensed Materials to other formats. When such changes, modifications, or migrations occur, the Licensor shall give notice of any such changes to Licensee as soon as is practicable, but in no event less than sixty (60) days in advance of modification. Such a notice may also be given directly by the Publisher to the Licensee. If any of the changes, modifications, or migrations renders the Licensed Materials substantially less useful to the Licensee, the Participating Institutions or their Authorized Users, the Licensee may seek to terminate this Agreement for breach pursuant to the termination provisions of this Agreement in Section XI, below.
Expansive Protocols Where the capability exists, originating or terminating traffic reroutes may be implemented by either party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the parties.
Collaboration on Compliance and Enforcement A Competent Authority will notify the other Competent Authority when the first-mentioned Competent Authority has reason to believe that an error may have led to incorrect or incomplete information reporting or there is non-compliance by a Reporting Financial Institution with the applicable reporting requirements and due diligence procedures consistent with the Common Reporting Standard. The notified Competent Authority will take all appropriate measures available under its domestic law to address the errors or non-compliance described in the notice.
License Types The following License Types may be offered with respect to individual Software products or product families. Additional license types may be specified with respect to certain products or product groups as set forth in the Product Specific Terms. The License Type will be specified in an LSDA.
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.
