EMERGENCY/REPORTING FOR WORK Sample Clauses

EMERGENCY/REPORTING FOR WORK. Hours actually worked (exclusive of premium time) during a “call in” by Maintenance workers who are not designated to shifts as per the Collective Agreement, will count in the computation of forty (40) hours for the purpose of determining the level of payment for overtime.
AutoNDA by SimpleDocs

Related to EMERGENCY/REPORTING FOR WORK

  • REPORTING FOR WORK 11.01 An employee reporting for work at the scheduled starting time, unless notified the previous day not to report, and for whom no work is available, shall receive four

  • Reporting for Duty Where an employee is not notified beforehand not to report for duty, and she reports for duty at her regularly scheduled starting time she shall be paid for her entire shift even when work is not available in her normal assignment. In such circumstances the employee may be required to perform other available work.

  • DISASTER OR EMERGENCY REPORTS Any disaster or emergency situation, natural or man-made, such as fire or severe weather, shall be reported telephonically within 72 hours, followed by a comprehensive written report within seven days to DHA.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Reporting of Non-Force Majeure Events Each Party (the “Notifying Party”) shall notify the other Parties when the Notifying Party becomes aware of its inability to comply with the provisions of this Agreement for a reason other than a Force Majeure event. The Parties agree to cooperate with each other and provide necessary information regarding such inability to comply, including the date, duration, reason for the inability to comply, and corrective actions taken or planned to be taken with respect to such inability to comply. Notwithstanding the foregoing, notification, cooperation or information provided under this Article shall not entitle the Party receiving such notification to allege a cause for anticipatory breach of this Agreement.

  • Contractor Work Hours and Safety Standards Contractor shall ensure compliance with all safety and hourly requirements for employees, in accordance with federal, state, and County safety and health regulations and laws.

  • Reporting Frequency During any period of time when you are subject to the requirement in paragraph 1 of this award term and condition, you must report proceedings information through XXX for the most recent five year period, either to report new information about any proceeding(s) that you have not reported previously or affirm that there is no new information to report. Recipients that have Federal contract, grant, and cooperative agreement awards with a cumulative total value greater than $10,000,000 must disclose semiannually any information about the criminal, civil, and administrative proceedings.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

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