Six-Day Turnaround Sample Clauses

Six-Day Turnaround. Where the Employee works six consecutive days in a work week, there shall be a continuous thirty-four (34) hour rest period, which includes the ten (10) hour rest period in subparagraph (a)(i) above, for each Employee who works the sixth day in a seven day work week. If such rest period is encroached, such Employee shall be paid at a rate equal to two times (2x) the rate such Employee was receiving at the end of the preceding shift, but in no event in excess of three times (3x) such Employee's straight time contracted hourly rate. Such rate shall be paid for the time beginning at the start of the next call through the end of such encroached thirty-four (34) hour rest period and calculated pursuant to subparagraph (e) below. (i) Six-Day Worked Turnaround Encroachment Applicable to the Seventh Day of Work Week: Where the sixth day worked occurs on the seventh day of the work week, there shall be a continuous thirty-four (34) hour rest period between the end of the shift on the fifth day and the commencement of the shift on the seventh day for each Employee who works a sixth day on the seventh day of the work week. If this rest period is encroached, the Employee shall be paid at a rate equal to two times (2x) the rate such Employee was receiving at the end of the preceding shift but in no event in excess of three times (3x) such Employee’s straight time contracted hourly rate for the time beginning at the start of the sixth day worked through the end of the encroached thirty-four (34) hour rest period and calculated pursuant to subparagraph (e) below.
Sample 1Sample 2See All (16)
AutoNDA by SimpleDocs
Six-Day Turnaround. Where the Employee works six consecutive days in a work week, there shall be a continuous thirty-four (34) hour rest period, which includes the ten (10) hour rest period in subparagraph (a)(i) above, for each Employee who works the sixth day in a seven day work week. If such rest period is encroached, such Employee shall be paid at a rate equal to two times (2x) the rate such Employee was receiving at the end of the preceding shift but in no event in excess of three times (3x) such Employee's straight time contracted hourly rate. Such rate shall be paid for the time beginning at the start of the next call through the end of such encroached thirty-four (34) hour rest period and calculated pursuant to subparagraph (e) below.
Sample 1Sample 2Sample 3See All (15)

Related to Six-Day Turnaround

  • Turnaround There shall be a 10 hour rest period between the termination of work on one call and the commencement of work on the next call (see paragraph (f) below for specific rules) and a fifty-four (54) consecutive hour break for a five day week, and thirty-four (34) consecutive hour break for a six day week).

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

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Work Day The standard work day shall be eight (8) consecutive hours of work exclusive of a lunch period in a consecutive twenty-four (24) hour day.

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • Scheduled Outages (1) No later than five (5) Business Days prior to the dates required by the ISO for delivery of schedules for planned outages (which such ISO required delivery dates are currently January 15th, April 15th, July 15th and October 15th of each calendar year during the Facility Term), and at least sixty (60) days prior to the later of: (A) Initial Synchronization, or (B) SCE becoming Seller’s Scheduling Coordinator, Seller shall submit to SCE its schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty four-month period using the Web Client. If Seller fails to submit an Outage Schedule for any period as required under this Section 3.19, then Seller shall not be permitted to schedule or have any planned outages with respect to such period. The foregoing shall not prevent Seller from modifying its Outage Schedule in cooperation with SCE and the ISO. SCE shall provide Notice to Seller in the event that the ISO changes the ISO required delivery dates for schedules for planned outages. In addition, no later than thirty (30) days prior to October 15 of each year, Seller shall submit to SCE its estimate of its planned outages for the following year. (2) Seller shall provide the following information for each proposed planned outage: (A) Start date and time; (B) End date and time; and (C) Capacity expected to be online, in MW, during the planned outage. (3) Within twenty (20) Business Days after SCE’s receipt of an Outage Schedule, SCE shall notify Seller in writing of any reasonable request for changes to the Outage Schedule, and Seller shall, consistent with Prudent Electrical Practices and as permitted by the ISO, accommodate SCE’s requests regarding the timing of any planned outage. (4) Seller shall cooperate with SCE to arrange and coordinate all Outage Schedules with the ISO. (5) In the event a condition occurs at the Generating Facility which causes Seller to revise its planned outages, Seller shall provide Notice to SCE, using the Web Client, of such change (including an estimate of the length of such planned outage) as soon as practicable after the condition causing the change becomes known to Seller. (6) Seller shall promptly prepare and provide to SCE upon request, using the Web Client, all reports of actual or forecasted outages that SCE may reasonably require for the purpose of enabling SCE to comply with Section 761.3 of the California Public Utilities Code or any Applicable Law mandating the reporting by investor owned utilities of expected or experienced outages by electric energy generating facilities under contract to supply electric energy.

  • Line Outage Costs Notwithstanding anything in the NYISO OATT to the contrary, the Connecting Transmission Owner may propose to recover line outage costs associated with the installation of Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades on a case-by-case basis.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!