Avoidance and Management of Short Shifts Sample Clauses

Avoidance and Management of Short Shifts. 47.1 Meaning of 'short shift' 47.2 No short shifts on night duty 47.3 Use of short shifts (a) one 'AM' shift (commencing and concluding within the 'AM' shift); and/or (b) one 'PM' shift (commencing and concluding within the 'PM' shift); and/or (c) one cross over shift, being a shift that commences before 12.00pm and concludes during the 'PM' shift. 47.4 Short shifts only by agreement (a) An Employee will not be rostered to work short shifts unless the Employee agrees to work them. (b) An Employee working a short shift arrangement may cease that arrangement by giving 28 days' written notice to the Employer that they wish to work full shift lengths and the arrangement will cease in the next roster or, if a roster has already been posted in accordance with subclause 45.1, the following roster posted. (c) Nothing in this clause allows for the unilateral changing of an Employee's contract of employment. 47.5 Replacement of rostered shift/s (a) Considerations in the use of replacement shifts (i) patient safety/acuity; (ii) skill mix; (iii) the time at which the absence was notified; (iv) whether the xxxx/unit is staffing above the ratios under the Safe Patient Care Act; (v) the number of short shifts on the xxxx; (vi) the nature of any professional development being provided by the Employer; (vii) the capacity for Employees to attend professional development; and (viii) whether there is any pre-arranged education for casual staff.
AutoNDA by SimpleDocs
Avoidance and Management of Short Shifts. 47.1 Meaning of ‘short shift’ 47.2 No short shifts on night duty 47.3 Use of short shifts (a) one ‘AM’ shift (commencing and concluding within the ‘AM’ shift); and/or (b) one ‘PM’ shift (commencing and concluding within the ‘PM’ shift); and/or (c) one cross over shift, being a shift that commences before 12.00pm and concludes during the ‘PM’ shift. 47.4 Short shifts only by agreement (a) An Employee will not be rostered to work short shifts unless the Employee agrees to work them. (b) An Employee working a short shift arrangement may cease that arrangement by giving 28 days written notice to the Employer that they wish to work full shift lengths and the arrangement will cease in the next roster or, if a roster has already been posted in accordance with subclause 45.1, the following roster posted. (c) Nothing in this clause allows for the unilateral changing of an Employee's contract of employment.
Avoidance and Management of Short Shifts. 47.1 Meaning of 'Short Shift' 47.2 No short shifts on night duty 47.3 Use of short shifts (a) Except as provided at clauses 47.5, 47.7 and 47.8 below, up to two Short Shifts may be used for a xxxx or unit per day using no more than two of the following: (i) one 'AM' shift (commencing and concluding within the 'AM' shift); and/or (ii) one 'PM' shift (commencing and concluding within the 'PM' shift); and/or (iii) one cross over shift, being a shift that commences before 12.00pm and concludes during the 'PM' shift. (b) These limitations do not apply to Short Shifts in addition to ratios. (c) No existing shift length as at the commencement date of this Agreement will be reduced by the operation of (b) above.

Related to Avoidance and Management of Short Shifts

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Workload Management 11.1 The parties to this Agreement acknowledge that employees and management have a responsibility to maintain a balanced workload and recognise the adverse affects that excessive workloads may have on employee/s and the quality of resident/client care. 11.2 To ensure that employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the employee/s may advance the matter through Clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the employer and the employee representative, which may include the union/s.

  • Management of Change a. The parties to this Collective Agreement accept that change in the health service is necessary in order to ensure the efficient and effective delivery of health services. They recognise a mutual interest in ensuring that health services are provided efficiently and effectively, and that each has a contribution to make in this regard.‌ b. Regular consultation between the employer, its midwives and the union is essential on matters of mutual concern and interest. Effective communication between the parties will allow for: • improved decision making; • greater co-operation between employer and midwives; and • a more harmonious, effective, efficient, safe and productive workplace.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • Management of Business (a) No Limited Partner or Assignee (other than the General Partner, any of its Affiliates or any officer, director, employee, agent or trustee of the General Partner, the Partnership or any of their Affiliates, in their capacity as such) shall take part in the operation, management or control (within the meaning of the Act) of the Partnership’s business, transact any business in the Partnership’s name or have the power to sign documents for or otherwise bind the Partnership. (b) The transaction of any such business by the General Partner, any of its Affiliates or any officer, director, employee, partner, agent or trustee of the General Partner, the Partnership or any of their Affiliates, in their capacity as such, shall not affect, impair or eliminate the limitations on the liability of the Limited Partners or Assignees under this Agreement.

  • Procurement of Small Works Works estimated to cost $250,000 equivalent or less per contract, up to an aggregate amount not to exceed $800,000 equivalent, may be procured under lump-sum, fixed-price contracts awarded on the basis of quotations obtained from three (3) qualified domestic contractors in response to a written invitation. The invitation shall include a detailed description of the works, including basic specifications, the required completion date, a basic form of agreement acceptable to the Bank, and relevant drawings, where applicable. The award shall be made to the contractor who offers the lowest price quotation for the required work, and who has the experience and resources to complete the contract successfully. Part D: Review by the Bank of Procurement Decisions

  • MANAGEMENT OF THE BUSINESS Pursuant to Section 00-00-000 of the Act, and as stated in its Articles, the Company’s day to day affairs are managed by the Member. The Member is responsible for the daily operations of the business.

  • Superintendent of Schools The duly appointed executive officer of the Owner authorized to act by and through The School Board of Broward County, Florida. Referred to hereinafter as the Superintendent.

  • Classroom Management The certificated classroom teacher demonstrates in his/her performance a competent level of knowledge and skill in organizing the physical and human elements in the educational setting.

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