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 EVALUATION OUTCOMES 12.1 Where the Employer is, any time during the Employee’s employment, not satisfied with the Employee’s performance with respect to any matter dealt with in this Agreement, the Employer will give notice to the Employee to attend a meeting;
12.2 The Employee will have the opportunity at the meeting to satisfy the Employer of the measures being taken to ensure that his performance becomes satisfactory and any programme, including any dates, for implementing these measures;
12.3 Where there is a dispute or difference as to the performance of the Employee under this Agreement, the Parties will confer with a view to resolving the dispute or difference; and
12.4 In the case of unacceptable performance, the Employer shall –
12.4.1 Provide systematic remedial or developmental support to assist the Employee to improve his performance; and
12.4.2 After appropriate performance counselling and having provided the necessary guidance and/or support as well as reasonable time for improvement in performance, the Employer may consider steps to terminate the contract of employment of the Employee on grounds of unfitness or incapacity to carry out his or her duties.
Measurement and Billing 5.6.1 For billing purposes, each Party shall pass Calling Party Number ("CPN") information on each call carried over the Traffic Exchange Trunks at such time as the originating switch is equipped for SS7 and from all switches no later than December 31, 1998. At such time as either Party has the ability, as the Party receiving the traffic, to use such CPN information to classify on an automated basis traffic delivered by the other Party as either Local Traffic or Toll Traffic, such receiving Party shall xxxx the originating Party the Local Traffic termination rates, Intrastate Exchange Access rates, or Interstate Exchange Access rates applicable to each minute of Traffic for which CPN is passed, as provided in Exhibit A and applicable Tariffs.
5.6.2 If, under the circumstances set forth in subsection 5.6.1, the originating Party does not pass CPN on up to ten percent (10%) of calls, the receiving Party shall xxxx the originating Party the Local Traffic termination rates, Intrastate Exchange Access rates, Intrastate/Interstate Transit Traffic rates, or Interstate Exchange Access rates applicable to each minute of traffic, as provided in Exhibit A and applicable Tariffs, for which CPN is passed. For the remaining up to ten percent (10%) of calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic as Local Traffic termination rates, Intrastate Exchange Access rates, Intrastate/Interstate Transit Traffic rates, or Interstate Exchange Access rates applicable to each minute of traffic, as provided in Exhibit A and applicable Tariffs, in direct proportion to the minutes of use of calls passed with CPN information.
5.6.3 If the originating Party does not pass CPN on more than ten percent (10%) of calls, or if the receiving Party lacks the ability to use CPN information to classify on an automated basis traffic delivered by the other Party as either Local Traffic or Toll Traffic, and the originating Party chooses to combine Local and Toll Traffic on the same trunk group, it will supply an auditable Percent Local Use ("PLU") report quarterly, based on the previous three months' traffic, and applicable to the following three months. If the originating Party also chooses to combine Interstate and Intrastate Toll Traffic on the same trunk group, it will supply an auditable Percent Interstate Use ("PIU") report quarterly, based on the previous three months' terminating traffic, and applicable to the following three months. In lieu of the foregoing PLU and/or PIU reports, the Parties may agree to provide and accept reasonable surrogate measures for an agreed-upon interim period.
5.6.4 Measurement of billing minutes for purposes of determining terminating compensation shall be in conversation seconds.
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.
SCOPE OF SERVICES/CASE HANDLING A. Upon execution by GPM, attorneys are retained to provide legal services for the purpose of seeking damages and other relief in the Litigation. Client provides authorization to seek appointment as Lead Plaintiff in the class action, while the Attorneys will seek to be appointed Class Counsel. If this occurs, the Litigation will be prosecuted as a class action.
B. If you obtain access to non-public information during the pendency of the Litigation, you must not engage in transactions in securities.
C. Attorneys are authorized to prosecute the Litigation. The appointed Lead Plaintiffs will monitor, review and participate with counsel in the prosecution of the Litigation. The Attorneys shall consult with the appointed Lead Plaintiffs concerning all major substantive matters related to the Litigation, including, but not limited to, the complaint, dispositive motions and settlement. Because of potential differences of opinion between Clients concerning, among other things, strategy, goals and objectives of the Litigation, the Attorneys shall consult with the appointed Lead Plaintiffs as to the courses of action to pursue. The Client agrees to abide by the decisions of the appointed Lead Plaintiffs, which shall be final and binding on all Clients.
D. GPM is given the authority to opt the Client out of any class action proceeding relating to the claims authorized herein and/or pursue the Client claim individually in a group action, if the Client is not appointed Lead Plaintiff and GPM is not appointed Class Counsel.
E. The Attorneys shall provide sufficient resources, including attorney time and capital for payment of costs and expenses, to vigorously prosecute the Litigation.
F. Any recovery from defendants that the Attorneys are responsible for will be divided among class members based on the recognized loss by each class member as calculated by a damage allocation plan which will be prepared by a financial expert or consultant, provided to the appointed Lead Plaintiffs, be subject to the Court's approval and will account for such factors as size of securities ownership, date of purchase, date of sale and continued holdings, if any. Under the rules governing class action litigation, while the Lead Plaintiffs recover according to the same formula as other class members, the Court may approve, upon application therefore, reimbursement of the Lead Plaintiffs’ reasonable costs and expenses directly related to the representation of the class. Examples are lost wages and travel expenses associated with testifying in the action.
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.
Quality Management Grantee will:
1. comply with quality management requirements as directed by the System Agency.
2. develop and implement a Quality Management Plan (QMP) that conforms with 25 TAC § 448.504 and make the QMP available to System Agency upon request. The QMP must be developed no later than the end of the first quarter of the Contract term.
3. update and revise the QMP each biennium or sooner, if necessary. Xxxxxxx’s governing body will review and approve the initial QMP, within the first quarter of the Contract term, and each updated and revised QMP thereafter. The QMP must describe Xxxxxxx’s methods to measure, assess, and improve -
i. Implementation of evidence-based practices, programs and research-based approaches to service delivery;
ii. Client/participant satisfaction with the services provided by Xxxxxxx;
iii. Service capacity and access to services;
iv. Client/participant continuum of care; and
v. Accuracy of data reported to the state.
4. participate in continuous quality improvement (CQI) activities as defined and scheduled by the state including, but not limited to data verification, performing self-reviews; submitting self-review results and supporting documentation for the state’s desk reviews; and participating in the state’s onsite or desk reviews.
5. submit plan of improvement or corrective action plan and supporting documentation as requested by System Agency.
6. participate in and actively pursue CQI activities that support performance and outcomes improvement.
7. respond to consultation recommendations by System Agency, which may include, but are not limited to the following:
i. Staff training;
ii. Self-monitoring activities guided by System Agency, including use of quality management tools to self-identify compliance issues; and
iii. Monitoring of performance reports in the System Agency electronic clinical management system.
Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.
Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:
Management and Control Systems Grantee will:
1. maintain an appropriate contract administration system to ensure that all terms, conditions, and specifications are met during the term of the contract through the completion of the closeout procedures.
2. develop, implement, and maintain financial management and control systems that meet or exceed the requirements of Uniform Statewide Accounting System (UGMS). Those requirements and procedures include, at a minimum, the following:
i. Financial planning, including the development of budgets that adequately reflect all functions and resources necessary to carry out authorized activities and the adequate determination of costs;
ii. Financial management systems that include accurate accounting records that are accessible and identify the source and application of funds provided under each Contract of this Contract, and original source documentation substantiating that costs are specifically and solely allocable to a Contract and its Contract and are traceable from the transaction to the general ledger;
iii. Effective internal and budgetary controls;
iv. Comparison of actual costs to budget; determination of reasonableness, allowableness, and allocability of costs;
v. Timely and appropriate audits and resolution of any findings;
vi. Billing and collection policies; and
vii. Mechanism capable of billing and making reasonable efforts to collect from clients and third parties.
