Related Research Sample Clauses

Related Research. Sponsor understands and agrees that nothing in this Agreement interferes with UMD’s right to conduct research similar or related to the subject of the Research Project (“Related Research”), provided that such Related Research is conducted separately from the Research Project and does not involve the unauthorized use of Sponsor Confidential Information. Sponsor further understands and agrees that nothing in this Agreement grants Sponsor any rights to intellectual property that is conceived of or reduced to practice in the performance of any Related Research. Payment and Payment Schedule. Sponsor hereby awards to UMD a cost reimbursement award in an amount not to exceed $XXXX. UMD will invoice the Sponsor monthly for costs incurred in accordance with the Research Project Budget as shown in Attachment 2. OR Sponsor will pay UMD the total firm fixed price amount of $XXXXXX (“Award Amount”) below in accordance with the following installment schedule:
View SourceView Similar (4)
Related Research. Sponsor understands and agrees that nothing in this Agreement interferes with UMD’s right to conduct research similar or related to the subject of the Research Project (“Related Research”), provided that such Related Research is conducted separately from the Research Project and does not involve the unauthorized use of Sponsor Confidential Information. Sponsor further understands and agrees that nothing in this Agreement grants Sponsor any rights to intellectual property that is conceived of or reduced to practice in the performance of any Related Research.
View SourceView Similar (2)
Related Research. In the automotive domain, ISO 26262 [4] is the functional safety standard. Some critical functions are supposed to work independently on a single core with their dedicated resources. When this is not the case, partitioning and shared resource techniques are used. ▇▇▇▇ [5] state: “The safety assurance argument that these techniques should address is that the presented items of evidence should show sufficiently spatial and temporal independence between each partition.” With the introduction of multi-core computers, multiple partitions may run concurrently on a single computing card, all accessing memory or I/O interfaces at the same time and needing to share processing time and resources in a ‘safe’ way. Kotaba [6] analyzed the low-level temporal effect from sharing the on-chip resources that impact the execution time. In the “multicore domain, the applications compete for resource access, typically arbitrated in a non-explicit manner by the specific hardware implementation. This causes non- deterministic temporal delays to the execution”. They analyzed the effects and suggest mitigation techniques for resources such as system bus, bridges, memory bus and controller, memory (DRAM), shared cache, local cache, Translation Lookaside Buffer, addressable devices, pipeline stages, or logical units. In SPEEDS [7] a formal meta-modeling language and the syntax of component contracts were developed and implemented. These contracts define the premises and promises of the component regarding its behavior in a specific way as well as an attribute designating its viewpoint. Another project that pursued this idea, ▇▇▇▇▇ [8], defined the ▇▇▇▇▇ Meta-Model (CMM), which includes the concept of ‘rich’ components that can be connected and integrated into hierarchies. Different kinds of rich components are possible depending on the perspective, such as operational actors, functions, logical components, or technical components. The CMM is based on the integration of component-based design with contracts based on input from the SPEEDS project, EAST-ADL2 (traceability, verification and validation) from the ATESST project, and its own ▇▇▇▇▇ Requirements Management Meta-Model (RMM). All these propose a metamodeling language for components dealing with safety-critical systems. From another perspective, the FRESCOR project [9] (Framework for Real-time Embedded Systems based on COntRACTS) proposed contract-based resource management in distributed systems. It uses service contracts as a ...
View Source
Related Research. Company understands and agrees that nothing in this Agreement interferes with the right of UMD to conduct research similar or related to the subject of the Project, provided that such related research is conducted separately from and/or under the supervision and control of a researcher not involved in the Project. Company further understands and agrees that nothing in this Agreement grants Company any rights to intellectual property that shall be conceived of, reduced to practice, or used in the performance of such related research.
View Source
Related Research. The protocol specification allows a comparison with ex- isting membership protocols. The TTP specification [16] includes a membership service which imposes no direct overhead on the network. This is achieved instead by plac- ing the load of the failure detection on the CRC mecha- nisms and by requiring the membership state to be explicitly broadcasted in order to allow the reintegration of previously moment, before reconfiguration, there are edges directed to each node, therefore agreement is ensured.
View Source

Related to Related Research

  • Research Primary Investigator as part of a multi-site study (25 points) • Co-Investigator as part of a multi-site study (20 points) • Primary Investigator of a facility/unit based research study (15 points) • Co-Investigator of a facility/unit based research study (10 points) • Develops a unit specific research proposal (5 points) • Conducts a literature review as part of a research study (5 points)

  • Technology Research Analyst Job# 1810 General Characteristics

  • Research Funding (a) During each Collaboration Term and in connection with any wind-down activities contemplated by Section 13.4. Gilead shall reimburse Hookipa for all Out-of-Pocket Costs actually incurred (with no markup) by Hookipa in connection with the applicable Program, to the extent specifically contemplated in the applicable Research Plan and in accordance with the applicable Research Budget. Gilead shall reimburse the undisputed amount of such Out-of-Pocket Costs incurred in a [***] within [***] days after receipt from Hookipa of an invoice therefor issued within [***] days after the end of such [***]. (b) During each Collaboration Term for a Program, Gilead shall reimburse Hookipa at the FTE Rate for the costs of any FTEs (not to exceed the number of FTEs specified in the applicable Research Plan for such Program for any period without first obtaining, in each case, Gilead’s prior written consent) actually performing activities allocated to Hookipa under such Research Plan. Hookipa shall provide to Gilead, within [***] days after the end of each [***] during each Collaboration Term, a report indicating the number of FTEs actually provided by Hookipa with respect to each Program during such [***], Hookipa shall use standard industry systems and processes to record the number of hours and FTEs actually applied to each Program, which systems and processes shall be consistently and equitably applied to all Hookipa research programs with Third Parties. Gilead shall reimburse Hookipa the undisputed amount for such FTE costs incurred in a [***] within [***] days after receipt from Hookipa of an invoice therefor issued within [***] days after the end of each [***]. (c) For clarity, Gilead shall not be obligated to reimburse Hookipa for any costs or expenses incurred by Hookipa in the course of its activities under the Programs, other than: (i) those costs and expenses expressly identified in this Section 9.6 or elsewhere in this Agreement; (ii) reimbursement for the supply of Licensed Products to Gilead in accordance with the terms of any supply agreement entered into by the Parties pursuant to Section 7.2; or (iii) any other costs and expenses approved by Gilead in writing in advance.

  • Development Records Each Party shall maintain complete, current and accurate records of all Development activities conducted by it hereunder, and all data and other information resulting from such activities. Such records shall fully and properly reflect all work done and results achieved in the performance of the Development activities in good scientific manner appropriate for regulatory and patent purposes. Each Party shall document all non-clinical studies and Clinical Trials in formal written study reports according to Applicable Laws and national and international guidelines (e.g., ICH, cGCP, cGLP, and cGMP).

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