Fallback Management Sample Clauses

Fallback Management. Contacting the Service Desks may be carried out via e-mail and/or fax 24 hours per day, 7 days a week. The Service Desks may receive telephone calls within the normal office hours (defined in Appendix B). During non-office hours, holidays and weekends if backup personnel are not allocated to support the service, the phone calls should be forwarded to an answering machine. When e-mail and/or fax access is not possible, the NSD will inform the CSD accordingly, within a maximum of one working hour delay. The NSD will inform all involved parties in advance, should an interruption in the service be anticipated, due to e.g., scheduled maintenance activities. On the other hand the CSD will inform all involved parties in advance, should an interruption in the service be anticipated, due to e.g., scheduled maintenance activities or as soon as possible should an unexpected interruption in the service occurs. The National Service Desks should maintain the fallback procedures applicable to its operational standards. Each National Service Desk shall confirm to the CPT the existence of a national fallback procedure applicable to the Service Desk.
Sample 1
AutoNDA by SimpleDocs

Related to Fallback Management

  • Network Management 60.1 CLEC and CenturyLink will exchange appropriate information (e.g., network information, maintenance contact numbers, escalation procedures, and information required to comply with requirements of law enforcement and national security agencies) for network management purposes. In addition, the Parties will apply sound network management principles to alleviate or to prevent traffic congestion and to minimize fraud associated with third number billed calls, calling card calls, and other services related to this Agreement. 60.2 The Parties will employ characteristics and methods of operation that will not interfere with or impair the Parties’ networks, or the network of any third parties or Affiliated companies, connected with or involved directly in the network or facilities of CenturyLink. 60.3 CLEC shall not interfere with or impair service over any circuits, facilities or equipment of CenturyLink, its Affiliated companies, or its connecting and concurring carriers. 60.4 If CLEC causes any impairment or interference, CenturyLink shall promptly notify CLEC of the nature and location of the problem and that, unless promptly rectified, a temporary discontinuance of the use of any circuit, facility or equipment may be required. The Parties agree to work together to attempt to promptly resolve the impairment or interference. If CLEC is unable to promptly remedy, then CenturyLink may, at its option, temporarily discontinue the use of the affected circuit, facility or equipment until the impairment is remedied. 60.5 Any violation of Applicable Law or regulation regarding the invasion of privacy of any communications carried over CenturyLink’s facilities, or that creates hazards to the employees of CenturyLink or to the public, is also considered an impairment of service. 60.6 CenturyLink shall give advanced notice to CLEC of all non-scheduled maintenance or other planned network activities to be performed by CenturyLink on any Network Element, including any hardware, equipment, software, or system, providing service functionality of which CLEC has advised CenturyLink may potentially impact CLEC End Users. 60.7 The Parties shall provide notice of network changes and upgrades in accordance with 47 C.F.R. §§51.325 through 51.335. CenturyLink may discontinue any Interconnection arrangement, Telecommunications Service, or Network Element provided or required hereunder due to network changes or upgrades after providing CLEC notice as required by this Section. CenturyLink agrees to cooperate with CLEC and/or the appropriate regulatory body in any transition resulting from such discontinuation of service and to minimize the impact to customers which may result from such discontinuance of service.

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

  • 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.

  • Contract Management To ensure full performance of the Contract and compliance with applicable law, the System Agency may take actions including: a. Suspending all or part of the Contract; b. Requiring the Grantee to take specific corrective actions in order to remain in compliance with term of the Contract; c. Recouping payments made to the Grantee found to be in error; d. Suspending, limiting, or placing conditions on the continued performance of the Project; e. Imposing any other remedies authorized under this Contract; and f. Imposing any other remedies, sanctions or penalties permitted by federal or state statute, law, regulation, or rule.

  • Financial Management System Subrecipient shall establish and maintain a sound financial management system, based upon generally accepted accounting principles. Contractor’s system shall provide fiscal control and accounting procedures that will include the following: i. Information pertaining to tuition rates, payments, and educational assistance payments; and

  • 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

  • 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.

  • 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;

  • 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.

  • PERFORMANCE MANAGEMENT SYSTEM 6.1 The Performance Plan (Annexure A) to this Agreement sets out – 6.1.1 The standards and procedures for evaluating the Employee’s performance; and 6.1.2 The intervals for the evaluation of the Employee’s performance. 6.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force; 6.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames; 6.4 The Employee’s performance will be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan (IDP) as described in 6.6 – 6.12 below; 6.5 The Employee will submit quarterly performance reports (SDBIP) and a comprehensive annual performance report at least one week prior to the performance assessment meetings to the Evaluation Panel Chairperson for distribution to the panel members for preparation purposes; 6.6 Assessment of the achievement of results as outlined in the performance plan: 6.6.1 Each KPI or group of KPIs shall be assessed according to the extent to which the specified standards or performance targets have been met and with due regard to ad-hoc tasks that had to be performed under the KPI, and the score of the employer will be given to and explained to the Employee during the assessment interview. 6.6.2 A rating on the five-point scale shall be provided for each KPI or group of KPIs which will then be multiplied by the weighting to calculate the final score; 6.6.3 The Employee will submit his self-evaluation to the Employer prior to the formal assessment; 6.6.4 In the instance where the employee could not perform due to reasons outside the control of the employer and employee, the KPI will not be considered during the evaluation. The employee should provide sufficient evidence in such instances; and 6.6.5 An overall score will be calculated based on the total of the individual scores calculated above.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!