Licenses From Agilent to Keysight Sample Clauses

Licenses From Agilent to Keysight 
AutoNDA by SimpleDocs

Related to Licenses From Agilent to Keysight

  • Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Certification Regarding Prohibition of Boycotting Israel (Tex. Gov. Code 2271) 5 Certification Regarding Prohibition of Contracts with Certain Foreign-Owned Companies (Tex. Gov. 5 Code 2274) 5 Certification Regarding Prohibition of Discrimination Against Firearm and Ammunition Industries (Tex.

  • RELEASE OF GENERAL INFORMATION TO THE PUBLIC AND MEDIA NASA or Partner may, consistent with Federal law and this Agreement, release general information regarding its own participation in this Agreement as desired. Pursuant to Section 841(d) of the NASA Transition Authorization Act of 2017, Public Law 115-10 (the "NTAA"), NASA is obligated to publicly disclose copies of all agreements conducted pursuant to NASA's 51 U.S.C. §20113(e) authority in a searchable format on the NASA website within 60 days after the agreement is signed by the Parties. The Parties acknowledge that a copy of this Agreement will be disclosed, without redactions, in accordance with the NTAA.

  • Certain Additional Actions Regarding Intellectual Property If any Event of Default shall have occurred and be continuing, upon the written demand of the Collateral Agent, each Pledgor shall execute and deliver to the Collateral Agent an assignment or assignments of the registered Patents, Trademarks and/or Copyrights and Goodwill and such other documents as are necessary or appropriate to carry out the intent and purposes hereof. Within five (5) Business Days of written notice thereafter from the Collateral Agent, each Pledgor shall make available to the Collateral Agent, to the extent within such Pledgor’s power and authority, such personnel in such Pledgor’s employ on the date of the Event of Default as the Collateral Agent may reasonably designate to permit such Pledgor to continue, directly or indirectly, to produce, advertise and sell the products and services sold by such Pledgor under the registered Patents, Trademarks and/or Copyrights, and such persons shall be available to perform their prior functions on the Collateral Agent’s behalf.

  • Inventions Retained and Licensed I have attached hereto, as Exhibit A, a list describing all inventions, original works of authorship, developments, improvements, and trade secrets which were made by me prior to my employment with the Company (collectively referred to as “Prior Inventions”), which belong to me, which relate to the Company’s proposed business, products or research and development, and which are not assigned to the Company hereunder; or, if no such list is attached, I represent that there are no such Prior Inventions. If in the course of my employment with the Company, I incorporate into a Company product, process or machine a Prior Invention owned by me or in which I have an interest, the Company is hereby granted and shall have a nonexclusive, royalty-free, irrevocable, perpetual, worldwide license to make, have made, modify, use and sell such Prior Invention as part of or in connection with such product, process or machine.

  • USE OF NASA NAME AND NASA EMBLEMS A. NASA Name and Initials Partner shall not use "National Aeronautics and Space Administration" or "NASA" in a way that creates the impression that a product or service has the authorization, support, sponsorship, or endorsement of NASA, which does not, in fact, exist. Except for releases under the "Release of General Information to the Public and Media" Article, Partner must submit any proposed public use of the NASA name or initials (including press releases and all promotional and advertising use) to the NASA Associate Administrator for the Office of Communications or designee ("NASA Communications") for review and approval. Approval by NASA Office of Communications shall be based on applicable law and policy governing the use of the NASA name and initials. B. NASA Emblems Use of NASA emblems (i.e., NASA Seal, NASA Insignia, NASA logotype, NASA Program Identifiers, and the NASA Flag) is governed by 14 C.F.R. Part 1221. Partner must submit any proposed use of the emblems to NASA Communications for review and approval.

  • Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? No

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • Dissemination of Research Findings and Acknowledgement of Controlled-Access Datasets Subject to the NIH GDS Policy

  • Certification Regarding Entire TIPS Agreement for Part 1 and Part 2 Contracts 5 This is a two part solicitation. Part 1 is solicited for TIPS sales that are not considered a "public work" construction (1) The TIPS solicitation document resulting in the Agreement; (2) Any addenda or clarifications issued in relation to the corresponding TIPS solicitation; (3) All solicitation information provided to Vendor by TIPS through the TIPS eBid System; (3) Vendor’s entire proposal response to the corresponding TIPS solicitation including all accepted required attachments, acknowledged notices and certifications, accepted negotiated terms, accepted pricing, accepted responses to questions, and accepted written clarifications of Vendor’s proposal, and; any properly included attachments to the TIPS Contract. Does Vendor agree? Yes, Vendor agrees TIPS Members often turn to TIPS Contracts for ease of use and to receive discounted pricing. Vendor must respond with a percentage from 0%-100%. The percentage discount that you input below will be applied to your Part 1 "Catalog Pricing", as defined in the solicitation, for all TIPS Sales made during the life of the contract. You cannot alter this percentage discount once the solicitation legally closes. You will always be required to discount every TIPS Sale by the percentage included below with the exception of limited goods/services specifically identified and excluded from this discount in Vendor’s original proposal. If you add goods or services to your "Catalog Pricing" during the life of the contract, you will be required to sell those new items with this discount applied.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

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