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

Related to Service Management Tools

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

  • Internet Services Transfer Agent shall make available to Fund and Shareholders, through its web sites, including but not limited to xxx.xxxxxxxxxxxxx.xxx (collectively, “Web Site”), online access to certain Account and Shareholder information and certain transaction capabilities (“Internet Services”), subject to Transfer Agent’s security procedures and the terms and conditions set forth herein and on the Web Site. Transfer Agent provides Internet Services “as is,” on an “as available” basis, and hereby specifically disclaims any and all representations or warranties, express or implied, regarding such Internet Services, including any implied warranty of merchantability or fitness for a particular purpose and implied warranties arising from course of dealing or course of performance. Transfer Agent shall at all times use reasonable care in performing Internet Services under this Agreement.

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

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition.

  • Collaboration Management Promptly after the Effective Date, each Party will appoint a person who will oversee day-to-day contact between the Parties for all matters related to the management of the Collaboration Activities in between meetings of the JSC and will have such other responsibilities as the Parties may agree in writing after the Effective Date. One person will be designated by Merck (the “Merck Program Director”) and one person will be designated by Moderna (the “Moderna Program Director,”) together will be the “Program Directors”. Each Party may replace its Program Director at any time by notice in writing to the other Party. Any Program Director may designate a substitute to temporarily perform the functions of that Program Director by written notice to the other Party. The initial Program Directors will be: For Moderna: [***] For Merck: [***]

  • Asset Management Services (i) Real Estate and Related Services:

  • Support Services HP’s support services will be described in the applicable Supporting Material, which will cover the description of HP’s offering, eligibility requirements, service limitations and Customer responsibilities, as well as the Customer systems supported.

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

  • Relationship Management LAUSD expects Contractors and their Representatives to ensure that their business dealings with and/or on behalf of LAUSD are conducted in a manner that is above reproach.

  • Information Services The Custodian may rely upon information received from issuers of Securities or agents of such issuers, information received from Subcustodians or depositories, information from data reporting services that provide detail on corporate actions and other securities information, and other commercially reasonable industry sources; and, provided the Custodian has acted in accordance with the standard of care set forth in Section 6 (a), the Custodian shall have no liability as a result of relying upon such information sources, including but not limited to errors in any such information.

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