CONCESSION FOR USE, DEFECTS Sample Clauses

CONCESSION FOR USE, DEFECTS. 3.1. The objects rented out by spidercam are technically complex devices and correspondingly susceptible to faults, which consequently require particularly careful handling and operation by technically qualified personnel.
AutoNDA by SimpleDocs

Related to CONCESSION FOR USE, DEFECTS

  • RECTIFICATION OF DEFECTS 27.1 The Purchaser shall within 14 (fourteen) days after the Contractual Occupation Date notify the Seller in writing by way of a snaglist of all or any defects in the Unit, failing which the Purchaser shall be deemed to have accepted the Unit in good order and condition. Only ONE snaglist shall be considered. The Seller shall within a reasonable time thereafter at its cost repair all such defects and the Seller undertakes to rectify all latent and/or patent defects which become apparent to the Purchaser within 3 (three) calendar months from the Contractual Occupation Date and which is the result of defective materials and/or workmanship.

  • System defects In the event you become aware of a material defect, malfunction or virus in the System or in an Electronic Service, you will immediately notify us of such defect, malfunction or virus and cease all use of such Electronic Service until you have received permission from us to resume use.

  • Inspection and Rejection of Nonconforming Goods (a) Buyer shall inspect the goods within five days of receipt (“Inspection Period”). Xxxxx will be deemed to have accepted the goods unless it notifies Seller in writing of any Nonconforming Goods during the Inspection Period and furnishes documentation reasonably required by Seller. “

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Correction of Defective Work 2.10.1 Design-Builder agrees to correct any Work that is found to not be in conformance with the Contract Documents, including that part of the Work subject to Section 2.9 hereof, within a period of one (1) year from the date of Final Acceptance of the Work or any portion of the Work, or within such longer period to the extent required by the Contract Documents or applicable Legal Requirements or Government Approvals.

  • Correction of Defects 35.1 The Engineer shall give notice to the Contractor of any Defects before the end of the Defects Liability Period, which begins at Completion and is defined in the Contract Data. The Defects Liability Period shall be extended for as long as Defects remain to be corrected.

  • YOUR BILLING RIGHTS - KEEP THIS NOTICE FOR FUTURE USE This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.

  • Unsafe Work Conditions No employee shall be disciplined for refusal to work on an assignment which, in the opinion of:

  • Retainage for Unacceptable Corrective Action Plan or Plan Failure If the corrective action plan is unacceptable to the Department or Customer, or implementation of the plan fails to remedy the performance deficiencies, the Department or Customer will retain ten percent (10%) of the total invoice amount. The retainage will be withheld until the Contractor resolves the performance deficiencies. If the performance deficiencies are resolved, the Contractor may invoice the Department or Customer for the retained amount. If the Contractor fails to resolve the performance deficiencies, the retained amount will be forfeited to compensate the Department or Customer for the performance deficiencies.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

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