Joint Proposals for Third Party Funding Sample Clauses

Joint Proposals for Third Party Funding. As mutually beneficial opportunity presents, COMPANY and ROWAN may elect to submit joint proposals to other funding agencies for research or development. One of the entities will be designated as the lead organization, consistent with the guidelines of the funding agency. The lead organization shall obtain the approval of the other organization in writing prior to including their name, personnel or resources in any such proposal. The lead organization will develop a subcontract with the secondary organization in such activities.
AutoNDA by SimpleDocs

Related to Joint Proposals for Third Party Funding

  • Exclusions and Limitations for Third Party Software SUBJECT TO THE EXCLUSION OF DAMAGES STATED IN SECTION 9.2 AND WITH RESPECT TO THIRD PARTY SOFTWARE, UNDER NO CIRCUMSTANCES AND REGARDLESS OF THE NATURE OF ANY CLAIM SHALL SAP OR ITS LICENSORS’ BE LIABLE FOR AN AMOUNT IN EXCESS OF THE PAID LICENSE FEES FOR THE THIRD PARTY SOFTWARE DIRECTLY CAUSING THE DAMAGES.

  • Application of Funding Techniques to Programs 6.3.1 The State shall apply the following funding techniques when requesting Federal funds for the component cash flows of the programs listed in sections 4.2 and 4.3 of this Agreement.

  • Third-Party Applications Oracle or third party providers may offer Third Party Applications. Except as expressly set forth in the Estimate/Order Form, Oracle does not warrant any such Third Party Applications, regardless of whether or not such Third Party Applications are provided by a third party that is a member of an Oracle partner program or otherwise designated by Oracle as “Built For NetSuite,” "certified," "approved" or “recommended.” Any procurement by Customer of such Third Party Applications or services is solely between Customer and the applicable third party provider. Customer may not use Third Party Applications to enter and/or submit transactions to be processed and/or stored in the NetSuite CPQ, unless Customer has procured the applicable subscription to the NetSuite CPQ for such use and access. Oracle is not responsible for any aspect of such Third Party Applications that Customer may procure or connect to through the NetSuite CPQ, or any interoperation, descriptions, promises, or other information related to the foregoing. If Customer installs or enables Third Party Applications for use with the NetSuite CPQ, Customer agrees that Oracle may enable such third party providers to access Customer Data for the interoperation of such Third Party Applications with the NetSuite CPQ, and any exchange of data or other interaction between Customer and a third party provider is solely between Customer and such third party provider pursuant to a separate privacy policy or other terms governing Customer’s access to or use of the Third Party Applications. Oracle shall not be responsible for any disclosure, modification or deletion of Customer Data resulting from any such access by Third Party Applications or third party providers. No procurement of such Third Party Applications is required to use the NetSuite CPQ. If Customer was referred to Oracle by a member of one of Oracle’s partner programs, Customer hereby authorizes Oracle to provide such member or its successor entity with access to Customer’s business information related to the procurement and use of the NetSuite CPQ pursuant to this Agreement, including but not limited to User names and email addresses, support cases and billing/payment information.

  • Technology Research Analyst Job# 1810 General Characteristics Maintains a strong understanding of the enterprise’s IT systems and architectures. Assists in the analysis of the requirements for the enterprise and applying emerging technologies to support long-term business objectives. Responsible for researching, collecting, and disseminating information on emerging technologies and key learnings throughout the enterprise. Researches and recommends changes to foundation architecture. Supports research projects to identify and evaluate emerging technologies. Interfaces with users and staff to evaluate possible implementation of the new technology in the enterprise, consistent with the goal of improving existing systems and technologies and in meeting the needs of the business. Analyzes and researches process of deployment and assists in this process.

  • Additional Information for Product Development Projects Outcome of product development efforts, such copyrights and license agreements. • Units sold or projected to be sold in California and outside of California. • Total annual sales or projected annual sales (in dollars) of products developed under the Agreement. • Investment dollars/follow-on private funding as a result of Energy Commission funding. • Patent numbers and applications, along with dates and brief descriptions.  Additional Information for Product Demonstrations: • Outcome of demonstrations and status of technology. • Number of similar installations. • Jobs created/retained as a result of the Agreement.

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)

  • Application and Submission Information In addition to the application and submission language discussed in PART II: Section I, you must include the following in your application:

  • Technical Proposals Technical proposal information will be streamlined, e.g., the Government anticipates written proposals consisting of thirty (30) pages or less stating compliance or exception to requirements, risks, assumptions and conflict of interest issues. Proposals shall not merely restate PWS/SOO requirements. Written technical proposals shall normally address: * Technical Approach and descriptive narrative of the contractor's understanding of the requested effort * PWS in response to a SOO * Integrated Master Plan (if applicable) * Integrated Master Schedule (if applicable) * Key Personnel Assigned * Quantities/Hours of Personnel by Labor Categories and narrative justification (if applicable) * Other Direct Costs (ODCs) (materials and supplies, travel, training, etc.(quantities and types only)) * Period of Performance * Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI) * Security (including clearance level) * Teaming Arrangement (including subcontracting; identify new ACAs) * Small Business Plan (if a large business) * Other Pertinent Data, such as assumptions made.

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