Performance Test at end of Warranty Period Sample Clauses

Performance Test at end of Warranty Period. The Principal may perform a Performance Test at the end of the Warranty Period at its own cost and risk and If the performance of the Equipment has deteriorated below the performance levels specified in Annexure D the Principal and Supplier will meet in good faith to discuss and determine the reasons for the deterioration (for the removal of doubt, the Principal will engage the Supplier under a separate contract for this purpose).
AutoNDA by SimpleDocs

Related to Performance Test at end of Warranty Period

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

  • Warranty Period The warranties set forth in Clauses 12.1.1 and 12.1.2 shall be limited to those defects that become apparent within **** after Delivery of the affected Aircraft (the “Warranty Period”).

  • Acceptance Testing The MCP must have the capability to report all elements in the Minimum Data Set as set forth in the ODJFS Encounter Data Specifications and must submit a test file in the ODJFS-specified medium in the required formats prior to contracting or prior to an information systems replacement or update. Acceptance testing of encounter data is required as specified in Section 29(a)(v) of this Appendix.

  • Year 2000 Compatibility Borrower shall take all action necessary to assure that Borrower's computer based systems are able to operate and effectively process data including dates on and after January 1, 2000. At the request of Bank, Borrower shall provide Bank assurance acceptable to Bank of Borrower's Year 2000 compatibility.

  • Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.

  • Product Testing Upon request, Customer shall provide Operator a laboratory report for each Product delivery by Customer or Customer’s supplier. Operator will not be obligated to receive Contaminated Product for throughput through the Pipelines, nor will Operator be obligated to accept Product that fails to meet the applicable quality specifications for the Berths under the BAUTA and any Terminal Service Orders issued thereunder.

  • Performance Review The Company will periodically review Executive’s performance on no less than an annual basis and will make adjustments to salary or other compensation, as they deem appropriate in their sole and absolute discretion.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Root Cause Analysis Upon Vendor's failure to provide the Services in accordance with the applicable Service Levels (for any reason other than a Force Majeure Event) Vendor will promptly (a) perform a root-cause analysis to identify the cause of such failure, (b) provide Prudential with a report detailing the cause of, and procedure for correcting, such failure, (c) obtain Prudential's written approval of the proposed procedure for correcting such failure, (d) correct such failure in accordance with the approved procedure, (e) provide weekly (or more frequent, if appropriate) reports on the status of the correction efforts, and (f) provide Prudential with assurances satisfactory to Prudential that such failure has been corrected and will not recur.

  • Year 2000 Problem The Company and its Subsidiaries have reviewed the areas within their business and operations which could be adversely affected by, and have developed or are developing a program to address on a timely basis, the "Year 2000 Problem" (that is, the risk that computer applications used by the Company and its Subsidiaries may be unable to recognize and perform properly date-sensitive functions involving certain dates prior to and any date after December 31, 1999). Based on such review and program, the Company reasonably believes that the "Year 2000 Problem" will not have a Material Adverse Effect.

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