AGREEMENT MANAGEMENT Pinellas Community Foundation designates the following person(s) as the liaison for the Xxxxxx Xxxxxx, CEO Pinellas Community Foundation
Exit Management 58.1. The Service Provider shall perform its relevant Exit Management obligations as part of the Contract whether applicable on either the expiry or early termination of this Contract.
58.2. The Service Provider agrees that if it breaches (or attempts or threatens to breach) its obligation to provide Exit Management, the Purchaser and their respective customers and stakeholders shall be irreparably harmed. In such circumstance, the Service Provider agrees that the Purchaser may proceed directly to court notwithstanding anything to the contrary in the dispute resolution procedure outlined in Clause 53 (Dispute Resolution). If a court of competent jurisdiction finds that the Service Provider has breached (or attempted or threatened to breach) any such obligation, the Service Provider agrees that without any additional findings of irreparable injury, or other conditions to interdict, the Service Provider shall not oppose the entry of an appropriate order compelling performance by the Service Provider and restraining the Service Provider from any further breaches or attempted or threatened breaches of its obligations in relation to Exit Management.
58.3. A draft of the Exit Plan shall be produced by the Service Provider and supplied to the Purchaser within [three (3) months] after the Commencement Date and shall include or address the matters specified in Clause 59.3. The Purchaser shall provide to the Service Provider the Purchaser’s comments on the plan within one (1) month of the Purchaser’s receipt of the plan. The Service Provider shall take into account the comments and suggestions of the Purchaser and shall issue the final version of the Exit Plan to the Purchaser within ten (10) Working Days of receipt of the Authority’s comments.
58.4. The Service Provider shall throughout the period of the Contract review, maintain and continuously update the Exit Plan which shall include:
58.4.1. the activities required to enable the Purchaser to re-tender the Purchaser Requirements and/or the provision of the Services;
58.4.2. the activities necessary to support any Replacement Service Provider or the Purchaser in carrying out any necessary due diligence relating to all or part of the Services;
58.4.3. details of the Exit Management to be provided by the Service Provider prior to the Exit Management Date;
58.4.4. support for the Replacement Service Provider or the Purchaser during their preparation of any relevant plan for the transition of the System to the Replacement Service Provider or Purchaser, including prior to and during such transition period;
58.4.5. the maintenance of a ‘business as usual’ environment for the Purchaser during the period when Exit Management obligations are applicable; and
58.4.6. all other necessary activities to support the preparation for, and execution of, a smooth and orderly Exit Management and transfer of all or part of the Services to either a Replacement Service Provider or the Purchaser.
58.5. No amendment of the Exit Plan shall be made without prior written consent of the Purchaser.
Incident Management 3.1. We shall notify You without undue delay after We becomes aware of any accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, stored or otherwise processed by Us or Our sub-processors of which We become aware (“Security Incident”).
3.2. We shall use best efforts to identify the cause of such Security Incident and take the measures We deem necessary and within Our control for remediating and securing Customer Data; We shall coordinate such efforts with You without undue delay.
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.
Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.
Document Management The Contractor must retain sufficient documentation to substantiate claims for payment under the Contract and all other records, electronic files, papers, and documents that were made in relation to this Contract. The Contractor must retain all documents related to the Contract for five (5) years after expiration of the Contract or, if longer, the period required by the General Records Schedules maintained by the Florida Department of State available at the Department of State’s Records Management website.
Performance Management 17.1 The Contractor will appoint a suitable Account Manager to liaise with the Authority’s Strategic Contract Manager. Any/all changes to the terms and conditions of the Agreement will be agreed in writing between the Authority’s Strategic Contract Manager and the Contractor’s appointed representative.
17.2 The Contractor will ensure that there will be dedicated resources to enable the smooth running of the Framework Agreement and a clear plan of contacts at various levels within the Contractor's organisation. Framework Public Bodies may look to migrate to this Framework Agreement as and when their current contractual arrangements expire. The Contractor will where necessary assign additional personnel to this Framework Agreement to ensure agreed service levels are maintained and to ensure a consistent level of service is delivered to all Framework Public Bodies.
17.3 In addition to annual meetings with the Authority's Strategic Contract Manager, the Contractor is expected to develop relationships with nominated individuals within each of the Framework Public Bodies to ensure that the level of service provided on a local basis is satisfactory. Where specific problems are identified locally, the Contractor will attempt to resolve such problems with the nominated individual within that organisation. The Authority's Strategic Contract Manager will liaise (or meet as appropriate) regularly with the Framework Public Bodies' Contract Manager, and where common problems are identified, it will be the responsibility of the Contractor to liaise with the Authority's Strategic Contract Manager to agree a satisfactory course of action. Where the Contractor becomes aware of a trend that would have a negative effect on one or more of the Framework Public Bodies, they should immediately notify the Authority's Strategic Contract Manager to discuss corrective action.
17.4 Regular meetings, frequency to be advised by Framework Public Body, will be held between the Framework Public Bodies' Contract Manager and the Contractor's representative to review the performance of their Call-Off Contract(s) under this Framework Agreement against the agreed service levels as measured through Key Performance Indicators (KPIs). Reports will be provided by the Contractor to the Framework Public Bodies' Contract Manager at least 14 days prior to the these meetings.
17.5 Performance review meetings will also be held annually, between the Authority's Strategic Contract Manager and the Contractor's representative to review the performance of the Framework Agreement against the agreed service levels as measured through Key Performance Indicators. A summary of the quarterly reports will be provided by the Contractor at least 14 days prior to these meetings.
17.6 The Authority will gather the outputs from contract management to review under the areas detailed in the table below. Provision of management reports 90% to be submitted within 10 working days of the month end Report any incident affecting the delivery of the Service(s) to the Framework Public Body 100% to be reported in writing to FPB within 24 hours of the incident being reported by telephone/email Prompt payment of sub-contractors and/or consortia members (if applicable). Maximum of 30 from receipt of payment from Framework Public Bodies, 10 days target 100% within 30 days
Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity
1.1.02 Identify at least one individual to act as the program contact in the following areas:
1. Immunization Program Manager;
Investment Management If and to the extent requested by the Advisor, the Sub-Advisor shall, subject to the supervision of the Advisor, manage all or a portion of the investments of the Portfolio in accordance with the investment objective, policies and limitations provided in the Portfolio's Prospectus or other governing instruments, as amended from time to time, the Investment Company Act of 1940 (the "1940 Act") and rules thereunder, as amended from time to time, and such other limitations as the Trust or Advisor may impose with respect to the Portfolio by notice to the Sub-Advisor. With respect to the portion of the investments of the Portfolio under its management, the Sub-Advisor is authorized to make investment decisions on behalf of the Portfolio with regard to any stock, bond, other security or investment instrument, and to place orders for the purchase and sale of such securities through such broker-dealers as the Sub-Advisor may select. The Sub-Advisor may also be authorized, but only to the extent such duties are delegated in writing by the Advisor, to provide additional investment management services to the Portfolio, including but not limited to services such as managing foreign currency investments, purchasing and selling or writing futures and options contracts, borrowing money or lending securities on behalf of the Portfolio. All investment management and any other activities of the Sub-Advisor shall at all times be subject to the control and direction of the Advisor and the Trust's Board of Trustees.
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.
