Service Monitoring & Management Sample Clauses

Service Monitoring & Management. See previous comment. This Section may need to be revised if Vendor will provide hosting services through a third-party hosting provider. Vendor will perform continuous monitoring and management of the Services to optimize availability of Services. Included within the scope of this section is the proactive monitoring of the Server and all service components of Vendor’s firewall for trouble on a 7 day by 24 hour basis, and the expedient restoration of components when failures occur within the time period set forth in Section 8 (Service Outages) of this Exhibit. Vendor shall maintain redundancy in all key components such that service outages are less likely to occur due to individual component failures. Vendor will monitor “heartbeat” signals of all servers, routers and leased lines, and HTTP availability of the Server, by proactive probing at 30-second intervals 24 hours a day using an automated tool. If a facility does not respond to a ping-like stimulus, it shall be immediately checked again. When Vendor receives a “down” signal, or otherwise has knowledge of a failure in the Server or the application software and/or hardware, Vendor personnel will: Confirm (or disconfirm) the outage by a direct check of the facility; If confirmed, take such action as may restore the service in one hour or less, or, if determined to be a telephone company problem, open a trouble ticket with the telephone company carrier; Notify the State of Iowa by telephone or pager according to mutually agreed upon procedures that an outage has occurred, providing such details as may be available, including the Vendor trouble ticket number, if appropriate, and time of outage; Work through the problems until resolution, escalating to appropriate management or to engineering as required; Notify the State of Iowa of final resolution, along with any pertinent findings or action taken, and request concurrence by the State of Iowa prior to closing the applicable trouble ticket.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Service Monitoring & Management. (a) MDC will perform continuous monitoring and management of each Web Site to optimize availability of service. Included within the scope of Service Monitoring & Management is the proactive monitoring of the web servers and all service components of the MDC's firewall for trouble on a 7 day by 24 hour basis, and the expedient restoration of components when failures occur within the time period set forth in "Service Outages" below. MDC shall maintain redundancy in all key components such that service outages are less likely to occur due to individual component failures. i. Permissible Down Time 1. In any month during the term of this Agreement, the Web Sites shall be in a Fully Functional State for no less than ninety-ninety nine and
Sample 1Sample 2
Service Monitoring & Management. Vendor will perform continuous monitoring and management of the Services to optimize availability of Services. Included within the scope of this section is the proactive monitoring of the Server and all service components of Vendor’s firewall for trouble on a 7-day by 24-hour basis, and the expedient restoration of components when failures occur within the time period set forth in Section 10 (Service Outages) of this Exhibit. * CERTAIN INFORMATION HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. Vendor will monitor “heartbeat” signals of all servers, routers and leased lines, and HTTP availability of the Server, by proactive probing not to exceed 300-second intervals 24 hours a day using an automated tool. If a facility does not respond to a ping-like stimulus, it shall be immediately checked again. When Vendor receives a “down” signal, or otherwise has knowledge of a failure in the Server or the application software and/or hardware, Vendor personnel will: Ø Promptly notify Xxxxxx by email, DNAnexus blog or Twitter according to mutually agreed upon procedures that an outage has occurred, providing such details as may be available, including the Vendor trouble ticket number, if appropriate, and time of outage; Ø Work the problems continuously until resolution, escalating to management or to engineering as required; Ø Promptly notify Xxxxxx of final resolution, along with any pertinent findings or action taken, and requests concurrence to close the trouble ticket.
Sample 1
Service Monitoring & Management. Vendor will perform continuous monitoring and management of the Services to optimize availability of the Services. Included within the scope of this section is the proactive monitoring of the Platform and all service components 24 hours a day, 7 days a week, 365 days a year, and the expedient restoration of components when failures occur. Vendor shall maintain redundancy in all key components such that service outages are less likely to occur due to individual component failures.
Sample 1
Service Monitoring & Management. (a) MDC will perform continuous monitoring and management of each Web Site to optimize availability of service. Included within the scope of Service Monitoring & Management is the proactive monitoring of the web servers and all service components of the MDC's firewall for trouble on a 7 day by 24 hour basis, and the expedient restoration of components when failures occur within the time period set forth in "Service Outages" below. MDC shall maintain redundancy in all key components such that service outages are less likely to occur due to individual component failures.
Sample 1

Related to Service Monitoring & Management

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

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

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

  • Information Management Information and Records

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

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

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

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

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