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.
Coordinators The contractor shall assign coordinators as needed to coordinate At-Sea Monitor deployment and provide At-Sea Monitor support services. The coordinator shall be designated as key personnel under this contract (per section H.
Teams One team for the purposes of the Event shall consist of one Vehicle. Each Vehicle can contain a maximum of three Team Members, provided such Team Members have entered into a Team Entry Agreement with the Company or have otherwise agreed in writing to participate in the Event upon and subject to the Terms of Entry and the Event Rules. For the avoidance of doubt, it is the sole responsibility of each Team to inform themselves of the maximum numbers of persons legally permitted to travel in the Vehicle under Relevant Law. The Company shall provide each Team with the contact details of the Approved Hirer who will be able to provide each Team with a Vehicle for use in the Event, subject to the Team entering into an agreement (the "Borrowing Agreement") with the Hirer outlining the terms of use of the Vehicle. Should the Vehicle not be delivered to the Designated Finish Point by 14:00 local time on 19th September 2021, then the team will be liable for the "Hire Costs" outlined below. Each Vehicle will be of a similar specification to that outlined in Schedule 4 to the Team Entry Agreement. For the avoidance of doubt, the Company shall make no representations or warranties as to the suitability of the Approved Hirer or of the Vehicle for participation in the Event and any rights or warranties which a Team may have or be granted in relation to the Vehicle shall be limited to those contained in the Rental Agreement or implied by any Relevant Law.
Manage supervise and administer the Trust Account subject to the terms and conditions set forth herein;
Project Managers The JBE’s project manager is: [Insert name]. The JBE may change its project manager at any time upon notice to Contractor without need for an amendment to this Agreement. Contractor’s project manager is: [Insert name]. Subject to written approval by the JBE, Contractor may change its project manager without need for an amendment to this Agreement.
Train Fund Tri- Fund Org. Fund Total Pkg. W. D. Ded. OPDC Dues Ind. Fund 05/01/07 18.85 1.89 2.40 3.81 0.35 0.10 0.00 27.40 0.56 0.25 0.16 05/01/08 19.17 1.92 2.50 4.06 0.35 0.10 0.00 28.10 0.57 0.35 0.16 05/01/09 19.49 1.95 2.60 4.31 0.35 0.10 0.00 28.80 0.58 0.35 0.16 01/01/10 19.49 1.95 2.70 4.56 0.40 0.10 0.00 29.20 0.58 0.35 0.16 Utility Contractor’s Association 2007-2010
Place and Manner Borrower shall make all payments due to Lender hereunder in lawful money of the United States and in same day or immediately available funds.
Project Team To accomplish Owner’s objectives, Owner intends to employ a team concept in connection with the construction of the Project. The basic roles and general responsibilities of team members are set forth in general terms below but are more fully set forth in the Design Professional Contract with respect to the Design Professional, in the Program Management Agreement with any Program Manager, and in this Contract with respect to the Contractor.
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.
Coordination The Parties shall confer regularly to coordinate the planning, scheduling and performance of preventive and corrective maintenance on the Large Generating Facility and the Interconnection Facilities.
