Acceleration test execution Sample Clauses

Acceleration test execution. The vehicle shall approach line AA' at an initial steady vehicle speed vAA' as specified below. When the front of the vehicle reaches line AA' the accelerator handle shall be fully opened as quickly as practically possible and kept in that position until the rear of the vehicle reaches the line BB'; the accelerator handle shall then be returned as quickly as possible to the idle position. The vehicle speed achieved, when the rear of the vehicle reaches the line BB' is called vBB'. The engine speeds corresponding to vAA' and vBB' in a specific test condition are called nAA' and nBB'. In the case of articulated vehicles consisting of two non-separable units regarded as a single vehicle, the semi-trailer shall be disregarded in determining when line BB' is crossed. For all measurements, the vehicle shall be driven in a straight line along the test track in such a way that the track of the median longitudinal plane of the vehicle is as close as possible to the line CC'. Figure 1 Measuring positions for vehicles in motion
AutoNDA by SimpleDocs

Related to Acceleration test execution

  • Reasonable Suspicion Testing The Employer may, but does not have a legal duty to, request or require an employee to undergo drug and alcohol testing if the Employer or any supervisor of the employee has a reasonable suspicion (a belief based on specific facts and rational inferences drawn from those facts) related to the performance of the job that the employee:

  • Independence from Material Breach Determination Except as set forth in Section X.D.1.c, these provisions for payment of Stipulated Penalties shall not affect or otherwise set a standard for OIG’s decision that CHSI has materially breached this CIA, which decision shall be made at OIG’s discretion and shall be governed by the provisions in Section X.D, below.

  • Modification to Performance Frameworks The Parties acknowledge that specific terms, forms, and requirements of the Performance Frameworks may be modified to the extent required to align with changes to applicable State or federal accountability requirements as set forth in law or policies or based on other circumstances that make assessment based on the existing Performance Framework requirements impracticable. In the event that such modifications are needed, the Commission will make its best effort to apply expectations for school performance in a manner as reasonably consistent with those set forth in the Performance Frameworks and the School's Educational Program as set forth in Exhibit A to this Contract.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Excuse from Performance The Parties shall be excused from performing their respective obligations hereunder if they are prevented from so performing by reason of floods, earthquakes, other acts of nature, war, civil insurrection, riots, acts of any government (including judicial action), and other similar catastrophic events which are beyond the control of and not the fault of the Party claiming excuse from performance hereunder. Labor unrest, including but not limited to strike, work stoppage or slowdown, sick-out, picketing, or other concerted job action conducted by Contractor's employees or directed at Contractor is not an excuse from performance and Contractor shall be obligated to continue to provide service notwithstanding the occurrence of any or all of such events. The Party claiming excuse from performance shall, within two (2) Business Days after such Party has notice of such cause, give the other Party notice of the facts constituting such cause and asserting its claim to excuse under this Section. If either Party validly exercises its rights under this Section, the Parties hereby waive any claim against each other for any damages sustained thereby. The partial or complete interruption or discontinuance of Contractor's services caused by one or more of the events described in this Section shall not constitute a default by Contractor under this Agreement. Notwithstanding the foregoing, however, if Contractor is excused from performing its obligations hereunder for any of the causes listed in this Section for a period of thirty (30) calendar days or more, the SCWMA shall nevertheless have the right, in its sole discretion, to terminate this Agreement by giving ten (10) calendar days notice to Contractor unless Contractor has demonstrated, by the thirtieth (30th) calendar day, to the satisfaction of the SCWMA that the Contractor will resume services no later than the sixtieth (60th) day following the date service was interrupted or discontinued by Contractor.

  • Payment for Material Completion The Contractor may request payment of the remaining contract balance, including retainage, less amounts credited the Owner or incurred as liquidated damages, and less amounts withheld for the Punchlist by reason of Minor Items or Permitted Incomplete Work (See Paragraph 6.5.3.2). Payment for Material Completion shall be made by a check payable jointly to the Contractor and Surety and shall be mailed to the Surety.

  • Termination for Non-Performance Should a party to this Agreement fail to materially perform in accordance with the terms and conditions of this Agreement, this Agreement may be terminated by the performing party if the performing party first provides written notice to the non-performing party which notice shall specify the non-performance, provide both a demand to cure the non-performance and reasonable time to cure the non-performance, and state a date upon which the Agreement shall be terminated if there is a failure to timely cure the non- performance. For purpose of this Section 4.4, “reasonable time” shall be not less than five (5) business days. In the event of a failure to timely cure a non- performance and upon the date of the resulting termination for non-performance, the Contractor shall prepare a final accounting and final invoice of charges for all performed but unpaid Services and authorized reimbursable expenses. Such final accounting and final invoice shall be delivered to the Town within fifteen (15) days of the date of termination; thereafter, no other invoice, xxxx, or other form of statement of charges owing to the Contractor shall be submitted to or accepted by the Town. Provided that notice of non-performance is provided in accordance with this Section 4.4, nothing in this Section 4.4 shall prevent, preclude, or limit any claim or action for default or breach of contract resulting from non-performance by a Party.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

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

  • EFFECTIVE DATE/COMPLETION OF SERVICES 3.1 Notwithstanding any provision of this Agreement to the contrary, and subject to the approval of the Governor and Executive Council of the State of New Hampshire, if applicable, this Agreement, and all obligations of the parties hereunder, shall become effective on the date the Governor and Executive Council approve this Agreement as indicated in block 1.17, unless no such approval is required, in which case the Agreement shall become effective on the date the Agreement is signed by the State Agency as shown in block 1.13 (“Effective Date”).

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