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.
Union/Management Meetings The Union Committee and the Senior Union Official of the Union, or her/his representative, shall, as occasion warrants, meet with the Committee on Labour Relations for the purpose of discussing and negotiating a speedy settlement of any grievance or dispute arising between the Employer and the employee concerned, including possible re-negotiations relative to this Agreement and the Schedules which are a part hereof. However, except for renegotiations of Agreements, these matters shall be introduced to such meetings only after the established grievance procedure has been followed. Grievances of a general nature may be initiated by a member of the Union Committee in step two of the grievance procedure outlined in Article 9.04.
Management meetings 31.1 Either the Engineer or the Contractor may require the other to attend a management meeting. The business of a management meeting shall be to review the plans for remaining work and to deal with matters raised in accordance with the early warning procedure.
31.2 The Engineer shall record the business of management meetings and is to provide copies of his record to those attending the meeting and to the Employer. The responsibility of the parties for actions to be taken is to be decided by the Engineer either at the management meeting or after the management meeting and stated in writing to all who attended the meeting.
Labour Management Meetings The committee meeting shall normally be held every second month however, either party may call a meeting of the Joint Labour Management Committee. The meeting shall be held at a time and place fixed by mutual agreement but no later than fourteen (14) calendar days after the initial request, unless mutually agreed.
Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.
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.
Labour Management Committee (a) Where the parties mutually agree that there are matters of mutual concern and interest that would be beneficial if discussed at a Labour Management Committee Meeting during the term of this Agreement, the following shall apply.
(b) An equal number of representatives of each party as mutually agreed shall meet at a time and place mutually satisfactory. A request for a meeting hereunder will be made in writing prior to the date proposed and accompanied by an agenda of matters proposed to be discussed, which shall not include matters that are properly the subject of grievance or negotiations for the amendment or renewal of this agreement. Any representative(s) attending such meetings during their regularly scheduled hours of work shall not lose regular earnings as a result of such attendance.
(c) It is agreed that the topic of a rehabilitation program for drug and alcohol abuse is an appropriate topic for the Labour-Management Committee. It is also agreed that the topic of the utilization of full-time and part-time staff is an appropriate topic for the Labour-Management Committee. The committee shall have access to work schedules and job postings upon request.
(d) It is understood that joint meetings with other Labour-Management Committees in the Hospital may be scheduled concerning issues of mutual interest if satisfactory to all concerned.
(e) Where two or more agreements exist between a Hospital and CUPE the Committee may be a joint one representing employees under both agreements, unless otherwise agreed.
Service Management Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.
Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout
RECORDS MANAGEMENT AND MAINTENANCE CONTRACTOR, its officers, agents, employees and subcontractors shall, throughout the term 12 of this Agreement, prepare, maintain and manage records appropriate to the services provided and in 13 accordance with this Agreement and all applicable requirements.
