MIPS ARCHITECTURE LICENSE DOCUMENTATION Sample Clauses

MIPS ARCHITECTURE LICENSE DOCUMENTATION. Subject to the terms and conditions of this Agreement and upon payment by WEITEK to MIPS of the fees set forth in section 3.1.1 MIPS shall grant to WEITEK and WEITEK shall accept a worldwide, personal, non-exclusive, fully-paid, non-transferable, non-assignable and revocable right and license, to use, modify, copy and distribute, all for Internal Use only, without any right to market, copy or distribute outside of WEITEK, MIPS Architecture License Documentation as set forth in Exhibit A.
AutoNDA by SimpleDocs

Related to MIPS ARCHITECTURE LICENSE DOCUMENTATION

  • Product Documentation You should review the policy documents carefully to ensure they accurately reflect the cover, conditions, limits, and other terms that you require. Particular attention should be paid to policy conditions and warranties as failure to comply with these could invalidate your policy. It is important that you retain and keep safely all documents associated with your policy so that you can refer to them in the event of a claim.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

  • Technical Documentation Prior to commencement of the Tests on Completion, the Contractor shall supply to the Engineer the technical documentation as specified in the Employer’s Requirements. The Works or Section shall not be considered to be completed for the purposes of taking- over under sub-clause 10.1 [Taking Over of the Works and Sections] until the Engineer has received the technical documentation as defined in this sub-clause 5.7, the "history file" including design calculations and certain certification as well as any other documents required to meet the CE Marking requirements.

  • Software License Subject to the terms of this Agreement, Viasat grants to you a personal, non-exclusive, non-assignable and non-transferable license to use and display the software provided by or on behalf of Viasat (including any updates) only for the purpose of accessing the Service ("Software") on any computer(s) on which you are the primary user or which you are authorized to use. Our Privacy Policies provide important information about the Software applications we utilize. Please read the terms very carefully, as they contain important disclosures about the use and security of data transmitted to and from your computer. Unauthorized copying of the Software, including, without limitation, software that has been modified, merged or included with the Software, or the written materials associated therewith, is expressly forbidden. You may not sublicense, assign, or transfer this license or the Software except as permitted in writing by Viasat. Any attempt to sublicense, assign or transfer any of the rights, duties or obligations under this license is void and may result in termination by Viasat of this Agreement and the license. You agree that you shall not copy or duplicate or permit anyone else to copy or duplicate any part of the Software, or create or attempt to create, or permit others to create or attempt to create, by reverse engineering or otherwise, the source programs or any part thereof from the object programs or from other information made available under this Agreement.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • TECHNICAL SUPPORT SERVICES 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Software Licenses Seller has all necessary licenses to use all material third-party software used in connection with the Purchased Assets, and to Sellers’ knowledge, Sellers’ use of third-party software does not infringe the rights of any Person or Entity.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

  • Manufacturing Technology Transfer With respect to each Technology Transfer Product, upon AbbVie’s written request after the Inclusion Date for the Included Target to which such Technology Transfer Product is Directed, Morphic shall effect a full transfer to AbbVie or its designee (which designee may be an Affiliate or a Third Party manufacturer) of all Morphic Know-How and Joint Know-How relating to the then-current process for the Manufacture of such Technology Transfer Product (the “Manufacturing Process”) and to implement the Manufacturing Process at facilities designated by AbbVie (such transfer and implementation, as more fully described in this Section 5.3, the “Manufacturing Technology Transfer”). To assist with the Manufacturing Technology Transfer, Morphic will make its personnel reasonably available to AbbVie during normal business hours for up to [***] FTE hours with respect to each Included Target (in each case, free of charge to AbbVie) to transfer and implement the Manufacturing Process under this Section 5.3. Thereafter, if requested by AbbVie, Morphic shall continue to perform such obligations; provided, that AbbVie will reimburse Morphic for its full-time equivalent (FTE) costs (for clarity, in excess of [***] FTE hours) and any reasonable and verifiable out-of-pocket costs incurred in providing such assistance. CERTAIN CONFIDENTIAL INFORMATION CONTAINED IN THIS DOCUMENT, MARKED BY [***], HAS BEEN OMITTED BECAUSE IT IS NOT MATERIAL AND WOULD LIKELY CAUSE COMPETITIVE HARM TO THE COMPANY IF PUBLICLY DISCLOSED.

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!