TIME AND CASUAL STAFF Sample Clauses

TIME AND CASUAL STAFF. 12.1 Part-Time Staff
Sample 1Sample 2
AutoNDA by SimpleDocs
TIME AND CASUAL STAFF. During the recent negotiations the parties had extensive dialogue relative to the shift scheduling of part-time and casual workers. The current part-time employees were being scheduled to a maximum of 3 shifts per week with available shifts then being assigned to casual employees to a maximum of 3 shifts. Prior to posting schedules of work, additional available replacement shifts will be scheduled for employees over and above their regularly scheduled hours in the following order: First to part-time employees, on a seniority basis, up to a total of 3 shifts per week. Next to casual employees, on a seniority basis, up to a total of 2 shifts per week. Next to part-time employees, on a seniority basis, up to a total of 4 shifts per week. Next to casual employees, on a seniority basis, up to a total of 3 shifts per week. Next to part-time employees, on a seniority basis, up to a total of 5 shifts per week. Next to casual, on a seniority basis, up to a total of 4 shifts per week. Such additional work does not change the status of an employee from part-time to full-time. This procedure does not affect call-ins. The scheduling of more than 3 shifts per week for a part-time employee shall be at the employee’s option, which shall be provided by the employee in advance of this process. Part-time to be scheduled by seniority. Call-ins shall be by seniority to part-time employees for whom such shift would not qualify for overtime and then to casual part-time employees. Casual part-time employees shall only receive scheduled shifts after regular part-time have been offered the shifts.
Sample 1

Related to TIME AND CASUAL STAFF

  • Professional Staff A. 1. This Article shall apply to all members of the unit except teaching faculty, librarians, Demonstration Teachers and Demonstration Specialists — A.

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

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

  • Reporting of Total Compensation of Subrecipient Executives I. Applicability and what to report. Unless you are exempt as provided in paragraph [4.]of this award term, for each first-tier subrecipient under this award, you shall report the names and total compensation of each of the subrecipient's five most highly compensated executives for the subrecipient's preceding completed fiscal year, if—

  • Evaluation and Comparison of Tenders 2.24.1 The Procuring entity will evaluate and compare the tenders which have been determined to be substantially responsive, pursuant to paragraph 2.22

  • SCHOOL STAFF COMMITTEES 1. If the majority of the teaching staff in the school so decide, there shall be established a recognized staff committee in that school.

  • PROMOTIONS AND STAFF CHANGES 22.1 Job Postings

  • ACCESS TO OPERATIONS SUPPORT SYSTEMS 2.1 BellSouth shall provide Max-Tel access to operations support systems (“OSS”) functions for pre-ordering, ordering and provisioning, maintenance and repair, and billing. BellSouth shall provide access to the OSS through manual and/or electronic interfaces as described in this Attachment. It is the sole responsibility of Max-Tel to obtain the technical capability to access and utilize BellSouth’s OSS interfaces. Specifications for Max-Tel ’s access and use of BellSouth’s electronic Version R4Q01: 12/01/01 interfaces are set forth at xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx and are incorporated herein by reference.

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • TESTING OF THE BCDR PLAN The Service Provider shall test the BCDR Plan on a regular basis (and in any event not less than once in every Contract Year). Subject to paragraph 6.2, the Purchaser may require the Service Provider to conduct additional tests of some or all aspects of the BCDR Plan at any time where the Purchaser considers it necessary, including where there has been any change to the Services or any underlying business processes, or on the occurrence of any event which may increase the likelihood of the need to implement the BCDR Plan. If the Purchaser requires an additional test of the BCDR Plan, it shall give the Service Provider written notice and the Service Provider shall conduct the test in accordance with the Purchaser's requirements and the relevant provisions of the BCDR Plan. The Service Provider's costs of the additional test shall be borne by the Purchaser unless the BCDR Plan fails the additional test in which case the Service Provider's costs of that failed test shall be borne by the Service Provider. The Service Provider shall undertake and manage testing of the BCDR Plan in full consultation with the Purchaser and shall liaise with the Purchaser in respect of the planning, performance, and review, of each test, and shall comply with the reasonable requirements of the Purchaser in this regard. Each test shall be carried out under the supervision of the Purchaser or its nominee. The Service Provider shall ensure that any use by it or any Sub-contractor of “live” data in such testing is first approved with the Purchaser. Copies of live test data used in any such testing shall be (if so required by the Purchaser) destroyed or returned to the Purchaser on completion of the test. The Service Provider shall, within twenty (20) Working Days of the conclusion of each test, provide to the Purchaser a report setting out: the outcome of the test; any failures in the BCDR Plan (including the BCDR Plan's procedures) revealed by the test; and the Service Provider's proposals for remedying any such failures. Following each test, the Service Provider shall take all measures requested by the Purchaser, (including requests for the re-testing of the BCDR Plan) to remedy any failures in the BCDR Plan and such remedial activity and re-testing shall be completed by the Service Provider, at no additional cost to the Purchaser, by the date reasonably required by the Purchaser and set out in such notice. For the avoidance of doubt, the carrying out of a test of the BCDR Plan (including a test of the BCDR Plan’s procedures) shall not relieve the Service Provider of any of its obligations under this Contract. The Service Provider shall also perform a test of the BCDR Plan in the event of any major reconfiguration of the Services or as otherwise reasonably requested by the Purchaser.

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