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 Assumptions
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.
Sample 1Sample 2
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
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

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:

  • Access Management The Engineer shall coordinate and evaluate access management within the project limits in accordance with the latest State Access Management Manual or as directed by the State.

  • Network Maintenance and Management 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.

  • 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 ECI Usage Information to ECI pursuant to Section 8.3 of this Attachment; and, (b) “Verizon OSS Information”, as defined in Section 8.1.4 of this Attachment.

  • 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 described in the SLA.

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

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

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