WEIGHT ON DRIVERS Sample Clauses

WEIGHT ON DRIVERS. A weight of 67,000 pounds for each axle will be used to compute Engineers’ pay.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
WEIGHT ON DRIVERS. Consult Table #1 to find the weight of a particular class of engine(s).
Sample 1
WEIGHT ON DRIVERS. 1 1 When Fort Xxxxxxx is Terminal................................................................... 25 44 Work Outside Yard Limit – Yard Service ................................................. 76 44 APPENDIX APPENDIX PAGE Dues Deduction Agreement ....................................................................... 1 50 Wage Assignment Authorization ............................................................... 2 52 Compulsory Retirement Age...................................................................... 3 54
Sample 1
WEIGHT ON DRIVERS. Paragraph 3 of Attachment (e) (System Agreement – Weight on Drivers) of the “Agreement between Union Pacific Railroad (UP) and the Brotherhood of Locomotive Engineers (BLE),” dated March 21, 1996, created a forum to address and simplify matters pertaining to determination of actual unit weights and proper payment for weight-on-drivers. Paragraph 3 provided, in relevant part, the parties would “… establish an Average Weight-on-Driver Committee, to develop and implement a new system that will eliminate the necessity of determining actual unit weights to determine the proper rate of pay.” Pursuant thereto, UP and BLET agree the following changes in the determination and payment of weight-on-drivers shall be made:
Sample 1
WEIGHT ON DRIVERS. Section A. In order to apply a uniform method of paying engineers based on the number of units in the consist instead of the weight on drivers, the existing agreement provisions relating to pay based on weight on drivers ( such as Rule 1 A on D&RGW; Article 33 on Western Lines; Article 27, Sections 11(a) and (b) on former EP&SW; Article 28, Section 7 on Eastern Lines and Article 34 on SSW) are cancelled and replaced with the following system.
Sample 1
WEIGHT ON DRIVERS. 1. In lieu of the present weight-on-driver allowance payment, locomotive engineers performing service in the following class(es) of service will be paid an average weight-on-drivers allowance based on the amount actually paid during the measurement period September 30, 2020, through August 1, 2021. The amount to be paid to locomotive engineers for a weight-on-driver allowance will be as set forth in the following table: Class of Service Average Weight-on-Driver Allowance Amount Work Train $2.47 Yard Service $1.84 Local Freight $2.33 Combination Switch & Road Service $2.04 Through Freight* $1.15 * This amount will be added to the existing 1,200,000-pound (three (3)-unit) rate schedule for through freight service trips.
Sample 1
WEIGHT ON DRIVERS. (1996 UP on property Agreement, Attachment E)
Sample 1
AutoNDA by SimpleDocs

Related to WEIGHT ON DRIVERS

  • Table 3 Appendix Information

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Table 2 Software Subscription Use Case OpenShift Enterprise OpenShift Enterprise Broker Infrastructure OpenShift Enterprise is intended to be used as a platform as a service and will be supported only when used in that capacity. OpenShift Enterprise is not supported on non-server hardware such as desktops or workstations. OpenShift Enterprise is intended for use on a dedicated Physical Node or Virtual Guest; running other applications and/or programs of any type on the Physical Node or Virtual Guest can have a negative impact on the function and/or performance. Red Hat JBoss Enterprise Application Platform for OpenShift and/or Red Hat JBoss EAP for xPaaS will be supported in accordance with the terms of Exhibit 1.B.

  • Table 2 (definition of “Casino Gross Revenue”) 15(e) 2 (definition of “Commissioning”) 19 2 (definition of “Committee’s Nominated Representative) 20(1) 6(1)(c) 20(2) 7(8)(a) 21(d) 11(1) 21(e) 11(2) 22(2) 11(3) 23(b) 14(d) 33(2) 15(a)(B) 35(1) 15(b)(i) 35(2) 15(c) 36(b) 15(d) 36(c)

  • Headers The descriptive headings hereof do not constitute a part of any Schedule and no inferences shall be drawn therefrom.

  • Registry-­‐Level Fees (a) Registry Operator shall pay ICANN a registry-­‐level fee equal to (i) the registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-­‐level transaction fee (collectively, the “Registry-­‐Level Fees”). The registry-­‐level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-­‐accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-­‐level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met. Registry Operator’s obligation to pay the quarterly registry-­‐level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-­‐level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls.

  • Table 4 Ending this Addendum when the Approved Addendum Changes Which Parties may end this Addendum as set out in Section 19: Importer Exporter Ending this Addendum when the Approved Addendum changes Part 2: Mandatory Clauses Entering into this Addendum

  • Table 1 4 If ‘Yes’ to any then you are likely required to carry out a DPIA under Article 35 GDPR. If ‘No’, to all then a DPIA may not be required. 1 xxxxx://xxx-xxx.xxxxxx.xx/legal-content/EN/TXT/?uri=CELEX:02016R0679-20160504

  • Attainment on Performance Indicators The District will be responsible for overseeing the academic programs offered in its schools and ensuring that those programs meet or exceed state and local expectations for levels of attainment on the statewide performance indicators, as specified in 1 CCR 301-1.

  • SHOP XXXXXXX (a) The Union may elect or appoint a Shop Xxxxxxx or Shop Stewards to represent the employees and the Union shall notify the Company as to the name or names of such Shop Xxxxxxx or Shop Stewards. The Company agrees that no Shop Xxxxxxx shall suffer any discrimination by reason of holding such office.

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