Shift Schedules within the Flight Operations Unit Sample Clauses

Shift Schedules within the Flight Operations Unit. Pursuant to the terms and conditions of the Collective Agreement, the parties shall refer to the Joint Shift Scheduling Committee the issue of the appropriate shift schedule for all of the positions listed herein. The Joint Shift Scheduling Committee has accepted that a specific shift schedule be implemented for the Flight Operations Unit and this shall confirm that the parties agree with such recommendation. It is also agreed that the following shift schedule is being agreed to on a without prejudice and precedent basis. Moreover, the parties agree that such a shift schedule is not appropriate for other areas of the Winnipeg Police Service and neither party shall attempt to introduce such a shift schedule in other areas. Lastly, it is agreed that the agreed upon shift schedule shall be reviewed annually in order to determine the shift schedule’s suitability. In the event the parties cannot agree that the shift schedule should continue or agree upon an alternate shift schedule, this matter may be referred to arbitration as contemplated in the Collective Agreement. It is agreed that, as with all shift schedules, no such schedule can be implemented without the express agreement of the Association. The parties agree that the shift schedule in effect on July 26, 2013 shall remain, in effect, without modification or amendment, unless agreed otherwise between the parties until the date of the annual transfer deadline for 2016. Should the parties fail to agree to continue the current shift or to the terms and conditions of a new shift ninety (90) days prior to the above deadline, the matter may be referred to arbitration by either party.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Shift Schedules within the Flight Operations Unit

  • Green Economy/Carbon Footprint a) The Supplier/Service Provider has in its bid provided Transnet with an understanding of the Supplier’s/Service Provider’s position with regard to issues such as waste disposal, recycling and energy conservation.

  • Approved Services; Additional Services Registry Operator shall be entitled to provide the Registry Services described in clauses (a) and (b) of the first paragraph of Section 2.1 in the Specification 6 attached hereto (“Specification 6”) and such other Registry Services set forth on Exhibit A (collectively, the “Approved Services”). If Registry Operator desires to provide any Registry Service that is not an Approved Service or is a material modification to an Approved Service (each, an “Additional Service”), Registry Operator shall submit a request for approval of such Additional Service pursuant to the Registry Services Evaluation Policy at xxxx://xxx.xxxxx.xxx/en/registries/rsep/rsep.html, as such policy may be amended from time to time in accordance with the bylaws of ICANN (as amended from time to time, the “ICANN Bylaws”) applicable to Consensus Policies (the “RSEP”). Registry Operator may offer Additional Services only with the written approval of ICANN, and, upon any such approval, such Additional Services shall be deemed Registry Services under this Agreement. In its reasonable discretion, ICANN may require an amendment to this Agreement reflecting the provision of any Additional Service which is approved pursuant to the RSEP, which amendment shall be in a form reasonably acceptable to the parties.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Please see the current Washtenaw Community College catalog for up-to-date program requirements Conditions & Requirements

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Human and Financial Resources to Implement Safeguards Requirements The Borrower shall make available necessary budgetary and human resources to fully implement the EMP and the RP.

  • Transactional Services The Service Provider shall communicate to its Customers, as to shares of the Fund, purchase, redemption and exchange orders reflecting the orders it receives from its Customers or from any brokers and banks for their Customers. The Service Provider shall also communicate to beneficial owners holding through it, and to any brokers or banks for beneficial owners holding through them, as to shares of the Fund, mergers, splits and other reorganization activities, and require any broker or bank to communicate such information to its Customers.

  • Disaster Recovery and Business Continuity The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:

  • Trunk Group Connections and Ordering 5.2.1 For both One-Way and Two-Way Interconnection Trunks, if Onvoy wishes to use a technically feasible interface other than a DS1 or a DS3 facility at the POI, the Parties shall negotiate reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.2 When One-Way or Two-Way Interconnection Trunks are provisioned using a DS3 interface facility, if Onvoy orders the multiplexed DS3 facilities to a Frontier Central Office that is not designated in the NECA 4 Tariff as the appropriate Intermediate Hub location (i.e., the Intermediate Hub location in the appropriate Tandem subtending area based on the LERG), and the provision of such facilities to the subject Central Office is technically feasible, the Parties shall negotiate in good faith reasonable terms and conditions (including, without limitation, rates and implementation timeframes) for such arrangement; and, if the Parties cannot agree to such terms and conditions (including, without limitation, rates and implementation timeframes), either Party may utilize the Agreement’s dispute resolution procedures. 5.2.3 Each Party will identify its Carrier Identification Code, a three or four digit numeric code obtained from Telcordia, to the other Party when ordering a trunk group. 5.2.4 For multi-frequency (MF) signaling each Party will out pulse ten (10) digits to the other Party, unless the Parties mutually agree otherwise. 5.2.5 Each Party will use commercially reasonable efforts to monitor trunk groups under its control and to augment those groups using generally accepted trunk- engineering standards so as to not exceed blocking objectives. Each Party agrees to use modular trunk-engineering techniques for trunks subject to this Attachment.

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