Product/Instrument Safety Alert and Product/Instrument Recall Sample Clauses

Product/Instrument Safety Alert and Product/Instrument Recall. 9.1 If the Goods/On-loan Instruments do not meet the criteria in Clause 6 or Clause 8 of these T&Cs, or if there is local or overseas adverse incident, e.g. product recall, hazard alert, etc., the Seller is obligated to inform the Authority in writing via e-mail (xxxx_xxx_xx@xx.xxx.xx) within 24 hours after the Seller has known or reasonably should have known the happening of the incident, giving full details of the incident and its proposed response. 9.2 The Seller’s product safety alert notice (“Safety Alert Notice”) must be issued even if the Seller disputes legal liability for the problem or the hazard, or requires more time to establish remedial actions to be undertaken in relation to it, and the Safety Alert Notice shall not relieve the Seller from any other liability or obligation under the Contract and/or the Purchase Orders. The Safety Alert Notice must contain at least the following information: (a) the manufacturer and the type/brand/model of the Goods/On-loan Instruments in question; (b) the safety issue in question; (c) when and how the safety issue was discovered; (d) the distribution list of affected type/brand/model of the Goods/On-loan Instruments delivered to the Buyer; (e) the manufacturer’s recommendation in respect of the patients who may have used the Goods/On-loan Instruments in question and other action that needs to be taken. 9.3 The Seller’s product recall notice (“Product Recall Notice”) must contain at least the following information: (a) the manufacturer and the type/brand/model of the Goods/On-loan Instruments in question; (b) the safety issue in question; (c) when and how the safety issue was discovered; (d) the distribution list of affected type/brand/model of the Goods/On-loan Instruments delivered to the Buyer; (e) the anticipated duration of the product recall exercise; (f) whether the product recall is at hospital level or on patient level; (g) the manufacturer’s recommendation in respect of patients who may have used the type/brand/model of the Goods/On-loan Instruments in question and other action that needs to be taken; (h) whether the Department of Health has been alerted. 9.4 The Seller’s Safety Alert Notice or the Product Recall Notice (as the case may be) must comply with regulatory requirements (including as to registration requirements) and align with industry practice of goods similar to the Goods and/or the On-loan Instruments. The Seller must inform the Authority timely as and when new information emerges in ...
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs

Related to Product/Instrument Safety Alert and Product/Instrument Recall

  • Supply Agreement Seller and Buyer, or their Affiliates, shall have executed the Supply Agreement.

  • Quality Agreement Concurrently with execution of this Agreement, the Parties will enter into an agreement that details the quality assurance obligations of each Party with respect to the Manufacture and supply of Supplied Products under this Agreement (the “Quality Agreement”). Each Party shall perform its obligations under the Quality Agreement in accordance with the terms and conditions thereof. In the event of a conflict between the terms of the Quality Agreement and the terms of this Agreement, the provisions of the Quality Agreement shall govern.

  • PRODUCT MANUFACTURER'S SUPPLIERS Only those dealers/distributors listed by the manufacturer will be considered authorized to act on behalf of the Product Manufacturer.

  • Field Order A written order issued by Engineer which requires minor changes in the Work but does not change the Construction Contract Price or the Construction Contract Times.

  • Field Orders The documents listed in Paragraph 9.01.A are attached to this Agreement (except as expressly noted otherwise above).

  • 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. 2) Compliance with the Software License Agreement is the responsibility of the Customer. DIR shall not be responsible for any Customer’s compliance with the Software License Agreement. If DIR purchases software licenses for its own use under this Contract, it shall be responsible for its compliance with the Software License Agreement terms and conditions.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Supply Agreements For a period of three years from the consummation of the IPO, Odetics shall not unilaterally terminate or assign its guarantee obligation with respect to any supply agreement pursuant to which it has guaranteed the performance by ATL of ATL's obligations, unless such suppliers have consented to the termination or assignment of such guarantee.

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

  • Contractor Licensing, etc. Notwithstanding Section 14.c, District may terminate this Contract immediately by written notice to Contractor upon denial, suspension, revocation, or non-renewal of any license, permit, or certificate that Contractor must hold to provide services under this Contract.

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