Bench Test Sample Clauses

Bench Test. Bench testing describes the process used to check the NCHRP 1-37A software for run-time issues and model prediction reasonableness, as well as identification of calibration needs. Although the software had a few problems with unexpected crashes, this did not present significant difficulties. The reasonableness of the models was checked by varying the primary design parameters of traffic loading, climate, slab thickness, joint spacing, dowels, base type, and soil type (as shown in Table 2) and then comparing the results with generally accepted PCC pavement performance. Key observations from the bench testing were as follows: • Transverse cracking was most influenced by joint spacing. When joint spacing was set at 15 feet (typical for WSDOT), results showed very little cracking (as expected). • Dowel bar use heavily influenced the development of faulting and related roughness (as expected). • Base type, traffic loading, and climate had significant impacts on faulting and roughness predictions (as expected). • With a few exceptions (Xxxxxxxxxx et al., 2005) predicted performance and its relation to input values matched well with consensus pavement knowledge. Table 2 Design Parameters Used for Bench Testing Design Parameters Varied Values Traffic loading (million ESALs) 2, 1, 0.5, 0.2, 0.05 Climate WW, EW, mountain pass, Minnesota, Alaska, Florida Slab thickness (inch) 14, 12, 9, 5 Joint spacing (feet) 21, 19, 17, 15, 13, 11 Dowels yes or no Base type Granular, ATB, CTB Soil type SM, SC, ML, A-4… These findings correlate well with previous studies and indicate that the NCHRP 1-37A software predicts reasonable PCC pavement performance (Xxxxxxxxxx et al., 2005). In comparing the NCHRP 1-37A software output with actual WSDOT data, several calibration issues were identified. First, the default models tended to (1) over- predict transverse cracking, (2) predict significantly different faulting trends, and (3) under-predict roughness.
Sample 1
AutoNDA by SimpleDocs
Bench Test. Within 30 days of the Effective Date, the Parties shall conduct a “Bench Test” as follows:
Sample 1
Bench Test. Not applicable.
Sample 1

Related to Bench Test

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

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

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

  • 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 across the Berths, nor will Operator be obligated to accept Product that fails to meet the quality specifications set forth in the arrival notice.

  • Financial testing The financial covenants set out in Clause 20.2 (Financial condition) shall be tested by reference to each of the financial statements and/or each Compliance Certificate delivered pursuant to Clause 19.2 (Compliance Certificate).

  • Testing Landlord shall have the right to conduct annual tests of the Premises to determine whether any contamination of the Premises or the Project has occurred as a result of Tenant’s use. Tenant shall be required to pay the cost of such annual test of the Premises; provided, however, that if Tenant conducts its own tests of the Premises using third party contractors and test procedures acceptable to Landlord which tests are certified to Landlord, Landlord shall accept such tests in lieu of the annual tests to be paid for by Tenant. In addition, at any time, and from time to time, prior to the expiration or earlier termination of the Term, Landlord shall have the right to conduct appropriate tests of the Premises and the Project to determine if contamination has occurred as a result of Tenant’s use of the Premises. In connection with such testing, upon the request of Landlord, Tenant shall deliver to Landlord or its consultant such non-proprietary information concerning the use of Hazardous Materials in or about the Premises by Tenant or any Tenant Party. If contamination has occurred for which Tenant is liable under this Section 30, Tenant shall pay all costs to conduct such tests. If no such contamination is found, Landlord shall pay the costs of such tests (which shall not constitute an Operating Expense). Landlord shall provide Tenant with a copy of all third party, non-confidential reports and tests of the Premises made by or on behalf of Landlord during the Term without representation or warranty and subject to a confidentiality agreement. Tenant shall, at its sole cost and expense, promptly and satisfactorily remediate any environmental conditions identified by such testing in accordance with all Environmental Requirements. Landlord’s receipt of or satisfaction with any environmental assessment in no way waives any rights which Landlord may have against Tenant.

  • Commercial Milestones In partial consideration of the rights granted by AstraZeneca to Licensee hereunder, Licensee shall pay to AstraZeneca the following payments, which shall be non-refundable, non-creditable and fully earned upon the first achievement of the applicable milestone event:

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

  • Financial Tests The Company hereby certifies and warrants to you that the following is a true and correct computation as at the Computation Date of the following ratios and/or financial restrictions contained in the Credit Agreement:

  • Final Completion The full and final completion of all Work in accordance with the Contract Documents.

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