Service Management Tools Sample Clauses

Service Management Tools. During Phase I of Transition, the Service Provider will obtain access to the monitoring and management tools installed on DIR and DIR Customer’s systems. In Phase II, the Service Provider will review thresholds and identify any changes required to meet SLAs, including installation of new tools if needed. The Service Provider will provide a service measurement tools list (used to monitor and measure SLA compliance) 30 days prior to Commencement. There is no impact to the Service Provider’s solution if it is unable to gain access to the Mainframe tools prior to Commencement.
Sample 1Sample 2
AutoNDA by SimpleDocs
Service Management Tools. During Phase I of Transition, the Service Provider will deploy and manage tools in the Server environment to support Event Management, Configuration Management, Performance Management, Backup and Recovery and Security. The Service Provider will perform two gap analyses: 1) identify the servers without tools; and 2) a threshold analysis for the tools currently deployed. The Service Provider will work with DIR and DIR Customers to prioritize critical servers lacking tools for Phase I tool deployment. Tools will be installed on all remaining servers during Phase II. As appropriate, the tools will be integrated into its Event correlation system which will be integrated into the MSI ITSM’s tool for auto- ticketing. To deploy the tools, the Service Provider will create tool packages (both agent based and agentless) and test the packages in the Service Provider labs against the operating systems that these packages will be installed on. Upon successful completion of the testing, approved change tickets, and administrative access granted to the systems, the Service Provider’s technicians will modify each system with the appropriate package. This approach will ensure that only the right software agents are applied to the required systems and that the right testing has been performed with that agent and operating system combination. If the Service Provider is unable to install their tools onto systems during Phase I, at Commencement the Service Provider will manage the systems as they are managed by the Incumbent Service Provider and start the tools deployment during Phase II of Transition. For systems with no monitoring, the Service Provider will be made aware of outages when DIR or DIR Customers have a problem and call into the Service Desk. The Service Provider also understands that some systems may not have the capacity to accept additional tools. In this case, the Service Provider will manage the systems as they are managed by the Incumbent Service Provider until they are consolidated or refreshed.  Event Management: To ensure no service interruption, the Service Provider will assume management of the Tivoli Monitoring tool. For systems that are not managed by Tivoli, the Service Provider will deploy its monitoring tool(s) to those systems so they can be monitored. The configuration for Event Management will be included in the tool package and that package will only be applied to systems that are not monitored by the Incumbent Service Provider. The Service Pro...
Sample 1Sample 2
Service Management Tools. The Service Provider plans to deploy and manage tools in the network environment that will support Event Management; Configuration Management; Performance Management; and Security. As appropriate, the tools will be integrated into the Service Provider’s Event correlation system which will be integrated into the MSI ITSM’s tool for auto-ticketing. The tools the Service Provider intends to deploy during Phase I are agentless tools that will only need SNMP read strings and ICMP access to the network devices. To deploy the tools, the Service Provider will work with the Incumbent Service Provider to install appliances in the ADC or SDC, as appropriate. The Service Provider will work with the Incumbent Service Provider’s network administrator to obtain cabinet space to install appliances, IP addresses to connect to the LAN, open the appropriate firewall ports and SNMP read-strings to the devices.  Event Management: Service Provider will deploy SevOne network management tool for device event management. This tool will be deployed in Phase I and will be ready for operations at Commencement  Configuration Management: Service Provider will deploy EMC Voyence for Network Configuration Management tool during phase I.  Performance Management: Service Provider will deploy Apparent Networks AppCritical for performance management during phase I.  Security: In order to provide a smooth transition from the existing security infrastructure to the proposed security solution, the Service Provider will implement a phase-in, phase-out approach. During Phase I of Transition, the Service Provider will establish a takeover in place and knowledge transfer strategy for the security tools supported by the Incumbent Service Provider. Until each tool reaches its contract end date or the appropriate master security infrastructure tools the Service Provider is implementing are in place and tested, the Service Provider plans to manage as is under a Transition security operation plan.  Intrusion Detection Services and Intrusion Prevention System: During Phase II, the Service Provider will replace the Incumbent Service Provider’s intrusion detection service with the new McAfee Intrushield appliance architecture as described in the solution documents.  Anti-virus; Host-Based Intrusion Protection Service (HIPS): The Service Provider will leave in place and manage the existing agent based Anti-virus and HIPS enterprise command infrastructure while in parallel build the future McAfee Enter...
Sample 1Sample 2
Service Management Tools. 43 55 6.2.3 Technical Monitoring and Reporting 44 56 6.3 SERVICE MANAGEMENT 45 57 6.3.1 RACI matrix for Service Management 45
Sample 1
Service Management Tools. 1352 The SMP shall provide service management functionalities, where the user accounts, the 1353 provided services and the related resources are managed. The SMP shall also contain online 1354 help, e.g. FAQs, etc. 1355 The Contractor shall provide as far as possible a complete set of service management/operation 1356 tools for ECHA to ensure that ECHA has the appropriate tools and interfaces to efficiently 1357 consume services. Such tools shall be integrated and in or available from the SMP with the same 1358 web based GUI requirements. 1359 The Contractor can read about ECHA’s current toolset in Annex 1: IT Infrastructure Architecture 1360 (CMO). 1361 The Contractor shall provide at least the following Service Management Tools: 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381  users/group management for the SMP, according to a role based access control model, including account management logging (e.g. create, delete, provision, de-provision, security component changes, etc.)  metadata tagging of VMs and other pertinent services, including forced tags that cannot be excluded.  start/stop/redefine the computing resources or services
Sample 1
Service Management Tools. As set forth in this Exhibit to the Services and Support Responsibilities Schedule, the Provider will assume responsibility and provide the Services for the operation, management, and support of Company’s Service Management Tools (SMT) as of the Effective Date and successful completion of a knowledge transfer as described in the project plan. The Service Management Tools as of the Effective Date are reflected in Attachment A to this Exhibit. Any incremental changes to Attachment A shall be submitted through the Service Request process and charged to Company on a time and materials basis for a period of twelve months from the date such Service Request is approved for Provider’s support of requested changes to the applications. During the twelve month period, Provider shall provide to Company a monthly report of the labor hours used to support those applications that Company requests to be added to Attachment A to this Exhibit. After the twelve month period, Attachment A shall be updated to reflect the agreed upon SMT application changes and any applicable Charges for the Service Management Tools Support may be adjusted accordingly as agreed to by the Parties. For those applications removed from Attachment A, the Parties will mutually agree on applicable adjusted Charges based on historical labor hours for those applications and the Agreement shall be updated accordingly. For the SMT described in Attachment A to this Exhibit that are outside of the Facilities, Company shall be charged on a time and materials basis for the application migration services of those servers and applications at Company’s request. The Provider is also required to provide the Services in Section 3.0 of Exhibit 2.6 to this Schedule in conjunction with the Services described in this Section 4.0.
Sample 1

