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.
35.2 Every time notice of a Defect is given, the Contractor shall correct the notified Defect within the length of time specified by the Engineer’s notice.
ACCEPTANCE OF INCOMPLETE OR NON-CONFORMING DELIVERABLES If, instead of requiring immediate correction or removal and replacement of defective or non- conforming deliverables, the City prefers to accept it, the City may do so. The Contractor shall pay all claims, costs, losses and damages attributable to the City’s evaluation of and determination to accept such defective or non-conforming deliverables. If any such acceptance occurs prior to final payment, the City may deduct such amounts as are necessary to compensate the City for the diminished value of the defective or non-conforming deliverables. If the acceptance occurs after final payment, such amount will be refunded to the City by the Contractor.
Hardware Warranty Company warrants that for a period of one (1) year from delivery of Hardware, Hardware will be free from defects in material and workmanship in normal use, but does not cover any of the following: (i) improper installation, maintenance, adjustment, repair or modification by Customer or a third party; (ii) misuse, neglect, or any other cause other than ordinary use, including without limitation, accidents or acts of God; (iii) improper environment, excessive or inadequate heating or air conditioning, electrical power failures, surges, water damage or other irregularities; (iv) third party software or software drivers; or (v) damage during shipment.
Description of Deliverables The Contractor shall Perform as set forth in Exhibit A.
Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.
C.1. <Title> Deliverable 1
Inspection and Rejection of Nonconforming Goods The Buyer has the right to inspect the Goods on or after the Delivery Date. Buyer, at its sole option, may inspect all or a sample of the Goods, and may reject all or any portion of the Goods if it determines the Goods are nonconforming or defective. If Buyer rejects any portion of the Goods, Buyer has the right, effective upon written notice to Seller, to: (a) rescind the Order in its entirety; (b) accept the Goods at a reasonably reduced price; or (c) reject the Goods and require replacement of the rejected Goods. If Buyer requires replacement of the Goods, Seller shall, at its expense, promptly replace the nonconforming Goods and pay for all related expenses, including, but not limited to, transportation charges for the return of the defective goods and the delivery of replacement Goods. If Seller fails to timely deliver replacement Goods, Buyer may replace them with goods from a third party and charge Seller the cost thereof and terminate this Order for cause pursuant to Section 19. Any inspection or other action by Buyer under this Section shall not reduce or otherwise affect Seller's obligations under the Order, and Buyer shall have the right to conduct further inspections after Seller has carried out its remedial actions.
Acceptance of Deliverables The State’s Project Manager shall be responsible for the sign-off acceptance of all Deliverables required and performed/submitted pursuant to this Agreement. Upon successful completion of a Deliverable, Contractor shall provide the State’s Project Manager with a completed Acceptance and Signoff Form (Exhibit E). The State’s Project Manager will apply the standards established in Exhibit D and the acceptance criteria set forth in subparagraph B of this article, as appropriate, to determine the acceptability of the Deliverable provided by Contractor. If the State’s Project Manager rejects the Deliverable, the parties agree to any dispute(s) resulting from such rejection(s) will be resolved as set forth in this article. Acceptance Criteria for Deliverables (“Criteria”) provided by Contractor pursuant to this Agreement include: Timeliness: The Work was provided on time; according to schedule; Completeness: The Deliverable contained all of the, Data, Materials, and features required by the Agreement; and Technical accuracy: The Deliverable complied with the standards of this Agreement, or, if this Agreement lacks a standard for provision of the Work, the currently generally accepted industry standard. Contractor shall provide the Deliverable to the State, in accordance with direction from the Project Manager and as provided for in Exhibit D. The State shall accept the Deliverable, provided that Contractor has delivered the Deliverable in accordance with the Criteria. The State’s Project Manager shall assign the Acceptance and Signoff Form to notify Contractor of the Deliverable’s acceptability. If the State rejects the Deliverable provided, the State’s Project Manager shall submit to Contractor’s Project Manager a written rejection describing in detail the failure of the Deliverable as measured against the Criteria. If the State rejects the Deliverable, then Contractor shall have a period of ten (10) Business Days from receipt of the Notice of rejection to correct the stated failure(s) to conform to the Criteria.
ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.
11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses.
11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.
Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.
