Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.
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.
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:
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.
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.
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;
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
Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.
Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5
Office Visits (other than Preventive Care Services) This plan covers office and clinic visits to diagnose or treat a sickness or injury. Office visit copayments differ depending on the type of provider you see. This plan covers physician visits in your home if you have an injury or illness that: • confines you to your home; or • requires special transportation; and • because of this injury or illness, you are physically unable to travel to the provider’s