Related to Service Management Tools

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

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

  • Verizon OSS Services Access to Verizon Operations Support Systems functions. The term “Verizon OSS Services” includes, but is not limited to: (a) Verizon’s provision of Reconex Usage Information to Reconex pursuant to Section 8.1.3 below; and, (b) “Verizon OSS Information”, as defined in Section 8.1.4 below.

  • Beta Services From time to time, We may invite You to try Beta Services at no charge. You may accept or decline any such trial in Your sole discretion. Beta Services will be clearly designated as beta, pilot, limited release, developer preview, non-production, evaluation or by a description of similar import. Beta Services are for evaluation purposes and not for production use, are not considered “Services” under this Agreement, are not supported, and may be subject to additional terms. Unless otherwise stated, any Beta Services trial period will expire upon the earlier of one year from the trial start date or the date that a version of the Beta Services becomes generally available. We may discontinue Beta Services at any time in Our sole discretion and may never make them generally available. We will have no liability for any harm or damage arising out of or in connection with a Beta Service.

  • Online Services Microsoft warrants that each Online Service will perform in accordance with the applicable SLA during Customer’s use. Customer’s remedies for breach of this warranty are in the SLA. The remedies above are Customer’s sole remedies for breach of the warranties in this section. Customer waives any breach of warranty claims not made during the warranty period.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

  • Web Services Our Web Services are designed to enable you to easily establish a presence on the Internet. Our Web Hosting and Design is composed of our Web Hosting and Design Publishing Component and other miscellaneous components. These components may be used independently or in conjunction with each other.

  • Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Network Services Local Access Services In lieu of any other rates and discounts, Customer will pay fixed monthly recurring local loop charges ranging from $1,200 to $2,000 for TDM-based DS-3 Network Services Local Access Services at 2 CLLI codes mutually agreed upon by Customer and Company.

Time is Money Join Law Insider Premium to draft better contracts faster.