Run-Around Sample Clauses

Run-Around. Section a) modified by Agreement #1803139681 dated October 10, 1996
AutoNDA by SimpleDocs
Run-Around. (A) When an engineer is run around, he shall be allowed one-half day, but if not called on duty within eight hours, one day will be allowed. Payment to be made at the rate of service and engine for which he should have been called.
Run-Around. Time lost when an employee is available, but not dispatched in proper order under agreed upon local dispatch rules between the Company and the Association, shall be paid at the hourly rate from the time he should have been dispatched until the actual time of departure on trip and/or tour with a maximum of ten (10) hours at the applicable work time rate in each twenty-four (24) hour period, notwithstanding legal hours of operation and drivers ability to report to the dispatching terminal.
Run-Around. 16.1 Spare board locomotive engineers who are run-around will be paid four hours over and above the guarantee and not calculated in the hours of overtime purposes. The locomotive engineer will maintain his position on the spare board.
Run-Around. When engineers are run around at their own request, or for their own convenience, or when they cannot be found, they will not be paid for time lost, and stand last out. When not called in turn, through no fault of their own, they will be paid 100 miles for being run around, and will stand last out. When called in turn but not sent out in turn, through no fault of their own, Engineers runaround will be paid 25 miles for each runaround in addition to pay for trip. In case of wreck call, necessitating the immediate use of the wrecker, the first available engineer may be used, in which event the engineers who are run around will not be allowed compensation therefor.
Run-Around. In the event that a driver has notified the Dispatcher of a run-around, and the Dispatcher is able to correct the error immediately he/she shall do so.

Related to Run-Around

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Required Coverages For Generation Resources Of 20 Megawatts Or Less Each Constructing Entity shall maintain the types of insurance as described in section 11.1 paragraphs (a) through (e) above in an amount sufficient to insure against all reasonably foreseeable direct liabilities given the size and nature of the generating equipment being interconnected, the interconnection itself, and the characteristics of the system to which the interconnection is made. Additional insurance may be required by the Interconnection Customer, as a function of owning and operating a Generating Facility. All insurance shall be procured from insurance companies rated “A-,” VII or better by AM Best and authorized to do business in a state or states in which the Interconnection Facilities are located. Failure to maintain required insurance shall be a Breach of the Interconnection Construction Service Agreement.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.

  • New York State Statewide Financial System New York State Statewide Financial System (SFS) went live for NYS agencies in April 2012. Future SFS procurement functionality envisions the ability to fully host Contract catalogs, to integrate Contractor-hosted punch-out catalogs, and/or to submit and process invoices electronically. OGS reserves the right to integrate any or all of these future catalog functions with a Contractor during the contract period, and by submittal of a Vendor Submission, a Vendor agrees to coordinate with SFS, OGS and/or a third party host, for integration, if OGS exercises its right to do so. No costs or expenses associated with providing information and integration shall be charged to NYS. Technical Requirements for the data elements, such as data types, maximum field lengths, and cXML element names shall be provided by SFS, OGS and/or a third party host during integration. For more information on SFS, its use, and its capabilities please visit the SFS website here: xxxx://xxx.xxx.xx.xxx/.

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Shift Rotation Routine shift rotation is not an approach to staffing endorsed by the Employer. Except for emergency situations where it may be necessary to provide safe patient care, shift rotation will not be utilized without mutual consent. If such an occasion should ever occur, volunteers will be sought first. If no one volunteers, the Employer will rotate shifts on an inverse seniority basis until the staff vacancies are filled.

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

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