Minimum Vendor License Requirements Vendor shall maintain, in current status, all federal, state, and local licenses, bonds and permits required for the operation of the business conducted by Vendor. Vendor shall remain fully informed of and in compliance with all ordinances and regulations pertaining to the lawful provision of goods or services under the TIPS Agreement. TIPS and TIPS Members reserve the right to stop work and/or cancel a TIPS Sale or terminate this or any TIPS Sale Supplemental Agreement involving Vendor if Vendor’s license(s) required to perform under this Agreement or under the specific TIPS Sale have expired, lapsed, are suspended or terminated subject to a 30‐day cure period unless prohibited by applicable statue or regulation.
License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.
PRODUCT SUPPORT Partners may provide support for Products and other value-added services, and Partner is responsible for the performance of any services it provides. If Customer purchases Microsoft Support Services through a Partner, Microsoft will be responsible for the performance of those services subject to the terms of this Agreement.
AUDIT OF LICENSED PRODUCT USAGE Contractor shall have the right to periodically audit, no more than annually, at Contractor’s expense, use of licensed Product at any site where a copy of the Product resides provided that: (i) Contractor gives Licensee(s) at least thirty (30) days advance written notice, (ii) such audit is conducted during such party’s normal business hours, (iii) the audit is conducted by an independent auditor chosen on mutual agreement of the parties. Contractor shall recommend a minimum of three (3) auditing/accounting firms from which the Licensee will select one (1). In no case shall the Business Software Alliance (BSA), Software Publishers Association (SPA), Software and Industry Information Association (SIIA) or Federation Against Software Theft (FAST) be used directly or indirectly to conduct audits, or be recommended by Contractor; (iv) Contractor and Licensee are each entitled to designate a representative who shall be entitled to participate, and who shall mutually agree on audit format, and simultaneously review all information obtained by the audit. Such representatives also shall be entitled to copies of all reports, data or information obtained from the audit; and (v) if the audit shows that such party is not in compliance, Licensee shall be required to purchase additional licenses or capacities necessary to bring it into compliance and shall pay for the unlicensed capacity at the NYS Net Price in effect at time of audit, or if none, then at the Contractor’s U.S. Commercial list price. Once such additional licenses or capacities are purchased, Licensee shall be deemed to have been in compliance retroactively, and Licensee shall have no further liability of any kind for the unauthorized use of the software.
Sublicense Requirements Any Sublicense:
(A) is subject to this Agreement;
(B) will reflect that any sublicensee will not further sublicense;
(C) will prohibit sublicensee from paying royalties to an escrow or other similar account;
(D) will expressly include the provisions of Sections 8, 9, and 10 for the benefit of Stanford; and
(E) will include the provisions of Section 4.4 and require the transfer of all the sublicensee’s obligations to *****, including the payment of royalties specified in the Sublicense, to Stanford or its designee, if this Agreement is terminated. If the sublicensee is a spin-out from *****, ***** must guarantee the sublicensee’s performance with respect to the payment of Stanford’s share of Sublicense royalties.
Marking of Licensed Products To the extent commercially feasible and consistent with prevailing business practices, Company shall xxxx, and shall cause its Affiliates and Sublicensees to xxxx, all Licensed Products that are manufactured or sold under this Agreement with the number of each issued patent under the Patent Rights that applies to such Licensed Product.
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.
Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.
(b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program.
(c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only.
(d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use.
(e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient.
(f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor.
(g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient.
(h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes.
(i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5.
(j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.
Product Supply 5.1 In the event that Eisai notifies Radius of its desire to purchase bulk substance of Compound from Radius, Radius shall supply Eisai with all amount of such bulk substance of Compound, which meets specifications for the Product determined by Radius in the course of its Development activities pursuant to this Agreement, required by Eisai for commercial sales of Product in Japan With respect to Eisai clinical development activities for Product in Japan, upon Eisai’s request, Radius shall supply Eisai the bulk substance of Compound for * Confidential Treatment Requested by the Registrant. Redacted Portion Filed Separately with the Commission. the conduct of the Eisai Development activities in the amounts and at the times determined by the SC, having reference to the quantity of the bulk substance of Compound required for clinical trials in Japan. Radius shall charge [*] for applicable bulk substance of Compound. Radius shall ship such bulk substance of Compound, FOB point of manufacturing.
5.2 In the event that Eisai notifies Radius of its desire to purchase Semi-Product from Radius which meets specifications determined by Radius in the course of its Development activities pursuant to this Agreement, Radius shall supply Eisai with all amount of Semi-Product required by Eisai for commercial sales of Product in Japan. With respect to Eisai clinical development activities for Product in Japan, upon Eisai’s request, Radius shall supply Eisai Semi-Product for the conduct of the Eisai Development activities in the amounts and at the times determined by the SC, having reference to the quantity of Semi-Product required for clinical trials in Japan. Radius shall charge [*] for Semi-Product. Radius shall ship such Semi-Product, FOB point of manufacturing.
5.3 The Parties agree that they shall, in good faith, discuss, negotiate and execute necessary agreements containing mutually acceptable terms, including but not limited to, a supply agreement for either bulk substance of Compound or Semi-Product as well as a quality control agreement of either bulk substance of Compound or Semi-Product, in the event that Eisai notifies Radius as set forth in Article 5.1 or 5.2.
5.4 As manufacturer of the Product, Radius shall be responsible for: (a) the control of the quality of the Product promoted and sold under the Radius trademarks; as provided in Article 2.3; and (b) ensuring that all bulk substance of Compound or Semi-Product supplied to Eisai pursuant to this Article 5 shall be manufactured in accordance with the applicable good manufacturing practices (GMP) and shall meet the then applicable specifications for the bulk substance of Compound or Semi-Product; and Radius warrants that all bulk substance of Compound or Semi-Product supplied to Eisai pursuant to this Article 5 shall be manufactured in accordance with the applicable GMP and * Confidential Treatment Requested by the Registrant. Redacted Portion Filed Separately with the Commission. shall meet the then applicable specifications for the bulk substance of Compound or Semi-Product and will be free from defects in material and workmanship. Radius shall resolve any product liability issues in the Territory relating to the Product and shall resolve any product liability issues in Japan relating to the Product or the bulk substance of Compound or Semi-Product, as the case may be, supplied to Eisai pursuant to this Article 5 in the event and to the extent related to a breach of the warranty set forth in Article 5.4(b) at its own expense and subject to Article 5.5.
5.5 Radius’ obligations with respect to product liability in the Territory and Japan shall include the following responsibilities, each to be taken at Radius’ expense:
(a) Radius shall report, at its expense, to appropriate authorities, in accordance with local requirements, all adverse events related to use of the Product in the Territory or Japan. Eisai shall provide to Radius, upon Radius’ request, reasonable assistance in connection with the reporting of all of adverse events, responding to safety queries and assessing safety issues, in each case, to the extent related to the Product in Japan. Adverse events shall be recorded in a single, centralized database, which shall be held and owned by Radius. Radius will provide, upon request by Eisai, any safety information in Radius’ control and reasonably required by Eisai in connection with the development and commercialization of the Product in Japan and all reasonable assistance in responding to safety queries related to the Product and in assessing safety issues related to the Product in Japan. Details of safety reporting activities relating to the Product will be addressed in a pharmacovigilance contract, which the Parties shall enter into after the Effective Date.
(b) In the event that (i) Radius determines that an event, incident, or circumstance may result in the need for a recall or other removal of the Product or any lot or lots thereof from the market; (ii) any regulatory authority in the Territory threatens to remove a Product from the market; or (iii) any regulatory authority in the Territory requires distribution of a “Dear Doctor” letter or its equivalent regarding the use of Product, Radius shall promptly advise Eisai in writing, and shall provide Eisai with copies of all relevant correspondence, notices and the like. Notwithstanding anything the contrary herein, Radius shall have final authority to make all decisions relating to any recall, market withdrawal or other corrective action with respect to the Product in the Territory. After establishing SC pursuant to Article 3.5, all decisions relating to any recall, market withdrawal or other corrective action with respect to the Product shall be decided by the SC as set forth in Article 3.6; provided that in the event that the Parties take different positions with respect to recall, market withdrawal or other corrective action with respect to the Product, then Radius shall have the right to cease supplying bulk substance of Compound or Semi-Product to Eisai for Japan if, after good faith discussions with Eisai, Radius reasonably believes that that continued supply to Eisai exposes Radius to liability as a result of its decision with respect to the Territory. If Radius elects to cease supply, it will terminate supply in an orderly manner, as soon as practical and in accordance with a schedule agreed to by Eisai and Radius. In the event of a recall, market withdrawal or other corrective action with respect to the Product in Japan, and at Radius’ request, Eisai shall provide reasonable assistance to Radius, at Radius’ cost and expense, in conducting any such recall, market withdrawal or other corrective action with respect to the Product in Japan.
5.6 THE WARRANTY IN SECTION 5.4(b) IS IN LIEU OF ANY OTHER WARRANTY WITH RESPECT TO THE PRODUCT, BULK SUBSTANCE OF COMPOUND OR SEMI-PRODUCT SUPPLIED BY RADIUS HEREUNDER, WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL (INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE).
MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.
